[Update]: The device is now detected by the PC.
After being a moron and messing around with Google Play Services with Luckpatcher, I soft-bricked my tab. I then flashed an incorrect ROM onto it resulting in that blue screen with text If I remember saying the update was not installed correctly (I can't find the image on google but it's a known error screen).
Now after receiving the device from a phone repair shop it's stuck on the boot screen seemingly with the correct ROM on it but when launching into recovery it shows No Command and shortly after goes into the recovery menu.
No Support SINGLE-SKU
Supported API: 3
# MANUAL MODE v1.0.0#
-- Appling Multi-CSC. . .
Applied the CSC-code : BTU
Successfully applied multi-CSC
Successfully verify for dmverity hash tree
cant delete
Related
**I've searched, asked, tried many different files--still boot loops**
tl;dr What files do I use in Odin to return to stock from a phone that boot loops? (i have no idea what software was on there before it started)
The phone came from Canada (Bell). Previous owner tried to unlock it for use in the US. Phone worked for a few days then turned off & wouldn't get past boot (it would show animation & sound then go into a black screen with menu/back key lit up). It was also missing volume up/down keys. Phone was given to me as I was moving back to Canada. Now here I am in Canada...
I've ordered & replaced the volume keys, got into download mode, and using Odin I've flashed "I9000XXJVU_I9000OXAJVU_OXA". I've no idea what software version was on the phone at the time. I used pit 512. The phone reboots and...
Code:
-- Copying media files...
[COLOR="Red"]E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard
your storage not prepared yet. please use UI men
u for format and reboot actions.[/COLOR]
Meida files copy failed.
-- Wiping data...
Formatting /data...
Formatting /dbdata...
Formatting /cache...
Deleting Meta Data
[COLOR="Red"]Data wipe failed.[/COLOR]
-- Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'KOR'
Successfully applied multi-CSC
The failed actions are due to me not having an SD card correct? And at the bottom there it says it applied the CSC-code 'KOR' for Korea? I'm in Canada.
Now the phone goes into a loop, flashing the "Galaxy S GT-I9000 Samsung" logo on and off for ever (no animation or sound this time). I also tried flashing the latest from sammobile (under GT-I9000M). It's a single file and that put me in a boot loop as well.
Any advice greatly appreciated!!!
Try this:
[HOWTO] Flashing CWRecovery to i9000m & upgrade to ICS AOSP 4.x ROM from any version
Hello,
A friend gave me his previously new Samsung galaxy tab for T-Mobile tablet, he said he's ordered a new nexus 7,and doesn't need the galaxy anymore. The problem with it is when I power it on, it goes through the booting process (the animated screen with music)..then it just 'stops' @ the Samsung logo, and just stays there. When I power it down and press the power key + the volume + key together, it goes to the 'recovery' screen. It's says the following:
--Verifying internal MMC block...
checksum confirmation -> check(0)
Not need checksum confirmation
already executed!!...
# MANUAL MODE #
-- Updating application...
E:failed to mount /preload (No such file or directory)
E:install_application_for_customer:Can't mount /preload
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed.
--Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/PHN/system/'.
Successfully applied multi-CSC.
Does all of this actually mean the tablet is 'un-usable', or can it somehow be re-loaded with 'stock' firmware ? The previous owner never rooted this tablet, or installed ClockWorkMod on it either. Hopefully....someone else has had this issue before.
Thanks,
David :crying:
Try to flash the SHW-M180S firmware...I m using it on my t849 and it works like charm
Just google "White Identity Final.tar" (4shared)
Hello,
I'm struggling with my s10, SM-G973F, i was rooted and twrp etc, then i decided that i want the q beta, went to ASII signup for the members ap to get the beta and tried 3 way's to run the update by SD card - could not mount the sd card and adb way and this failed, and offcourse i tryed trough the phone Software update but this had failed as well, can anyone give me a hint hot get this done.
When i'm on ASII if i try by card i get:
Reboot recover Cause is [BL: Recovery Mode is set by key)#
Support SINGLE-SKU
#Manual Mode v1.0.0#
E: Failed to mount /sdcard: no such file or directory
-- Couldn't mount sdcard.
Installation Aborted
When i do it trough adb is say it successful but i get every time on botloop , and i have downloaded the update from different sources.
Updated firmware to BTU: ASJD trough smart switch and then followed the the steps and downloaded the update ZSK3 (it showed directly beta 3) trough the software update from settings, after all done i end up in bootloop again.
Can anyone help with this, i spent my Saturday on this silly thing.
Many Thanks
Did you relocked the bootloader?
Hey guys,
Here's the situation. I was in the process of completing the setup of my 768GB Note 8 (SM-N950N) with Dr.Ketan P12 custom ROM, and RZ Kernal (for DriveDroid support). Out of nowhere, my Note 8 camera just stopped working, and the Dr.Ketan ROM Tools and Tweaks Pro apps could no longer be opened. I began back-tracking my steps; tried reverting magisk back to v20.1, tried dirty flashing the ROM again, all to no avail. In the process of troubleshooting, figured it could be something I toggled under developer settings. Noticed that my OEM Unlock toggle was turned on, even though I recall seeing it turned off earlier during the configuration process (as explained by @dr.ketan here, scroll to Note for OEM Issue). Thinking it's ineffective, I turned it off and was prompted to reboot my device, just to get stuck at the boot screen
I came across the following forum post describing how to recover from the boot loop, without needing to delete any data, by flashing the latest available official firmware AP***.tar (removed the .md5 extension) file using Odin3:
https://forum.xda-developers.com/sprint-galaxy-s6/help/custom-binary-blocked-frp-lock-how-t3581010
The problem is, during the flashing of the Dr.Ketan P12 custom ROM, I chose to flash the SM-N950F OMC for SM-N950N, in order to use a Korean-Free CSC (more details on why explained here). So, even though I've attempted all of the following:
- flashed the current latest available official firmware AP***.tar file for SM-N950N,
- simultaneously flashed the current latest BL/CP/HOME_CSC***.tar.md5 and AP***.tar firmware files via Odin,
- flashed the latest TWRP***.tar custom recovery (failed probably due to OEM unlock being disabled),
- wiped cache via the stock recovery,
- tried booting via the "Lacking storage booting" option in the stock recover,
- tried booting to safe mode,
- tried using Smart Switch for PC, it (nor its Emergency Software Recovery) never detected my Note while stuck at the Samsung boot logo, nor did it detect it in Recovery mode,
- etc.it still won't boot-up, and I think it's due to the CSC (UK Unbranded - BTU) not being available in the official firmware.
When I boot into recovery mode, I get the following message:
Code:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGL-SKU
File-Based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
# MANUAL MODE v1.0.0#
can't open directory '/system/omc/SUP/etc/sysconfig' . (No such file or directory)
can't open directory '/system/omc/SUP/etc/cid/sysconfig' . (No such file or directory)
can't open directory '/system/omc/SUP/etc/permissions' . (No such file or directory)
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : '/proc/device-tree/firmware/android/compatible' : No such file or directory
Would any of you folks have suggestions on how I could recover from this mess without needing to delete any data? Perhaps if there was a way I could add the UK Unbranded CSC to the official SM-N950N firmware and flash it via Odin, maybe that'll allow it boot? Please kindly advise, thanks in advance.
Bump
please i have the same proplem what to do
i dont know the meaning of bumb
please help
ah_1st said:
please i have the same proplem what to do
i dont know the meaning of bumb
please help
Click to expand...
Click to collapse
No luck on my end, lost months worth of data on my internal storage. Had to perform a factory reset on my Note 8 via Odin, reflash TWRP via Odin, then reflash my Custom ROM and tweaks. Lesson learned for real though
First off, I'm a little out of my depth here.
I had originally wanted to root my A8, but stopped short because it isn't officially supported by TWRP. I wanted to roll things back but botched the Odin process. I flashed the AP file but didn't include any of the others. As a result, I can't get into the bootloader. I'm not sure what my options are at this point, or if I have any.
I've already wiped the cache partition and done a data/factory reset.
Output on my Recovery screen is as follows:
Code:
Failed to load locales from the resource files, Failed to compare
#Reboot Recovery Cause is [UNKOWN]#
#Reason is []#
E:Failed to load bitmap installing_text for locale en-US (error -1)
Supported API: 3
# MANUAL MODE v1.0.0#
No command specified.
I'm hoping there's a procedure for completing loading in the other files, or getting back into the bootloader.
Do I have any hope or did I truly brick this thing?
Ok, I got it back by using vol up/down and plugging in the USB. Wasn't able to do it from the recovery, but the physical method worked. Odin worked, I'm back in business.