Related
Another day, another brick thread.
But here's the deal:
I followed these instructions, and made sure I had the most recent version of Odin (per the recommendation of other bricked threads that I looked at first before posting this).
I got my sboot from here.
After flashing the sboot (Odin says it's successful), I'm now stuck at the Samsung screen.
I can of course get into ODIN Mode by holding down+power+home. Odin3 will recognize it, so I then went back into Odin and flashed the most recent UniKernel. I'm still stuck at the Samsung screen though. It seems be thinking about something, because it's getting really warm. But I can't get out of the brick.
Like I said, I read a few other resolved brick threads and most were related to the Edge, and most of the suggestions were to use the non-edge sboot to fix it, and to make sure I used the most recent Odin (3.10.6). But I have a non-edge, used the non-edge sboot, and have the up to date Odin. Also, I didn't do a wipe or anything, so it's not missing an OS.
Any suggestions? Am I missing something?
You should be able to flash back to stock if you find the right TAR file.. Took me awhile to find my G920T file but it flashes me back to stock 5.1.1 every time I get stuck on Samsung screen after tripping KNOX
http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
So I stumbled upon the files for the nougat beta program for samsung on another forum that I follow. I just wanted to share this and know if this could mean anything as in a modified stock nougat for our phone or possible even a bootloader exploint found in this beta. Read the original link first for more details.
CAUTION
User Maherk from the forum said this on the flashing matter:
"One issue that I faced while flashing the device, is that Odin kept crashing when the process gets to system.img, which meant that I soft bricked my phone.
If that happened to you, don't panic, press volume down+power button for 10 seconds, the phone will show an emergency message, stay there, and plug the phone and flash the file again. Don't go back to the download mode, just stay on the emergency screen and flash it.
Another thing to consider, the zip file you get might have 4 files, AP, BL, CS, and CSC. If it does, then make sure to rename the AP to .tar instead of the .tar.md5
Good luck"
All credits below:
http://www.phonearena.com/news/No-place-left-at-the-Android-7.0-Nougat-beta-table-for-your-Galaxy-S7-Heres-how-to-sideload-it_id87665
Download to the Zip (2.06 GB):
http://downloadmirror.co/1KtH/G930FXXU1ZPK4-thanks-samfirm.net.zip
This is for the UK Exynos model. I'm fairly certain it won't work on Snapdragon devices, but would love for someone to tell me I'm wrong.
Have you flashed this on G930T?
atrix_noob said:
Have you flashed this on G930T?
Click to expand...
Click to collapse
I would've like to but I cannot as I need my phone for work. If someone would like to try this I would appreciate it very much but do be wary of risks that are posed with flashing Roms.
It will not work. It's like trying to put diesel in a gasoline engine.
I thought the same, this will not work.
First of all thank you for taking the time to read this. I've been struggling with this for a while and I hope we can resolve it somehow.
So here's what's been going on:
My Samsung S7 was an absolute mess for a few weeks, battery life was absolutely miserable (died 10 seconds after unplugging it from charger) but I just assumed it needed a battery replacement.
I've never attempted to root, flash or mess with my device in anyway, not after this issue has already occurred. One day I pull out my phone to check something and it's dead again, okay. nothing out of the usual.
I tried to turn it on and it would get stuck on the Samsung logo. I tried plugging it in and just leaving it and it would stay stuck on the Samsung logo forever. Please note at this point I have not tampered with my devices hardware or software yet.
I tried downloading odin and downloading stock ROMs from somewhere but that didn't work.
My phone is NOT rooted, USB debugging is NOT enabled.
The phone contains a lot of my stuff and I would prefer not to lose them. I was wondering if there was a way for me to retrieve my stuff before factory resetting it or throwing the thing away. The phone itself means nothing to me. I just want what's on it.
Any kind of help is appreciated, I really wanna get to the bottom of this. Thanks in advance to everyone.
How far into the Odin flash did you get? Because a stock flash still wipes data if you use all firmware files.
If you can get into recovery try the wipe cache partition option, this won't wipe any user data but might fight the boot issue.
If you can still get into download mode try flashing the BL and CP firmware files for your model/region/carrier/version and nothing else via Odin. Again flashing just these won't wipe, but may fix issues.
I'd recommend reading his guide before using Odin https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
When downloading firmware I'd recommend using a firmware resource like updato, sammobile or here on xda
Without USB debug and root you're limited in the tricks you can do to get the phone in a state to transfer files.
Beanvee7 said:
How far into the Odin flash did you get? Because a stock flash still wipes data if you use all firmware files.
If you can get into recovery try the wipe cache partition option, this won't wipe any user data but might fight the boot issue.
If you can still get into download mode try flashing the BL and CP firmware files for your model/region/carrier/version and nothing else via Odin. Again flashing just these won't wipe, but may fix issues.
I'd recommend reading his guide before using Odin
When downloading firmware I'd recommend using a firmware resource like updato, sammobile or here on xda
Without USB debug and root you're limited in the tricks you can do to get the phone in a state to transfer files.
Click to expand...
Click to collapse
I'm not entirely sure how far I got. I followed a tutorial that said to flash the BL files but I'm not entirely sure if it worked or not considering my phone wasn't rooted/didn't have USB debugging and didn't restart or fix the issue. I got the files from updato. I've tried wiping the cache partition but that didn't seem to fix it. I haven't tried flashing any CP on there as I didn't know what that was but I will try to do that today.
Should I flash new BL files and try again, and what are CP files/where do I obtain them? Thank you so much for your help.
If you get the firmware from updato, or sammobile it should come with 5 files: AP, CP, BL, CSC and Home CSC all in one zip.
I would say try flashing CP and BL from the zip, and for Odin flashing you don't need USB debugging or root etc. You just need to be in download mode.
So try putting the CP and BL files into Odin and flashing, the newer version the better, but anything thats the same as your android version i.e. if you're on Nougat than any Nougat BL should work
Beanvee7 said:
If you get the firmware from updato, or sammobile it should come with 5 files: AP, CP, BL, CSC and Home CSC all in one zip.
I would say try flashing CP and BL from the zip, and for Odin flashing you don't need USB debugging or root etc. You just need to be in download mode.
So try putting the CP and BL files into Odin and flashing, the newer version the better, but anything thats the same as your android version i.e. if you're on Nougat than any Nougat BL should work
Click to expand...
Click to collapse
So I got the firmware, the most recent I could find that matched my region/carrier etc. I ran it through Odin and it seemed to have worked. Odin said it passed and the phone restarted.
Then it showed that it was applying system updates or something. But then it stopped. It showed the android guy laying down and the words "No command" I tried figuring out how to resolve this but I couldn't find anything that could be done without having USB debugging already enabled. I can't think of anything else to try and I'm running out of options. If you have any more ideas I'd really appreciate it. It seems like such a waste to give up now when the phone is only soft-bricked and not completely useless.
Only extra steps I can think of will save the phone but lose the data
So the past couple days I've been learning what I can about rooting. Finally decided to give it a shot and well I can't seem to get ODIN to work correctly. It seems to always end with abl.elf and then failing at write. I've tried Comsy and a few versions of ODIN including the latest version.
I'm currently downloading the latest firmware for my phone which is what I was updated to.
I have the Galaxy s8+ SM-G955U originally through VZW. I remember the ending of my firmware was CRE9 so I found this version off of Samsclub: G955USQU4CRE9_G955UOYN4CRE9. I downloaded some stock files for my device because I wanted to reset my bootloader version so I could root and use PARTCYBORG's rom. That's when it seemed to start looping.
I have access to download and recovery if you need that information. I also have downloaded the latest samsung drivers for Odin. I'm pretty sure if I could get it to write I could fix this issue but I've gone through a hundred threads on this forum and I'm pretty much a bit overwhelmed now. Please help
EDIT: I think I've nearly gotten it, but I'm stuck now. Odin 3.12 and Comsy 3.12 seemed to get me close. I've ran into missing Home Binary and Fail! Model Mismatch. Trying a 3.13 version of ODIN and then calling it.
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
JeffDC said:
One of the frustrating things about rooting for the first time is 'what are the expectations' in how things 'should' go.
Make sure you are using the most recent USB drivers. Odin, for some, will error out on the first flash attempt. It sure did when I was first learning, and it still does now, however someplace that I don't recall suggested this:
Connect with Odin, and Odin will say your phone is connected.
Setup your flash pieces.
Then flash.
Odon will fail, but this time you will leave the phone connected and re-enter download Odin.
Doing the above got me and others past the Odin errors on first flash attempts. It sure was troublesome.
Hope this works for you.
Click to expand...
Click to collapse
hi I installed the image twrp 3.2.2.0 but by mistake on boot. how can I restore the boot? thank you
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Update: Turns out I must have made a mistake with the firmware I thought I had flashed, versus the one I was trying to flash and was failing. I downloaded the latest october firmware and it's currently flashing in odin!
This not be posted in development !
mchlbenner said:
This not be posted in development !
Click to expand...
Click to collapse
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
pleclair said:
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Click to expand...
Click to collapse
You forgot to flash all of them
BL, AP, CP, CSC
pleclair said:
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
Click to expand...
Click to collapse
Just because you have a lot of post you don't post question in development section.
587.saboor said:
You forgot to flash all of them
BL, AP, CP, CSC
Click to expand...
Click to collapse
I did flashed all of them. But it always fails. No matter if I select only BL, AP, CP, CSC... or all of them. Almost seems like twrp is preventing write or something else does.
It fails after a few seconds in the process. Is there any kind of log generated by odin? If so, where can I find it? I don't see much information beside that it fails.
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
supertac said:
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
Click to expand...
Click to collapse
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
pleclair said:
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
Click to expand...
Click to collapse
nope. NEVER flashed twrp once on the A5- the european firmware tripped it on the 520W