Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
shaharofir said:
Do you have TWRP installed? Try flushing it. You can also follow Dr. Ketan ROM installation guide, it's very straightforward.
Click to expand...
Click to collapse
I don't. I was looking at that post earlier and noticed that it mentioned the G998B/N model. Mine is the G998U1, so I was worried that it wouldn't work or cause more problems. I couldn't find any versions of TWRP that matched my specific model.
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
ffuser1 said:
your bootloader version is above v1. cannot be unlocked. you need to flash a samsung rom. try redownloading it if you can't boot. and twrp probably won't work either.
you're saying that if you hold the vol up key and power button when the device is off that it won't reboot into recovery at all?
Click to expand...
Click to collapse
I was actually able to get it to boot into recovery mode this morning. The download mode timed out and the phone shut off which allowed me to finally get into it. I tried redownloading the same rom I got from sammbolie again a few mins ago but still no luck.
Try another firmware with the same BL revision, CVC9 for example
dipotis said:
Hi, I need some help flashing my device. Somehow, my device got stuck in a boot loop last night, and I've been having trouble getting it to work again. I think my phone may have reset during an update while in my pocket as I was laying down on the couch last night.
I found my device firmware on sammobile according to the specs listed below. I've downloaded Odin 3.14.4 and have flashed my phone successfully 3 or 4 times at this point, but when it restarts post-flash, it keeps booting into download mode. I can't seem to get it to boot into recovery mode or just turn it off at all anymore. No matter what, it boots straight into download mode.
Does anyone know of a way that I can force it into recovery mode so that I can try restarting it normally? This is my first time flashing a phone, so I have little experience here though I am competent with technology and willing to try further tricks to get it working.
I'm just looking for recommendations and hoping that my phone isn't bricked. I've only owned it for 3 months at this point, so I'm very disappointed.
Thanks in advance for the help, and I'm happy to provide any more information if it helps you come up with any potential solutions.
Specs
Phone: Samsung 21 Ultra
Model: SM-G998U1
PDA: G998U1UES5CVCB
Carrier: XAA
Text on download mode screen:
<!>
partition recovery
Reason avb.slot_verify.c:276: ERROR: recovery: Hash of data does not match digest in descriptor. [2nd]
Calculated Hash of (recovery) : 9C3B9F195F, (VEMETA) : 1C38BF9F7A
Samsung recovery, G998U1UES5CVCB, 50338466R
VBMETA G998U1UES5CVCB, 50341365R
Click to expand...
Click to collapse
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
JG96EVO said:
Was your phone carrier branded originally? And you're flashing the u1 firmware so you won't have bloat? Or is it originally an unlocked model? I ask because if it was originally carrier branded and you used the Odin version from the SamMobile site then that may be the reason. U need to use the modded version of Odin that's floating around somewhere. If you need it I can upload it to my drive and let you download that version. I literally just flashed VCB last night and everything worked just fine.
Click to expand...
Click to collapse
No, I bought my phone directly from Samsung, and I bought the unlocked model. I chose the rom from sammobile that looked to be exactly what my phone originally had on it based on the model and PDA/carrier info I found when looking through the recovery logs on the phone when the issue first occurred, before flashing anything onto it. If you think the modded Odin might work, I'd be willing to give it a shot.
I can't tell you the exact differences, but I would flash with the patched odin. it's on xda if you search for it.
No luck so far. I've downloaded the patched Odin software and have tried flashing my device numerous times with the same result. I also tried tried flashing firmware that I found on Frija instead of the firmware I originall downloaded from sammobile to see if anything would be different, and that didn't seem to make a difference.
My best guess (could be wrong) is that it doesn't like the bootloader tied to the firmware I've tried to flash onto the device. I've spent a good while searching firmware that uses the version of the bootloader it wants, but I can't find it anywhere. At this point, I'm all out of ideas, but I appreciate everyone's responses and advice.
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
You can extract the CSC file using 7zip. In there you will find the PIT file and you can try flashing it with repartition selected and inserting the PIT file in developers section of Odin.
ffuser1 said:
So this is what you are saying: You're using patched odin (https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/) to flash an official U1 Samsung rom (https://samfw.com/firmware/SM-G998U1/XAA/G998U1UES5CVCB for example) in the AP slot, all other slots are empty, without any odin errors during flash, and are then unable to boot, with partition errors seen in download mode? This is very unusual... flashing in download mode overwrites partitions, including recovery. I would assume if there are no odin errors, then the rom file is not corrupt and the sd card is not damaged. I don't know much about flashing through odin with a locked bootloader, maybe unpatched odin with the above instructions is worth a shot. I'm out of ideas aside from the sd card being damaged or trying unpatched odin if the above instructions with patched odin are resulting in recovery partition errors. I don't think you can access adb in download mode either.
Click to expand...
Click to collapse
Interesting. I did not try it with only the AP slot populated. I thought you needed to always flash with the BL, AP, CP, and CSC.
wait, i messed up. if it has all of those files, flash them. my bad. i was thinking about custom roms - sorry about that.
Hey everyone, just wanted to make a final update.
I ended up bringing my phone into ubreakifix after trying just about everything I could, and they were not able to fix it either. They suggested that it might be a hardware issue and recommended sending it to Samsung for repair. I then sent it over to Samsung, and they confirmed that it was an issue with my motherboard. Samsung replaced my motherboard, and the phone is back in action. Since I only had my phone for about 6 months, it was still under warranty.
I appreciate everyone who took their time to provide me with advice. I hope that this post may help someone experiencing a similar issue to mine in the future.
Related
ODIN MODE
PRODUCT NAME: SM-G925A
CURRENT BINARY: SAMSUNG OFFICAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
SECURE DOWNLOAD: ENABLED
KNOX WARRANTY VOID: 0 (0X0000)
AP SWREV: B: 4 K: 3 S: 3
Good evening,
First time poster long time reader/browser. Before posting this message I have read all other posts/threads in an attempt to fix this issue. Long story short I busted my old Samsung Galaxy S6 Edge SM-G925A AT&T and bought this one used online. The seller never mentioned it was bricked as all pictures posted of it showed it operating and at least booting up. When I received phone I turned it on and it is stuck in a boot loop. I have tried to boot in recovery mode by pressing VOL UP+HOME+POWER button and it does nothing. I am only able to boot into download mode. I have attempted to flash multiple stock firmwares which 3 have been successful and passed in ODIN, however once they pass and the phone reboots it is still stuck in a boot loop. I have been successful in flashing the below firmwares. I do not know anything about the phone besides the IMEI number, S/N, SKU and manufactured date. I do not know what firmware was on the phone originally and do not know what was flashed on phone when I received it (I'm assuming phone was flashed or rooted before due to the above stating SYSTEM STATUS: CUSTOM) Am I stuck with a bricked phone? I've attempted flashes with PIT Files, w/o PIT FILES, with just the AP file, with all 4 BL, AP, CP and CSC files and each time it gets in a bootloop. Can someone please assist me? I've read that sometimes all is needed is to wipe the cache in recovery mode and that would clear bootloop, but I cannot get into recovery mode. Any suggestions. Again, below are what I've flashed successfully but continues to bootloop. Thank you all in advance.
G925AUCS5DPJ1--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
G925AUCU3BO12--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
G925AATT3BOJ7--SUCCESSFUL ODIN FLASH-STILL BOOTLOOP
I will say after flashing the DPJ1 files I can no longer flash the BL file for either of the 2 firmwares below it (the AP, CP and CSC files all still flash successful).
I'm just about to give up and shell out the money and buy new phone. Was just hoping someone on here could provide me some advice, some sort of miracle file or a way I can odin flash a tar/md5 file that will wipe my cache/system cache like it would as if you did it in recovery mode.
OH! Also Samsung Smart-Switch will not recognize the phone. I'm able to input the model name and S/N in the emergency software initialization but as soon as I input the S/N and click ok it immediately crashes and closes out Smart-Switch. Thanks Guys!
Paul
You need to find a Marshmallow odin file. The phone has most like;y already been updated to Marshmallow in the past. Once on MM, you cant go back to Lollipop which is what those 3 files you listed are.
Edit, NM....that PJ1 file is marshmallow. Try taking it to Best Buy and having them reflash it with the latest MM file.
Thank you, I will try that. I have tried taking to AT&T but they wouldn't help at all. They said since I'm not AT&T customer then I'd have to go thru Samsung. I'm aggravated. I've been working on this off and on for 3 months now. Thanks again for the reply. I've read a lot of people saying after wiping cache partition and rebooting it fixed bootloop after successful flash.
You said I could go back to Lollipop. If I use anything other than the 3 files I listed Odin will fail with various,
Secure Check fail message. Do you know if anyone has created a Odin file that will successfully wipe the cache partition like it would via system recovery?
Thanks again for the reply.
Any updates on this ? I'm having the same issue with my G925I.
why don't you try to flash the DPK5 update from ODIN in the nougat update thread. that's the latest ODIN file I think
saketkutta said:
why don't you try to flash the DPK5 update from ODIN in the nougat update thread. that's the latest ODIN file I think
Click to expand...
Click to collapse
No matter what I flash , it's always stuck on the s6 edge logo.. And I can't enter any recovery be it stock or custom recovery. All I can do is enter download mode and flash official ROMs but none seem to work.
Thats some unfortunate situation. I don't know what to do. If official roms don't boot then it's permanent brick I think. Any senior devs know what to do?
Sent from my SAMSUNG-SM-T337A using Tapatalk
I am suffering from the similar fate,, its a friend mobile whose stuck on Samsung logo, he tried to fix it with Kies and Smart Switch and it did not workout for him.
The phone does not boot into recovery. I tried flashing G925AUCU1AOCE and G925AUCU3BOJ7 stock firmwares but no luck.
I successfully flashed G925AUCU6EQCF but it is still stuck on Samsung Logo
Any help or suggestion would be welcome
edit 3rd: Ok now I have managed to flash G925AUCS5DPJ1, still it won't boot into recovery and it is looping to Samsung logo
Same for me ... The recovery is not accessible and the phone reboots in a loop, Smart Switch tell me that the S / N does not match the phone model ...
Hi there!
So my Note 4 died on my eyes and it was greatly missed. So I decided to buy Note 5 and got one. Old one was running Cyanogenmod for 3 years without a fail.
Did not read about releases in Europe. Apparently there is no m920F. Download mode said it is N920T.
Things I've done:
Installed TWPR (TWRP-3.0.2-1-G928T-N920T) with Odin (Heimdall used for PIT file).
Checked was it installed - reboot. Then bootloop started.
Tried to flash a couple of firmware ROMS thrugh Odin. No luck.
Used ADB to transfer firmware rom downloaded from Sammobile. Tried to flash with TWRP. Got "coulnd't find META-INF/com/google/android/update-binary in the zip file"
Things I haven't done:
No backup.
Did not check OEM unlock.
Did not spend a day reading how to do it properly.
It's been a while since my last encounter with custom roms and installing them. I spent all night trying different things, to no avail.
I appreciate the fact that this is common and quite boring issue, so I'm offering a tenner ing GBP (PayPal transfer) for whoever will make my phone work again
I tried again to flash with TWRP to check for exact error this time. But it turns out, that the file with firmware pushed previously is not there any more.
Firmware downloaded is a read-only zip file, so I can't flash it with Odin either.
Tried adb sideload and got the same error - could not find meta-inf/com/google/android/update-binary.
Any ideas, please?
lukja123 said:
I tried again to flash with TWRP to check for exact error this time. But it turns out, that the file with firmware pushed previously is not there any more.
Firmware downloaded is a read-only zip file, so I can't flash it with Odin either.
Tried adb sideload and got the same error - could not find meta-inf/com/google/android/update-binary.
Any ideas, please?
Click to expand...
Click to collapse
First of all see if ur phone can get into download mode. If YES and since your phone is 920T then download the latest firmware from sammobile. Extract the files inside the folder and flash firmware using ODIN method & try.
maheshhtc said:
First of all see if ur phone can get into download mode. If YES and since your phone is 920T then download the latest firmware from sammobile. Extract the files inside the folder and flash firmware using ODIN method & try.
Click to expand...
Click to collapse
Yes I can get into the download mode.
I read some posts on sammobile and the problem with unziping the zip file might be connected with slow download, resulting in corrupted file.
I'll give it a try after work.
Thanks!
Ok. Better download during night time after 11pm. Those time the internet speed is high. Day time is not good for downloading.
Sent from my [device_name] using XDA-Developers Legacy app
Still no luck with downloading a file that is not corrupted. I managed to unzip it with winzip, but then Odin says the file is corrupted.
I've dowloaded a file from a different website, that unzips normally (previously couldnt unzip - winzip worked though), but it is not one file. There is AP, BL, CP and CSP. Firmware number corresponds with that on the sammobile.
Should I give it a go?
A corrupted file was detected. In order to continue, you must select a valid Odin File - that's what Odin says.
Can this have anything to do with Odin, well really JOdin3 being on MacOs?
pm
lukja123 said:
Hi there!
So my Note 4 died on my eyes and it was greatly missed. So I decided to buy Note 5 and got one. Old one was running Cyanogenmod for 3 years without a fail.
Did not read about releases in Europe. Apparently there is no m920F. Download mode said it is N920T.
Things I've done:
Installed TWPR (TWRP-3.0.2-1-G928T-N920T) with Odin (Heimdall used for PIT file).
Checked was it installed - reboot. Then bootloop started.
Tried to flash a couple of firmware ROMS thrugh Odin. No luck.
Used ADB to transfer firmware rom downloaded from Sammobile. Tried to flash with TWRP. Got "coulnd't find META-INF/com/google/android/update-binary in the zip file"
Things I haven't done:
No backup.
Did not check OEM unlock.
Did not spend a day reading how to do it properly.
It's been a while since my last encounter with custom roms and installing them. I spent all night trying different things, to no avail.
I appreciate the fact that this is common and quite boring issue, so I'm offering a tenner ing GBP (PayPal transfer) for whoever will make my phone work again
Click to expand...
Click to collapse
1. use samsung smart switch software...connect ur ph with pc...click more menu....click on emergency software recovery...hope ur phone get the official firmware for ur phone
2. plz send the pic of back side of ur phone(where the serial no model no displayed on phone)..& the pic of the box of ur phone
HELP!!! Lost IMEI & Hard bricked Note 8 SM-N950F/DS.
I flashed back my Note8 via Kies3 to stock rom, while updating the process got stuck at 24%. I left it overnight but the phone kept looping to the Installing Update screen then to recovery and on and on.
Then I flashed TWRP recovery through odin and wiped dalvik cache, cache, data and factory reset. The same thing kept on happening but instead of stock recovery it now ends up on TWRP recovery. Then I flashed dm-noverity. After that the phone booted up but there is no IMEI and phone signal. Please help.
mohiminul said:
HELP!!! Lost IMEI & Hard bricked Note 8 SM-N950F/DS.
I flashed back my Note8 via Kies3 to stock rom, while updating the process got stuck at 24%. I left it overnight but the phone kept looping to the Installing Update screen then to recovery and on and on.
Then I flashed TWRP recovery through odin and wiped dalvik cache, cache, data and factory reset. The same thing kept on happening but instead of stock recovery it now ends up on TWRP recovery. Then I flashed dm-noverity. After that the phone booted up but there is no IMEI and phone signal. Please help.
Click to expand...
Click to collapse
Hey. Try download your phone firmware from Sammobile the correct make N950F then use Odin to flash the firmware.
http://www.**********.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Hope this helps
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
AwesomeARC said:
Hey. Try download your phone firmware from Sammobile the correct make N950F then use Odin to flash the firmware.
http://www.**********.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Hope this helps
Click to expand...
Click to collapse
Try this link
https://m.wikihow.com/Recover-a-Bricked-Samsung-Galaxy
Hope it helps
AwesomeARC said:
Hey. Try download your phone firmware from Sammobile the correct make N950F then use Odin to flash the firmware.
http://www.**********.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Hope this helps
---------- Post added at 03:43 PM ---------- Previous post was at 03:41 PM ----------
Try this link
https://m.wikihow.com/Recover-a-Bricked-Samsung-Galaxy
Hope it helps
Click to expand...
Click to collapse
Brother I have tried the above method as per your suggestion but no result.
mohiminul said:
Brother I have tried the above method as per your suggestion but no result.
Click to expand...
Click to collapse
Try
https://www.fonepaw.com/bricked/fix-bricked-android-phone.html
You need Combination file to fix it
lost emei
this happened to me. I lost imei and could not make calls. what network were you on. I downloaded software for that network from sammobile and installed via odin, the imei returned and I was able to make calls again. I think what happened in my case was I rooted phone and put a rom on it. in aroma I selected t mobile America so it installed the file for that. I was on o2. my phone was unlocked. it did not recognise my simcard
Flash different modems
Hi
It has happened to me too many times with different phones including note 8
Just flash different modems and bootloaders to find the proper one.
androidfilehost .com/?w=files&flid=221868
*:Remove the space bofore .com
You can use both odin and twrp but if you want to stay stocked try odin mode.
If none of the above files worked for you look for other modems.
Odd that you can connect note 8 to kies3.. and not switch..
Sent from my SM-N950F using Tapatalk
I have literally tried everything. No results . I have possibly narrowed down the problem. My bootloader (OEM) is locked. If it was unlocked I could have flashed TWRP and then dm-verity no encrypt mod. Anyone with any suggestions. @holifo I got hold of a few combination files but none of them seems to boot beyond the screen FACTORY BINARY.
mohiminul said:
I have literally tried everything. No results . I have possibly narrowed down the problem. My bootloader (OEM) is locked. If it was unlocked I could have flashed TWRP and then dm-verity no encrypt mod. Anyone with any suggestions. @holifo I got hold of a few combination files but none of them seems to boot beyond the screen FACTORY BINARY.
Click to expand...
Click to collapse
Have you tried this one COMBINATION_FA71_N950FXXU1AQK2
While flashing combination file you need to flash HOME_CSC_OXM with it
mohiminul said:
I have literally tried everything. No results . I have possibly narrowed down the problem. My bootloader (OEM) is locked. If it was unlocked I could have flashed TWRP and then dm-verity no encrypt mod. Anyone with any suggestions. @holifo I got hold of a few combination files but none of them seems to boot beyond the screen FACTORY BINARY.
Click to expand...
Click to collapse
Jtag
holifo said:
Have you tried this one COMBINATION_FA71_N950FXXU1AQK2
While flashing combination file you need to flash HOME_CSC_OXM with it
Click to expand...
Click to collapse
Flashed COMBINATION_FA71_N950FXXU1AQK2 Factory binary from 2 sources along with HOME_CSC_OXM. No improvement. :crying:
so your phone is soft bricked. Its less of an issue since you have access to:
-recovery
-dl mode
go to updato.com and grab about 3 different stock firmwares.
1-the oldest one compatible with your phone you can find. forget about your region just be sure its an early FW and its for N950F. f or ds dosent matter.
2-again same as above but try one from south America.
3- same as #1 but from france or north west europe region.
before flashing, enter recovery and wipe data and cashes.
after wipe dont let the phone boot, have it go straight to DL mode.
now use latest odin and flash the firmwares above. if one of the flashes fail in odin Check your cables and usb port if any of the firmware flashes get stuck or give errors. Be sure to flash all BL AP CP and CSC files. for csc I think HOME csc has the pit file so you might also want to try repartition/bootloader update option if nothing else works. Since your phone is probably out of warranty by now.( might want to check if you can simply get it fixed before trying anything of the above first)
edit:
i saw you said having used kies 3 to do the emergency recovery. Im not sure how that were possible. do you mean smartswitch? if you have not used it, then go dl it and do the recovery from smartswitch. I dont even think kies support the note 8.
Ask him - https://forum.xda-developers.com/an...x-box-free-t3648947/post73222755#post73222755
mohiminul said:
Flashed COMBINATION_FA71_N950FXXU1AQK2 Factory binary from 2 sources along with HOME_CSC_OXM. No improvement. :crying:
Click to expand...
Click to collapse
And this file is flashed via odin til the end - with green PASS? Strange.
Hi mate, i know your feelings.
Ok, i just can tell about my issue. I was on a QK6 custom rom with a QKG bl/modem and fell back in jail So i had to flash stock but only the AP (QK6 bc QKG was at work :angel and CSC file. It booted up with the data of the custom rom and worked quite good. Except the gallery. So i decided to flash the QK6 bl/modem. The flash with odin crashed at the bootloader part. The phone booted without connections, no imei, no baseband...an exclusiv paperweight.
I tried a lot all a disaster. I searched for imei repair with the intencion to pay a lot of money but nothing. Even imei gurus said it's impossible for now to fix the imei for the note 8 with knox 0x1 by software.
Last thing i thought before i went crying to bed was the incomplet flash of the bootloader. So i downloaded over night the whole QKG package and flashed it in the morning.
AND all was fine again. I think the culprit is the Bootloader you can't downgrade from QKG. In the Iron Rom thread are the same issues after flashing the QK6 Bootloader with the rom over a QKG bootloader - all have lost there imei and baseband. They also fixed it than by flashing QKG BL (and modem).
This was my story and i hope it would help to fetch your problem.
I have same problem with your case, its made me sick 1 day but here is my success solution worked like charms !!
1. Download newest stock firmware via SAMFIRM ( for me i used XXVN code) extract it you will have AP and CSC using on this case
2. Download BL and CP via this link: (remove space before .com) You will have BL and CP
androidfilehost .com/?w=files&flid=244051
3. Open Odin chose BL, CP download from Androidfilehost. AP and CSC form stock firmware
Flash them and your Note will be back !! Reply me if u success !!
Ps: This case will upgrade ur blootloader to BRA2
And i heard that cant be rooted again, however my Note 8 is undead so im gonna sell it away better than bricked
Good luck from VietNam
Nice !!!! Its worked !! after i got check fail device 3, binary 2. I could flash ap,cp,csc but BL so now my Note is back to stock
Cheer
mohiminul said:
HELP!!! Lost IMEI & Hard bricked Note 8 SM-N950F/DS.
I flashed back my Note8 via Kies3 to stock rom, while updating the process got stuck at 24%. I left it overnight but the phone kept looping to the Installing Update screen then to recovery and on and on.
Then I flashed TWRP recovery through odin and wiped dalvik cache, cache, data and factory reset. The same thing kept on happening but instead of stock recovery it now ends up on TWRP recovery. Then I flashed dm-noverity. After that the phone booted up but there is no IMEI and phone signal. Please help.
Click to expand...
Click to collapse
Does the imei appear as uknown? or a bunch of zeros?
THORMUNZ said:
Does the imei appear as uknown? or a bunch of zeros?
Click to expand...
Click to collapse
The post you are responding to is 5 months old !
Just saying...
Sent from my Galaxy Note 8 using XDA Labs
THORMUNZ said:
Does the imei appear as uknown? or a bunch of zeros?
Click to expand...
Click to collapse
It used to come as unknown. I figured out a solution. Used https://drive.google.com/file/d/1qI8L3y1GkSlQu_Q03dsZr0DfBkb0ZRcs/view?usp=sharing this combination rom and this eng_boot https://1drv.ms/u/s!Aq07ytE0dzjkhv0iFXiB216r10pAvw
my phone booted to factory repair mode and then just went to IME option and dialed *06#
Samsung Note 8
I experienced the dreaded "Only official released binaries are allowed to be flashed" error.
I have tried flashing with the stock firmware via Odin but the phone need to restart after finding the PIT. The problem is the restart, it is stuck in booting with the display "Only official released binaries are allowed to be flashed".
I also tried for bootloader but same thing, the phone need to restart after finding the PIT. Same boot loop error.
Any help?
Thanks a lot!
iuseandroid said:
Samsung Note 8
I experienced the dreaded "Only official released binaries are allowed to be flashed" error.
I have tried flashing with the stock firmware via Odin but the phone need to restart after finding the PIT. The problem is the restart, it is stuck in booting with the display "Only official released binaries are allowed to be flashed".
I also tried for bootloader but same thing, the phone need to restart after finding the PIT. Same boot loop error.
Any help?
Thanks a lot!
Click to expand...
Click to collapse
What rom you have? your note 8 is europe model? whats your steps before appear the issue? you flash wrong kernel? you disable the oem unlock from dev options? you try hard reset and soft reset with buttons compination before flash with odin? I resolve the issue before some months. I flash with odin my official samsung stock rom. Is possible your official stock rom to be broken. Download other official rom and try again. Take a look the video how flash with odin. https://www.youtube.com/watch?v=aLv1y5Pu61Q
Every device has different PIT file associated with its stock firmware. A correct PIT file is needed in order properly flash the stock firmware on your phone. PIT is similar to a hard disk on a PC system partition and dbdata partition.
iuseandroid said:
I experienced the dreaded "Only official released binaries are allowed to be flashed" error.
I have tried flashing with the stock firmware via Odin but the phone need to restart after finding the PIT. The problem is the restart, it is stuck in booting with the display "Only official released binaries are allowed to be flashed".
I also tried for bootloader but same thing, the phone need to restart after finding the PIT. Same boot loop error.
Click to expand...
Click to collapse
I don't have the Exynos version, but there seems to be a lot of great information in the OP of this thread HERE. Your specific error message is mentioned in the OP too. Also, I believe he recommends some steps to take for someone who may have had the same PIT issue as you did in this comment HERE.
bogarty said:
I don't have the Exynos version, but there seems to be a lot of great information in the OP of this thread (URL="https://forum.xda-developers.com/showpost.php?p=75514974&postcount=1")HERE(/URL). Your specific error message is mentioned in the OP too. Also, I believe he recommends some steps to take for someone who may have had the same PIT issue as you did in this comment (URL="https://forum.xda-developers.com/showpost.php?p=75528275&postcount=20")HERE(/URL).
Click to expand...
Click to collapse
Follow the steps maybe it can fix your issue.
y0000 said:
What rom you have? your note 8 is europe model? whats your steps before appear the issue? you flash wrong kernel? you disable the oem unlock from dev options? you try hard reset and soft reset with buttons compination before flash with odin? I resolve the issue before some months. I flash with odin my official samsung stock rom. Is possible your official stock rom to be broken. Download other official rom and try again. Take a look the video how flash with odin. https://www.youtube.com/watch?v=aLv1y5Pu61Q
Every device has different PIT file associated with its stock firmware. A correct PIT file is needed in order properly flash the stock firmware on your phone. PIT is similar to a hard disk on a PC system partition and dbdata partition.
Click to expand...
Click to collapse
I was using REPULSA ROM and SmurfKernel, all were working fine.
I tried the Taimen 2.0 ROM with Notorious Kernel. I may have forgotten to enable OEM unlock before the system rebooted by itself (Taimen is not stable), then I encounter the issue. :'(
bogarty said:
I don't have the Exynos version, but there seems to be a lot of great information in the OP of this thread HERE. Your specific error message is mentioned in the OP too. Also, I believe he recommends some steps to take for someone who may have had the same PIT issue as you did in this comment HERE.
Click to expand...
Click to collapse
Apparently, these methods require restarting my phone, which currently is not possible because my phone cannot boot up and is stuck in boot loop showing the "Only official released.." error. :'(
Not sure if after waiting for 7 days will reset everything and can do recovery again.
Thank you.
iuseandroid said:
Apparently, these methods require restarting my phone, which currently is not possible because my phone cannot boot up and is stuck in boot loop showing the "Only official released.." error. :'(
Not sure if after waiting for 7 days will reset everything and can do recovery again.
Thank you.
Click to expand...
Click to collapse
Hey, my phone which is different model is in the same situation. Please tell me how did you solve it?
You need to download the official version and you can flash it via odin. Is very easy. Possible you download wrong official stock rom. Thats you cant boot correct. Download from this site https://www.sammobile.com/firmwares/galaxy-note8/SM-N950U/ and search for infos into this site https://forum.xda-developers.com/galaxy-note-8/how-to/official-stock-firmware-update-odin-t3677072 Im 100% sure you dont flash correct. Note 8 is unbrickable.
Why my samsung s10 exynos shows "only official binaries are allowed to be flashed"after my first reboot after root?
I only use magisk.
Root
[email protected] said:
Why my samsung s10 exynos shows "only official binaries are allowed to be flashed"after my first reboot after root?
I only use magisk.
Click to expand...
Click to collapse
Hi, you did something wrong in the critical part of the rooting process going to guess and say it was the main reboot after odin flash.
Had this issue 3 times, the best would be to follow this root process and READ everything line for line.
You'd be supersized that the smallest thing you've missed may have caused it.
To fix it, download original software for your model and country from SamMobile or any other form - use this software: https://forum.xda-developers.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584
Remember DO NOT DELETE THE .md5 from the file name after you've extracted it.
Root + TWRP Link: https://forum.xda-developers.com/showpost.php?p=79914231&postcount=125
fdeklerk said:
hi, you did something wrong in the critical part of the rooting process going to guess and say it was the main reboot after odin flash.
Had this issue 3 times, the best would be to follow this root process and read everything line for line.
You'd be supersized that the smallest thing you've missed may have caused it.
To fix it, download original software for your model and country from sammobile or any other form - use this software: https://forum.xda-developers.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584
remember do not delete the .md5 from the file name after you've extracted it.
Root + twrp link: https://forum.xda-developers.com/showpost.php?p=79914231&postcount=125
Click to expand...
Click to collapse
thank you very much
flash stock rom AP file to fix this issue and remember to flash CSC too
[email protected] said:
Why my samsung s10 exynos shows "only official binaries are allowed to be flashed"after my first reboot after root?
I only use magisk.
Click to expand...
Click to collapse
Something has gone wrong with your rooting, happened to me once.
Press and hold Volume-down, Bixby and Power button, connect phone with USB to PC, wait, release all buttons soon as Download screen appears. Now flash with stock firmware and start rooting from scratch.
FdeKlerk said:
Hi, you did something wrong in the critical part of the rooting process going to guess and say it was the main reboot after odin flash.
Had this issue 3 times, the best would be to follow this root process and READ everything line for line.
You'd be supersized that the smallest thing you've missed may have caused it.
To fix it, download original software for your model and country from SamMobile or any other form - use this software: https://forum.xda-developers.com/galaxy-s9/how-to/tool-frija-samsung-firmware-downloader-t3910584
Remember DO NOT DELETE THE .md5 from the file name after you've extracted it.
Root + TWRP Link: https://forum.xda-developers.com/showpost.php?p=79914231&postcount=125
Click to expand...
Click to collapse
So the same thing happened to me too while rooting my device so I tried to flash my device no matter what I do it won't flash sometimes the Odin gets stuck and sometimes it shows the process failed,I"be been trying to unbrick my phone from a week now but nothing seems to really work,so help if you can,thank you!
surajismarcus said:
So the same thing happened to me too while rooting my device so I tried to flash my device no matter what I do it won't flash sometimes the Odin gets stuck and sometimes it shows the process failed,I"be been trying to unbrick my phone from a week now but nothing seems to really work,so help if you can,thank you!
Click to expand...
Click to collapse
Hi, Ok the best way to do so is to get hold of stock firmware for your device.
Try this: https://forum.xda-developers.com/s10-plus/how-to/tool-frija-samsung-firmware-downloader-t3910594
Then secondly you will need the PIT file of your device !IF YOU BREAK YOUR PHONE IT IS NOT MY RESPONSIBILITY! :https://zfirmware.com/samsung-galaxy-s10-plus-g975-repair-firmware/
Make sure that when you select BL,AP,CP and CSC to leave the .md5 extension on the file, if all 4 loads without any errors and you have the correct PIT file you will be able to boot stock firmware.
In my case i had the same error because i flashed a modded debranded firmware without first flashing the stock AP.
So first, debrand you phone by flashing the stock debranded firmware, then flash the magisk patched version of it.
In other words, always flash the STOCK version of the firmware you want THEN flash the magisk PATCHED version (if you are moving from a version to another one, particularly if CSC is different).