Problems while flashing onto Samsung Galaxy A40 - Android Q&A, Help & Troubleshooting

Hello,
The last week or so I have been trying to flash TWRP onto my Samsung Galaxy A40 (SM-A405FN) to install LineageOS. However, as I started following different guides and methods I have run into several problems that I can't get around and I was wondering if anyone here has had a similar experience or knows the solution.
The first problem I ran into was that when trying to flash onto the phone, neither ADB nor Fastboot detected the phone in download mode (when it was turned on normally they did). I tried various things to solve it: uninstalling and reinstalling different drivers, trying to find the device in device manager (it wasn't there) and nothing worked. I got around it, however, using Odin to flash. Odin did recognize the phone. I had already unlocked the bootloader and made sure VaultKeeper didn't lock it again. I believe it is fully unlocked now, I have even waited the week period to remove the RMM thing (I'm not entirely sure what it is and if I've done it properly, it's been a while since I've messed with android, but it used to display "KG state: checking" and now it's gone).
So, with Odin recognizing the phone I tried to flash the official TWRP recovery for it, following the instructions on the website. However, after flashing it, the phone bricks and boots into download mode all the time, with the error "Error validating footer (6)" on the top left corner. I have googled far and wide and the only solution I find is to reflash the stock ROM. Of course, this works, but I would like to be able to install LineageOS on the phone.
Thank you for in advance and let me know if you need more information or pictures of some sort.

Bump

Hello,
You can try the tuto on the following link:
It's for samsung A20, but you can apply the same practice for the samsung A40.
The first part of this tuto is woking for me (TWRP) but not the last one: "Rmm bypass"
Best regard's, Gregory

Related

[Q] Samsung S4 I9502 root / flash failed - NEED HELP

Hey Guys,
I tried to root my Samsung S4 GT-I9502 (OS Android 4.3), for that I found this website:
http://marrkdaviid.com/2013/08/fix-caller-id-install-google-play-on-the-galaxy-s4-i9502/
But it failed (more information below) and I had the following error message and no wifi.
I am able to put the device into download mode, though I keep getting this error message when I try flashing the device in Odin.
(here someone with a similar problem: http://androidforums.com/international-galaxy-s4-all-things-root/768632-sos-cannot-open-gt-i9502-after-failed-boot.html)
"Complete(Write) operation failed."
When attempting to flash the device, it quickly goes through boot.img, recovery.img and system.img (when it should take longer for each step, and you should see the little green progress bar move), before failing. Does this mean that Odin is having issues writing to the device?
I live in China and I just bought the phone, I needed 5 days to download the necessary files, because most download pages are blocked in China. So I am loosing my last nerve right now.
I am pretty confident that I have the correct Samsung drivers installed. I don’t have Samsung Kies installed. I have even tried using a different computer (Laptops), and two different ROMs.
I have tried flashing the below ROMs:
I9502ZNUCMG2_I9502CHUCMG2_I9502ZNUCMG2_HOME.tar.md5
I9502ZNUEMK3_I9502CHUEMK3_I9502ZNUEMK3_SVA.tar.md5
Someone with a the same problem tried the 'Firmware upgrade and initialization' option in Samsung Kies, but it didn’t work, so I didn’t try. (Here the link: http://forum.xda-developers.com/showthread.php?t=2382979)
Instead I tried a recovery. I used Odin 3.07 and the following file:
i9502-cwm-recovery.tar.md5
I got my phone back to work for a while, I reset the phone, just in case. But know I can’t switch the Wifi on and the phone wants to Reboot.
So I allowed the phone to Reboot, I clicked on “reboot system now” and then on “Yes – (I forgot what was written behind the Yes, but I didn’t just click on the normal Yes, I clicked on the Yes - …)
The problem here: The Phone changed to a China Unicom Screen and stayed like that. After 5 h I took the battery out, but I couldn’t restart the phone.
So I did an cwm recovery and know I am afraid to reboot. The Wifi is not working and I can’t find any information about how to fix it.
So please help me. Do I reboot? Can I already install SVA ROM, although I couldn’t flash the Stock Firmware? Do I send the phone back and give up?
Please let me know if you need any other information to be able to help me.
PS: This is the first time that I flash a smart phone. And although I already spent several days now, searching the internet for how-to-dos, tips & tricks, guidelines, Q&As and god knows what, I still do not fully understand what exactly I am doing here. Hence, I would be very happy to receive somewhat easy understandable answers.
Thank you so much for your help!
Anna

What worked for me to fix: The frp lock Soft-brick (using Samsung Smart Switch)

This will save you 8-12 hours of your time if you are lucky. This means that it also includes the meaningful links of 8-12 hours of searching. Sentences in italic are important. 1 link is for the Odin official website, the rest are re-links back into XDA.
The device in question is a SM-925T Tmobile S6 Edge.
The problem was this. I rooted my phone and messed around with Greenify and the Play store. To prepare for rooting, I allowed unknown downloads, unlocked the bootloader, and turned my security lock off (I had set it to a finger print lock). After I was done rooting, I immediately locked the bootloader again(<--A mistake that caused my bootloop/ soft-brick). After I was finished messing with the above apps (Greenify, etc), I wanted my phone to restart. So I held the Power button and selected restart, while I was on the lock screen (may not be important). I noticed that it took a long time to restart, and upon closer examination, I noticed another error under the "kernel is not seandroid enforcing" (which appears to be natural for rooted phones). The error was "Custom Binary blocked by FRP Lock". It was a new error. I investigated this new problem using the internet , and this dude was panicking like hell, but he didn't appear to fix his problem. He did hint that returning to the bootloader to its locked state was a mistake. Looked a bit more and this guy pointed to another thread, which introduced me to flashing and more importantly his fix, which was to flash the stock 5.1.1 image through odin. He used this link, which contains all the stock firmware for the majority of the new Samsung S6 and S6 edge versions. To make a long story short, most of these fixes involved flashing your firmware to the stock version. So I went to the Odin Website, and downloaded every version, as a couple threads have said that different versions worked for them. Here is a thread with everything you need for Odin. Now, after sorting through and finding micro USB cables that are detectable by Odin, an important step because Odin might develop a pattern of detecting then failing to detect your device through that cable, and testing all the usb 2.0 ports, I was ready, and had Odin with my stock firmware. Odin kept saying "NAND Write", then in the next line "FAIL". This was annoying as Odin wouldn't detect my device again unless I unplugged it, restarted it to download mode, then restarted Odin before plugging it back in. I got confused and found links for somehow fixing the .tar files, stock roms, .pit files (DO NOT MESS AROUND WITHOUT KNOWING WHAT THOSE THINGS DO), and other threads/websites that say to boot into recovery mode , factory reset, then wipe your cache. I could only do that once. After me messing around with all of the above file variants and supposed fixes to help with my issue, I couldn't boot into recovery mode, it got stuck on the "Samsung Galaxy S6 Edge" logo. It did not fix the NAND write failing. There however, are a lot of websites allowing you to download stock software for your phones, and I don't think I can link them as it might break a rule. Surprisingly, some have claimed that using a stock file for another device worked to fix their problem. This thread, which convinced me to use Smart Switch when it failed for everyone else, was very useful, although I recommend downloading Smart Switch from the official website of Samsung. None of the Odin flashing had worked so far, including the Roms and .pit files so I tried Smart Switch. I opened it, and upon selecting the "more" tab on the upper right corner, a bunch of tabs drop down. One should be "Emergency Software recovery and initialization". I had to find my S / N (Serial) number, and I was very confused on how to obtain that number as I was locked out. But to obtain it, do the same process to boot into download (hold volume down, home key, and power key), but stay on the prompt and don't go to the screen that has the word download in the middle. Don't do anything other then reaching the prompt confirming if you want to install a custom ROM. Then, press the home key and it should show your S / N number along with your IMEI number. Once I imputed the code I saw on my phone into Smart Switch, it told me to connect the device. Now, by this time, I realized that Odin only detects my device if it is actually in the download screen. Why shouldn't my computer? I booted into Download on my phone and followed the steps on my computer, making sure that the computer can recognize my phone while it is using a valid USB port and Cable. And after some waiting, for me, my problem was fixed and I could use my phone again, it reverted to it's out-of-box state. I hope this drawn out but very specific explanation helps you guys. It's my first post And also, this thread confirms that you can use a USB hub for flashing(at least for ROMS), Smart Switch, and for rooting.​
Thank you for this detailed account, however nothing of the above has worked for me. Odin won't flash the firmware of 5.0.2 (and I tried 5.1.1) and Smart switch does not recognize the device to do anything. BTW phone has been rooted for months and last night decided to turn on its FRP lock randomly and now I'm stuck. Any help would be greatly appreciated.
Explain throughly what you have tried. Especially different ports, cables, and computers. Did you have the right device drivers? Did you do anything else?
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Xalmey said:
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Click to expand...
Click to collapse
press vol down home keys and power key once you get to the first blue screen release vol and power keep holdind home but I already tried smart swich didn't help
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
EsperaKing said:
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
Click to expand...
Click to collapse
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
callumbr1 said:
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
Click to expand...
Click to collapse
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
EsperaKing said:
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
Click to expand...
Click to collapse
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
callumbr1 said:
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
Click to expand...
Click to collapse
Thank you for you reply.
Please can you tell me where I can find such software or how to do it clearly! I know how to use Odin but I don't know how to exclude user_data to be wiped. Thank you
Bonafid3 said:
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Click to expand...
Click to collapse
Thank you thank you thank you!!! This is exactly what I was looking for I had just rooted my note 4 running 6.0.1 and had no idea what the oem option was as no rooting method talked about it at all so naturally as soon as i added my Google account phone restarted and locked up.
Kies was the answer I needed as frp lock was active in download mode and my factory reset in recovery failed everytime but running Kies firmware upgrade and entering my model and serial number it installed perfectly in download mode with frp lock still active saved me alot of hassle ?

Elephone p9000 brick - Screen lights up after flashing stock ROM but no boot

I tried flashing the stock rom onto my Elephone P9000 with sp tools. I followed all the steps correctly as I have done in the past. Sp flash tools downloads the rom and says it is a success but yet when attempting to boot the phone, the screen turns on and remains blank. No logo or recovery. Recently I tried flashing TWRP onto the device and that also did not work, when attempting to open recovery mode, the device just rebooted a couple of times, so I left it and forgot about it. I have managed to successfully flash the stock rom in the past but since I sent off my phone to have it's screen replaced, flashing no longer seems to work. I have tried flashing with battery in and out. And i've unplugged cables and replugged them inside the phone, checking for loose connections. If it also makes a difference, since the screen repair, the wireless charging does not seem to work.
If anyone can offer any advice it would be greatly appreciated.
edit: potentially relevant info, flash tool memory test states nand flash is not detected, found a relevant thread but the answer provided did not work for me: http://forum.xda-developers.com/showthread.php?t=1866962
-William
Flash the stock firmware 15072016

Device keeps rebooting into recovery. Tried every trick in the book.

Firstly, let me quickly outline what I have done.
Unlocked bootloader
Installed TWRP
Installed a ROM. I wasn't happy with it. It was rooted which of course my banking app didn't like. hideSU didn't work, I couldn't remove root so I tried another ROM.
Once installed I reboot and I have stuck in this loop ever since. I cannot get into TWRP. I've gone into fastboot mode multiple times and tried over and over to install TWRP and reboot into it but nothing.
Worse still is the erecovery option to download latest version over wifi just doesn't work, "Getting package info failed".
Another "useful" Huawei feature if the ability to hold vol up and down to auto install a firmware image. Not helpful when I have no ability to put any files on the device in these modes.
Finally, I have no idea what exact version of firmware I need to download. All I know it is a P20 lite and I bought it from the UK.
Can anyone help? I'm literally staring at this brick stuck in eRecovery.
your try to use hwOTA8, this installs 100% all the firmware (I had the same problem as yours).
nm
Never knew that existed so thanks.
I thought I was finally on the right track but it seems my phone is different from every other one.
I used HWOTA8 and it wants to install TWRP right away. I followed the video instructions and mimicked his movements exactly and when his reboots into TWRP mine does not.
UGH

Samsung Galaxy Tab S6 Lite (LTE) Bricked? Bootloop HELP

Hello, I am new here and I made a huge mistake!
I purchased Samsung Galaxy Tab S6 Lite (LTE) literarally 1-2 days ago and I wanted to root it, I had my smart phone rooted which did not have Knox protections, it was as straight forward as flashing TWRP and use Magisk via instructions I followed.
I make use of "Root" privileges a lot when using my device, I find it very important to my daily life so I decided to risk rooting it, after doing so my tablet was showing 2 errors, that its not using official samsung software and that the boot loader is unlocked, when I unlocked the boot loader using OEM Unlock everything went fine, the option was greyed out and checked afterwards.
During the boot process, it reboots 2 times and it shows a integrity error, integrity and some very long number, I am assuming its a integrity check? I have the exact matching firmware, so I flashed back the stock firmware and... the "not using official samsung software" warning disappeared, it boots me into recovery mode, I choose "reboot" and the device goes to boot looping with the same error.
I was following this tutorial: https://forum.xda-developers.com/galaxy-tab-s6-lite/how-to/howto-unlock-root-galaxy-tab-s6-lite-t4132289
But there are some things I skipped, here the exact steps I took:
Unlocking Boot Loader:
Followed all the steps from 1 to 4 but I skipped the 5th step entirely, the step where it asks you to mess with firmware date and twrp, I did none of that, I will mention that when I was looking for stock firmware to download before doing anything, I was not able to understand the CSC so I didn't know which firmware to exactly use until a software update came up which told me the exact firmware, I accepted the update and download that stock firmware, because my firmware was updated I didn't think that following the few steps of the step 5 would've done everything as I was already off the path.
I didn't do the 6th step as I just checked of the OEM Unlock is greyed out and still checked in the "developer options" section, I assumed that it was a success, not to mention the boot loader unlocked warning that was showing up and yes, all the data was erased and was forced to go through the setup process again as expected.
Root the tablet:
1. I have downloaded the firmware as it says not just for the purpose of rooting, the firmware that the software update told me about, this is the firmware I downloaded, the firmware is a exact match, everything is matching: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
2. I follow all the steps from 2 to 11 from here.
3. When I reached step 12, I went to download mode and I look for any messages regarding it only allowing for official samsung images, but I saw no such message, didn't really pay attention to anything else, I just glossed over things, considering there was no such message I assumed that KG/RMM state was good, don't know what it was but it might not have been "prenormal" because there was no message regarding official samsung images, from here I falshed the boot.tar file like in the instructions, that lead me to my current problem I mentioned at the very start of this post.
4. There was no step 13 as I can't boot into android due to "integrity" error I have, right now I have my tablet turned off (thank god I can do that) via the recovery that shows up after flashing stock firmware.
Addition Info:
1. I don't have any data to lose, if I need to do a factory reset or something of that sort, I have no problems doing that.
2. As I mentioned at top, I do have a stock firmware downloaded from this link here: https://samfrew.com/download/Galaxy__Tab__S6__Lite__-LTE-__/xs5l/SEB/P615XXU3BTI3/P615OXM3BTI3/
3. The tablet is: SM-P615 (Samsung Galaxy Tab S6 Lite (LTE), I bought the LTE so I could use it as my phone)
4. At the download mode, the OEM (Boot Loader) state is set to NO and the FFS (I don't remember if its FFS exactly at the moment, something FF I believe, I don't want to turn on my tablet at the moment) was set to NO.
5. The KG (No RMM mention that I could see anywhere) state is showing up as "Checking..."
What do I need to do to fix my tablet? do I need to wait for 7 days? if so how do I do so, like does leaving my tablet off count or not?
PS: I am a self-thought experienced low-level windows programmer, I've been doing programming for over 10 years now, never have worked with Android development but I can attempt to build something from source if necesarry, I know very little about Linux OS as I purely work with Windows and use Windows for everything including servers.
I have done some research regarding that "integrity" error and I can't find any screenshot in google images that matches how it looks on my screen, but there are a lot of them quite similar to it, which basically says "verification failed, factory data reset your phone", in my case I don't have that message, it just says "integrity", but when the boot looping stops and shows that failure I do have 3 options, "try again" and "Factory data reset" and the 3th one I don't remember, I am suspecting that this could be my problem! I believe the samsung just changed the way that particular message is shown (visual change), so I just need a factory data reset and it will work, most likely with the rooted boot.img file! I will attempt this after a few hours of this reply, I may have panicked too early.
The issue has been fixed
Well this is surprising, I was about to do the factory reset but before doing so I decided to flash the same magisk patched boot.img file, when I flashed I saw seeing those 2 warning messages as expected, I was expecting for it to fail after 2 boot loops so I can do the factory reset as intended but on the 3th boot loop the tablet booted up! I was brought at the android setup screen, once I was done with that I checked the OEM Unlock, it was still checked and greyed out, downloaded Magisk Manager and to my surprised it worked! Magisk Root latest version is installed and working, it asked me to allow magisk do some "additional setup", the tablet booted up perfectly fine after that "additional setup", I check root privileges using "Root Checker" and it worked, I have root privileges! I most likely have panicked too soon, sorry for wasting your time! Hopefully this post will be useful to someone in the future looking to root their tablet.
My assumption of what happened: When I flashed the stock firmware AP a second time so I can turn off my tablet, it most likely did a factory reset without me knowing, so when I flashed magisk again before letting it try boot up again, the tablet booted perfectly fine because factory reset has already occured, which brought me to the android setup screen.

Categories

Resources