Related
Hey guys,
I was having trouble with a previous ROM that I was using (Paranoid Android 4.2) after several months I decided to reflash...
With a pretty full internal SD so I decided to delete some of my old files etc. I picked a new ROM (JediMindTricks 4.2), updated my CWM/Rom Manager, wiped with SuperWipe, Installed the rom, and now I am stuck in a real jam....
Of course I am boot looping and as a result of that I am trying to revert to a backup, however CWM freezes almost instantly when trying to do anything. Whether it's wiping, reinstalling, or restoring a back-up it freezes. So with a similar previous issue I decided at this point I need to revert to stock ICS using ODIN. Inside ODIN (which I have never had any issues with) when I put the phone in download mode ODIN never recognizes it and will not allow me to revert to stock...
At this point I seem to be out of options.... What do you guys think?
namelessghoul said:
Hey guys,
I was having trouble with a previous ROM that I was using (Paranoid Android 4.2) after several months I decided to reflash...
With a pretty full internal SD so I decided to delete some of my old files etc. I picked a new ROM (JediMindTricks 4.2), updated my CWM/Rom Manager, wiped with SuperWipe, Installed the rom, and now I am stuck in a real jam....
Of course I am boot looping and as a result of that I am trying to revert to a backup, however CWM freezes almost instantly when trying to do anything. Whether it's wiping, reinstalling, or restoring a back-up it freezes. So with a similar previous issue I decided at this point I need to revert to stock ICS using ODIN. Inside ODIN (which I have never had any issues with) when I put the phone in download mode ODIN never recognizes it and will not allow me to revert to stock...
At this point I seem to be out of options.... What do you guys think?
Click to expand...
Click to collapse
Did you try to boot in recovery and install CWM from internal SD? Wipe data / factory reset and wipe cache in recovery mode... I'm not an expert but it won't hurt to try!
jonmassot said:
Did you try to boot in recovery and install CWM from internal SD? Wipe data / factory reset and wipe cache in recovery mode... I'm not an expert but it won't hurt to try!
Click to expand...
Click to collapse
Unfortunately it is completely unresponsive when attempting to install any version of CWM.zip that I try to install in recovery.
namelessghoul said:
Unfortunately it is completely unresponsive when attempting to install any version of CWM.zip that I try to install in recovery.
Click to expand...
Click to collapse
Yesterday I had trouble with a bad upgrade through Kies and my cell kept telling me to plug it with Kies and do an emergency recovery. Nothing worked as the emergency recover didn't work with my cellphone and I wasn't able to boot in recovery nor download mode. I had to plug it in another computer and re-ODIN an earlier version of my stock rom... Not sure if it will helps you...
Plug in your phone to your computer, open kies, select "emergency firmware recovery", enter serial number from phone (write down beforehand) then cross your fingers and hope for the best. Good luck.
Also, be careful with those wiping scripts.
Sent from XDA app
jonmassot said:
Yesterday I had trouble with a bad upgrade through Kies and my cell kept telling me to plug it with Kies and do an emergency recovery. Nothing worked as the emergency recover didn't work with my cellphone and I wasn't able to boot in recovery nor download mode. I had to plug it in another computer and re-ODIN an earlier version of my stock rom... Not sure if it will helps you...
Click to expand...
Click to collapse
After literally wrestling with this for the last 7 hours ODIN has finally recognized it...
You DONT super wipe with the latest cmw recoveries. Superwipe was made for the early 5.0.x.x version, it breaks the new recoveries.
So i reset my GS3 yesterday. I am running a stock rooted phone.. My phone has always been fine but after a reset through the phone the phone never loaded back up. It was stuck on the samsung screen. I tried pulling the battery out a few times. I went into my CWM recovery and tried wiping both caches with no luck. I tried restoring the phone and that didn't work. I finally tried wiping all data and now the phone won't boot at all. It says phone can not boot and will go into odin mode. Odin will recognize my phone though. What should i do? Should I try to restore my phone to factory through odin? I can't find the stock sprint version tar file. I could only find the verizon one. Can someone help me and tell me what is the best step for me? I can get into CWM but the phone won't boot.
wings9130 said:
So i reset my GS3 yesterday. I am running a stock rooted phone.. My phone has always been fine but after a reset through the phone the phone never loaded back up. It was stuck on the samsung screen. I tried pulling the battery out a few times. I went into my CWM recovery and tried wiping both caches with no luck. I tried restoring the phone and that didn't work. I finally tried wiping all data and now the phone won't boot at all. It says phone can not boot and will go into odin mode. Odin will recognize my phone though. What should i do? Should I try to restore my phone to factory through odin? I can't find the stock sprint version tar file. I could only find the verizon one. Can someone help me and tell me what is the best step for me? I can get into CWM but the phone won't boot.
Click to expand...
Click to collapse
If you can get into recovery mode, you can just restore a nandroid backup (if you have one made). If you don't have one, you can wipe /system, /data, and the caches and reflash your Rom (provided you have it saved on your SD card).
If none of the above work, download mode is your best friend.
You can get into Download (Odin) Mode. That's a good thing. Sextape has the md4 TAR file for your over in their thread (warning, outside link). They have the stock unrooted as well as stock rooted file. Since you have already wiped your data, you might as well flash the "Restore" version:
"Restore" Versions - Wipes your user data
SPH-L710_MD4_1130792_Stock_Restore [EXE|TAR.MD5.GZ]
SPH-L710_MD4_1130792_Rooted_Restore [EXE|TAR.MD5.GZ]
Click to expand...
Click to collapse
If you know how to use Odin, you can just downlaod the TAR file, but I recommend using their auto-extractor (the exe file), since it's well tested and there's less chance of user error.
All that being said, I'm curious to how your phone became "softbricked." Did you install any apps or mods recently that could've caused it? Custom Kernel?
It sounds like you eventually ended up wiping /system, which would be why you can't boot up now. I haven't heard of it automatically going into download mode because of that, but I haven't tested it on my phone, either.
try rwilco 12's android file repository. he has everything you will need
http://www.rwilco12.com/
You can also take the sd card out plug into a computer download a rom zip put it on the sd card pop it back into the phone and flash through the custom recovery which should be there.
Sent from the future via Xparent Green Tapatalk 2
Thanks for the help everyone. I guess I didn't soft brick the phone I just wiped it and there was no rom on it.
So this is the weirdest "brick" I have ever experienced. My phone was working flawlessly with a TWRP recovery and a slightly modded mostly stock ROM. I was playing around modding the stock MMS app, SecMms.apk, and flashing it through recovery. One of these flashes did not complete successfully. I got to the lockscreen, but it would not respond. And there was no network connection. So I figured something got screwed up. I rebooted into recovery and flashed a stock ROM. Boot loop. I got back into recovery and performed a factory data reset, erased everything, flashed a stock ROM. Boot loop. I downloaded a completely stock ROM with stock recovery, stock everything. Got into download mode and flashed it through ODIN. Boot loop. Well, actually, the initial boot got a screen where I could see the taskbar with time and no-service indicator; the rest of the screen was black for a minute; then I got a popup window stating that "Process system is unable to continue" and asking if I wanted to wait of close it. Then it boot looped. I tried booting without a SIM card and an external SD card - same result.
So, to recap - I can get to Download Mode, and ODIN, but anything I flash, including completely stock ROM boot loops.
I am at a loss as to what to try next. If anyone has ideas, I'm willing to try just about anything. I'm gonna take it to T-Mo store tomorrow to see if they can do anything with it...
re: phone issues
6uPMAH said:
So this is the weirdest "brick" I have ever experienced. My phone was working flawlessly with a TWRP recovery and a slightly modded mostly stock ROM. I was playing around modding the stock MMS app, SecMms.apk, and flashing it through recovery. One of these flashes did not complete successfully. I got to the lockscreen, but it would not respond. And there was no network connection. So I figured something got screwed up. I rebooted into recovery and flashed a stock ROM. Boot loop. I got back into recovery and performed a factory data reset, erased everything, flashed a stock ROM. Boot loop. I downloaded a completely stock ROM with stock recovery, stock everything. Got into download mode and flashed it through ODIN. Boot loop. Well, actually, the initial boot got a screen where I could see the taskbar with time and no-service indicator; the rest of the screen was black for a minute; then I got a popup window stating that "Process system is unable to continue" and asking if I wanted to wait of close it. Then it boot looped. I tried booting without a SIM card and an external SD card - same result.
So, to recap - I can get to Download Mode, and ODIN, but anything I flash, including completely stock ROM boot loops.
I am at a loss as to what to try next. If anyone has ideas, I'm willing to try just about anything. I'm gonna take it to T-Mo store tomorrow to see if they can do anything with it...
Click to expand...
Click to collapse
Go into recovery mode and do a complete wipe including "Factory Reset", wipe data, wipe system,
wipe cache, wipe dalvik cache and then if you have a working nandroiod backup restore it.
If you don't have a nandroid backup then go into download mode and flash the official stock
firmware for the N900T phone from http://SamMobile.com
Either one of these two options will get your phone back up and running.
Good luck!
I have already done all of the above, and...no go. Even stock firmware from SamMobile boot loops. Unfortunately, I do not have a nandroid backup, so that's the one thing I cannot do.
6uPMAH said:
I have already done all of the above, and...no go. Even stock firmware from SamMobile boot loops. Unfortunately, I do not have a nandroid backup, so that's the one thing I cannot do.
Click to expand...
Click to collapse
Google zedomax you will find his website for unrooting note 3. Will walk you thru with ever step.
It is no longer rooted after I have flashed stock firmware/ROM from SamMobile. Believe me , I have tried all the known methods of returning this phone to stock/unroot. I have flashed through recovery when I had custom recovery. I have flashed through ODIN. So far I have been unable to fix the issue. I am thinking my internal storage is corrupt, or the partition is corrupt. Anyone knows of a way to rebuild/repartition internal storage?
6uPMAH said:
It is no longer rooted after I have flashed stock firmware/ROM from SamMobile. Believe me , I have tried all the known methods of returning this phone to stock/unroot. I have flashed through recovery when I had custom recovery. I have flashed through ODIN. So far I have been unable to fix the issue. I am thinking my internal storage is corrupt, or the partition is corrupt. Anyone knows of a way to rebuild/repartition internal storage?
Click to expand...
Click to collapse
Did you try the "boot loop fix" flashable? It's essentially a script that sort of recreates the efs partition in recovery. It's been linked a few times in the twrp thread, and there may be a thread dedicated to the topic (search for "brick loop") - I don't have the links handy though, apologies.
The mans right^ that helped me out through my "soft brick". Totally out of the blue. Wasnt even messing around with anything I didnt knew I was doing
Sent from my SM-N900T using Tapatalk
Anybody has a link? I've searched, but there's nothing specific to Note 3 TMO...
6uPMAH said:
Anybody has a link? I've searched, but there's nothing specific to Note 3 TMO...
Click to expand...
Click to collapse
The method is outlined in the OP of this thread but the flashable version of what is outlined there can be found in this thread - hope that helps!
Thanks. I'll give it a go after work.
UPDATE: All is well in the world again. Thanks everyone for all your help. Thanks dwitherell ! The thread you pointed me to was the solution!
So I was running CM11 M8 and restored back to stock(Root66) BNC1 on my T999L.Ever since that not one single ROM will boot regardless of which recovery I try to flash it with(CWM,TWRP,PhilZ,Multiboot).I can Odin back to BNC1(Root66 or Straight Stock) with no issues and the ROMS never give any error's while installing they just hang at the boot screen.I've tried factory reset with dalvik and cache after flashing as well and get nothing still.My phone works fine still no issues there just not able to sucessfully boot a flashed ROM.Any advice would be greatly appreciated.
How long did you leave it on the boot screen? It can take a while at times
serio22 said:
How long did you leave it on the boot screen? It can take a while at times
Click to expand...
Click to collapse
Of course I waited. When I install CM 11 it was almost 30 minutes before I said screw it and restored my nandroid.
Have you tried factory resetting from stock recovery? It will wipe internal sd just so you know.
DocHoliday77 said:
Have you tried factory resetting from stock recovery? It will wipe internal sd just so you know.
Click to expand...
Click to collapse
Yes I have also tried that Doc.
Try flashing another rom from recovery. Before trying to reboot, select Copy Log to SD. See if it has any clues. (It'll be towards the end of the file)
You can post it here if you can't find anything.
Aside from that, all I can think to try is flashing with Odin again and select re-partition.
DocHoliday77 said:
Try flashing another rom from recovery. Before trying to reboot, select Copy Log to SD. See if it has any clues. (It'll be towards the end of the file)
You can post it here if you can't find anything.
Aside from that, all I can think to try is flashing with Odin again and select re-partition.
Click to expand...
Click to collapse
Did that as well and looked at the log.Did another restore through Odin to complete stock then to Root66 and that seems to have fixed the issue...hmmm no idea what was wrong.
Sometimesbtheres just no good way to know the cause.
Glad to hear it seems to be ok now! For the next several flashes you do, just kerp an eye on how its acting and copy the log to sd each time, just in case. If it still is working ok after a few times it should be ok to go back to doing things like normal.
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?