Related
So I decided to try out the new cyanogen mod 7.1. I followed These instructions and everything went fine until it was time for the phone to reboot after heimdall's flash.
It didnt reboot, but stayed on the splash screen. I could still both boot in recovery (recovery was CVM) and download. I thought everything was ok, and put the cyanogen-update zip onto the external memory card. However, as all of you (and now I) already know, it doesnt work that way, as the zip has to be on the internal SD.
"Sucks to be me" I thought, but I applyed the update.zip that was already on the card, hoping that it would reset everything (did a factory wipe as well). It didnt.
So, I started kies, set the phone to download and hoped. Kies detects the phone, but it couldnt connect (it just tries infinitly). So, here comes the retard part: I found a guide for installing the same kernel with odin, so I tried that. Odin found the device, but stopped right after (SetupConnection). So, I pulled the battery, waited 5 minutes, and the dreaded "download error" came up. So I restarted the phone, tried to put it in download mode, and it worked! So, now Im back at square retard, becuase heimdall can still flash it and kies still finds the phone (without succeding in connecting), but it doesnt do anything else.
So: what do I do? At the present, I am prepared to settle for stock everything, as long as I get my phone back (I will probably try to install cyanogen again, and come back with new questions, but that is a later problem).
Thanks in advance<3
Prob better posting this in General or on a CM 7 thread/post...
You shouldn't have a problem flashing a stock rom with odin. Just remember to pick repartition, with the correct pit file for the rom.
Sent from my GT-I9000 using XDA App
I have an i747 and after a week of research and trail and error I was able to get back to a factory working phone. I wanted to share my findings so that the next person may get up and running a bit quicker. First off, my phone was never rooted. I was getting it ready to sell and was going to factory reset it when I realized I forgot the system password. So I installed Kies and proceeded to factor rest it there. For whatever reason the reset did not take and after several failed attempts with kies the phone began to boot in ODIN mode. I built a USB jig and was able to get back into download mode but nothing would bring it back to life. Downloading the official rom from sammobile and flashing with ODIN3.07 would fail every time. Emergency recovery in kies also failed. So here was my final approach that worked. Maybe the wrong way to do this, maybe the long way to do it.. IDK.. but it worked for me..
1) get the official Samsung files from kies (google -"does kies store firmware")
2) boot do download mode
3) flash CSC file with auto reboot and F. reset time checked
4) boot do download mode
5) flash PDA file with auto reboot and F. reset time checked
6) boot do download mode
7) flash Modem file with auto reboot and F. reset time checked
* I closed ODIN between each step, might be overkill.
** I did not flash the bootloader file
I have read that it takes a long time the first boot, and I have been waiting 15 minutes at the SAMSUNG screen but it is still pulsing so i think it is still processing. If it is still at this screen in the morning, I will let you all know but this is further than I have been in over a week.
On a side note, when it crashed I took this into AT&T they told me over the past month or so they have seen numerous people with the same issue. All from doing a factor rest in Kies. My phone was out of warranty and they barely looked at it before asking me to upgrade. I took it to BestBuy and they fixed it from booting to ODIN mode but it still locked up on the AT&T logo, so I was back to square one.
Food for thought. How about waiting to see if your instructions actually work on your phone before posting them here for people with similar issues to use. Kind of useless if it doesn't end up working, huh?
lordblue969 said:
I have an i747 and after a week of research and trail and error I was able to get back to a factory working phone. I wanted to share my findings so that the next person may get up and running a bit quicker. First off, my phone was never rooted. I was getting it ready to sell and was going to factory reset it when I realized I forgot the system password. So I installed Kies and proceeded to factor rest it there. For whatever reason the reset did not take and after several failed attempts with kies the phone began to boot in ODIN mode. I built a USB jig and was able to get back into download mode but nothing would bring it back to life. Downloading the official rom from sammobile and flashing with ODIN3.07 would fail every time. Emergency recovery in kies also failed. So here was my final approach that worked. Maybe the wrong way to do this, maybe the long way to do it.. IDK.. but it worked for me..
1) get the official Samsung files from kies (google -"does kies store firmware")
2) boot do download mode
3) flash CSC file with auto reboot and F. reset time checked
4) boot do download mode
5) flash PDA file with auto reboot and F. reset time checked
6) boot do download mode
7) flash Modem file with auto reboot and F. reset time checked
* I closed ODIN between each step, might be overkill.
** I did not flash the bootloader file
I have read that it takes a long time the first boot, and I have been waiting 15 minutes at the SAMSUNG screen but it is still pulsing so i think it is still processing. If it is still at this screen in the morning, I will let you all know but this is further than I have been in over a week.
On a side note, when it crashed I took this into AT&T they told me over the past month or so they have seen numerous people with the same issue. All from doing a factor rest in Kies. My phone was out of warranty and they barely looked at it before asking me to upgrade. I took it to BestBuy and they fixed it from booting to ODIN mode but it still locked up on the AT&T logo, so I was back to square one.
Click to expand...
Click to collapse
Seems a pretty long route to take. If you are on an Odin flashable firmware version (e.g. 4.1.1), you only need to flash one partition - PDA. This updates all partitions to stock including bootloader, modem, recovery, kernel. The newer firmware versions - 4.1.2 & 4.3 are, however, not Odin flashable. Also, if you couldn't do a factory reset from settings because of password issues, you could have booted into recovery mode and done a factory reset there. This wouldn't require a password and would still have the same effect of wiping data and returning to factory settings.
If your phone is stuck at the Samsung screen for 15 minutes, then it's stuck. Reboot into recovery mode and try a reset there. If this doesn't work, then it means you have a soft brick you need to restore your firmware via custom recovery. Your phone is never hard bricked when you can get to download and recovery modes. Flash custom recovery via Odin in download mode. Reboot to custom recovery and flash a clean, complete stock image for 4.3. That's your best option now since you are selling
Larry2999 said:
Seems a pretty long route to take. If you are on an Odin flashable firmware version (e.g. 4.1.1), you only need to flash one partition - PDA. This updates all partitions to stock including bootloader, modem, recovery, kernel. The newer firmware versions - 4.1.2 & 4.3 are, however, not Odin flashable. Also, if you couldn't do a factory reset from settings because of password issues, you could have booted into recovery mode and done a factory reset there. This wouldn't require a password and would still have the same effect of wiping data and returning to factory settings.
If your phone is stuck at the Samsung screen for 15 minutes, then it's stuck. Reboot into recovery mode and try a reset there. If this doesn't work, then it means you have a soft brick you need to restore your firmware via custom recovery. Your phone is never hard bricked when you can get to download and recovery modes. Flash custom recovery via Odin in download mode. Reboot to custom recovery and flash a clean, complete stock image for 4.3. That's your best option now since you are selling
Click to expand...
Click to collapse
So like the true repository of knowledge we have here, Larry you are correct.. After about 30 minutes I decided it was really stuck.. So this time I watched the process I described above a bit more closely and as you stated the PDA file is all i needed.. but I had tried several from different sources including the office from sammobile and they always crashed. So what eventually worked for me was after being stuck at the samsung logo...
I booted into recovery mode
wiped the cache
factory reset it
then flashed with the Kies PDA file that I obtained in Kies in emergency recover mode.
This finally worked.
and as stated was a shorter route to take. The PDA that i used had 4.1.1 on it.
Thanks for the clarification in the fact that flashing with the PDA takes care of the bootloader, cache, file system, etc.
DMF1977 said:
Food for thought. How about waiting to see if your instructions actually work on your phone before posting them here for people with similar issues to use. Kind of useless if it doesn't end up working, huh?
Click to expand...
Click to collapse
excitement over came me.
Still having issues
Ok, keepers of knowledge.. I have a phone that will boot up but I have no baseband version. It shows unknown.. I have tried just flashing the modem file but i still do not get it back.. if I try to flash anything other than the official files from kies, ODIN fails. My phone is now at 4.1.1, build JR003L.I747UCDLK3.
If I try to update via wifi with the software updater, it says I am up to date. If I try to update with Kies, it fails..
I am at a loss...
Please help..
Thanks in advance..
My daughter's note 2, which looks to be in perfect condition, was running dirty unicorn. She messages me in a panic because the phone turned off on her, and wouldn't reboot.
I could get into recovery, but many of the options like factory reset wouldn't work. Reformatting /cache gives an error with ext4 and can't write, and at the bottom of some of the screens is an error about unable to access some log files in the /cache directory. Going to install zip to reinstall dirty unicorn doesn't seem to do anything, it can't find any files.
Wipe system gives errors like "format_volume: make_extf4fs failed on /dev/block/mmcblk0p12". It can't mount /data, just gives an error.
I tried reflashing the stock mj4 via odin, which ran successfully, but didn't resolve anything.
Tried using KIES 2.6, which did go into download mode and said it downloaded a bunch of stuff and then flashed the phone, but it's still stuck at the bootloader.
I tried flashing a bootloader, but am unclear of how to flash the param file if necessary (does it go in bootloader? PDA? what slot in odin?).
I need some ideas. Maybe the flash has died on it, and it's unrecoverable, but it's in such perfect shape that I hate to just toss it.
I have recover 6.0.4.3 (CWM) installed, and can still get into it. But upon loading recovery, it gives me errors like "Can't mount /cache/recovery/command", "Can't open /cache/recovery/last_log", etc.
Any help appreciated.
mrcpu said:
My daughter's note 2, which looks to be in perfect condition, was running dirty unicorn. She messages me in a panic because the phone turned off on her, and wouldn't reboot.
I could get into recovery, but many of the options like factory reset wouldn't work. Reformatting /cache gives an error with ext4 and can't write, and at the bottom of some of the screens is an error about unable to access some log files in the /cache directory. Going to install zip to reinstall dirty unicorn doesn't seem to do anything, it can't find any files.
Wipe system gives errors like "format_volume: make_extf4fs failed on /dev/block/mmcblk0p12". It can't mount /data, just gives an error.
I tried reflashing the stock mj4 via odin, which ran successfully, but didn't resolve anything.
Tried using KIES 2.6, which did go into download mode and said it downloaded a bunch of stuff and then flashed the phone, but it's still stuck at the bootloader.
I tried flashing a bootloader, but am unclear of how to flash the param file if necessary (does it go in bootloader? PDA? what slot in odin?).
I need some ideas. Maybe the flash has died on it, and it's unrecoverable, but it's in such perfect shape that I hate to just toss it.
I have recover 6.0.4.3 (CWM) installed, and can still get into it. But upon loading recovery, it gives me errors like "Can't mount /cache/recovery/command", "Can't open /cache/recovery/last_log", etc.
Any help appreciated.
Click to expand...
Click to collapse
The other weird thing is that I used odin 3.06 to flash twrp 2.8.5, or at least attempt to, download processed, device reset, but recovery is still CWM 6.0.4.3. WTH?
Ok check this thread where I just helped fix a note 2, simular to your situation ok.
Plenty of links in there for you. Keep in mind everything in this thread I'm sending you too it's for the AT&T i317 ok.
http://forum.xda-developers.com/showthread.php?p=59000961
Which I'm sure that is what you have, posting your problem in the Att q&a thread.
Bajanman said:
Ok check this thread where I just helped fix a note 2, simular to your situation ok.
Plenty of links in there for you. Keep in mind everything in this thread I'm sending you too it's for the AT&T i317 ok.
http://forum.xda-developers.com/showthread.php?p=59000961
Which I'm sure that is what you have, posting your problem in the Att q&a thread.
Click to expand...
Click to collapse
Correct, it is an AT&T. I have tried the options in that thread, but I swear, nothing I flash actually "sticks". I've used odin 3.06, put the files in PDA, plugged it in in download mode, the progress bar appears on both odin and the phone, it resets, it reboots, and nada. Hung.
I can't even flash a replacement recovery, nothing "sticks". I've used KIES to flash, it tells me it's successful, but I still have CWM 6.0.4.3. I've tried the original 4.1.1, NJ1 (rooted), I've tried flashing a bootloader, then tried the one with the param file attached, I downloaded a pit file, followed the directions on that page with the Re-partition option, and I still can't get anywhere with it.
If I cold even just get a different recovery installed, just so that I *know*, my odin is OK, then I'd feel better about making progress.
I've tried to flash philz_touch 6.48.4, openrecovery-twrp-2.8.5 through odin, and I can't even get the CWM recovery replaced. Odin reports success, reboots the device, frozen.
I swear, if this was one of my servers at work, I'd figured the NSA has hacked the firmware to just discard writes and report back success.
I'm not crystal clear in ODIN how to flash bootloaders, on one hand, presumably, the "bootloader" button, but one guide shows the bootloader file being put in PDA, so who knows. I may have ended up with a bootloader mismatch, but I thought flashing the latest stock recoveries.
FWIW, the phone was running Dirty Unicorn, although I'm unsure of specifically which version, she's had it for a while.
Thanks for any help.
Just realized something.
If I hold down the power/vol down/home and boot into download mode, I get the little red "odin mode" at the top left, 4 lines of text about custom, etc, and then the green android icon.
If I boot into recovery, then use it to boot into download mode, the green android is there, but none of the text (odin mode, etc) is on the screen. Is this normal?
I have also been having some strangeness with my Telus Note II. Very similar symptoms to what you're describing. One morning I woke up to my phone stuck on the Samsung logo as the phone must have rebooted itself overnight. When I tried to reboot it would freeze at the same spot once again. I tried to go into recover (TWRP) and it wouldn't, and a subsequent reboot left me in a boot loop.
Nothing I tried would help. I couldn't get into TWRP. Using ODIN 3.07 I put on CWM and I was able to get into recovery now, but nothing in it worked. Finally I tried using ODIN to put on CF-Auto-Root-t0ltecan-t0ltevl-sghi317m and I was finally able to get into a recovery that allowed me to do a factory reset. Once I did that I was able to boot up the phone.
I then re-installed TWRP and restored a back up that I had, and everything was normal again. The phone was running great. However, sometime at night things get messed up again. The phone has either reboot itself, and get's stuck again. I then have to repeat this whole process. During the day, the phone runs amazing. It almost seems to run better than before. However at night, if I'm on battery it will get messed up again.
I hope this helps you. Good luck.
have you tried all this using the same computer and usb cable? i would try a different computer, port, usb and re download all files again. perhaps use a different version of odin. good luck:fingers-crossed:
It's the same computer and cable I do my Note 3, and kindle fire 8.9, and with a different cable my nook HD, so I'm skeptical that it's any of those pieces, but for the heckuvit, I will try a different one.
Note 2 GT N 7100 --Stuck on CWM 6.0.4.3
gizhola said:
I have also been having some strangeness with my Telus Note II. Very similar symptoms to what you're describing. One morning I woke up to my phone stuck on the Samsung logo as the phone must have rebooted itself overnight. When I tried to reboot it would freeze at the same spot once again. I tried to go into recover (TWRP) and it wouldn't, and a subsequent reboot left me in a boot loop.
Nothing I tried would help. I couldn't get into TWRP. Using ODIN 3.07 I put on CWM and I was able to get into recovery now, but nothing in it worked. Finally I tried using ODIN to put on CF-Auto-Root-t0ltecan-t0ltevl-sghi317m and I was finally able to get into a recovery that allowed me to do a factory reset. Once I did that I was able to boot up the phone.
I then re-installed TWRP and restored a back up that I had, and everything was normal again. The phone was running great. However, sometime at night things get messed up again. The phone has either reboot itself, and get's stuck again. I then have to repeat this whole process. During the day, the phone runs amazing. It almost seems to run better than before. However at night, if I'm on battery it will get messed up again.
I hope this helps you. Good luck.
Click to expand...
Click to collapse
Dear friends, sorry for my interference, i having CWM recovery v 6.0.4.3 on GT N7100, i used to flash omega ROM 4.3, everything went well until i got stuck on Samsung log and the phone did want restart, i decided to go on CWM recovery, stunned with this message
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Still I can go on download mode, I tried use odin to flash stock rom but failed it takes me always to CWM v 6.0.4.3 where it stuck and dont allow me to format or do any thing except my external sd1 that I tried to flash from but returned to same prob ( CWM v 6.0.43)
also I tried to flash tried twrp 2.8.0.4 but failed
the prob is my internal sd can't be mounted and whatever i do don't pass
I read in your post something about flashing auto root in odin or fix CWM root
can you help please Im stuck in CWM v 6.0.4.3
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
You probably need to do a factory reset
In the future you should make a full backup before installing a rom
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
AHH!! Sorry to have made this post... here's what I did to get it actually boot:
reflahed the stock firmware through odin again, tried to reboot, it failed, obviously. rebooted to recovery, factory reset in recovery, power down option in recovery, then turned the phone on again and it magically worked!
hopefully this post will help someone who encountered the same issue
eousphoros said:
You probably need to do a factory reset
In the future you should make a full backup before installing a rom
Click to expand...
Click to collapse
thank you so much for the quick reply, I ended up figuring out the solution while you were typing. sorry to pull you away from other tasks. I have several backups saved to my PC but thank you for the reminder!! :laugh::laugh:
kswa1987 said:
AHH!! Sorry to have made this post... here's what I did to get it actually boot:
reflahed the stock firmware through odin again, tried to reboot, it failed, obviously. rebooted to recovery, factory reset in recovery, power down option in recovery, then turned the phone on again and it magically worked!
hopefully this post will help someone who encountered the same issue
Click to expand...
Click to collapse
I had the same excat same thing happen when flashing this via Odin. I didnt need to Odin stock twice though . I just booted stock recovery and did a factory reset. After that I went ahead an powered down and rebooted . All good now
How long did you have to wait in the stock recovery to get past the "installing system update" screen? Mine just sits there and I'm unable to view other options in recovery.
EDIT for noobs (like me): wait 30 seconds on the "installing system update" screen.
I'm still stuck in boot loop
Im in the same exact situation , but I'm still stuck in boot loop. I followed your restore instructions and nothing. Please help.
Creel711 said:
Im in the same exact situation , but I'm still stuck in boot loop. I followed your restore instructions and nothing. Please help.
Click to expand...
Click to collapse
Looks here, may apply to your case. http://forum.xda-developers.com/showthread.php?p=63226466
Pp.
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
Problem with Samsung Galaxy S4 Mini GT-I9195
Hi everyone
I'm new to the whole ROM flashing and using Odin. I had a bootloop problem and recovery mode showed all the options but has a green android man laying down with red icon above him and No Command below the android man. Tried the factory wipe and cache wipe but it gives some red writing with the word failed in the coding and the word error under the android man. Tried to flash a stock ROM from sammobile using Odin. Odin gives a pass but the same problems persist. Can someone please help?
any solution, i have this problem to? only bootloop, nothing else. Updatet bootloader with 4up
kswa1987 said:
Hi guys,
I have the t-mobile s6 edge
After messing around with my device last night and this morning, I decided to go back to stock for a bit.
I have ODIN 3.10.6. I went into download mode on my phone. extracted the stock firmware from this thread: http://forum.xda-developers.com/galaxy-s6-edge/general/sm-g925f-s6-firmware-thread-t3078841
loaded the "G925TUVU1AOCG_G925TTMB1AOCG_G925TUVU1AOCG_HOME.tar.md5" file into the ap box for odin
connected my phone to computer, odin recognized it. hit start. ran successfully. rebooted, android guy came up briefly and said installing system update, then it changed to "Erasing..." then it rebooted again
now it's just bootloops forever after the tmobile screen. I can boot to recovery and it says installing system update each time I boot to recovery, but selecting reboot system there shows a no command error. force the phone to power off... power on again to bootloops.
tried to go into download mode again and reflash everything through odin, same issue!
I started last night by rooting using chainfire, then installing TWRPv2, then I flashed the 5.1.1 ROM available from @eousphoros (sorry for the tag, just thought you might want to be apprised of the issues in getting back to stock after using the 5.1.1 ROM).
with 5.1.1 loaded, smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm in bootloop city
any help would be greatly appreciated
Click to expand...
Click to collapse
had the same issue ... did a factory wipe...(had lineage os 14 installed with gapps 7.1.1) flashed stock rom using odin(success) . stuck in bootloop(samsung logo fades in and out) pleaase help (sm-g900H)
Very usefull post, same issue, solved trough recovery->wipedata/factoryreset. Thanks!!!!
my s6 was freezing and restarting again and again, I reinstalled the firmware for odin and then it didn't encounter any problem for a whole day but now i have the same problem again - freezing and restarting
any help would be appreciated
I am already done with factory reset and wiping cache partition but still nothing turnout to be helpful
Hi Please help me.
I did everything that mentioned but no succes at all. Any new suggestion?
Btw my phone passing ODIN and stuck in "installing system updates then erasing"
hello
i need downgred g925t frome androide 7 to 6 or 5.1.1
can anyone help me
im flashed phone whit dis frimwer from anroide 7 G925TUVS6FRC1_G925TTMB6FRC1_TMB
im dawnloaded this frimwer 4Files-G925TTMB3EPD1-6.0.1-By-NoLoGiG but not work or not flashed have error
So my phone on day decided to randomly go into boot loop. Trying to use recovery to go to factory default resulted in the same bootloop.
Next, I Flashed twrp-2.6.3.1-hltetmo.tar successfully and then stock.
Here's the issue. While its connected into my PC, it gets all the way to the T-mobile sign at full brightness. But it only goes that far when it's plugged it in.
When I unplug it, it goes right back to a boot loop. And attempts to go to recovery results in it saying it's going to recovery, and then right back to boot-loop.
Now, I'm not sure which one I should be treating, the bootloop or my phone inablity to go to the flashed custom recovery.
Did you try flashing a stock ROM in Odin?
audit13 said:
Did you try flashing a stock ROM in Odin?
Click to expand...
Click to collapse
2 different stocks, same result.
Flashing was successful both time?
audit13 said:
Flashing was successful both time?
Click to expand...
Click to collapse
By successful, Odin said pass at the end and the phone restarted.
Try flashing the latest stock ROM with Odin and uncheck everyyhing except f reset time. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use the button combination to try and enter recovery.
If it still doesn't work, try flashing the latest version of TWRP and then use TWRP to perform a full wipe including the system, and try Odin again.
If it's still a no go, try flashing stock with a pit file.
audit13 said:
Try flashing the latest stock ROM with Odin and uncheck everyyhing except f reset time. When you see the word reset in the status window, remove the USB cable from the phone, remove the battery, replace the battery, use the button combination to try and enter recovery.
If it still doesn't work, try flashing the latest version of TWRP and then use TWRP to perform a full wipe including the system, and try Odin again.
If it's still a no go, try flashing stock with a pit file.
Click to expand...
Click to collapse
I'm using the XDA pit file I found in the BootLoopRecovery Heimdal file. Since it appear you need something the
BL file, should be the stock rom or the recovery. And does the one box check ruled applies as well here?
This one to be exact.
https://forum.xda-developers.com/showthread.php?t=2545009
This has always been reliable for me when flashing Samsung phones with a stock ROM:
use the original Samsung USB cable that came with the phone;
use Odin 3.07;
use a USB 2.0 port, not USB 3.0;
use the latest stock ROM from sammobile.com.
To flash with a pit file, put the pit file in the pit box, flash the ROM in the PDA box, only things checked should be re-partition (this is selected automatically when adding a pit file), f reset time, and auto reboot.
I keep getting, "Secure Check Fail : Pit" when the re-partition button is checked and the same problem when it's not. (Odin says pass, but it gets stuck at the T-mobile sign while plugged in, and unplugged, it goes back to bootloop.)
At this point, I would conclude that the memory chip is damaged. Was the phone dropped or exposed to moisture?
Kind of feeling the same thing as it was one random reset and hasn't been the same since. Not the mention the thing has tendency to go all Gambit playing card on me, so it really might be terminal.
Ty for the help anyways, somebody probably will find their answer in this thread.
NotReallyBrain said:
So my phone on day decided to randomly go into boot loop. Trying to use recovery to go to factory default resulted in the same bootloop.
Next, I Flashed twrp-2.6.3.1-hltetmo.tar successfully and then stock.
Here's the issue. While its connected into my PC, it gets all the way to the T-mobile sign at full brightness. But it only goes that far when it's plugged it in.
When I unplug it, it goes right back to a boot loop. And attempts to go to recovery results in it saying it's going to recovery, and then right back to boot-loop.
Now, I'm not sure which one I should be treating, the bootloop or my phone inablity to go to the flashed custom recovery.
Click to expand...
Click to collapse
Flash TWRP 3.1 for hlte...that recovery is dope! It will flash the newest cm 14 and other nougat roms. It won't flash tw roms though. You'll need TWRP 2.8.7 for that.