No recovery or download on SM-T500 - Samsung Galaxy Tab A series Questions & Answers

Seems I found a way to semi brick my SM-T500. I was attempting to install the LOS 18.1 ROM just posted in the guide section. Some how I got the "can only install official" error message on my download screen after flashing TWRP. Made the mistake of flashing only the stock AP without BL or CSC and now I can't get into either recovery or download modes. Holding vol up and down and plugging in USB cable does nothing. Same with holding power button and either vol up or down. Blank screen. Can only power on and boot to system.

Did you install twrp and can you get into recovery. I had similar problem but was still able to get into download mode from power off. However to do so I had to boot into twrp and select reboot and power off... from that menu you can also boot directly to download mode... I know that doesnt halp much if you hadnt installed twrp yet... but thought I would throw that out there...

wizzdome said:
Did you install twrp and can you get into recovery. I had similar problem but was still able to get into download mode from power off. However to do so I had to boot into twrp and select reboot and power off... from that menu you can also boot directly to download mode... I know that doesnt halp much if you hadnt installed twrp yet... but thought I would throw that out there...
Click to expand...
Click to collapse
I can't boot TWRP or download. The only thing that will boot is system. Can't even get to the lock/unlock screen.

can you connect to adb shell? and try #reboot download
or #reboot twrp. I figure if you get to download you can reflash stock and start over.
Also when your trying to boot into recovery try not being plugged in. Not sure about this device but a lot of older Samsung's that I had would not let me get into recovery if I was plugged in during boot.

Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset

I saw alot of issues with twrp so I tried Magick for first time ever on my SM-T500 and had a minor hiccup bc I wasn't paying attention to firmware and installed an old AP with newer firmware but ended up just reflashing the whole tablet with the same firmware as the AP that is required for Root and presto it worked! AND HEY IM DEF A NEWBIE!

housemusix said:
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
Click to expand...
Click to collapse
Yeah I've run into the same thing, I originally missed the step to run Magisk after I flashed the patched tar and rebooted into the System and it triggered the "Prenormal KG state" problems. Finally I managed to flash stock ROM back and got to exactly where you are now.
I was able to just flash the patched Magisk AP without CSC and BL, and now it will only go to stock recovery and was able to get TWRP to work once but couldn't factory reset or wipe cache due to (which I assume was) a ton of mounting failures when it loaded.
Anyone else have suggestions to get this thing stable so I can flash LOS? I can get to Download mode.

hello, I post this because it's seems the same subject. I have to password protected (forget password) original rom tablet (non root). For me the datas are not important , I just want to remove the password or reflash with original rom. I downloaded Odin , usb driver and correct firmware. I select AP firmware with Odin, I see the connexion (COM3 green) and it's stuck to "setup connexion".
My problem is that it's impossible to enter in download mode.
When I try to shutdown the tablet, it ask me for a password.
When I press for seconds the power button , after few second I see the Samsung Logo and the tablet restarts.
I try to press volume up, volume up and volume down etc...but each combinaison...no recover, no download mode, nothing and impossible to flash . is it normal ? how to do to unsticked SetupConnetion ?
regards
bruno

housemusix said:
Locked oem mode
Locked download mode
Locked wipe factory
Locked update from sd card
Recycling item...
Need factory reset
Click to expand...
Click to collapse
This is not the same as my problem. My problem is that I flashed AP without BL and the two don't match. It isn't that things are locked but that I can't boot to anything but system. Can't boot recovery or download so I can't flash ANYTHING. Not even stock.

Related

Samsung Galaxy S5 SM-G900F 5.0 stuck during root

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

HELP Soft Bricked A2017U

