I unfortunately can not provide some sort of logs but I can tell some sort of history.
So I have some rom that I installed ages ago I believe the zipfile says note4our.
Anyways I dropped my phone a couple weeks ago and noticed that my phone was slowly acting up, as in random reboots, and sometimes it would restart into download mode. Sometimes it would just hang at the very first screen that says kernel in the top left. Luckily I was able to go into recovery and clearing caches seemed to sort me out temporarily. Last night the phone randomly rebooted and has not been able to boot up at all. Just constant bzz bzz reboot lol. I am still able to go to recovery mode, however when I plug it into my computer it seems that I can't get any files on or off via a drag and drop, and I also can't use windows to move files between an sdcard mounted in the phone to the internal storage either. Which is weird since it windows can list all of my files but it can't open it either. I do not have read-only checked. When I try to move files windows says something about the device having stopped hence I can't move.
So I'm guessing there's no way for me to recover my files later? Or will my twrp backup of the just the data portion suffice? Any other things I should try before I go full nuclear and do a complete wipe and try a fresh? Normally I would use this situation to update as well but I figured I would do that after my reflash since I'm sure I would need to update my bootloader or something and I'm still trying to potentially salvage my files if I still can.
So yeah it's been over a year or so, and I need my hand held at this point. Please and thank you and I'll do my best to provide anymore information after work tonight.
That locked USB is av ***** ain't it. I've been getting that for the last couple of updates to. It wont stay locked. It just needs enough time to make sure the build stays the same. Pull the battery put put it back in and wait a few minutes. It still unlock again.
Sent from my SM-N910P using Tapatalk
@bryyando
A possible scenario may have been your SuperSU updated to systemless root in Google Play and later you factory reset? That would cause you lose root and fail to boot with existing custom kernel.
If that happened, you could flash the SuperSU zip and it should boot again. Here's an updated version of the original system based SuperSU that the ROM had:
http://forum.xda-developers.com/attachment.php?attachmentid=3969639&d=1481813000
If that doesn't work, you could try to flash the ROM without wiping data. Or you could backup data partition but I think you need to include more than one partition to make it valid (but that may only pertain to titanium backup; I'm not sure). Since recovery is working, you could include that partition.
If it comes to trying to the nuclear option, I'd recommend flashing the linked SuperSU after restoring TWRP backup of data.
Maybe one of those options works but I suspect your issue is loss of root. It's a must have with custom kernel. Otherwise, no boot.
If you do boot and recover without losing data, make a backup. Valuable time saver to have a current backup.
Sent from my SM-N910P using Tapatalk
@samep
So I totally remembered about dirty flashing while at work and proceeded to do that when I got home, before I read this thread. The phone appears to marginally do better as it is rebooting after it at least optimizes some apps... Also I for reference my ROM version is 1.1 and twrp is 2.8.7.0 lol
And just my luck my spare note 2 seems to have an emmc failure...
@samep
Managed to do a twrp backup of my data partition. Oddly enough my phone rebooted the first time, but made it the second time. For the hell of it I cleared just the caches and then did a bootup. Each time it had less apps to optimize and eventually I made it past the lockscreen, my phone alerted me to my missed messages and then would do a bootloop again. I did notice that the screen had weird pink lines on the bottom right before it vibrated and restarted. Still can't save files onto computer while connected in recovery mode. I luckily found an sdcard that should have enough memory for me to move my pictures and notes that I'm trying to save. Then I'll do an advanced wipe this time. Flash my 1.1 rom, then the supersu you provided and see if it works. If that doesn't then I'll odin up to PE1? Or whatever the new roms need and see if my phone crashes still while on stock and then go from there. Did I miss anything?
bryyando said:
@samep
Managed to do a twrp backup of my data partition. Oddly enough my phone rebooted the first time, but made it the second time. For the hell of it I cleared just the caches and then did a bootup. Each time it had less apps to optimize and eventually I made it past the lockscreen, my phone alerted me to my missed messages and then would do a bootloop again. I did notice that the screen had weird pink lines on the bottom right before it vibrated and restarted. Still can't save files onto computer while connected in recovery mode. I luckily found an sdcard that should have enough memory for me to move my pictures and notes that I'm trying to save. Then I'll do an advanced wipe this time. Flash my 1.1 rom, then the supersu you provided and see if it works. If that doesn't then I'll odin up to PE1? Or whatever the new roms need and see if my phone crashes still while on stock and then go from there. Did I miss anything?
Click to expand...
Click to collapse
Since you mentioned a ROM with Xposed framework, I hadn't considered that Xposed framework may have gotten corrupted causing the reboots. You're on an old ROM. I'd update and not worry with it.
I'd recommend backing up your data that you'd like to keep, wiping internal memory, format data and factory reset, Odin PE2 and clean install freeza's Note 4our beta 3. Kernel and ROM are based on PE2.
The ROM is here but this link points to a known issue you'll need to fix Xposed installer to update or install Xposed modules.
http://forum.xda-developers.com/showthread.php?p=67383249
But if you're not interested in Xposed at all, you may consider another ROM. I'd recommend being on the right update as you're trying to do already. You may not have noticed freeza updated to PE2 if that was your goal.
If you prefer Xposed framework and custom modules, freeza offers a quick and custom way to get there with minimum flashing.
Sent from my SM-N910P using Tapatalk
@samep
I think we might be on the right track with a potentially corrupted xposed. I did notice that some of modules would stop working sometimes. Also what may be potentially interesting is that my phone does reboot when I am in recovery mode. Although xposed probably wouldn't cause that? I do think my phone is more stable in recovery mode as it seems is running for longer periods while I'm in there vs trying to boot up in which I barely make it past the samsung boot animation. I am slowly moving folders over so I have both a twrp data backup as well as the original files, it is just taking a long time as I am not normally at home to do this. On top of that ODIN flash, I noticed that twrp has been updated to 3.0.2.0 I'm guessing I should update that as well. I adb load the img file correct? The tar is just compressed for easier download?
bryyando said:
@samep
I think we might be on the right track with a potentially corrupted xposed. I did notice that some of modules would stop working sometimes. Also what may be potentially interesting is that my phone does reboot when I am in recovery mode. Although xposed probably wouldn't cause that? I do think my phone is more stable in recovery mode as it seems is running for longer periods while I'm in there vs trying to boot up in which I barely make it past the samsung boot animation. I am slowly moving folders over so I have both a twrp data backup as well as the original files, it is just taking a long time as I am not normally at home to do this. On top of that ODIN flash, I noticed that twrp has been updated to 3.0.2.0 I'm guessing I should update that as well. I adb load the img file correct? The tar is just compressed for easier download?
Click to expand...
Click to collapse
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk
I have not tried or was aware of safe mode. I meant that the phone would sometimes reboot while in recovery mode as well.
samep said:
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
samep said:
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I won't say that's terminal. There's been two occasions that I had to flash TWRP again because it was buggy but the phone was otherwise fine after that.
It's possible you have more than one partition corrupted. I wouldn't worry unless you have trouble flashing with Odin.
Hopefully once you're done with Odin and flash the new ROM, you're back to normal.
Sent from my SM-N910P using Tapatalk
Seem to be having problems with ODIN, hangs when I load up the tar for a bit and then when I hit run it says 0 succeed 0 fail. Are there separate drivers I need as well?
bryyando said:
Seem to be having problems with ODIN, hangs when I load up the tar for a bit and then when I hit run it says 0 succeed 0 fail. Are there separate drivers I need as well?
Click to expand...
Click to collapse
You need the Samsung driver. Google Samsung SM-N910P support and you should find it. Like this:
http://www.samsung.com/us/support/owners/product/galaxy-note-4-sprint (scroll down to driver and agree to terms to download)
On your tar, verify the md5 against the zip. If good, extract the tar.md5 from it. When you load that into Odin AP slot, expect about minute delay to verify it. I usually wait before plugging my USB in to download for that reason. You shouldn't try to start the download before it's ready.
When you plug-in in download mode, also verify your phone is added (highlights when added) in the COMM window.
Sent from my SM-N910P using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/a/d1EyB
This is what I got, and same thing. Doesn't really get past the powered by android screen. Maybe sometimes it shows the sprint logo. Guess my phone is dead?
@samep
There was this too.
bryyando said:
@samep
There was this too.
Click to expand...
Click to collapse
So it flashed and booted?
I didn't see the whole Odin log to verify your phone was added as COM. You should see a progress bar lb the phone screen and some warning like writing; do not disconnect.
Sent from my SM-N910P using Tapatalk
Here's what it said about my twrp install, except it never boots up...
Yeah the rom tried to boot but then it would just get into a bootloop again.
bryyando said:
Yeah the rom tried to boot but then it would just get into a bootloop again.
Click to expand...
Click to collapse
Did you factory reset? If not, try that in stock recovery now and reboot.
Sent from my SM-N910P using Tapatalk
Tried it again,
Did a factory reset but still bootloop. Was able to get into recovery mode tho
samep said:
Did you factory reset? If not, try that in stock recovery now and reboot.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
bryyando said:
Tried it again,
Did a factory reset but still bootloop. Was able to get into recovery mode tho
Click to expand...
Click to collapse
You did the wipes I suggested in post #6? I've seen that happen when internal memory isn't wiped for users with CM coming to back to stock. I've seen it happen with nand erase all for some users but you didn't do that, did you?
When that happens for those doing just the nand erase all without tar and PIT with repartition, the Odin flash doesn't take right. Just boot stock recovery, factory reset and wipe cache partitions and power down , pull battery for at least 1 minute and reinstall, boot to download mode and flash stock tar with Odin defaults. Let it auto boot.
Even if you didn't have CM, I'd consider that before proceeding. I'd even flash TWRP and wipe internal memory if that was skipped as a prep in the previous stock tar flash. I'm not sure if stock recovery factory reset is any different than TWRP but it seems to have made a difference for some users that had flash issues with Odin in the past so consider that before wiping with TWRP.
Try stock tar prep and install without PIT or repartition or nand erase all (Odin defaults only). Hopefully that helps to boot. I'd need to know if you already wiped internal memory before suggesting the PIT. There is s thread with links already posted but it's less of a last ditch effort fix but rather more of a diagnosis for hardware failure. Small chance it works so most likely a bad flash or corruption only fix. Most of these failures seem to indicate hardware failure, IMO. Dropping it hard enough could possibly damage hardware or corrupt. I don't know as fact but I'd think either is possible. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk
Related
Hello. First post because I'm usually pretty good at finding solutions to my problems just searching. I can't find the solution to my current issue and I hope you fine folks can give me some advice.
Issue arose while clean flashing my d2att to the most recent Task650 AOKP build using the latest TWRP. Did my nandroid to internal sd like usual, factory reset, and format system. Done this 100 times with no issues. This time, TWRP crashed while formatting system and phone vibrates, reboots, hangs on the new kernel splash screen for Task650s Rom. Pull the battery, replace, then boot recovery with the volume home power method. TWRP splash screen shows, screen goes black, vibrates twice, then reboots back into previously mentioned kernel splash and hangs.
So I can't boot recovery and I can't boot my phone. I enter download mode and try to Odin the most recent twrp tar. Same. I try a previous twrp tar. Same.
I think I can use a rooted stock image to get back up and running, but I don't want to lose the contents of my internal sd.
How can I fix this with minimal data loss? Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Ugh.
AFAIK, you're stuck and will have to Odin back to stock JB just to get running properly again.
Maybe try to Odin stock recovery? I'm pretty sure it's out there somewhere to flash. Then use it to wipe cache/dalvik and then Odin TWRP again. Or try to Odin CWM?
You can use ADB to copy all the files from your phone over to your computer so you don't lose anything. The commands to do this are out there somewhere. I don't know them off the top of my head.
CZ Eddie said:
Ugh.
AFAIK, you're stuck and will have to Odin back to stock JB just to get running properly again.
Maybe try to Odin stock recovery? I'm pretty sure it's out there somewhere to flash. Then use it to wipe cache/dalvik and then Odin TWRP again. Or try to Odin CWM?
You can use ADB to copy all the files from your phone over to your computer so you don't lose anything. The commands to do this are out there somewhere. I don't know them off the top of my head.
Click to expand...
Click to collapse
Thanks for the feedback CZ. I didn't want to mess around with ADB so I just used Odin to flash rooted stock and expected to lose some data. Much to my surprise, once the phone was back up and running, my data was still on the internal SD. So everything is good now and I shall go back to lurking!
GhastlyTT said:
Thanks for the feedback CZ. I didn't want to mess around with ADB so I just used Odin to flash rooted stock and expected to lose some data. Much to my surprise, once the phone was back up and running, my data was still on the internal SD. So everything is good now and I shall go back to lurking!
Click to expand...
Click to collapse
Odin won't delete /data only a factory reset in stock recovery will
Hi, I have been trying to flash a new ROM to my Note II.
It was on Official Stock 4.3 ROM and I flashed succesfully another 4.3 ROM based on stock with some Note 3 features using Philipz Touch.
Then I switch Philipz to TWRP in order to install DN3 V4 ROM and I made the wipes and format /data and I start flashing the ROM, and since that moment It stucks on the first screen.
When I try to flash a stock 4.3 ROM using Odin, It seems to flash correctly, but when I try to boot, it stucks again.
I can enter to recovery and download mode, I can install some ROMS using TWRP but when it finishes it shows "Unable to mount /data" and if I try to boot, It always stucks on fisrt screen.
I hope you can help me.
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Still the same
biokiller said:
Do it again: format cache; davik; systems; data and install rom again. If not, flash cwm recovery via odin.
Good luck.
Sent from my Assistant
Click to expand...
Click to collapse
I really appreciate your help, but I can't fix the problem yet.
With CWM I can't make a factory reset, when I try to make it, it restarts the phone and it stuks on the first screen.
I have flashed stock ROMS with odin and it says PASS but when the phone boots It always stucks on the first screen.
Fear not.
I am fairly confident this will work, but read the whole post first
You tick erase all nand as well as the usual two options. Then boot into recovery (should give warnings about unmountable /data) and wipe data / factory reset. Then reboot and it should work / odin a stock rom as normal.
If that doesnt work / or instead you get the correct pit file and flash it as well as the rom and have four options ticked: pit, erase all nand + normal two.
If someone gave me their phone with the same symptoms as yours and said: fix it right now that's what I'd do. I'd also warn them I really need to do more research before doing this and using these two options in odin could brick the phone forever.
I hope this gives you lines of inquiry. I found many mixed messages with the erase nand option, most said nothing of merit except don't do it, some said you must wipe data first (which u can't), some said exactly what I've repeated, some say a pit is enough, others had many steps and files ive never heard of to solve the same issue. There is a large thread in the S3 forum about this, even got mentioned on xda proper. My brief cookie crumbs journey did not return any note 2 threads.
Remember one thing, before using odin, double check every detail. Battery, cable being used, files being used (right ones, md5s), right options ticked, computer is in good health, internet is off, Kies is not running. (I'm sure ive missed some)
Solved
I install again the stock kit Kat firmware and the problem was the same, but this time I boot stock recovery and there I made factory reset and that's it. Problem solved and Note boot normally.
Thanks for your help
With or without erase nand in odin?
No, I just flashed normally as all the stock firmwares
I see, thought you'd rule that out. Disappointing really. Glad ur sorted anyway. Remeber wiping data is important when changing roms, even if it's not always absolutely necessary.
Did you try TWRP or Philztouch ? Did you flash 4.3 stock rom?
Sent from my GT-N7100 using Tapatalk
I was running rooted stock version of kit kat. Yesterday afternoon I had Google Music running while doing housework when suddenly the music stopped. I checked the phone and the screen was black and would not turn on. Pulled the battery and then it stuck at the AT&T logo for 30+ minutes. I booted into CWM to perform a factory reset and potentially reinstall the ROM from the external sd card. The factory reset produced the following error.
Code:
--Wiping Data ...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
Fiddled around more with CWM to reset and try to fix. Now, upon reboot, it hands at the Samsung Galaxy Note II screen.
Any help on fixing this so it can at least limp along until my Nexus 6 gets here would be greatly appreciated.
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
ShrekOpher said:
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
You can check here
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my SHIELD Tablet using XDA Free mobile app
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
John.T.Erskine said:
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
Click to expand...
Click to collapse
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Tried that and received the same error as the OP. Can not mount SD card.
ShrekOpher said:
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Same issue
I'm having the same issue as OP. The phone won't get back to recovery. Won't even go into download mode.......Please help!
Edit: I was so used to working on my wife's phone (Note 1) that I was using the wrong button combination for download mode. I still can't get back to recovery, but I'll be ok once I get home.
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
absinthesummer said:
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
Click to expand...
Click to collapse
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
ProjektTHOR said:
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
Click to expand...
Click to collapse
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Flash that, re-root, flash new recovery (note: use a newer recovery, cwm sometimes has issues with our device, but twrp has been updated to work with 4.3+ same with philz, if you prefer that UI. Once 4.4.4 comes out, it doesn't play well with cwm, philz, OR older versions of twrp- I had a fight with a note 3 and recoveries yesterday, finally got it going with the latest twrp).
Boot up the device, flash/update your supersu. If you want to install a different rom now, go ahead. Once you have a new recovery installed, format (manually) /system /data /internal storage /cache /dalvik. The internal storage is important b/c it's usually what causes the /data corruption. Always wipe internal storage when switching between roms (or even between an update, I do). I don't usually wipe everything 3 times like some people do, but it is important to wipe the essentials. In twrp, internal storage is an option when wiping. In cwm & philz, you have to go under mounts & storage & it's second up from the bottom (format /data including /data/media> sdcard). Then back out to the main recovery menu and flash your rom, if you have any issues reboot recovery (not system) and re-flash it.
One more thing, make sure you have enough system storage for the gapps. I've run into issues where the rom flashed fine but gapps was too big for the system and didn't flash correctly. Try a slim gapps
Hope this helps, if you have any other questions I'm happy to try to help. We'll get it fixed for ya
Not able to flash other ROMS besides Stock now.......
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
dirtyalphaman said:
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
Click to expand...
Click to collapse
Ok so you've got the ne5 bootloader, so any time you flash stock you'll have to flash that version or above. Stock rom works, but custom ones don't, correct?
What's weird is that the latest dn3 is a modified stock rom so that shouldn't be an issue.
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
Also, cwm is pretty old and prone to bugs on our devices. However philz is based on cwm and very similar in terms of user interface. It's not as different as twrp is. It has the same style and setup just a few additional tools that cwm doesn't have. It's also more compatible with our devices. If I had to choose one I wouldn't choose cwm, I'd go with philz or twrp for the sake of compatibility.
Thanks. I'll try this when I get home. Yea, once I flashed stock I kept getting Security Notices. I saw this was due to Knox and disabled it but that was a few flash attempts ago. I will follow you steps and let you know how it goes. Once again, thanks.
absinthesummer said:
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Click to expand...
Click to collapse
You are a saint. I'm not sure why I was struggling to find stock 4.4-series firmwares that could be flashed. I was so focused on getting them from sammobile or samware-firmware that I didn't even think to look here. I am going to try this process today and let you know if it works out!
absinthesummer said:
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
Click to expand...
Click to collapse
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
dirtyalphaman said:
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
Click to expand...
Click to collapse
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
absinthesummer said:
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dirtyalphaman said:
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
Click to expand...
Click to collapse
Awesome! Good luck (and I think we're all flash-aholics)
Thank you for all of your help!!! Flashed the latest DN5 rom and it's working great. I found an issue that might have been preventing me from flashing earlier besides the botched root. My external sd card is having a few issues. A week or so ago it changed to read only and wouldn't let me move any files to or from it. Tonight it wouldn't let me flash the rom, but it worked when moved the rom to the internal storage. So I'm good to go! Can't thank you enough!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Please Anyone...
My phone was in Good status before i went to bed last night... I remembered i was playing music on it before i slept off. I woke up lightly in the middle of the night i heard the music still playing. Tiredly, i pushed the Power button and Switched off the device and continued my sleep.
I woke up this morning to switch on my phone and it started this annoying reboot. It boots up to the homescreen and the next 2 seconds, it freezes , trips off and restart. If allowed to Restart, it would follow the same cycle on and on. I was rooted and running Sickness Insane Hybrid V6. I decided to boot into recovery but could not get into Recovery, it hangs on the TWRP Splashscreen. I have restored the Firmware via Odin, the problem persists... I flashed Philz Recovery via Odin and was able to get into Recovery but when i try to perform Factory & Data Reset, the Phone goes off and restarts....
I have gone back to stock via Odin, Rooted and flashed Philz Recovery via Odin, and tried to flash the Insane Hybrid.... The flashing completes but after booting the phone it kept restarting... I also noticed all my apps are still installed even after Going Back to stock and flashing a new ROM.
Any help on what i can do please?
SOLUTION!!!
Thanks! Thanks!! Thanks!!!
In respect to my previous Device Problem, I found a solution to it and here it is should anyone fall in the same shoe!!!
Since i was Flashing Stock in Odin and Custom ROMs, I noticed all my previously installed apps were still present which i dont expect it to be. Then i though one of those apps would have gone Haywire and causing that problem. So i had to get rid of all the installed apps. I cant do that because the Phone would not settle for me to uninstall them, i can not get into TWRP to wipe all Internal Device... Great i can get into Philz Recovery but can not do a Factory Reset... So i flashed the AROMA File Manager in Philz Recovery which enabled me to access my Device files. I navigated to "data/app" and deleted all the Apps. I exited the recovery, Flashed stock in Odin and Voila!!!!
PROBLEM SOLVED!!! No more restarts!!! But the TWRP i used to flash before still would not load up... Still hangs on the "TEAMWIN" splashscreen. Should solve that too soon....
Thanks...
Incase, this solution worked for you... Give me a Thumb!!! CatchYah!!!
?
Pp.
PanchoPlanet said:
?
Pp.
Click to expand...
Click to collapse
Hello please, can you point out to any Flashable Wipe Script to wipe my Device?
Using Aroma FM in Recovery, i noticed tonnes of some error files, if i decide to mark and delete them, it hangs up... My device can no longer boot to Homescreen. How can i wipe my Device please.... System,Data, Cache.... If possible all the folders in the Device.
Sounds like you need to flash stock firmware using odin.
Start fresh with full wipes, don't know anything about this aroma fm in recovery stuff (probably cause of your problem ), keep it simple.
Flash stock run phone for several hours, see if everything works properly.
If you can't live without a custom recovery use CWM, I see a lot issues concerning twrp in posts all the time.
Pp.
PanchoPlanet said:
Sounds like you need to flash stock firmware using odin.
Start fresh with full wipes, don't know anything about this aroma fm in recovery stuff (probably cause of your problem ), keep it simple.
Flash stock run phone for several hours, see if everything works properly.
If you can't live without a custom recovery use CWM, I see a lot issues concerning twrp in posts all the time.
Pp.
Click to expand...
Click to collapse
Thanks, But i have being getting the problem even before trying to use AROMA File Manager.... I only use AROMA FM to see if i could manually delete every folder in the phone. I have FLASHED STOCK over a Hundred times.... Its still the same!!!
Now, after some more researches... i was asked to use the Re-Partion option on Odin with a PIT File... Please can you point out to where i can get SGH-M919 Pit File?
Have never used a pit file but have seen requests for it in development, ShinySide has a semi stock ROM and may have it for you. Flashing a pit file can be tricky so proceed with caution and follow instructions to the letter. Maybe putting a request for it with instructions in ShinySide's thread can get you fixed up.
Here .…..... http://forum.xda-developers.com/showthread.php?t=2873695
Pp.
sent from my microwave running lollipop 5.0.
Following want to now how this turns out so I can fully fix my buggered device.
strtkempo said:
Following want to now how this turns out so I can fully fix my buggered device.
Click to expand...
Click to collapse
Sorry i'm replying late. Already fixed my Device... Can yo explain the current Bug State of your Device and the present behaviour...
Always Quote or Mention me so i can always attend to it...
Hey everyone so I took my phone out of my pocket and it was stuck in a boot loop. I tried taking the battery out, volume up + power + home, volume down + power + home but nothing. I've tried booting it also without a battery.
I have Quantum running on my phone, and have never had any problems. The occasional restart but now my phone won't even get to the home screen. I get just a boot loop with normal sounds, and then my LED begins to flash. Then it just loops again ..
Don't really know what to do.
UPDATE: Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
DELETED - irrelevant information.
StoneyJSG said:
DELETED
Click to expand...
Click to collapse
Why ?
Rovon said:
Why ?
Click to expand...
Click to collapse
Will your computer detect it if connected? (Odin, Heimdall, adb)
dawgdoc said:
Will your computer detect it if connected? (Odin, Heimdall, adb)
Click to expand...
Click to collapse
Yes computer is detecting it with Odin.
Rovon said:
Yes computer is detecting it with Odin.
Click to expand...
Click to collapse
What is on the phone's screen while the device is detected by Odin?
There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.
dawgdoc said:
What is on the phone's screen while the device is detected by Odin?
There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.
Click to expand...
Click to collapse
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"
Rovon said:
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"
Click to expand...
Click to collapse
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
Rovon said:
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/
Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
Click to expand...
Click to collapse
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...
Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.
jason2678 said:
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...
Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.
Click to expand...
Click to collapse
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.
Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.
Rovon said:
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.
Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.
Click to expand...
Click to collapse
So I keep getting a bunch of errors with TWR. I tried installing AOKP but got stuck at a boot screen again, and after trying to wipe my phone I get an error message saying "Failed". Now I'm trying install Quantum again but get an error message saying "Zip file is corrupt". T__T
Going to try another rom..
Update: I've tried Quantum again and it finally installed but now I'm stuck in a bootloop again. This is so frustrating ...
It seems like you are on the correct track. Don't give up.
Hopefully it is not a matter of the internal sdcard going bad.
If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.
dawgdoc said:
It seems like you are on the correct track. Don't give up.
Hopefully it is not a matter of the internal sdcard going bad.
If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.
Click to expand...
Click to collapse
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything
Rovon said:
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything
Click to expand...
Click to collapse
Couple of thoughts:
Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.
It could be that a full wipe before trying again to flash the ROM would be what you need.
If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.
dawgdoc said:
Couple of thoughts:
Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.
It could be that a full wipe before trying again to flash the ROM would be what you need.
If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.
Click to expand...
Click to collapse
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.
Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.
Rovon said:
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.
Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.
Click to expand...
Click to collapse
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
jason2678 said:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
Click to expand...
Click to collapse
+1
also to confirm modem , type in ...
getprop | grep version.baseband
"all i can really do , is stay out of my own way and let the will of heaven be done"
jason2678 said:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.
I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses). There are plenty of landmines and some bear traps out there.
Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:
Code:
getprop ro.bootloader
That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.
Was your storage encrypted when you were running normally?
The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...
If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it . The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.
If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
Click to expand...
Click to collapse
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.
My bootloader is: I747UCDLK3
I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.
mrrocketdog said:
+1
also to confirm modem , type in ...
getprop | grep version.baseband
"all i can really do , is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
Hmm .. that command didn't seem to pull anything up for me.
Rovon said:
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.
My bootloader is: I747UCDLK3
I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.
Hmm .. that command didn't seem to pull anything up for me.
Click to expand...
Click to collapse
LK3 is a pretty out of date bootloader, and in this case that might be a good thing.
You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/
For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.
This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.
jason2678 said:
LK3 is a pretty out of date bootloader, and in this case that might be a good thing.
You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/
For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.
This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.
Click to expand...
Click to collapse
Alright I'm downloading this now. Assuming this works, should I do an OTA update then root or am I safe to root the device from odin as soon as this bootloader is installed?