Related
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
Recently just received a warranty replacement Note 2 and of course first thing I did was root and unlock it. After flashing a rom a indicator would pop up saying TWRP had lost root permissions and after selecting okay, fix permissions for it. I wrote it off not thinking much of it but after flashing a different rom the same pop up appeared again, still no problems. Finally my phone started locking up and today it eventually bricked up as I flashed a rom. No biggie, I flashed back to stock and am good to go but I just want to know if anyone else has come across this same issue as well?
Sent from my SCH-I605 using Tapatalk 4 Beta
endo689 said:
Recently just received a warranty replacement Note 2 and of course first thing I did was root and unlock it. After flashing a rom a indicator would pop up saying TWRP had lost root permissions and after selecting okay, fix permissions for it. I wrote it off not thinking much of it but after flashing a different rom the same pop up would appear again, still no problems. Finally my phone started locking up and today it eventually bricked up as I flashed a rom. No biggie, I flashed back to stock and am good to go but I just want to know if anyone else has come across this same issue as well?
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Only time I've seen this it has been an issue with the rom I'm flashing.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Only time I've seen this it has been an issue with the rom I'm flashing.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
For some reason it happened with every rom I would flash. Possibly mucked something up when I rooted and unlocked in the first place.
Sent from my SCH-I605 using Tapatalk 4 Beta
I is twrp that causes the issue, if I'm mistaken they have updated to fix that bug.
M.A.D.NoTe.||
Going through the exact same thing right now, same situation and all, did you get this worked out? I flashed back to stock just a couple minutes ago and am now in the process of flashing a custom rom again. Never experienced this before and been flashing on this phone the Note 2 since October. New phone, new problem. Used the Toolkit to do everything every time I get a new phone. This is my third.
StevetotheH said:
Going through the exact same thing right now, same situation and all, did you get this worked out? I flashed back to stock just a couple minutes ago and am now in the process of flashing a custom rom again. Never experienced this before and been flashing on this phone the Note 2 since October. New phone, new problem. Used the Toolkit to do everything every time I get a new phone. This is my third.
Click to expand...
Click to collapse
Sorry for such a long delay in responding. I found a fix for this issue. I ended up just flashing all the way back to the original stock rom when the Note 2 was released then went about using the unlocking/rooting methods and have not ran into a single problem.
Sent from my SCH-I605 using Tapatalk 4 Beta
endo689 said:
Sorry for such a long delay in responding. I found a fix for this issue. I ended up just flashing all the way back to the original stock rom when the Note 2 was released then went about using the unlocking/rooting methods and have not ran into a single problem.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I was having this issue a few days ago and formatting my internal SD with TWRP and reflashing my ROM fixed it.
Sent from my SCH-I605 using XDA Premium HD app
I wipe internal every time along with the normal wipes when I flash a rom. Gives you the best chance of everything being stable and having a great gps lock even on aosp or tablet roms
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
I wipe internal every time along with the normal wipes when I flash a rom. Gives you the best chance of everything being stable and having a great gps lock even on aosp or tablet roms
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I do this as well but for some reason twrp still lost root permissions.
Oh well having no issues anymore so I am a happy camper.
Sent from my SCH-I605 using Tapatalk 4 Beta
USB connection problems
Now I keep running into USB driver issues as of late. Don't understand why this keeps happening. Uninstalled and reinstalled all drivers and Note 2 connects for awhile and then completely stops. I can browse/edit items on the phone but cannot copy files over to it. A pop up saying it has been disconnected and cannot copy files to said device. WTF?!
endo689 said:
Now I keep running into USB driver issues as of late. Don't understand why this keeps happening. Uninstalled and reinstalled all drivers and Note 2 connects for awhile and then completely stops. I can browse/edit items on the phone but cannot copy files over to it. A pop up saying it has been disconnected and cannot copy files to said device. WTF?!
Click to expand...
Click to collapse
What OS you on? Try a different cable and different usb port. Use the drivers from mskips all in one tool from the forum. Have you tried adb devices to see if it recognizes your device? If you haven't rebooted you rig lately do that and your device as well. I had this happen for a minute on Win8 I had to manually point the driver update to the file I wanted to use.
Rock, Flag and Eagle!
Way back when I got my Note 2.... the version of casual actually flashed a wrong TWRP , it was the one for the international Note 2.
The fix was to simply install the newest TWRP for our phone (SCH-i605)
Milimbar said:
Way back when I got my Note 2.... the version of casual actually flashed a wrong TWRP , it was the one for the international Note 2.
The fix was to simply install the newest TWRP for our phone (SCH-i605)
Click to expand...
Click to collapse
What?
Rock, Flag and Eagle!
StevetotheH said:
What OS you on? Try a different cable and different usb port. Use the drivers from mskips all in one tool from the forum. Have you tried adb devices to see if it recognizes your device? If you haven't rebooted you rig lately do that and your device as well. I had this happen for a minute on Win8 I had to manually point the driver update to the file I wanted to use.
Rock, Flag and Eagle!
Click to expand...
Click to collapse
I will definitely give this a shot when I have a chance.
Sent from my SCH-I605 using Tapatalk 4 Beta
Make sure youre using the latest TWRP version.
I'll try to make this brief and to the point. I just got my Thunderbolt a few days ago and it was already rooted. My original goal was to flash it myself and put it on PagePlus. (I posted in another thread, but no one answered) I ran CDMA Workshop and I noticed that my T-bolt wasn't showing up in the ports under device manager. I then attempted to unroot it but that failed badly. I ran through a bunch of articles online and I figured out how to install customs roms. I thought that would fix the issue.
So far I've tried 4 different roms and they've all installed fine. It's just the reboot that's the issue now. When it turns on it goes to the white HTC screen and then it hangs on a blank screen until it reboots again. It's stuck in a loop. So if anyone knows what's wrong, I'd seriously be very thank full.
Any help would be extremely appreciated. Thank you very much in advance.
I guess I didn't ask the question correctly. I dunno. I installed a few custom roms and and it gets stuck after the HTC screen. what can I do to fix it?
What recovery are you using?
Sent from my ADR6400L using Tapatalk 2
thank you for replying. I'm using 4EXT Recovery Touch. I make sure I wipe / format everything first everytime.
When you boot into the bootloader does it list your radio version?
Sent from my ADR6400L using Tapatalk 2
yes, it's Radio - 1.48.00.930w_3
Here is the complete list:
MMECHA XD SHIP S-ON
HBOOT - 1.05.0000
MICROP - /
Radio - 1.48.00.930w_3
eMMc - boot
Have you flashed either of the official ICS ota radios? I think you have the wrong baseband.
Sent from my ADR6400L using Tapatalk 2
OK, so I went to this site and got the radio, renamed it, and then moved it over to the freshly formatted sd card. I ran bootloader, it's been at the HBOOT checking ... [PG05IMG.zip] screen for about 5 minutes now, I'm about to reboot and try again. I don't understaned the part about having s-off. I know it means security off, but I don't know how to turn it off.
http://www.androidmodmarket.com/ModMarket/Listings/XDA-L-2136273.html
edit: still hangs at the HBOOT checking ... [PG05IMG.zip] screen
Lol you're s on so you cant flash a radio. You need to run the revolutionary tool and get s off. Then flash the radio in the bootloader.
Sent from my ADR6400L using Tapatalk 2
Is there another way to turn s-off? I can't get it to recognize my phone at all and the drivers are installed. I turn on the phone and then it goes go the htc logo and then to a blank screen. it hangs there for a few and then reboots into a loop. since s-on can't I just install a stock rom and be done with it?
Try flashing a GB ROM.
Sent from my ADR6400L using Tapatalk 2
all the rom downloads I found are on Multiupload. Nothing I can use. do you have a link?
Yea I can't help you much there. I'm sure someone else might have a link. You could try infectedrom.com. I bet the link to eternity still works
Sent from my ADR6400L using Tapatalk 2
I think all I need it to get s-off. I found a rom that is compatible with the radio I have. Is there another way to turn s-off with a bootloader or through recovery?
before this phone becomes a victim of Hulk Smash, does anyone else have any ideas?
So are you able to connect with ADB from a computer? The All-in-One tool might be able reset to factory, so you can start over. It can also walk you through Revolutionary/S-Off.
http://forum.xda-developers.com/showpost.php?p=41384498&postcount=519
Note on Windows 7 with the latest version of the tool I linked above, I had to use Koush's Universal ADB Driver instead of the HTC one -- it kept causing my computer to blue screen/reboot.
If you're still looking for a GB ROM as someone mentioned a few posts back, the ThunderShed ROM on rootzwiki is very good.
jhudak said:
So are you able to connect with ADB from a computer? The All-in-One tool might be able reset to factory, so you can start over. It can also walk you through Revolutionary/S-Off.
http://forum.xda-developers.com/showpost.php?p=41384498&postcount=519
Note on Windows 7 with the latest version of the tool I linked above, I had to use Koush's Universal ADB Driver instead of the HTC one -- it kept causing my computer to blue screen/reboot.
If you're still looking for a GB ROM as someone mentioned a few posts back, the ThunderShed ROM on rootzwiki is very good.
Click to expand...
Click to collapse
I just installed Airborne-GoUI-B1, Is ThunderShed better in your opinion?
Did go airborne install OK and boot? If so you should try using the revolutionary tool to get s off now.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
Did go airborne install OK and boot? If so you should try using the revolutionary tool to get s off now.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Oh, yeah. I'm way passed all the issues I had earlier. I'm back to rooted and running smoothly again. I installed airborne, but I really don't care too much for it. It seems real boring. I am considering going back to stock so I can use the legit ICS. All I have to do is just flash the update stock update file and I should be good to go right? I think it's on Android 2.??? and I'd rather have it on legit 4.???
Whatever you do don't take the update.... Just make sure you have ICS radios flashed before you flash the ICS ROMs.
Sent from my ADR6400L using Tapatalk 2
when i install RLS 6 hyperdrive my phone starts fine but after one minute it restarts and again turns again on works fine for 30 seconds and again restart help!!!!
When posting something like this its good to know the beforehand so people know what led up to this. Did you wipe? What recovery you using? Did you follow the install instructions word for word?
SCH-I545 using Tapatalk 2
A couple of possibilities:
Make sure you wipe per the dev's recommendations prior to flashing.
Try installing with minimal mods and see if you can get it to boot. Once you flash, you can always dirty flash the same installer and pick a couple additional mods and see what's causing the issue. Some people noted they were having problems with the Walkman mod causing bootloops.
Check the MD5 of your download against what is in the OP. If you downloaded to PC then copied to SD card, check that the MD5 on the card matches that on the PC and what's online (some people had problems where the file was corrupted during transfer to phone).
Also making sure you have one of the most recent recoveries is a good thing to check. I believe I used TWRP 2.6.0.0 and it worked fine for me.
Finally, try using the stock kernel instead of stock optimized or a third party kernel. I can use stock or stock optimized, for example, but when I flash faux it bootloops about 80% of the time on my phone.
There is a good bit of info about the bootlooping issue on RLS6 in the original Hyperdrive thread. Start on page 472 and read on from there.
http://forum.xda-developers.com/showthread.php?t=2301724&highlight=bootlooping&page=472
hexitnow said:
When posting something like this its good to know the beforehand so people know what led up to this. Did you wipe? What recovery you using? Did you follow the install instructions word for word?
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
yes i did man i swear !!!!
thanks
wontongo said:
There is a good bit of info about the bootlooping issue on RLS6 in the original Hyperdrive thread. Start on page 472 and read on from there.
http://forum.xda-developers.com/showthread.php?t=2301724&highlight=bootlooping&page=472
Click to expand...
Click to collapse
thanks but i dont think that my problem sir thanks !!! more help please?
Did you flash with twrp or cwm. Theres been a few people reporting bootloops when wiping/flashing with twrp. If so you might want to try cwm. Have been using cwm since the DX was the "it" phone. Got it on 4 devices now and have never had a single problem with it.
SCH-I545 using Tapatalk 2
i found the solution
hexitnow said:
Did you flash with twrp or cwm. Theres been a few people reporting bootloops when wiping/flashing with twrp. If so you might want to try cwm. Have been using cwm since the DX was the "it" phone. Got it on 4 devices now and have never had a single problem with it.
SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
the solution was not to install any audio mods and any players like the walkman just the samsung one thanks man !!
TWRP = bad news with HD6
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
dvdrsmth said:
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
Click to expand...
Click to collapse
I've installed HD6 twice on my phone using TWRP 2502. I followed Dev's installation instructions to the T and have had zero issues.
Includes inissac
reebz said:
I've installed HD6 twice on my phone using TWRP 2502. I followed Dev's installation instructions to the T and have had zero issues.
Click to expand...
Click to collapse
Good to know. I believe that I followed the dev instructions as well.
One time my uncle was over and I was telling him about a marital concern. He told me that I should probably not do what I had been doing and that there was probably a better way. I listened to him and life has been better. Life is full of choices.
dvdrsmth said:
Just want to say that TWRP and HD6 definitely are not playing nice together. CWM FTW!
Click to expand...
Click to collapse
I agree, like I said have been using it on multiple devices, for close to 3 years now and have never had a single problem. Tried out twrp a few weeks ago and didnt like it to much. To each his own though :thumbup:
SCH-I545 using Tapatalk 2
I have also been having difficulty with both bootloops and the phone freezing on the Samsung image and not booting past this point.
I did a full wipe including data with Twrp. After multiple attempts I'm considering switching to CWM. My question is how to I install CWM on a device without a functioning rom?
Does this require flashing back to stock with odin or is there an easier way?
Sent from my SPH-L900 using Tapatalk 2
rickt1152 said:
I have also been having difficulty with both bootloops and the phone freezing on the Samsung image and not booting past this point.
I did a full wipe including data with Twrp. After multiple attempts I'm considering switching to CWM. My question is how to I install CWM on a device without a functioning rom?
Does this require flashing back to stock with odin or is there an easier way?
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
You can flash CWM from within TWRP, just use ADB to copy the zip file onto your phone then flash, or alternatively you can use fastboot to flash a new recovery directly to the phone. Neither method needs a working ROM to accomplish.
So the problem started when I flashed a 4.3 rom last friday. I formatted my internal memory in recovery mode because for some reason I only had 4 gigs of space and had moved everything over to the sd card. Once that was done phone said like 8 gigs available and thought everything was fixed. Well now if I turn off my phone it gets stuck in some kind of bootloop but it's not looping. It's just sits at the Samsung unlock symbol and custom screen. Doesn't loop just sits there. So one day I decided to format the internal memory again and the phone boots up like normal, but I can't power off the phone without going into recovery and formatting the internal memory every time. Any ideas on what is causing it or how I can make the Samsung custom boot stock instead so I can send it out.
I also have tried flashing another 4.3 rom and it doesn't seem to go away either.
I'm not an expert on how they have to make this stuff work with the mdk bootloader but I'm sure it's not hardware related. Have you tried flashing back to a 4.2 rom?
Sent from my SCH-I545 using Tapatalk 2
Downloading one now hopefully it will fix it.
Which recovery are you using? Make sure to wipe data, cache, and dalvik 3x each, then flash your rom
Sent from my SCH-I545 using Tapatalk 2
TWRP and I flashed hyperdrive still no luck still freezing in the same spot and have to actually format to get past it.
Anyone else have any idea on what else I can try?
BlackDynomitr said:
Anyone else have any idea on what else I can try?
Click to expand...
Click to collapse
What version of TWRP are you using?
Sent from my SCH-I545 using Tapatalk
I believe 2.5 I'm guessing only way to check is to go into recovery again.
BlackDynomitr said:
I believe 2.5 I'm guessing only way to check is to go into recovery again.
Click to expand...
Click to collapse
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
heath2805 said:
Yep that's the only one I've never had any issues with. TWRP 2.5.0.2
Edit: If your still having issues you could always Odin back with Stock firmware and get a clean start. I know its a pain lol
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
BlackDynomitr said:
Well I think that might work only thing I'm afraid is what if it doesn't turn on.
Click to expand...
Click to collapse
Well if it doesn't turn on after flashing stock firmware via Odin, you'll know its a hardware issue with it and your warranty should cover a new replacement.
Sent from my SCH-I545 using Tapatalk
I had this issue when I first got my phone. I bought it off Swappa, it was already running TWRP 2.5.0.2, giving me nothing but problems. I switch to Philz Touch and no longer have the issue.