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...
Related
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
cugami said:
Hello
I have been using my int Gs3 for sometime and decided to root and explore the mods and custom fw world. I have started with getting to root access and after that install CWM.
Then I try to install nightly cyanogenmod 10. It didnt work and boot back to normal GS3 Touchwiz interface. After that I tried the GooManager and when the phone is restarted it went to bootloop. I removed the battery and put it back. The problem started there.
The phone does not boot to any OS, I only can see the galaxy s3 9300 black splash screen and awatis there. I can go into download mode, but when I go into recovery mode, I can see the Android robot, and it dies The screen is too fast but what I can see it cannot mount EFS, System and any folder.
So I have tried several different methods
- Tried to flash with original rom, different roms, CWM and what I can find suitable for international model. But everytime I got stucked in Nand Write part. In some of them, the flash started and stucked in installing some parts(passes the cache and hidden and stuck after that)
- Tried with bricked phone roms, different PIT files and Bootloader Vralec methods.
- When I am trying these, I have tried with 3 different PC's with/without KIES and Samsung drivers installed. When I plug the phone in Download mode, the PC recognizes it as Generic device.
- I manage to flash the CWM but when it restarts it does not go any further than the first splash screen, but in Odin, some time later it turns to pass. Funny, when the phone is on Galasy S3 black splash screen, the pc recognizes the phone and starts to install the driver.
So, here is an interesting flashing story of mine. I really would appreciate your valuable comments and suggestions.
Thanks in advance.
Click to expand...
Click to collapse
GO here : http://forum.xda-developers.com/showthread.php?t=1993044
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Varjo said:
Hello,
I have a S3 which is stuck in a bootloop at the samsung logo.
when i turn it on it shows the logo for some seconds then the screen goes black and the logo re-appears.
i can not boot into recovery mode, but download mode is working without a problem every time.
i tried flashing stock firmwares with odin and also tried kies emergency firmware recovery. the flashing always went without any problem, but it had effect. whatever i try, i am never able to boot into recovery and still stuck in the bootloop.
in some tries after flashing the screen just shows the samsung logo forever, but after rebooting it once it then is stuck in a bootloop again (shows the logo - screen goes black - shows the logo...)
i also tried flashing TWRP and CWM via odin, but again i can never boot into recovery mode.
what should i try next?
thx alot for any helpful comment
Click to expand...
Click to collapse
You can Try this:
1.) Pull out battery
2.) Put it in again
3.) Press Vol up + home + power
4.) When the Samsung Logo appears let it off
I think you press the Buttons too long.
I had the same problem!
S1ay3r666 said:
I think you press the Buttons too long.
Click to expand...
Click to collapse
i really tried everything, it's not working. btw with i am stuck at the very first image, where it says "samsung Galaxy sII GT-I9300".
i dont think it's just the way i press the buttons because i can reach it on my s1 and s2 without a problem, it's just not working on this device.
could some setting like "nand erase all" in odin help? in other threads there is sometimes mentioned that the internal file system might be screwed up and in those cases a simple odin reflash does not help anymore...
Nand erase will usually hard brick it. Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Try the rescue firmware from general forum, sticky thread. Follow the guide exactly as it includes a pit file.
Click to expand...
Click to collapse
thx, but i already did that (multiple times) and flashing via odin always succeeds. then the phone reboots and is stuck at the first samsung galaxy s.. screen. twice i managed somehow to get into recovery (after flashing cwm6) but it then randomly rebooted.
and i dont think that the power button is stuck because when i am in download mode it is perfectly fine it never reboots itself unexpectedly.
Had a similar issue on my tab2 p3100. It all happened when I tried flashing a custom recovery from rom manager.
A bad flash of anything related to recovery or bootloader could be a probable cause.
I remember a knowledge share on one of the threads describing this issue and as mentioned on it all I had to do is this:
1) switch off the device and plug in the charger. This would light up the display showing you the charging status. The status has to show if at least your bootloader part of the phone is fine.
2) plug out the charger and immediately press the three buttons (home + vol up + power) get into recovery mode. This step has to work and help you get to recovery mode.
***Note : the interval within which this step has to be performed is too short since the display would turn off immediately as soon as you plug out the charger. A bit tricky too so you have to be fast. If this misses getting you into recovery, pull out the battery and put it back again. Repeat step1 and 2 again.
3) upon successfully getting into recovery, perform wipe data, cache and select reboot phone from option available on recovery again.
Allow the device to boot. This could take a while since you have performed a data wipe and may prompt for first time set up.
I was able to restore functionality on my tab after these steps and like ppl learn from their mistakes, I then learnt that recoveries and bootloaders are things that needs to be done with a pc only.
Worth a try if you have tried other alternatives and found no go. may help. Who knows..
all the best.
thats also not working. i tried to get into recovery since two days now...
i also tried the steps from this thread: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367
but again, after i flash the cf-root (successfully) the phone does neither boot into recovery by itself nor can i do it by hand...
its crazy... in download mode i can see the model number (GT-I9300) and i thought as long as the model number is there and i can enter download mode there should be a way to recover the device.
but i cannot think of anything to try that i have not done yet
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Sent from my GT-I9300 using Tapatalk
boomboomer said:
If the rescue firmware didn't help then it looks like the emmc chip is damaged.
Click to expand...
Click to collapse
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Varjo said:
is there a way to make certain of this? how can i tell if it is really a hardware damage and not just a software brick?
i just dont want to let the phone go, it looks still so shiny
is there anything else that could cause the phone not booting into recovery mode after flashing custom recoveries?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gala...-help-t2737707
Same here, still didn't found how to fix it.. I guess our motherboard just died..
Howewer I have a solution that "almost" worked for me.
Get a stock firmware in odin and turn on Nand erase and T-flash
When it's done phone reboots and you'll see just "Downloading..." mode when you turn it on.
Then got to Kies and Select firmware recovery...
Enter s/n and model name and wait for the flash to complete.
With it , I got past boot logo and actually booted into android but the phone crashed because I guess I have a memory issue..
Well , gl. If you don't find anything else helpful , try going with this method..
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?
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