Related
Hello there, please help me
My A520F flashed with Resurrection Remix (Oreo) while I was using Nougat Stock ROM, then my IMEI was gone. So I flashed it again with RR (Nougat) and I could use Wifi but simcard didnt detected. I flashed it again with Stock Rom, Hades Rom and still no IMEI.
I didnt know about RMM state and KNOX before (because I used Lollipop and Marshmellow, not Samsung phone before) , so I flashed it over and over again, and then I was stucked. Root access was gone, efs corrupted, couldnt get into homescreen.
After tried any stock firmwre and method that i found, I could bring my A520F back to home screen with A520FXXU7CRHA XID and/or A520FXXU7ARJ1 (Combination Firmware), 'cant mount /efs' problem was gone but still NULL IMEI.
so now, this is my A520F condition :
1. IMEI (1,2,SV), Baseband ----- NULL (can't connect to internet or SIM card)
2. FRP lock : OFF, RMM state : Prenormal, KNOX void : 1.
3. I cant find OEM lock status in Download Mode screen, and I dont find it in developer option because my A520F barely flashed. I can't do the 'Date and Time' trick or waiting 168 hr for opening OEM unlock menu because my NULL IMEI and Baseband, NO Connection.
4. The only firmware that successfully made my A520F booted to home screen were A520FXXU7CRHA XID and A520FXXU7ARJ1 (Combination Firmware).
5. There was an error in recovery mode, which is said :
E: [libfs_mgr] Blob verification failed : 255
dm-verity verification failed...
E: [libfs_mgr] Error creating device mapping. Device or resource busy
[omc-app-link] fail to mount /system as rw
Other firmware installed resulting on error/no command bluescreen and I couldn't enter the home screen. I can't root it with OneClickRoot neither Kingroot.
I can't install Custom Recovery or Root because RMM state and OEM Locked. I've tried 'fastboot boot recovery.img' in adb command but no result, couldn't use fastboot command.
So.... what should I do? at least the first step for now to solve it....
dinoonino said:
Hello there, please help me
My A520F flashed with Resurrection Remix (Oreo) while I was using Nougat Stock ROM, then my IMEI was gone. So I flashed it again with RR (Nougat) and I could use Wifi but simcard didnt detected. I flashed it again with Stock Rom, Hades Rom and still no IMEI.
I didnt know about RMM state and KNOX before (because I used Lollipop and Marshmellow, not Samsung phone before) , so I flashed it over and over again, and then I was stucked. Root access was gone, efs corrupted, couldnt get into homescreen.
After tried any stock firmwre and method that i found, I could bring my A520F back to home screen with A520FXXU7CRHA XID and/or A520FXXU7ARJ1 (Combination Firmware), 'cant mount /efs' problem was gone but still NULL IMEI.
so now, this is my A520F condition :
1. IMEI (1,2,SV), Baseband ----- NULL (can't connect to internet or SIM card)
2. FRP lock : OFF, RMM state : Prenormal, KNOX void : 1.
3. I cant find OEM lock status in Download Mode screen, and I dont find it in developer option because my A520F barely flashed. I can't do the 'Date and Time' trick or waiting 168 hr for opening OEM unlock menu because my NULL IMEI and Baseband, NO Connection.
4. The only firmware that successfully made my A520F booted to home screen were A520FXXU7CRHA XID and A520FXXU7ARJ1 (Combination Firmware).
5. There was an error in recovery mode, which is said :
E: [libfs_mgr] Blob verification failed : 255
dm-verity verification failed...
E: [libfs_mgr] Error creating device mapping. Device or resource busy
[omc-app-link] fail to mount /system as rw
Other firmware installed resulting on error/no command bluescreen and I couldn't enter the home screen. I can't root it with OneClickRoot neither Kingroot.
I can't install Custom Recovery or Root because RMM state and OEM Locked. I've tried 'fastboot boot recovery.img' in adb command but no result, couldn't use fastboot command.
So.... what should I do? at least the first step for now to solve it....
Click to expand...
Click to collapse
1 - Pull SIMs. Developer Mode enabled. Ensure 'Auto Update System' is disabled.
2 - Changed date to 4 weeks ago (turn off 'Automatic Date and Time')
3 - Check Software Updates (Check updates manually). Ensure 'Download Updates Automatically ' is disabled
4 - Reboot. Check for OEM switch in Developer Options
5 - Check date again (it's likely that the date will be current date, but if it is, just set it back to 3 days before last date change)
6 - Check OEM Unlock toggle is present. If not, go back and forth between the general settings tab and developer options and if needed use "close all" from recents and reopen settings again.
7 - If not working, undo all the above. Restart and try again.
8 - If it does work...celebrate - you can flash custom binaries and custom ROMs
9 - Get TWRP flashed through Odin
moozer said:
1 - Pull SIMs. Developer Mode enabled. Ensure 'Auto Update System' is disabled.
2 - Changed date to 4 weeks ago (turn off 'Automatic Date and Time')
3 - Check Software Updates (Check updates manually). Ensure 'Download Updates Automatically ' is disabled
4 - Reboot. Check for OEM switch in Developer Options
5 - Check date again (it's likely that the date will be current date, but if it is, just set it back to 3 days before last date change)
6 - Check OEM Unlock toggle is present. If not, go back and forth between the general settings tab and developer options and if needed use "close all" from recents and reopen settings again.
7 - If not working, undo all the above. Restart and try again.
8 - If it does work...celebrate - you can flash custom binaries and custom ROMs
9 - Get TWRP flashed through Odin
Click to expand...
Click to collapse
I really appreciate your idea sir, but the problem is i dont have any connection to network (simcard or wifi, because of the null imei), so the Check Software Updates is unusable.
And I can't flash TWRP because of OEM locked and RMM state prenormal
chimera tool bro
i can help you but not free sorry for saying that
Odin
Try Odin or Samsung Flash Tools! Its always helpful for me if that doesnt work try flashing twrp then a rom and changing the IMEI with root for root you can install magisk
---------- Post added at 10:32 PM ---------- Previous post was at 10:31 PM ----------
Wifi connectivity is might be because of the different files you flashes are not for the correct device it might be for A5 but different country
dinoonino said:
Hello there, please help me
My A520F flashed with Resurrection Remix (Oreo) while I was using Nougat Stock ROM, then my IMEI was gone. So I flashed it again with RR (Nougat) and I could use Wifi but simcard didnt detected. I flashed it again with Stock Rom, Hades Rom and still no IMEI.
I didnt know about RMM state and KNOX before (because I used Lollipop and Marshmellow, not Samsung phone before) , so I flashed it over and over again, and then I was stucked. Root access was gone, efs corrupted, couldnt get into homescreen.
After tried any stock firmwre and method that i found, I could bring my A520F back to home screen with A520FXXU7CRHA XID and/or A520FXXU7ARJ1 (Combination Firmware), 'cant mount /efs' problem was gone but still NULL IMEI.
so now, this is my A520F condition :
1. IMEI (1,2,SV), Baseband ----- NULL (can't connect to internet or SIM card)
2. FRP lock : OFF, RMM state : Prenormal, KNOX void : 1.
3. I cant find OEM lock status in Download Mode screen, and I dont find it in developer option because my A520F barely flashed. I can't do the 'Date and Time' trick or waiting 168 hr for opening OEM unlock menu because my NULL IMEI and Baseband, NO Connection.
4. The only firmware that successfully made my A520F booted to home screen were A520FXXU7CRHA XID and A520FXXU7ARJ1 (Combination Firmware).
5. There was an error in recovery mode, which is said :
E: [libfs_mgr] Blob verification failed : 255
dm-verity verification failed...
E: [libfs_mgr] Error creating device mapping. Device or resource busy
[omc-app-link] fail to mount /system as rw
Other firmware installed resulting on error/no command bluescreen and I couldn't enter the home screen. I can't root it with OneClickRoot neither Kingroot.
I can't install Custom Recovery or Root because RMM state and OEM Locked. I've tried 'fastboot boot recovery.img' in adb command but no result, couldn't use fastboot command.
So.... what should I do? at least the first step for now to solve it....
Click to expand...
Click to collapse
Combination Firmware is used to reinsert IMEI Manually not to fix 'cant mount /efs' problem' !
Try reflashing latest stock rom using modded odin (do google search)
How to Flash TWRP & Root Samsung Galaxy A10 series (Unlocked Exynos Only, A10s (A107F/M) not supported)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!).
How to get OEM Unlock option back?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.2. setup the phone by skipping the wizard.
B. Disabling Android Verified Boot
1. Reboot to DOWNLOAD mode.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
C. Flashing TWRP/Magisk
link
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Thanks and credit
For more details read Installation guide by @topjohnwu from Here.
All credit and thanks go to @topjohnwu for magisk & guide.
@dr.ketan for this guide from Here
@jesec for rooting guide Here
@ianmacd for multidisabler from here
Me
reserved.
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
dani3ltony said:
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
Click to expand...
Click to collapse
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
for step 6, can we transfer the file via SD card?
afaneh92 said:
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
Click to expand...
Click to collapse
Hi
I triple did it, but no luck
s_ryan said:
for step 6, can we transfer the file via SD card?
Click to expand...
Click to collapse
Sure.
dani3ltony said:
Hi
I triple did it, but no luck
Click to expand...
Click to collapse
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
afaneh92 said:
Sure.
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
Click to expand...
Click to collapse
s_ryan said:
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
Click to expand...
Click to collapse
yes
will try to make patched tar for all bootloaders when I got some free time.
Guide updated with more details
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
afaneh92 said:
Guide updated with more details
Click to expand...
Click to collapse
s_ryan said:
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
Click to expand...
Click to collapse
My bad I didnt test this, the BL file contain vbmeta.img and need to be patched. Will try to find better solution.
You can flash stock BL file only then reboot again to bootloader and flash the rest files.
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
s_ryan said:
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
Click to expand...
Click to collapse
Can you replace vbmeta.img from patched AP with BL using 7zip.
remove md5 extension from BL file.
Guide updated and added flash TWRP instructions
afaneh92 said:
2.Download A10_multidisabler-*-1.41.zip from here and copy to Ext Storage (Because once you flash TWRP, Int storage will not be readable)
Click to expand...
Click to collapse
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
ianmacd said:
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
Click to expand...
Click to collapse
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
afaneh92 said:
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
Click to expand...
Click to collapse
Thanks. In your case, it's easier now if you just verify that the script I attached is working, since I've already integrated the changes you made in your clone.
Anyone who wants multidisabler support for a new device, however, can either send me a pull request against the latest code, or run the following script on a live, rooted device:
Code:
#!/bin/sh
getprop ro.boot.bootloader
echo --
ls -l /vendor/etc/init/pa_daemon*.rc /vendor/etc/fstab.exynos*
echo --
cat /vendor/etc/fstab.exynos*
echo --
su -c cat /init.rc
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
s_ryan said:
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
Click to expand...
Click to collapse
Try using this vbmeta.img (inside the tar file). It worked for me on the A20 with similar error. This file normally seems to be a checksum checker and if it doesn't match what the phone wants to see it gives you that error. But this file was modified to essentially be blank so there is nothing to give the phone an error.
My Note 10+ shut down earlier today and has been stuck on a blue downloading screen but it hasn't changed and won't boot into any other screens to give me options. I've read about others having similar problems on other Samsung devices after flashing but as far as I know I did nothing to trigger it and I am not knowledgeable in sideloading so I don't really know where to start on fixing the issue.
The screen reads:
partition boot
Reason boot: Hash of data does not match digest in descriptor.[2nd] (3)
Calculated Hash of (boot) : D45EF024EE, (VMETA) : 594C218D84
SAMSUNG boot, N975USQS4CTF3, 32618795R
VBMETA N975USQS4CTF3, 32618795R
lux.aestiva said:
My Note 10+ shut down earlier today and has been stuck on a blue downloading screen but it hasn't changed and won't boot into any other screens to give me options. I've read about others having similar problems on other Samsung devices after flashing but as far as I know I did nothing to trigger it and I am not knowledgeable in sideloading so I don't really know where to start on fixing the issue.
The screen reads:
partition boot
Reason boot: Hash of data does not match digest in descriptor.[2nd] (3)
Calculated Hash of (boot) : D45EF024EE, (VMETA) : 594C218D84
SAMSUNG boot, N975USQS4CTF3, 32618795R
VBMETA N975USQS4CTF3, 32618795R
Click to expand...
Click to collapse
It seems your device has a corrupted firmware. This could have been while trying to update and getting a bad download with some data absent.
Either ways, you have to find the latest firmware for your model, download and unzip it, and then flash it properly with Odin 3.14, and you will be fine
Best of luck
Hello.
I bought a refurbished a3y17lte and expect it will run /e/ in GSI flavor (no official nor unofficial build yet).
- OEM unlock enabled > FRP LOCK: OFF in download mode,
- manual updated to latest 'Orange Télécom' version from device itself,
- then I flashed latest stock ROM with Heimdall (Debian Buster),
-
Code:
a3y17lte:/ $ getprop ro.treble.enabled
false
so I posted > there <.
I've got any more 'n00b' questions...
While unzipping stock image, Xarchiver just needs
Code:
~# apt install lz4
Then, in CSC folder I've got an A3Y17LTE_EUR_OPEN.pit file. May I flash it too ? Stock partitioning shows:
Code:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 2 (MMC)
Identifier: 70
Attributes: 5 (Read/Write)
Update Attributes: 1 (FOTA)
Partition Block Size/Offset: 34
Partition Block Count: 16
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename: -
FOTA Filename:
======I tried to flash TWRP and install LOS 16.0; 3.3.1 worked with difficulty (needs to choose 'Don't install' twrp as sytem app), 3.3.0 works, 3.4.0 return 'ERROR 7', so I went back to stock (heimdall flash). May I prefer OrangeFox recovery ?
Expecting this Exynos 7870 will run GSI, may I install 'Repartition' script or try H-Vendor (both by @Astrako ) ? I'm not sure to understand well how to use. What are the proper steps to avoid brick ?
Thanks a lot.
P.S.: I'm reading this (old) thread...
P.S.2: and this other one. I will become fan of @Astrako
Hello.
Well, well, well, I don't want 'another brick'... so fast replies on telegram Pruh 7870 don't match with my poor knowledge. I'm coming from Moto, easy to use with twrp and adb/fastboot...
My pit contains CARRIER instead of VENDOR (certainly why Shelter points a 'custom ROM'), so I probably need to flash europe_open.pit from stock ROM first. Then, I'm not sure what exactly do:
- flash custom recovery (twrp, orangefox, skyhawk?) first,
- universal-repartitioner_7870 (or older?),
- treble,
- a a_only gsi (e-pie-gsi),
- gsi_patch.
I will wait for advice and read again and again @starbright_ (#58) to understand how to proceed...
Note I want to try e-pie first (full build) then Q (light custom build).
Thanks.
P.S.: found last twrp custom 3.4.0-0-a3y17lte, thanks.
trefix said:
Hello.
Well, well, well, I don't want 'another brick'... so fast replies on telegram Pruh 7870 don't match with my poor knowledge. I'm coming from Moto, easy to use with twrp and adb/fastboot...
My pit contains CARRIER instead of VENDOR (certainly why Shelter points a 'custom ROM'), so I probably need to flash europe_open.pit from stock ROM first. Then, I'm not sure what exactly do:
- flash custom recovery (twrp, orangefox, skyhawk?) first,
- universal-repartitioner_7870 (or older?),
- treble,
- a a_only gsi (e-pie-gsi),
- gsi_patch.
I will wait for advice and read again and again @starbright_ (#58) to understand how to proceed...
Note I want to try e-pie first (full build) then Q (light custom build).
Thanks.
P.S.: found last twrp custom 3.4.0-0-a3y17lte, thanks.
Click to expand...
Click to collapse
What is a e-pie?
Custom Recovery (I thing which one is not important) is first. But isn't order explained in my post? All custom ROMs have some deficits. I try to modify a stock now, but I ma just facing some problems with location... (look for the deploat thread if you like). So frustrating....
Thanks.
Sorry, e-pie is /e/ OS based on LOS-Pie. No build for a3y17lte except a GSI one.
Your post (linked above) is fine, but I'm not sure about some details, as 'install just system' (about flashing GSI ROM)...
May I follow straight or adapt with new tools (H-Vendor, universal_repartitioner)? I don't already see what's happen at each step.
trefix said:
Thanks.
Sorry, e-pie is /e/ OS based on LOS-Pie. No build for a3y17lte except a GSI one.
Your post (linked above) is fine, but I'm not sure about some details, as 'install just system' (about flashing GSI ROM)...
May I follow straight or adapt with new tools (H-Vendor, universal_repartitioner)? I don't already see what's happen at each step.
Click to expand...
Click to collapse
Repartition is needed in both cases. Treble is for GSI Pie (A only) and H-ROM for A/B Q. Is this answering you question?
Hello.
Yes, thanks > two different combo so I need to choose first Pie or Q flavor. And clean flash from Pie to Q....
I will try, probably tomorrow. Thanks again.
Hello.
First of all, after 'Custom rom' message from Shelter, it seems I need to flash eur_open.pit (entries 24 to 27 are slightly different) to complete 'stock' flash. I have the right a3y17lte_eur_open.pit from Samsung stock rom, but didn't know how to flash safely the pit. I already extracted and saved on PC the 'factory' (Orange Telecom) pit with Heimdall...
I found on web, to flash the pit:
Code:
heimdall flash --repartition -- --pit my-samsung-file.pit
- Can I flash lonely, boot in download mode (buttons) then reboot system?
- May I add a new flash of all files extracted from Samsung's stock ROM (already flashed)?.
Thanks in advance.
.
P.S.: don't know where adv-env.img has to be flashed...
Hi.
Code:
heimdall flash --repartition --PIT A3Y17LTE_EUR_OPEN.pit --no-reboot
Code:
Uploading PIT
ERROR: Failed to receive PIT file part response!
ERROR: PIT upload failed!
Hello.
Back to 'seller' ROM (fr. Orange telecom) but still 'PIT upload failed' while flashing stock standard ROM and nor more buttons-mode recovery acces, with 'No command' response.
TWRP (unofficial from Pruh 7870) was running buggy, too...
'Orange' has a A3Y17LTE_EUR_OPEN_HIDDEN200M.pit (and ROM has a lot of bloatwares).
PS: same while launching command as root, with 'Can't open ---.pit file'
Édith used a w$ PC (with Odin 3.14.4) and then device now runs stock 'standard' ROM with repartition OK I will begin to flash treble...
Hello.
Well, trying 'pie' method, I've always have an issue during process: one or other partition falls 'unmountable', despite a reboot in Recovery after each successful flash.
- I'd first flash Disable_DM-verity_ForceEncrypt_03.04.2020.zip with twrp-3.3.1-0 (didn't work with twrp-3.4.0-0-astrako),
- when 'repartitioner' works (with /vendor seen 'mountable' in Advanced > Mount), treble's installation ends with " unable to mount '/vendor' ",
- installing only System (choose rom.img > 3 checkboxes Boot / Recovery / System) ends in a bootloop,
- flashing gsi-patch doesn't solve and ends in bootloop too...
Strange thing, despite a full wipe and format data, date/time remain after flashing stock ROM (with *.pit) and twrp-3.3.1-0 sometimes comes back by itself, replacing 3.4.0-0-astrako.
Now I presume this device (version needing to disable DM-verity) asks for an other flash sequence. Perhaps something like:
disable_DM > Repartitioner > GSI-patch > Treble > ROM.
???
Advises are welcome.
P.S.: Treble always return " failed to mount '/vendor' ", all tests went to bootloop.
PS2: two consecutive 'Repartition' whit reboot in Recovery, first 'failed... vendor', second OK but recovery 3.4.0-0 self downgrade to 3.3.1-0
PS3: twrp-3.4.0-0-astrako doesn't show re-partition (no more /vendor, from Advanced > Mount), 3.3.1-0 does I will try with another recovery, because it seems something isn't stable...
If you still need help with this, find me in Telegram @martinvalentine
Hi everybody,
I'm stuck in a pretty damn mess here. I have an Galaxy S20+ G985F device which is stuck in Download Mode with no ROM installed, a locked bootloader, and a changed recovery and vbmeta (one that came with a working TWRP image) image flashed. :/
Is thee any way to get out of this situation of which I don't know how exactly the phone got there? Seems like a mistakenly locked boot loader by long pressing the Vol Up button once in the Booloader Lock/Unlock menu.
When trying to flash with heimall the phone says, ie.:
Custom Binary (VBMETA) Blocked By OEM Lock
Any chance on recovering the device? There should actually no ROM be installed at the moment. Cannot boot anything, the device always goes into Download mode only showing an entry for "Vol Down + Side Key for 7 seconds: Cancel (restart phone)" which results in the device going to the screen again...
Flashing with "odin4" on Linux says:
odin4 -b BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5 -a AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5 -c CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5 -s CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
Check file : CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
/dev/bus/usb/001/054
/dev/bus/usb/001/054
Setup Connection
Set Partition
Receive PIT Info
success getpit
Upload Binaries
Binary arrange fail. Binary is invalid
Fail uploadBinaries
Kind regards and thanks for any help,
Marc
try with samsung smart switch with emergency software recovery
kosique said:
Hi everybody,
I'm stuck in a pretty damn mess here. I have an Galaxy S20+ G985F device which is stuck in Download Mode with no ROM installed, a locked bootloader, and a changed recovery and vbmeta (one that came with a working TWRP image) image flashed. :/
Is thee any way to get out of this situation of which I don't know how exactly the phone got there? Seems like a mistakenly locked boot loader by long pressing the Vol Up button once in the Booloader Lock/Unlock menu.
When trying to flash with heimall the phone says, ie.:
Custom Binary (VBMETA) Blocked By OEM Lock
Any chance on recovering the device? There should actually no ROM be installed at the moment. Cannot boot anything, the device always goes into Download mode only showing an entry for "Vol Down + Side Key for 7 seconds: Cancel (restart phone)" which results in the device going to the screen again...
Flashing with "odin4" on Linux says:
odin4 -b BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5 -a AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5 -c CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5 -s CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
Check file : CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
/dev/bus/usb/001/054
/dev/bus/usb/001/054
Setup Connection
Set Partition
Receive PIT Info
success getpit
Upload Binaries
Binary arrange fail. Binary is invalid
Fail uploadBinaries
Kind regards and thanks for any help,
Marc
Click to expand...
Click to collapse
And also you cannot turn off your phone? )
Prepare a recovery tar file with vbmeta and recovery in it. Flash with odin and reboot. Then disable encription.
Then redo the initial process of flashing tar file with or without the rest of the rom files.
If ur alao flashing rom files put your recovery tar file to others section in odin.