Can't get into recovery... - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

Had a Goldeneye ROM installed, wanted to try something different. I'm on MLD baseband. Managed to load a Nexus ROM, but couldn't get wifi to work. Tried Goldfinger ROM, same result. Somewhere along the way, I lost the ability to get into TWRP recovery. I can get to the fallen android recovery menu, but whenever I try to reboot it goes to directly to the ROM (prior to this, if I tried to reboot to TWRP, it would first go to the fallen android, but then selecting reboot got me to TWRP). I have a nandroid backup, but don't know how to try it out without first going to recovery? Alternatively, I could try this method, but don't have a windows box and can't figure out which files I need to flash using heimdall. Thanks for the help...

Do not flash the link on your device. You can get the stock mdl firmware at sammobile.com. Flashing what you linked to will put the mk2 firmware on your device and you'll no longer be able to use twrp. Sorry I can't help you on heimdall though, I've never used it.
Sent from my Nexus 5 using XDA Free mobile app

Have you tried reflashing twrp? I would install flashify from playstore and go from there.

Airtioteclint said:
Have you tried reflashing twrp? I would install flashify from playstore and go from there.
Click to expand...
Click to collapse
OK, well, I managed to get back into recovery. Installed towelroot, then just reinstalled the safestrap recovery apk. Was able to restore my backup, and all was well. Tried reinstalling goldfinger, and wifi was gone again, as was my recovery (again). Weird.

nola mike said:
OK, well, I managed to get back into recovery. Installed towelroot, then just reinstalled the safestrap recovery apk. Was able to restore my backup, and all was well. Tried reinstalling goldfinger, and wifi was gone again, as was my recovery (again). Weird.
Click to expand...
Click to collapse
Meh, forgot to RTFM when installing the ROM. Needed to flash the ATT modules. In my defense, that info was buried pretty deep in the FM

nola mike said:
Meh, forgot to RTFM when installing the ROM. Needed to flash the ATT modules. In my defense, that info was buried pretty deep in the FM
Click to expand...
Click to collapse
Sigh. I just need to quit while I'm ahead. After messing with some xposed modules, I eventually became unable to boot into recovery again, and am stuck at the bootloader screen. I think I need to reinstall firmware via odin (but I have no windows PC, so I'm going to try heimdall).
Is this method the correct one?
I have this file as my firmware: I337UCUAMDL_I337ATTAMDL_ATT.zip

nola mike said:
Sigh. I just need to quit while I'm ahead. After messing with some xposed modules, I eventually became unable to boot into recovery again, and am stuck at the bootloader screen. I think I need to reinstall firmware via odin (but I have no windows PC, so I'm going to try heimdall).
Is this method the correct one?
I have this file as my firmware: I337UCUAMDL_I337ATTAMDL_ATT.zip
Click to expand...
Click to collapse
...And, we're back in business! Multiple problems, one of which was the wrong firmware version--the above is MDL, not MLD
I flashed back to stock MK2 firmware, then upgraded using towelroot and safestrap.
Had a bunch of problems trying to figure out Heimdall, and couldn't figure out what was going wrong (turned out to be the USB cable--I saw posts about this, and went through FIVE cables before I could find one that worked. It was a kindle cable, FWIW).
Tried ODIN in the meantime using my wife's old XP box. What a PITA. Had all kinds of issues trying to get kies to install. Anyway, I'll write up exactly what worked for me. A lot of the info I used was fragmented, old, and contradictory.
EDIT: Re-borked, and tried upgrading again, and ended up with the same errors using the new cable. Then used a different computer, and didn't have any trouble with multiple flashes. I think my USB controller is touchy on the original computer...

Related

[Solved]Need help after formatting internal storage! Soft Brick

