Phone wont boot - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

Been running Notorized Stable 2 for a few weeks with no issues. Today I shut off my phone for a little while at work, when I went to turn it back on it went through the Samsung screen, Sprint Spark screen, then it vibrates once, goes black and doesn't do anything after that. I've tried factory reset, clearing/wiping everything and reflashing Notorized, same thing happening. No idea what to do now. HUGE thanks in advance for any assistance.

fcramtek said:
Been running Notorized Stable 2 for a few weeks with no issues. Today I shut off my phone for a little while at work, when I went to turn it back on it went through the Samsung screen, Sprint Spark screen, then it vibrates once, goes black and doesn't do anything after that. I've tried factory reset, clearing/wiping everything and reflashing Notorized, same thing happening. No idea what to do now. HUGE thanks in advance for any assistance.
Click to expand...
Click to collapse
Sounds like the reactivation lock from OE1 or OF5 build. Is that where you started before Noterized?
Can't boot after re-flashing CF Auto Root? Wiping everything and powering off and Odin OF5 stock tar could be your only option; Odin another stock tar would fail if you're on one of those builds. You'd have to boot and disable reactivation lock in Settings/Security and enable developer mode and USB debugging mode to get back to Noterized. But I'm not sure that's 0 issues, 100% compatibility. Unless maybe after all that, you can still see reactivation lock in security after booting Noterized? Still wouldn't know, myself; I'm still on OB7. (You have to tell me otherwise).
Sent from my SM-N910P using Tapatalk

Flash the recovery again. Just my guess.

samep said:
Sounds like the reactivation lock from OE1 or OF5 build. Is that where you started before Noterized?
Can't boot after re-flashing CF Auto Root? Wiping everything and powering off and Odin OF5 stock tar could be your only option; Odin another stock tar would fail if you're on one of those builds. You'd have to boot and disable reactivation lock in Settings/Security and enable developer mode and USB debugging mode to get back to Noterized. But I'm not sure that's 0 issues, 100% compatibility. Unless maybe after all that, you can still see reactivation lock in security after booting Noterized? Still wouldn't know, myself; I'm still on OB7. (You have to tell me otherwise).
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Yeah i was on stock OE1 when i rooted. I have tried reflashing w/ CF Auto ROot and then reflashing the ROM. Guess I'll have to try and track down a stock OE1 .tar?

fcramtek said:
Yeah i was on stock OE1 when i rooted. I have tried reflashing w/ CF Auto ROot and then reflashing the ROM. Guess I'll have to try and track down a stock OE1 .tar?
Click to expand...
Click to collapse
I'll save you the search trouble. Search for OF5 tar instead. There never was a OE1 tar release.
http://forum.xda-developers.com/showthread.php?p=61877147
Sent from my SM-N910P using Tapatalk

samep said:
I'll save you the search trouble. Search for OF5 tar instead. There never was a OE1 tar release.
http://forum.xda-developers.com/showthread.php?p=61877147
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks! I was searching for an OE1 tar for a while. I came across the OF5 but wasn't sure if i'd be able to use it or not. Downloading now. Hopefully it works. I owe you a beer if it does!!!

samep said:
I'll save you the search trouble. Search for OF5 tar instead. There never was a OE1 tar release.
http://forum.xda-developers.com/showthread.php?p=61877147
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Alright, so i got the OF5 .tar flashed and I can finally get past the yellow spark screen, but not much further. The "Android is upgrading...optimizing app xx of xxx" window comes up. It'll update a few numbers, then resets and keeps looping like this. Any thoughts? Try and reflash?

fcramtek said:
Alright, so i got the OF5 .tar flashed and I can finally get past the yellow spark screen, but not much further. The "Android is upgrading...optimizing app xx of xxx" window comes up. It'll update a few numbers, then resets and keeps looping like this. Any thoughts? Try and reflash?
Click to expand...
Click to collapse
Did you check the OF5 tar md5? Wipe everything but ext sdcard? Did you power down prior to Odin stock tar. Is that all you flashed?
You're saying the initial boot after stock tar Odin fails?
md5 shared earlier and confirmed was aae4cbc9f8b12e61c42819cf8ae542bf
Sent from my SM-N910P using Tapatalk

