n900t TWRP installed, now no recovery and bootloop - Galaxy Note 3 Q&A, Help & Troubleshooting

so i bought this N3 about a month ago, so it was on 4.4.2 from the factory. first thing i did was root it to get rid of the bloat. fast forward to now. nova launcher is getting boring and i want to try a new rom. first thing i did was try to install twrp. im using the latest file from twrp and odin 3.09, and everything went fine. tried to boot into recovery and it boot looped with the "seandroid enforcing" loading screen. even pulling the battery did nothing. i had to put it in download mode and cancel out for it to boot back up normally. now my problem is i have NO recovery and thats not sitting well with me. i also do not want philz recovery, so im not gonna even bother to try flashing that until i have no choice.

dirtyjerzz said:
so i bought this N3 about a month ago, so it was on 4.4.2 from the factory. first thing i did was root it to get rid of the bloat. fast forward to now. nova launcher is getting boring and i want to try a new rom. first thing i did was try to install twrp. im using the latest file from twrp and odin 3.09, and everything went fine. tried to boot into recovery and it boot looped with the "seandroid enforcing" loading screen. even pulling the battery did nothing. i had to put it in download mode and cancel out for it to boot back up normally. now my problem is i have NO recovery and thats not sitting well with me. i also do not want philz recovery, so im not gonna even bother to try flashing that until i have no choice.
Click to expand...
Click to collapse
i'm facing same issue here
i can't enter download or recovery mode

dirtyjerzz: Flash a stock ROM via Odin after that -> flash CWM -> Philz -> TWRP
mohd.itcs: Buy or make a USB JIG

Related

From CynogenMod to WanamLite - Help me get there!