I truly need the community's help on this one. Trying to fix a rom that I was using, I decided to wipe everything to reflash it. However, some how I read the thread wrong. Using TWRP, I formatted the "internal storage" thinking that was going to fix my Rom problems.
Now, I can't boot into the Rom or any rom, unless I wipe everything and restore one of my back ups. I restored a back up and it booted, but my data is jacked and phone service is not operable. I thought maybe a reboot will fix it, and now my phone is stuck at "Samsung Galaxy S 4". It doesn't move from there.
What should I do? How do I get it it continue the boot into the rom after a regular reboot? How do I get my radio back?
It's funny to me because I usually never get this careless with my phone. So I can laugh about it but damn I have to figure this one out!
Please help!!!!!!!!!!!!!!!!!
I am by know means an expert but I think you may have to start here with the firmware files then try and flash your backup http://forum.xda-developers.com/showthread.php?t=2338919
Sent from my SPH-L720 using Tapatalk 4
Thanks Chief, let me try that!
Thanks Chief. Unfortunately, that didn't work. I used Odin to flash the Firmware files and let it reboot. I'm still stuck at the Samsung Gal...boot screen. Let me try manually going into recovery and restoring.
Any other ideas? Anyone?
Kenjari said:
Thanks Chief. Unfortunately, that didn't work. I used Odin to flash the Firmware files and let it reboot. I'm still stuck at the Samsung Gal...boot screen. Let me try manually going into recovery and restoring.
Any other ideas? Anyone?
Click to expand...
Click to collapse
Have you tried flashing the complete odin ROM? You can find the all in one somewhere on the dev thread, it has rom, kernel, firmware and the rom all in one as it came from samsung. That should take care of your problem. It will wipe everything, or I think there was also a thread somewhere with odin flashables that didn't wipe data or internal sd but I can't seem to find it right now.
ifly4vamerica said:
Have you tried flashing the complete odin ROM? You can find the all in one somewhere on the dev thread, it has rom, kernel, firmware and the rom all in one as it came from samsung. That should take care of your problem. It will wipe everything, or I think there was also a thread somewhere with odin flashables that didn't wipe data or internal sd but I can't seem to find it right now.
Click to expand...
Click to collapse
Exactly. I'm on the target. I'm currently waiting for this tar that will unroot the phone. It is MDL but I will update and reroot. I hope this does the ticket. I'm going to use Odin to flash it or unroot.
Well strike two. That didn't work either. I downloaded a unrooted MDL tar and connected to Odin. When through the entire process and it rebooted. It still is stuck at "Samsung Galaxy S4".
I read on the Nexus 7 that I might have to reflash a system.img and boot.img? Someone else had a similar experience on the N7 and had to download it via flashdrive and then install via recovery. I'm not saying that's the case but I wonder if I need to reflash a boot.img or something.
Please help. Not sure where to go at this point. Unrooting didn't help.
Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's
Progress made.
leaderbuilder said:
Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's
Click to expand...
Click to collapse
leader, chief, ifly4,...I'm making progress.
leader, actually I flashed a previous version, the MDL via Odin. At first it didn't boot as stated in my previous post. I decided to wipe and factory reset. """"Bingo"""" it booted. Now I'm on MDL and unrooted. However, I transferred my phone over to a previous device so I can't update profile and prl. I'm going to activate the phone and see if it works. For some reason I can't can't seem to get a radio signal on it. It shows the be O with the slash in the middle. This is what it looked like before I deactivated it and lost everything before.
I post back with results. Not quite solved yet.
Thanks leader and everyone else.
Sound like your on the wrong firmware/baseband. what does your modem/baseband say?
Yeeessssss
leaderbuilder said:
Sound like your on the wrong firmware/baseband. what does your modem/baseband say?
Click to expand...
Click to collapse
It says L720VPUAMDL. I actually got it going. I had to change it from WCDMA to CDMA and reset. Now I'm unrooted. and going. However, leader, is there away to update the modem/baseband before I root? Or should I root then flash the MF9 Modem?
if you got MDL to activate you can jst take the OTA update to MF9. It will update it all.
Then use CF-Autoroot to gain root. After that same - install goomanager from Playstore and use it to install TWRP.
leaderbuilder said:
if you got MDL to activate you can jst take the OTA update to MF9. It will update it all.
Then use CF-Autoroot to gain root. After that same - install goomanager from Playstore and use it to install TWRP.
Click to expand...
Click to collapse
Awesome. Hey thanks again leader for helping me out. I'm usually never careless with these things. I use SACS rom but decided to try Miui. From some reason every time I flash Miui, I get the "Roaming Indicator Off" thing along with two signals. Reading the thread it suggest to format the internal. Why oh Why did I try that step. The rest is history....
Thanks again. Learned a lot with this process.
Glad you got it working.
There is a 'thanks' button too.
leaderbuilder said:
Glad you got it working.
There is a 'thanks' button too.
Click to expand...
Click to collapse
No doubt. I got to remember that!
Sent from my SPH-L720 using Tapatalk 4
Glad to hear you got it going.
Sent from my SPH-L720 using Tapatalk 4
leaderbuilder said:
Try downloading this file extract the tar and flash that in PC Odin. (don't check repartion!).
That is the full stock MF9 firmware, boot, recovery, kernel and ROM.
Then maybe use CF Autoroot, then goomanger to get twrp and flash one of your nand's
Click to expand...
Click to collapse
Thank you!

[RESOLVED]Recovery help

RESOLVED:
- Flashed a stock firmwire image from Sammobile using Odin. (AMDL)
- Did a factory reset in the stock recovery TWICE to get it to finally boot.
- Rooted with motochopper
- Installed TWRP
- Back to Task650.
Okay, so I'm a bit stuck. I was running the newest Task650 rom and KT's 9/17 kernel.
I updated to the 10/20 kernel as soon as it was released and it bugged my phone. Blew up everything, glitched my DPI and colors. It was unusable, however the weirdest part is that my custom recovery was removed so I can't seem to flash the old kernel to get my device back to normal.
I tried using odin but it just keeps failing, so I really am unsure what to do now. If I could get the previous kernel back onto it, it would be fine.
Any help? I can't seem to find a .tar.md5 file for TWRP or clockworkmod to flash a new recovery in Odin. I tried Philz .tar.md5 files but it fails as well.
Click to expand...
Click to collapse
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
jball said:
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I cannot use the Google Playstore.. my entire screen is over scaled and impossible to navigate.
So no use of DPI settings.can you use ADB or terminal emulator
Sent from my SAMSUNG-SGH-I337 using xda premium
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
xBeerdroiDx said:
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Click to expand...
Click to collapse
I managed to get the latest stock firmwire (AMDL 4.2.2) off of Sammobile. I did successfully flash the stock .tar.md5 image through Odin, using the PDA slot. Phone seemed to restart and boot right up, but now gets stuck at the AT&T logo. It makes the boot sound and than BAM; frozen.
Now I am truly stuck. Seems flashing the stock image didn't work.. unless I did it wrong through Odin but I doubt it. These are the steps I took,
- Start Odin
- Connect phone in downloaded mode
- Click PDA (select the I337UCUAMDL_I337ATTAMDL_ATT.tar.md5 file)
- Wait for it to confirm the firm, than hit start.
- After waiting about 5 minutes it's successful.
Am I doing ANYTHING wrong?
Te3k said:
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
jd1639 said:
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
Click to expand...
Click to collapse
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Br4nd3n said:
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Click to expand...
Click to collapse
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
jd1639 said:
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
Click to expand...
Click to collapse
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Good deal
Sent from my GT-I9505 using xda premium
Br4nd3n said:
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Click to expand...
Click to collapse
:good:

I need help with installing the Alliance ROM PLEASE.

EDIT: I have successfully installed the Alliance ROM. Here's how i did it.
Prerequisites:
Your phone at at least 50% battery
A charge cable
MicroSD card that you can plug into your computer
Odin 3.09
SafeStrap, version 3.75 APK on your MicroSD card
Alliance ROM on your MicroSD card
NCG tar.md5 (the big file, not the kernel)
I started off on a rooted 5.0 VZW Galaxy S5. After some confusion, I downgraded to NCG (4.4.2) using Odin. After doing that, I went to Towelroot, got the APK, rooted, downloaded SuperSU from the play store (I had to sign into google at this point), installed it's binaries (NORMALLY! Don't choose the TWRP method), rebooted when it asked me to. From there, I installed BusyBox from the play store and installed it within the app. Then I installed Safestrap (version 3.75), which I had on my MicroSD card. I used the app My Files to navigate to my MicroSD and installed the APK. Then I installed it within the app, and when the "reboot to recovery" button worked, I rebooted into SafeStrap recovery mode. At this point, the Alliance ROM zip file should ALREADY BE ON YOUR MICROSD CARD, WHICH SHOULD BE IN YOUR PHONE. Now, you're going to press the INSTALL button to the top right in Safestrap recovery, and you're going to navigate to your MicroSD card. It might be already opened to that. Then you're gonna select the Alliance ROM and flash it. After it successfully flashes, reboot into download mode (if for some reason you aren't able to do it immediately, you get into download mode by holding volume down, home button, and power button at the same time). Now, using Odin, you're gonna flash the firmware that the instructions in the Alliance thread tells you to (here's the thread: http://forum.xda-developers.com/ver.../rom-alliancerom-build-3-rom-control-t2818632). If everything works, it's gonna take a couple of minutes, optimize apps, and boot.
Huge thanks to Beans and his team for creating the Alliance mod, and huge thanks to Tulsadiver for helping me get through the process during my confusion.
Original thread below
Hi. I'll cut to the chase. I was an idiot and thought I could just flash the Alliance ROM from my SD card, but my phone is currently a factory restored 5.0. So, after unsuccessfully flashing Alliance ROM, I thought, well, I probably need to be on 4.4.2 to do this. So, what I'm wondering is, do I need to go back down to 4.4.2 to install Alliance ROM? And do I need Safestrap recovery to do it, or can I do it from stock recovery (home button+volUp+Power)? I did a lot of digging in the Alliance ROM post and there were no posts regarding my problem/question, probably because they're all experienced and I'm not (this is my first time trying to flash a custom ROM).
It SOUNDS like I need to flash a full stock tar using Odin, is that correct? Once I do that, I would be on stock wiped 4.4.2, I assume. From there, could I flash the Alliance ROM and continue with the instructions? Or do I need to root first and get safestrap and all that crap? I feel like Beans was really vague with his instructions on installing ROMs, but whatever. Please help though, I'm kind of stuck in the middle of this with a softbricked phone.
Thank you so much in advance, I appreciate it.
~isra
EDIT: Also, I was on ROOTED 5.0 Lollipop just before this. I just got so sick of lollipop, I was ready for something different. So here we are. To confirm, my phone is the standard retail SM-G900VZW model.
EDIT2: Apparently App Ops and SuperSU survived the wipe and, after downloading Root Checker, I can confirm that I'm still rooted... Huh.
israphial said:
Hi. I'll cut to the chase. I was an idiot and thought I could just flash the Alliance ROM from my SD card, but my phone is currently a factory restored 5.0. So, after unsuccessfully flashing Alliance ROM, I thought, well, I probably need to be on 4.4.2 to do this. So, what I'm wondering is, do I need to go back down to 4.4.2 to install Alliance ROM? And do I need Safestrap recovery to do it, or can I do it from stock recovery (home button+volUp+Power)? I did a lot of digging in the Alliance ROM post and there were no posts regarding my problem/question, probably because they're all experienced and I'm not (this is my first time trying to flash a custom ROM).
It SOUNDS like I need to flash a full stock tar using Odin, is that correct? Once I do that, I would be on stock wiped 4.4.2, I assume. From there, could I flash the Alliance ROM and continue with the instructions? Or do I need to root first and get safestrap and all that crap? I feel like Beans was really vague with his instructions on installing ROMs, but whatever. Please help though, I'm kind of stuck in the middle of this with a softbricked phone.
Thank you so much in advance, I appreciate it.
~isra
EDIT: Also, I was on ROOTED 5.0 Lollipop just before this. I just got so sick of lollipop, I was ready for something different. So here we are. To confirm, my phone is the standard retail SM-G900VZW model.
EDIT2: Apparently App Ops and SuperSU survived the wipe and, after downloading Root Checker, I can confirm that I'm still rooted... Huh.
Click to expand...
Click to collapse
Download busybox from play store. Install it. Install safestrap. Once recovery is installed, go into recovery, install alliance, from within safestrap, boot into download mode and flash the full firmware Odin tar.
Tulsadiver said:
Download busybox from play store. Install it. Install safestrap. Once recovery is installed, go into recovery, install alliance, from within safestrap, boot into download mode and flash the full firmware Odin tar.
Click to expand...
Click to collapse
Wait, so I don't need to downgrade my phone? Keep in mind I'm on stock rooted 5.0, which just got factory reset so I got nothing except for the root. Also, what full firmware odin tar are you referring to? NE9? This one: https://www.androidfilehost.com/?fid=23610159112652201
Or this one: https://www.androidfilehost.com/?fid=23622183712472727
I'm getting these links from here: http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
I really appreciate you replying. Thank you.
The first one. That firmware will downgrade you to NE9.
Tulsadiver said:
The first one. That firmware will downgrade you to NE9.
Click to expand...
Click to collapse
Ok, so I don't need to downgrade to install the ROM. Got it. Thank you. Is there anything else I should know?
Not that I know of. ROM installations are different so always refer to their installation instructions. Some will say to flash the firmware first. The op knows best. Alliance NE9 says to do a full wipe (everything but SD card). Install the ROM, reboot to download mode ( don't hit reboot system). Once in download mode, flash the firmware tar and let your phone reboot.
Tulsadiver said:
Not that I know of. ROM installations are different so always refer to their installation instructions. Some will say to flash the firmware first. The op knows best. Alliance NE9 says to do a full wipe (everything but SD card). Install the ROM, reboot to download mode ( don't hit reboot system). Once in download mode, flash the firmware tar and let your phone reboot.
Click to expand...
Click to collapse
So, I installed Safestrap and did all that, but when I press the reboot into recovery button, it just reboots the phone normally. It doesn't go into safestrap recovery. Am I supposed to hold some buttons or something?
Did safestrap ask for SuperSU permissions? Did you install busy box? You can't just download the app.
Tulsadiver said:
Did safestrap ask for SuperSU permissions? Did you install busy box? You can't just download the app.
Click to expand...
Click to collapse
Yes, I've installed BusyBox and given SS root permissions. I installed the APK 3.75 Safestrap that I used to get into SS recovery when I was getting to rooted 5.0 a while back, so I know that the APK isn't corrupt or anything like that.
I forgot. You are on lollipop. You need to flash the NE9 kernel first ( via Odin). You already have safestrap but it doesn't work on lollipop. After you flash the NE9 kernel you will have the option to boot into recovery. Have alliance on your SD card ready to install.
Tulsadiver said:
I forgot. You are on lollipop. You need to flash the NE9 kernel first ( via Odin). You already have safestrap but it doesn't work on lollipop. After you flash the NE9 kernel you will have the option to boot into recovery. Have alliance on your SD card ready to install.
Click to expand...
Click to collapse
Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275
Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275
israphial said:
Found a "NE9 Stock tar.md5". Does that sound right? DL is here: https://www.androidfilehost.com/?fid=23578570567721275
Click to expand...
Click to collapse
That is it.
Tulsadiver said:
That is it.
Click to expand...
Click to collapse
Thank you. I'm going to flash the kernel then, then I'll get back to you if anything comes up. Again, I really appreciate you helping me. Thank you.
Tulsadiver said:
That is it.
Click to expand...
Click to collapse
It booted into stock recovery mode after odin successfully flashed NE9. Now do I install the ROM from stock recovery, or do I boot the phone and get to Safestrap to install the ROM from Safestrap recovery? I am currently in recovery mode.
You must not have had safestrap on your phone after all. Can you get back to download mode? You probably need to flash your lollipop kernel to get back to lollipop.
Tulsadiver said:
You must not have had safestrap on your phone after all. Can you get back to download mode? You probably need to flash your lollipop kernel to get back to lollipop.
Click to expand...
Click to collapse
I definitely had safestrap. Though, here's something: Everyone talks about a menu that pops up during boot that allows you to enter either safestrap recovery, or boot, and I've never had/seen that menu, even when I was rooting 5.0. Yes, my BusyBox worked and was properly installed, and yes, I had Safestrap recovery installed.
I just tried rebooting and it after sitting at the first screen for a while, it rebooted quickly and went back into recovery mode. What if I try installing Alliance from recovery mode? Will it work?
israphial said:
I definitely had safestrap. Though, here's something: Everyone talks about a menu that pops up during boot that allows you to enter either safestrap recovery, or boot, and I've never had/seen that menu, even when I was rooting 5.0. Yes, my BusyBox worked and was properly installed, and yes, I had Safestrap recovery installed.
I just tried rebooting and it after sitting at the first screen for a while, it rebooted quickly and went back into recovery mode. What if I try installing Alliance from recovery mode? Will it work?
Click to expand...
Click to collapse
I've never been on stock recovery before. I think it has to be a custom recovery. You might need to pull your battery and let it set for a bit and see if you can get into download mode.
Tulsadiver said:
I've never been on stock recovery before. I think it has to be a custom recovery. You might need to pull your battery and let it set for a bit and see if you can get into download mode.
Click to expand...
Click to collapse
I can get into download mode perfectly fine. I'm going to kernel back to 5.0 then...
But what do I do now? Should I downgrade to 4.4.2 with the stock firmware once I successfully boot 5.0?
EDIT: Yup, booted 5.0 perfectly fine. Now what? Downgrade to 4.4.2 and flash the NE9 Kernel?
Proof that Safestrap is on my phone:
http://imgur.com/cGa1v1n

[Q] I don't get it

I had to Odin and went back to ncg. I have searched and posted in relevant forums and no answers that work. I am rooted have safestrap and I have flashfire. I would like to go up to the new MOAR rom. For some reason when I try to flash anything with safestrap it fails everytime, just shows updating partitions and then a red failed.
When I try with flashfire I can not see zips on my SD or internal. Everyone says it should work fine. It doesnt. I did repatriation with pit when going to ncg. I try flashing the stock rooted OA8 and it fails. Any help is super appreciated. I did not have trouble when I first got the phone and rooted but I started at OA8 and went to ncg.
Is there no solution?
jhr5474 said:
Is there no solution?
Click to expand...
Click to collapse
Odin back to NCG but using the full wipe tar file found here. Then root again with towelroot. Download supersu from playstore. Update binaries and reboot. Install busybody from playstore and install. Install safestrap. You should be good to go.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
Tulsadiver said:
Odin back to NCG but using the full wipe tar file found here. Then root again with towelroot. Download supersu from playstore. Update binaries and reboot. Install busybody from playstore and install. Install safestrap. You should be good to go.
http://forum.xda-developers.com/ver...ment/stock-collection-kernels-modems-t2842069
Click to expand...
Click to collapse
I have done this 3 times now thinking that I had a bad flash or something. Still I am not able to flash any roms with safestrap. I get failed EVERYTIME! This is with multiple downloads so I know they are not bad downloads. I have also tried using flashfire. I am wondering if I should odin and flash up then back to ncg since the newer ones repartition differently?
jhr5474 said:
I have done this 3 times now thinking that I had a bad flash or something. Still I am not able to flash any roms with safestrap. I get failed EVERYTIME! This is with multiple downloads so I know they are not bad downloads. I have also tried using flashfire. I am wondering if I should odin and flash up then back to ncg since the newer ones repartition differently?
Click to expand...
Click to collapse
it sure can't hurt.
jhr5474 said:
I have done this 3 times now thinking that I had a bad flash or something. Still I am not able to flash any roms with safestrap. I get failed EVERYTIME! This is with multiple downloads so I know they are not bad downloads. I have also tried using flashfire. I am wondering if I should odin and flash up then back to ncg since the newer ones repartition differently?
Click to expand...
Click to collapse
Seems like that pit file messed things up. I've always stayed away from it. I'm guessing you used it with Beantowns full NGC tar. Maybe you should try it again. You could use Misterxtcs this time. Other than that you could try connecting a thumb drive directly to your phone and see if Flashfire can see zips on it. Won't fix anything but it might get you on Moar. I know you've tried a lot of times and this is getting old. I've also heard of people trying different versions of Odin in trying to find one that works for their specific problem.
You could also try connecting to kies to see if their emergency recovery might help.
Edit: everything I read says to leave that pit file alone unless you are bricked. Your idea of flashing a firmware from higher up sounds like a good plan. Maybe OC4.
SOLVED! I bought a crappy SD from geek.Com 128gb put a 4 gb in and I was able to see zips and flash fine with flashfire.
Running themed MOAR and loving it. Thanks guys.

Bricked note 4 with CF- Auto-Root, can i revive it?

Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Blu3sman said:
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Click to expand...
Click to collapse
Instead of flashing any firmware , try to flash the correct cf auto root file.
Reporting Via N910G
Blu3sman said:
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Click to expand...
Click to collapse
Download firmware from sammobiles. com
http://www.sammobile.com/firmwares/database/SM-N910H/
yashthemw said:
Instead of flashing any firmware , try to flash the correct cf auto root file.
Reporting Via N910G
Click to expand...
Click to collapse
Ok well i tried that and that didn't work. However after double checking its seems that i had the correct file in the first place. So what went wrong?
One thing i need to ask. Does your phone NEED to be unlocked in order to root it?
Trex i went to Sammobiles and what my problem is there is WHICH country firmware to i d/l??? there are so many!!! Should any one of them do the trick?
Blu3sman said:
Ok well i tried that and that didn't work. However after double checking its seems that i had the correct file in the first place. So what went wrong?
One thing i need to ask. Does your phone NEED to be unlocked in order to root it?
Trex i went to Sammobiles and what my problem is there is WHICH country firmware to i d/l??? there are so many!!! Should any one of them do the trick?
Click to expand...
Click to collapse
try flashing a custom recovery specific for your phone model and from within flash superSU.
its_me_Sandy said:
try flashing a custom recovery specific for your phone model and from within flash superSU.
Click to expand...
Click to collapse
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Blu3sman said:
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Click to expand...
Click to collapse
This is the current supersu 2.78-sr1. It's systemless root for all samsung marshmallow firmware.
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
1 Download to phone.
2 Boot into recovery.
3 Click install, and find zip that you downloaded.
4. Reboot, All done
Phone will boot loop once. That is normal.
P.S. If this is first time you installed Twrp, I would make a full backup and save it some where.
:good: if that helped.
aaron74 said:
This is the current supersu 2.78-sr1. It's systemless root for all samsung marshmallow firmware.
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
1 Download to phone.
2 Boot into recovery.
3 Click install, and find zip that you downloaded.
4. Reboot, All done
Phone will boot loop once. That is normal.
P.S. If this is first time you installed Twrp, I would make a full backup and save it some where.
:good: if that helped.
Click to expand...
Click to collapse
Well Aaron thats my problem, i can't download it to my phone. The one constant through all this is that i can't turn my phone on as such.
My pc doesn't even recognize it, in fact the only thing that does is Odin, not Kies, not ADB, nothing lol.
I can get the phone into the custom recovery i have flashed (TWRP) and get into "download" mode, but thats it. So where do we go from here?
Ok i have an update on this. PC now sees the phone but only as a modem.
Blu3sman said:
Well Aaron thats my problem, i can't download it to my phone. The one constant through all this is that i can't turn my phone on as such.
My pc doesn't even recognize it, in fact the only thing that does is Odin, not Kies, not ADB, nothing lol.
I can get the phone into the custom recovery i have flashed (TWRP) and get into "download" mode, but thats it. So where do we go from here?
Ok i have an update on this. PC now sees the phone but only as a modem.
Click to expand...
Click to collapse
Oh, I misunderstood.
If that's the case. If you can goto download mode, download stock firmware, then flash with Odin.
To get your csc, since you can go in twrp. Use twrp file explorer. copy the file in /efs/imei folder. Thinks it's called mps_code. Copy to ext sd. Now that file should have your csc region code written in it. Read file in pc. That should be firmware you want to download.
See if that helps.
Blu3sman said:
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Click to expand...
Click to collapse
Find the correct version of superSU from the above post..put it in a pen drive or in the memory card via card reader.
Flash it via OTG cable or put back the card n flash
ALRIGHT!!!! Ok guys just a heads up. As you can probably guess my phone is WORKING!!!....so far. Was able to do as you suggested and found the txt file, Using TWRP file browser ,that told me what ver firmware i have, inserted an sd card i had in my Tab S, copied file to that, read in my pc card reader, downloaded and installed said firmware and BADA BING BADA BOOM, all good!! I still am unsure on how this happened. I've rooted 3 HTC phones and my Galalxy Tab S successfully, so it's not like i didn't know what i was doing, 1 question that hasn't been answered though is, must the phone be network unlocked in order to root it? Because thats the one thing i didn't do that i did on the others. Want to thank all you guys for all your help. This was doing my head in and without your direction i probably would not have been able to do this.
Many Thanks.
PS: any one suggest a good rooting method for this phone??? lol
hi. i have the exact problem. can you please help,, i dont have twrp or supersu. [email protected] please if anyone can help

Categories

Resources