samep said:
Did you check the OF5 tar md5? Wipe everything but ext sdcard? Did you power down prior to Odin stock tar. Is that all you flashed?
You're saying the initial boot after stock tar Odin fails?
md5 shared earlier and confirmed was aae4cbc9f8b12e61c42819cf8ae542bf
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
MD5 was good. Wiped everything at least 3 times. Powered down, waited, then booted into download mode, flashed the stock OF5 tar in ODIN. Once it passed, disconnected phone from computer. Phone started going through boot process(Samsung screen, Sprint Spark screen) after that is when the "Android is upgrading..." window pops up and starts optimizing apps, but it'll only get through a few before it freezes and the phone resets.

fcramtek said:
MD5 was good. Wiped everything at least 3 times. Powered down, waited, then booted into download mode, flashed the stock OF5 tar in ODIN. Once it passed, disconnected phone from computer. Phone started going through boot process(Samsung screen, Sprint Spark screen) after that is when the "Android is upgrading..." window pops up and starts optimizing apps, but it'll only get through a few before it freezes and the phone resets.
Click to expand...
Click to collapse
PM sent. If anyone knows what works in this situation please share it; I'm on OB7 and can't recall an issue like this being resolved with confirmation...which limits ideas to theories.
Sent from my SM-N910P using Tapatalk

Related

Soft Brick!!!! Please Help