Hi,
I'm currently running CyanogenMod KitKat version with ClockWorkMod. Since the rom has several bugs and for the past few months they haven't published any updates to my Galaxy s4 I9505, I've decided to switch to WanamLite.
There I found out I need TWRP recovery so I went ahead and downloaded GooManager which installed an outdated version, as I've found out.
I tried wiping my internal storage as recommended but the recovery couldn't mount any of my partitions.
So now CyanogenMod won't boot. I know this issue is fixed in the updated version of TWRP but I'm not sure how to update it without the phone booting (Odin perhaps? It doesn't recognize it currently... Should I move to download mode for it to be detected?)
Anyways, I'm kind of stuck as of now. Any help would be very much appreciated!
Btw I have a question, what's the difference between using Odin 1.85 and 3.09? Why do people still use the old version?
Thanks in advance!!
Neta
Edit:
Alright, now I can't get into recovery either. When I try, I can see the Samsung logo and there's "recovery" written in the top left but then it just restarts again into the same logo without "recovery". I'm starting to lose my cool now. Anyone have any ideas?
Try flashing latest stock through download mode and see if it boots.
Sent from my GT-I9506 using Tapatalk
Flash this recovery through odin. It's TWRP 2.6.3.1. Worked alwys for me.:fingers-crossed:
https://db.tt/SwLvOrZl
Uncheck auto-reboot in Odin.
Thank guys
I got freaked out and just did everything I could to make the phone working again.
I found a thread on XDA explaining how to return your phone to stock version, so I followed it, rooted with auto root, (btw Odin didn't recognize my phone because I used the front usb... how annoying!), then flashed the latest TWRP (2.7.0.1, not 2.6.x.x as GooManager downloaded for me), then booted to recovery and flashed WanamLite.
Everything is working now!
Except one thing - I'm still not able to access recovery mode through physical buttons, only using boot apps. Is this a kernel issue?
Could be some incompatibility since CyanogenMod uses it's own kernel and CWM recovery.
The recovery itself is working fine, but when I try to access it using buttons it shows the Samsung logo with the recovery on the top left, and then reboots again to normal boot.
What do you think?
Thanks!

Phone stuck on Samsung logo after failed ROM flash

Hello everyone, I wanted to flash a ROM to my Galaxy S4 i9505. I first rooted it like described in this tutorial. That went all ok.
After that I downloaded this and tried to flash using Odin Mobile. It rebooted to some sort of recovery, wiped data, cache etc. and then it wrote some error.
After that, I am stuck at the Samsung logo and can't boot into android. I can't also enter recovery, when i hold the buttons, it boots and there is written BOOTING RECOVERY (in the left top corner) but after that it goes to the Samsung logo again.
I can still get into Download mode. If anyone could help with this I would be really grateful.
davidv1 said:
Hello everyone, I wanted to flash a ROM to my Galaxy S4 i9505. I first rooted it like described in this tutorial. That went all ok.
After that I downloaded this and tried to flash using Odin Mobile. It rebooted to some sort of recovery, wiped data, cache etc. and then it wrote some error.
After that, I am stuck at the Samsung logo and can't boot into android. I can't also enter recovery, when i hold the buttons, it boots and there is written BOOTING RECOVERY (in the left top corner) but after that it goes to the Samsung logo again.
I can still get into Download mode. If anyone could help with this I would be really grateful.
Click to expand...
Click to collapse
Hi mate,
Why you flashed a custom rom with Odin mobile???
Go into recovery and do a factory reset try to reboot and see if it works if not....
Go to recovery do a factory reset ...and flash rom from there ( did you installed a custom recovery?)
If no working ..go to recovery do a factory reset ...download a stock rom ( sammobile) download Odin ( not odin mobile) flash stock rom...
Then you can root , install custom recovery and flash custom rom from there...
I did try to install the recovery using odin (this one), but when i rebooted there was the default recovery So after that i decided to flash the rom using odin mobile (and that got me here).
Can i install custom recovery with firmware ending with GNG8? I had 4.4.2 stock before this.
davidv1 said:
I did try to install the recovery using odin (this one), but when i rebooted there was the default recovery So after that i decided to flash the rom using odin mobile (and that got me here).
Can i install custom recovery with firmware ending with GNG8? I had 4.4.2 stock before this.
Click to expand...
Click to collapse
Hi
What odin did you use to flash the custom recovery? it should work, you can also try TWRP recovery
http://teamw.in/project/twrp2/182
Do not use odin mobile go with the pc type
You can install a custom rom...but you need a custom recovery
MAX 404 said:
Hi
What odin did you use to flash the custom recovery? it should work, you can also try TWRP recovery
link
Do not use odin mobile go with the pc type
You can install a custom rom...but you need a custom recovery
Click to expand...
Click to collapse
Thanks for the tip, I installed it through Odin 3.09, first I got stuck on booting into recovery, but on the second try I kept holding the volume up only after phone logo appeared and now I am in the TWRP.
Reseting the phone now and I will install the rom after that. Thanks again, hope it will succeed now.
davidv1 said:
Thanks for the tip, I installed it through Odin 3.09, first I got stuck on booting into recovery, but on the second try I kept holding the volume up only after phone logo appeared and now I am in the TWRP.
Reseting the phone now and I will install the rom after that. Thanks again, hope it will succeed now.
Click to expand...
Click to collapse
Great mate!
Let us know how it goes

[Q] ODIN fails while installing TWRP, stuck at boot

I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
Update: I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.

Issues With Bootloop Into Faulty Recovery

Hey there guys,
I was playing around with my phone and I was trying to install a custom recovery. I tried to install CWM but could not find the correct version for my phone online. My phone is a note 3. However I didnt mind this and went ahead with installing a twrp recovery. When i tried to install it I used odin and the AP option. I managed to install it, but there was an error. When i would go into the recovery mode it would only show the two lines of writing as license:recovery. However this was fine as if i didnt go into recovery mode i could still access the phone. Now i installed ROM MANAGER and tried to use that instead of ODIN. However when i pressed open in recovery option the same useless recovery screen with two lines came up. Not even the stock recovery option. Now this is where i Messed up. Now when i turn phone on it boots into recovery which is useless. and then reboots into recovery agian and again. At this point i am unsure what to do. I was hoping to try twrp recovery again but cant as i cant connect to ODIN as i cant open the download screen because it goes straight into the recovery screen. Mega confused at this point and would really appreciate help asap.
Thanks a bunch
Was the phone rooted when rom manager was used?
Did you try downloading the latest stock rom for your phone from sammobile.com and flashing it in Odin?

HELP! Phone stuck in boot cycle, cannot flash rom

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

Categories

Resources