Related
Hello!
I have a problem with my moto g3, he gets stuck at fastboot screen at gives error "version downgraded for boot, failed to validate boot image" after an ota update.
I've tried with different factory ROMs and everyone of them says error "(bootloader) Preflash validation failed
FAILED (remote failure)"
What can I do? My phone won't work ever o there's a solution?, I've tried and I couldn't get it to flash anything.
I can't get it to claim warranty nor do I believe there's a specialized motorola service where I live.
Thanks in advance.
Psicovirus said:
Hello!
I have a problem with my moto g3, he gets stuck at fastboot screen at gives error "version downgraded for boot, failed to validate boot image" after an ota update.
I've tried with different factory ROMs and everyone of them says error "(bootloader) Preflash validation failed
FAILED (remote failure)"
What can I do? My phone won't work ever o there's a solution?, I've tried and I couldn't get it to flash anything.
I can't get it to claim warranty nor do I believe there's a specialized motorola service where I live.
Thanks in advance.
Click to expand...
Click to collapse
What did you do to it before this occurred? try to flash lollipop?
what model number, country, carrier; what was the last working rom you had on it.
Have you done this?
https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
KrisM22 said:
What did you do to it before this occurred? try to flash lollipop?
what model number, country, carrier; what was the last working rom you had on it.
Have you done this?
https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Click to expand...
Click to collapse
Thanks for answering friend.
Is an XT1540. US retail. Unlocked. It had 6.0 before the ota that i think ir was a security update because it was aprox. 300mb.
Yes, i tried that with several images (factory) it wont ley me flash anything, gives me the errors that i mentioned before when i tried to flash gpt, system an recovery, it only flash logo.bin, nhlos succesfully.
I've tried to flash the 6.0 image corresponding to my model(xt1540 RETUS 2GB).
It says in the fastboot "invalid PIV image" and un the cmd "invalid signed image" or something like that.
You think is solvable?
Thanks a lot.
what twrp have you flashed?
No one, bootloader's locked, therefore i couldn't flash either twrp nor custom roms.
I suppose it had factory recovery, but it i choose to go to the recovery, il'll loop and go to the fastboot screen. I can only acces to the fastboot and fastboot logs.
Hang on a few minutes I'm working on a new guide...
If you do, i guess ill have to buy some marble to stand a statue un you honor man, thanks.
plastic's fine.
Start at the beginning and alert me if there's any confusion so I can fix it. Thanks.
https://forum.xda-developers.com/2015-moto-g/general/guide-osprey-moto-g3-begin-how-to-t3599251
Friend, it's pretty clear. Le probleme est that i dont hace and unlocked bootloader, but un order to unlock it i hace to check the box un developer options and i cannot do that cuz im stuck un bootloader mode, is a vicious circle, do you get me?
Can you boot to stock recovery - same as with TWRP but you will get a luing down android - press vol-up and after a few secs you will be in stock recovery. Do a factory reset. Maybe then you can boot. If not I am out of ideas.
It wont ley me boot to recovery, i ve done several factory reset vía fastboot mode.
Thanks forma taking the time trying to help me, i appreciate that.
you're welcome!
Psicovirus said:
It wont ley me boot to recovery, i ve done several factory reset vía fastboot mode.
Thanks forma taking the time trying to help me, i appreciate that.
Click to expand...
Click to collapse
okay, thinking more on this - since you can do fastboot factory reset, can you do a fastboot flash recovery? - show me a pic of the commands and results when you try it. Grab squid's latest and see what happens. Or will it just block it because you're locked.
haven't had a chance to look fully at this. Most need recovery, but...
https://www.google.com/search?clien...8#channel=fs&q=fastboot+turn+on+usb+debugging
Hey, you came back!! Haha.
Well, trying to flash anything will give me the error "failed remote failure" and "preflash valiudation failed", I've tried to flash either factory recoveries and TWRP with the same result. Addtionally, If i try to flash any sparsechunk it will also give the error " invalid signed image".
I'll have to say that trying to enable USB debugging vía fastboot is an excellent idea, i did't try that, i hope i can do it without the recovery cuz i can't boot to it and until now, i couln't flash any recovery.
Thanks again!
Edit: I've read quite a bit and seems like in every case you would need a working recovery to allow USB debugging, so I think I can not do it in the actual state of things haha.
Edit2: I have a pair of questions:
1. Do i need to check allow oem unlocking in developer options in android 6.0 in order to unlock the bootloader?
2. In order to use RSD lite and it recognizing muy phone do i have to have USB debugging allowed?
Psicovirus said:
Hey, you came back!! Haha.
Well, trying to flash anything will give me the error "failed remote failure" and "preflash valiudation failed", I've tried to flash either factory recoveries and TWRP with the same result. Addtionally, If i try to flash any sparsechunk it will also give the error " invalid signed image".
I'll have to say that trying to enable USB debugging vía fastboot is an excellent idea, i did't try that, i hope i can do it without the recovery cuz i can't boot to it and until now, i couln't flash any recovery.
Thanks again!
Edit: I've read quite a bit and seems like in every case you would need a working recovery to allow USB debugging, so I think I can not do it in the actual state of things haha.
Edit2: I have a pair of questions:
1. Do i need to check allow oem unlocking in developer options in android 6.0 in order to unlock the bootloader?
2. In order to use RSD lite and it recognizing muy phone do i have to have USB debugging allowed?
Click to expand...
Click to collapse
I don't know - I did.
Probably. I didn't know you could use RSDlite on the Moto g3 - paste a link if you find one!
What do you say you did? Didnt understand that
Psicovirus said:
What do you say you did? Didnt understand that
Click to expand...
Click to collapse
Sorry - I believed I switched on that switch for allow bootloader unlocking as well as USB Debugging.
from that google search - look at this and try it
https://www.youtube.com/watch?v=ShjJ3KkH6_I
http://www.allmobitools.com/2014/10/android-multi-tools-v102b-all-pattern.html
KrisM22 said:
from that google search - look at this and try it
https://www.youtube.com/watch?v=ShjJ3KkH6_I
http://www.allmobitools.com/2014/10/android-multi-tools-v102b-all-pattern.html
Click to expand...
Click to collapse
Hey friend, i don't want to be a pushover. You're taking the time to help me and i see that, but i saw the video, and he starts the phone by making a data erase, i already did that, and the phone refuses to start. Same error. "version downgraded for boot" "failed to validate boot image" "fastboot reason: fall-through from normal boot mode".
And says in big red letters "Start up failed: Your device didn't start up succesfully. Use the software repair assistant on computer to repair your device."
I feel like i've tried everything.
Thanks again.
Ulefone power 2 Development and Support-
Basic Device Details-
Display- 5.5 inch
OS- android 7.0 Nougat
Chipset - MT6757T
RAM- 4GB
Disclaimer-
Code:
i am not Responsible for any damage to Your Device..
official Firmware-
https://drive.google.com/drive/folders/0B8NC4kBpjQhYV1lWOEtYWThRRms
twrp Recovery-
https://drive.google.com/open?id=0B1aXJDZjE8bvM0h0aTVEOEdBS1U
SP Flash tools and Driver-
https://drive.google.com/folderview?id=0B6O3B5Tc7Wr9ZzgxQmcyNmNoX00
Magisk-
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
No verity opt-Encrypt-
https://www.androidfilehost.com/?fid=673368273298927206
extras-
Greenify for Battery-
http://m.hiapphere.com/apk-com.oasisfeng.greenify
Build.prop tweaks-
[Must Backup official before try-
https://forum.xda-developers.com/attachment.php?attachmentid=4248841&stc=1&d=1503381757
Guide-
Flash Firmware-
1. Install Vcom Driver Run SP flash tools, Load Scatter File , Check Everything and then click Download, as soon as connect your Switched off Phone.
Flash twrp-
Code:
fastboot oem unlock
fastboot flash recovery recovery.img
or use inbuild script
if you have Scatter then you can Flash with SP flash tools.
Root-
flash Magisk via twrp or you can also use Supersu 2.78XX.
Mod-
Will be added Soon....:good:
version- 3.00XX
Credit- XN Logos
Donation- https://Paypal.me/droiddeveloper
Please Don't create mirror Without the Link of This Page.
I tried it but it didn't work. twrp is installed but my phone doesn't boot into the system anymore. When I reboot it goes back to Twrp and then the touchscreen doesn't work anymore. I have to connect an USB-mouse. But it still doesn't boot.
When I try to flash or wipe sth it says "unable to mount"
I had to flash the original software again with SP Flash Tools
No flash No verity encrypt to Disable boot verification
XN Logos said:
No flash No verity encrypt to Disable boot verification
Click to expand...
Click to collapse
sorry but what does that mean?
So i used your TWRP Recovery, normally it should work and it does but why is my data shown as 0.
Thank you too. Please help
where is the scatter file?
gasperoni said:
where is the scatter file?
Click to expand...
Click to collapse
no Scatter included use Fastboot, or You can take scatter from ROM.
Ok but where is the recovery image file to flash via SP Flash Tools? I only see an exe-file saying "flash recovery" and a 12.6MB file called "rk" but it's shown me as a mp4-file
it worked!!! Thank yoU!! @gasperoni, just start "Flash Recovery.exe" and do what is written in the window. It's really easy.
i have include a Script which have ability to unlock bootloader and then flash twrp, if you flash with SP flash tool your Device not bootup because bootloader is Loacked. so Simply use Given Instruction Not SP flash.
any custom ROM
non yet
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Unlucky25 said:
hm..i install twrp with your "flash recovery.exe", my phone reboots, i have to press "volume up" to unlock my bootloader. then trwp starts.
until here everything works fine. But when i am installing Superuser and restart my phone, it writes sth like "orange mode, your phone is untrusted" and just boots into twrp, touchscreen isnt working. So i have to flash it again, but i didnt achieve twrp of course :S
Click to expand...
Click to collapse
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
kylebutler said:
Same issue for me.
I tried twice to install the recovery with the .exe file. Both times I bricked the phone. Why?
Click to expand...
Click to collapse
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash softwhttps://forum.xda-developers.com/usercp.phpare says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
pavelmracek said:
I had also issues using the flash tool provided on the Ulefone website, the same as you say (with the checksum). None of checksum-generating software worked for me, so I was searching long for an alternative and found this flash tool: https://spflashtool.com/. Using this tool, flashing worked for me perfectly even without having to bother with checksums.
Good luck!
Click to expand...
Click to collapse
Thank you very much for this! That tool works flawlessly unlike the ulefone garbage.
On another note... anyone know if there is source code for the power 2 to be found somewhere or did the dev just port another recovery somehow? I tried a while back just porting twrp by swapping files but i couldn't get the image to repack with the kitchen tool so i gave up.
ml11ML said:
Same result here. But how did you get the factory rom to flash on the phone? I first got some checksum error and had to find a checksum generator and now the silly multiport flash software says:
" Warning maybe error as follows: 1 com port number repetitive or invalid 2 brom and preloader have the same comport number! Please modify them in INI file or scan again."
I think i did everything correctly (installed the drivers and stuff as it says on the ulefone download page) but i haven't flashed any mediatek devices in a long time and i would be very thankful if someone can tell me what i'm doing wrong. I don't mind it getting bricked as i know that is always a risk with mediatek, but i do need to be able to flash the stock rom.
Click to expand...
Click to collapse
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Unlucky25 said:
hey, how did you set your IMEIs after bricking? I usually used Engineer Mode to set them, but thats not working since i am missing "CDS Information"
Click to expand...
Click to collapse
Uh, i never even bothered to think about imei as it just worked without doing anything.
ml11ML said:
Uh, i never even bothered to think about imei as it just worked without doing anything.
Click to expand...
Click to collapse
ok nevermind, i found a solution..yeyy
so if anybody stumples across here, who has no IMEI set, CDS information in MTK mode and no rooted phone... u can set your IMEI in MTK engineering mode under "GPRS"!
Hello, i just got my GS7 as an upgrade from rogers a few days ago. I flashed TWRP and rooted with CF auto root. I made a huge mistake by disabling developer options after rooting, and then rebooted my phone. When i disabled developer options, it also disabled OEM unlock. When my phone rebooted it said in red letters above the samsung logo: Custom binary blocked by FRP lock. It would then turn off and only show that screen. I could not boot into recovery, i could only go to download mode. So using odin i attempted to flash the stock firmware and stock recovery. Now when i try to turn on my phone it is stuck in a boot loop but i can get into the stock recovery. In recovery i did a factory reset, but it was still in a boot loop. At the bottom of the recovery page it says:
No Support SINGLE-SKU
Supported API: 3
dm-verity error . . .
In download mode it says: ODIN MODE
DOWNLOAD SPEED: FAST
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:2 K:0 S:1
I have tried using kies 3 emergency firmware recovery, but my device does not show up on the list. I tried firmware upgrade and initialization by entering model number and serial number, but it says SM-G930W8 does not support initialization.
MODEL: SM-G930W8
SM-G930WZKAXAC
Im stuck and dont know what else to try. Any advice?
mrkole said:
Hello, i just got my GS7 as an upgrade from rogers a few days ago. I flashed TWRP and rooted with CF auto root. I made a huge mistake by disabling developer options after rooting, and then rebooted my phone. When i disabled developer options, it also disabled OEM unlock. When my phone rebooted it said in red letters above the samsung logo: Custom binary blocked by FRP lock. It would then turn off and only show that screen. I could not boot into recovery, i could only go to download mode. So using odin i attempted to flash the stock firmware and stock recovery. Now when i try to turn on my phone it is stuck in a boot loop but i can get into the stock recovery. In recovery i did a factory reset, but it was still in a boot loop. At the bottom of the recovery page it says:
No Support SINGLE-SKU
Supported API: 3
dm-verity error . . .
In download mode it says: ODIN MODE
DOWNLOAD SPEED: FAST
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 1 (0X0500)
RP SWREV: B:2 K:0 S:1
I have tried using kies 3 emergency firmware recovery, but my device does not show up on the list. I tried firmware upgrade and initialization by entering model number and serial number, but it says SM-G930W8 does not support initialization.
s/n: r58jc1a22hr
MODEL: SM-G930W8
SM-G930WZKAXAC
Im stuck and dont know what else to try. Any advice?
Click to expand...
Click to collapse
When flashing with Odin, what files did you use? (Did you use all 4: BL, AP, CP, and CSC?)
Craz Basics said:
When flashing with Odin, what files did you use? (Did you use all 4: BL, AP, CP, and CSC?)
Click to expand...
Click to collapse
i only used AP. I was following a youtube video where he only selected AP
mrkole said:
i only used AP. I was following a youtube video where he only selected AP
Click to expand...
Click to collapse
Ah. You need to use atleast ap AND csc. Dont use home csc if its there.
Down the stock ROM from sammobile.com. It will be in a zip format. Unzip once it using 7zip to yield a tar.md5 file. Just flash this entire file in the appropriate Odin slot.
I have always flash Samsung stock firmware without splitting the firmware into 4 files.
I would not use kies anymore.
audit13 said:
Down the stock ROM from sammobile.com. It will be in a zip format. Unzip once it using 7zip to yield a tar.md5 file. Just flash this entire file in the appropriate Odin slot.
I have always flash Samsung stock firmware without splitting the firmware into 4 files.
I would not use kies anymore.
Click to expand...
Click to collapse
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?
Craz Basics said:
Ah. You need to use atleast ap AND csc. Dont use home csc if its there.
Click to expand...
Click to collapse
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?
mrkole said:
Update: I flashed "combination files" which was supposed to disable FRP lock. After flashing I seem to have gotten an entirely new 'recovery?' I'm really not sure what this is or where to go from here. This is what it looks like: Combination Files https://imgur.com/gallery/jsJIJ
Any ideas on what this is?
Click to expand...
Click to collapse
Thats the recovery or android?
Download this: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/XAC/download/G930W8VLU2BQK4/198012/
And flash all 4 files in Odin. Not sure what firmware you flashed lol. This should fix up everything, you'll have to unlock the bootloader again if you had to unlock it yourself.
Here is the latest Rogers rom I found: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/RWC/download/G930W8VLU2BQK4/197399/
I have never flashed 4 files to a Samsung phone when restoring to stock. I download the file, zip once to get a single tar.md5 for, and flash the single file in Odin.
Craz Basics said:
Thats the recovery or android?
Download this: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/XAC/download/G930W8VLU2BQK4/198012/
And flash all 4 files in Odin. Not sure what firmware you flashed lol. This should fix up everything, you'll have to unlock the bootloader again if you had to unlock it yourself.
Click to expand...
Click to collapse
Solved!!! after flashing combination files found here: https://www.androidfilehost.com/?fid=529152257862696216
on the left panel i could enable developer options in the settings app: https://imgur.com/gallery/jsJIJ
Then using the free trial of the chimera tool for windows i downloaded and flashed the stock firmware. Phone booted up and i just had to enter my google account info and i was good to go!
audit13 said:
Here is the latest Rogers rom I found: https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/RWC/download/G930W8VLU2BQK4/197399/
I have never flashed 4 files to a Samsung phone when restoring to stock. I download the file, zip once to get a single tar.md5 for, and flash the single file in Odin.
Click to expand...
Click to collapse
Solved!!! after flashing combination files found here: https://www.androidfilehost.com/?fid=529152257862696216
on the left panel i could enable developer options in the settings app: https://imgur.com/gallery/jsJIJ
Then using the free trial of the chimera tool for windows i downloaded and flashed the stock firmware. Phone booted up and i just had to enter my google account info and i was good to go!
Hello,
I have unlocked the bootloader. I tried to do the steps with Magisk, this is it:
-Install Magisk.
-Patch AP.
-Copy it to PC.
-ReFlash with ODIN.
But when I do that, I got errors during installation on Download mode and the phone bricks. So I don't know if I am doing something wrong or happens that this device can't be rooted.
I have been searching but can't find any reliable information about, could you please give me some information or help?
Thank you!
Bump!
Got this error following installation instructions:
ODIN MODE (AVB Fail)
vbm*** Error verifying vbmeta image: HASH_MISMATCH (3)
vbmeta: VERIFICATION_DISABLED bit is set
CUSTOM VBMETA
VBMETA G715FNXXU8CUE1, 4000301 4R
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
tys0n said:
It's pretty simple and straight forward. I won't go in on details about odin, drivers etc as there's many guides about that already.
Or join the A40 tg group for any assistance with firmware, odin etc.
You'll need to unlock bootloader first, and it will TRIP KNOX.
Please read up on what it means before you proceed if you're not sure about it. It can't be reversed.
Download and install latest Magisk manager to your phone. https://github.com/topjohnwu/Magisk/releases
Download and install 7zip ZS to your pc. https://github.com/mcmilk/7-Zip-zstd/releases
Get the firmware for your phone and extract the AP file from the firmware zip. (Use samfirm or frija for fast download)
Open the AP*.tar.md5 with 7zip ZS and click on the boot.img.lz4, then drag the boot.img out of there.
Copy the boot.img to your phone, open Magisk Manager and click install, and again install, then "select and patch a file".
Browse to the boot.img you just copied to your phone and let Magisk do it's magic.
You'll find a magisk_patched.img in your download folder when it's done.
Copy it over to your pc, rename it to boot.img and make a .tar archive with boot.img in it.
Open Odin, put the tar in AP slot, connect your phone in download mode and hit start in Odin.
Open Magisk Manager again once the phone is booted to finish the setup.
Done.
Click to expand...
Click to collapse
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Awesome! The bad thing is that I already sold Xcover Pro because I need root yes or yes but well, I hope it will be useful for people in the future! Maybe even somebody try to port LineageOS.
d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?
-SpaceCowboy- said:
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?
Click to expand...
Click to collapse
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far
On my rooted SM-G715FN, I have:
CURRENT BINARY: Custom (0x3)
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF(U)
Secure Download: Enabled
Click to expand...
Click to collapse
In Developer Options, I have `OEM Unlocking` enabled.
iBowToAndroid said:
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far
Click to expand...
Click to collapse
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.
d5sword said:
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.
Click to expand...
Click to collapse
Because his phone is not SM-G715FN
The ADB removal method worked for me. There's a "Debloat" text file up on GitHub that makes this a breeze.
Link: https://github.com/khlam/debloat-samsung-android tellthebell
Once in debug mode, USB connected, and drivers installed:
ADB shell < commands.txt
Obviously, the text file must reside in the same folder as ADB.
travis659 said:
El método de eliminación de ADB funcionó para mí. Hay un archivo de texto "Debloat" en GitHub que hace que esto sea muy sencillo.
Enlace: https://github.com/khlam/debloat-samsung-android tellthebell
Una vez en modo de depuración, USB conectado y controladores instalados:
Shell ADB <comandos.txt
Obviamente, el archivo de texto debe residir en la misma carpeta que ADB.
Click to expand...
Click to collapse
i think only working in snapdragon devices, no? the Xcover use Exynos
d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
Just wanted to say a huge thank you to yourself and tys0n.
I purchased an Xcover Pro brand new from Microless global for an absolute steal...as in a price that was simply too good to be true. It was only upon setting up the device that I realised why they were offering such a low price.
The device was encumbered by an unavoidable corporate knox enrollment service. Sadly I suspect most people who purchase from them won't realise just how much control of their device they are handing to some random company if they just press OK during setup, but I wasn't having it. Ignoring the enrolment promp was not possible; you couldn't even access the home button or recent button until you'd authorised under knox and handed control of the device over to some faceless entity.
Thanks to the efforts of those in this thread I have been able to unlock BL, root the SM-G715FN/DS and freeze all of the knox bull****. The device now belongs to me.
The only thing I'd like to ad for those that come here looking for answers is that the process above is spot on, but I had to use this tool to create my .tar file. Simply creating a .tar archive with the .img file in it wasn't good enough for my device; it rejected that as an unauthorised file.
Use this tool once you've patched the boot.img with magisk and renamed it.
[Script][Tool] how to create a tar.md5 file from img For Odin
for how want to use Odin to flash the ClockWorkMod Recovery img or any image files like "boot.img", this is a tool to create a tar.md5 file from the img file. unzip the file tool, and put your img files into the same directory of the batch file...
forum.xda-developers.com
Props to mkh.mourad and testament to the usefulness of XDA that a file from 2013 got me over the line.
I'm certainly no developer, but given the relative ease with which we got this far, I hope it's not too far down the road until we get TWRP and can start mucking around with some roms. Please post here if you have any ideas. This device has real potential as a very long term solution.
Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.
TomasNM said:
Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.
Click to expand...
Click to collapse
The "KG" status must be in "checking" so that you can flash a custom binary, you must leave the phone on 168 hours in a row with an internet connection otherwise it will not disappear
SpaceCowboy,
thank you for the advice, I waited a bit and today I managed to root the phone successfully.
However, I tried to install some Magisk modules and the phone stuck on initial screen (Samsung Galaxy Xcover Pro), even not get to the "SAMSUNG" screen.
Only solution was to wipe all data in recovery.
Any ideas how to install Magisk modules without risk?
Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.
Psyckosama said:
Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.
Click to expand...
Click to collapse
What's your Baseband Version?
iBowToAndroid said:
What's your Baseband Version?
Click to expand...
Click to collapse
g715u1uescbuj1
Psyckosama said:
g715u1uescbuj1
Click to expand...
Click to collapse
OEM unlock doesn't exist on US models. This model is bootloader unlockable via paid 3rd party services, but only up until bootloader revision 7. Since you're fully updated, you have revision 12
Hi
I tried to install stock Android 12 on my samsung A31. Due to some error in the PC the installation stopped halfway.
I used FRP hijacker tool to get back to download window. However now the error shows "Partitions prism. Reason prism: Error verifying vbmeta image : invalid vbmeta header(6) "
And when I tried to flash using odin again it says setup connection. Complete failed.
Is there no way to get this phone working? Please help!!
Repartition definitely should be off. Also make sure you have the right file to flash, I know there are some different Note 10 tab models. Easiest way to download the latest firmware version is Frija, it doesnt have the limited download speed like Sammobile. The .enc4 file it will give you can easily be extracted just like a .zip file omegle xender .
You shouldt need the .pit file when repartition is off
Junkun007 said:
Hi
I tried to install stock Android 12 on my samsung A31. Due to some error in the PC the installation stopped halfway.
I used FRP hijacker tool to get back to download window. However now the error shows "Partitions prism. Reason prism: Error verifying vbmeta image : invalid vbmeta header(6) "
And when I tried to flash using odin again it says setup connection. Complete failed.
Is there no way to get this phone working? Please help!!
Click to expand...
Click to collapse
You're trying to flash a firmware with an older RP rev than the one stored in your device, you can see it from the error "Fused 2 > Binary 1". Download a firmware with RP rev 2 or higher (more info here)