Related
CURRENT UPDATE 07/August:
able to get into Custom Recovery & Installed 5.1 Stock Image GPE on my XT1032 Moto G
booted using custom recoveries : a)TWRP 2.8.7.0 b)Philz recovery ( philz_touch_6.58.7-falcon )
NEXT STEP : I wanted to Install PA OR REsurrection Latest Custom Build ROM for 5.1 , but getting following error.
Error Messages :-
detetected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching system image unconditionally
blkdiscard failed : Invalid argument
Error executing updater binary in Zip "/sdcard/resurrection-falcon.zip "
Error flashing zips , Installation aborted.
Let me know if i am missing anything.
Thanks for your support.
............................................................................................................................................................................................................................................................................
Hi All,
I need your help to enter into recovery. Looks i have messed up something.
Last Version :- Lollipop 5.1 Optimized
Model :- XT1032 GPE
I was getting below error while flashing any 5.1 Custom ROM
patching system image unconditionally
blkdiscard failed invalid argument
error executing updater binary in zip
Hence, i flashed below file.
http://forum.xda-developers.com/moto-g/general/fix-android-lollipop-ota-gpe-stuck-t2970842
I am stuck at bootloader screen & can't go to recovery.
I have tried flashing CWM recovery & TWRP recovery latest version.
Thanks for your support in advance.
I've attached the GPE 5.1 Partition Table (gpt.bin) - flash via fastboot.
EDIT: Regarding "error executing updater binary in zip" - Read the 'Bugs' section post #3 in the Optimized ROMs thread.
Another Issue
lost101 said:
I've attached the GPE 5.1 Partition Table (gpt.bin) - flash via fastboot.
EDIT: Regarding "error executing updater binary in zip" - Read the 'Bugs' section post #3 in the Optimized ROMs thread.
Click to expand...
Click to collapse
@lost101
Thanks for your support.
I was successfully able to get Lollipop 5.1 , but now i am facing another issue.
When i try to install Custom ROM ( installation of latest file " Resurrection-Remix-LP-v5.5.3-20150803-falcon " ) via TWRP custom recovery , i got following error :-
blkdiscard failed : Invalid argument
Error while doing installation from SDcard , Installation aborted.
Model :- XT1032 GPE
Current Setup :- Android 5.1 Lollipop Optimized
I did factory reset while going ahead for installation.
I think the reason might be different partition type ( Moto G GPE= ext4 type , above ROM = f2fs type )
Could you suggest how i am able to install above ROM ?
Thanks for your support in advance.
@as2014 - It probably is a requirement of most custom ROMs to have a f2fs-formatted /data partition. This can be done in TWRP :
Wipe > Advanced Wipe > Select 'Data' > FS OPTIONS > CHANGE FS > F2FS
Need Help
@lost101
Thanks again for your help.
Now , i have changed file system to f2fs via TWRP , but following problems are there :-
1. After rebooting , Phone is stuck up in bootloop.
2. I am not able to access custom recovery via Bootloader ( Bootloader -> Recovery ).
Model :- XT1032 GPE
Android system :- 5.1 Optimized Version.
Thanks again.
Try: fastboot erase userdata - you should now be able to enter TWRP. Also make sure you are using the latest version of TWRP from here:
http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Thanks
@lost101 ...This helped & i was able to access TWRP custom recovery.
However when i tried to install Custom ROM ( Resurrection OR PA ), i got following error :-
detetected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching system image unconditionally
blkdiscard failed : Invalid argument
Error executing updater binary in Zip "/sdcard/resurrection-falcon.zip "
Error while doing installation from SDcard , Installation aborted
Now , i am able to run successfully Android 5.1 Optimized on my Moto G.
But , i certainly wanted to run custom ROM's for few features.
Any suggestion , how to go ahead ?
Thanks for your support again.
@as2014 - Are you using the version of TWRP I suggested? If so, are you doing a factory reset in TWRP before flashing?
@lost101 ......
Earlier , i was 2.8.5.0 TWRP , but now i have tried with twrp-2.8.7.0.-falcon_STOCK.img as custom recovery.
here is complete setup :-
1. Android OS :- 5.1 Optimized & device :- XT1032 GPE , Recovery :- twrp-2.8.7.0
2. Reboot into recovery
3. Change " Data ' Partition to F2FS format via TWRP ( Wipe > Advanced Wipe > Select 'Data' > FS OPTIONS > CHANGE FS > F2FS )
4. Factory Reset
5. Install Custom ROM " pa_falcon-5.1-20150704.zip " OR " Resurrection-Remix-LP-v5.5.3-20150803-falcon.zip "
Error Messages :-
detetected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching system image unconditionally
blkdiscard failed : Invalid argument
Error executing updater binary in Zip "/sdcard/resurrection-falcon.zip "
Error flashing zips , Installation aborted.
Let me know if i am missing anything.
Thanks for your support.
@as2014 - There appears to be corruption somewhere. To simplify things, I suggest you return phone entirely to factory condition. Fastboot flash the GPE 5.1 Firmware Image:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
From that point other solutions can be explored if necessary.
as2014 said:
@lost101 ......
Earlier , i was 2.8.5.0 TWRP , but now i have tried with twrp-2.8.7.0.-falcon_STOCK.img as custom recovery.
here is complete setup :-
1. Android OS :- 5.1 Optimized & device :- XT1032 GPE , Recovery :- twrp-2.8.7.0
2. Reboot into recovery
3. Change " Data ' Partition to F2FS format via TWRP ( Wipe > Advanced Wipe > Select 'Data' > FS OPTIONS > CHANGE FS > F2FS )
4. Factory Reset
5. Install Custom ROM " pa_falcon-5.1-20150704.zip " OR " Resurrection-Remix-LP-v5.5.3-20150803-falcon.zip "
Error Messages :-
detetected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching system image unconditionally
blkdiscard failed : Invalid argument
Error executing updater binary in Zip "/sdcard/resurrection-falcon.zip "
Error flashing zips , Installation aborted.
Let me know if i am missing anything.
Thanks for your support.
Click to expand...
Click to collapse
Change the steps 3 and 4, do a factory reset first and then format data to f2fs
Sent from my XT1033 using Tapatalk 2
@pradeeppk........Changing the steps 3 & 4 didn't helped.
@lost101 .... Please find the further findings :-
1. I installed GPE_5.1_XT1032_LMY47M.M001_CFC.xml ( Android 5.1 ) via following command sequence :-
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
2. Afterwards , i installed TWRP custom recovery via Bootloader
mfastboot flash recovery twrp-2.8.7.0.-falcon_GPE.img
3. reboot to custom recovery
4. Root via UPDATE-SuperSU-v2.46.zip ...reboot to recovery again
5. Factory Reset
6. Change " Data ' Partition to F2FS format via TWRP ( Wipe > Advanced Wipe > Select 'Data' > FS OPTIONS > CHANGE FS > F2FS )
7. Try to install Resurrection-Remix-LP-v5.5.3-20150803-falcon.zip OR pa_falcon-5.1-20150704.zip. Again Same error :-
detetected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
patching system image unconditionally
blkdiscard failed : Invalid argument
Error executing updater binary in Zip "/sdcard/resurrection-falcon.zip "
Error flashing zips , Installation aborted.
Let me know if i can go ahead any further.
Thanks for your support.
@as2014 - Did the Stock Firmware boot without issue?
lost101 said:
@as2014 - Did the Stock Firmware boot without issue?
Click to expand...
Click to collapse
@lost101 .....Yes ....stock firmware ( GPE_5.1_XT1032_LMY47M.M001_CFC.xml ) booted without any issues.
It was downloaded from below Link :-
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
as2014 said:
@lost101 .....Yes ....stock firmware ( GPE_5.1_XT1032_LMY47M.M001_CFC.xml ) booted without any issues.
Click to expand...
Click to collapse
Try some other custom ROMs if you can - I wonder if it's something specific to the ROMs that are failing to flash.
@as2014 - Something that I suspect may have happened is where the /system partition has become read-only. That would explain why you can boot the GPE ROM but not flash any other. If you search XDA you will see it appears to occur fairly often.
Maybe try the following: http://forum.xda-developers.com/note-4-sprint/help/internal-memory-read-fix-apps-t2926040
@lost101 .....
I tried below commands via terminal emulator , but still same error :-
su
restorecon -v -R /data/media
Could you suggest me commands/steps , that i should try to check if /system is read only ?
Thanks for your support.
"This package is for A0001, this device is bacon." Wiped internal storage, cant flash
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
KuranKaname said:
If you can acces TWRP, just by connecting the OPO to your PC should give you acces to storage. I guess that you are trying to install H2OS, download the fixed version with the updater-script fixed. If it gives you this error with another rom, just download another custom rom and put in on the internal storage or flash the stock OS with fastboot
Click to expand...
Click to collapse
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
Instead of using adb push metod try to flash stock rom (https://forums.oneplus.net/threads/oxygenos-2-1-4-for-the-oneplus-one.425544/) and then flash the rom you want.
Good luck!
Note: You will loose twrp, so you have to flash it via fasboot [fastboot flash recovery (recovery name).img]
I'd suggest you to start over with a clean flash of COS13 fastboot factory image. Sounds like you are on a very old base.
Try to reboot TWRP and flash again. Or remove that check string from the updater-script.
download CM11 factory recover tool from my google drive @ https://drive.google.com/open?id=0ByfGPjP5zNYSTDZZcXZpLU44Q00 and install drivers and go to fastboot and plug in the phone and run recovery tool to push default factory image then install whatever CM version you want directly
No updater-script file that I can see
Can't find that file!
Anghirrim said:
Yep, inside the rom zip, there is a file called updater-script.
In this file, there is a line checking the phone name.
While most of the roms are using "bacon", H2OS original zip file uses "A0001" instead.
Can you try with any other rom?
Click to expand...
Click to collapse
use usb otg, success each time!
setup on ubuntu
Instructions for install on linux (test on ubuntu)
1- install adb :
Code:
$ sudo apt-get install android-tools-adb
2- install fastboot :
Code:
$ sudo apt-get install android-tools-fastboot
3- Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
4- test if the phone is detected with the cmd :
Code:
$ fastboot devices
5- unlock bootloader (/!\ it wipe the phone) :
Code:
$ sudo fastboot oem unlock
6- install TWRP :
- go to the path where is the img
Code:
$ cd path/to/twrp/folder/
- rename the image to twrp.img
Code:
$ mv old_name.img twrp.img
- flash the recovery
Code:
$ sudo fastboot flash recovery twrp.img
/!\ Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually turn it off by pressing and holding power button until it switches off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step. /!\
7- install custom/official ROM with TWRP :
- Wipe > Swipe to Factory Reset
- Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
- Install GApps using same process as ROM, then reboot. (optionnal: the official OnePlus ROM come with GApps pre-installed)
Possible errors with official ROM :
"This package is for device: A0001; this device is bacon" or "This package is for device: OnePlus; this device is A0001" or other similar
==> go into the ROM zip file, in "/META-INF/com/google/android/" there is an "updater-script" file. Open it, locate the expression ' getprop("ro.build.product") == "A0001" ' and replace the "A0001" by the device name you have. Replace the file in the archive. Note : after that, you can't verify the official MD5 !
- example : "This package is for device: A0001; this device is bacon", the ' getprop("ro.build.product") == "A0001" ' become getprop("ro.build.product") == "bacon" '
Sources :
https://forums.oneplus.net/threads/...oader-install-custom-recovery-and-root.64487/
https://forum.xda-developers.com/oneplus-one/help/package-a0001-device-bacon-wiped-t3457766
Oneplus one Oxygen Installation error using TWRP
niranjanbhat said:
Like an idiot, I accidentally wiped internal storage while trying to flash a new ROM, so all my data ( which I dont care about ) and my backup images got deleted. I still have access to TWRP so I thought it wasnt that bad and went ahead installing ROMS as I usually would.
I transferred the zip files from PC to the phone via adb push method and tried to flash
However, I an unable to install any ROM as it gives me an error every time. This is what the error message reads:
Skipping MD5 check : no MD5 file found
This package is for device: A0001; this device is bacon
E: Error executing updater binary in zip ' /sdcard/cm...(name of the rom here).zip '
Error flashing zip ' /sdcard/(nameofrom).zip '
I did quite a bit of research and read on one of the official OnePlus that all the ROMs are signed for the device A0001 but the device itself reads itself as bacon, which is its codename. Since "bacon" != "A0001" the zip installation fails.
Am I stuck with an expensive paperweight here? Please help.
TLDR: Wiped internal storage, No OS, flashing throws up error every time
Click to expand...
Click to collapse
check this post
wirelessindeed.blogspot.com/2017/07/oxygen-installation-error-on-oneplus.html
Update TWRP Recovery
I know this is an old post, so this is here in case anyone finds it in the future and requires help...
My mate asked me to upgrade his OnePlus (original, codename Bacon) and I received this error when upgrading from LineageOS 14.1 to 15.1.
To resolve, its extremely easy - simply upgrade the TWRP recovery. My mate originally had TWRP 3.1.1.0 installed, but the latest weekly LineageOS 15.1 required v3.2.3.0 installed which resolved the error message "This package is for device: bacon, a1001. this device is ."
Either Vol+ and Power to enter bootloader, or from command line:
adb reboot bootloader (with Android USB debugging turned on. You can test for connection using command "adb devices" and if successful it should show your phone's serial number). You will need to trust the computer's connection on your phone. To get to Android USB Debugging, you need to go Settings -> Developer menu options, and if you can't see that: Settings -> About Phone and tap "Build" 7 times for developer mode to appear.
Once phone goes into bootloader mode, type:
fastboot flash recovery "path:\twrp-x.x.x.x-bacon.img" (obviously path is the directory that the recovery is stored in, and x.x.x.x will be replaced with the version you've just downloaded. At time of writing, v3.2.3.0 is the latest. You can always use "fastboot devices" if you used Vol+ and Power to enter bootloader to ensure you have a valid connection, in USB debugging mode on your phone and correct Android adb drivers installed in Windows.
Wait until it's succeeded, and turn off phone. Now go into recovery and try again - and this time you should be good to go!!!
All the above implies your bootloader is unlocked. If you need to unlock your bootloader, there are plenty of instructions telling you how to do this - but HAVE A BACKUP as unlocking your bootloader will do a factory reset on your phone.
Hope this helps someone
......mmmmmm BACON!!!
hey guys I had deleted my operating system and currently having no operating system but I have twrp . I had tried so many time to install custom roms
1. Letv_1s_x500_Ghost45_v7 but it is in rar format so don't know how to install.
2. lineage-14.1-20170415-UNOFFICIAL-X3 but every time it shows "error executing updater binary in zip" I had wipe data many time but same error is coming.
i'm using letv 1s x509 can anyone help please
Use Sp Flash tool to Format or install the zip file using twrp.
[Problem solved] If anybody faces this kind of problem please notice it is not the problem of Nand-erase but DRK error and flashing with .pit file won't fix your problem. Just go to this discord group, https://discord.gg/Z4UZheJ [permanent] and ask for #Augustin. He will solve your problem 100%. He did for me. Full working network + rooted.
---------------------------------------------------------------------------------------------------
Hello, I was trying to update my s7 edge (SM-G935FD) with Oreo 8.0 from Nougat 7.0 with a custom firmware from sammobile.com.
The used file is: sammobile.com/firmwares/galaxy-s7-edge/SM-G935FD/BNG/download/G935FXXS3ERHD/236500/
But when flashing with Odin I accidentally selected "Nand Erase" option. After the operation completed my phone tried to boot up, showed installing updates, then tried to boot again and now permanently stuck on "SAMSUNG Galaxy S7 edge POWERED BY android".
Still, I can access "download mode" by using "Power + down + home" button and "android recovery" by using "Power + up + home" button.
While loading android recovery screen it shows, "Installing update..." then "Error" with an icon of android eyes crossed.
In my recovery menu, these lines are shown:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API : 3
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
I flashed with this same firmware to no avail. I have also tired "Wipe data / Factory reset" and "Wipe cache partition". Nothing worked.
Now, other people who have tired this firmware faced the same problem for #fail to open recovery_cause
But, in my case, as bold lines indicates, this is may be due to using "Nand Erase" in Odin.
I do have :
Nougat 7.0 firmware for my device [Please notice that its baseband is U2 - so I can't downgrade bootloader from S3 to U2 hence can't flash with Nougat]
.pit file for my device [not sure about this one - I actually need a valid pit file from the above firmware, others don't seem to work.]
I have tried Z3box / octopus / smart switch samsung software to recognize my device, but they always reply with "Card not found". My Windows treats my device as unrecognized in this situation.
Please help me fix this issue. I just have bought this phone - second hand.
-----------------------------------
Update - I tried to use stock recovery files to flash with TPRW stock recovery. After I did that It started the tprw recovery and I installled two files
1. twrp-3.1.0-0
2.SR3-superuser
It completed and when I selected to reboot my phone, it just won't turn on anymore. I guess it is due to my partition is all messed up. I forced it to start up using my charger cable and plugging it to charging. Using "Download mode" then I tried to uninstall this TPRW and flashed only "AP" with "G935FXXU2ERD5" with odin as I was unable to find any stock recovery for "G935FXXS3ERHD".
Now, I am stuck with U2 bootloader whereas I need S3 bootloader. My phone still doesn't turn on normally. I have to plug it in charging port / USB cable to pc, then it goes straight up to "Android Recovery" and Now shows this:
File-Based OTA
Supported API : 3
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
Successfully verified dmverity hash tree
E: Failed to clear BCB message: failed to find /misc partition
Please help me. I know I messed up, I shouldn't have used the TPRW recovery. Now I can't even flash with previous G935FXXS3ERHD or any U2 firmware. Please help me. I feel like crying.
hello
SM-G935F ODD multi CSC ( BNG INS INU NPL SLI SLK )
by default : INS
HERO2LTE_EUR_OPEN_HIDDEN45M.pit
https://drive.google.com/file/d/1E2zQvp0XriLVBAKT83mODWCSmgE8evLN/view?usp=sharing
regards
I have similar issues. For me working result was
Flash original firmware latest from updato
Format data to ext4 and flash no verify
push TGP rom to data
install TGP rom with: flash bootloader, flash modem, flash tgp kernel: checked in Aroma Installer
yakapa40 said:
hello
SM-G935F ODD multi CSC ( BNG INS INU NPL SLI SLK )
by default : INS
HERO2LTE_EUR_OPEN_HIDDEN45M.pit
drive.google.com/file/d/1E2zQvp0XriLVBAKT83mODWCSmgE8evLN/view?usp=sharing
regards
Click to expand...
Click to collapse
jaqjacek said:
I have similar issues. For me working result was
Flash original firmware latest from updato
Format data to ext4 and flash no verify
push TGP rom to data
install TGP rom with: flash bootloader, flash modem, flash tgp kernel: checked in Aroma Installer
Click to expand...
Click to collapse
Dear all,
I don't know how to say it, but a miracle just happened. My phone was stuck to "Android recovery" mode for half an hour. The charging cable was plugged in - in this time. Right before I am about to disconnect the cable in order to take it to repair shop, it started booting out of nowhere. :fingers-crossed:
Then I set up the device and the device installed applications by itself. God knows what happened but here is my system spec now :
Android version 8.0.0
Samsung Experience version 9.0
Baseband version G93FXXU3ERHC
Kernel version 3.18.91-13895453-QB19588583
Build number R16NW.G93FXXS3ERHD
The TPRW application is also installed.
I don't know what happened but it has managed to boot.
--------------------------------
The problem I faced is, It doesn't let me select any network carrier for my region instead it just says, "Failed to connect! Try again later."
Now I am afraid to even restart the device fearing if it gets stuck in the boot loop again. I am so scared I don't know if I will flash this device with any stock firmware anymore.
And the "Android recovery" option still shows "Installing updates" following with "Error" with android icons eye crossed out + shows previous error messages still the same.
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
File-Based OTA
Supported API : 3
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr] Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-permission-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
Thank you, everyone.
If you could just help me solve my problems I will be always grateful to you guys and this community.
@jaqjacek if you can point out a tutorial to me or just explain the steps elaborately that would be helpful.
@yakapa40 if you can help me how to use those files, please.
My device is now booted up but still showing errors in "Android recovery" option + the sim network doesn't work.
What version of Odin are you using to flash?
quasihellfish said:
What version of Odin are you using to flash?
Click to expand...
Click to collapse
Odin3 v3.12.7 in windows 10. Installed samsung driver both manually and via Smart Switch.
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
yakapa40 said:
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
with SM-G935FXXS3ERHD_G935FODD3ERI2 firmware only use ODIN V3.13.1 ( files are lz4 compressed ) or highter version
pit file :
open ODIN / pit / yes / copy/paste : HERO2LTE_EUR_OPEN_HIDDEN45M.pit
in option uncheck auto reboot
flash pit file
if it's ok : flash 4 files firmware ( don't flash HOME_CSC_FTM_G930FFTM2EREB_CL13637986_QB18191660_REV00_user_low_ship.tar.md5 ) with auto reboot checked
Click to expand...
Click to collapse
Ok, sir, I will try and let you know. One question though, is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
My android recovery says:
Android Recovery
samsung/hero2ltexx/hero2lte
8.0.0/R16NW/G935FXXU2ERD5
user/release-keys
use volume up/down and power.
is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
i don't know , flashing pit file will remove partitions and flashing firmware will re mount partitions ( but not Non Volatile memory )
yakapa40 said:
is there any possibility that my phone may be stuck in the boot loop again while doing this .pit flash?
i don't know , flashing pit file will remove partitions and flashing firmware will re mount partitions ( but not Non Volatile memory )
Click to expand...
Click to collapse
Dear sir,
I am still waiting for some kind of help. I haven't flashed my phone with .pit file cause I am too scared that my phone will get stuck in boot loop again. Please, somebody, help me. If I get stuck in the boot loop again, I don't think I can revert back to current position [Cause I don't know how my phone was fixed, it just fixed itself somehow.] and I can't take the stress. Please somebody who is an expert on this matter, please help me. I beg you.
I am still waiting for someone to reply to my post. I have not fixed my problem and honestly, I can't think I can until someone expert help me in this matter. Please, someone, help me.
ukero said:
I am still waiting for someone to reply to my post. I have not fixed my problem and honestly, I can't think I can until someone expert help me in this matter. Please, someone, help me.
Click to expand...
Click to collapse
I Fix that problem Yesterday on my phone. Download latest rom with proper country from https://updato.com/firmware-archive-select-model?q=sm-g930f&exact=1&r=&v=&rpp=15
Unzip it
take out latest PIT file from CSC file. I just use Total Comander and treat tar.md5 file like any other compress archive
Use odin 3.13.1 put BL to BL, CP to CP... Use CSC file not HOME_CSC and remember you will lose your data on phone.
PUT pit in pit panel.
Flash it with every option check but one. The Reboot Phone should be uncheck.
When Every thing will be good restart your phone with combination Vol- + HOME + power
Phone will run erasing , reboot and show "no command" if not and its boot normally you lucky.
if "no command"
-put phone into download mode
download latest twrp.tar.md5 and put in in AP section inside odin
flash it with every thing uncheck in odin no reboot, no erase nand
reboot your phone and go to recovery vol+ + HOME + power when phone start booting
if TWRP boots just plug phone back to computer download no-verify script zip put it on phone and flash it, or use adb sideload
wipe cache and factory reset
reboot phone
every thing should be ok from now
if phone after some time will have poor network connection or GSM singal will be gone thats is the problem that I don't have fix for now.
jaqjacek said:
I Fix that problem Yesterday on my phone. Download latest rom with proper country from https://updato.com/firmware-archive-select-model?q=sm-g930f&exact=1&r=&v=&rpp=15
Unzip it
take out latest PIT file from CSC file. I just use Total Comander and treat tar.md5 file like any other compress archive
Use odin 3.13.1 put BL to BL, CP to CP... Use CSC file not HOME_CSC and remember you will lose your data on phone.
PUT pit in pit panel.
Flash it with every option check but one. The Reboot Phone should be uncheck.
When Every thing will be good restart your phone with combination Vol- + HOME + power
Phone will run erasing , reboot and show "no command" if not and its boot normally you lucky.
if "no command"
-put phone into download mode
download latest twrp.tar.md5 and put in in AP section inside odin
flash it with every thing uncheck in odin no reboot, no erase nand
reboot your phone and go to recovery vol+ + HOME + power when phone start booting
if TWRP boots just plug phone back to computer download no-verify script zip put it on phone and flash it, or use adb sideload
wipe cache and factory reset
reboot phone
every thing should be ok from now
if phone after some time will have a poor network connection or GSM signal will be gone that's is the problem that I don't have fix for now.
Click to expand...
Click to collapse
Thank you for the very late reply. I have updated my post a long time ago and you will see following your method wouldn't fix my phone properly - the connection issue remained although the booting up was solved. You can't fix the DRK (Device root key) error in this process. You have to flash with a modified combination file to fix this error. It is only possible by the Samsung developers as the bootloader itself is in the Trusted App Sector.
I have mentioned in my edited post that Augustin in a PDA Group in Discord [The link is provided at the start] fixed my problem. As I followed his method, I realized no matter how many times I would've flashed my device with the stock Rom's .csc it wouldn't fix my problem. I initially thought that flashing with .pit file would fix my phone because I used Nand Erase - but I was wrong. It was a safety measure by Samsung to protect their device. You need a modified .csc file that Augustin gave me. I can give you all the files he gave me to use but I think it would be better if you contact him instead. The process is so complicated it took me 5 hours.
I flashed with the combination file he gave me, then flashed the stock rom's .csc separately. Then I tried to flash the whole ROM again. It worked but with no network. Then I installed TWRP recovery, edited some system file [I don't remember which one but he said to me that I needed refreshed new files], then formatted. Then did the whole process again. At some point, I remember I faced some problem with Bootloader exception [You will too because of the combination file but its ok], just follow this video when you need it cause he didn't know exactly how to fix this for the s7 edge but this video showed how.
https://www.youtube.com/watch?v=C9uSE4XbXvg
At last for many trials and errors my phone was fixed. I couldn't thank him enough bro.
I don't think anybody on the internet can fix this with custom combination lock like him. Trust me cause I searched a lot. They even kicked me from XDA Discord group when I posted this exact solution pointing out to the PDA group after asking to help me [when no one did]. I don't know what it is between them, but they kicked me.
You can have the files if you know what to do by yourself. Just give me a knock, I will give you the Google drive link to the files. Thanks anyway.
ukero said:
Thank you for the very late reply. I have updated my post a long time ago and you will see following your method wouldn't fix my phone properly - the connection issue remained although the booting up was solved. You can't fix the DRK (Device root key) error in this process. You have to flash with a modified combination file to fix this error. It is only possible by the Samsung developers as the bootloader itself is in the Trusted App Sector.
I have mentioned in my edited post that Augustin in a PDA Group in Discord [The link is provided at the start] fixed my problem. As I followed his method, I realized no matter how many times I would've flashed my device with the stock Rom's .csc it wouldn't fix my problem. I initially thought that flashing with .pit file would fix my phone because I used Nand Erase - but I was wrong. It was a safety measure by Samsung to protect their device. You need a modified .csc file that Augustin gave me. I can give you all the files he gave me to use but I think it would be better if you contact him instead. The process is so complicated it took me 5 hours.
I flashed with the combination file he gave me, then flashed the stock rom's .csc separately. Then I tried to flash the whole ROM again. It worked but with no network. Then I installed TWRP recovery, edited some system file [I don't remember which one but he said to me that I needed refreshed new files], then formatted. Then did the whole process again. At some point, I remember I faced some problem with Bootloader exception [You will too because of the combination file but its ok], just follow this video when you need it cause he didn't know exactly how to fix this for the s7 edge but this video showed how.
https: //w w w. youtube .com /watch?v= C9uSE4XbXvg
At last for many trials and errors my phone was fixed. I couldn't thank him enough bro.
I don't think anybody on the internet can fix this with custom combination lock like him. Trust me cause I searched a lot. They even kicked me from XDA Discord group when I posted this exact solution pointing out to the PDA group after asking to help me [when no one did]. I don't know what it is between them, but they kicked me.
You can have the files if you know what to do by yourself. Just give me a knock, I will give you the Google drive link to the files. Thanks anyway.
Click to expand...
Click to collapse
hey, im needing the file. i know how to do. please, help me. im with same issue, but with s7 flat SM G930F
Augustin is the best!
Hey there, I have a very similar problem with my S7 G930F. Could someone help me please? Thanks in advance.
(PS. The discord link is down, so I can't talk to Augustin)
After a lot of problems with my computer @ZeroXO helped me to solve the problem
Issue freeze and restarting
ZoOMBeE said:
Augustin is the best!
Click to expand...
Click to collapse
Can u tell me a way to contact him? the discord's link doesn't work anymore. I'm facing a freeze issue with my s7 edge. I mean It freezes when Im using it and also on TWRP so I can't install anything :c. I already flash stock firmware and it boots successfully , but in about 2 minutes it freezes and restart again. Also it happens in safe mode and recovery. Help me :c
Hi, I have a problem trying to install lineage os 16. The problem is when I flash the rom with twrp (no matter what version). The installation stops at 46% and I get the following message: "patching system image unconditionally ...
patching vendor image unconditionally ...
detected filesystem ext4 for / dev / block / bootdevice / by-name / system."
After this and after installing the google apps, I reboot but I am loading the rom and later the recovery is restarted.
I tried with abd sideload and copying the zip file to internal storage.
Could anyone help me and give me some advice? Thank you.
I have searched on internet to find a solution but I haven´t see anything