Database Info

i9003 problem!!!!

dear~
i have a problem in my gt-i9003
stopped on samsung icon~~! tow days like this i try install more than 5 rom,s ….same problem
i enter system recovery menu to now what is the problem this massage shown to me:
–Movi_check Start..!!
movinand open fail
Movinand Checksum Confirmation Fail
Ifs pass open fail
–movi_checking undone!..
update media.plese wait
E:Can,t mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media:Can,t mount SDCARD:
your stroge not prepared yet plese use UI menu for format and reboot actions.
copy default media content failed.
plese take me a solution

after flash with odin appear this error~

Avoiding errors when installing Android IA on Samsung XE700T1C

Like a lot of others I've was repeatedly getting the following error when attempting to install the XE700T1C Android IA image -
fatal: assertion failed bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr encountered an error (status 100)
[email protected]:/#
This is related to the secure keys of the hardware and the EFI boot loaders which are used to install Android IA.
To install sucessfully, select the MokManager option from the boot menu and select to 'Import hash from disk' - choose the bottom option then browse to the BOOT/EFI folder and select to trust each of the .EFI files - when prompted press 0 then Y to import the keys.
After this the installation will happen without the error.
Hope this helps anyone getting as wound up by this error as I've been.
Cheers.

catmand0 said:
Like a lot of others I've was repeatedly getting the following error when attempting to install the XE700T1C Android IA image -
fatal: assertion failed bootable/iago/plugins/gummiboot.c:gummiboot_execute:154 'efibootmgr encountered an error (status 100)
[email protected]:/#
This is related to the secure keys of the hardware and the EFI boot loaders which are used to install Android IA.
To install sucessfully, select the MokManager option from the boot menu and select to 'Import hash from disk' - choose the bottom option then browse to the BOOT/EFI folder and select to trust each of the .EFI files - when prompted press 0 then Y to import the keys.
After this the installation will happen without the error.
Hope this helps anyone getting as wound up by this error as I've been.
Cheers.
Click to expand...
Click to collapse
Hello,
i've found a solution. Problem is AI installer can't add boot entry in EFI, but all necessary files are stored in right place. All you need is a EasyUEFI 1.8 to manually add boot entry into EFI Boot Mgr.
After install an run program just select "Create", choose type as "Linux", enter boor entry name "Andoid", select partition with "combobox". After that select ".efi" file in bottom file chooser (gummiboot.efi) it must be in "/" of EFI Partition.
Next and last what you need is select that record to boot first.

black screen on boot ,samsung gt-i9003

hello every one here ,
i have a samsung gt-i9003 which initially had a problem on boot showing the following :
Code:
E:failed to mount /data (No such file or directory)
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_cache_media:Can't mount /sdcard
your strotage not prepared yet. please use UI menu for format and reboot action
Media file copy faild.
# NORMAL MODE #
-- Appling Multi-CSC..
Instaling Multi-CSC
multicsc : scan access to ojpcom.
multicsc : scan access to ojpom.
multicsc : opera mini[lib] reset.
Appling the CSC-code 'MID'.
successfully applied multi-CSC.
i tried this solution : http://forum.xda-developers.com/showthread.php?t=2382961
after flashing the PIT file ,the phone's screen become black and i can no more access recovery .
removed battery and held power button and reinserted battery , turned on the phone ,and then it just vibrates and shows a black screen .
please please help me out .

[GUIDE] Update to CRC7/CRD7 with root without clear data and enter jail again

