When I proceed to flash an earlier version(downgrade) of stock rom, it get stuck on recovery.img in Odin and on the device it says "sw rev check fail bootloader device 2 binary 1" Tried flashing other earlier versions of stock roms even the latest but still getting that message and never get past recovery.img. Fortunately, the device still works when I boot it normally. How can I fix this? Wanted to try other roms because of oem not appearing even after 168hrs.
Device: S9+ SM-G965F/DS
Exynos
Aug. 1, 2018 Patch
i am facing the same issue i did some googling on this matter & found out that our binary number is updated to U2 from U1 so in simple words boot loader is updated to u2 & you cannot flash it back to U1 so far my learning is this.if you want to try some other rom you will need to flash U2 only something like this G965FXXU2
Post a screenshot in download mode and i'll post you a link of your right firmware also recovery error may cause of usb port try to change usb port
Can we downgrade to U2 to U1 pls let me know
rockykv2 said:
i am facing the same issue i did some googling on this matter & found out that our binary number is updated to U2 from U1 so in simple words boot loader is updated to u2 & you cannot flash it back to U1 so far my learning is this.if you want to try some other rom you will need to flash U2 only something like this G965FXXU2
Click to expand...
Click to collapse
Now that you said it, all the firmwares I've downloaded got U1 in it. So I assume you also updated to the August patch?
I update to August patch that changed the binary to u2 udpated the boot loader so when u try to flash the same it will not downgrage u need to find u2 only in firmware... if there is a workaround if anyone can help it will be good
archillect said:
Post a screenshot in download mode and i'll post you a link of your right firmware also recovery error may cause of usb port try to change usb port
Click to expand...
Click to collapse
I did try all the Usb ports and cables and the results are still the same
Screenshot:
https://ibb.co/dyvk5p
rockykv2 said:
I update to August patch that changed the binary to u2 udpated the boot loader so when u try to flash the same it will not downgrage u need to find u2 only in firmware... if there is a workaround if anyone can help it will be good
Click to expand...
Click to collapse
Never got to show oem since I got this device, that's why I've been flashing other stock roms and still no luck until updating to August patch made it more impossible
Same issue i am facing
johnpaulang38 said:
When I proceed to flash an earlier version(downgrade) of stock rom, it get stuck on recovery.img in Odin and on the device it says "sw rev check fail bootloader device 2 binary 1" Tried flashing other earlier versions of stock roms even the latest but still getting that message and never get past recovery.img. Fortunately, the device still works when I boot it normally. How can I fix this? Wanted to try other roms because of oem not appearing even after 168hrs.
Device: S9+ SM-G965F/DS
Exynos
Aug. 1, 2018 Patch
Click to expand...
Click to collapse
please let me know if its there any solution...thanks in advance
Yeah apparently this is a somewhat common issue for newer samsung devices (i think it started from the s6)
You can't downgrade anymore, the only way i ever got an older version to work was by flashing the bootloader from a combination firmware. Other than that sol.
Did u manage to downgrade with combination rom can u share your steps
My S9+ wont flash back to stock firmware (assuming because of the error above) any ideas how to fix this ?
---------- Post added at 07:26 PM ---------- Previous post was at 07:16 PM ----------
Whats a combination firmware? my device is G965 BTU
rockykv2 said:
Did u manage to downgrade with combination rom can u share your steps
Click to expand...
Click to collapse
u cant
i got the same problem! could we assuming that in future stockrom's the bootloader is equal or higher to update that ****?
Same thing in my samsung a105g,can someone help me please..?
Related
I was in the process of removing kingroot and installing supersu when my phone decided to reboot and now will not boot past the very first screen no matter how long I let it sit. I tried factory resetting it but that didn't change anything. I've searched high and low for firmware but have come up empty. Does anyone have stock firmware for the Alcatel Streak? Thanks.
archmagusdg said:
I was in the process of removing kingroot and installing supersu when my phone decided to reboot and now will not boot past the very first screen no matter how long I let it sit. I tried factory resetting it but that didn't change anything. I've searched high and low for firmware but have come up empty. Does anyone have stock firmware for the Alcatel Streak? Thanks.
Click to expand...
Click to collapse
Concur.
I had exactly the same problem. Alcatel Streak (40600) would not boot after I did KingRoot and superSu replacement.
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.
i need the file for the streak 4060o
@Viva La Android
Viva La Android said:
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.[/QUOT
Ive been able to aquire a stock firmware as well...the problem is after i flash with qfil it wont boot??? Qualcom qfil says download complete with no sahara errors..ive got the emmc programmer file if anyone needs... i just dont know what to do next to get it to boot
Click to expand...
Click to collapse
KtownJeff said:
@Viva La Android
Viva La Android said:
There has been no activity on this or other Alcatel STREAK threads for some time, but for any members needing, I have a full stock ROM for the Cricket Alcatel STREAK (4060o), Android 6.0.1 Marshmallow. Any interested members please leave a comment and I will upload the ROM and post a download link.[/QUOT
Ive been able to aquire a stock firmware as well...the problem is after i flash with qfil it wont boot??? Qualcom qfil says download complete with no sahara errors..ive got the emmc programmer file if anyone needs... i just dont know what to do next to get it to boot
Click to expand...
Click to collapse
I understand your dilemma. My stock ROM and firmware are installable via TWRP, which I have ported over from the Alcatel IDEAL (4060a). Flashing a firmware to this device without using a custom recovery is problematic to say the least. QFIL/QPST does not seem to work, and true to their typical protocol, TCL seems to have disabled fastboot mode on the 4060o. I will research this matter some more to see if I can help. There are reports of forcing the device into a hard brick by corrupting the /sbl1 bootloader partition. As such, Qualcomm's EDL (9008) mode is enabled which will allow for an emergency firmware installation per firehose protocol via QPST. But again, I'll try and research this more. Also, if you don't mind, could you share the firmware you have please? It sounds like you have an official package which I have not been able to locate. My ROM and firmware are both self compiled. Thank you.
Click to expand...
Click to collapse
awesome
Viva La Android said:
KtownJeff;80315069 [user=10059830 said:
@Viva La Android[/user]
I understand your dilemma. My stock ROM and firmware are installable via TWRP, which I have ported over from the Alcatel IDEAL (4060a). Flashing a firmware to this device without using a custom recovery is problematic to say the least. QFIL/QPST does not seem to work, and true to their typical protocol, TCL seems to have disabled fastboot mode on the 4060o. I will research this matter some more to see if I can help. There are reports of forcing the device into a hard brick by corrupting the /sbl1 bootloader partition. As such, Qualcomm's EDL (9008) mode is enabled which will allow for an emergency firmware installation per firehose protocol via QPST. But again, I'll try and research this more. Also, if you don't mind, could you share the firmware you have please? It sounds like you have an official package which I have not been able to locate. My ROM and firmware are both self compiled. Thank you.
Click to expand...
Click to collapse
https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
stock cricket Rom mm 6.0.1
@Viva La Android
...now let me tell you how this started to give you more info....I rooted with kingroot installed twrp for the 4060a with flashify and directly installed magisk 18 with twrp...somewhere in there i deleted king root...everything worked great..made a full back up through twrp..I had titanium backup installed deleated all the bloat and started on magisk mods..installed xposed as well...flashed viper4...well I got greedy and started trying to dirty flash pixie4 roms to get a higher os like oreo...fail fail fail...I had read in the forum not to tick fix permissions in TWRP but i did it anyway...never ending bootloop after that...i side loaded a custom rom for the 4060a ....hard brick...i guess thats when i was EDL mode because of the wrong bootloader...i tried to flash the cricket rom with qset\qfil and it would not work...then i flashed the stock 4060a and it worked...wouldn't boot past the splash screen...kinda weird though because the splash screen was split in half and reversed with a gap in the middle....ill figure out a way to screen shot later....but i was able to hook back into the pc and I have adb but unauthorized because the OS got factory wiped so no usb debugging...I do have fastboot access now...which is strange but since my oem unlock is not ticked in the OS every boot img recovery img or system img i try to flash acts all good then fail in fastboot....my realization is that I wiped my modem somewhere in there and it replaced it with a downgrade which forced the EDL mode...well I flashed wrong with the 4060a firmware so Im stuck is all I can figure...I cant get adb shell access either haven't tried
shell with ubuntu/python maybe i can get shell access to force feed super user and tick oem unlock for the bootloader...other than that Im stumped...Maybe DD commands and a good dump file to see where I stand...and as far as my TWRP backup goes..I got careless and deleated it when I formated my PC to remove all the crap Ive picked up trying to fix this mess off the MTK and GSM sites...
My main objective right now is to get my adb key authorized there has to be a way
Click to expand...
Click to collapse
Yeah I agree totally. If there was a way to enable the OEM Unlocking option from a shell environment, you would likely have total control of the device via fastboot protocol. Like you, I concur that there has to be a way. You have me perplexed enough to dig in and help find an answer. I have a working device and a bricked device, so I am free to experiment around on my brick using QFIL/QPST. I am impressed that you have been able to access fastboot. This is more progress than most people make, so congrats there. Nice work.
By the way @KtownJeff, if you need any partition dumps from my device, for example, /sbl1, /aboot, /rpm, /tz, etc., just let me know. Just a thought, but if you could push my /persist partition image to your device (my OEM Unlocking is enabled), I think your OEM Unlocking would tick enabled. I recall a Moto device where OEM Unlocking was enabled in a similar manner. @KtownJeff, if possible, please share a download link of the official firmware package to which you referred. I will be glad to share my self compiled firmware package and stock ROM. Thank you friend.
Viva La Android said:
Yeah I agree totally. If there was a way to enable the OEM Unlocking option from a shell environment, you would likely have total control of the device via fastboot protocol. Like you, I concur that there has to be a way. You have me perplexed enough to dig in and help find an answer. I have a working device and a bricked device, so I am free to experiment around on my brick using QFIL/QPST. I am impressed that you have been able to access fastboot. This is more progress than most people make, so congrats there. Nice work.
By the way @KtownJeff, if you need any partition dumps from my device, for example, /sbl1, /aboot, /rpm, /tz, etc., just let me know. Just a thought, but if you could push my /persist partition image to your device (my OEM Unlocking is enabled), I think your OEM Unlocking would tick enabled. I recall a Moto device where OEM Unlocking was enabled in a similar manner. @KtownJeff, if possible, please share a download link of the official firmware package to which you referred. I will be glad to share my self compiled firmware package and stock ROM. Thank you friend.
Click to expand...
Click to collapse
I actually stumbled on the fastboot accidentally!!...After I flashed the Stock 4060A firmware with the split up splash image I checked my driver to see if I was in qloader 9008 mode still and I saw the holy grail "Android Bootloader"...The phone screen didnt have anything showing on it like any moto mfastboot mode or like a samsung when hooked up to odin...just the frozen "half splash" Alcatel Logo..I had minimal adb/fastboot installed...I switched to the Android platform tools latest version and had better results...I had a lot of failures when it come down to recovery partition and system partition...I had some successes tho...Fastboot erase works but I dont know if thats standard and the OS reinstalls what I erased because of the lock..prob so just like no superuser access in ADB...I tried to re flash TWRP for like three days and gave up...I forgot to mention I have no stock recovery access.......Yes please I need a full phone dump of whatever you got... all the better..I might try shorting my board to get back to EDL so I can try flash the cricket 6.0.1 again...but I don't want to lose my fastboot access either....the 6040O aboot partion does not have fastboot... The Stock crickit 4060O rom link was posted earlier...I'm in the process of uploading to MEGA as we speak so here in a few I will post all my stuff for this phone...And please share yours as well...
stock Rom's and tools for Alcatel 4060A/O
@Viva La Android
TWRP Recovery https://mega.nz/#!QTwlESgJ!YSu6T5r93AonRiSxh6QQtov_ZDsxz95YW1RXYSuPJRQ
QSET/QSIL Qualcom all in one https://mega.nz/#!xSoSQCTK!MPQJytxtVUl4aHBXQp7wYbZb9o6ZpXX5wpTy3dqX7xA
Firehose Programmer file for QFIL/QSET https://mega.nz/#!EGQAXKBC!LfyE2zJzhXB15XeAgxB3H2HcL0OiXNa38V74ZodJf5I
Acatel Ideal 4060A AT&T Stock Firmware L 5.1.1
https://mega.nz/#!8ewAxCZS!sGURkuzmzcgbh6_AYOMyokzkx3VA74g50gYfZPFZOAA
Alcatel Streak 4060O Cricket Stock Firmware MM 6.0.1 https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
Fix BootLoop Alcatel Ideal
there´s any stock rom flashable for the alcatel ideal? i need unbrick my device because when i make a flashable stock rom the device boots and shows the screen for a second and after still bootlooping, i tried with QFIL but i have problems connecting the device, any way to fix? porting a rom with same chipset? or using another methods. PLZ i need unbrick my phone :crying:
KV2_URSS said:
there´s any stock rom flashable for the alcatel ideal? i need unbrick my device because when i make a flashable stock rom the device boots and shows the screen for a second and after still bootlooping, i tried with QFIL but i have problems connecting the device, any way to fix? porting a rom with same chipset? or using another methods. PLZ i need unbrick my phone :crying:
Click to expand...
Click to collapse
There was one here on XDA. It was a TWRP flashable Android 5.1.1 stock ROM I believe. The OP of the ROM is no longer on XDA and it appears that the download links are dead. I'll try to find you a copy of the ROM though.
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
KtownJeff said:
@Viva La Android
TWRP Recoveryhttps://mega.nz/#!QTwlESgJ!YSu6T5r93AonRiSxh6QQtov_ZDsxz95YW1RXYSuPJRQ
QSET/QSIL Qualcom all in onehttps://mega.nz/#!xSoSQCTK!MPQJytxtVUl4aHBXQp7wYbZb9o6ZpXX5wpTy3dqX7xA
Firehose Programmer file for QFIL/QSET https://mega.nz/#!EGQAXKBC!LfyE2zJzhXB15XeAgxB3H2HcL0OiXNa38V74ZodJf5I
Acatel Ideal 4060A AT&T Stock Firmware L 5.1.1
https://mega.nz/#!8ewAxCZS!sGURkuzmzcgbh6_AYOMyokzkx3VA74g50gYfZPFZOAA
Alcatel Streak 4060O Cricket Stock Firmware MM 6.0.1https://mega.nz/#!BGwGFAgK!gW3ik2f_-oyI9MtER-PCrfSTQCio4CFzVWR6JVmSw_0
Click to expand...
Click to collapse
Oh thank you very much. I was in need of the 4060o official firmware package. I'm in debt to you. Thanks for all the extras as well! Nice. I will upload my stock partition dump of my 4060o and get that posted ASAP. Have you tried using an insecure boot image for ADB superuser (ADBD) access? If you want I can set my stock boot image insecure with ADBD and upload that as well.
I'm found a copy of a stock 5.1.1 ROM for the 4060a that is TWRP flashable. I'm uploading it to Mega File now. I'll post the link when completed. I fixed the installer on this ROM and rewrote the Edify script.
4060a Stock ROM
TWRP Flashable Zip
Android 5.1.1 Lollipop
Build No. M5RUAR4
Root: SuperSU v2.82-SR5
Link: https://mega.nz/#!VEVUwaxB!sCsdYXPE-_ytsqKnXRJHhFLVLnn3jxCDY8bG7FP89nM
@KV2_URSS, if you have TWRP installed, this may unbrick your device.
Update: I dissected that ROM and discovered some syntax errors in the Edify script. I've rewritten the installer and fixed some bugs with the updater-script. I also just tested the ROM on my own 4060a and confirmed that it does work. I'll post the updated link to replace the other link in a few minutes.
Viva La Android said:
Update: I dissected that ROM and discovered some syntax errors in the Edify script. I've rewritten the installer and fixed some bugs with the updater-script. I also just tested the ROM on my own 4060a and confirmed that it does work. I'll post the updated link to replace the other link in a few minutes.
Click to expand...
Click to collapse
Thanks, this is a posibility for unbrick my phone, you now fixed the rom link? :good:
KV2_URSS said:
Thanks, this is a posibility for unbrick my phone, you now fixed the rom link? :good:
Click to expand...
Click to collapse
flashed but still bootlooping, i think my phone its broken Anyway: thanks for help!
KV2_URSS said:
flashed but still bootlooping, i think my phone its broken Anyway: thanks for help!
Click to expand...
Click to collapse
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
---------- Post added at 01:22 PM ---------- Previous post was at 01:17 PM ----------
@KtownJeff I'll try to have the 4060o stock 6.0.1 ROM posted later today, and I'll post the dump files from my device. Thank you again for the official firmware.
Viva La Android said:
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
Click to expand...
Click to collapse
i flashed the updated rom with your name in updater script and still bootlooping
KV2_URSS said:
i flashed the updated rom with your name in updater script and still bootlooping
Click to expand...
Click to collapse
Ok. My guess is your boot chain may be corrupt. I'll write you an installer to try and fix it. I'm fixing some things on the 4060o ROM, so I'll write you an installer for your 4060a when I get ready to upload the other ROM. In the installer, I'll place some of the bootloader partitions from the firmware package to be installed on your device.
Viva La Android said:
Did you download from the updated link? The ROM from the old link was bootlooping my 4060a also. I fixed the installer script and when I tried it again it worked. On the new one, I added my username to the installer script and removed the original dev's name. Is this the one you tried? Also, did you do a full wipe before installing? (/system, /cache, Dalvik, format /data)
---------- Post added at 01:22 PM ---------- Previous post was at 01:17 PM ----------
@KtownJeff I'll try to have the 4060o stock 6.0.1 ROM posted later today, and I'll post the dump files from my device. Thank you again for the official firmware.
Click to expand...
Click to collapse
@Viva La Android....no problem for the files my friend...please post the ROM and dump files...i went as far as test point into EDL mode and I cant get anything to download for some reason...Im gonna play around with QSET and see if there is a way to just wipe and manual install partitions that way
KtownJeff said:
@Viva La Android....no problem for the files my friend...please post the ROM and dump files...i went as far as test point into EDL mode and I cant get anything to download for some reason...Im gonna play around with QSET and see if there is a way to just wipe and manual install partitions that way
Click to expand...
Click to collapse
Ok friend. I'll expedite and get that done now. To clarify, you want a full partition dump of my 4060o, correct?
The partition dump files and MM stock ROM for 4060o are uploading now. @KtownJeff, I don't have the best signal tonight in terms of fast upload/download data speed, but the ROM and files you need are uploading and links will be posted here ASAP. For informational purposes, my partition dump is taken from a stock Android 6.0.1 Alcatel STREAK, Build No. A45UC50, Build Date: June 24, 2016; Security Patch Level June 1, 2016, Kernel Version: 3.10.49, and Baseband Version: MSM8909.12110.15W46. My ROM has been built from this firmware version as well.
Update: Link will be posted within the hour.
All gone. Including TWRP. The only thing that remains is Stock Recovery. Phone Locked, FRP Locked. It happened after I restored OEM. No USB Debugging enabled, so cant re-flash rom with ADB. Same goes for OEM Unlock. ADB sees the phone, but cannot unlock or re-flash. eRecovery fails to download firmware. So, any ideas ? What can I do ? 200$ worth motherboard change or any other way ? Please help.
i bricked my mate 10 lite too....
edcavdar said:
All gone. Including TWRP. The only thing that remains is Stock Recovery. Phone Locked, FRP Locked. It happened after I restored OEM. No USB Debugging enabled, so cant re-flash rom with ADB. Same goes for OEM Unlock. ADB sees the phone, but cannot unlock or re-flash. eRecovery fails to download firmware. So, any ideas ? What can I do ? 200$ worth motherboard change or any other way ? Please help.
Click to expand...
Click to collapse
i did an upgrade from 7.0 nougat to oreo 8.0 using firmware finder.apk, after that every thing was going good, i backed up my stock rom and wanna try 8.0 custom rom and accidentally i formatted my backup and and tried many custom roms but no survival chances,
now my oem info shows RNE-L21C432B133, i had also downloaded the full ota + hw/eu file but dont know how to flash properly mate 10 lite.
can any one help ?
https://forum.xda-developers.com/android/development/help-mate-10-lite-nova-2i-soft-bricked-t3807939
check this forum
---------- Post added at 08:01 PM ---------- Previous post was at 08:01 PM ----------
JAZZYBUTT999 said:
i did an upgrade from 7.0 nougat to oreo 8.0 using firmware finder.apk, after that every thing was going good, i backed up my stock rom and wanna try 8.0 custom rom and accidentally i formatted my backup and and tried many custom roms but no survival chances,
now my oem info shows RNE-L21C432B133, i had also downloaded the full ota + hw/eu file but dont know how to flash properly mate 10 lite.
can any one help ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/development/help-mate-10-lite-nova-2i-soft-bricked-t3807939
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Info about the device
For some unknown reason, I can't upload photos, here is the device info:
Model number: SM-S327VL
Android version: 6.0.1
baseband version: S327VLUDS4ARF2
kernel version:
3.18.24-11771718
[email protected] #1
Mon Jun 11 11:55:20 KST 2018
Build number
MMB29M.S327VLUDS4ARF2
HenryGong2001 said:
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Click to expand...
Click to collapse
I have the exact same problem. This is as close as I have gotten to installing custom recovery in order to root my phone
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------
I have the stock firmware if anyone needs it. It's the arf2 variety. Flashed it several times. Check hovatec if you want to find a root this year. I haven't found it yet but they are more active.
schrstopph said:
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
Click to expand...
Click to collapse
I think the problem could be that the bootloader is locked. I don't think there is a way to unlock it . I should be getting a new phone here soon, (Moto G6 that allows bootloader unlocking), so I will be able to test more freely with the SM-S327VL without worrying about bricking it.
schrstopph said:
This recovery does not work on SM-S327VL. I have tried to email him and get him to take the garbage down but he seems happy letting people waste time trying to flash it.
---------- Post added at 12:14 PM ---------- Previous post was at 12:09 PM ----------
I have the stock firmware if anyone needs it. It's the arf2 variety. Flashed it several times. Check hovatec if you want to find a root this year. I haven't found it yet but they are more active.
Click to expand...
Click to collapse
I need it.
I Want to put the newest Android version on my phone and I Need some help I tried 3 times.
My email: [email protected]
HenryGong2001 said:
I got this phone from Tracfone, and I'm trying to flash TWRP recovery on this phone. I find the recovery image here: https://www.getdroidtips.com/twrp-recovery-galaxy-j3-luna-pro/
Thanks to the tool created by mkh.mourad(https://forum.xda-developers.com/showthread.php?t=2446269), I successfully converted the recovery.img to recovery.tar.md5. When I try to flash the recovery through odin, I got the error: SECURE CHECK FAIL: recovery.
I have enabled the OEM unlock and CROM Services.
Can anyone give me some help? Thanks.
Click to expand...
Click to collapse
From what I know enabling oem unlock is only half of the issue. I assume you forgot the adb steps to perform the oem unlock commands.
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Arnys said:
Because you used wrong firmware.
(092y) or similar numbers are here because wrong firmware..
At least that was case for me, when I installed single SIM firmware over dual SIM phone, and of course, that build number not exist in update servers, so no updates here, till you fix your firmware
Click to expand...
Click to collapse
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
metalfangs said:
This is what I feared, thanks for confirming. I am hoping flashing this will solve my issues. Any advice before doing so?
Click to expand...
Click to collapse
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that.
And more important, what was full build number for your phone, aka ane-lx3c779, something like that, can you find it? Then I maybe be able to help.
And ,wulda be great if you type down all you did with phone, what used, etc.
Arnys said:
HM.. in link you gave here, is writed about ane-lx1, you mentioned your phone are ane-lx3 single sim, so, I'm not sure it can fix your problem..
And I'm not used that files, and can't say anything about that..
Click to expand...
Click to collapse
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
metalfangs said:
I noticed the file name is LX1 however in the description it says its for all models which is confusing. Any idea where I could find an official firmware download for LX3? Even a functional custom rom compatible with my device would be fine if I could find one.
I used hisuite to first downgrade and then used the firmware from this post to dload downgrade again in order to unlock the bootloader. I then factory reset after successfully unlocking the bootloader which left me at build 046.
To be honest I cannot remember what the original build number was although c779 does sound very familiar.
Click to expand...
Click to collapse
Hm, did you tried erecovery method ? Maybe that can fix your problem
metalfangs said:
So I managed to downgrade to successfully unlock my bootloader however I am now stuck on 8.0.0.046(092Y) and am unable to OTA update. I have installed magisk and TWRP and they are both currently working however I am curious as to why I cannot update to a newer 8.0 OTA firmware. Any suggestions? The device is an ANE-LX3 single sim.
Click to expand...
Click to collapse
Hello there brother. May I humbly ask how did you get your bootloader unlocked after downgrading? Can you share some steps please if you don't mind. Thank you
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
I also have the Samsung A21 from T Mobile (SM-A21UZKATMB). The phone is unlocked by T Mobile but there is no OEM bootloader unlock button under the Developer mode. Changing the date (forward and backward in time), then run the software update did not solve the OEM bootloader unlock button problem. I suspect the carrier (T Mobile) has disabled this function. You will need to unlock the bootloader to install the stock firmware.
To those who have enabled the OEM bootloader in the A21. Is your phone locked to a carrier in the USA like Verizon or T Mobile?
I also have the SM215DL, using straight talk utilizing verizon service, I also cannot unlock the bootloader. Everything you guys did, I did. Nothing worked.
samsung has done this to all A series phones intended for the U.S. from what i understand
Where there's a will, there's a way... someone has messed with my phone too do doesn't that mean that they're altering the data/data partition to r/w. Did you guys try fastboot flashing unlock vs. fastboot oem unlock. I'm going to contact Samsung about this and let u all know what's up.
And also why would there be a usb debugging port if this phone can't be modded? Idon't know the answer but maybe someone more expediency could come in and help us out. I also wonder if the flash_image command or just dd it would bypass it?
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
MaBo2020 said:
... there is NO way, to root the A21(s), see here: https://forum.xda-developers.com/t/root-possibility.4130739/page-12#post-84944589
Click to expand...
Click to collapse
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
thatha said:
I confirm that I have rooted my A21S sucessfully using this modified magisk (U3 Rom). No need to patch the whole AP.tar file, just patch boot.img file only. I upload my patched boot.img for those who need it. Just flash it via odin in AP slot. Thank you very much @grccorps.
https://forum.xda-developers.com/attachments/boot-tar.5299081/
Click to expand...
Click to collapse
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
MaBo2020 said:
... exactly Step-by-Step, how u do it with downloadlinks of all Software, what u used !
Many Peoples writes, that they have rooted the A21s, but no one shows, how ! With the newest Firmware u cant rooted the Phone, because there is no working TWRP, SuperSU or MAGISK - Version out for this Phone !
Click to expand...
Click to collapse
Extract boot.img from AP.tar, then use modified-magisk to patched it
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
And this is my U5 patched boot.img
MaBo2020 said:
... this Methode is not working, i try it many Times, no RootAcess ! Again: if u have newer Firmware on this Phone (End 2020 - until now) u cant root this Phone ! Maybe on ure Phone an older Firmware ...
Click to expand...
Click to collapse
I have just made a post here, you can try it
[SHARING] HOW TO ROOT A21S STOCK ROM WITH MAGISK
Hello friends I just want to share how to root A21S stock rom in case anybody needs it: 1. Unlock bootloader 2. (On PC) Extract boot.img.lz4 from AP...tar file, then copy it to phone 3. (On phone) Install ZArchiver to extract boot.img from...
forum.xda-developers.com
... and u shure, it its for the A21s or for A21 ?
The only hope of getting root on this phone is if you find a Dev who's interested enough to build a bootstrap recovery. I've not looked at the firmware & have no idea if there's an exploit that would work for that purpose.
Bootstrap recovery was the only way of getting root/custom recovery back in the days of Motorola D2 & Droid X, the original Droid X. Motorola was THE phone for development... Liberty ROM, Gummy ROM, Simply Stunning, etc.
I would not hold out hopes for that to happen here.
Peace - MS
Seriousfreedom said:
samsung has done this to all A series phones intended for the U.S. from what i understand
Click to expand...
Click to collapse
No, Samsung has done this to ALL North American models ever since the Galaxy S8. The bootloaders are not user-unlockable, like they are on international models. However, some models can be rooted via a software exploit if they're running very old firmware, or some models can even be bootloader unlocked via special files, if their firmware version is old enough
SpectreCular said:
I have a brand new Galaxy A21 (SM-S215DL). In Developer Options, there is NO OEM Unlock toggle (not even a grayed out one; it simply does NOT exist anywhere in settings). I have tried several different variants of the date/time trick to try to get it to appear, and none of them worked. But while in Download Mode, KG Status is shown as `CHECKING`, so doesn't that mean it should at least be visible? Do I even need to unlock my bootloader? Is it even possible?
Using Frija, I managed to get what I believe to be the correct stock firmware for my device. I also grabbed both of the latest official and patched versions of Odin. Flashing the stock firmware works, but flashing the patched Magisk AP fails with an AUTH error for file `vbmeta.img`, which leads me to believe that I actually DO need to unlock my bootloader... but if that's the case, I'm having trouble figuring out how to do so without the OEM toggle.
Is there anything else can I try?
Click to expand...
Click to collapse
Mine is rooted. But you have to buy a token.
o.class.jav said:
Mine is rooted. But you have to buy a token.
Click to expand...
Click to collapse
what token??
[email protected] said:
what token??
Click to expand...
Click to collapse
The one generated by the SamPwns steady.bin flash.
{Mod edit: Quoted post removed}
and where does one get 'TWRP' for the Samsung Galaxy A21S?? Thanks for the post its very detailed with very clear instructions, and i agree with you this is the tried and tested and perfect way of rooting your phone, only problem is that this is an unperect world a world where 'TWRP' for the SM-A217F does not exist
I just received a refurbished SM-S215DL (A21,) not as my provider's solution to the VoLTE soon to be required for 4G devices thing and right now it's a pretty severe downgrade for me since it lacks a lot of basic functionality I'm used to from my 2017 phone running LineageOS. Obviously it's pretty unlikely or probably outright impossible to ever see a real LineageOS ROM for this thing (and even if someone ever does it probably would be insanely unstable or incomplete,) but if I could at least root it (even if I have to manually patch or something) it would really help me out a lot. Has just nothing really been found short of sending some unknown person online some very very key device details and money (which I don't have or I'd be buying something else anyway)? (Also kind of suspicious that whatever method they're using isn't something available to the public anyway...)