The issue I am having is that I wanted to set my phone back to factory, after I relocked the bootloader my phone when booting(with or without the volume keys) would shut off right after showing the ZTE boot screen. Now when I connect it, it shows up as HS-USB QDLoader 9008 (COM5)..
Ive been looking at these two forums similar to my problem:
https://forum.xda-developers.com/axon-7/help/bricked-a2017u-t3573798
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
I understand I should use the axon7tool(When I try "axon7tool -r boot" i get failed to connect) , but I dont know exactly what I am doing.. I apologize for me being so dumb about this but if someone could please spell out exactly what I would have to do, to get my phone back to factory settings. Any help would be greatly appreciated.
RECAP: Bootloader locked, shows up as HS-USB QDLoader 9008 (COM5), It did have TWRP.
EDIT: When trying MiFlash, I get a ERROR_BAD_FORMAT 0
I just did the exact same thing you did and had the same issue. What worked for me was downloading the factory image from ZTE, putting it on an SD card, going into stock recovery (vol up + power) and select apply update from sd card. The file you download from ZTE is double zipped, so make sure to extract the update.zip file from the parent zip before you put it on the SD card. It will be in a folder with the same parent zip name. I no longer can boot into bootloader from stock recovery (not sure if that's normal), but at least my phone works again. Here's the link.
https://www.zteusa.com/axon-7#support
Hope this helps.
EDIT: I also had TWRP when I locked my bootloader, so I'm assuming you're able to get to stock recovery with volume up + power.
Doesnt let me boot into anything.. Not sure how I screwed it up this badly. Im trying a MiFlash method right now to see if it helps
what happens when you hold down volume up and power button at the same time? you should feel a vibrate and when you let go, you should see the stock recovery.
No, Just shuts off after the ZTE logo pops up
The phone might still be on at that point. When the ZTE logo would pop up for a split second for me, MiFlash was able to see the phone. What happens when you just hold the power button for about 10 seconds right after the screen goes off? Does it stay off?
I believe you are right, when the logo isnt up(after it disappears) that is when it connects as the COM5 otherwise when the logo pops up it disconnects the resumes the cycle.
so if I hold it, it just keeps showing the ZTE logo then shutting off
Just to clarify, holding down both the volume up and power button simultaneously at the same time for at least 3-5 seconds after the phone is off (not after the screen goes blank after the ZTE logo) still gives the same result as if you just pressed the power button?
Yes.
If MiFlash can see the phone, maybe you can unlock the bootloader again?
exact same problem as you, except MiFlash successfully flashes B19 but it still doesn't boot
What you need is FLASH stock recovery in EDL Mode.
That will fix your problem..
P.S. as soon you boot your device after Flashing stock recovery ,will perform a factory reset.
DrakenFX said:
What you need is FLASH stock recovery in EDL Mode.
That will fix your problem..
P.S. as soon you boot your device after Flashing stock recovery ,will perform a factory reset.
Click to expand...
Click to collapse
I'm on stock recovery but I still get stuck on ZTE logo
Fazedyrus said:
I'm on stock recovery but I still get stuck on ZTE logo
Click to expand...
Click to collapse
You should download YOUR variant SDCARD UPDATE zip and flash using stock recovery.
DrakenFX said:
You should download YOUR variant SDCARD UPDATE zip and flash using stock recovery.
Click to expand...
Click to collapse
"E:failed to map file, Installation Aborted"
I have not tried to flash a redownloaded version of B15 because I cannot move the file onto my sd card. I was able to flash a signed twrp on locked bootloader before to enable MTP, but whenever I flash a signed twrp now, I just get stuck on zte screen. Why is this phone so inconsistent?

Trouble flashing TWRP

Hi, everyone.
I have a galaxy s8 SM-G950FD. I have once flashed TWRP and rooted the device successfully.
Then I tried to install a custom ROM but I got bootloop.
After that, I flash official ROM to unbrick my device. But since then, whenever I tried to flash TWRP again I got this message "Verification failed unable to restart your device the integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
My device is still working fine but I want to try to flash a new ROM (even if I may brick my device forever). I don't know what to do. Can you guys give me some advice ?
Thank you!
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
But I cannot boot into TWRP. How can I do that ?
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
MikeTheTechSavvy said:
It's quite a simple fix I think: You need to make a backup of the Data partition and then do a wipe using TWRP. This happens because TWRP cannot handle Samsung's Encryption; the only way to bypass this problem is by formatting once again.
Click to expand...
Click to collapse
MikeTheTechSavvy said:
If you're stuck in the bootloop you should press the force reboot key combination: Power Down + Home + Power. After the device restarts switch the Volume Down key for the Volume Up key right after the screen goes blank. That should get you into TWRP (if it's correctly installed), otherwise directly into the stock recovery.
Click to expand...
Click to collapse
I cant flash/get into TWRP. I tried to boot into stock recovery and do a system wipe/factory reset. Then I flash TWRP again but nothing seem to happen. I tried to boot into recovery and it get me to the stock recovery not TWRP.I did unlock OEM, used Odinv3.12, twrp-3.1.1-2-dreamlte.img.tar.
I had the same issue.
After Odin has flashed the Recovery it performs an auto reboot (if checked in Odin). So at this reboot hold Vol up + Home + Power as soon the screen goes of. You need to be quick. Then it should boot into TWRP.
True, Samsung's stock recovery is very persistent lately and if you tick the auto-reboot you have to be very fast in switching to Recovery mode combo.
Otherwise you can choose not to tick auto-reboot, force restart the device after the TWRP flashing was successful and immediately switch to the Recovery combo.
Here you go: two ways of doing this.

[SOLVED] Can not install TWRP [#failed to open recovery] Help!

[ORIGINAL POST] - solution further down - (TLDR do not reboot into system after flashing recovery)
Hi,
I'm trying to install TWRP but when i've flashed PDA via ODIN and reboot into recovery, this is what i get. [see images] https://imgur.com/a/zfdvs
TWRP file from TWRP website: 'twrp-3.2.1-0-dream2lte.img.tar' for Samsung Galaxy S8+ (Exynos) (dream2lte)
As this did not work i tried to flash new BL and CP and then i retried to install TWRP, no luck.
Can you please help me! Thanks!
I also tried flashing TWRP (another version just to be safe) via heimdall, but that didnt work either. The enitire prosess is fine, but when i reboot into recovery i still get to the same page. [see images above]
[SOLUTION]
*Do not* boot into system after flashing recovery (TWRP), instead, make sure to boot directly into recovery.
Apparently Samsung Reinstalls recovery when you boot into system after flashing TWRP (or any other recovery for that matter). I do not know if it's like this for all Samsung devices or only the S8, but that's the way it is.
Credit from this article and comment section: https://davideddu.org/blog/posts/how-to-flash-a-recovery-image-using-heimdall/
I had the same problem and found instructions to press volume down + bixby + power and then start the Odin load. The load went fine but my phone locked up at the Samsung Logo screen. I tried getting back to the download mode but the screen went black. Now the phone will not power on at all. Exceedingly frustrating.
I've spent 2 hours trying to work out what did I do wrong (checking hashes, odin version, etc) and the simple solution was to boot into recovery right away after flashing via Odin. Thanks!
Hektor1154 said:
I've spent 2 hours trying to work out what did I do wrong (checking hashes, odin version, etc) and the simple solution was to boot into recovery right away after flashing via Odin. Thanks!
Click to expand...
Click to collapse
I've followed different procedures but basically use ODIN to push TWRP to my SP-580. After that, the tablet reboots. I disconnect the cable and power the tablet down. I then hold VOLUME DOWN and VOLUME UP and connect the cable again. But instead of going into recovery mode, it just shows me the percent charged dial. I can get no further than that and have done that at least 15 times. HELP???? Thank you!!

[solved!] Used ODIN to install twrp but phone won't boot into recovery at all

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

Resources