I recently used Odin to flash a custom recovery on my samsung galaxy j3 (SM-J320W8 is the model) and odin said that it succeeded. However, when I try to boot into recovery, a message pops on in the top left corner, and says recovery is not senadroid enforcing and stays there. I can pull the battery and reboot normally into the Os no problems. I was able to boot into the stock recovery before this process.
my phone recently randomly crashed and got into a bootloop (no prior modifications). I had to factory reset, losing all data on internal memory. To prevent this, I want to use a custom recovery so i can backup my internal storage. What can I do to fix this? I have no interest in rooting my phone, I simply want the custom recovery to work. Running on Android 6.0.1
AliTheAce said:
I recently used Odin to flash a custom recovery on my samsung galaxy j3 (SM-J320W8 is the model) and odin said that it succeeded. However, when I try to boot into recovery, a message pops on in the top left corner, and says recovery is not senadroid enforcing and stays there. I can pull the battery and reboot normally into the Os no problems. I was able to boot into the stock recovery before this process.
my phone recently randomly crashed and got into a bootloop (no prior modifications). I had to factory reset, losing all data on internal memory. To prevent this, I want to use a custom recovery so i can backup my internal storage. What can I do to fix this? I have no interest in rooting my phone, I simply want the custom recovery to work. Running on Android 6.0.1
Click to expand...
Click to collapse
You need to find compatible Recovery for your phone.
Exp. I created CWM Recovery and flashed via Odin and same message on left corner.
I resolve this flashing TWRP recovery for my phone.
Which phone you have?
Maybe your phone have Carrier limitations?!
---------- Post added at 11:52 AM ---------- Previous post was at 11:49 AM ----------
AliTheAce said:
I recently used Odin to flash a custom recovery on my samsung galaxy j3 (SM-J320W8 is the model) and odin said that it succeeded. However, when I try to boot into recovery, a message pops on in the top left corner, and says recovery is not senadroid enforcing and stays there. I can pull the battery and reboot normally into the Os no problems. I was able to boot into the stock recovery before this process.
my phone recently randomly crashed and got into a bootloop (no prior modifications). I had to factory reset, losing all data on internal memory. To prevent this, I want to use a custom recovery so i can backup my internal storage. What can I do to fix this? I have no interest in rooting my phone, I simply want the custom recovery to work. Running on Android 6.0.1
Click to expand...
Click to collapse
Which model of phone you have?
Maybe your phone have Cartier limitations!?
---------- Post added at 11:54 AM ---------- Previous post was at 11:52 AM ----------
Which phone you have?
Maybe phone have Carrier limitations?!
Did you try compatible recovery for your phone?
Related
I have to think I'm not the first to be in this situation but my searches didn't turn up anything that looked familiar.
I rooted the stock phone and installed TWRP 2.6xx a month or two ago with no issues. Everything's been running great and I decided it was time to make another backup using TWRP.
After a successful backup I wiped dalvik and cache out of habit and went to reboot -- TWRP said I was not rooted and wanted to know if I wanted to install SuperSU? This question was unexpected since I'd been rooted for a long time, and I decided to just say yes. The phone rebooted and stopped at the Samsung Galaxy S4 boot screen. I did up-volume reboot to recovery, but it seemed to hang at the TWRP blue screen -- I later discovered it will eventually get to the menu after a minute or two of the blue screen. I tried wiping cache and dalvik again and rebooting -- every time I try to reboot now it asks if I want to install SuperSU -- whether I say yes or no seems to make no difference -- I've tried both several times. Every time it hangs at the Samsung boot screen, or it takes forever to get to TWRP if I'm booting to recovery.
I've tried wiping cache, dalvik and data with no improvement. I finally tried formatting data, but again no improvement. I also tried restoring my backup several times and wiping cache and dalvik but still stuck.
I prior to today's problems I'd used TWRP a number of times and I don't recall it asking the SuperSU question, so I am thinking that is the key to this problem, and I'm wondering if anyone knows what it means?
You need to go to 2502 twrp, 26+ has hanging problems and possible Partition issues, also what rom are you on? Do you need to flash super su along with the rom /gapps?
Here's the twrp forum for us SPH-L720
The last page has a download link for the most stable build for us good luck!
http://forum.xda-developers.com/showthread.php?t=2262999
I'm running what came on the phone, just unlocked, rooted, and installed TWRP.
I ran CM10.1 on my previous phone and currently on my tablet, but my impression from running it previously is CM is a downgrade in voicemail functionality (you get these annoying text messages and have to call the voicemail), and I'm assuming it doesn't support the special GS4 hardware features like being able to hover your finger.
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Nerva said:
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Click to expand...
Click to collapse
How did you root? CF auto root also installs SuperSU
Do you have a back up from when you were rooted? IF twrp keeps giving you problems, use cwm, are you able to get past the Samsung boot..
Yeah that's what I did back when I rooted it months ago. I tried running CF auto root again today and it didn't work, so I ran it from Odin and it did work that time, but there was no change -- still hangs on the Samsung boot screen, although now I'm back to the stock recovery. So I tried installing the stock MF9 firmware from Odin -- still hangs on the boot screen. I don't know what to do at this point...
After mf9 install avd stock recovery did you factory reset
Yes, I did a factory reset -- followed the video instructions by qbking77. Still hangs on the boot screen.
Take out battery.. Put back in. Go to stock recovery, holding all 3 buttons volume up factory reset.. If you used odin abd flashed mf9 it should fix you?
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Well I guess I tried man, someone who has more knowledge should chime in now
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
This
http://forum.xda-developers.com/showthread.php?t=2400192
Im also stucked with the same problem!! After flashing my rom succesfully it just ask ur device is not rooted swipe to install!! I tried all the posiblities!! but i stuck with the boot image!! pls help me!!
From experience it sounds like you should head over to sammobile and Odin back to stock and start fresh.
1. Odin to stock
2. Root phone
3. Put desired recovery
4. Flash ROM (be sure to read dev install instructions some require reboot of recovery after wipe)
5.try to restore backup (best if you flash ROM that is backup then restore backup)
6.if you went into nae or ng2 you cannot downgrade to me
7.google has many solutions
Sent from my SCH-I545 using XDA Free mobile app
Sorry for necro, but did anyone figure out a solution to this? This just happened to me.
Just Reflash it
We have the same issue, tried to install supersu binary, after installing through twrp recover, my phone went bootloop, as i've tried to search the internet, the issue doesn't fix by by most of the users unless they reflash their device. though its a bit hassle starting from zero, but atleast, you got ur device back
This helps me:
1. Run Odin on your computer and, after entering download mode on your phone, establish a connection between your devices with the help of the USB cable.
2.Note: for download mode – power off your smartphone and then press and hold, at the same time, the Power, Volume Down and Home buttons.
3.Odin will try to recognize your device; if everything works as expected, on the program the “added” message will be displayed and the ID:COM field will be turned yellow, or blue. (Note: if that’s not happening, unplug the USB connection, close Odin, force restart your phone and reinstall the USB drivers on your computer before retrying the steps from above)
4.From the program click on the “PA” button and load the custom recovery image; don’t check Re Partition and Auto Reboot options.
5.When done, click on “start” and wait while TWRP recovery is being added on your phone
6.In the end, Odin will display the “pass” message and the ID:COM filed will be turned green (or other color) with message - RESTART; you can then remove the USB cord and reboot your smartphone.
I have had this prob on a few things , if you have a backup,flash any mod that will go to the device will do then run the backup and reflash should work .and if you have twrp try to reformat all but the system and see if that helps.
Good luck.
Hi to everyone.
Today, I installed the TWRP and the ROM and both were installed correctly on a Le Pro3 X722. The problem started when the Google services were updating. Suddenly, the phone restarted and entered in a bootloop. I was not even able to enter the TWRP. The page freeze on LE-Recovery logo and then crashed (fill full of lines). I disconnected the battery for a while and then, I was able to enter the TWRP for 2 time but recovery crashes in few seconds. I wanted to wipe and install a clean rom but I cannot enter TWRP anymore.
Please, Is there someone that could help me?
Thank you very much in advance
PS. My phone is not recognized via ADB. I tried with the AIO Tool but my device is not detected.
Hi, I followed the whole process for Qfil explained here:
Leeco Le Pro3 x720 Hard Brick
So the phone was running lineageos 15.1 nightly from 22.08 which i guess was kind of really unstable (even opening twitter in the morning could turn off the device. It could be turned back on right away though), xposed framework v90 w/yt...
forum.xda-developers.com
Installation was correct but nothing change in my phone:
- same start page and bootloop
- Same problem trying to access the recovery.
Now, i can connect via fastboot and I would like to install a fastboot rom (preferable EUI stock 20) but I cannot find one. All links are dead.
Thank you very much in advance
Hi guys,
So I've been playing with my S4 GT-I9505 since it was released , flashing different ROMS, customs recoveries and so on... It sometimes went bad, but I always was able to recover the phone because I could access Download Mode.
At the beginning of this week, I was testing an AOSP MM build for GS4 with TWRP 2.8.7.2 and F2FS. Since almost all of the apps weren't working, I decided to do a TWRP backup and restore from my TWRP of JDCTeam's 5.1.1 custom rom based on CM12.
I kinda made a mistake and decided to recovery my boot partition also. Phone booted up then couldn't boot system. Then the screen flashed weirdly, and went progressively yellow, with the samsung logo fading in the background. So I pulled the battery there, and rebooted. Phone couldn't boot recovery nor system. But I could enter Download Mode. So I decided to flash TWRP Recovery 2.8.7.2, but I still couldn't enter recovery.
Since, I've tried and flashed for 5 or 6 times a Stock ROM (5.0.1 ) through both Odin and Heimdall, with and without Auto-Reboot in order to make a Hard Reset after by pulling the battery, with and without Re-Partitioning with the PIT file.
The phone no longer says "set warranty bit: custom " and so, but still can't enter in recovery or system...
What do you think I should do? Send it to the after sales service (even if I got no warranty anymore)? Is there a secret trick?
PS: The last custom ROMs I flashed were quite particular (custom kernel, f2fs support (that I used)) and KIES does not seem to be able to help
Note Stuck in First Boot screen where it says galaxy note 3 sm-n9005
I had aryamod.
Installed xposed(which i shouldnt have).
Rebooted.
It got stuck into samsung logo.
Decided to do a rom install.
After the rom install its stuck in first boot logo. When powered on it gives a vibrate. Remain stuck at that screen. No LED blinking or anything.
Tried to wipe cache factory reset format and even tried to flash again.
::UPDATE::
Flashed SlimKat Custom Rom.
It is working now.
Afraid to Flash Stock Rom over it again, Don't wanna **** up.
Any suggestions?
Via recovery mounts and storage Format system data cache .
Boot to download mode flash stock rom via Odin .
You wanted to flash Xposed on AryaMod.
If you read the thread, many users (including me) have said to flash arter97's version 75 xposed.
Nobody got bootlop with this version
---------- Post added at 08:02 PM ---------- Previous post was at 08:01 PM ----------
And now best option is to flash Stock via Odin (as mentioned above) and then try others.
Hey guys,
So I rooted my Note 4 about 6 months ago using Odin and CF Auto root. Today I decided i wanted a custom recovery and opted to go with TWRP. I'm not sure what i did wrong, but its been a nightmare. Now my phone will not boot. I get the the red "recovery is not seandroid enforcing" message on the top and it just gets stuck on the screen which says Samsung Galaxy Note 4 . When i go to recovery mode, im able to access TWRP. And it seems to be installed and working. But i cant get my phone to boot and work like normal. I'm thinking if i can some how flash back the original STOCK Recovery with odin it may fix the issue? I really dont want to loose all my data. I did make a backup of boot, data and system with TWRP but this was only after the phone didnt boot.
So my main question is:
1. If i can find the stock recovery for my phone, and flash it over TWRP with odin would that fix things?
2. If not, could I flash back to factory rom (delete everything) Then re-root and try install TWRP again. And then restore the data / system backup i have stored on my external SD with TWRP to get back all my phones data?
Thanks in advance!
Hi everyone! Surfed the forums in the past for some minor help but never needed to register till now. I've tried everything and can't get my phone to boot.
So last night while camping my phone started boot cycling out of nowhere. I let it try a few times and then removed the battery and went to sleep. This morning I woke up and tried a few more times, replaced the battery with a non-stock double-capacity one I have, and still cycled. Sometimes it restarts on the Galaxy Note 4 logo, and sometimes on the Sprint logo. It will do this indefinitely. At one point It finally booted and said it was updating apps (like from an Android update, not the regular app updates.) Before I could do anything else with it though, the battery wiggled loose and it started power cycling again. Because of this one boot I think the root cause is related to an Android update that decided to run without my permission.
So I gave up and drove hoe from camping. Tonight I had tried everything I could find from factory reset to the toolkit to Odin and nothing has had any effect. The toolkit didn't see the device, and Odin failed to flash. Can anyone help me? I can boot to recovery and I can get into download mode, but nothing seems to work. The phone isn't hard bricked, but everything I can find on soft brick solutions hasn't worked. Thanks in advance!
~Evan
Oh also, when I boot into recovery mode it says "installing system update" with the android open chest logo, and then goes to a dead android and says "no command" before getting into the recovery mode menu.
ekuest said:
Oh also, when I boot into recovery mode it says "installing system update" with the android open chest logo, and then goes to a dead android and says "no command" before getting into the recovery mode menu.
Click to expand...
Click to collapse
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.
Trex888 said:
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.
Click to expand...
Click to collapse
Ok thanks that worked! I got into TWRP by setting Odin to not reboot. If I let it reboot then it just restarted after the TWRP flash and kept power cycling like before. If I uncheck auto reboot in Odin then after the flash I can pull the battery (can't figure out any other way to turn the phone off) and then when I restart in recovery mode it goes into TWRP. From there I tried a factory reset (wipe data, cache, and dalvik) and that didnt fix the power cycling. Do I have to flash TWRP and then immediately flash a rom right after? Or should I try an advance wipe in TWR, or maybe "repair or change file system" from the advanced wipe menu?
Bump? I still can't boot my phone. Got into TWRP but no idea what to do from there. I can't flash any rom successfully in Odin and I can't get the phone to boot. Now it just hangs on the "Samsung Galaxy Note 4" splash screen, doesnt even go to the "Samsung" screen or the "Sprint" screen like it used to.
Trex888 said:
If you able to go download mode then flash twrp recovery in odin and go to twrp recovery for your specific model and do clean wipe system then flash any rom for your model.then wait 10 to 15 minuts until phone boot.
Click to expand...
Click to collapse
how do you do the "then flash any rom" part? i have no idea how to do that since Odin doesn't seem to work.
ekuest said:
how do you do the "then flash any rom" part? i have no idea how to do that since Odin doesn't seem to work.
Click to expand...
Click to collapse
1,Flash twrp recovery in odin
2,press volume up+home+power button and boot into twrp
3,in twrp go to wipe/advance wipe and wipe system/cache/data/dalvik cache
4,Flash any custom rom for your model from twrp recovery
If you allready have twrp installed then skip 1 and download any rom like cm12 and gapps
Then flash from twrp
Trex888 said:
1,Flash twrp recovery in odin
2,press volume up+home+power button and boot into twrp
3,in twrp go to wipe/advance wipe and wipe system/cache/data/dalvik cache
4,Flash any custom rom for your model from twrp recovery
If you allready have twrp installed then skip 1 and download any rom like cm12 and gapps
Then flash from twrp
Click to expand...
Click to collapse
Do I just go to install in TWRP and then select the zip file on my microSD card? I tried that with N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip and if says "Could not find 'META-INF/com/google/android/update-binary' in the zip file. Error installing zip file '/external_sd/N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip'" Then I tried with a CM called cm-12.1-20161016-NIGHTLY-trltespr.zip and it seemed to work, and showed a little blue android face but then it still wouldnt boot. Now when I try to start the phone it says "KERNEL IS NOT SEANDROID ENFORCING Set Warranty Bit: Kernel" in tiny text on the top right of the Galaxy Note 4 splash screen, then boots to the blue android face and then powers off after about 2 seconds. After that, I cant even recovery boot the phone until I remove and reinstall the battery. Then the same thing happens, boot to blue android face and then shut down. I'll try some more android zips I found but I think there is a deeper problem with the phone here.
ekuest said:
Do I just go to install in TWRP and then select the zip file on my microSD card? I tried that with N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip and if says "Could not find 'META-INF/com/google/android/update-binary' in the zip file. Error installing zip file '/external_sd/N910PVPU3BOF5_N910PSPT3BOF5_SPR.zip'" Then I tried with a CM called cm-12.1-20161016-NIGHTLY-trltespr.zip and it seemed to work, and showed a little blue android face but then it still wouldnt boot. Now when I try to start the phone it says "KERNEL IS NOT SEANDROID ENFORCING Set Warranty Bit: Kernel" in tiny text on the top right of the Galaxy Note 4 splash screen, then boots to the blue android face and then powers off after about 2 seconds. After that, I cant even recovery boot the phone until I remove and reinstall the battery. Then the same thing happens, boot to blue android face and then shut down. I'll try some more android zips I found but I think there is a deeper problem with the phone here.
Click to expand...
Click to collapse
Which android version you ware running last time before this issues start happning ? 5.1.1 or 6.0.1 ?
And i think you are trying to flash firmware file from twrp thats not possible you will require a custom rom.
If you are on 5.1.1 then try any lojjipop n910p based roms like cm 12
If you are on 6.0.1 then try n910p marshmallow based rom like cm13
Trex888 said:
Which android version you ware running last time before this issues start happning ? 5.1.1 or 6.0.1 ?
And i think you are trying to flash firmware file from twrp thats not possible you will require a custom rom.
If you are on 5.1.1 then try any lojjipop n910p based roms like cm 12
If you are on 6.0.1 then try n910p marshmallow based rom like cm13
Click to expand...
Click to collapse
I always run the updates so I'm pretty sure I was on 6.0.1. I tried again with CM13 with and without GApps and same thing always happens. No matter what I do, the phone always hangs and shuts off when it gets to the CM splash screen. I will upload a video soon. Do you know why the phone says that SEANDROID thing?
I am using CM13 from here: https://www.androidfilehost.com/?w=files&flid=44727
I am using GApps from here: http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico
ekuest said:
I always run the updates so I'm pretty sure I was on 6.0.1. I tried again with CM13 with and without GApps and same thing always happens. No matter what I do, the phone always hangs and shuts off when it gets to the CM splash screen. I will upload a video soon. Do you know why the phone says that SEANDROID thing?
I am using CM13 from here: https://www.androidfilehost.com/?w=files&flid=44727
I am using GApps from here: http://opengapps.org/?download=true&arch=arm&api=6.0&variant=pico
Click to expand...
Click to collapse
Seandroid thing is normal if you are running custom rom. Cuz any custom comes with root and custom kernel so nothing to worry.
Did you tried another battery?
And how long did you wait to phone boot after flashing cm13 ?
Go to sprint note 4 xda forum and try different roms and be patient and wait atleast 20min to phone boot
You cannot flash cm13 without gapps and make sure gapps is for 6.0.1 marshmallow.
Once your phone boot normal go to download mode and flash 6.0.1 firmware in odin and after finish flash immediately go to stock recovery and do factory reset your phone will be normal.
Make sure your battery is not damaged maybe it is causing shut off. Issue.
Well since I can't flash CM13 with TWRP and I can't flash a stock rom with Odin, what other options do I have? Is there any way to get a bcakup file that someone else has made on their Note 4 in TWRP and try restoring from that? I've also read about ADB sideloading and another recovery called CWM or something and I don't know if those will be any different or just more failed flashes. I think the problem is deeper in the phone since it wouldn't boot with the stock rom and now it won't boot with CM13.
EDIT: Just saw your last post. I have 2 batteries, one samsung stock and one aftermarket TechOrbits double capacity. The phone does the same thing with either one so I ruled out the battery a while ago. Think there's any chance theyre both bad and I should order a new one? I don't really want to invest more money into a dead phone. I don't think I waited that long after installing CM13. I'll try it again and give it a half hour. I doubt that will change anything though.
EDIT2: Also when I go to download mode (says "ODIN MODE <HIGH SPEED>" at the top) it has some red text at the bottom I think might mean something. Does this mean anything to you or is it typical?
UDC START
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
[1]eMMC write fail: ABOOT