my sam gt-p1000 had problem - General Questions and Answers

need anyone advice and help.. for my problem..
sir, i want ask help.. my gadget samsung gt-p1000 had problems..
it just power on and shut down by itself.. and stuck in samsung logo.. and repeat power on again..
when i'm using recovery boot mode something occure :
the enter key for boot mode should be home key.. but in mine gadget.. become OK key, i can't use my home key to enter...
this condition too :
-- Verfing internal MMC block...
checksum confirmation -> check(1)
the # of partition : 3
part(1) BR_ChkSum in header : 94CE1E2144A86FEE9B8C810A30208A9D
part(1) BR_checksum : 94CE1E2144A86FEE9B8C810A30208A9D
part(1) DATA_Chksum in header : 696EA8F29ECB20C45B97B704AD543871
part(1) DATA checksum : 2184010839EB3D021EED0BB7EC395B51
E: part(1) DATA Checksum Error
E: part(1) Checksum Error
Internal MMC checksum verify failed.
# MANUAL MODE #
-- Updating application...
Successfully updated application.
-- Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'XSE'.
Successfully updated multi-CSC.

keitagusy said:
need anyone advice and help.. for my problem..
sir, i want ask help.. my gadget samsung gt-p1000 had problems..
it just power on and shut down by itself.. and stuck in samsung logo.. and repeat power on again..
when i'm using recovery boot mode something occure :
the enter key for boot mode should be home key.. but in mine gadget.. become OK key, i can't use my home key to enter...
this condition too :
-- Verfing internal MMC block...
checksum confirmation -> check(1)
the # of partition : 3
part(1) BR_ChkSum in header : 94CE1E2144A86FEE9B8C810A30208A9D
part(1) BR_checksum : 94CE1E2144A86FEE9B8C810A30208A9D
part(1) DATA_Chksum in header : 696EA8F29ECB20C45B97B704AD543871
part(1) DATA checksum : 2184010839EB3D021EED0BB7EC395B51
E: part(1) DATA Checksum Error
E: part(1) Checksum Error
Internal MMC checksum verify failed.
# MANUAL MODE #
-- Updating application...
Successfully updated application.
-- Appling Multi-CSC...
Installing Multi-CSC
Applied the CSC-code 'XSE'.
Successfully updated multi-CSC.
Click to expand...
Click to collapse
I have the same thing! found any solution?
Please help

Related

[Q] installion problem

E:can't open /cache/recovery/last_log
help me in this case ,i am still stuck on
recovery
my model is-p3100
plz fast reply
when i flashed sshdv4 rom
If you do full wipe and before flash kernel with odin?
sent from p3100
C:\Users\user\Desktop\galaxy_tab.zip: CRC failed in system\app\SecSettings.apk. The file is corrupt
! C:\Users\user\Desktop\galaxy_tab.zip: CRC failed in system\app\SemcAlbum.apk. The file is corrupt
! C:\Users\user\Desktop\galaxy_tab.zip: CRC failed in system\app\textinput-tng.apk. The file is corrupt
! C:\Users\user\Desktop\galaxy_tab.zip: CRC failed in system\framework\framework-res.apk. The file is corrupt
! C:\Users\user\Desktop\galaxy_tab.zip: CRC failed in system\lib\libSVIEngine.so. The file is corrupt
! C:\Users\user\Desktop\galaxy_tab.zip: CRC failed in system\lib\libfacerecognition.so. The file is corrupt
! C:\Users\user\Desktop\galaxy_tab.zip: CRC failed in system\vendor\lib\egl\libGLESv2_POWERVR_SGX540_120.so. The file is corrupt
-------------------------------------------------------------------------------------------------------------------------------------------

Unable to install any Rom , /system: No such file or directory

