Heya! So, this is my first post on XDA, i have tried to flash android 10 on my sm-t515, it failed, restarted, then showed this error and its now bootlooping, i cannot access twrp or any recovery, cant access bootloader, cant use odin, smart switch. Is my tablet bricked?
Related
Hello guys,
I need extremely technical help as no longer know what to do.
I have a Galaxy S7 Edge device, which installed the rom BobCat and everything went well until then.
Later I decided to install another rom to test KingRom that left me unsatisfied, because I thought it had some bugs. Had the TWRP 3.0.0 recovery and decided to upgrade to 3.0.2, everything went well.
At one point I do not remember when or how if was when install back, downgrade to TWRP3.0.0, I do not remember if it was via Odin or TWRP, it happens that the installation stopped halfway. Then unplug the device, restarted in recovery mode and got the following message "E: falied to mount EFS (Invalid Argumen)", I could not restart the device (Boot Loop, and stucked at Samsung Logo) except in Recovery Mode, which also made to stay without IMEI number and Serial Number.
I googled until I came to this tutorial:
http://forum.xda-developers.com/s7-e...ssues-t3379516
I followed all the steps explained, I back up EFS_backup and RADIO_bakcup partitions.
Installed FACTORY BINARY G935, everything went well. After restarted, already had the correct IMEI number but still did not present the S / N.
After all that, i tried to install Stock Firmware via Odin, from here started the problems that could not solve.
In the first attempt Odin stucked in "System" (also used the PIT file with the same CSC ... .i do not know if I was right using PIT?). Restarted the device forcibly, entered the stock Recovery, did a complete wipe and always get this message "E: falied to mount System (Invalid argument), I returned to install Factory Binary, then reboot in Recovery and the same message no longer appeared.
Again I try to install the Stock Firmware and Odin always stucks in System, or NAND writing, or Partition, etc. I've tried various Stock Firmware, with and without PIT files, always without success.
Only Factory Binary that successfully installs. The TWRP via Odin also but when device restarts to enter Recovery Mode always get the message at the top of the display:
"Recovery image signature check Fail"
"Reboot to avoid Warranty bit set."
1. Does the partitions are in good shape? how can I check it?
2- I did good or bad using PIT file?
3- Does the problem is running Windows XP through a Virtual Machine?
4 What else can I do?
In all actions used and am using a Macbook 4.1, OsX Lion 10.7.5, Odin 3.11 Windows XP Professional 32bit through Oracle VM VirtualBox 3.4.38
Device:
Galaxy S7 Edge (SM-G935F) CSC = SWC SwissCom
1st Original Firmware: (I guess was 1?) G935FXXS1APG5_G935FVFG1APF3_SWC
Need help Please
Thank you so very much!
Hey guys,
I tried to root my gf's S5 with CF-AutoRoot's package. I got this for the specific version which I double-checked
Included in the package was Odin and the image with an "installer".
Everything was fine, device detected in Odin, selected image in AP and let it rip... Except I got an error after it was in the process, under UDC start, can't remember exactly as I had restarted the device with the loading bar at like 30% of the way... it stated something dev_state
After I restarted, I got the "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I would've thought it was going to be pretty straight forward and decided not to do a backup but I'm so getting killed if I'm going to lose the data!!!
Any insight? thanks
I tried to get Samsung Kies for the recovery but under the list of devices requiring emergency recovery it won't detect it...
I managed to retry the Odin flash with the same outcome.
The error message is unsupport dev_type if that makes any sense to someone
Well issue seems to have fixed itself by flashing latest TWRP... The Odin flash went smooth and phone booted normally...
must've been something off with the AutoRoot
I've been trying to update my phone to emui 5.0, every time it just says update failed. I also tried to flash custom roms through twrp, which always make my build number to something about test-keys. Maybe I'm just to dum. I wiped the system and tried again, but when booted to fastboot it says locked bootloader(it isn't what I want) so I unlocked the bootloader. Now it somehow only boots into the error mode: NO11(recovery image) and NO2(load failed).
I tried button combinations, it just keeps booting to error mode(I also read through other threads, but the solutions like waiting till the phone dies, than press volume - and connect to pc didn't work).
PLEAEAEAS Help!!!
Backstory:
Received the message "Custom binary blocked by FRP lock" when restarting my phone. I had a custom ROM installed so this was probably why, but I had flashed no-verity-opt-encrypt previously so I don't know why I randomly got this message.
Tried to flash the latest Android 8.0.0 stock firmware from sammobile, successfully flashed through Odin but when the phone boots it keeps looping into recovery, followed by "No command".
When I try to access the recovery settings by pressing power+up it comes with:
fail to open recovery_cause(No such file or directory)#
Reboot Recovery Cause is [UNKNOWN]# No Support SINGLE-SKU
Along with a bunch of lines saying failed to mount /system and dm-verity failed.
I've tried flashing many different stock ROMs but only the factory binary combination ROM is able to boot up. Therefore, I cannot turn off FRP lock. I am struggling to find out why, even though Odin successfully flashed the whole stock BL, AP, CP and CSC, the recovery cannot be opened.
Any ideas would be greatly appreciated.
Edit: Managed to fix it through a YouTube video by Mr.Lee
Try downgrading to nougat or marshmallow. That should remove FRP.
Sent from my SM-G935FD using Tapatalk
I've tried but I cannot find any marshmallow/nougat version which does not result in a SW REV CHECK FAIL error, my kernel only accepts Oreo or higher it seems.
Noob here: I need help with my Note 3 (SM-N900V).
I bought a used phone to replace a stolen one; it came with Android 4.0. A few years ago I successfully used Odin to flash TWRP 3.1.0.0 and the stock OF1 Android 5.0 rom, followed by a root with ArabicTool.
Phone works fine for everyday use, including root-requiring apps, but several apps are now requiring a more recent version of Android. Also, I can no longer boot into recovery mode; instead I get a message saying "System software not authorized by Verizon Wireless has been found on your phone".
I thus decided to try to flash the phone from scratch.
First I tried to use ADB and Fastboot to make sure the bootloader is unlocked. Unfortunately, while ADB worked fine, I was never able to get Fastboot to see the phone, despite following the advice of several web pages addressing this issue, and trying several different drivers.
Pressing on, I decided to try to install TWRP again. Booted phone with VolDown, Home, Power. First I tried using Heimdall 1.4, both with drivers from Samsung, and then with the MSM8960 drivers that came with Heimdall, using this command:
heimdall flash --RECOVERY twrp-3.3.1-0-hlte.img --no-reboot
In both cases, all I got was "ERROR: Failed to access device. libusb error: -12"
Therefore, decided to try it with Odin. Booted phone with VolDown, Home, Power. Run Odin 3.12.4_4, which immediately shows "Added". Load TWRP 3.3.1.0 with AP button, click Start...and get a red Fail flag within a few seconds. Log shows "FAIL! (Auth). Phone shows "SYS REV CHECK FAIL: No Version" and "SECURE MAGICCODE CHECK FAIL: recovery".
I didn't even bother trying to flash the LineageOS ROM.
Can someone please tell me what I'm doing wrong? Please don't assume I know anything about what I'm doing.
--
*not an expert*
Verify that you are using the correct build of twrp-3.3.1.
I am using the hlte build of 3.3.1 on my phone (SCL22)... but my gut tells me that you and I wouldn't share the same build.
Nope basic problem is that OP is in the wrong forum for a Verizon phone .
Assuming that download mode still works (if it is, lucky you); I'd suggest reflashing the stock firmware for your Verizon device.
Flashing a stock firmware would *hopefully* fix your recovery and download issues.
Perhaps the errors you described may have been caused by installing the wrong ROM/firmware.
So, NEVER INSTALL/FLASH a custom or stock ROM that is not tested to work on your device. The main reason is because different variants of the same device (N9000, N900A, N900V) use different chipsets, software and drivers. Also, flashing a wrong ROM/kernel/firmware may cause application errors, boot loops, broken recovery/download mode, or a hard brick.