(help) samsung tab a 8.0 t-350 bricked? - Android Q&A, Help & Troubleshooting

So I'm stuck at this blue screen in my Samsung Tab A 8.0 with the message: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
See what had happened was...
I was having problems with the battery and when I booted into recovery it said a message (can't remember it now) along the lines of: E: can't load bitmaps /poc0008 No such file or directory! & successfully verified DM-Verity hash & E: can't load /dev/block/(something) No such file or directory!
So here went I, Mrs. Pseudo-developer and I upgraded the firmware via Odin ver 3.13.1 Previously I think it was N7.0.1 and then it became N7.1.1. It was a much smoother experience and my battery didn't die as quick. Yay!
But there I had to go tinkering... Again, via Odin (which I'm comfortable with, btw. I have all my devices firmwares' backed-up. All my devices are rooted) tried to flash cf-autoroot and something happened, I couldn't read the argument and I booted into recovery and then into bootloader and started to reflash my firmware only for my usb to get unplugged in the midst of it. This sucks and does anybody has a tissue, because my tablet just died.

dilcia said:
So I'm stuck at this blue screen in my Samsung Tab A 8.0 with the message: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software."
See what had happened was...
I was having problems with the battery and when I booted into recovery it said a message (can't remember it now) along the lines of: E: can't load bitmaps /poc0008 No such file or directory! & successfully verified DM-Verity hash & E: can't load /dev/block/(something) No such file or directory!
So here went I, Mrs. Pseudo-developer and I upgraded the firmware via Odin ver 3.13.1 Previously I think it was N7.0.1 and then it became N7.1.1. It was a much smoother experience and my battery didn't die as quick. Yay!
But there I had to go tinkering... Again, via Odin (which I'm comfortable with, btw. I have all my devices firmwares' backed-up. All my devices are rooted) tried to flash cf-autoroot and something happened, I couldn't read the argument and I booted into recovery and then into bootloader and started to reflash my firmware only for my usb to get unplugged in the midst of it. This sucks and does anybody has a tissue, because my tablet just died.
Click to expand...
Click to collapse
Can you still go into recovery mode? Or the device was hard bricked? If the device is not booting you can try to patch boot.img

Related

Error Cannot Update Software

Hello,
I've Samsung Galaxy SM-J701F/DS and i did factory reset and started getting into panic mode. So, I tried to flash stock ROM through odin and I only selected AP and left other files like Bl, CP and CSC. Thus it took longer time without any result so, I closed the odin. Since then my phone only boots in download mode.
And while trying recovery or normal boot I get " Error Cannot Update Software ".
I used this ROM:
https://www.sammobile.com/firmwares/...-nxt/SM-J701F
And now my phone is showing as Samsung USB Modem while plugging in PC.

Galaxy S7 Edge soft-bricked / Odin gets stuck

Hello androids, I have a big problem or a good challenge, depends on your optimism. I've been looking for and trying solutions for hours and hours, but I think I've come across a wall and I need your help:
Originally I wanted to root my s7 Edge / SM - G935F (OS Marshmallow 6.0.1) by following a tutorial using an autoroot ROM for this phone. I remember I had USB debugging and OEM unlock enabled. I also installed the USB / ADB drivers correctly.
I used Odin v3.11, since they recommended using it for this mobile and MM 6.0.1. According to Odin, the rom was installed successfully, but my phone entered a loop with the Samsung logo and "RECOVERY IS NOT SEANDROID ENFORCING". Something failed in the process and I decided to install a S7 Edge stock ROM in 8.0.0 from SAMMobile (this one) with Odin v3.13 using HOME_CSC so that I don't lose certain data
Unfortunately everything was going well until just at the end when "hidden.img" did not process correctly and resulted in FAIL. I've been since then stuck with this error:
"An Error has occurred while updating the device software. Use the Emergency Recovery in the Smart Switch PC Software."
It won't even turn off. From there I can only access the Download Mode and neither the Smart Switch or the ADB & Fastboot console won't detect the device. Odin does recognize the phone, but every time I try to install a rom, the log gets stuck in "SetupConnection ..".
I have tried a bunch of solutions such as removing the "hidden.img" from the package, reinstalling the drivers, changing the USB port, changing Odin's version, installing only the BL, etc., but nothing shows progress...
I'm sorry if during the process I managed to do some stupidity that I am not aware of. Other phones I have never had problems, but now I feel defeated and lost. I need a savior! :crying:
Any way to make Odin work, ADB detect my device or access a working bootload? Thanks in advance!

Samsung Galaxy Note 8 stuck on boot logo and unable to flash stock rom

Hello, today I was trying to restart my phone after it was updating an app from the google play store for several hours and since then it gets stuck on the Samsung Galaxy Note 8 logo. My phone is rooted and has TWRP installed.
I still can enter TWRP recovery mode but literally everything I can do there fails. I get the "unable to mount storage" message whenever I try to wipe or format something and it is showing 0MB for all partitions.
I tried flashing the stock firmware using adb sideload but I am still just getting unable to mount storage/cache/data messages after a second. I also tried flashing the .zip file through USB OTG cable but got the same result.
When I tried flashing the file with JOdin3 (Odin for Linux) I got this message: "A corrupted file was detected. In order to continue, you must select a valid Odin File" (Still got this message after I redownloaded the file)
If anyone has any suggestions, please leave a comment.
Edit: Tried flashing with Heimdall and it somewhat worked but if I boot my phone now I get "fail to open recovery cause no such file or directory" error for a split second and then it reboots...
Please can anyone help me?

Stuck in locked bootloader download mode

Hey all, hope everyone is having a great day (I'm not),
I own a SM-T510 Samsung Galaxy Tab A 10.1 WiFi.
It all started when I tried to flash Nexus and it worked partially, but I didn't gain access to my internal storage for some reason, so I reverted back to stock rom.
Then for some reason part of the nexus rom was still there, but I was afraid of damaging my device further.
For some reason, netflix wasn't working, so I tried to apply a software update to my device using Smart Switch.
The update didn't work and I was caught in a Nexus bootloop. I entered download mode and I tried flashing twrp using odin. I thought it worked until I realised that it wouldn't get past the teamwin screen.
I re-entered download mode and there it gave me an option to factory reset the device while locking the bootloader. This is where I screwed up as I thought what else could possibly happen to my device?
SO I locked my bootloader and whatever I did I couldn't get out of download mode. AND here I screwed up even more. I tried to flash the stock ROM again using odin as a last resort but it just wouldn't complete after 10 minutes, so I closed Odin and restarted my device and here I am, stuck in a screen that says, "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." Now obviously this wouldn't work because my device isn't even listed there. But to note, my device is recognised by Odin and my PC.
Note: I am an absolute noobie at rooting so be easy on me.
Note 2: adb and fastboot doesn't work for me for some reason, my powershell says, "The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again."
Thank you all for any help. I am at my wit's end.

Question No flashing possible, phone stuck in bootloop

Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
why did you u
Insomnium_D said:
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
Click to expand...
Click to collapse
why did you OTA update the rooted phone
it is clearly written that your phone might brick.
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
I didn't, because I get (as always, this is not my first rooted phone) the message, that the system has been changed. OTA is not working and I read that uninstall magisk, update the phone and BEFORE reboot install magisk again on partition B. But I accidentaly pressed the second option in magisk, complete uninstall or how its name is. Didn't expected, that its start instantly without a "Caution" message.
Uninstalling Magisk should not bring my phone into a bootloop anyway, even if I wipe the cache. Or am I wrong?
raja0408 said:
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
Click to expand...
Click to collapse
That is the problem how do I do that, when everything with odin stops imediately or odin crashes.
Does Odin give you any error messages? Are you patching all of the files for the firmware AP BL CP & CSC? Are you making sure to use the non home CSC? Have you tried using Samsung Smart Switch to recover your phone?
Smart Switch didn't recognize the phone. The only error on Odin was "succeed 0 / failed 1).
It worked with Windows 10 notebook and the USB C Port. However it didn't worked on Win 7 and regular USB Ports. Very strange. Well, but now I have the original firmware and again lots of bloatware. TWRP doesn't work, impossible to boot with it. How can I root the A52 with Magisk that way, to deactivate it - if needed - for firmware updates? The phone doesn't has A/B partition.
Same happened to me.
So, I have an A52 Indian version and want to flash the Canadian firmware. I downloaded different versions of the Canadian firmware and used Odin to flash. I followed the instructions on downloading the files, loading them into Odin,hit Start and it kept failing. It was giving an error message regarding a repartitioning error. Could this be due to having to tick "OEM Unlocking" in developer options which I hadn't done?
Hey, is your phone still stuck ?
SHAREit​

Categories

Resources