So I flash another ROM to my tab last night (AOKP) and it was running great but I wanted to go back to Clean Rom. I flashed the new rom and wiped everything and anything as I always do with roms. After flashing Clean rom then wiping, I rebooted to a bootloop. I left it overnight and checked on it, and it was still in a bootloop.
I hooked up and started running Odin today to flash stock and Odin was stuck on recovery.img for 3 hours while I was at work. I came home and hit the power button on my tablet and within a few seconds it loads a screen "Firmware upgrade encountered and issue. Please select recovery mode in Kies & try again" Kies does not work on my PC so I cannot use it. Hitting power+volume up doesn't get me into recovery. I know it can be fixed but, how? I have looked all over for this same issue and cannot find much that will help. Any ideas?
*nevermind* finally found something that worked.
You should post the solution you found. It may help others.
Sent from my amazing 10.1 galaxy tab
Related
I have the 32 GB retail model of the galaxy tab 10.1 and it was working perfectly and I had no problems until I tried to boot it up today. It gets stuck between the Samsung animation and the Samsung logo. I'm not very great with fixing these kinds of things so could someone walk me through it?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
1canine2 said:
I have the 32 GB retail model of the galaxy tab 10.1 and it was working perfectly and I had no problems until I tried to boot it up today. It gets stuck between the Samsung animation and the Samsung logo. I'm not very great with fixing these kinds of things so could someone walk me through it?
Click to expand...
Click to collapse
what was the last update you did to your tab? any app or tweak?
I once had a similar problem but doing a wipe/factory reset from the recovery menu seemed to fix it for me and I've had no problems since.
Ok thanks, I just did a factory reset and now its back to normal.
How do you do a Factory Wipe and reset? I cannot get mine to take the ClockworkMod Recovery.... I have tried many times to install it and Odin says that it was successful but when I try to boot into the CWM... All I get is the USB fastboot or Odin again... any suggestions? I am trying to fix my Boot Loop issues on Galaxy Tab 10.1
novafreak69 said:
How do you do a Factory Wipe and reset? I cannot get mine to take the ClockworkMod Recovery.... I have tried many times to install it and Odin says that it was successful but when I try to boot into the CWM... All I get is the USB fastboot or Odin again... any suggestions? I am trying to fix my Boot Loop issues on Galaxy Tab 10.1
Click to expand...
Click to collapse
If you have fastboot that means your tab is Google I/O tab. So i believe the method may be different to install CWM for you. Google it
Hi guys! Can you give me a tip? Since yesterday my tab got caught in a boot loop. Didn't made any changes, just went into it. I have rooted it a long time ago. I can't get into recovery mode by holding power+up. All I can get it the download mode that first says "waiting for usb cable" and if I connect it to the PC it goes to "press the [START] of Odin3". Do I need to try the fastboot method and reset it to factory details? I've being trying to do that but no devices were listed... Or do I need to reflash something with oding again? Please, just give me a tip.
nightrave said:
Hi guys! Can you give me a tip? Since yesterday my tab got caught in a boot loop. Didn't made any changes, just went into it. I have rooted it a long time ago. I can't get into recovery mode by holding power+up. All I can get it the download mode that first says "waiting for usb cable" and if I connect it to the PC it goes to "press the [START] of Odin3". Do I need to try the fastboot method and reset it to factory details? I've being trying to do that but no devices were listed... Or do I need to reflash something with oding again? Please, just give me a tip.
Click to expand...
Click to collapse
Hey nightrave
I got caught in a bootloop the other day after updating to 3.2 from 3.1, my tab was rooted and running the starburst ROM. When I rebooted it it keeped getting stuck on the logo screen, and my device wasn't being recognized when I plugged it into my PC. I found a file online for the stock 3.1 firmware and flashed it using Odin and it got it out of the boot loop. If you can't go into CWM to flash a rom or do a recovery I would try using ODIN to flash the firmware your device was on. I ended up flashing the firmware for 3.2 the same way and the Galaxy Task 10 ROM. Let me know if that helps
app not working
i downloaded an app and it was working fine for a few days and now when i go use it i get an error msg and it kicks me out of the app. ive deleted and reinstalled app a few times but it still does it. what do i do?
Did u try goin on rom manager and clicking fix permissions.. its suppose to fix any force close issues, not sure if that would work.
I was able to fix my issue by installing a 3.2 rom. My tablet is not bricked anymore
Getting a com.android.phone error now but i'm trying to figure it out.
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
moraha1287 said:
I tried updating my ROM (to CM11) and came across so many issues. For some reason, it kept rebooting and then at one point just got stuck at the animation screen. So I decided to just start everything from scratch again.
I tried to get into download mode to install CWM, but the phone kept shutting off as soon as I got in. After MANY tries, I finally got in and got it installed. When it finally worked, I tried to get into recovery mode and the same thing happened. Finally after many tries I was able to get in there too. I then installed my ROM and then when it finally loaded, the phone then shut off and tried rebooting but wouldn't get passed the animation screen again.
I did a lot of research and found that some people had their internal power button either get stuck or become defective. Mine clicks so I don't know if that's the problem, but the symptoms that others have mentioned have all happened to me.
Does this in fact sound like a button issue to anyone? Any help is appreciated.
Click to expand...
Click to collapse
Seems like your hardware button could be broken, I would all do in this order:
Download Philz Touch Recovery from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9300/
Official Firmware from here: http://www.sammobile.com/firmwares/3/?download=28378
Flash Philz touch through Odin
Reboot to Recovery, selct "Clean to install a new rom"
Wipe cache and dalvik cache
Go to downoad mode and flash the md5.tar file through odin
Hi,
My problem started a couple days ago. I had my Samsung Galaxy S2 (I9100) charging overnight and when I woke up it was off. When I turned it back on it was stuck in a boot loop. I could not access recovery mode (although it would enter recovery mode and then drop out) but I could enter download mode. It was running a stock ROM and I had never played around with flashing before.
After leaving it for about a day without power nothing had changed so I started reading up about recovering from soft-brick and possibly the NAND read-write corruption at the guide on XDA here http://forum.xda-developers.com/galaxy-s2/general/guide-fix-unflashable-soft-bricked-gsii-t1449771
The guide is a bit old now so some links are broken which made it more difficult for me to figure out what I had to do. Particularly with what file should be going where.
I ended up downloading the same ROM that i think was already on my phone from samfirmware and tried to flash it using Odin (various versions) without success. I tried to flash just the kernel using heimdall which now stops me from even entering recovery mode. I tried to flash everything in the ROM from samfirmware using heimdall but it got stuck on the second file (cache) at 62%, the first file was the bootloader which it said was successful. However now I don’t even get the Samsung logo anymore. I only get "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I still have download mode so I have hope.
I haven’t tried repartitioning yet, is that my next step? Can someone give me instructions on how to determine what the problem is and what I should or shouldn’t be flashing? I’m not against going to a completely new ROM like cyanogen mod either. I need some help from people who have more experience with this.
Thanks for your help, I should be around to answer questions.
Same thing happened to me
Hi, almost the same thing happened to me - except that I was running Cyanogenmod 10 custom rom and I'm not being able to go into recovery mode, but I can go into download mode.
So far I've only managed to worsen things while trying to use odin to write a recovery kernel, so I had a bad firmware upgrade and now instead of powering up to Samsung logo it goes into the "Firmware upgrade encountered an issue" screen. But I'm still able to boot into download mode.
Did you manage to fix your phone? If so, how did you do it?
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...
Hi everyone.
Got Note Edge N915G which was running fine with Micky's MM ROM V3. As there was one problem- low incall volume in the ROM, I decided to revert to Stock firmware yesterday. Accordingly, I flashed Stock Firmware with Odin 3.12. Flashing went fine with Odin but I got this infinite bootloop. I am having this cycle of Phone turning on and logo appearing for two seconds and turning off again. I cannot go to stock recovery (shows <blue> "recovery booting' message and phone turns off) but can go to download mode fine.
What I have done so far:
-Flashing different versions of stock firmware (Lollipop and Marshmallow) by Odin 3.12. It completed with "Passed" message but the problem remains the same.
-Flashing by Samsung Smart Switch application. It completed 100% but the problem is same.
-Flash TWRP recovery by Odin. Then tried to install Micky ROM again but it could not complete. Device switches off at the stage of flashing of "system.img"
-Flash custom kernal also but no good.
-Thought it might be "Power button" problem, tried to soft press it various ways. But it does not seem so.
I have been flashing custom ROM for some time and thought I am good at it. But I cannot get the idea what the current problem is. So I would appreciate someone please help me out.
saviour555 said:
Hi everyone.
Got Note Edge N915G which was running fine with Micky's MM ROM V3. As there was one problem- low incall volume in the ROM, I decided to revert to Stock firmware yesterday. Accordingly, I flashed Stock Firmware with Odin 3.12. Flashing went fine with Odin but I got this infinite bootloop. I am having this cycle of Phone turning on and logo appearing for two seconds and turning off again. I cannot go to stock recovery (shows <blue> "recovery booting' message and phone turns off) but can go to download mode fine.
What I have done so far:
-Flashing different versions of stock firmware (Lollipop and Marshmallow) by Odin 3.12. It completed with "Passed" message but the problem remains the same.
-Flashing by Samsung Smart Switch application. It completed 100% but the problem is same.
-Flash TWRP recovery by Odin. Then tried to install Micky ROM again but it could not complete. Device switches off at the stage of flashing of "system.img"
-Flash custom kernal also but no good.
-Thought it might be "Power button" problem, tried to soft press it various ways. But it does not seem so.
I have been flashing custom ROM for some time and thought I am good at it. But I cannot get the idea what the current problem is. So I would appreciate someone please help me out.
Click to expand...
Click to collapse
Ummmm..........maybe your bootloader is your problem. i remember in 2014 my note 2 same problem as your.
When i update to 4.4 custom rom i need to back to 4.3 because of doesn't work the wifi so i back and boom...bootloop, i forgot to flash the firmware and bootloader and hey is working again.
So maybe you should Try out.
Sent from my Pixel 2 XL using Tapatalk
JohnMichaelCost said:
Ummmm..........maybe your bootloader is your problem. i remember in 2014 my note 2 same problem as your.
When i update to 4.4 custom rom i need to back to 4.3 because of doesn't work the wifi so i back and boom...bootloop, i forgot to flash the firmware and bootloader and hey is working again.
So maybe you should Try out.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thanks. Now I wipe out everything from the mobile. I Initiated software recovery process from the Smartswitch. The process completed to 100%. But still I am stuck in the bootloop. Now, device turns on, show blue "recovery booting" and samsung logo then turns off. It goes on repeatedly. Please suggest what to do...
saviour555 said:
Thanks. Now I wipe out everything from the mobile. I Initiated software recovery process from the Smartswitch. The process completed to 100%. But still I am stuck in the bootloop. Now, device turns on, show blue "recovery booting" and samsung logo then turns off. It goes on repeatedly. Please suggest what to do...
Click to expand...
Click to collapse
You should maybe take to samsung store to fix your phone.
Is my final answer can't helping your phone because i dont have a note edge/4 talk to the admin or samsung developer.
Sent from my Pixel 2 XL using Tapatalk