I have a strange boot loop issue (GT-P5210) Tab 3 10.1
I tried Philz CWM and TWRP and some flashes via Odin
I tried to install stock ROM's and pre-rooted Stock ROM's of different versions from sammobile and here on the xda forums and samsung-updates dot com
I tried a few recovery version's as well
And finally, thinking my partition table got screwed up I even looked for hours and found the pit file and tried that along with a recovery
The recoveries I tried are both through Odin and through TWRP and CWM, and my results vary slightly but never result in a good full boot.
Sometimes the tablet reboots upon the Samsung logo
Sometimes the Tablet tries to boot and even gets the Blue splash but just sits there endlessly without rebooting but at the same screen
I am at a loss as far as what to try next, what version, and in what order.
Anyone else experience this or have any direction they can please put me in?
[update]
I found that with latest TWRP 2.8.6.0 and no other recovery can I successfully flash CM12 and have it boot correctly, so how the heck do I get stock back on here? I am completely confused now.
I fixed it, took a bunch of trial and error and trying different ROM's from sammobile but also needed stock bootloader to fix the denied access to \data by properly wiping it, doing so from TWRP and CWM failed to fix it, only fixed from stock.
Related
So my note 2 had been working very well, but just the other night it turned off and then was stuck at the Samsung logo screen. I attempted to boot into recovery, but it would freeze at the TWRP logo screen. I decided to Odin a new recovery and put the latest version of TWRP on there. I can now boot into recovery, but it asks for a password. I assumed I had just used a bad version, so I tried several others which resulted in the same outcome. Pressing cancel lets me get into TWRP, and it seems as though I can browse files, but trying to perform any other action gives an error message saying that TWRP cannot find the partition for data, system, and a few others.
Is the phone dead? Or is there something I can do to bring it back to life?
captterrible said:
So my note 2 had been working very well, but just the other night it turned off and then was stuck at the Samsung logo screen. I attempted to boot into recovery, but it would freeze at the TWRP logo screen. I decided to Odin a new recovery and put the latest version of TWRP on there. I can now boot into recovery, but it asks for a password. I assumed I had just used a bad version, so I tried several others which resulted in the same outcome. Pressing cancel lets me get into TWRP, and it seems as though I can browse files, but trying to perform any other action gives an error message saying that TWRP cannot find the partition for data, system, and a few others.
Is the phone dead? Or is there something I can do to bring it back to life?
Click to expand...
Click to collapse
Try to flash a stock rom with Odin.
If this does not work you are facing a compareable problem to mine http://forum.xda-developers.com/showthread.php?t=2440687 .
Maybe you find a way to get it work in this link.
Sounds like SDS
Luke44 said:
Try to flash a stock rom with Odin.
If this does not work you are facing a compareable problem to mine http://forum.xda-developers.com/showthread.php?t=2440687 .
Maybe you find a way to get it work in this link.
Click to expand...
Click to collapse
I just read through that thread, I'm not sure where I could find the correct pit mapping for this phone though =/
muppetmania said:
Sounds like SDS
Click to expand...
Click to collapse
I really hope it isn't SDS. I can odin a recovery onto the phone, but so far other odin-able images just fail. I'm downloading a pure factory image currently and will check to see how that works,
I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.
According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
I am trying to fix a Samsung Note 2 (Model No. SGH-i317) that refuses to boot.
When you push power, the white Samsung logo appears and just stays there until you pop the battery and remove USB power.
It will not go into the recovery menu after pushing Power+VolUp+Home.
It will however go into download mode after pushing Power+VolDn+Home. Once in download mode I tried to update the kernel to no avail. I also tried to install CWM thinking that maybe installing a new recovery over an old stock one that was corrupted somehow might help. Both approaches did nothing.
The device was originally running stock Samsung; I never attempted to load another ROM until this problem hit. So the phone was just as it was from the factory two years ago when this problem recently hit and I have been trying to fix it. After trying to flash the aforementioned things, the counter on the download screen (i.e. Odin), now shows the number of different times I have tried to update the recovery or the kernel, which is currently at four or five.
So, some aspects of the phone are working but clearly not enough for me to even get it to recovery, let alone boot. Any advice? Many thanks in advance.
roll-back said:
I am trying to fix a Samsung Note 2 (Model No. SGH-i317) that refuses to boot.
When you push power, the white Samsung logo appears and just stays there until you pop the battery and remove USB power.
It will not go into the recovery menu after pushing Power+VolUp+Home.
It will however go into download mode after pushing Power+VolDn+Home. Once in download mode I tried to update the kernel to no avail. I also tried to install CWM thinking that maybe installing a new recovery over an old stock one that was corrupted somehow might help. Both approaches did nothing.
The device was originally running stock Samsung; I never attempted to load another ROM until this problem hit. So the phone was just as it was from the factory two years ago when this problem recently hit and I have been trying to fix it. After trying to flash the aforementioned things, the counter on the download screen (i.e. Odin), now shows the number of different times I have tried to update the recovery or the kernel, which is currently at four or five.
So, some aspects of the phone are working but clearly not enough for me to even get it to recovery, let alone boot. Any advice? Many thanks in advance.
Click to expand...
Click to collapse
Try to odin the stock firmware then before it boots up boot into recovery and wipe dalvik and cache then boot it up.
Flashing Kernel did not help
cnote74 said:
Try to odin the stock firmware then before it boots up boot into recovery and wipe dalvik and cache then boot it up.
Click to expand...
Click to collapse
I run Linux and don't really have access to a Windows box and have been using heimdall to flash things. When you said
"Try to odin the stock firmware"
Click to expand...
Click to collapse
is that the same as trying to loading a kernel image and then going to recovery before it fully boots? If so, I tried that with the following command using the image I downloaded from sammobile.com. This is the command that I ran:
Code:
heimdall flash --kernel KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar.md5 --verbose
That resulted in the same as when I tried to flash a new CWM recovery. It doesn't allow me to access the recovery, it just boots and shows the white Samsung logo and hangs there till you pop the battery & remove the USB cable.
If what you are suggesting is something different than the flash that I did with the image from sammobile.com, please let me know. This is my first attempt to fix something like this. Many many thanks.
So my issue is pretty similar, see what you guys think. i been trying everything i can think of.
i updated from xtrestolite 2.1 to 2.2 with out wiping. everything worked fine except when i would make calls, the other people could not hear me. so i updated the bootloader and modem again (i had done it before) and the problem persisted. i flashed back to stock and was getting stuck at the s6 edge screen. the only way to get around this was and get my phone to boot was to flash aou kernel. i was still having a similar issue with calling so I download a modem from a diffrent server and all of a sudden, it was working again on stock firmware... AWESOME!
now that i had all that done and my phone working as it should, i reset my phone for the first time and i got the FRP lock, wont boot phone because custom kernel. GREAT
I then flashed stock of6 again, the tar ball, and the 4 piece version. no dice
i then found of8, tried to flash that still no dice.
id love to flash twrp and load a rom on, but FRP is a alsjdflajs.
the phone will flash successfully, but upon reboot, it will go into recovery, run its course, reboot, and get stuck that the galaxy s6 edge screen.
i use the vol and power click during recovery to see what its doing and everything seems to go fine. it will then say failed to mount /data. im hoping flashing this with the pit file will work, but i cannot download the pit file from my work computer (hahah its blocks on 4shard and mega).
anyone have any other advice? i will update if i figure it out.
Regards team,
-Mad
p.s. none of this is xtrestolite's fault, that rom has been nothing but good to me.. my phone has been picky though. after 5.1.1 i had to flash a custom kernel in order for the digitizer to function properly.... any help is appriciated guys.
SO UPDATE!
nothing good, i tried the pit with of6 and of8, no dice. still stuck.
anyone got a s6 edge w a broken screen? you can claim it lost for all i care.
no one?
i guess if anything past flash stock firmware people dont know? was hoping for alittle more insight.
im sure if i could flash a kernel i could get it to turn on, but FRP has be at bay...
no help for you bro...Samsung just needs to release there software fixing for this comunity...I'm looking a for a dev to answer my question in this section about just flashing zip files in twrp instead of using odin or whatever other methods that can avoid all these problems that are all similar...hopefully in next few months it will be addressed
Hey mate, try this...
http://forum.xda-developers.com/showthread.php?p=61531848
Sent from my SM-G925T using Tapatalk 2
holy... fu34%# /S45it.... IT BOOT?!
after flashing every firmware 100000 times...
THANK YOU!
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.