Related
Long story short, I messed some stuff up on my phone. I'm pretty surre it's not completely bricked, but I have no idea what to do. I'm able to boot into recovery and download mode. But in CWM I can't do anything. If I try to restore one of my Nandroids, it goes fine until restoring data, at which point it hangs and then reboots, but gets stuck at the initial boot logo. The same thing happens if I do a wipe. I booted into download mode and connected to PC Odin and flashed the SGN_XX_OXA_KJ1_FACTORYFS.tar from dr ketan's guide, but then when it rebooted, it got stuck at the boot logo again. And now when I connect to Odin and try to flash anything, it doesn't flash.
Obviously it's not completely bricked, but is there anything I can do to restore it?
Did your SGN_XX_OXA_KJ1_FACTORYFS.tar flash went all the way through? Did
you see succeeded: 1/failed: 0 message in PC Odin?
If you did, all you had to do when stuck in bootloop afterwards was to pull out your
battery, wait a bit, put it back in, boot into stock recovery and do a factory reset and
cache wipe.
freedomispopular said:
Long story short, I messed some stuff up on my phone. I'm pretty surre it's not completely bricked, but I have no idea what to do. I'm able to boot into recovery and download mode. But in CWM I can't do anything. If I try to restore one of my Nandroids, it goes fine until restoring data, at which point it hangs and then reboots, but gets stuck at the initial boot logo. The same thing happens if I do a wipe. I booted into download mode and connected to PC Odin and flashed the SGN_XX_OXA_KJ1_FACTORYFS.tar from dr ketan's guide, but then when it rebooted, it got stuck at the boot logo again. And now when I connect to Odin and try to flash anything, it doesn't flash.
Obviously it's not completely bricked, but is there anything I can do to restore it?
Click to expand...
Click to collapse
Does the Odin get stuck at datafs???and in cwm at /data???
chasmodo said:
Did your SGN_XX_OXA_KJ1_FACTORYFS.tar flash went all the way through? Did
you see succeeded: 1/failed: 0 message in PC Odin?
If you did, all you had to do when stuck in bootloop afterwards was to pull out your
battery, wait a bit, put it back in, boot into stock recovery and do a factory reset and
cache wipe.
Click to expand...
Click to collapse
Yes, that's the message I got. And then I went to flash it again (I guess that was the wrong thing?) and then it didn't work, like it wouldn't even connect, it would get stuck at SetupConnection. But I'm trying it again right now and it's working so I'll try what you said.
vijai2011 said:
Does the Odin get stuck at datafs???and in cwm at /data???
Click to expand...
Click to collapse
Yes, cwm gets stuck at /data.
Ok, it successfully flashed again. And I got this:
<ID:0/013> Added!!
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> factoryfs.img
<ID:0/013> NAND Write Start!!
<ID:0/013> RQT_CLOSE !!
<ID:0/013> RES OK !!
<ID:0/013> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/013> Removed!!
Click to expand...
Click to collapse
It bootlooped again, and with the USB cord still plugged in, Windows said something like there was a malfunction and it couldn't read the device, or something like that. Does that mean anything?
Ok, chasmodo, I did what you said and booted into recovery, but it boots into cwm, not stock. Still do a factory reset/cache wipe?
Yes, and reboot.
Ok so I did that, and it got stuck at "Formatting /data" and rebooted/bootlooped again.
That's odd, factory reset/cache wipe usually help to remove bootloops after PC Odin flash.
Any idea where to go from here? I really messed this up bad, didn't I?
It is time for any wannabe-flasher to make up your mind where to belong:
- to be a experienced flasher and not to cry about bricked phone;
- or to be USER of that phone and stop using any advice from devs. That means going back to GB and from there full wipe and continue using stock and wait for stock (ICS) for your region.
From what I see:
1) devs make contradictory statements;
2) devs deny that the problem seems to be only CWM related (incompatibility between stock ICS kernel and great works of devs);
3) devs are 100% glueless about what to do in practical terms.
I'm not crying about a bricked phone, and I'd consider myself to be a fairly experienced flasher. I've run into a seemingly serious problem that I've never had before, and that's why I'm here asking for help. I'm trying to go back to GB, but it's just not working. I've reflashed SGN_XX_OXA_KJ1_FACTORYFS.tar via Odin multiple times without problem, but now when I do it, it doesn't reboot. If you can help me in any way, I'd greatly appreciate it.
Ok, so I decided to try flashing the original firmware that it came with (N7000XXLA6_N7000XXLA4_N7000XEULA1_HOME.tar.md5). It actually worked, and it rebooted, and then went through the whole "Installing update package" or whatever it says. At one point it said "Can't access to '/system/csc/XEU/system/'." Does that mean anything? So it finished installing and rebooted but then bootlooped again. So I went into recovery, and this time it was stock recovery, did a factory reset/cache wipe, and it actually worked. But then when I rebooted, it still ended up bootlooping.
Here's the backstory. Skip to the next paragraph if you don't want to bother reading it. (Phone is GT-I8190N)
Originally, all was well with custom cyanogenmod kitkat from novafusion. I got a USB dac which didn't work with the kitkat I had. Phone freezes upon plugging in. So I decided to go to lollipop.
So I flashed cm12.1_golden.nova.20150627 into the phone with 2.8.0.0 teamwin recovery. (Couldn't update to 2.8.3.0 for some reason. Used Odin. Said PASS! But version stays the same in phone.)
Everything went well, I got lollipop running. I decided to do a reset in android through the settings menu.
Phone restarted and this happened (teamwin splash screen flashes): /watch?v=Wr-dlk7q06A (Newcomer can't post link... This isn't spam but if I really can't put links I'll remove it)
I admit I panicked and did some things I'm pretty sure screwed myself even further so here goes:
Went back to Odin and tried to flash a stock rom onto it. (I8190XXAMJ2_I8190ORGAMJ1_HOME) Unfortunately. I was dumb and didn't realize my phone was GT-I8190N and not GT-I8190. So I got the wrong stock rom.
Odin FAIL! with error stuck on "complete(write) operation failed."
The second time I tried it the error was "There is no PIT partition."
So I did Re-Partition with goldenxx + the stock rom. It errored at "nand write start modem.bin fail complete(write) operation failed"
I did finally realize I got the wrong stock rom. That flashed properly and stock rom is working. Not sure if the PIT thing blew something up. Anyhow, onto the next paragraph where the current situation lies.
So now it's in stock ROM.
I got Odin to flash CWM 6.0.2.7 then I tried to use that to flash the same lollipop I used before. It got the error status 7. Can't install this package on top of incompatible data. No file context detected.
I tried the delete assert line trick. Now CWM gives no error. I don't remember what it exactly said. I think it said Updating. Then installation failed. No specific error.
So I flashed TWRP 2.8.0.0 and tried to flash lollipop again. Again error. Can't install this package on top of incompatible data. Error executing updater in zip.
And that's about it. I have absolutely no clue how to continue this. All help is appreciated! Thank you for your time!
Have you tried flashing a different rom, lp or kk? Also rooting & doing full wipes, maybe jump from stock to lp is too big, I'm not too sure
Sent from my GT-I8190 using XDA Free mobile app
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Its hard to tell what version it was on previously since recovery wont even boot, but from how its acting i'd say it was on LP and bricked for a KK flash, so you flashing NCE(Kitkat) is doing zilch. Seeing as there is no option for you to root, and im assuming you arent interested in that anyway, i would just take it to bestbuy or the att store and get them to reflash it, just say you got it off ebay and it was like that.
Sent from my Tw5ted SM-G900A using Tapatalk
I took the phone to BestBuy and the guy there flashed it with 5.0.1 with the same results. Boots to the Recovery Booting. . . . screen for about 30 seconds and then reboots. My daughter is taking it to an AT&T repair center to see if they have any better luck.
Have you tried flashing the boot image?
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
Boot image. Not sure which file you are talking about.
Could you give me a little more information or a link to the file?
Re: Softbricked AT&amp;amp;amp;amp;T Galaxy S5
If you have the oc4 update zip, in the zip should be a boot image, create an md5 tar file from it then flash in AP. If that doesn't work, you flashed a bad kernel and may have to use jtag to fully recover. Or bring it to a repair facility to have them do it.
My daughter took the phone to an AT&T repair center and they also could not successfully flash the phone. The only OC4 update i have found is the G900AUCU3BOC4_OneClick..exe update and I do not believe I can extract the boot image from that update. Is there another source of the OC4 update available where I could obtain the boot image.
Thanks for the help everyone.
I'll look for the DL link. But if they tried flashing it, and it didn't work. You may be SOL.
Bogiemaker said:
I purchased a soft bricked sm-g900a phone off of Ebay with the idea of using Odin to reflash and recover the phone. Since the phone was purchased soft bricked I do not have a history on what firmware was running on the phone or what the previous owner flashed that may have caused the phone not to boot to the OS or into recovery. I am assuming the previous owner was on 5.0 and tried to downgrade and ran into problems.
Short description of the current state of the phone:
1. Phone will boot into Odin Mode and can be flashed using Odin.
2. Phone will start to boot to recovery but sticks at "Recovery Booting. . . ." and reboots after about 30 seconds
3. Phone boots to Samsung logo and reboots after about 30 seconds.
What works:
Using Odin I can flash the following without errors: After flashing the phone exhibits the behavior above.
G900A_OC4_Stock_Kernel.tar.md5,
G900A_OA1_Stock_Kernel.tar.md5
G900A_OC4_Stock_Modem.tar.md5,
G900A_OC4_Stock_Partitions.tar.md5
G900AUCU3BOC4_OneClick..exe - reboots to recovery and "Recovery Booting. . . ."
I can flash SM-G900A_pit.pit with Odin 3.07 but not 3.09 or 3.10.
What does not work.
Tried flashing G900A_Downgrade_to_NCE.tar.md5 - Odin reports error
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Auth)
Phone reports errors
SYS REV CHECK FAIL :Refer 2> Binary 1
SECURE CHECK FAIL : System
Tried flashing SM-G900A 4.4.2 G900AUCU1ANCE Firmware - AP_G900AUCU1ANCE_964333_REV00_user_low_ship_MULTI_CERT.tar.md5 in AP slot
Same errors as above .
Tried to use Kies to recover the phone. It goes through the process of recovering with 4.4.2 and crashes about the same place flashing wit Odin does.
I assume if I could get into recovery to do a factory wipe I would be able to get the phone to boot. I have read multiple forum posts and blogs on getting the bricked phone to work where most recommend flashing G900A_Downgrade_to_NCE.tar.md5 and then if you can't get into recovery to flash either G900A_OC4_Stock_Kernel.tar.md5 or G900A_OA1_Stock_Kernel.tar.md5 and then you should be able to get into recovery. This of course has not worked for me.
Does anyone have any idea how I might go about getting this phone to boot into recovery? Also is it possible to have the local AT&T store re flash 5.0 on the phone.
I know it is a risk buying soft bricked phones but I sure would not like to have an expensive paper weight.
Click to expand...
Click to collapse
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!
jebep said:
Hello! OP...are you still around?
Did you ever recover this phone?
I was in the same situation...maybe worse...and I was finally able to recover it.
Please let me know what happened with yours?
THANKS!
Click to expand...
Click to collapse
How did you recover yours?
Hello,
I recently tried to flash a stock NE4 Kernel onto my device and this ended up soft bricking it into a boot loop.
I have tried to wipe/factory reset my device already since I was able to get into recovery mode but to no avail.
I have tried to flash the stock ROM onto my device but I get a FAIL! (Auth) error in Odin. Specifically: G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5
At this point I could care less whether or not it's possible to root my AT&T S5 Active, I just want to be able to use it again.
... Please help, I'm super worried I won't be able to get it back.
My Device Model is SM-G870A
qq
JunSoHot said:
qq
Click to expand...
Click to collapse
-_- ... Thaaaaannnks
"Recovery is NOT SEANDROID ENFORCING" after CF-Odin rooting N910T3 run on M6.01
Just got a US Cellular Galaxy Note 4 phone. Did a factory reset and it run perfectly on T Mobile N910T3 Marshmallow 6.01 (stock). Must have been rooted before, but flashed back to stock firmware and unrooted. So I want to get it rooted again.
Without realizing the difference of rooting androids running on Marshmallow and previous versions, I downloaded the latest specific CF-Odin tool for N910T3, run it to root it. Quickly, Odin showed the green "Pass!" But the phone got stuck immediately after that when it proceeded to reboot with this error:
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
And the Galaxy Note 4 logo.
I removed the battery, waited for many minutes or a day. Power it on or boot to Recovery Mode always get to the above same error, so I cannot wipe data or do factory reset, as some suggested.
From above error screen, hold Volume down+Power+Home, I can easily get to the Download Mode. So I downloaded N910T3UVS2EPE2 (not the latest N910T3UVS2EPG2, as it's too slow from Samsung), but failed to flash it with Odin (3.11.1 or 3.10.6) with or without PC's Antivirus Off. And on the phone I got:
SW REV CHEKC FAIL : [aboot]Fused 2 . Binary 1
[1]eMMC write fail: ABOOT
Wonder if I can flash TWRP with Odin in such a state? Besides, I forgot and didn't install USB drivers for Galaxy Note 4. Could this be the problem? I have USB drivers for Note 2, and it seems the PC communicate normally with this Note 4.
Appreciate very much for any help!
Having the same issue. Can't even get the phone to flash the pit file or the stock software it fails every time.
Think the phone is Toast.
***Update***
Had to do some weird stuff to get it booted and running stock un rooted again. I ODIN flashed TWRP booted into recovery and formatted DATA, then I ODIN flashed the GP2 PIT file along with the newest version of the CF Auto Root at the same time (For some reason this is the only way the PIT flash would not fail, Then I ODIN flashed the [email protected] stock firmware, and it finally booted again. After not being able to boot for 2 weeks. Device is running the setup now.
Update:
I was too scare to take any actions on the phone for almost a week! However, yesterday I only flashed TWRP with Odin and it automatically rebooted back to normal!! Everything seems to be working perfectly again! The only exception when I boot it to recovery mode to TWRP, I still see a flash of the following error message before TWRP:
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Some how TWRP can pass the bootloop.
With TWRP I was able to root the phone, thanks to Rootmygalaxy.net, and did some backups.
Wonder if I can get rid of that error message by wiping Cache/data...?
You will get an error on that screen; kernel error or not seandroid enforcing error because it is not Samsung stock being used. There's no getting g around the warning that I'm aware of and it doesn't cause a difference on the phone running stock modified or just going all out and running any other rom.