(ADDED $20 BOUNTY IF YOU HELP ME, WILL PAYPAL YOU WITHIN 24 HOURS)
Hey guys,
I've been flashing ROMS for years and this is my first real issue.
I tried to upgrade from an earlier version of CM10 to the newest one. After I flashed GAPPS this caused the phone to get stuck on reboot so I went back to CWM recovery.
ALL MY DOWNLOADED FILES WERE GONE IN CWM. Including all the roms I had, and my NANDROID backup (which I would have just reflashed right there).
I tried to Odin back to stock and it passes but gets stuck on the Samsung boot logo every time.
I've tried to scour threads on XDA and on Google. The closest thing I found was a thread where it mentioned I'd need Tmobile Bootchain commands but I can't find those either.
All help is greatly appreciated.
Have you tried to Odin using a different computer.. or redownload Odin and the files needed
Sent from my SGH-T999 using xda premium
Odin the stock firmware you mean from a different comp? I don't think that is the issue since Odin shows that the flash was successful. The phone reboots itself and it gets passed the Samsung Galaxy S3 screen to the Tmobile Android 4g boot animation.
Additionally, people in the Verizon S3 forum are describing my issue exactly here (http://forum.xda-developers.com/showthread.php?t=1840030)
SeanFloyd said:
(ADDED $20 BOUNTY IF YOU HELP ME, WILL PAYPAL YOU WITHIN 24 HOURS)
Hey guys,
I've been flashing ROMS for years and this is my first real issue.
I tried to upgrade from an earlier version of CM10 to the newest one. After I flashed GAPPS this caused the phone to get stuck on reboot so I went back to CWM recovery.
ALL MY DOWNLOADED FILES WERE GONE IN CWM. Including all the roms I had, and my NANDROID backup (which I would have just reflashed right there).
I tried to Odin back to stock and it passes but gets stuck on the Samsung boot logo every time.
I've tried to scour threads on XDA and on Google. The closest thing I found was a thread where it mentioned I'd need Tmobile Bootchain commands but I can't find those either.
All help is greatly appreciated.
Click to expand...
Click to collapse
After a successful odin flash boot into stock recovery manually and select wipe data, factory reset, then wipe cache partition. Reboot, bingo.
Sent from my SGH-T999V using xda premium
neysito said:
After a successful odin flash boot into stock recovery manually and select wipe data, factory reset, then wipe cache partition. Reboot, bingo.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
I can't get into stock recovery man, or any kind of recovery.Holding vol up + home + power hangs permanently after the SGS 3 boot screen, nothing happens.
Go to Doc's stickie and I think it is in the 2nd post, there is an Odin flashable version of TWRP (maybe a copy of CWR but since I don't use it I'm not sure).
Flash that and let it "try" and reboot. It won't but you can do the key combo to get into TWRP recovery and either flash a ROM, Restore or at the very least Factory Reset, which would be my first choice.
Somewhere back there in your efforts, I think you may have erased your internal and if that is where your backups were kept then that might be why they are gone. Just a thought though.
In odin, uncheck auto reboot. Flash the recovery tar in pda spot. When it says pass, pull the battery and boot into recovery with volume up, home, and power. Release the power button when u feel the vibrate. Then thank mrmako777 for teaching me this tonight
Click to expand...
Click to collapse
You are the mf'in man. This is what fixed my phone. Give me your email so I can paypal you $20.
To anyone who can't get into recovery if you mess up your phone with the wrong GAPPS, this method is the only thing that worked for me.
SeanFloyd said:
To anyone who can't get into recovery if you mess up your phone with the wrong GAPPS, this method is the only thing that worked for me.
Click to expand...
Click to collapse
Glad you had it all worked out.
This is exactly what was suggested to you before, since you said in your OP you had already odin back to stock. What I don't get is how come you were not able to boot into original recovery when it was just going on a boot loop. It doesn't matter. At least you fixed it. Enjoy
Sent from my SGH-T999V using xda premium
neysito said:
Glad you had it all worked out.
This is exactly what was suggested to you before, since you said in your OP you had already odin back to stock. What I don't get is how come you were not able to boot into original recovery when it was just going on a boot loop. It doesn't matter. At least you fixed it. Enjoy
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
My bad man, I quoted the wrong reply. Here is what fixed it.
GalaxyS3Guy said:
In odin, uncheck auto reboot. Flash the recovery tar in pda spot. When it says pass, pull the battery and boot into recovery with volume up, home, and power. Release the power button when u feel the vibrate. Then thank mrmako777 for teaching me this tonight
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse

Failed Root Attempt On Previously Unrooted I317UCALK7 - Bricked?

I wanted to try an AKOP ROM or two on my completely stock, never rooted Note 2 running the OTA UCALK7 update. I followed the guide here (flash the SU injected stock UCALJ2 image) to root and now my note gets stuck at the Samsung logo. I have tried the following:
Downloaded the completely stock UCALJ2 unrooted image and flashed via ODIN.
Tried flashing both stock and rooted ROMs on another computer using the stock USB cable.
Flashed CWM touch via ODIN after flashing rooted UCALJ2 image, it can boot to CWM but fails miserably most likely to the lack of root.
My guess is it's bricked because sammy closed the root hole in the UCALK7 update and flashing back to rooted UCALJ2 isn't enough to bypass the patched exploit. Is there an ODIN flashable complete UCALK7 image that I can try (I've looked to no end, all I can find are rooted zips flashable via CWM) or am I really up the creek?
Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.
shakabra said:
Pull the battery.
Hold the Center Home Button + Vol Down + Power
Slide the battery in.
If you do this right you can get into odin before the Samsung logo. I just had the same problem because I flashed the wrong recovery. It worked for me.
Click to expand...
Click to collapse
Thanks but I can get into Odin and flash the stock ROM just fine. It then reboots and gets stuck at the Samsung logo.
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
The three finger salute lol:thumbup:
Sent from my GT-N7105 using Tapatalk 2
twanskys204 said:
Once upon flash completely stock threw Odin.... do the three finger salute, go into stock recovery and factory reset... done
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks - I actually figured that part out since my second post. The phone boots after the factory reset however I don't get phone/data service. I've since tried flashing the two AT&T modems I could find, atti317ucalj2modemfixed.zip and ATT K7 Modem - Baseband.zip. Neither resolve the issue.
Cheack ur apn
Sent from my SGH-I317 using xda premium
twanskys204 said:
Cheack ur apn
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Thanks but I can't even enter the network configuration settings - it tells me to insert a SIM. My SIM is in the phone.
I'm having other problems too which I think are partition related. Apps are acting funny, saying there isn't space on the phone (dropbox can't download anything, etc). I'm trying to get TriangleAway installed so I can just RMA it but I can't even download it to my phone. Also a CWM fix permissions fails even though I grant it root access.
It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium
twanskys204 said:
It's really simple..download firmware from Sammobile.com flash it in Odin.. u might get stuck on the Samsung screen, if that happens factory reset. Make sure your downloading right file...u r now messing with Odin and it doesn't forgive
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
I know what you're saying, I'm definitely using the right file and process. I'm a pretty seasoned veteran when it comes to rooting/odin/RSD/fastboot, etc. I've run custom ROMs on dozens of phones since the G1. What's happening to me is apparently not a common failure with the note 2 or GS3. Is there a PIT file available for the AT&T Note 2? I see one for the Verizon Note 2 but I wouldn't dare try to flash that.
There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium
twanskys204 said:
There is a pit file around but I really don't think it's that.
And also just checking don't mean to insult ur intelligence but if u are using Odin it will be a .tar, if it's a recovery its I .zip
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Yeah, it's a tar file I'm flashing through Odin, got it from SamsungUpdates: Samsung-Updates.com-SGH-I317_ATT_1_20121005095854_bpaaavv07o.
I also tried flashing the stock ROM in deodex'd zip form after I got a custom recovery on there, still no dice. The non-functioning modem and lack of proper root/storage affects both Sammy and CM/AKOP based ROMs. I don't know about the modem part but I've seen weird things like this when the NAND starts going bad and things written to it don't "stick." I don't think that's the case here since it's only on its 4th or 5th flash. More than likely the latter problem is a file system issue. I have no idea about the radio.
I'm going to try and exchange it tomorrow. At least I got the flash count cleared and I'm back on a stock ROM (with the same problems).

Flashed Stock, Phone still thinks I'm on a Custom Rom

So I downloaded the stock firmware for my phone to flash via Odin, (The Samsung GS4 M919V), and I just noticed that the phone still thinks i'm on modified software. Is there anyway to fix this? I want to be 100% on stock so I can receive OTA updates...
Have you tried Triangle Away from the market? https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
KaneHusky said:
Have you tried Triangle Away from the market? https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway
Click to expand...
Click to collapse
I'm not longer rooted. I don't see why the flash counter would make my device "modified". On my S3 I had a huge flash counter and when I'd flash stock I was able to install OTA's.
Mateoftw said:
So I downloaded the stock firmware for my phone to flash via Odin, (The Samsung GS4 M919V), and I just noticed that the phone still thinks i'm on modified software. Is there anyway to fix this? I want to be 100% on stock so I can receive OTA updates...
Click to expand...
Click to collapse
Do you by any chance have a microSd card plugged in? I'd recommend you take it out, reboot and see if you still get the same message. Also delete any rom, root files you may have on your Internal & external SD.
Sent from my SGH-M919V using Tapatalk 4 Beta
dj_aj said:
Do you by any chance have a microSd card plugged in? I'd recommend you take it out, reboot and see if you still get the same message. Also delete any rom, root files you may have on your Internal & external SD.
Sent from my SGH-M919V using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried that and it didn't have any effect :/
Bump
Sent from my SGH-M919V using Tapatalk 4 Beta
Did you perform a factory reset? You have to, to get it to say official again.
Mateoftw said:
Bump
Sent from my SGH-M919V using Tapatalk 4 Beta
Click to expand...
Click to collapse
You must use triangle away. It is the only way to reset everything to factory standards.
Sent from my SGH-M919 using Tapatalk 2
stevessvt said:
Did you perform a factory reset? You have to, to get it to say official again.
Click to expand...
Click to collapse
By flashing stock it's assumed that it's also a factory reset. None the less I just factory reseeted the phone and it didn't do anything. In order to use Triangle Away, I need to be rooted, which I am not.
Mateoftw said:
By flashing stock it's assumed that it's also a factory reset. None the less I just factory reseeted the phone and it didn't do anything. In order to use Triangle Away, I need to be rooted, which I am not.
Click to expand...
Click to collapse
Which stock file did you flash? There was a "return to stock" file floating around, but it was made from a system dump and not an official ROM.
Mateoftw said:
By flashing stock it's assumed that it's also a factory reset. None the less I just factory reseeted the phone and it didn't do anything. In order to use Triangle Away, I need to be rooted, which I am not.
Click to expand...
Click to collapse
Okay so root your device by flashing cwm through Odin the flash supersure zip and boom you got root. Now run triangle away
Sent from my SGH-M919 using Tapatalk 2
Or chainfire auto root...then use triangle away, while still in triangle away have it reboot back in to bootloader mode, odin stock again, after it reboots perform another factory reset.
Done.
Mateoftw said:
So I downloaded the stock firmware for my phone to flash via Odin, (The Samsung GS4 M919V), and I just noticed that the phone still thinks i'm on modified software. Is there anyway to fix this? I want to be 100% on stock so I can receive OTA updates...
Click to expand...
Click to collapse
Get Triangle Away and use CF-Auto-Root to root but leave you with stock. Reset the flash counter and use the workaround which delays loading superuser on each startup. That makes your phone report "official". Then factory wipe.
Sent from my GT-P7510 using xda app-developers app
Yeah, I was wondering the same thing. The file floating around is 2.4gb~ file (uncompressed), but its failing for me. I downloaded it twice and attempted from 2 different computers. Also, is there a Triangles Away compatible with the S4.
Sorry for the n00b questions. i just moved to S4. I was on S3 and a land where everything just worked
Toleraen said:
Which stock file did you flash? There was a "return to stock" file floating around, but it was made from a system dump and not an official ROM.
Click to expand...
Click to collapse
electroyo said:
Yeah, I was wondering the same thing. The file floating around is 2.4gb~ file (uncompressed), but its failing for me. I downloaded it twice and attempted from 2 different computers. Also, is there a Triangles Away compatible with the S4.
Sorry for the n00b questions. i just moved to S4. I was on S3 and a land where everything just worked
Click to expand...
Click to collapse
Nothing you flash will reset you back to an official status. You MUST use triangle away. Period.
electroyo said:
Yeah, I was wondering the same thing. The file floating around is 2.4gb~ file (uncompressed), but its failing for me. I downloaded it twice and attempted from 2 different computers. Also, is there a Triangles Away compatible with the S4.
Sorry for the n00b questions. i just moved to S4. I was on S3 and a land where everything just worked
Click to expand...
Click to collapse
Try this if you haven't already. Use the 'UVUAMDL official' tar and make sure to MD5 the file after downloading.
Toleraen said:
Try this if you haven't already. Use the 'UVUAMDL official' tar and make sure to MD5 the file after downloading.
Click to expand...
Click to collapse
This is a great tutorial, however, just following this tutorial alone, will restore you to stock with a CUSTOM bootloader status.
Use triangle away to reset the flash counter, once triangle away is finished, it will ask if you wish to reboot to system, or reboot to download mode. Select download mode, then follow that tutorial.
I don't know what I'm doing wrong. I put my S4 in download mode checked the md5 of the suggested tar file but it failed again
Him rlandtst
I was able to flash the original original tar file just fine. So I know its not my phone. Maybe I need to wait till the Nexus ROM on the 26th. Can't even get the baseband up
electroyo said:
I don't know what I'm doing wrong. I put my S4 in download mode checked the md5 of the suggested tar file but it failed again
Click to expand...
Click to collapse
Reboot phone back into download mode and try again. They fail for unknown reasons from time to time. Also make sure you're connected directly to the USB port and not a hub.
Sent from my SGH-M919 using Tapatalk 2

[Q] NEED Help!!! Continual rebooting...

I've been on XDA for sometime but this has me frustrated. My note 3 keeps rebooting over and over. It will show the Note III screen then the Samsung screen and then the white with pink T-Mobile screen. After several seconds...it starts to reboot this same manner over and over. Every once and a while it will boot up to lock screen. When I swipe the screen it says that the system is not responding. It asked me do I want to wait or cancel. Eventually it just reboots and starts the process over and over. I have tried odin maybe 50 times. Tried kies. It will load the odin tar stock rom and say successful but the rebooting just starts again. I've tried a stock kernel and I tried the green compusion kernel. Please, if you have the knowledge to help, I would be very grateful. I've flashed roms and odined bricked devices for years...but this one has me stuck....Thanks ahead of time. It will go into download mode fine. It will go into recovery fine as well.
I have read the other threads and post similar to this one but they haven't help up to this point and do not seem ti be active anymore.
BACARDILIMON said:
What where you loading when phone went bad
NOTE 3
Click to expand...
Click to collapse
I was on Darthstalker and was flashing Jedi Elite. I may have in the process also tried to restore a backup with efs. But...the problem was already occurring.
teknowiz23 said:
so i take it since you have flashed odin back to stock, you are getting stock recovery menu and not twrp or cwm right?
Click to expand...
Click to collapse
I'm on stock recovery right now nut I have and can odin twrp easily. Yes I have backups but they don't load correctly either.
brojoe11 said:
I'm on stock recovery right now nut I have and can odin twrp easily. Yes I have backups but they don't load correctly either.
Click to expand...
Click to collapse
k, when you odin back to stock are you using AP and CSC or just AP?
**and, are you using the stock tmo firmware off of sammy website or one for the root?
brojoe11 said:
I'm on stock recovery right now nut I have and can odin twrp easily. Yes I have backups but they don't load correctly either.
Click to expand...
Click to collapse
Have you tried the complete restore function in Kies? Where you have to enter your Model & Serial number?
Using the stock downloaded from sammobile. And I have tried kies restor with the model and sn. It load perfectly on the phone just like odin but when the phone starts to boot up....it bootloops.
I just load the md5 file in PDA and hit start.
brojoe11 said:
Using the stock downloaded from sammobile. And I have tried kies restor with the model and sn. It load perfectly on the phone just like odin but when the phone starts to boot up....it bootloops.
I just load the md5 file in PDA and hit start.
Click to expand...
Click to collapse
okay, have you tried using the AP and CSC in the de la vega root method instead? i would try that if you haven't.
** for your comvenience
http://forum.xda-developers.com/showthread.php?t=2484223
if you can't get CSC and AP availability in odin,
close odin
open odin.ini
change csc and ap to =1 under {ButtonOption]
reopen odin and flash AP and CSC
teknowiz23 said:
okay, have you tried using the AP and CSC in the de la vega root method instead? i would try that if you haven't.
** for your comvenience
http://forum.xda-developers.com/showthread.php?t=2484223
Click to expand...
Click to collapse
I'll sure give it a shot. Thanks.
brojoe11 said:
I'll sure give it a shot. Thanks.
Click to expand...
Click to collapse
good luck man, that's the situation we all slightly fear in the very depths of our mind when we are flashing.. that sucks. half the fun though lol..
teknowiz23 said:
good luck man, that's the situation we all slightly fear in the very depths of our mind when we are flashing.. that sucks. half the fun though lol..
Click to expand...
Click to collapse
Fun once you get your heart settled back in your chest, realizing you may have just made a fancy paperweight.
Did you also try the steps here in post # 2?
http://forum.xda-developers.com/showthread.php?t=2467001
chstewart said:
Fun once you get your heart settled back in your chest, realizing you may have just made a fancy paperweight
Click to expand...
Click to collapse
wouldn't know, hasn't happened to me yet. if there's one thing i've noticed with this stuff, is that it is very rare to permanently (although slightly possible via software/software-hardware conflicts) to brick a device unless you do something really stupid. i'm fairly confident that joe will get this working.
Thanks for all the confidence and the humor as well. Yeah, I've come close to bricking several devices. But usually with some great insight and help....they are "usually" restorable . Thanks guys. I'm downloading root de la vega files now...soon we shall see....
Thanks for the twrp thread link. I've flashed twrp several times...no problem..the problem is when the rom starts to load it just loops and loops and...
well...tried it...it loaded. came to tmobile screen then began looping again...unbelieveable....
brojoe11 said:
well...tried it...it loaded. came to tmobile screen then began looping again...unbelieveable....
Click to expand...
Click to collapse
Reboot into stock recovery and wipe data and cache. That's power, home and volume up button to get into recovery.
Sent from my SM-N900T using XDA Premium 4 mobile app
gforceriders said:
Reboot into stock recovery and wipe data and cache. That's power, home and volume up button to get into recovery.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
try twrp and restore previously working system or boot partition. i'd only try one at a time.
OOOOOORRRRRR
try reflashing stock kernel then wiping cache, dalvik, fix permissions.
if that don't work try a custom kernel then wipe cache, dalvik, and fix permissions.
i think you are one step closer.
Message came up and said "process system isn't responding" and then looped again....any more ideas?
brojoe11 said:
Message came up and said "process system isn't responding" and then looped again....any more ideas?
Click to expand...
Click to collapse
k. restore a previously working system partition. preferably one from a stock rooted but whatever rom system should be worth a try.
brojoe11 said:
Message came up and said "process system isn't responding" and then looped again....any more ideas?
Click to expand...
Click to collapse
I am telling you this happen to me. Just run Odin back to stock and reboot into recovery after and wipe data and cache. Even if your phone doesn't seem to go into download mode still run odin.
Sent from my SM-N900T using XDA Premium 4 mobile app
gforceriders said:
I am telling you this happen to me. Just run Odin back to stock and reboot into recovery after and wipe data and cache. Even if your phone doesn't seem to go into download mode still run odin.
Sent from my SM-N900T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You let it totally boot. then go into recovery and wipe data and cache right?
I restored system and then boot from a stock rooted backup. Still didn't work...So, I'll try the odin with stock and wipe data and cache...thanks guys. Maybe one of these will work.
brojoe11 said:
You let it totally boot. then go into recovery and wipe data and cache right?
I restored system and then boot from a stock rooted backup. Still didn't work...So, I'll try the odin with stock and wipe data and cache...thanks guys. Maybe one of these will work.
Click to expand...
Click to collapse
No when you odin you should still have the boot loop. Then you can do a battery pull and reboot into stock recovery and wipe data and cache.
Sent from my SM-N900T using XDA Premium 4 mobile app

Stuck in brickloop, Tried odin stock firmware, no go

Hello all!
So I bought a SGH M919 s4 off craigslist for 150 knowing that it wouldn't boot past the Samsung galaxy s4 boot screen, Thinking it would be an easy fix by flashing the stock firmware through odin. Well that's not the case, I've tried just about everything I am capable of...
1.Both odin 3.0 7 and odin 3.0 9 both flash and the device passes but on the boot screen it says booting recovery and just sticks there, It stuck on that over night so I am being patient.
2. I've tried flashing 4.3 which fails right away leading me to believe the phone was updated to 4.4.2 at some point in time.
3. It wont let me boot into stock recovery or I've even tried flashing TWRP, CWM and it pass's but still will not let me boot into those recovery's either.
4. Tried rooting the phone a couple times and that passes in odin but does nothing after that.
5. I ve tried different phone cables, I haven't tried a different computer yet.
6. The only thing I can get into on the phone is download mode and it says this on the screen
ODIN MODE
PRODUCT NAME: SGH-M919
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0X0
KNOX WARRANTYVOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: enable
eMMC BURST MODE enable
I don't remember seeing those last two things on the list normally if I can recall. Any help will be greatly appreciated and possibly a donation if we can get this thing fixed. Thanks.
Repartition it with the pit file while youre installing the firmware.
Last 2 strings are normal.
Sent from my SGH-M919 using XDA Premium 4 mobile app
ShinySide said:
Repartition it with the pit file while youre installing the firmware.
Last 2 strings are normal.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, Do you know where the pit file can be found or what do I write in the pit file box?
Ok so I pulled the pit file from another T-Mobile s4 I have and flashed that with the stock firmware and that didn't work. The phone I pulled the pit file from is on 4.3 still so I'm assuming that's why it didn't work???
Quickvic30 said:
Ok so I pulled the pit file from another T-Mobile s4 I have and flashed that with the stock firmware and that didn't work. The phone I pulled the pit file from is on 4.3 still so I'm assuming that's why it didn't work???
Click to expand...
Click to collapse
Na that wouldnt matter. Your pit file is for your partition layouts. Which dont ever change.
I really cant think of anything else of why you can't get into recovery or boot the phone with everything you've tried. You might just need to Jtag the device
Sent from my SGH-M919 using XDA Premium 4 mobile app
ShinySide said:
Na that wouldnt matter. Your pit file is for your partition layouts. Which dont ever change.
I really cant think of anything else of why you can't get into recovery or boot the phone with everything you've tried. You might just need to Jtag the device
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help, I might jtag it or just try to find a used motherboard :laugh:
Quickvic30 said:
Thanks for the help, I might jtag it or just try to find a used motherboard :laugh:
Click to expand...
Click to collapse
The OP mentions that you tried flashing 4.3 and you speculated if it had been updated to 4.4.2. Just out of curiosity, have you tried flashing the stock 4.4.2 firmware?
lordcheeto03 said:
The OP mentions that you tried flashing 4.3 and you speculated if it had been updated to 4.4.2. Just out of curiosity, have you tried flashing the stock 4.4.2 firmware?
Click to expand...
Click to collapse
Yes I've been to flashing 4.4.2 and it passes Odin. I think maybe you meant have I tried flashing 4.2.2? I have not tried flashing 4.2.2 firmware yet, I might try that but 4.2.2 didn't have the Knox counter did it?
Sent from my SM-G900A using XDA Free mobile app
Quickvic30 said:
Yes I've been to flashing 4.4.2 and it passes Odin. I think maybe you meant have I tried flashing 4.2.2? I have not tried flashing 4.2.2 firmware yet, I might try that but 4.2.2 didn't have the Knox counter did it?
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
No, I meant 4.4.2. It was a dumb question, but sometimes it's the simple things you overlook. Like I said, the OP only said you tried flashing MK2. You won't be able to flash anything pre-KNOX so there's no need in wasting the time downloading the MDL firmware.
An idea would be to power the phone off, boot straight to download mode, flash NB4, pull the battery when it's complete, boot straight back to download mode and re-flash NB4. I know that you have to do that sometimes for the modem to stick, perhaps you could try that with the firmware itself. Hey, worth a shot. Good luck.
lordcheeto03 said:
No, I meant 4.4.2. It was a dumb question, but sometimes it's the simple things you overlook. Like I said, the OP only said you tried flashing MK2. You won't be able to flash anything pre-KNOX so there's no need in wasting the time downloading the MDL firmware.
An idea would be to power the phone off, boot straight to download mode, flash NB4, pull the battery when it's complete, boot straight back to download mode and re-flash NB4. I know that you have to do that sometimes for the modem to stick, perhaps you could try that with the firmware itself. Hey, worth a shot. Good luck.
Click to expand...
Click to collapse
I think I might have tried flashing twice in a row but I'll try it again since I haven't tried that since I've flashed the pit file. Thanks for the tip and I'll report back after the double flash.
Sent from my SM-G900A using XDA Free mobile app
So I flashed it, pulled the battery and flashed it again and still the same thing......:sigh: lol Time to look for another wrecked phone for spare parts
Bought a phone off cl with a cracked screen and swapped the motherboard into the phone and it works like a champ now! :thumbup:
Sent from my SM-G900A using XDA Free mobile app

Categories

Resources