Related
Hi everyone,
Before blasting away with comments as to why I would do this, here's my story,
I live in Canada and just brought home a i9508, a China variant of the S4. It belonged to my dad and he didn't want it so I just took it. The i9508 doesn't have Play Store, and it doesn't work on Canadian 3G network.
So to me, the phone is useless right off the start (don't intend on selling it either, who wants it?) So I had 2 options:
1) Leave the phone as it is, and probably use it once every 1-2 years when I visit HK
2) Flash custom roms on it fully aware of the risk it will have so that there's a possibility I can make it more usable
So in the end I went with option 2.
I followed a guide and flashed TWRP for i9505 using Odin onto the phone, and used TWRP to install chainfire SU, and it actually worked (but SU wouldn't open because some sort of security on the phone is blocking it)
Next step, I downloaded the CM version for i9505 and flashed onto the phone, and that worked too. Only problem I've encountered was that the phone would only boot after a fresh install. If I installed CM, turned the phone off after the initial start up, the phone wouldn't boot pass the Samsung logo.
Up until this point, I didn't make a backup, because of my arrogance, cause I have available a copy of the official firmware, in case anything happens.
So I figured at this point, maybe if I restore the original firmware, and try the whole process again, the custom rom would work. So I went into Odin, flash the firmware with PDA, and failed. It just wouldn't work. After retrying it a couple of times, and downloading different updates of the firmware, nothing worked. Only thing working right now is, I can get into Download mode, and I can get into TWRP recovery (but for some reason, I can't flash the zips that I've adb pushed onto the phone, zip can't open)
For me, if it can't be fixed, then it's really SOL. But if there's a way to fix it, I'm open to testing anything people have in mind, cause afterall, this phone is paper weight either way. I'm interested in seeing if I could enable 3G by flashing a i9505 radio, despite warnings, although, I've never actually came across a thread where someone had actually tried it before.
Either way, if someone has any idea on how to fix the phone, and wouldn't mind sharing it, that'll be greatly appreciated.
Working
I can get into Download mode, but Odin is failing (if you need the error please let me know and I'll post it)
I can get into TWRP recovery, but can't flash files
I can get into adb
This isnt the correct forum for your phone. XDA don't follow clones
Unfortunately a section for i9508 doesn't exist, so I figure the closest one would be i9505.
Anyhow, if someone has an idea of how to fix it, I'm more than happy to do testing on it, like flashing other roms or radios.
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.
Note 4 Stuck in Boot Loop - Help
I have a Note 4 SM-N910F, never been rooted, stock rom upgraded to 5.1.1 back in October, working fine until yesterday when it got stuck in a Boot loop.
Not sure what caused it but before it got stuck I was messing around with Google Photos which was running a bit slow.
Also I put it on the Qi Charger just before the loop started. It has an aftermarket Fone charger stuck to the battery. I’ve had this and the Qi Charger for 6mths with no problems before now.
It gets to the Samsung page waits a couple of seconds then boots again.
Here’s what I’ve tried - unsuccessfully - to fix the boot loop:
1: recovery mode.
I can get the little recovery text to appear in the top left but after a few seconds it boots again.
2: volume down, home
This gets me to the screen with up/down for continue/cancel.
This is the _only_ screen I can get to stay up without rebooting. It sits there waiting for input.
- Cancel, causes restart, of course, but back into the bootloop
3: Mashing on power button. Banging it, wiggling it, blowing on it.
I read somewhere this could cause a boot loop, but I doubt it is my case because
a. I’ve never had problems with the power button before
b: When I take out the battery and put it back in, it does NOT turn on. If I do the same holding the power button, it powers into the boot loop. So if the button were jammed on I would expect it to never remain off with the battery in.
3: flashing stock rom
I’m not 100% sure what build I had before. I know it was stock 5.1.1 OTA, and I’m pretty sure it was unlocked (my wife bought the phone and i inserted my old sim, but she may have bought it from my carrier and can’t remember)
So anyway I tried all three versions of TPH (unlocked) 5.1.1 from Sammobile.
Installed Odin 3.10.7 and flashed them.
It reboots to recovery but immediately boot loops again.
I doubt its to do with the version of the rom anyway since the symptoms are identical after flashing. Only now the boot loop always shows the little ‘recovery booting...’ text in the top left.
Here’s what I have NOT tried but am thinking about:
A: Re-partition option in Odin
B: Nand Erase All option in Odin
C: Buying a new battery.
On A/B: as far as I can tell what I have done so far should have left the data intact. I’m prepared to wipe all my data if it fixes my phone (no lectures about backups please!) and I’m tempted to do one of these on the off chance that the problem is caused by data or the “disk" problems.
But I don’t want to brick it. Can someone recommend how likely these are to help
And what they actually do?
(Please refrain from responses I see elsewhere like “this will brick your phone if you don’t know what you’re doing”. I don’t know what I’m doing, thats why I’m asking - just the facts please)
On C: the battery seems ok in that the power is solid even after not being plugged in for a long time, but since it was on the Qi Charger with that aftermarket thing stuck to it when it happened, I’m suspicious. Can any one say if this is a likely cause?
If so, it might be worth waiting till I get a new batter before doing A or B (can I wait days for Amazon!?)
[UPDATE] Got a new (genuine) battery at a local electronics store. No dice. Same problem, so it's not the battery. Shall I go ahead and re-partition.
[UPDATE] Got a PIT file from another forum, and flashed again with re-partition checked and PIT loaded. same results.
Is Nand-rease worth trying?
The phone is still under warranty so maybe I can return it.
But in that case I want to erase what's on it first.
thanks for any help
rhubarb
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
You can flash TWRP through ODIN while on COJ5 bootloader. It's locked but you still can flash recoveries and kernel and 5.1.1 ROMS
I am very interested in this thread. I have the EXACT same problem as you have after installing SimplRom, which was a ROM prior to COJ5. It could indeed be that our bootloaders are locked now?
I am using the N910F and just like you, installing any ROM/Custom Recovery/Bootloader/Kernel doesn't help. Perhaps installing a COJ5 ROM might help. I will give that a try, but I've recently used Kies to install the latest official firmware, but it didn't fix the issue.
I will report back here and we'll work on this together to make our phones work again!
Osama lakdawala said:
I don't think that the Samsung service center will accept cuz u have unofficiall custom
Simple Go to ur any nearby SOFTWARE ENGINEER may be he will help u out
Even I had the same problem with my NOTE 4 EDGE
Click to expand...
Click to collapse
Thanks but:
1: I have no custom rom. I have never had a custom rom on this device. I want to take it to Samsung, but want to clear the memory first. How can I do that?
2: I _am_ a software engineer_
dork997 said:
Try downloading and flashing any "COJ5" build of 5.1.1 from sammobile. Samsung has recently issued a new update "COJ5" it basically locks down the bootloader and will not allow the device to run any previous builds.....Maybe your phone updated to COJ5 in the background and then it started messing around because the phone is rooted. Flashing "COJ5" will lock your bootloader and you will not be able to flash 4.4.4 or 5.0.2 but there is nothing to lose when your phone is already pretty much dead?.....ORRR if this is not a software issue then it could be related to hardware maybe the memory of your phone is done. I am not an expert on this but this is just an advice.....i have told you what will happen if u flash coj5 build now its up to you to decide. I would suggest you wait and wait if you are lucky to get a response from an expert and do what they say .......if not then give this a try!
**EDIT** another idea....First flash a custom recovery such as TWRP....see if it lets you boot into recovery and if it does then perform all sorts of formats.....and factory resets in there see if it works....if its still rebooting after format then flash the coj5 build of 5.1.1....note that you "MUST" format it with TWRP first and then check if its working because once you have coj5...it might not let you flash custom recoveries.
Click to expand...
Click to collapse
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
roverrhubarb said:
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Click to expand...
Click to collapse
I have the exact same as you. I did install a custom recovery (multiple) and still get the bootloop. From my tries yesterday, I indeed also suspect it may be a hardware issue. Perhaps to do with the battery/charging port. When I have my device unplugged and try to start in recovery/normalboot, it does not have a bootloop but simply turns off (and then doesn't respond until I pull the battery out). I think a NAND erase wouldn't do anything as I've personally tried that already.
Have you prior (upto a week) before you got the issues had your phone in a moist environment (bathroom while showering for example). I got my problems a week after I accidentally left my phone in the bathroom and installed custom ROM (which was done earlier and had no issues).
I've read online that it may have caused oxidation on the inside and may need some cleaning/drying with alcohol.
I still hold hope that we just have a software issue as download mode is working fine (apart from the Power off not working unless we pull out the battery).
Anybody have any experience with oxidation on their phone? Perhaps have had a similar bootloop due to hardware failure?
roverrhubarb said:
Thanks to you and dork97 for the ideas. First some notes:
- I have never flashed a custom ROM, nor ROOTed this Note 4. The recent upgrade to 5.1.1 was official.
the first upgrade to 5.0.1 was automatic and after that I turned off automatic upgrades and upgraded to 5.1.1. manually. So I dont think it was an upgrade that caused it and it certainly was NOT a custom ROM or ROOT. I was doing nothing at all when the boot loop started.
- I'm not sure what ROM I had, but when I went looking for the available Portugal unlocked ROM, which _should_ be what I had, the latest were CJ03 (3, not 5) and before that CH03, CI03. Presumably I had one of those (my last update was October, so probably CH03).
I have tried all 3 of these, but the symptoms are the same.
I'm tempted to try the TWRP option - but would like some more details on what is and what it does, or what problem I might have that it would fix.
However I am probably still in time for a warranty repair - especially since I didnt actually do anything for this to happen. I would like to avoid losing that chance.
If I do take it in for warranty, I'd like to wipe the memory first though. How can I do that?
Finally can anyone actually tell me if the NAND ERASE is likely to help? How does flashing TWRP compare?
I get the feeling in fact, that I have a hardware problem. Especially given there were not software system changes around the time it happened, and given that it loops while trying to boot into recovery mode. In fact the only mode that doesnt constantly cycle is download mode. (Even holding the power button in dl mode does nothing which makes me suspect that, but pulling the battery out and replacing it leaves it off until I press the power button so perhaps not)
Thanks for the replies so far. Any more ideas, details?
Click to expand...
Click to collapse
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
dork997 said:
Well if you still have warranty then don't try anything on your own and go for the warranty repairs.
Click to expand...
Click to collapse
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
Since you can get into download mode I'd flash firmware through ODIN again after verifying it's correct.
I'm seeing off the sammobile site for the 910F not all are the COJ5 locked bootloader.
Since you did update in Oct you may be on the COJ3. I'd try one of those and see if it works.
If it doesn't work and stops on the sboot.bin file then you have the COJ5
roverrhubarb said:
thanks. How can I wipe personal data without voiding the warranty, using odin or kies? Given I canNOT get it into recovery mode, only download mode.
Click to expand...
Click to collapse
i am sorry i don't know any way to remove personal data other than doing it via recovery. There is an option of "nand erase" in odin it is used while flashing firmware and it wipes everything on the phone but i have never used it (and also don't know whether it can help you or not) ... Senior members kindly help us with this.
Any update to your situation?
very interested as I am in the same situation as you are. Download mode works, recovery+normal boot not. No matter what ROMs/recoveries I install
Same issue I think
I am also in the same situation, although I can enter the recovery mode - home power and volume up - I have tried the wipe cache and then factory wipe to no avail - I have also entered download mode and flashed the stock recovery and even though Odin says pass, it is still in a boot loop. Also when I go to the download screen it has a line saying knox warranty void 0x1(4) does this mean I have voided the warranty even though I only used Odin to flash stock recovery?
Did anyone found a solution
Did anyone ever found a solution to this problem I'm having the exact same issue on a note 4 smn910a
I have a slightly different issue with my Note 4 SM-N910G, wherein am not able to start the phone at all, it is completely dead, if i put the cell phone on charge then also there is no LED on the top but if i connect the device to the PC it does make the connected sound on the PC but Odin is still not able to recognize the device neither kies. I tried draining the power by removing the battery, connected the device to PC without battery and then inserting it but the same problem. Please suggest me any resolution for this dead body am carrying from past few weeks.
hi Op,
did you find any solution for this issue?
Hello all. This is advice to use as a very last resort if you are experiencing the recovery bootloop issue AND you don't have the emmc failure bug. I had the recovery reboot, sudden shutdown with no warning, etc. issue for the past two weeks. I tried everything on Google and Youtube to fix my problem with no success. I flashed multiple stock ROMS and recovery tars (stock and TWRP) via ODIN, but nothing worked. Oddly enough, I never received the emmc error that I have read about. Also, in the few times that my phone booted normally, I even loaded the Wakelock Power Manager app, set it to partial wakelock and my phone STILL continued to bootloop. As a last resort, I bought a new battery, but the reboot problems continued in Android 4.4.4 Kitkat, 6.0 Marshmallow, 7.1 Nougat and 8.1 Oreo ROMS. Well, here is what finally helped me to get my phone back operational. I had a backup ROM from a previous install and a TWRP flashable version of the same ROM on my SD card (in case the phone did not stay on for the full restore). I put the phone into a ziplock bag into a freezer for about 20 min. (thankfully this time TWRP stayed on long enough for me to do the following):
1) copy all the files I wanted to save from internal storage to a computer.
2) performed a full wipe (Dalvic, Cache, System, etc. Like when flashing a ROM, but this time also internal storage. Note: Please do not wipe both internal and SD card, as you may have a difficult time trying to load the ROM file back on the sd card (assuming you don't have a card reader).
3) After wiping, I was able to restore my stock ROM backup (or you can just flash the stock ROM).
I can't be 100% sure, but I think my wiping internal and then flashing the stock ROM finally did the trick. Since this morning, the phone has been pretty much back to as it was before. In either case, I'm sharing this with the hope that it helps someone else.
Sent from my SM-N910T using Tapatalk
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.
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
aerialslam said:
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
Click to expand...
Click to collapse
If you can at least get into download mode, then simply flash it with the latest STOCK firmware for your particular model.
That will bring it back to life, and you can attempt rooting it again, if you dare
aerialslam said:
I'm completely at a loss at this point.
I attempted to root my Samsung S7 (AT&T) with Odin, and received an error. This is my first time ever rooting a phone, and I am generally oblivious to this kind of stuff. I disconnected the phone, and it began bootloop. I loaded it into download mode, and attempted to reset to stock. However, I have had endless issues trying to flash the stock firmware to my phone. At one point I unplugged the device once again, and I received the "use Emergency Restore" error screen. I tried to restore with Smart Switch, but I was not able to access my S/N (box is nowhere to be found, managed to find a S/N on Samsung's website since I registered it but Smart Switch wouldn't take it). So, I figured trying to restore with Odin was my last option. I have tried at least 3 different Odin versions, both modified and not, and not a single one of them has worked. I've received Complete(write) errors, Model Dispatch Fail errors, and Re-Partition errors. I've tried about 3 different firmware files as well, and while I think the one I have right now is most recent, none of them seem to be working. I thought maybe an issue I was encountering was that USB debugging or whatever it's called was disabled, but I have no way of telling because I cannot boot my phone.
I was fiddling around with all of this from 11pm to 6am last night, and picked it back up as soon as I woke up. I've been freaking out about this for hours.
I feel like I'm running in circles here. I don't understand what I'm doing wrong. I'm recovery bootlooped as well. The only thing I can boot is download mode.
I wasn't very cautious with this process, and I am completely unfamiliar with most lingo on these forums and the whole process in general. I really regret trying to do this. So -- is there anything else I can try to do to fix it? Or is my phone bricked for good??? I'm endlessly frustrated and have honestly felt like crying a few times over this. I shouldn't have messed with something I know nothing about. :crying:
I thank you for your patience in dealing with me as a beginner + appreciate any help you're able to give.
Cheers.
Click to expand...
Click to collapse
Did you finally recover your phone? I'm in the same problem here since yesterday and feel your frustration right now. My phone is a Samsung S7 model SM-G930A from AT&T.
I found this thread https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039 and I following the "Return to stock part", now downloading the firmware. Hope it helps.
I'm stucked in the blue screen "An error ocurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". Of course I try the Smart Switch but says that my model is not supported!
How can you recovered the download mode? I press the on/off button for some seconds and the screen turn of, but it turn on again with the freaking blue screen "An error ocurred while updating the device software. ...". I tried all the possible button combinations.
Thanks and good luck.
Stock firmware
Make sure when you go into download mode and flash that plugging the phone in is the LAST thing you do. I.e. plug phone in only after it is in download mode and only after you open Odin. Secondly, make sure you flash the STOCK firmware, as in Android Marshmallow v6.0.1 . Additonally, make sure that the re-partition option is NOT ticked, and also you might want to try turning off auto-reboot, and just hold the power button after unplugging once the status bar is all the way full and Odin says complete. Also, you need to make absolutely sure that you're getting the firmware for your exact device. I.e. SM-G930A stock firmware is NOT compatible with SM-G930F models. You could also try reinstalling the Samsung drivers. I just flashed to stock firmware then updated back to Nougat yesterday, mostly without a hitch by following these guidelines. There is a download page on rootmygalaxy with all the stock firmwares, that's what I used (I'd link but I just registered here). There is a very helpful guide on droidviews about how to update to Nougat 7.0 once you have finished flashing the stock firmware.
If I were you, I would just avoid rooting altogether. Rooting for me caused very bad performance and battery life, and it wasn't really worth the trouble. Sure, getting in-app-purchases for free was nice but I never tried flashing a custom ROM or anything because most of the stories I read involved soft bricks, bootloops, etc.
Hopefully not having USB Debugging and OEM unlock ticked doesn't brick your phone, I'm doubtful that it will. For the poster above me, make sure your phone is all the way off, the download mode button combo is vol. down+power+home all at the same time, and hold them. A screen should pop up saying press vol. up to continue. If you're still having problems, I regret to say that I am also relatively new to this and I am not all that knowledgeable.
I just made a post about my unrooting process, hopefully it helps!
https://www.youtube.com/watch?v=o6ryOQepX2Q Video shows booting into Download Mode. Or take it to a Best Buy that has a Samsung Sales section.