Hi Guys,
samsung/gts311texx/gts3llte
8.0.0/R16NW/T825XXU2BRL2
really struggling with my TabS3 which is about 1.5years old. Had sent it to Samsung for repair but they sent it back without repairing the problem.
was fine until a few weeks ago the battery had died within a few hours of charging. I charged again and noticed it was just bootlooping but was occasionally giving a blue screen error saying no command then in recovery was showing failed to verify diverity hash tree
It hasnt been possible to get into android to enable OEM unlock due to bootlooping issues
was running stock firmware and not rooted
I tried to reinstall stock firmware from samfirmware via Odin but was just giving an error when flashing AP
now when booting its giving " an error has ocurred while updating the device software. use the emergency recovery function in the smart switch pc software"
in recovery giving error dm-verity verification failed... E:failed to mount system (invalid argument)
any ideas? £20 reward if helps get it sorted!
NI3K said:
Hi Guys,
samsung/gts311texx/gts3llte
8.0.0/R16NW/T825XXU2BRL2
really struggling with my TabS3 which is about 1.5years old. Had sent it to Samsung for repair but they sent it back without repairing the problem.
was fine until a few weeks ago the battery had died within a few hours of charging. I charged again and noticed it was just bootlooping but was occasionally giving a blue screen error saying no command then in recovery was showing failed to verify diverity hash tree
It hasnt been possible to get into android to enable OEM unlock due to bootlooping issues
was running stock firmware and not rooted
I tried to reinstall stock firmware from samfirmware via Odin but was just giving an error when flashing AP
now when booting its giving " an error has ocurred while updating the device software. use the emergency recovery function in the smart switch pc software"
in recovery giving error dm-verity verification failed... E:failed to mount system (invalid argument)
any ideas? £20 reward if helps get it sorted!
Click to expand...
Click to collapse
Just a couple of thoughts. Do you know what error you were getting in Odin? Are you using the latest version of odin, 3.13, and try downloading the stock firmware from updato.
Sent from my [device_name] using XDA-Developers Legacy app
using odin 3.13, when trying to flash its showing no errors in odin just FAIL! (Auth) and tablet screen showing secure check fail: aboot [1]eMMC write fail: aboot
Internal memory issue maybe? tried a version from updato, similar story
NI3K said:
using odin 3.13, when trying to flash its showing no errors in odin just FAIL! (Auth) and tablet screen showing secure check fail: aboot [1]eMMC write fail: aboot
Internal memory issue maybe? tried a version from updato, similar story
Click to expand...
Click to collapse
Are you flahing the same firmware version that's on your device, BLR2? aboot is the bootloader and it looks like it's failing trying to write that. If your flashing an earlier version of firmware you'll get that error. But it could also be caused if eMMC is bad. When you sent it to Samsung did they do anything to it, or tell you anything that might be wrong? When you boot into the bootloader what does it say about FRP lock?
Edit, also, if you're not, run Odin as administrator.
Sent from my [device_name] using XDA-Developers Legacy app
FRP lock: On
I'm not completely sure which firmware was on the device, was assuming BLR2. Done a successful flash in Odin (using BLR2) but still only boots to recovery giving error -
#fail to open recovery_cause (no such file or directory)#
No support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed
Samsung only told me its a non EU device but couldnt tell where it originated from and that they can't help as components are different from EU devices
any ideas?
NI3K said:
FRP lock: On
I'm not completely sure which firmware was on the device, was assuming BLR2. Done a successful flash in Odin (using BLR2) but still only boots to recovery giving error -
#fail to open recovery_cause (no such file or directory)#
No support SINGLE-SKU
File-Based OTA
Supported API: 3
dm-verity verification failed
Samsung only told me its a non EU device but couldnt tell where it originated from and that they can't help as components are different from EU devices
any ideas?
Click to expand...
Click to collapse
Ok, so you don't know what country the device came from? And I assume you're in the EU? There's a few things to try. Have you tried Samsung's smart switch program, Google it. I haven't had luck with their software but maybe it'll work. And might identify your device.
Also, try flashing just the bootloader with Odin. I assume you're trying to flash just the AP binary. Try flashing just the bootloader. Choose BL in Odin and the BL file from the stock firmware. Don't flash anything else. See if that will flash and then boot.
I believe the device was from China but seems to have been running UK software as thats the only firmware that will load without a dev_error
Smart switch didnt identify it as a device which could be repaired
tried flashing bootloader only, same issue of bootlooping or automatically booting to recovery.
I have flashed to older android version T825XXU2BRJ1 but exactly the same issue of bootlooping/recovery
Even im facing same problem without any solution.
I'm so sorry that this happened. I would've tried to help you IF ONLY MY TAB WASN'T HARD BRICKED
Related
Hi there,
My moto e 2nd gen got stuck in bootloader and won't boot.
The monitor displays as below:
**********************************************
Start Up Failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
EROOR: Failed to pass validation, backup fastboot
Fastboot Reason: Fall-through from normal boot mode
BL:
Baseband: M8916_2020629.41.03.21.51R SURNIA_RECTA_CUS
Product/Variant: surnia XT1527 8GB P3
Serial Number:
CPU:
eMMC:
DRAM
Console [NULL]: null
Battery OK
Device is LOCKED. Status Code: 0
Software status: Official
Connect USB Data cable
**************************************************
In the Recovery Mode display, I see "qe 0/0" which I learned from the other thread that it means the device has never been rooted.
Below is how this happened;
I used the app called KingRoot.
But the app says failed to root the device.
My phone acted weird so I uninstalled KingRoot.
Then I tried to remove the .exe file of KingRoot but failed somehow.
Right after I just turned on some secure feature (which warns the user that the app may be harmful?) of the device, the device went black and displayed the bootloader screen.
Below is what I have done so far:
Wipe cache partition (successful), then Reboot the system (Failed)
Wipe data/factory reset (successful), then Reboot the system(Failed)
Apply update from ADB with the stock Rom I found in the [http://firmware.center/firmware/Motorola/Moto E (2nd gen-2015)/Stock/XT1527/] but received error as below,
***********************************************
Finding update package...
Opening update package...
Verifying update package...
E:footer is wrong.
E:signature verification failed.
Installation failed.
************************************************
Then, I flashed three image files (recovery, boot, bootloader) using fastboot command (without unlocking bootloader).
I did not use the bootloader unlocking command.
So I thought the flashing would failed but somehow succeeded only with recovery.imag.
I believe my device has never been rooted and the bootloader has never been unlocked.
Is it possible that KingRoot has modified some system files even when the device has never been rooted and the bootloader has never been unlocked?
And how can I fix my bricked moto e?
Could someone help me out on this please? :crying:
quicksand99999 said:
Hi there,
Click to expand...
Click to collapse
Flash stock firmware. BTW you asked in the wrong thread. This is for moto e1
drs22 said:
Flash stock firmware. BTW you asked in the wrong thread. This is for moto e1
Click to expand...
Click to collapse
Hi Thank you for the reply and pointing-out.
I re-posted the thread in E 2015.
Regarding flashing stock rom, I flashed three image files and two of them failed due to the older version.
Is it possible to flash the entire files without unlocking the bootloader?
I have got marshmallow stock rom and have never tried to flash.
Hope you reply me back in my thread in Moto E 2015 forum.
Hi,
I believe my nexus 5x is "soft bricked" or in a "boot loop" (sorry newb here). The phone will restart and turn off during the boot animation. I am able to get into recovery mode and have attempted to use adb sideload to apply the latest 7.1.1 OTA zip from google's website. During that process (50% through) it said I could not update it because I needed to load a current or newer version. I realized I am on beta 7.1.1 NPF26F but am unable to locate the OTA zip for this.. I did download one online (seemed legit) but got an error E: signature verification failed, E: error 21. At this point I am a bit lost and unsure what to do.. any help would be appreciated.
Mike
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
es0tericcha0s said:
Is your bootloader unlocked? If so, then just install the whole system update, not just the OTA. This will get your off of the beta and onto the official update as well.
Click to expand...
Click to collapse
I do not believe my bootloader is unlocked. I tried to go through the " fastboot oem unlock " steps today but I need to turn on USB debugging on the device (which I cannot do) to even have that option. Will I need to wait until the OTA.zip is released or is there another way ?
http://storage.googleapis.com/andro.../preview/bullhead-npf26f-factory-0e9ab286.zip
is this the factory image or the OTA?.. guessing by the size its the factory image. I am unaware how to flash this if my USB debugging is LOCKED. Please help
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Meranico said:
Hey!
I have a problem with my Honor 9 (STF-L09C432): It's not booting properly. Bootloader and FRP are unlocked.
First of all: I have TWRP (from here) and the boot.img and system.img came from here. I unpacked them with the Huawei Update Extractor. I flashed those (via fastboot) again after I installed Xposed, because that gave me a bootloop. Too bad it couldn't fix this.
After booting the phone the message, that my phone cannot be trusted, appears, then the Honor Logo, then the message again and then the eRecovery. Inside the eRecovery I can only download the latest version, which is too bad, because I cannot connect to my WiFi as he says the Password of the AP is wrong (which is not). Edit: Tried it with an unprotected Access Point, still failed (Could not retrieve Package Info or something like that).
I don't know where I went wrong and why it won't boot anymore, so you are my last hope!
Edit: I also tried the update menu (Volume Up and Down while Powering on) with the B150 update in the DLOAD folder. But it just goes to 5 % and shows "Software install failed!".
Edit2: I would also be fine by hard formatting the complete system and reflashing a stock ROM. But first I'd need to know how to format the system and second I need a stock ROM.
Edit3: When I tried to reflash Magisk (I read that it could fix some errors like this), I got another error: "Failed to mount '/system' (Device or resource busy)"
Click to expand...
Click to collapse
If you can boot to "downloader" use rebranding SW, it will fix everything
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
Thank you so much! My mobile phone is working again! :victory:
Edit: Small problem persists: I cannot use the buttons left and right of the scanner. They do not react.
Edit2: Could fix this. I flashed B120 and the buttons worked again.
FearFac said:
If you can boot to "downloader" use rebranding SW, it will fix everything
Click to expand...
Click to collapse
whats rebranding sw and hoe do i do it as i have the smae problem please help
corey568brown said:
whats rebranding sw and hoe do i do it as i have the smae problem please help
Click to expand...
Click to collapse
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Meranico said:
Look here. Everything is explained in this thread. I recommend flashing B120 (it is linked in the thread) and updating via Firmware Finder and Firmware Finder Proxy.
Click to expand...
Click to collapse
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
corey568brown said:
no worries all fixed now except for the touch buttons i used this :https://forum.xda-developers.com/honor-9/how-to/guide-honor-9-t3653719
but if you have any idea how to fix the buttons it would be appreciated.
Click to expand...
Click to collapse
Good to know!
As I had the same problem as you do know: I flashed B120, which does not seem to have the bug with the buttons and upgraded via Firmware Finder to B130 and then to B150.
honor 9 stf-al00
phone unlocked and frp unlock
bricked the phone installing oreo.
twrp is installed but all the roms i flash i get error 9.
dload with update.app get stuck at 5% and after "system update failed"
i also extracted update.app and i can flashed boot,kernel and recovery but i get an error flashing system
At this point i just want the phone running anything but everything that i do doenst work
"FRP Unlock SM-T377W, Unsuccessful on 7.1.1 ? Help Please"
I have SM-T377W with 7.1.1
I tried to flash it with this COMBINATIONS firmware
COMBINATION_OYA_FA60_T377WVLU3ARG1
Then I used the Z3x Tool to reset FRP, it says "OK"
however, then when I put it again on Download mode it is still Locked FRP
Also when I re-flash it with OEM it still ask for Google Verification
I also tried to flash it with TWRP to Root it but I keep getting
Custom Binary Block by FRP Lock
IS THERE A WAY TO REMOVE FRP FROM THIS DEVICE ?
--------- OEM flash in this device is ----------
Canada (Rogers)
PDA: T377WVLU3BRG4
Product Code: RWC
CSC: T377WOYA3BRG4
Phone: T377WVLU3BRG4
-------------------------------------
Any Suggestions Guys ?
Regards
msaithan said:
"FRP Unlock SM-T377W, Unsuccessful on 7.1.1 ? Help Please"
I have SM-T377W with 7.1.1
I tried to flash it with this COMBINATIONS firmware
COMBINATION_OYA_FA60_T377WVLU3ARG1
Then I used the Z3x Tool to reset FRP, it says "OK"
however, then when I put it again on Download mode it is still Locked FRP
Also when I re-flash it with OEM it still ask for Google Verification
I also tried to flash it with TWRP to Root it but I keep getting
Custom Binary Block by FRP Lock
IS THERE A WAY TO REMOVE FRP FROM THIS DEVICE ?
--------- OEM flash in this device is ----------
Canada (Rogers)
PDA: T377WVLU3BRG4
Product Code: RWC
CSC: T377WOYA3BRG4
Phone: T377WVLU3BRG4
-------------------------------------
Any Suggestions Guys ?
Regards
Click to expand...
Click to collapse
i am having the exact same problem as you with a samsung j1
cant get the custom recovery modes onto the phone.
odin flashes the stock rom no problem, but i cant get SR1-SuperSU-v2.78-SR1-20160915123031 or twrp on the phone.
DaDirtiest said:
i am having the exact same problem as you with a samsung j1
cant get the custom recovery modes onto the phone.
odin flashes the stock rom no problem, but i cant get SR1-SuperSU-v2.78-SR1-20160915123031 or twrp on the phone.
Click to expand...
Click to collapse
yea i have been trying for days now with no luck !
FRP Unlock solution for SM-T377W
msaithan said:
yea i have been trying for days now with no luck !
Click to expand...
Click to collapse
This is the only method that worked to solve the FRP lock issue. The video is not in English but you can still follow the instructions.
youtube_com/watch?v=NplMF8O2aTk&t=579s&index=2&list=LLWLJUl2J_mwEvi3FgXukeUA
Ray_D_2018 said:
This is the only method that worked to solve the FRP lock issue. The video is not in English but you can still follow the instructions.
youtube_com/watch?v=NplMF8O2aTk&t=579s&index=2&list=LLWLJUl2J_mwEvi3FgXukeUA
Click to expand...
Click to collapse
You are a Legend BRO (+ who made the video), finally i unlocked the Samsung SM-T377W from rogers
I had the correct files (combination + stock) its just that one step i was missing, the final step of combining the 3 correct files (sboot, boot + system)
I appreciate it bro
Ray_D_2018 said:
This is the only method that worked to solve the FRP lock issue. The video is not in English but you can still follow the instructions.
youtube_com/watch?v=NplMF8O2aTk&t=579s&index=2&list=LLWLJUl2J_mwEvi3FgXukeUA
Click to expand...
Click to collapse
i followed to youtube tutorial and succesfully flashed my A520w using COMBINATION_OYA_FA60_A520WVLU1AQC1 but i cannot get the phone to reboot any suggestions?
the odin operation was a success so are there other things i should push up in this phone and how can i get it to reboot its really weird i can only put it into download mode before it gave me the message about operating system error use samsung smart switch software, now it doesnt do that its just black screen of death when i choose rebooot
DaDirtiest said:
i followed to youtube tutorial and succesfully flashed my A520w using COMBINATION_OYA_FA60_A520WVLU1AQC1 but i cannot get the phone to reboot any suggestions?
the odin operation was a success so are there other things i should push up in this phone and how can i get it to reboot its really weird i can only put it into download mode before it gave me the message about operating system error use samsung smart switch software, now it doesnt do that its just black screen of death when i choose rebooot
Click to expand...
Click to collapse
You might want to try and do a factory reset at this point and see if that resolves the issue. Alternatively, maybe trying loading the stock software ROM through download mode and retry the process.
GuestD0091 said:
You might want to try and do a factory reset at this point and see if that resolves the issue. Alternatively, maybe trying loading the stock software ROM through download mode and retry the process.
Click to expand...
Click to collapse
did the 3 file combination
then flashed with stock rom
now finally into the phone, but
stuck at the frp lock screen
A520W with videotron
Trying to flash the latest factory image I got a message
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
Tried again but the same happened. When tried to reboot i got the "Your device is corrupted" mesasge and now i have a battery symbol in the middle of a black screen and nothing is responding. Any ideas?
Small update. I managed to go into bootloader again but i still get the same mesage even when i try to flash with the -w flag.
arvylas said:
Small update. I managed to go into bootloader again but i still get the same mesage even when i try to flash with the -w flag.
Click to expand...
Click to collapse
It's a known problem with the lastest platform tool (v.34). Reboot to bootloader and flash the factory image again with either Android Flash Tool or older version of platform tool (v. 33.0.3) would solve your problem.
To delete.
RhapsodyK said:
It's a known problem with the lastest platform tool (v.34). Reboot to bootloader and flash the factory image again with either Android Flash Tool or older version of platform tool (v. 33.0.3) would solve your problem.
Click to expand...
Click to collapse
Yup, thats the case. I just tried before seeing your reply. I flashed with platform tools 33.0.3 even with the -w removed and it worked. Booted fine
I still get "Your device is corrupt" at boot but everything works fine though.
arvylas said:
I still get "Your device is corrupt" at boot but everything works fine though.
Click to expand...
Click to collapse
To be edited.
No, right now I have a warning screen before that with a red triangle. If you Google the message you'll see it. Usually this screen comes up when verity is not enforcing but in my device is enforcing and the message still shows up at boot.
arvylas said:
No, right now I have a warning screen before that with a red triangle. If you Google the message you'll see it. Usually this screen comes up when verity is not enforcing but in my device is enforcing and the message still shows up at boot.
Click to expand...
Click to collapse
Sorry I was confused with the message "Your bootloader is unlocked and software integrity cannot be guaranteed." Silly me!
Try repairing and updating it again by using Pixel Update and Software Repair Tool from Google
RhapsodyK said:
Sorry I was confused with the message "Your bootloader is unlocked and software integrity cannot be guaranteed." Silly me!
Try repairing and updating it again by using Pixel Update and Software Repair Tool from Google
Click to expand...
Click to collapse
Thanks, I'll try it a bit later. Is this user data safe? Or it will wipe everything?
arvylas said:
Thanks, I'll try it a bit later. Is this user data safe? Or it will wipe everything?
Click to expand...
Click to collapse
It will wipe everything. I would suggest you try the Google Flash Tool first, which you have the option the flash the factory image without wiping.
Heyya, i had the exact same issue, luckily we didn't brick the phone as some people had that happening, to remove the corrupt message, flash the Feb update using android flashing tool and then flash the march update after using the same android flashing tool site, that was the only way i managed to remove that, just wiping the phone or locking and relocking the bootloader won't do the trick also because the phone doesn't continue to the bootloader automatically because of that corrupt notification, here and there while the installation is happening you will have to click the power button to enter into the bootloader but just keep and eye on it and anytime you see you are on the corrupt screen click the power button to continue