So I tried to install LineageOS on my Honor 8. I unblocked the Bootloader and I am currently able to get into TWRP and Fastboot Mode. I did change the filesystem for the cache system and data as described in this video: w w w. youtube.com /watch?v=X7yDPszoQ5s to enable the encrypted folders.
When I try to install any ROM I am getting the following Errors in red:
E: unknown command (log)
Updater process ended with ERROR: 7
Error installing zip file 'romname'
Also:
Skipping MD5 check: no MD5 file found
could not detect filesystem for /dev/block/bootdevice/by-name/system at /system: No such file or directory
unmount of /system failed; no such volume
patching system image uncoditionally...
E1001: Failed to update system image.

Soft-locked my phone?

Help me out here.
Basically, my situation is like this:
Recovery: Doesn't work, when i boot to recovery an error message like this appeared:
ERROR MODE
Attention!
Please update system again
*green android guy*
Error!
Func NO: 11 (recovery image)
Error NO: 2 (load failed)
Fastboot:
works, but flashing anything but openkirin's lineage os and the kernel results into this error:
FAILED (remote partition length get error)
Normal boot: goes to erecovery
i dont know what to do now, someone help me

Galaxy S8 SM-G950F

Hello i have a problem with my phone.
After installing the Stock firmware, it show up a blue screen with android guy and it says "Installing Update"
Then it restart to recovery and it shows this:
#fail to open recovery_cause (No such file or directory)
#Reboot Recovery cause is [UNKNOWN]
Support SINGLE-SKU
File-Based OTA
E:Failed to mount /efs: Invalid argument
Supported API: 3
E:Failed to mount /efs: Invalid argument
E:Unknown volume for path [/odm]
E:Unknown volume for path [/vendor]
E:Failed to mount /efs: Invalid argument
dm-verity verification failed...
E:[libfs_mgr]is_dt_compatible firmware info was not valid : '/proc/device-tre
/firmware/android/compatible: No such file or directory
Can someone help to solve my problem?
TheDoctorMoDz said:
Hello i have a problem with my phone.
After installing the Stock firmware, it show up a blue screen with android guy and it says "Installing Update"
Then it restart to recovery and it shows this:
#fail to open recovery_cause (No such file or directory)
#Reboot Recovery cause is [UNKNOWN]
Support SINGLE-SKU
File-Based OTA
E:Failed to mount /efs: Invalid argument
Supported API: 3
E:Failed to mount /efs: Invalid argument
E:Unknown volume for path [/odm]
E:Unknown volume for path [/vendor]
E:Failed to mount /efs: Invalid argument
dm-verity verification failed...
E:[libfs_mgr]is_dt_compatible firmware info was not valid : '/proc/device-tre
/firmware/android/compatible: No such file or directory
Can someone help to solve my problem?
Click to expand...
Click to collapse
Just reboot to system and that's it. Unless it just boot loops back to recovery.

Question Stock recovery error: SamMobile firmware footer is wrong; signature verification failed

Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
I’ve just flashed the full firmware.
The SW REV check failures were fixed, but my device is still being boot looped
What to do next?
My A12 has MTK chipsets (according to my CPU-Z), hence also their ‘‘secure’’ boot locks, now going to unlock it by their SPFlashTool
speedmetal444 said:
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
Click to expand...
Click to collapse
Heimdall flashes are always by PIT partitions; PIT means partitioning informative tables
Odin flashes, on the other hand, are instead more by tar packages, namely BL, AP, CP, and CSC
* BL = BootLoaders; AP = Android PDA’s i.e. systems with also recoveries; CP = Core PDA’s i.e. modems; CSC = Country support codes or Consumer software customizations
I’m still being boot looped due to sth in unknown errors named PDP
Code:
Android recovery
samsung/a12nsxx/a12
11/RP1A.200720.012/A125FXXU1BUE3
...
Supported API: 3
# MANUAL MODE v1.0.0#
No commands specified
-- Wiping data ...
Formatting /data ...
E: [PDP] lstat /c___/pdp_b__: 0 - No PDP scenario
Formatting /cache ...
Formatting /metadata ...
Formatting /keydata ...
Formatting /keyrefuge ...
Data wipe complete.
hd_scania said:
Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Click to expand...
Click to collapse
The error at the last is probably because the firmware you are trying to flash has older bootloader than what it is currently and it looks like you cannot downgrade bootloader.
I

Categories

Resources