Related
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not be able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
altae said:
Guys I still don't believe it but I did very well this evening I just managed to brick my device by copying some avi and wmv files from the external SD-Card to my internal storage. How did I do that? I have no f...... clue. The phone froze, I waited almost half an hour but nothing happened. So I finally decided to pull the battery and restart the phone. And what did I get? I phone nicely stuck at the boot logo. Ok I thought, no biggie. Let's try to clean cache and dalvik cache, this action had helped in the past when the phone had been stuck at the boot logo. But no, it did not help at all. Then I thought ok, before I restore my nand backup I can still try to reflash the kernel. And I think that killed my phone. After the kernel had successfully been flashed (according to the log in CWM) I tried to reboot but nothing worked anymore. I could not even boot into CWM recovery. Hm, that's not good but now I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash. So bang, there it is, my own full brick. Huray. Off to the service center I go. At least I always paid attention not to increase the flash counter/ trigger the red triangle. So since the phone is completely dead I am optimistic that they should not able to proof that my phone was rooted (fingers crossed).
In case you are interested, my rom was LRQ, my kernel was the latest version of the PhilZ kerne with it's touch recovery.
Click to expand...
Click to collapse
I have never considered the "hex-patched" kernels to be safe...
jeriz said:
did you check to see if the drivers on the computer are properly installed? I'm tinking it might be a case of pc not finding the phone.
or maybe you had some bad blocks since the days of unsafe kernels
Click to expand...
Click to collapse
Yep. I don't think the drivers are the problem since the phone is recognized. But it does not start to flash. It simply does nothing and the phone stays in download mode forever.
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
this in itself is a huge statement
altae said:
I could still try reflashing the rom using pc odin because the download mode still worked (in fact it still works). But it does absolutely nothing. It does not even start to flash.
Click to expand...
Click to collapse
This is diferent... not even start to flash...
Sent from my GT-P3110 using Tapatalk 2
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
It seems that remaining on Gingerbread (until official JB) for the moment is the best thing for people who do not have a warranty for their Note.
Many people confuse superbrick (phone dead right away, no life even if you plug a charger) and other bricks. This is just an unfortunate other brick not related in any way to emmc described one. Good luck at RMA
Also, copying big video to your sdcard is a good way to kill it. Old i9000 thread was popular with that
Sent from my GT-I9100 using Tapatalk 2
Was running Paranoid Android
Tried to restore the Note back to the latest UK stock ICS ROM via ODIN
Forgot to wipe/davlik before hand
then got stuck in boot loop
more boot loops
Then tried flashing a rooted GB rom in ODIN
stuck now on the Samsung Note boot screen occasionally looping.
Then tried flashing an original non-rooted GB rom in Odin
got stuck on Data.img
Then tried again and it stuck on FACTORYFS wont even get passed this.
Took battery out, then back in...
Now the screen shows three images and the message
firmware upgrade encountered an issue
Now with the Samsung Repair centre in Eastbourne and they are failing to be able to do anything...they still have my NOTE:crying:
Entropy512 said:
I have never considered the "hex-patched" kernels to be safe...
Click to expand...
Click to collapse
Sure, you can theorically miss the binary check in rare circumstances. But this is just "an other brick" without any common relation typical to described emmc brick: no wipe, no flash, and mainly no right away (or even) complete dead phone
Sent from my GT-I9100 using Tapatalk 2
@ Entropy. Even guy above Phil3759 his bricked his note starting from PA which has a "safe" kernel, and eventually superbricking just useing PC Odin (long time considered safe). No wipes involved. Anyway, is Tungstwenty's detection method flawed for stock ICS kernels? Or is there are problem changing the offending byte from a 1 to a zero
Sent from my GT-N7000 using xda app-developers app
At least this brick has made me decide to leave my note well alone, after flashing roms practically daily for the last month or so, I have become insanely addicted to changing roms...once i get the Note back from the Sammy Service place, I am sticking with stock and wait till the official JB update arrives, which looks fantastic.
As it states on all these roms flashing custom roms at your own risk, thus its my own fault, finger crossed it can be sorted.
You can brick any phone, it happens, yes. Superbrick related to emmc bug occurs under special circumstances with typical symptoms.
Binary patching kernels, in theory, if you happen to have duplicate binary code or different, you could miss it. But, as far as i know, and for all manual checks i did, it never happened...
Sent from my GT-I9100 using Tapatalk 2
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Markuzy said:
Since this is not the usual EMMC brick, what is the diagnosis? Just so it can be prevented/avoided in the future
Sent from my GT-N7000 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
As i said, it is really non recommended to use your internal sdcard for regular heavy write operations like videos. It will be corrupted at a certain point. On the i9000 this used to be a way for some to get warranty. Phone stuck often after a continuous write/wipe overnight
But this is not the superbrick. And one day, all your phones will brick. That's flash storage
Sent from my GT-I9100 using Tapatalk 2
altae said:
I have no clue. And since the phone is now completely dead (even download mode does not work anymore) it's kind of hard to examine it. So I would say we will never now what exactly bricked my phone.
Click to expand...
Click to collapse
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
shoey63 said:
I have read about this before. First can't flash with PC Odin. Then recovery mode goes, then download mode and finally dead phone. Friggin' Samsung
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
If you read across HTC and other forums, you'll see so much bricks and unhappy people. Why blame Samsung, there will be always faulty devices and unhappy unfortunate people
Sent from my GT-I9100 using Tapatalk 2
Yeah, you're right. Even PC Nand causes grief. Just hoped a Company on the cutting edge of technology like Samsung would have been able to resolve such problems.
Sent from my GT-N7000 using xda app-developers app
I would better trust seagate or corsair to push it further. Samsung HDD always failed on me. Ditched them long ago
Sent from my GT-I9100 using Tapatalk 2
---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------
By the way, for people that want to know more about binary patching kernels, read here, it is worth it
http://forum.xda-developers.com/showthread.php?p=29609295
Sent from my GT-I9100 using Tapatalk 2
Hey Guys,
I am hoping someone could assist me. I have been using various roms over the past couple of months with no issues. Tonight I flashed a rom and went through the setup process. Once completing the setup it went to the install and showed 100% then rebooted. Now it is stuck in the never ending reboot.
I have attempted to wipe the cache, and dalvik cache and reboot but still nothing. I've attempted to go and reinstall the rom but the odd part is that there are no files found on my device.
I then attempted to go to my SD card due to I have all my ROM's, other than the one I was flashing, there. However, it won't recognize the SD card.
I'm sorry if this is an easy fix but I am truly not sure how to proceed.
Thanks for any help.
PC Odin Noobls MDC tar and you'll be good.. That's what I'd do. Not sure why this happened. Maybe someone else will know.. Seems as though things somehow have been wiped.. Maybe more info would help ... What recovery and version were you using? What ROM did you flash.. Maybe someone esle will know why.. All I know is Odin will more than likely get you going again and if not you can always Google J-tag service..
Sent from my Skanky Jfltespr using xda premium
flashback7 said:
PC Odin Noobls MDC tar and you'll be good.. That's what I'd do. Not sure why this happened. Maybe someone else will know.. Seems as though things somehow have been wiped.. Maybe more info would help ... What recovery and version were you using? What ROM did you flash.. Maybe someone esle will know why.. All I know is Odin will more than likely get you going again and if not you can always Google J-tag service..
Sent from my Skanky Jfltespr using xda premium
Click to expand...
Click to collapse
Thanks for the prompt response and sorry for being vague, at the moment. I just don't want to list the rom due to I don't want to possibly give the developer bad press when I think it is probably something I did. I'll keep messing with it and I also shot the developer a message so if I don't get anywhere in the next day I'll then post a little more information.
Thanks again,
Fixed
flashback7 said:
PC Odin Noobls MDC tar and you'll be good.. That's what I'd do. Not sure why this happened. Maybe someone else will know.. Seems as though things somehow have been wiped.. Maybe more info would help ... What recovery and version were you using? What ROM did you flash.. Maybe someone esle will know why.. All I know is Odin will more than likely get you going again and if not you can always Google J-tag service..
Sent from my Skanky Jfltespr using xda premium
Click to expand...
Click to collapse
Thanks again! I've always used Clockwork. Odin did the trick and all is a-ok.
Thanks for your help.
:good:
The Knox Bootloader is.... Annoying
Anyone know if I could flash the MF9 tar in ODIN and revert back to the 4.2 Bootloader
do not you will even cause bigger problems stay cool untill a tar is released they are working hard to see what they can due the only choice you have no is to go to a ROM that is 4.3 but that I know of it is still un heard of KNOX is a whole new monster that I have a feeling is gonna tick a lot of people off love love love Samsung phones but they need to realize this could hurt them....
NO.
Sent from my SPH-L720 using Tapatalk
jprocket45 said:
do not you will even cause bigger problems stay cool untill a tar is released they are working hard to see what they can due the only choice you have no is to go to a ROM that is 4.3 but that I know of it is still un heard of KNOX is a whole new monster that I have a feeling is gonna tick a lot of people off love love love Samsung phones but they need to realize this could hurt them....
Click to expand...
Click to collapse
Thanks for the reply. If I had known that KNOX was gonna be such a problem I would of held off from upgrading...
Guess I gotta be patient until our beautiful dev community comes up with some way to deal with KNOX
Robin Dhicke said:
Thanks for the reply. If I had known that KNOX was gonna be such a problem I would of held off from upgrading...
Guess I gotta be patient until our beautiful dev community comes up with some way to deal with KNOX
Click to expand...
Click to collapse
so there is no way to go back to MDC then huh? -/-
kalanir said:
so there is no way to go back to MDC then huh? -/-
Click to expand...
Click to collapse
Well not yet.
Sent from my SPH-L720 using xda app-developers app
nope stuck just like the rest of us lol its not fun
Don't worry......it's only a matter of time. If u need a stable rom, I highly recommend sac23's custom 4.3 rom. V3 will be out soon. This rom has made it easier to cope with 4.3, well easier for us who are stuck with the Knox......check out his thread. You'll love it.
Sent from my SPH-L720 using XDA Premium 4 mobile app
I'm not sure what any of you are talking about. I updated to 4.3 a couple of days ago, then wiped and flashed a MDC tar with ODIN and brought it back to MF9 with OTA updates. Everything is fine.
---------- Post added at 12:15 AM ---------- Previous post was at 12:14 AM ----------
Robin Dhicke said:
The Knox Bootloader is.... Annoying
Anyone know if I could flash the MF9 tar in ODIN and revert back to the 4.2 Bootloader
Click to expand...
Click to collapse
Yes... You can do this. I did it. See my last post above.
Sleepycloud said:
I'm not sure what any of you are talking about. I updated to 4.3 a couple of days ago, then wiped and flashed a MDC tar with ODIN and brought it back to MF9 with OTA updates. Everything is fine.
---------- Post added at 12:15 AM ---------- Previous post was at 12:14 AM ----------
Yes... You can do this. I did it. See my last post above.
Click to expand...
Click to collapse
Hello,
How did you manage to do it?
I tried to do that with Odin 1.85 and 3.07 and nothing. It aborts right away.
edgardch said:
Hello,
How did you manage to do it?
I tried to do that with Odin 1.85 and 3.07 and nothing. It aborts right away.
Click to expand...
Click to collapse
I wiped everything in TWRP, and rebooted into download mode. Then flashed the tar with 3.07 and a PIT file. Uncheck reboot. Check Repartitition, Nand erase, and F. Reset Time. When it reboots it wiil update in recovery with the little andy dude, and then reboot to load up. I pull the battery and factory reset. It works fine. I updated to 4.3 friday morning. and decided to go back to MF9 so that I could use The HotSpot Mod and Reboot Menu. F**k 4.3...it was disapointing.
EDIT-----> READ ALL OF THE FOLLOW-UP POSTS BEFORE YOU TRY THIS.... MY PHONE HAD A UNIQUE SITUATION AND THIS WILL NOT WORK FOR MOST EVERYONE ELSE.
Sleepycloud said:
I wiped everything in TWRP, and rebooted into download mode. Then flashed the tar with 3.07 and a PIT file. Uncheck reboot. Check Repartitition, Nand erase, and F. Reset Time. When it reboots it wiil update in recovery with the little andy dude, and then reboot to load up. I pull the battery and factory reset. It works fine. I updated to 4.3 friday morning. and decided to go back to MF9 so that I could use The HotSpot Mod and Reboot Menu. F**k 4.3...it was disapointing.
Click to expand...
Click to collapse
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
There is one problem. Now it won't update to MJA. Something is different, but I'm not sure what. I don't care if you don't believe me. I did it, and that is how I did it. There was one other issue. It kept redownloading the Sprint Default Configuration over and over and over. Like more than 50 times back to back.I finally deleted the apk to get that to stop. Outside of that, my phone works fine. I believe their are remnants of 4.3 and that is why it says the system is up to date on MF9 and does not prompt me for the 4.3 update. I really don't know, but m phone appears to be working perfectly.
Sleepycloud said:
There is one problem. Now it won't update to MJA. Something is different, but I'm not sure what. I don't care if you don't believe me. I did it, and that is how I did it. There was one other issue. It kept redownloading the Sprint Default Configuration over and over and over. I finally deleted the apk to get that to stop. Outside of that, my phone works fine.
Click to expand...
Click to collapse
As in tkaimg the OTA or trying to flash MJA ROM like Skyrockets or Sacs ?,
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
As in tkaimg the OTA or trying to flash MJA ROM like Skyrockets or Sacs ?,
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
The OTA. It doesn't recognize any update as being available anymore. It went from MDC to MDL to MF9 just fine. Then stopped. It says it's up to date now? I'm not sure what's going on with it, but I rerooted it and it works fine. I even innitialised it on KIES to set it all the way back to stock MF9 but it still won't show any update as being available for 4.3
daniel4653 said:
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I tried it just barely as I want to go back to my mf9 rom with the stock kernel. You get a secure error on pit and also a firmware revision error "fused 4 .... 1" can't remember what the word was where the dots were. It was a no go for me. I tried to odin back to mdc like was mentioned in the previous posts.
:EDIT Definitely don't try this. Caused my data partition to get corrupt. Couldn't format it. Couldn't pit restore it. Philz recovery couldn't mount it. Finally found an option to format data and sdcard. This allowed me to format data and restore. Once again Definitely don't try if you have the mja bootloader. (I'm back up and running and will let other figure this out.)
I just found out why I was able to go back to 4.2.2!!! When I updated to 4.3 via OTA a couple of days ago, I plugged it in to KIES 3 and noticed it said "PDA:MJA, Phone:MF9, CSC:MJA".... notice the phone says MF9! I don't know how that happened, but I didn't question it at the time because it was OTA. I thought it was supposed to be that way. Last night before I went to bed I manually flashed the 4.3 update zip after using KIES to initialise my phone back to complete stock. (It wouldn't load the zip when I was rooted) Anyways.... Well this morning I plugged it in to KIES 3 after flashing the 4.3 update.zip last night and it said MJA on all three. I'm not sure how that happened, but I only got part of the OTA update a couple of days ago it appears, and thus being, it is the reason I was able to revert. Sorry if I got anyones hopes up. I just went back and edited a warning in my first post with instructions.
Bummer!!! lol i was getting all excited.
wilsonwa said:
I tried it just barely as I want to go back to my mf9 rom with the stock kernel. You get a secure error on pit and also a firmware revision error "fused 4 .... 1" can't remember what the word was where the dots were. It was a no go for me. I tried to odin back to mdc like was mentioned in the previous posts.
:EDIT Definitely don't try this. Caused my data partition to get corrupt. Couldn't format it. Couldn't pit restore it. Philz recovery couldn't mount it. Finally found an option to format data and sdcard. This allowed me to format data and restore. Once again Definitely don't try if you have the mja bootloader. (I'm back up and running and will let other figure this out.)
Click to expand...
Click to collapse
I'm having the same issue that you had with the data partition being corrupt. I had stupidly tried to downgrade stock MJA to MF9 before checking with the forums if it was possible. It got stuck in the Firmware error message (can't remember what it exactly said), but got to restore it to a stock MJA. And now its data partition cannot be recognized in any computer. IE: Whenever I plug it into the computer it used to show that it is connected via USB and give me the MTP option. Now it will not even do that and I cannot access its data partition via the computer. Kies won't even recognize it.
How did you get to format data and sdcard?
EDIT: OK, dont know how, (I'm blaming crappy cable) but now I do have access to the phone. In other words it's working normal. But in case that this were to happen again, it would be awesome to know how to format data section, so as it can be recognized by the computer. Thanks in advance.
So I have had AOKP and CM being flashed back and forth for months now, but I am headed out of town tomorrow on a long trip and want the stock experience for roaming/reception/mms/etc...
I used Rwilco12's Stock Restore Automatic ODIN from here - http://www.rwilco12.com/downloads.p...H-L720)/Stock ROMs/MF9/No Data Restore/Rooted
Now when I went to download mode to run this bad boy and erase TWRP and AOKP and go back to stock, it randomly failed (not once, not twice but three times). SInce the first failed attempt it has been giving me a KIES error message about emergency firmware yadada. KIES won't recognize my phone tho, there was never any upgrades using KIES ever to my phone so I dont even have it setup and when I tried it wouldnt work.
What can I do to get any firmware working on my phone again? Right now I can access download mode and then any attempt to get into recovery/normal boot gives me that KIES error message.
PLEASE! I've got to get this fixed ASAP I'm leaving did not have time for this complication =[
Thank you in advance
dbaybay said:
So I have had AOKP and CM being flashed back and forth for months now, but I am headed out of town tomorrow on a long trip and want the stock experience for roaming/reception/mms/etc...
I used Rwilco12's Stock Restore Automatic ODIN from here - http://www.rwilco12.com/downloads.p...H-L720)/Stock ROMs/MF9/No Data Restore/Rooted
Now when I went to download mode to run this bad boy and erase TWRP and AOKP and go back to stock, it randomly failed (not once, not twice but three times). SInce the first failed attempt it has been giving me a KIES error message about emergency firmware yadada. KIES won't recognize my phone tho, there was never any upgrades using KIES ever to my phone so I dont even have it setup and when I tried it wouldnt work.
What can I do to get any firmware working on my phone again? Right now I can access download mode and then any attempt to get into recovery/normal boot gives me that KIES error message.
PLEASE! I've got to get this fixed ASAP I'm leaving did not have time for this complication =[
Thank you in advance
Click to expand...
Click to collapse
Big question?
Did you take MJA update?
If so you can ONLY get to an MJA ROM. There is a thread for that.
You're in luck If your firmware is still on MF9 check this out. Make sure to run PC Odin 'As administrator'
leaderbuilder said:
Big question?
Did you take MJA update?
If so you can ONLY get to an MJA ROM. There is a thread for that.
You're in luck If your firmware is still on MF9 check this out. Make sure to run PC Odin 'As administrator'
Click to expand...
Click to collapse
I have no taken any updates in SOOOO long, since like I got the phone I immediately put TWRP and then just been flashing ROMs. I have no clue which it is in I would have to say older than MF9 even? I'll try the MF9 one tho this reallllly sucks. I've found guides for fixing it via KIES but you need the serial number which STUPIDLY is not located on the battery backing sticker =[
Thanks for your help
I think it might have been on MDL when I switched to AOSP? Trying to find a MDL ODIN restore do you think that would work?
dbaybay said:
I have no taken any updates in SOOOO long, since like I got the phone I immediately put TWRP and then just been flashing ROMs. I have no clue which it is in I would have to say older than MF9 even? I'll try the MF9 one tho this reallllly sucks. I've found guides for fixing it via KIES but you need the serial number which STUPIDLY is not located on the battery backing sticker =[
Thanks for your help
Click to expand...
Click to collapse
Well if you don't have MJA (4.3) the mf9 method will work.
Kies blows a** in my opinion.
Things to keep in mind:
Start PC Odin as admin
put phone into Download before pluging it into PC.
Make sure you have a GOOD or BRAND NEW USB cable. [probably 20 times I've seen this be an issue too!].
If phone shows up on COM port then flash away.
First boot takes about five earth minutes. If it doesn't move past the yellow sprint bootscreen to 'update applications' after that time try a batter pull and restart. Then another five minutes. [sometimes flashing another kernel (back to downlaod mode, pc odin kernel in PDA slot) will resolve issue if batter pull didn't work after full .tar flash.
I
Kies definitely blows, I've never used it. Just since that's the only thing I can see is the KIES error message or download mode I figured I might be able to recover via KIES.
I tried a MF9 one click one nodata one no-root/deletes data, a couple times on both with two different cords and having no luck. My last shot is this MDL stock file I'm flashing via regular odin prayin it will work..
Waiting waiting waiting it's been on boot.img flashing part for ages now -_- I hope it didnt freeze.
dbaybay said:
Waiting waiting waiting it's been on boot.img flashing part for ages now -_- I hope it didnt freeze.
Click to expand...
Click to collapse
Like I mentioned (and others in the followups to my linked post) said, might have to do it a couple times or do battery pull. Maybe flash a custom kernel (KToonz etc) then try and boot.
Also you mentioned you think y were on mdc or mdl, you could grab one of those one clicks and give that a go too.
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Like I mentioned (and others in the followups to my linked post) said, might have to do it a couple times or do battery pull. Maybe flash a custom kernel (KToonz etc) then try and boot.
Also you mentioned you think y were on mdc or mdl, you could grab one of those one clicks and give that a go too.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Couldn't find a one click for MDL but I found the tar file which I'm flashing in the PDA section. Trying on my 3rd go now but it keeps freezing on the boot. I waited a good 20 minutes its just stuck there. I will keep trying, already pulled battery many times. I will look into a kernel because the one click/pda in odin is getting me no where =[
Sucks had the GS, GS2 and GS4 and never had a fail with ODIN until the one time I desperately need a freakig phone!
dbaybay said:
Couldn't find a one click for MDL but I found the tar file which I'm flashing in the PDA section. Trying on my 3rd go now but it keeps freezing on the boot. I waited a good 20 minutes its just stuck there. I will keep trying, already pulled battery many times. I will look into a kernel because the one click/pda in odin is getting me no where =[
Sucks had the GS, GS2 and GS4 and never had a fail with ODIN until the one time I desperately need a freakig phone!
Click to expand...
Click to collapse
Thought of something that saved me from taking a hammer to one of my phones. Take the battery out for at least twenty minutes to clear any residual stuff. Put it back in, boot to download mode try flashing again
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Thought of something that saved me from taking a hammer to one of my phones. Take the battery out for at least twenty minutes to clear any residual stuff. Put it back in, boot to download mode try flashing again
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Will leave it out now while I look for a kernel or MDL one click.
I just don't get it, it keeps failing when it tries to flash the boot.img part of the md5. This is just ridiculous ODIN always fixes the problem and now it just hates the **** out of me. So frustrated :crying:
OHHH UPDATE::: I just tried ODIN 3.04 after trying the three versions released since 3.04 and it made it past BOOT! It's flashing the system as I type. Fingers freaking crossed!!!
WELL! I'm getting somewhere. The ODIN was successful with 3.04 and an MDL tar file!
However I'm stuck on the yellow logo big time, took battery out after waiting 7 minutes and again when booting stuck on the yellow sprint screen. Should I try one of the MF9 one clicks again now that I'm free from the Kies error?
dbaybay said:
WELL! I'm getting somewhere. The ODIN was successful with 3.04 and an MDL tar file!
However I'm stuck on the yellow logo big time, took battery out after waiting 7 minutes and again when booting stuck on the yellow sprint screen. Should I try one of the MF9 one clicks again now that I'm free from the Kies error?
Click to expand...
Click to collapse
Two things that have helped me out. 1) upgrade the samsung drivers to the latest. Or 2) Whenever Im stuck in a bottloop or The Yellow Sprint screen after flashing to a stock rom is to go into stock recovery and do a factory reset. It usually works for me..
GS4 Stock Rooted MJA 4.3,Philz Touch CWM,HotSpot Mod,Transparent Weather Widget,8SMS(Stock Messaging,KitKat)
dbaybay said:
WELL! I'm getting somewhere. The ODIN was successful with 3.04 and an MDL tar file!
However I'm stuck on the yellow logo big time, took battery out after waiting 7 minutes and again when booting stuck on the yellow sprint screen. Should I try one of the MF9 one clicks again now that I'm free from the Kies error?
Click to expand...
Click to collapse
I would at least get to MF9. It was/is exteremely stable and usable.
leaderbuilder said:
I would at least get to MF9. It was/is exteremely stable and usable.
Click to expand...
Click to collapse
@dbaybay, pm me when you have a chance.
I recently fixed an infamous bootloop i had by letting the battery die 100% (yeah I know it is bad), and then it booted. Well i went to flash a new rom and it never rebooted. I then went to flash stock from google. Still a bootloop. tried like 3 roms, still a loop. I then tried the killing my battery thing. Still a loop. Please, i know the phone isn't hard bricked, is there anything else i can do to boot it other than just flashing stock and factory resetting. Thanks.
Another thing, when i try to flash 4.2.2 the phone doesn't go to the boot logo.
Anybody? I need to fix this phone soon.
Wrong thread sorry
YFBanana said:
Anybody? I need to fix this phone soon.
Click to expand...
Click to collapse
Fastboot flash the factory image. Then boot into the stock recovery and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Fastboot flash the factory image. Then boot into the stock recovery and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
unfortunately that doesn't work, i have tried it many times.
YFBanana said:
unfortunately that doesn't work, i have tried it many times.
Click to expand...
Click to collapse
Then you have an issue with your device. What happens if you lock the bootloader and then reboot? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Then you have an issue with your device. What happens if you lock the bootloader and then reboot? Does it stay locked or is it still unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It stays locked. I am guessing thats a good thing?
YFBanana said:
It stays locked. I am guessing thats a good thing?
Click to expand...
Click to collapse
Yep, if it didn't your emmc flash memory would be bad. I'd try re-downloading the factory image and trying again. Are you using the flash-all.bat to flash? You might try flashing all the components separately and see if any of them fail.
Sent from my Nexus 5 using XDA Free mobile app
You flashed stock firmware and it didn't work? What did it do when you flashed it?
Sent from my Moto G running Carbon ROM 4.4.4
jd1639 said:
Yep, if it didn't your emmc flash memory would be bad. I'd try re-downloading the factory image and trying again. Are you using the flash-all.bat to flash? You might try flashing all the components separately and see if any of them fail.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
None of the flashes failed. I have tried redownloading and i have also checked the md5's, so i dont think that would be it. I have also tried reformatting through twrp, and then flashing stock. Still nothing.
flashing 4.4.4 separately got me on the starting apps step, but that seems to be the place where it gets stuck.
I need to decide if i wanna take another month trying to fix the nexus 4 or just get the nexus 5. Nothing is working and i think i should just leave it now. But at the same time, i just wanna fix it so i don't have to spend money on a new phone. I have run out of things to try and revive the phone so i don't know what to do anymore.
YFBanana said:
I need to decide if i wanna take another month trying to fix the nexus 4 or just get the nexus 5. Nothing is working and i think i should just leave it now. But at the same time, i just wanna fix it so i don't have to spend money on a new phone. I have run out of things to try and revive the phone so i don't know what to do anymore.
Click to expand...
Click to collapse
so now you can boot to 4.4.4 ROM but your phone stuck at the "Starting apps" box rite?
groovepeppy said:
so now you can boot to the ROM? but never pass the "Starting apps"?
Click to expand...
Click to collapse
I think it was just the order i flashed the img files that made it go to that point, but i am pretty sure starting apps is where it gets stuck every time.
YFBanana said:
I think it was just the order i flashed the img files that made it go to that point, but i am pretty sure starting apps is where it gets stuck every time.
Click to expand...
Click to collapse
You can fastboot your phone i believe, you should try [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Start from point C
I hope you haven't tried it yet
groovepeppy said:
You can fastboot your phone i believe, you should try [HOW-TO] How to flash a factory image / return to stock / unlock / root #
Start from point C
I hope you haven't tried it yet
Click to expand...
Click to collapse
I have tried it. Still no boot.
YFBanana said:
I have tried it. Still no boot.
Click to expand...
Click to collapse
there's must be a way cause you can boot on 4.4.4 but unfortunately i'm not that good in these kind of problems
but i hope you can find the cure soon
You can obviously get into flashboot, have you tried booting the latest twrp, wiping /system /data /cache and sideloading something different, like Paranoid Android?
Bootloop fix
First thing is that you have use Wug's Tool and flash the 4.3 stock image. In the Wug's tool select the option 'SOFT BRICK or BOOTLOOP' option and then flash the stock image in the fastboot mode. Definitely, I hope the phone will launch without any problem. The same problem I had faced with my nexus 4 and I flash the 4.3 stock image with the help of Wug's tool. Try it I hope it will fix the problem.