I have a Tmobile GS6 Edge,My problem is this I was restoring a TWRP backup, coming from [ROM][5.1.1][OF8] OZOP EDGE. I used this Backup numerous times. But the last restore sent me into bootloop. I'm on OF8 but I ran an OF6 tar file through odin (it's the only one I can get to pass and run successfully). Heres what happened I 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 I'm stuck in bootloop. 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. I force the phone to power off... power on again to bootloops.
smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm lost. I read to reboot to recovery, factory reset in recovery, power down option in recovery but I'm still in bootloop Hell. Just flashed G925TUVU3DOI1 with ODIN, same issue, wont boot past Samsung logo and now I am stuck with OI1 firmware. It will not allow me to downgrade to OF8 or OF6 for example. I have created and flashed successfully my own bootloader.img.tar file with Modem.img.tar.file as suggested. And yes im still stuck at Samsung logo. Any ideas? Please help. Update: I used the emergecy recovery option with Samsung smart switch and..... Blinking logo as usuall
Related
Hi guys
I just installed the GlamourS4 ROM and it worked great. I restarted it a few times and nothing seemed to be wrong. Now I tried to boot into recovery through the power menu, but that didn't work and I'm stuck in a loop with mz S3 trying to boot into recovery but failing to do so.
I already tries to take out the battery and put it back in, but it still tries to boot into faulty recovery. By the way I'm using PhilZ Touch recovery and I can enter download mode.
You can still flash an Odin Version of a recovery with Odin Form your PC. Look for a clockworkmod tar file in the development theead, you should also find flashing instructions there.
I will try and see if it works. Thanks.
Phone took a dump today. Was fine, then shut down, then wouldn't boot past boot screen. Enter safestrap, wipe all, no boot. Odin to stock mj9, no boot. Factory reset after doing in stock recovery, no go. After Odin the phone will get to the Verizon splash screen then shut down. Subsequent attempts to boot after that will not make it past the Samsung logo. It doesn't stick there, it just shut off. Odin completes succesfully. Any ideas?
vlx600d said:
Phone took a dump today. Was fine, then shut down, then wouldn't boot past boot screen. Enter safestrap, wipe all, no boot. Odin to stock mj9, no boot. Factory reset after doing in stock recovery, no go. After Odin the phone will get to the Verizon splash screen then shut down. Subsequent attempts to boot after that will not make it past the Samsung logo. It doesn't stick there, it just shut off. Odin completes succesfully. Any ideas?
Click to expand...
Click to collapse
Sounds like a partition curroption..Have you tried using Heimidall and flashing each image separately?
Also, you might want to bring it Verizon tell them it won't turn on..
But you can try what I suggested above..
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
yoda254 said:
My phone is a verzon note 2 on deodox 4.3 with twrp recovery. The phone only boots to teamwin logo and flickers on and off. my computer will not recognize my phone either at this point.This is what happened. Ive been having some 4g lte loss and unstable wifi issues to i decided to do a factoty reset. when i rebooted into recovery i was stuck at the twrp logo and it would constantly bootloop the twrp logo.. I restarted my phone and did a factory reset from under the general setting. At that point it rebooted int the twrp but continued to just stay at the logo and would not go into recovery. I pulled the battery and restarted the phone but from that point on it would only boot into the twrp logo and stay there. I can get into download mode but my pc (win7) no longer recognizes the phone so i cant attempt to fix this in odin. Im not sure what to do to get this phone to work properly at this point.
Click to expand...
Click to collapse
My guess is that when you rooted with CASUAL, it changed the Samsung device driver on your computer and you need to reinstall the Samsung driver to get the computer to recognize the phone again in download mode.
Underneath step 7 of section 1b on Droidstyle's restore guide, he discusses issue with CASUAL replacing the Samsung driver... and he gives a link to Jeremy Loper's fix... "If odin no longer recognizes your device, most likely Casual killed the driver for odin!! follow this tutorial for restoring the driver: http://www.youtube.com/watch?v=zzghcV8HVVk"
Once the computer recognizes the phone again, you should be able to use ODIN to restore back to 4.1.2 so you can root/unlock again with CASUAL. After you get the phone restored with Odin, I would recommend booting into Stock Recovery and wiping cache/doing factory reset before running Casual again... this would enure you are starting over with a totally clean slate.
If the above doesn't work, then here's a thread where I tried to help someone else who couldn't get their computer to recognize the phone.... maybe some of those ideas will help - http://forum.xda-developers.com/showthread.php?p=55833998
Good luck!!
1 step forward two steps back. I got my pc /odin to recognizes my note 2(changed usb cords). Then tried to odin back to stock 4.1.2. At first odin kept saying (odin not responding) and would ask to close the program,after several attemps i final got it to flash the 4.1.2 file. When i flashed the file and was at the point where it reboots, it would not get past the samsung note 2 logo and continued to flicker and not boot up even when i tried to put it into download mode like it said to in this thread. http://forum.xda-developers.com/showthread.php?t=2024207. When i tried to reflash the file it failed. when i attempted again it just hangs at setupconnection. Tried again and it failed. Btw thanks for the help mattnmag.
Got it working! i simply forgot to place the sch-i605 pit. into the pit section of odin when i flashed the 4.1.2 rom.
Similar problems
I was running AllianceROM 26. My phone had been spontaneously rebooting for a bit recently. Today, it started to spontaneously reboot again, but this time, it never got past the Galaxy Note 2 screen. After pulling the battery, I tried to boot into TWRP. It just hangs on the twrp boot screen for a few minutes but never goes into twrp.
I figured I would try taking it back to stock. So, I used ODIN to try and put 4.1.2 on it and a new PIT file. That appeared to work fine. I got no errors in ODIN. However, I still cannot get this thing to get past these boot screens, either the Galaxy Note 2 one or TWRP when I try that there. I have tried this twice now, once with re-partition checked and another time with re-partition unchecked (saw conflicting instructions on that so I figured I would try it both ways). I still am not getting past the boot screen.
Any help or ideas are appreciated as right now, my phone appears to be bricked and I am out of ideas.
so what was the solution to the teamwin flashing on and off after a factory reset? this is certainly not a solution, having to reflash the phone...
My phone is MDK and used to have TWRP recovery. I was flashing a rom (EMPTY GALAXY) via TWRP and on the reboot it got in the bootloop. The symptoms are:
Can't boot into recovery, simply goes into BOOTING RECOVERY loop
Won;t even start without a cable, I put a charged battery and didn't want to start with just battery.
I reflashed the emergency MDK image via Odin with success, but still can't make the past BOOTING RECOVERY loop. I tried with PIT and without PIT file.
The only thing I can get into is the download mode
Kies 3 says says unsupported phone, while Kies2 keeps trying to connect
Kinda running out of options
I have a Tmobile GS6 Edge,My problem is this I was restoring a TWRP backup, coming from [ROM][5.1.1][OF8] OZOP EDGE. I used this Backup numerous times. But the last restore sent me into bootloop. I'm on OF8 but I ran an OF6 tar file through odin (it's the only one I can get to pass and run successfully). Heres what happened I 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 I'm stuck in bootloop. 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. I force the phone to power off... power on again to bootloops.
smart switch didn't recognize the phone for a reset so I decided to go with the ODIN method and now i'm lost. I read to reboot to recovery, factory reset in recovery, power down option in recovery but I'm still in bootloop Hell. Is there a pit file I can run? Anything? Please help.
Just flashed G925TUVU3DOI1 with ODIN, same issue, wont boot past Samsung logo and now I am stuck with OI1 firmware. It will not allow me to downgrade to OF8 or OF6 for example.
Update I have created and flashed successfully my own bootloader.img.tar file with Modem.img.tar.file as suggested. And still stuck at Samsung logo. Any ideas?
Anything in this?