Hello Folks
##IMPORTANT##I'm not responsible if soft brick occurs or a nuclear war starts. This steps I maked and work flawless
Attached bootimg has dm-verity disabled and encryption enabled. If your system has different combination make a new image.
- boot image for G950F/FD only, S8.
This guide intent to update from any OREO rooted to CRC7/CRD7 without loose Magisk and without wipe. Process work flawless if you maintains the same characteristics. Today I updated from CRC7 to CRD7 with this method.
To do this:
1) in a first edit "BOOT.IMG" and comment 2 lines from "init.samsungexynos8895.rc" to prevent VAULTKEEPER to relock or system changes "OEM Unlock" option.
symlink /dev/block/platform/11120000.ufs/by-name/STEADY /dev/block/steady on line 29 and
symlink /dev/block/platform/11120000.ufs/by-name/PERSISTENT /dev/block/persistent on line 32
(attached modified and patched version)
2) repack "BOOT.IMG" and place on internal storage. Use Magisk Manager to patch modified bootimg and generate TAR for ODIN.
3) make backup and grant "OEM Unlock" enabled before start.
4) ##IMPORTANT## enable "Secure Startup". Without this option enabled, first boot always require PIN, and if not defined... wipe.
5) prepare stock CRC7 image. For LZ4 version use Odin 3.13.1 (attached).
6) open Odin and place "BL_G950FXXU1CRD7_CL13396511_QB17776043_REV00_user_low_ship.tar.md5" to BL, "AP_G950FXXU1CRD7_CL13396511_QB17776043_REV00_user_low_ship_meta.tar.md5" to AP, "CP_G950FXXU1CRD1_CP9423385_CL13386667_QB17686073_REV00_user_low_ship.tar.md5" to CP and "HOME_CSC_OXM_G950FOXM1CRD5_CL13396511_QB17715765_REV00_user_low_ship.tar.md5" to CSC.
7) ##IMPORTANT## unmark "Auto Reboot" option.
8) put device in DOWNLOAD mode. Power off and press vol down + bixby + power. In a warning, press vol up.
9) press "Start" and wait process.
10) when finished, disconnect and press vol down + bixby + power and wait reenter download mode. Do not leave keys before warning screen. Press vol up.
11) press "Reset" button on Odin and load modified boot image on AP.
12) connect device and press "Start".
After this, enjoy CRD7 version without wipe!
After update "OEM Unlock" stay in disabled state because persistent partition is inaccessible. But BL shows "OEM LOCK: OFF".
REMEMBER!!!
- enable "Secure Startup"
- do the same combination
- this process work without wipe for a previous rooted devices. If you update without root and try this, wipe occurs!
Because of size of attachments I need to upload on a external host.
Attachments (boot image for G950F/FD):
CRD7
patched_boot-crd7.img.tar.zip -> modified image patched to Magisk 16.0 with dm-verity disabled and encryption enabled
http://www.mediafire.com/file/xeift5aeh7aido3/patched_boot-crd7.img.tar.zip
boot-modified-crd7.zip -> stock image with modifications without any root patches
http://www.mediafire.com/file/iur372vya8vqfmb/boot-modified-crd7.zip
CRC7
patched_boot.img.tar.zip -> modified image patched to Magisk 16.0 with dm-verity disabled and encryption enabled
http://www.mediafire.com/file/1gjypdagydotyry/patched_boot.img.tar.zip
boot-modified.zip -> stock image with modifications without any root patches
http://www.mediafire.com/file/6jsdlzu9lkgwx3p/boot-modified.zip
Odin3_v3.13.1.zip -> Odin with support to LZ4
http://www.mediafire.com/file/yp78xi3uccv5o5k/Odin3_v3.13.1.rar

knox trip? im on official crc7

Yes... KNOX trip.
My device already tripped. This guide is for a rooted devices.

Are people mistyping crb7 and really mean crb9?
My Oreo update isn't CRB7 or CRC7. It is CRB9. Which of the three is the newest?

CRB7 is a international version - G950F or G950FD.
CRB9 is a AT&T version. No compatible.

I'm on Crap. Could I use this guide? If not, how can I make it? Thank you!

rikawa said:
I'm on Crap. Could I use this guide? If not, how can I make it? Thank you!
Click to expand...
Click to collapse
Maybe work. I only tested on CRB7 to CRC7 because my device was on these version, but in theory, this work flawless from CRAP to CRC7.

