Hey I wish you a nice evening!
My Samsung Galaxy A40 does not boot, it is stuck on the Samsung Galaxy A40 Secured by Knox powered by Android Screen.
After some time it comes to the android recovery, but unfortunately it is OEM locked and I think USB debugging is disabled.
I tried the following things anyway:
wipe cache and factory reset
adb sideload (only this mode is available) with the original firmware results in "Error 21 Signature verification failed"
And from download mode I tried:
flash the original software (android 9, 10, 11) till I am at bios version 4 and can't get back --> result: only erasing data is shown, I did not get any further
flash twrp --> forbidden by OEM lock
I don't know any further, my next step would be to replace the motherboard, but if you have any idea that could solve the problem, please add a comment.
And as time passed I also tried Samsung SmartSwitch to fix the software, but it failed too.
In my opinion it is maybe a hardware fault..
Thank you very much
In the attachment you can find some images of my failed tries
Related
I bought a new Nexus 4 from the Playstore and I updated it from 4.2.2 to 4.3 when I first got it, used it for a day or two and when I restarted the phone it was stuck in a bootloop on the X screen. After further research I found that this was a common problem with the 4.3 update and I've tried a few solutions to no avail.
I've put it in the fastboot mode and recovery mode and tried to wipe the cache and factory reset the phone via recovery mode but I'm still stuck in the X screen.
Please note I can't turn on usb debugging or developer options because I can't access the phones operating system and also its stock not rooted.
I don't want to send it to google if there's a way to fix the software via flashing the rom because I was planning on doing that anyways, this is the first time I'm trying to customise software on a non Samsung Device (Galaxy S1, Note 2, Ace).
Any response would be appreciated.
Since you already know how to access the fastboot screen, you just need to connect the phone, install the adb/fastboot driver and flash the factory stock image. Check this guide (its in the stickies): http://forum.xda-developers.com/showthread.php?t=2010312
(The download the platform-tools attached in the post, it has the adb and fastboot software you need to do the flashing.)
Also make sure to post in Q&A section next time.
Hi.
Phone Info:
Samsung Galaxy Note 4 - (updated to) version 5.1.1, Sprint carrier, SM-N910P.
What I did:
Tried to root my 5.1.1 device via (presumably, now) incompatible protocols:
galaxynote4root dot com/galaxy-note-4-root/how-to-root-galaxy-note-4/
Tl;dr I used Odin and CF Auto Root via USB cable (Computer & Download mode on Phone).
What happened:
Root seemed to work, but immediately upon reboot, my device went into a perpetual boot loop.
Currently:
I've tried flashing, downloading proper firmware; fails.
I can access download mode & recovery mode.
Recovery mode tells me my dm verity verification has failed, so any attempt to clear the cache and factory reset has failed.
I've heard the possibility of a custom ROM fixing this issue, but I don't know the half about where to even begin there, and I'm so beyond frustrated. Any ideas are more than appreciated.
Jenn
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Have you tried Download mode ( vol - home button and power button) ?
Viesuliss said:
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Click to expand...
Click to collapse
Just download official firmware and flash with odin. (Make sure not to downgrade os version. )
go to downloadmode, be sure drivers are installed, COM must be green,flash firmware with odin "only PDA", return into bootlader after reboot, flash twrp, boot into recovery mode done
Same thing happened to me.
Don't search for any file, the solution is very simple: download Samsung Smart Switch (only Windows, Mac version didnt work for me).
On menu click "Others" then "Emergency software recovery". Write A510F and then your phone Serial Number. Wait 30/60 mins ?
Sent from my SM-A510F using XDA-Developers Legacy app
My J530F got totaly locked up after I tried to upgrade from an older Lineage version to the latest one, now it is stuck in download mode screen giving the message that something went wrong trying to upgrade.
Odin does recognize the device but it is unable to flash. Smartswitch does not recognize the device and neither does adb. Not it has an OEM & FRP lock and I am stuck on the same screen.
I can reboot to download mode, or I get the download mode screen with an error message. The device won't even shut down until it drains the battery. So it is pretty broken I think.
Can't seem to find any solution that works since the device won't let Odin flash anything, and Smartswitch won't work either, please help me find a solution..
Lineage 15.1 - Magisk 17.1 - TWRP 3.2.3.0 - FRP & OEM Lock stuck in download screen
Hi there,
I got an old man's S7 Edge (SM-G935F) and I'd like to help him rescuing his photos (he doesn't have a periodic backup but he learned from this now).
The phone did stuck at the boot screen. He didn't try to modify anything.
FRP Lock on unfortunately. Should be the latest Android.
I can enter the download mode (not the recovery) but no chance for TWRP b/c of FRP. Same error for an engineering recovery I found online.
AP SUREV: B:8 K:B S:7
So I got me two OEM firmware packages with Frija and try to reflash but it always stuck at flashing "boot.img" endlessly.
Also it got me to the "An error has occurred while updating the device software, Use the Emergency recovery function in the Smart Switch PC software." screen now.
(I have no code for Smart Switch recovery but I still can get into download mode using FRP Hijacker.)
Is the NAND most likely roasted and the only hope may be chipoff? Tried on different PCs with different cables.
Thanks,
Nico
Edit: I don't need a working device, decrypted dump would be enough.
Edit 2: When I skip the AP package (containing the "boot.img.lz4"), it stucks at flashing "RADIO" after a few percent.