I have a note 8, after the samsung logo it appears this message and i can't do anything; all i can do is to reset the phone, and even if i do it the message is still there.
I also tried to wipe data and cache from recovery but without results; and i also tried to flash the stock firmware many times with odine but it didn't work.
Are there any other ways that i can try to fix this terrible problem?
Thanks in advance.
elettrbel said:
I have a note 8, after the samsung logo it appears this message and i can't do anything; all i can do is to reset the phone, and even if i do it the message is still there.
I also tried to wipe data and cache from recovery but without results; and i also tried to flash the stock firmware many times with odine but it didn't work.
Are there any other ways that i can try to fix this terrible problem?
Thanks in advance.
Click to expand...
Click to collapse
Upload a photo of the error
I don't have the access of the phone now, but this is the error showed on my note 8.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
maybe try reflash with a different version of odin but maybe also try from a pc to access your accounts and do resets from there first
elettrbel said:
I don't have the access of the phone now, but this is the error showed on my note 8.
Click to expand...
Click to collapse
Never seen this before. Take it to Samsung ??
https://www.youtube.com/watch?v=ApSzrfckUUY
This is for S7 Edge but should be same for note 8, except for the files which you MUST download for your note 8.
make sure u download the correct firmware and select it in correct places on ODIN
vash_h said:
https://www.youtube.com/watch?v=ApSzrfckUUY
This is for S7 Edge but should be same for note 8, except for the files which you MUST download for your note 8.
make sure u download the correct firmware and select it in correct places on ODIN
Click to expand...
Click to collapse
Yeah this was the video that i followed without solve it.
I got a Solution!
1.Download latest dm-varity..
2.Go into TWRP and Format data "Type yes"
3.Reboot Recovery
4.Flash DM-varity and Reboot Recovery.
5.Now wipe all Partition
6.Boot Download Mode
7.Flash BQKG firmware!
8. Habe fun! Now you can inStall any Rom
Related
Hello everyone I'm desperate I explain the situation: a few days ago I installed the CyanogenMod on my samsung galaxy s5 sm-g900f, everything was fine but the next day at some point your phone is blocked and then restart it to restart remains the samsung logo and thus remains locked. So I decided to remove the battery and the phone after it shed no more signs of life, it does not go into recovery it in download mode. At this point by following a guide on the internet I formatted my external sd card in it, and I flashed a "debrick.img" file, so I tried to turn on the phone and a screen that leave you attached. The phone from that point is recognized by the computer whereas before no, and also by Odin, but trying to flash a new firmware with Odin me continually an error message "There is no PIT binary" and therefore fails the process tried flashing.Ho also to enter different PIT file, but without success.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try to find this pit file "MSM8974PRO_boot_recovery" and flash it with odin
if you can't find it send me privet message.
nahum05 said:
try to find this pit file "MSM8974PRO_boot_recovery" and flash it with odin
if you can't find it send me privet message.
Click to expand...
Click to collapse
hello thank you for answering . I tried to flash the file you have indicated to me , but unfortunately the device shows errors ( Odin : flash read failure , Error : there is no pit binary and Secure Check Fail : PIT ).
domy1797 said:
hello thank you for answering . I tried to flash the file you have indicated to me , but unfortunately the device shows errors ( Odin : flash read failure , Error : there is no pit binary and Secure Check Fail : PIT ).
Click to expand...
Click to collapse
pm me if it is still broke
Sent from my SM-G900F using XDA-Developers mobile app
Ok, so got my brand new shiny Oneplus 3T yesterday after waiting aged for it to come in.
Using it for a bit, noticed an OTA update to nougat came out (about 900mb) which downloaded in the background.
Triggered the upgrade, now the phone won't boot. I'm also having trouble installing any recovery roms on to it, because I was never intending to root the phone in the first place, and as a result didn't unlock the bootloader using the phone interface when it was on.
So now, it appears I'm stuck! My phone won't accept any side-load roms, (fails), full roms don't read (cannot open file) and fastboot won't unlock the bootloader (Not allowed)
....um.. not having a clue what I'm doing here....help???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
To fix it - see "[UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!! by Harris K". You have to download his two files onto a laptop or desktop computer and install a qualcomm driver (one of the files). The qualcomm driver will open a serial port into the phone's chipset. The other file will download a stock system, recovery, and fastboot to your phone through the qualcomm serial port. Harris is a genius, buy him a beer. This will fix the following problems.
1) It sounds like the OTA patch screwed up your /system where it doesn't even try to boot. You can still boot into /recovery and /fastboot but just not into /system. Since the phone is still "locked" (flashing prohibited) you cannot flash anything to fix it.
2) dm-verity does not allow any changes to /system. dm-verity checks a hash of hashes of /system. If the hash check fails when you boot /system, dm-verity will "brick" your phone (by design) leaving you with a black screen.
The OTA updates the system and downloads a hash key corresponding to that version. After the OTA, everyone has to end up with exactly the same system in order to pass the dm-verity check.
When you enable flashing (called "unlocking the bootloader") dm-verity will wipe /data to prevent someone from flashing a non-stock recovery to access your data.
infamousvincci said:
try going to stock oxygen recovery. wipe data and cache there. see if it boots.
try the unbricking thread too.
if all else fail, call OP customer service.
let us know what happens.
Click to expand...
Click to collapse
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
bunburyist said:
Ok, so went to the unbricking thread. The tool worked! I'm back up and running
Click to expand...
Click to collapse
I deserve a thank you button haha
This method is actually dangerous. Do not try this unless you have a good reason to do so
This method erases IMEI. Backup EFS with official or enhanced TWRP. Do not use any other TWRP as these might not backup EFS correctly and you will lose IMEI
Only use this as a last resort if everything else fails to revive your device.
First open the download tool. I will assume you at least know how to use it in the default upgrade mode
Press the verify button. The unbrick tool will freeze for a bit. Wait until it shows something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that close the verification window. An SMT download mode option will be unlocked
Yes, red signifies danger. Don't ask
Now press start
You'll see this box
The password is te123
Warnings: type the password exactly as it is. Do not make typos
Select your exact storage size
If you do not do this correctly you'll worsen the situation
Hit ok and the download will start
When the download completes you'll see this screen:
Disconnect your phone. Now exit the program
You might see this message but if it says download complete like in the screenshot above it is safe to press yes
Your device will not auto reboot like it did in the standard download mode. You'll have to press and hold the power button to force a reboot
Boot oxygenos fully and immediately use TWRP to restore your EFS backup
If you get an NV backup warning first restore EFS and then follow the steps given here https://forums.oneplus.com/threads/nv-backup-warning.474643/
I had a person who badly messed up his bootloader. The unbrick tool in upgrade mode didn't help. SMT fixed the issue and thankfully he had an EFS backup so the device was back to normal
Hi, meat I know where is the link to this download tool?
kakrona said:
Hi, meat I know where is the link to this download tool?
Click to expand...
Click to collapse
HERE
Um, hello guys, has anyone been able to unlock bootloader of a T-Mobile OP after SMT download?
Cuz I couldn't as it's giving me an error when flashing unlock_token.bin that says something like "Verify error (3:-2)".
If anyone had experience please report, thx in advance.
anupritaisno1 said:
I had a person who badly messed up his bootloader. The unbrick tool in upgrade mode didn't help. SMT fixed the issue and thankfully he had an EFS backup so the device was back to normal
Click to expand...
Click to collapse
How did you get SMT mode to work?
I used Magisk Manager 7.3.4 and patched a firmware (AP G9750ZHU2ASIK) for my Samsung 10+ (SM-G9750) and flashed it by Odin to my device but it only cuz it a bootfreze.
Yes I went the right way.... in the Dev options I set OEM unlock. Than I went to the Download Mod and pressed vollume up for 7 sec. I confirmed the bootloader unlock with vollume up again, and it booted into recovery and erased everything. I booted back to the Download mod and flasched the patched firmware with auto reboot option off in odin app. After passing successfully flashing, I turned the phone of and try to boot into recovery by using power + vollume up and bixby key, but it ends up with the black samsung screen freezed. No matter how often I try again to reboot normal or reboot into recovery, it doesnt change anything.
And yes I say that this is a bug in Magisk 20.0
because I also found an older patched firmware that I patched previously a few weeks ago. And I tried this one. No problem. I could boot into recovery to fullwiping and I was able to boot into system with Magisik root. But this older patched firmware has Magisik 19.
Once I open Magisk Manager than, and start updating to Magisk 20.0, it ends up with the same boot freez.
here is a picture with the freezed screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
h t t p s: / / img1.img1.de/20191015185446219b3.jpg
Its wired that if u look on the picture of the freezed screen that apears. than u can see that it says that OEM Lock is on, but If I open the download mod and have a look there. Than it says that OEM Lock is off. So there is defenetly something wrong with Magisk 20.0 for Samsung Galaxy S10+ (SD)
I beg the Masgik Dev to fix it, cuz I really wanna patch and use a recent firmware.
regards. Jens
Hi good evening, this is my first post in xda, I've used the forum since my first android back in the htc era, since 7 years I used my s8 with the hadesRom and everything was amazing, then I've broken my beloved s8, really the best smartphone ever, and I've bought an s10 a couple of month ago
Then, yesterday I start to follow the Magisk guide for unlock the bootloader and root my S10 G973F-DS and after it the the one for install the TWRP with the PlayStore method.
Unlocked the bootloader, rooted it, Magisk was installed, then I had the first problem: the internal storage was down to 25gb, I've wiped from recovery data and cache and the storage came back to normal, I've installed the twrp with the appstore method, rebooted to twrp, and wiped again data and cache as said in the hadesRom install guide and then all the system was gone, the twrp refuse to reboot to the stock one so I've tried to flash the HadesRom and now it's stuck in the Samsung GalazyS10 bootup splash screen, it just reboot with Bixby+volumeDown+Power but it always just go back to the splash screen, it doesn't recognize any other button sequence neithe the adb devices recognize it...
can I save it?
Thanks in advance..
Use ODIN to flash latest firmware again. Then use ODIN to flash LineageOS, then install lastest PixelExperience and boot on it. After boot PE, use ODIN again to flash TWRP and flash any rom u like.
Thanks for the answer, but I can't flash anything, it's stuck in this splashscreen, It only reboot with volume- bixby and power, but it just goes back to this one again.
I've tried flashing the orIginal fw, but it's not recognized by Odin so if I start Odin nothing appens actually.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Samsung Galaxy S10 G973F Test Point – EDL 9008 Mode
By using the Samsung Galaxy S10 G973F Test Point, you can easily restore the stock ROM, bypass FRP lock, or reset user data on your device via UFi Box. In
www.mobilerdx.com
This link may help u