ivcarlos said:
Maybe work. I only tested on CRB7 to CRC7 because my device was on these version, but in theory, this work flawless from CRAP to CRC7.
Click to expand...
Click to collapse
I'll give a try. Just one more question. I'm not encrypted, how can I make a new bootimg? Thank you!

rikawa said:
I'll give a try. Just one more question. I'm not encrypted, how can I make a new bootimg? Thank you!
Click to expand...
Click to collapse
You can download "boot-modified.zip" and patch with Magisk Manager on your device. Remember to set the option "output format" to ".tar". Or you can take "boot.img.lz4" from stock image, unmount, make modifications on specified file, remount and patch with "Magisk Manager".
These file, "boot-modified.zip" contains only stock bootimg with modifications on "init.samsungexynos8895.rc".
Remember, after update "OEM Unlock" stuck in disabled state, but BL shows "OEM LOCK: OFF". This occurs because persistent partition remains inacessible.
After update you can disable TIMA and VAULTKEEPER on "build.prop" with a privileged editor.

What's the difference between following this guide and flashing this (except for the added twrp and modem)?

Android reboots every 3 minutes (Magisk, TWRP, firmware upgrade, Galaxy A6)

I’d be much obliged for your guidance, gentle people.
## The issue
My device (a TWRP’d, Magisk’d Samsung Galaxy A6) boots into Android 10, but can be relied on to reboot every 3 minutes thereafter. Call it a long bootloop, if you like.
## The error message
I’m not sure if this is relevant, but booting into TWRP and running a factory reset results in the following message:
Factory reset complete​Failed​
Failed to mount ’/data’ (invalid argument)​Unable to recreate /data/media folder.​Updating partition details…​Failed to mount ’/data’ (invalid argument)​…done​Unable to mount storage​Failed to mount ’/data’ (invalid argument)​Full SELinux support is present.​Unable to mount /data/media/TWRP/.twrps​MTP Enabled​Failed to mount ’/data’ (invalid argument)​Formatting Cache using make_ext4fs…​Updating partition details…​Failed to mount ’/data’ (invalid argument)​…done​Unable to mount storage​
## How did I get here?
Here’s a short version of the story. I:
(1) Downloaded stock firmware with Samloader.
(2) Flashed the firmware (with heimdall-frontend, leaving the repartition option unselected), but not all of it: only the files in
AP (substituting a TWRP recovery.img for the stock one),
CP, and
HOME_CSC,
i.e. omitting the files in BL.
(3) Used TWRP to Wipe > Format data.
(4) Still using TWRP, installed zips for RMM_bypass and no-verity-opt-encrypt, and rebooted.
## And what did I do before that? And why?
Until recently, I’d been running the factory-installed OS, Android 8. I figured it was time for a firmware update, but the modifications I’d made (as mentioned above, Magisk and, presumably more to the point, TWRP) meant that I wasn’t getting OTA updates.
So I started following some instructions [1] for getting an OTA update installed on a Magisk’d device.
## Uninstalling Magisk
The first step was to open Magisk Manager and tap Uninstall > Restore Images. Without really understanding what I was doing, or if there were any risks involved, I did that.
## Firmware update: first try
The next step was to install the OTA update: “Head over to Settings > System > System Update > Download and install the latest available OTA.” Well, that didn’t work. Said the popup: “The operating system on your device has been modified in an unauthorised way, etc., etc.“ Ah yes, that’s why I haven’t been getting updates in the first place.
So what to do now? As already mentioned, I used Samloader to download the latest stock firmware for my model and region. I decrypted and unzipped the .zip.enc4 file, to find tar.md5 files with the prefixes BL, AP, CP, HOME_CSC and CSC.
Now, topjohnwu’s instructions for installing Magisk on Samsung devices include the following warnings:
Never, ever try to restore either boot or recovery partitions back to stock! You can easily brick your device by doing so, and the only way out is to do a full Odin restore with data wipe.
Click to expand...
Click to collapse
And:
To upgrade your device with a new firmware, NEVER directly use the stock AP tar file with reasons mentioned above. Always pre-patch AP in Magisk Manager before flashing in Odin. [2]
Click to expand...
Click to collapse
So I attempted to follow his instructions, adb-pushing the AP_...tar.md5 file to the device and then asking Magisk Manager to patch it. But Magisk Manager failed to patch the file. I got an error message saying "device not connected”, or something like that. (This didn’t make any sense to me, but at the time I guessed that it was perhaps a result of having already tapped on Uninstall > Restore Images.)
## Short bootloop and factory reset
I carried on regardless. My next step was to reboot the device. I suppose I wanted to know what the effect of Uninstall > Restore Images was going to be; voilà, it was, perhaps predictably, a (short) bootloop (Samsung/Knox/Android splash screen only).
But I could still boot into recovery, so firstly I tried to restore the old backup I’d made with TWRP when I first installed it. The attempt was not successful – the system partition was mounted read-only, it said, a situation which I did not attempt to alter.
Instead I tried a Wipe > Factory reset (data, cache, Dalvik cache). This appeared to succeed, but it didn’t solve my bootloop problem.
## Partial firmware flash
Finally I untar’d the firmware (*.tar.md5) files, which produced numerous .img and .bin files, a .pit file, and a few other bits and pieces, and prepared to flash the new firmware, as described above (”short version“).
At this point I faced a puzzling conflict of authorities:
modest_mandroid’s Definitive Guide to Bricking: Avoid flashing bootloader components [BL] if your device has (a) working bootloader(s). If something goes wrong while flashing the bootloader, you’ll end up with a hard brick. [3]
topjohnwu: “Never just flash only AP, or else Odin can shrink your /data filesystem. Flash full AP + BL + CP + HOME_CSC when upgrading.” [2]
Unwilling to end up like Buridan’s ass, I had to choose one of the alternatives. You already know the end of the story: I went with modest_mandroid, so a partial flash, followed by the RMM_bypass and no-verity-opt-encrypt, and then found that Android 10 would boot, but also that the device was then stuck in a long bootloop.
Android 10 seems to work ok. I went through the setup wizard. I’m not sure where to look from within Android to examine /data; I presume that’s not identical with Internal Storage > Android > Data. Which is accessible from within Android via the Samsung file manager, and seems to be quite mounted when accessed in that way.
The only troubleshooting step I’ve tried is to reboot into TWRP again and try both a factory reset and an Advanced wipe on ’data’ only. That’s when I noticed the error message quoted above.
The only other thing I’ve noticed is that Android now seems to operate in an inconsistent way. Sometimes when it boots up, it seems to work fine. At other times swiping at the lock screen will clear the time and date and the phone/camera icons but fail to unlock the screen. Sometimes the power off icon seems unresponsive. I never had either of these issues before. But perhaps they’re unrelated to the bootloop.
## Questions
I’d be interested in hearing people’s responses to any of these:
What are you actually doing when you tap Uninstall > Restore images in Magisk Manager? Could this have led to the initial, short bootloop I experienced?
Is the failure to mount /data likely to be a result of the Magisk Manager Uninstall or of the partial firmware flash, or of something else?
Is it likely to be related to the long bootloop?
What does repartitioning with heimdall do?
What should I do now? Full flash (AP + BL + CP + HOME_CSC)? Or just AP + CP + CSC? Repartition with heimdall? Something else?
## Sources
[1] https://www.droidwin.com/install-ota-rooted-android/
[2] https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
[3] https://forum.xda-developers.com/t/definitive-guide-to-bricking.1049294/

In case this is of interest to anyone, I've since flashed BL + AP + CP + HOME_CSC with Odin, which appears to have resolved the issue.