Hi everyone...
Two days ago, and a few hours after installing the 8.1 update, my mom's J7 touchscreen was unresponsive, including the power button. It ran out of battery, and after I restarted it this morning, it goes to recovery mode after it tries installing system update and the No command screen is displayed.
I've searched on the web for hours and hours for solutions but none of them have worked, most probably because it requires the phone to be connected to the PC, and my PC (Windows 10) isn't even seeing the phone via USB (can't use ODIN nor ADB). BTW, the debug option most probably wasn't turned on prior to soft brick.
Phone Info:
SM-J730G J730GDXS5BRK1
No root
Error on recovery screen (the SD card has been taken out):
======================================
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
Successfully verified dmverity hash tree
=======================================
Additional info: As I've mentioned, the power button isn't responsive, so I press the volume down button to choose the recovery options. I've tried all recovery options except for:
Wipe data / factory reset, as the phone data isn't backed up (mom doesn't want to lose the personal data as much as possible)
Apply update from ADB
Apply update from SD card
All other options are looping back to the recovery screen after installing system update screen.
Lastly, in recovery, there's an option at the bottom that states "Lacking storage booting". I'm sure that would mean something to someone reading this that would help solve the issue.
An OS downgrade or same 8.1 fix is preferred, as long as the phone data is intact. Any and all help would be much appreciated.
Try "Emergency Software Recovery" feature in Samsung Smart Switch for PC.
It could be a hardware issue as well. Clean your USB charging port with a brush and a drop of alcohol. Then dry with a hair drier.
Good evening, have you tried installing the latest version of the firmware by odin?
If not, try this.
probably its touch stopped working after the update because it was not original (already it has been changed) or it can be other cases ..
if you still can not install the newest firmware downloaded from the sammobile site you can do the second procedure.
Such you will find in this same forum.
In it you use the pc miracle box application and downgrade to 7.1.
this is the title of the post.
follow all procedures.
and it will be all right.
Fix Touch does not work on Samsung J7 Pro (J730G, J730GM) when updating Android 8.1
https://forum.xda-developers.com/ga...ix-touch-samsung-j7-pro-j730g-j730gm-t3850177
PS: Putting it into download mode: Turn the device on by holding the volume down buttons + Home + Power
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.
Cloud1245 said:
Then when you get to step II open the twrp and go into settings and uncheck the prompt option to install supersu if it is checked. whenever you do something in twrp uncheck this option. I do not know if this will be your problem but this always happens to me, if not clear at the time of restart the cell phone is in the loop screen exactly because of this option.
Click to expand...
Click to collapse
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.
Marius.Banderas said:
Checked TWRP Settings and there's no option / tickbox for supersu. I think one thing that I'm doing wrong is that I'm formatting data in TWRP during the wipe process instead of just sliding it to restore factory settings. I will try again later today after work.
Also, one thing I've noticed after flashing TWRP is that I have to enter recovery mode twice - the first time, it goes to the No command error screen then goes to stock recovery. Only after a reboot in the stock recovery would the phone enter TWRP recovery.
Click to expand...
Click to collapse
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
---------- Post added at 11:10 PM ---------- Previous post was at 11:05 PM ----------
Cloud1245 said:
Just one more thing. In tutorials on how to install twrp. when you enter twrp the first thing you should do is format the data. then install the rmm state prenormal and bypass files and only then install magisk or a custom rom.
Click to expand...
Click to collapse
https://youtu.be/UOACi_sUDQY
do only steps 1, 4, 5, 6, 7, and 8 of the video description.
Will be all right!
Marius.Banderas said:
Thank you. I've tried 3 times now as I am getting stuck at II. Flash TWRP and fix rom. After I flash the nougat rom via TWRP, phone reboots and the logos keep on looping. Either I am doing something wrong or I'm missing a step, or the zip is not working for my mom's phone.
Click to expand...
Click to collapse
Before trying to flash TWRP, first flash a full stock firmware and make sure your can at least boot all the way up to the main screen.
Once that works, only then try to flash any custom recovery or custom rom.
Same prob
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!
uz91 said:
I've just faced the same problem a few days after my update as well. Did you figure out how to get it back to normal? Thank you!
Click to expand...
Click to collapse
that is a drk error
you can modification the stock firmware with 7z program
1. open your stock firmware go to AP file
2. click rename than erase the (.md5)
3. extarct the file
4. find (system) file
5. make a (.tar) file with (7z) program with the that system file
6. flash
7. done
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
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
No one knows?
kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
What is the model number of your Note 4? When you are at the "no command" screen, try holding the volume up button and then press the power button to take you to recovery. I'd that doesn't work try holding the power button and tapping the volume up button quickly and release all buttons and see if it allows yoj to access recovery. I'd these do not work keep trying different button combinations. I'd you still cannot access the recovery menu you may have to Odin the factory firmware and start over. Let me know what happens.
Sent from my Nexus 6 using XDA-Developers mobile app
none of those button combinations work. I will install stock firmware on it again and see if that fixes the recovery.
I had this problem in the past, I think the problem was that when I was installing TWRP via Odin that I had not powered off the phone so it looked like it installed but actually didn't, try taking out the battery and then boot into recovery or download mode whatever it is that is used for Odin and install again
kratos0605 said:
none of those button combinations work. I will install stock firmware on it again and see if that fixes the recovery.
Click to expand...
Click to collapse
If you cannot get into recovery with any button combination boot to download mode and use Odin to flash all 4 files of the factory firmware. That will give you a fresh start. Let me know how it goes.
Sent from my Nexus 6 using XDA-Developers mobile app
Same here
After holding volume up+middle button+power bar
I get into recovery mode but right after recovery mode it goes into “installing system update….” and then “No command” shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
— Appling Multi-CSC…
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Any sort of help would be appreciated, thank you.
amk58 said:
Same here
After holding volume up+middle button+power bar
I get into recovery mode but right after recovery mode it goes into â??installing system updateâ?¦.â? and then â??No commandâ? shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
â?? Appling Multi-CSCâ?¦
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Any sort of help would be appreciated, thank you.
Click to expand...
Click to collapse
Use the VOLUME UP/DOWN BUTTONS to scroll to WIPE DATA/FACTORY RESET and let it do its thing. When it's done select REBOOT SYSTEM NOW.
Tell me what that does.
fast69mopar said:
Use the VOLUME UP/DOWN BUTTONS to scroll to WIPE DATA/FACTORY RESET and let it do its thing. When it's done select REBOOT SYSTEM NOW.
Tell me what that does.
Click to expand...
Click to collapse
but this will erase all my data from the phone
Yes it will but it is the most likely way out of your bootloop. Before you wipe, connect your device to your PC and boot to recovery. Once your PC recognizes your device internal storage, transfer everything that you can think of.
Sent from my Nexus 6 using XDA-Developers mobile app
fast69mopar said:
Yes it will but it is the most likely way out of your bootloop. Before you wipe, connect your device to your PC and boot to recovery. Once your PC recognizes your device internal storage, transfer everything that you can think of.
Click to expand...
Click to collapse
I'm not in bootloop
My phone is working normally.
I'm trying to root my note 4 N910H (Android 6.0.1 Marshmallow) device
I flashed TWRP recovery using Odin
now I need to boot into TWRP recovery so I can to Flash SuperSu.zip downloaded in my device
what is happening after holding volume up+middle button+power bar
I should expect a menu with install option so I can flash the SuperSUfile in the device internal memory, instead this is happening:
it goes into “installing system update….” and then “No command” shows up and after that I get the following message and options:
Android system recovery
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from ADB
apply update from external storage
apply update from cache
wipe/data/factory reset
wipe cache partition
reboot to bootloader
power down
View recovery logs
Enable cp logging
Disable cp logging
and at the bottom in yellow it says;
# MANUAL MODE #
— Appling Multi-CSC…
Applied the CSC-code : GLW
Successfully applied multi-CSC.
Click to expand...
Click to collapse
If i choose reboot system, the phone will work fine, but I need a way to access TWRP recovery so I can to Flash SuperSu
amk58 said:
I'm not in bootloop
My phone is working normally.
I'm trying to root my note 4 N910H (Android 6.0.1 Marshmallow) device
I flashed TWRP recovery using Odin
now I need to boot into TWRP recovery so I can to Flash SuperSu.zip downloaded in my device
what is happening after holding volume up+middle button+power bar
I should expect a menu with install option so I can flash the SuperSUfile in the device internal memory, instead this is happening:
If i choose reboot system, the phone will work fine, but I need a way to access TWRP recovery so I can to Flash SuperSu
Click to expand...
Click to collapse
That looks like TWRP didn't stick when you flashed it using Odin. Try a different version of Odin and flash TWRP.
Sent from my Nexus 6 using XDA-Developers mobile app
kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
So idk if you've gotten it fixed, but what worked for me was: I had been turning on the phone after odin did its thing, and that caused the oem recovery to reinstall itself. So instead of letting odin auto boot be ready to push the volume up button to put it into twrp recovery. I had to remove my battery to keep it from booting fully.
We need to try another time flash. Conditions - old Odin 3.06, configured to remove reboot.
swhockey347 said:
So idk if you've gotten it fixed, but what worked for me was: I had been turning on the phone after odin did its thing, and that caused the oem recovery to reinstall itself. So instead of letting odin auto boot be ready to push the volume up button to put it into twrp recovery. I had to remove my battery to keep it from booting fully.
Click to expand...
Click to collapse
thanks you saved me lot of time today !!!
Thanks - this helped me too
i have same problem
my phone is samsung j2lte
have you try untick /uncheck the "auto reboot" option on odin app. instead reboot manually after flashing twrp??
my problem not solved either
Thank you. This helped me too.
kratos0605 said:
hey guys! first post but I have been lurking here and there before registering.
Sorry if this is the wrong section to post this in. I am trying to root my note 4 and I installed TWRP using Odin. Now when I go into recovery mode to flash SuperSu, it says "no command" with the android guy laying on the floor. I tried the factory reset option and I installed TWRP again but still same problem. I can still load my phone and use it as usual but now I can't go into recovery mode with TWRP and flash supersu to root it. Anyone know how I can fix this problem? Any help would be appreciated.
Click to expand...
Click to collapse
In ODIN go to 'options' and uncheck 'auto-reboot', then flash TWRP. When it's done, it won't reboot, just pull the battery for several seconds, reinsert it and boot into TWRP Recovery.
Enjoy!
When I try to flash any thing it gets stuck on boot.img
I just flashed TWRP for the first time but it comes up with "Unmodified System Partition" but touchscreen doesn't work for some reason so I cant select anything. I tried removing the battery and rebooting my phone (Galaxy S4 19505) But it just boots back into recovery for TWRP in the "Unmodified System Partition" . Please Help, thanks.
Edit: Should I delete the TWRP disk image from my pc? (My phone also keeps vibrating while turned off). I have also noticed that there is a non physical home back and menue button, did I download the wrong version? I used the TWRP app to download and flash the image.
Hi,
Download the latest image or tar from here: https://dl.twrp.me/jfltexx/ and flash it with either Odin or Heimdall.
Not quite sure about the notice, is it on the screen that asks you if you want to keep the system partition read-only? Then you either need to swipe or click ok.
Normally flashing a recovery should not produce the problems you are describing, did you only flash the recovery?
Hi guys,
first of all i may apologize for my school-engl. and let you know i am really new in the world of roots.
My goal was to flash magisk in the custom recovery mode of twrp. So after about 3h research i flashed twrp with odin, everything worked like described in my intructions (cant post links here yet, it was from android gadgethacks) and root checker confirmed the root.
Now in all the instructions i have read, i am told to reboot in the recovery mode and see the new modificated "custom recovery"-menu where i can flash the magisk.zip in the intall-section.
I dont. Its rebooting in the original recovery mode, where i havent the possibility to flash anything, right?
In my desperation i tried to flash it in the intall section of twrp manager but that didnt work. Magisk Manager doesnt confirm that magisk is installed.
someone here has experience with that missing twrp-recovery-menu or another idea how i could install magisk on my rooted s5neo? Thanks in advance
Bombadadil said:
someone here has experience with that missing twrp-recovery-menu or another idea how i could install magisk on my rooted s5neo? Thanks in advance
Click to expand...
Click to collapse
I'm new to root as well, but I just rooted my own S5 Neo (which is why I saw your post while searching for information), so I'm a couple of weeks ahead of you.
I'm a little unclear why after flashing TWRP you say the root check confirmed root. My understanding is that TWRP alone won't root the phone.
You may have already figured this out, but here's what I needed to do to install TWRP and Magisk. The issue for me was that auto-reboot from ODIN was allowing the phone to clear TWRP before it was installed. I'm not sure what your issue is, but there is one possibility I note below.
My successful procedure follows (ask for clarification if I gloss over something you don't understand). Others should feel free to correct any mistakes I write, since I'm no expert and I'm writing from memory:
1) Download the Magisk ZIP to your phone, so it will be available when needed.
2) Ensure your phone is set for OEM Unlock (via the Settings/Developer Options setting menu, which is only shown after you activate it by going to Settings/About Phone/Software Information and tapping Build number 7 times).
3) Download the TWRP *.img.tar file to your PC. Make sure it was made for your model phone.
4) Start ODIN on your PC, and use the AP button to load the TWRP *.img.tar file. Wait for ODIN to finish checking it.
5) In ODIN's Options tab, unselect "auto reboot", so your phone won't reboot when done.
6) Turn off your phone, then boot into Download mode (vol_down+home+power button) and confirm with vol_up button.
7) Now connect the phone to the PC with a USB cable and confirm that the "Added!" message shows in ODIN.
8) Click Start in ODIN to flash TWRP to your phone. Wait for the top left to show a green PASS message.
9) At this point, your phone is connected and still in Download mode. Detach the cable and hold Vol_down+power until your phone shuts off (maybe 10-20 sec).
10) Boot into Recovery mode (vol_up+home+power). The phone should now be installing TWRP. Wait until it finishes and then shows something.
11) My memory here is fuzzy. I don't recall whether TWRP immediately shows now, or if the phone boots normally, or it asks you whether to boot or shutdown, so here are five possible routes:
11a) If the phone shows the TWRP window, go to step 12. I think this is what should happen.
11b) If the phone shuts off, boot into Recovery mode again. This should now be TWRP, so go to 12.
11c) If the phone boots normally, shut it off and boot into Recovery mode. This should now be TWRP, so go to 12.
11d) If the phone asks you what to do, select power off and then boot into Recovery mode. This should now be TWRP, so go to 12.
11e) If booting into Recovery doesn't show TWRP, then something is not quite right with my instructions, or how you followed them, so come back here with the results.
12) Here's where your issue may be. TWRP is installed temporarily by default, and restarting the phone will overwrite it. During this temporary time, you can immediately flash a Zip, then reboot and get your original stock recovery back. You may have restarted the phone without realizing this, which then overwrote TWRP. So you need to decide whether your want it temporarily to flash Magisk, or keep it permanent for other uses (like making Nandroid backups). To make the choice, TWRP asks you whether your want to "Keep Read Only" mode (temporary) or not (permanent).
13) If TWRP is temporary, you need to install Magisk now before rebooting. If it's permanent, you can reboot and do it later. In the TWRP menu, tap Install. Navigate to the location where you placed the Magisk ZIP. If you don't see it, look at the lower right button. If it says "Install Image", it should be showing available Zips. If it says "Install Zip", then it's showing images, so tap it to show Zips.
14) Select the Magisk Zip and it should be installed. Go back to the main TWRP menus and tap Reboot, then System to restart your phone.
15) Look in your Apps for the Magisk Manager. It should have been installed from the Zip. Open it and check that "Installed Version" has a green check. That should be it.
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