Hello,
I was on stock/rooted OC3, OTA'd to OE2, then rooted.
Here's a breakdown of what I did so far:
Original problem - Tried build.prop memory tweak which caused boot loop that I was unable to recovery from.
I did OC3 Odin, no service, would not activate, constant rebooting after about 30 seconds of use or plugging in USB to PC, with or w/o USB debugging.
I did the full OE3 Odin, from Sammobile, same results as OC3 Odin. Says "unknown" for Baseband in both cases and continuously reboots.
Then I flashed "Trailblazer101_925V_OE2_FLASH_ME.tar" but it still didn't work.
I've tried "Factory Reset" through Android and through the stock recovery, with the same results. At one point it rebooted and gave a message "due to failed factory reset....."
I don't know what else to try. Can anyone shed any light on this issue?
*edit* Today, of course after posting this threat I flashed "Trailblazer101_925V_OE2_FLASH_ME.tar" again and for some reason it stuck and it now seems to work.
Mods can delete this post, if need be. Thank you.
Related
To start, I was using I9000XXJP2 firmware on an unlocked samsung I9000 from Bell. I installed a lagfix a few days ago and everything was working fine. The phone was really slow and freezing a lot today so I decided to restart. Ever since then, the phone is stuck on the Samsung S screen (not the one with the triangle). I can get into download mode just fine and i tried reflashing XXJP2 using odin back onto the phone. Odin does everything fine up until i see a blue 'reset' on odin and the phone is in recover mode with the options asking for me to restart the system etc. I restored to factory settings from there and even cleared the cache and restarted but it is still stuck on that "S" screen at startup. Odin only says "pass" once the phone is disconnected. So as of yet I haven't been able to flash a working ROM back on the phone. If you have any ideas as to which ROM i should try, if you could place a link with that, I would be very grateful.
I've had this problem myself a couple of times (just happened today in fact).
Boot into recovery mode (vol-up, home & power). Do you see any error messages in yellow under the menu?
I was unsuccessful at reflashing any of the Froyo firmwares so I reverted back to the last official 2.1 firmware from Bell JH2. Since I was coming from a 512 pit firmware, I didn't repartition or specify a pit file. This ended up working for me. I've since flashed to JK3 and am about to go back to JPU.
Reply:
I actually do see an error message E:can't mount /dev/block/mmcblk0p1, Can't mount SD card.
I should mention that Im using the unlocked bell phone on fido. Will i lose the unlock if i downgrade? Also, if you could point me to the site where i can download bell firmware, that would be awesome. I went to samfirmware.com and they dont have canadian versions there.
Unless one of the pros comes by and says otherwise, I understand that's the error indicating internal sdcard issues.
However... if the thing is dead, you can't hurt it more by trying some fixes
You can get the official and unofficial Bell firmwares from samfirmware.com, you just have to look in the US section. You want the firmwares starting with "i9000UG". Here's direct download links for you:
JH2 (official 2.1)
http://www.multiupload.com/ZNBT2RY5Y0
JK3 (unofficial 2.2)
http://www.multiupload.com/WTZGSKJGPF
JK4 (official 2.2)
I've heard people flashing this via CWM but I haven't see the files.
Also, I've seen references to people saying their phones begin working again after this error msg after they've left the battery hour for hours.
Let us know how things go.
Reply:
No go. When i flash to 2.1, it just shows the "S" screen and turns off. When i flash to 2.2, does the same thing as my first post. I still can get to the download screen through all of this so I hope its not messed up too bad.
I tried several times this afternoon before it worked including clearing data/cache.
Although, I had a different error message so you might be SOL in the end.
called samsung
So I called samsung this morning and they basically said they won't repair it because Bell handles repairs. Since I dont have a bell account, I can't get it repaired. I keep reading on forums that if you can get into the download mode, if you see the battery icon when you plug the phone in, its not totally bricked so i still have hope yet everything I've tried doesn't work. I tried to adb into the phone in recovery mode and it detects it but says I dont have permissions to push files onto the phone. If anyone can tell me what possibly went wrong and if it is fixable, how, that'd be awesome because right now this is a very expensive paperweight.
hello everyone, this thread might seem like a repost to some of you, but since the answer has yet to be found on the other thread, might as well try asking about it myself
so i've got a galaxy s3 mini (the i8190 version, not the l or the n) it's in stock 4.1.2 international version. yesterday, out of nowhere the phone just keeps on rebooting after a few minutes of booting up ( it got to the lockscreen and home screen just fine, but it keeps rebooting after that). and i think, well might as well just flash something on top of this stock rom so i decided to get the cm11 from novafusion, along with odin and tried to flash it. it all goes well in odin, no problem at all (odin flashes green passed sign).
but the strange thing is, when the phone rebooted, it goes back to the stock rom, with all the apps intact and with stock recovery. so far, i've been trying to flash almost everything into this phone via odin and odin always says it succeeded but nevertheless, everything stays the same, i've tried flashing some custom roms, custom recoveries but it doesn't seem to work. and the flash counter never goes up, it still says "custom binary download : no"
i've also tried to go to stock recovery and tried to wipe data / factory reset the phone which it said it has done successfully but when i booted in, nothing changed. i'm still logged on as my account with all the apps and files intact.
this problem has also been asked here but no definitive answer seems to have surfaced there.
please, any help would be appreciated
Hello, i have been researching for this issue that i have for over a month now, and yet i haven't found any solution or even a clue on how to fix it, and im sure lots of people are having the same issue that im having, let me explain what exactly happened to my phone and what i exactly tried
i was running on 5.0.1 G920TUVU1AOCG, and at that time "Ping Pong Root" was not yet available, so the only way to root the phone was to flash the "g920t_of6_aou_kernel_v1.tar" witch i did and installed SU using "g925t_of6_aou_twrp_recovery_v13.tar" and the phone worked perfect after that, and after the 5.1.1 lollipop came out, i decided to upgrade to that, so i flashed stock 5.1.1 odin firmware and flash the custom kernel "g920t_of6_aou_kernel_v1.tar" to get it out the bootloop since it was flashed previously on it, it worked and booted up and all seemed to be fine, i also wanted to perform a factory reset, and here is where the PROBLEM started, i forgot to turn on OEM Unlocking in Dev options, so after the factory reset, the phone got stuck on the bootloop "Samsung galaxy s6; powered by android" and the only way to make it bypass this bootloop is by flashing the "g920t_of6_aou_kernel_v1.tar" again, but i cant flash that because i forgot to turn on the OEM Unlocking in the dev options, and every time i try for flash any custom recovery or custom kernel and will give me "Custom Binary (BOOT) blocked by FRP Lock", so now im stuck on the bootloop, i cant access the phone to turn on the OEM Unlocking, Phone is basically STUCK.
I have tried flashing all stock firmwares that are, i have tried flashing all available kernels, i have tried Factory resetting the phone and wiping the catch, i have tried every guide on XDA and nothing ever worked for me.
i apologize for the long explanation, but i just dont want people to think that i am repeating the same question over and over since a similar question was asked by other members on XDA previously.
Thank you very much for taking the time and reading my question.
Do you still have recovery mode?
EDIT: In this thread: http://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-t3152054 every person that had the problem fixed it by flashing the stock firmware. make sure you're flashing the stock firmware that's the exact same as the firmware when your phone worked. So if you were on OI1 for example, you have to flash OI1 firmware or it wouldn't work. Try a couple times too, I've heard ODIN can be wonky sometimes.
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
ameenz77 said:
Thank you for the reply, i actually did try all stock firmwares, it was on 5.1.1 OF8 before it bricked, and i tried that one too, no luck, flashing gives me successful, but phone is still stuck on the boot loop, i hope i can find a solution for this issue.
Click to expand...
Click to collapse
Try to factory reset in recovery and flash the tar trough ODIN again. If that doesn't work, try to restore it with SmartSwitch. A lot of people have success restoring their phone that way. If that doesn't work then I don't know.
My S6 edge is in a bootloop. I put off the 5.1.1 OTA for a while when my wifi would not turn on. Rebooted, still didnt work. I decided to do the update. installation went great but now its in a boot loop. I flashed the firmware (BOG7) using Odin. It worked. The phone was back on again but then it shut off after a few hours.
Its been stuck in the bootloop again. I flashed BOG7 again. Ive Flashed BOG9. Ive flashed the stock PIT. Ive tried ADB sideload. Smartswitch and Kies do not recognize the device. Of course, Ive wiped cache and factory reset. Attempted booting in safemode. All flashes were successful but when it reboots, It says "erasing" and goes to bootloop (Samsung powered by android).... Drivers are installed and working. MTP is not installed and I cant find the file.
Please .
same problem
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
I finally gave up on my GS6 Edge because upon carefully taking it apart for the 3rd time I noticed physical damage up by the wifi receiver and SIM card slot. My advice would be to try the things I tried (above) and, if it's not a hardware issue, it may fix the problem. Good luck.
beefriendly said:
I'm having the same problem with boot loop on g925v stock. I'm wondering if the op or anyone else can help!
No mater what I do, phone reboots after almost exactly 1min9 sec. Just enough time to select a language, but not get past the next "activation" screen.
Background: Phone has never been rooted, at first was on og5 and started freezing on the verizon logo, so I factory data reset, and after that nothing has really changed. knox has not been tripped, frp not tripped
First I tried flashing og5 with odin,
(of course checked md5, and odin=pass, then after flashing, I always tried several combinations of booting to recovery for wipe cache partition/ factory reset / and also power down by holding volume down and power button, then select boot in safe mode)
Then tried flashing og7, still boot loop
then tried flashing og9, 3 times, again, also many attempts of factory data reset/ wipe cache partition / safe mode.
I am starting to think this may be a hardware problem, BUT unfortunately I do not have samsung warranty available on this phone so I am pretty much stuck messing with it.
In researching the issue, I have run across quite a few similar freeze/boot loop problems all over the web, and never any real solutions, for both g925v, g920v, and other s6 models. I've also seen a stock s6 g920v that freezes randomly, flashing stock og9 never helped, owner was planning to replace the battery and see if that helps (I have not heard back).
I've tried looking at the boot log but I'm no expert. I know I can't downgrade, but I'm wondering if there is anything I can do with adb, or any other bootloaders that I could try flashing over the og9 (even if just temporarily, assuming I will flash stock og9 again after).
Thanks for any encouragement, help or advice.
Click to expand...
Click to collapse
Phone has been in the ****ter for the past day. Stuck on boot loop. I tried flashing the most recent stock firmware. It would not do it and kept throwing auth failed signs at me. I tried other stock firmwares for tmobile with no sucess. I Tried throwing them on my sdcard and installing through there in TWRP, but I keep getting md5 auth failures. I have wiped, factory reset, and cleaned house many times. Nothing works. Im at my wits end. Someone please help
I'm a guest to this forum..but same thing happened to me about 5 days ago. Last thing I remember seeing is the 5. update trying to take place and I was just about OUT of Internal memory (with NO microSD card). Phone just kept rebooting. I was able to do a Factory Wipe (Both in the OS and in the Recovery Mode)....Neither worked even though they appeared to be successful. Phone just came back with ALL of my data still intact. The other weird thing...I had about 60 seconds before phone decided to reboot each time. During those 60 seconds I was able to delete files, pictures, etc. to save space. As soon as the phone rebooted those same files were back! Very frustrating. Still having the issue.
im not sure what states either of you guys are in, but you can look on craigslist for people that do flashing. you make need to do a odin rebuild because the partitions are ****ed.
you can repair it yourself but with pure caution.
Have you tried flashing in download mode with your computer through ODIN? If twrp doesn't work, that's what I go to next.
You could also try flashing the firmware without the MD5 file and I believe twrp will skip the check. (not positive on this one)
Figured it out on my own. Flashed CF autoroot. Then flashed 5.1.1 which is the most up to date firmware. Im not sure if the issue was because I was doing 5.1.0 and didnt realize that was the most UTD version, or if CF to 5.1.1 was the trigger. Either way, it worked.