My Note 3 was bricked in the process of rooting. I can get to the Downloading screen on my phone, but I always get a "Failed" Message on Odin after NAND files are being written. The blue progress bar never goes past 10%. Any help would be awesome as I need to use this phone tomorrow! Many thanks!
Go here http://forum.xda-developers.com/showthread.php?t=2630669 this fixed it for the same situation as yours. Go into recovery mode as explained in the post and clear cache and then factory reset. If that doesn't work you will need to Odin back to stock. You will most likely have to use Vroot to root your phone.
Related
I have a Samsung Galaxy S4, the Sprint version. I wasn't able to send or receive picture messages and I thought it might have something to do with my APN being wrong (I bought the phone on eBay and had it flashed to nTelos, my provider) but I wasn't able to edit the APN and nTelos was, as usual, no help. So I figured I'd just root it and be able to edit it then!
It was at that moment I stuck my shovel into the soft dirt and started digging.
Essentially, I believe my phone is without an OS at this point. I have tried using ODIN to put a recovery on there so I can at least do something, but now even ODIN is freezing up when I try and flash the Clockwork recovery. I am stuck on the Samsung S4 logo screen and while I can enter download mode I don't think I can enter recovery mode - at least, it hasn't been working tonight. I don't remember everything I've done to my poor phone, but it has to be hurting after the beating I've put it through. I originally tried to root it though I don't think I was successful because the Root Checker said I wasn't, though I'm not sure what I was doing wrong then. Things went downhill from there.
I've read through thread after thread hoping for something that would work, but I've given up trying to use other people's problems to solve my own. This is me saying "Uncle". I require assistance. Let me know what you need from me to provide me with the help I need.
Also - I have ADB on my computer and I think I have a basic understanding of how to use it, but since I can't enter recovery mode I can't do anything other than pat myself on the back for figuring it out. I think my first problem at this point is ODIN. I uninstalled KIES so that's not interfering (and don't even get me started on KIES - I installed KIES and it told me to install KIES3 which told me my device wasn't supported... which is crap because it's running Android 4.3 - or was before I got to it).
Thanks,
If you're sure the phone was on 4.3, then your options are limited thanks to Knox. You can only restore a 4.3 (MJA) based ROM to the phone via Odin, whether it is stock or custom. Easiest giveaway is if you see a line for "Knox" on the Download Mode screen.
At this point you should look in the ROM directory here for a full ROM (xxxxx.tar.md5), either MF9 (4.2.2) if it doesn't have Knox or MJA (4.3) if it does. If you cannot use Odin to put a full ROM on there, then you will need some more serious help.
Odin the stock 4.3 MJA OEM. Will return your phone to a stock unrooted state.
http://forum.xda-developers.com/showthread.php?t=2522810
Hello everyone,
My phone just recently started having this issue, where the screen freezes when it first turns on. If I try plugging it in to charge, it freezes on the battery charging screen; there is no animation that indicates that it is charging. I've tried going into recovery mode but all there is is something that says "MMC: mmc_read fail Movinand Checksum Confirmation Fail". I can, however, go into download mode, where I can install a custom OS. It seems that this screen functions fine and my instinct is telling me that if I want to continue to use my phone, I'll have to reinstall the firmware. I'm not interested in installing a custom OS but I do just want to get my phone back. I did not do anything to my phone, I turned it off for a flight and when I landed, I turned it on and it started freezing when I tried using it. I was able to send out a few texts before it froze and I had to restart the phone but then it just wouldn't get past the Samsung Galaxy S5 screen.
Thank you for your help.
If I understand correctly your phone is not rooted ? Then only a factory reset will help you I think ...
In my experience, a factory reset will fix that, but wipe data also. On S3 and Note 3, I have Odin'ed stock firmwares over stock firmwares before and it has retained the data while fixing the problem. You may want to look into this method.
BCSC said:
In my experience, a factory reset will fix that, but wipe data also. On S3 and Note 3, I have Odin'ed stock firmwares over stock firmwares before and it has retained the data while fixing the problem. You may want to look into this method.
Click to expand...
Click to collapse
I've sort of looked into the Odin method but I'm still slightly confused and a little reluctant do so without clear instructions. Do you know of a particularly good tutorial that could help me with this? I do want to retain some of the data.
Thank you for your help, if this doesn't work, I'll probably just factory reset it.
allsheneedewassome said:
I've sort of looked into the Odin method but I'm still slightly confused and a little reluctant do so without clear instructions. Do you know of a particularly good tutorial that could help me with this? I do want to retain some of the data.
Thank you for your help, if this doesn't work, I'll probably just factory reset it.
Click to expand...
Click to collapse
Its quite simple. Donwload your region firmware from sammobile or from the firmware thread, open odin 3.07 (later versions have issues). Don't change any settings but do make sure "repartition" is NOT checked as this may cause brick. Click on "pda". Select the firmware you just downloaded. Now boot phone into download mode, I believe its vol down home and power pressed altogether. Dismiss the warning and connect your phone. Finally once it says "added" press start. Thats it, good luck!
@non4 said:
Its quite simple. Donwload your region firmware from sammobile or from the firmware thread, open odin 3.07 (later versions have issues). Don't change any settings but do make sure "repartition" is NOT checked as this may cause brick. Click on "pda". Select the firmware you just downloaded. Now boot phone into download mode, I believe its vol down home and power pressed altogether. Dismiss the warning and connect your phone. Finally once it says "added" press start. Thats it, good luck!
Click to expand...
Click to collapse
This is correct.
EDIT: FULL STORY BELOW. SKIP TO SECOND REPLY FOR UPDATE!
900A, AT&T, WAS 4.4.4. I rooted my phone with towelroot by downgrading via ODIN then reflashing 4.4.4. I've had the phone for a year and wanted to experiment with some custom roms--specifically Twi5ted Lollipop. The version I found last night was V3. Anyways I followed the instructions of installing safestrap then attempting to create a partition to host the mod. Every time I tried to boot the partition I would wait 12 minutes with nothing but a black screen (I presume a bootloop.) After reading some posts here I found it requires a clean flash--not a dirty flash. So I used safestrap to backup, then I wiped it and installed the mod. Nothing--still black screen. I then attempted to restore the backup I saved--fails every time.
At this point being the noob I am, I started to get very concerned. I went into advanced wipe and for some reason selected 'system' and wiped it. After a reboot, it shows the Samsung logo, goes blank, vibrates then goes back to the Samsung logo. I went into the standard bootloader and attempted to restore to factory settings but there is nothing to restore of course cause I wiped everything.
I'm currently at work bored as heck cause my phone is wiped. I can still go into download mode thankfully. Should I have no problems flashing stock via ODIN when I get home on my lunch break? Which stock firmware should I flash for this phone?
Thanks!
Unfortunately my lunch break brought me no good news. I downloaded stock found here: http://forum.xda-developers.com/showthread.php?t=2714455
After I flashed all the files (Except BL) when it boots, it get's to the Samsung logo--freezes halfway through then goes blank with the blue LED light on. I waited 10 minutes just to see what it does with no luck.
Another thing I found was weird-why when I boot does it still say 'Custom' when I flashed the stock firmware?
I really hope I don't have to drop $650 on a new phone Any help would be incredibly appreciated. Thanks guys!
DETAILED INFO: KOT49H. 6900AUCU1ANCE
MODEL: SM-6900A UD
FCC ID : A3LSMG900A
GALAXY S5 AT&T
why didn't you also flash the bootloader?
mike-y said:
why didn't you also flash the bootloader?
Click to expand...
Click to collapse
AT&T bootloader is locked right? Regardless I tried flashing the bootloader as a last resort and ODIN failed. Figured it just confirmed what everyone else said that it's locked.
Is there a specific way I need to flash the files? Like one at a time?
Do I need to restore factory settings/delete cache THEN flash each? or vice versa?
Am I basically screwed since I have AT&T?
:crying::crying::crying::crying:
FIXED!
After flashing 4.4.2 several times and trying different things, I came across this thread which finally brought my phone back to life. Thanks XDA!!!
http://forum.xda-developers.com/att...w-to-unbrick-flash-to-stocknce-g900a-t3077652
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Mal-0 said:
Hey guys,
I could use your expertise and help.
After updating my stock Note 4 Att variant from 5.1.1. to 6.0.1, I came back to my phone powered off. After turning it back on it freezes at the Att logo screen. Trying to boot into safe mode was a no go so I tried booting into recovery. Everything looked go for a second, I was greeted with an installing updates animation but that quickly was shut down and I got the "dm-verity verification failed..." error.
I tried wiping the cache and doing a factory reset. Talking with att technical support was no help at all. They basically told me if wiping the cache and factory reset didn't work I would have to get the phone replaced and pay a $150 deductible. I'm not paying them another dime when their update bricked my phone
So I'm here heart in hand hoping you guys could help me out. I did root my note 2 back in the day but forgot most of what it entails and was pretty bummed when I found out there was no root for the note 4. So I'm not a total noob but bear with me.
I did try Kies 3 but my phone wont connect. I tried off, on and in recovery still nothing.
Searching online it seems like most of the solutions require root access which this phone doesn't have. It also looks like it needs the stock firmware but most of the links I found here and elsewhere are dead, and sammobile doesn't have them either.
So what should I do? Am I out of options? Should I junk it cause Att sucks? Any sort of direction would be a big help! :highfive:
Click to expand...
Click to collapse
Make sure samsung kies or samsung usb drivers are installed on your pc.
Download stock marshmallow firmware and flash through odin .this method does not require root.
After flashing dont let the phone boot just go to recovery and wipe cache+wipe data factory reset then reboot.
Wait 10 to 15 minutes.
Stock rom link.
https://www.androidfilehost.com/?fid=24651430732238073
Extract file and choose AP tab in odin.
Upload firmware file then connct device via usb cable to pc.
Hit start in odin.
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Mal-0 said:
You're the man! Not only did you save my phone, you stuck it to Att's money grubbing hands in one fell swoop. People will write songs about you, you'll go down in the history books as the man, the myth, the legend! People will swoon in your presence!
In all seriousness though you're awesome! Thank you!
One last question, will I be able to use the ota updates from here? Not that I would be too comfortable using them after this debacle, just wondering if they should work.
Click to expand...
Click to collapse
Thanks for the compliment. you just made me feel like i am a Hercules :victory:
If you want my advice dont ever take ota updates.
Just go to www.sammobiles.com/firmwares and grab latest rom for your model and flash in odin as you did.
Latest rom comes with the same security patch update the 1 comes in ota.
I personally do this way all the time.
Hope that helps and have a good day.
Hello all. Today I decided to root my Samsung Galaxy S4, model SM-S975L. I followed a post from these forums to the T, and everything was going great, until my phone went to sleep and then locked. After it was locked, the touch screen stopped responding. I gave it a reboot and it worked until locked yet again, and again and again and again. I then attempted to use a USSD code that was supposed to bring up some kind of fix to the touch screen firmware, I believe, and the code didn't do anything. Got a pop up that said it was running the USSD code and then nothing happened, it just disappeared. I was also unable to update the su binary when I downloaded SuperSU. Don't know if this is related. Below is the link I used to root my phone. Any help would be wonderful!
https://forum.xda-developers.com/showpost.php?p=66590962&postcount=223
Judging by that guide, you did not root your device, you installed a completely different firmware.
Not only that, but it is an old version too.
I suggest you download this version and in the configuration screen select "STOCK KERNEL".
It's pretty much the same process as with the other version.
I forgot to mention I rooted my device with the PC version of KingoRoot, and when I used a root checker app it did say it was rooted.
But say I go this route, am I to also install open gapps? And does it need to be a different version?
So my touch screen stopped working again, this time during the AROMA installer. Managed to get through that with the volume keys and power button. Then it took me back to the screen from TWRP where it says I successfully installed the zip. But my phone is locked and my touch screen is not working. What to do? Please, anybody... I don't want to just pull the battery because I still need to wipe the cache and dalvik and doing that to your phone isn't good for it anyways, from my understanding. Please, I don't want to make it even worse if I can avoid it!
rainygreeneyes said:
So my touch screen stopped working again, this time during the AROMA installer. Managed to get through that with the volume keys and power button. Then it took me back to the screen from TWRP where it says I successfully installed the zip. But my phone is locked and my touch screen is not working. What to do? Please, anybody... I don't want to just pull the battery because I still need to wipe the cache and dalvik and doing that to your phone isn't good for it anyways, from my understanding. Please, I don't want to make it even worse if I can avoid it!
Click to expand...
Click to collapse
Then flash any other ROM that does not have the word "Optimized" or "Aroma" in its name.
You can also flash the official Lineage ROM, I assume it should work.
I attempted to unroot by flashing the original firmware for my Galaxy S4 and ended up soft bricking it, I think. It says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Kies is not recognizing the phone. Am I correct in thinking it is soft bricked? If so, how can this be fixed? Please explain as if you were explaining to a child, I am clearly not very good at this.
rainygreeneyes said:
I attempted to unroot by flashing the original firmware for my Galaxy S4 and ended up soft bricking it, I think. It says "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." Kies is not recognizing the phone. Am I correct in thinking it is soft bricked? If so, how can this be fixed? Please explain as if you were explaining to a child, I am clearly not very good at this.
Click to expand...
Click to collapse
try flashing it with Odin again, Kies isn't needed, just connect it to PC(while in that screen) and flash the stock rom with Odin, it should recognize it.