Related
I've had an MT6577 phone sitting around for a few years now that's been stuck in a boot loop. My phone karked it today and this is the only device lying around, hoping it can be revived some how to save a few dollars.
It all happened one time when I tried to use an app to install a new font just to see what it looks like.
Seems to be the most obscure thing ever made as it has many names and models all with 0 firmware available. Typically SoSoon X8 Elite 3 shows up as the most common make but I recall the original box having Senq X8 Elite on it.
The bad?:
USB Debugging is almost certainly off because ADB can't find a device no matter if I just plug it in off, in bootloop (shows 2 drives on my PC that are not ready to be used in this stage), fastboot mode, recovery (install update from ADB)
Questionable root, one of those generic one click apps.
No stock or custom roms available any where that I have found from searches here and there over the last few years
I tried to follow a tutorial to port an MT6577 rom but I would need the kernel off the phone, which can't be done to my limited knowledge.
No custom recoveries available, running Android System Recovery 3e. Can't use TWRP MTK 1 click install on my PC because the device needs to be fully booted to work.
The good?:
Fastboot seems to work as it does show the device in the command prompt "fastboot devices"
I think the bootloader was unlocked at some point, no idea on the relevance of that.
Any information on if/how to sort it out is greatly appreciated.
Last ditch effort to try revive it because it was decently usable for what it is, hoping that someone on here has one lying around somewhere.
Will add more information as I remember and reply to any responses asap
Thanks for your time
Hello have you tried a hard reset so far ?
-Hope- said:
Hello have you tried a hard reset so far ?
Click to expand...
Click to collapse
I have, through the recovery "Wipe cache partition" and "Wipe data/factory reset" have been done a few times as I've tried different ways to try and fix it
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
-Hope- said:
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
Click to expand...
Click to collapse
Good news: Tired it
Bad news: Nothing happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also tried "getvar all" which according to a post on a xiaomi forum, is an MTK specific command, returned nothing anyway.
Just showed the "..." until I pulled the USB cable out.
Thanks for the suggestion, guess that's a pretty significant strike against any kind of fix for it.
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
-Hope- said:
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
Click to expand...
Click to collapse
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the whole system.img unless you have TWRP or can sideload apps in the recovery that you have.
Sent from my SM-S903VL using Tapatalk
-Hope- said:
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
Click to expand...
Click to collapse
Thank you for finding this, much closer than anything I've ever found. From what I can see on it, it's really close spec wise. I'll download it and have a look through the files before trying it.
Droidriven said:
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the while system.img.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did try that. I have all kinds of zips that could supposedly be flashed with the stock roboto font as well as the file itself ofcourse but I could never get fast boot to so anything with it. Based solely off the assumption that all android devices use it as the default, and assuming that the app was just renaming custom fonts to Roboto or something along those lines.
During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
UPDATE: We now have enough people to really get the ball rolling for some development for this phone, so as we accomplish more things we'll post them here
Anything you try from here, you do so at your own risk. This may void your warranty, break your device, etc.
HOW TO UNLOCK THE BOOTLOADER
Go to Settings>About Phone>Build Number and tap this a lot really fast to enable developer mode
Go to the new developer mode option in the Settings menu, check the switch that says Allow OEM Unlock
Plug your phone into your computer, enable ADB Debugging, open up a terminal on your computer, and initiate an "adb reboot fastboot" to put the device into fastboot mode
In your computer terminal again, type in "fastboot oem unlock". If it fails, run it again. If it fails again, reboot to fastboot one more time and try a couple more times. Eventually it should work after a couple tries, it did for us
Confirm the device unlock on the phone (pressing volume up at the prompt I believe), and wait for the phone to reboot. Note that it's not stuck in a bootloop at this point, it's just factory resetting after the unlock, so give it time to work
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 1
Pull a recovery image from the phone with SPFT using a proper mtk6739 scatter file which I can't exactly find
Port TWRP to the phone from another device's mtk6739 TWRP image with carliv image kitchen tool, and flash it back to the phone with SPFT
Flash Magisk in TWRP, reboot, profit
HOW WE WANT TO ROOT IT (NOT DONE YET): METHOD 2
Pull a boot image with SPFT
Use the Magisk APK to inject magisk into the boot image
Flash the boot image back with SPFT (or maybe fastboot), reboot, profit
HOW TO FLASH TWRP TO THE PHONE (STILL EXPERIMENTAL)
Download the TWRP image from here
Reboot to the bootloader
Assuming you unlocked the bootloader from before, just do "fastboot flash recovery [imagename]" to get it on there
If fastboot complains about it not being able to flash, try running the command one more time
CUSTOM ROMS FOR THIS PHONE
This phone came with 8.1 Oreo, so that means it has to be Treble enabled. I'm no expert with Treble stuff but I believe GSIs made for arm a-only partitions SHOULD work on here. We haven't tested this for ourselves yet though
Like mentioned before, feel free to drop by and leave a message if you're willing to help us out on our endeavors. I also want to try and get 'Thew a working recovery on his phone again if possible, since for some reason when we try to flash back the image we pulled (with our "best guess" mt6739 scatter file) it didn't work
i might have one.. i will check as soon as i get to the shop
jasonmerc said:
During our quest to gain root on the ANS UL40, @Matthew702 and I went a bit off topic and started messing with his Vortex Synq he picked up. 'Thew was able to find a method to unlock the bootloader, which I will post here shortly, and we shortly thereafter found out that the device is "vulnerable" to using SPFT--as in the VCOM port stays open and allows us to read/write partition images directly from the emmc.
Unfortunately during our testing, he seems to have messed up his recovery image and is unable to restore a stock one on there. If there's any other owners out there willing to help us out (and maybe willing to risk their device for some test builds of TWRP too) I beseech thee to make yourself known.
Click to expand...
Click to collapse
i have one .. if you need
desbloqueokings said:
i have one .. if you need
Click to expand...
Click to collapse
Check your PMs on here, just sent you something
So the other 6739 scatter files we found didn't exactly work for this phone, so we pulled our own with a tool we found on Hovatek. This isn't a "port" from another phone, this directly came from the Synq itself.
Give major thanks to @desbloqueokings for pulling this for us!
The group we had seems a bit inactive now, so I'll post my new creations up here for all you guys here to test and tell us all if it works or not. One is a patched boot image that contains Magisk, all you'd need to do for that is flash the boot image and install a Magisk APK and you should be good to go for root. The other is a dirty port of TWRP Recovery I did from another MT6739 phone. It was hard finding an image to port from, so I want to give a huge thanks to @lopestom who sent me a 6739 image he had that I could port from
PLEASE BE AWARE THAT THESE ARE TEST IMAGES. I DONT HAVE THIS PHONE MYSELF AND CANT TEST IT MYSELF, SO IM NOT SURE IF THESE WILL WORK OR NOT. PLEASE MAKE A BACKUP OF YOUR CURRENT BOOT & RECOVERY IMAGES WITH SPFT USING THE SCATTER FILE ABOVE BEFORE TRYING ANY OF THIS. WHAT YOU DO TO YOUR OWN PHONE IS YOUR OWN RESPONSIBILITY. WHILE I WILL TRY TO HELP YOU IF SOMETHING BREAKS, IM NOT RESPONSIBLE FOR WHAT YOU CHOOSE TO DO
With that being said, here's the Mega folder containing the boot and recovery images. You can either flash these through SPFT like most people do with mediatek phones, or through fastboot, whatever you can get working. I'd also recommend you unlock your bootloader using the method posted above before doing any of this
Let me know if this stuff works or not, if you choose to flash it
Our victory was bittersweet, but a victory nonetheless
We got a working recovery image from @lopestom that seems to work fine on the surface, but when we need to flash the zip that disables dm-verity (disables force encryption) it supposedly breaks the /system partition on the stock ROM. My recommendation would be to take a backup of your /system directory in recovery before trying to flash anything. But since this is a Treble-enabled device, that means GSI ROMs could also work when flashed.
Here's a link to the recovery image we were using. We flashed it in fastboot with an unlocked bootloader but I imagine it would work just fine in SPFT too. I was told by the person that made the image that it's apparently not a good idea to flash the disable-force-encryption zip on a dirty port of a TWRP image like this (and to also never wipe /data). While you should be able to use this TWRP to flash something like Magisk, don't do those other two things for now.
Here's some screenshots from @Matthew702 to show the phone booting to TWRP (we made the mistake of trying to wipe /data and trying to flash the disable-encryption zip, please do not do this):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you!
You guys are amazing.
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx
xAlimorAx said:
I had a SYNQ just laying around taking up space. Now it is not totally useless. Anyway i wanted to say thanks and post some proof of concept.
Sorry for the horrible quality...
So i used the recovery image named “recoverytest3.img” if im not mistaken. Once that was complete (And i figured i messed everything up because i had a dead android guy every other time....) To my surprise TWRP popped up in russian. At that point i installed magisk manager and downloaded the most recent package then rebooted to recovery and flashed the pack.
NOTES - I did use Command line WIN 10 via the platform tools package your provided for the whole process.... If you don’t know russian or whatever lang TWRP happens to be in just good. Anyway im sure im missing some data i should add but i am dog tired and having trouble reading the phone.
night all and i hope it all goes well for everyone else.
xAlimorAx
Click to expand...
Click to collapse
Yeah it showed up in Russian for our tester too. Not sure why it does that, but otherwise it should still work fine
Need your assistance
Season greetings to you my friend, I ended up formatting my vortex synq using Sp flash tool, after attempting to root, now I have black screen only vcom for sp flash tool works but I need preloaded files and others to unbrick, it was gonna be a Xmas gift for my aunt, but I messed it up, wont turn on just vcom when connected to PC, I have the files stckboot and recovery but sp tool needs pre-loader error, plz help me
Please back up vortex synq
Good I ask for a help to see if someone will have or could make a back up for this vortex synq cell phone since some of us have problems in the firmware when modifying it and we do not have a previous backup if someone can collaborate, it would be infinitely appreciated.
I know this post is old but if somebody can backup the firmware from this it would be awesome, because i am trying to restore my vortex snyq (its hard bricked) but i can't find the preloader for this phone anywhere, when i tried to flash the preloader with sp flash tool it gives me this: STATUS_DA_HASH_MISMATCH, the preloader has to match this phone, if anyone has a backup of the firmware feel free to post it here or dm me, but yeah just wanted to post here.
also need firmware having the same issue ages now
any help much appreciated
safe 2021-2022
use this to unlock bootloader and backup fw https://github.com/bkerler/mtkclient
Making this post to do a dump of the Vortex Synq stuff I had on Mega. XDA allows us to upload large files to here now, and my Mega account is getting pretty full, so I want to transfer everything I have that's Vortex Synq related from there to here. That means any download links pointing to my Mega will be broken, but all of that stuff previously linked by me can be found in this zip.
disclaimer
Feel free to use any of my stuff in any way you see fit. The only thing I ask is that if you do improve on something, share it with everyone else and don't just keep it for yourself. Keep it going for the good of the community/public.
Also, know that it's been a long time since I've messed with this phone, so I don't remember what mods/images/etc in my Mega repo are functional or not. Anything contained within this zip, FLASH AT YOUR OWN RISK.
/disclaimer
Hi everyone,
Recently I purchased and Samsung A11. I wanted to root it and unlocked the bootloader first. Than I used Odin to install TRWP recovery. Odin showed "PASS" and I was supposed to press certain buttons which didn't work. Phone kept coming back to "Download Mode" although I pressed those buttons. So I was stuck. The only option was to cancel the download mode, so I pressed volume down + power button for more than 7 seconds. That was the end Now the phone turns on until I see the Samsung logo, there's a small vibration but it can't go forward. It resets back and now stuck in a loop. None of the buttons work including Volume Down+Power combination. Don't know what I am supposed to do now. Can anybody help?
Thanks...
1. Add Samsung A11 to this thread's title thus mainly owners of such a phone get addressed
2. My recommendation: Re-flash STOCK ROM to get rid off of all mods you applied.
jwoegerbauer said:
Re-flash STOCK ROM to get rid off of all mods you applied.
Click to expand...
Click to collapse
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
gokund said:
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
Click to expand...
Click to collapse
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
jwoegerbauer said:
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
Click to expand...
Click to collapse
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
gokund said:
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
Click to expand...
Click to collapse
it wouldn't ... usually the cause of bootloop is certain corrupted partition and as long as that partition is corrupted it would keep bootlooping.
if you doesn't know what your doing your best bet is Take it to authorized service center and let them fix it. like what @jwoubeir said
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
sammiev said:
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
Click to expand...
Click to collapse
great tip work on ADB too anyway OP is provably using sp flashtool since his phone is samsung so this method would be rather tricky
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told and I tried flashing another TRWP file thinking that might have caused the problem but nothing has changed. Same loop again ! So I flashed the original ROM back using Odin and it's back live again Thanks for the help guys. But to be honest, I am still curious. What might be the problem in not getting TRWP flashing going right?
gokund said:
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told
Click to expand...
Click to collapse
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
sammiev said:
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
Click to expand...
Click to collapse
I tried again from scratch with a new TRWP file and the result is the same. Odin shows "PASS" but the "Download Mode" screen gives the error as in the photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone model is A115F and I downloaded the TRWP file from this link:
Downloads for : Samsung Galaxy A11 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
The version I used is "twrp-3.5.0_10-3_afaneh92-a11q.tar"
I also tried rooting with Magisk without the need of TRWP installation. That was also unsuccesfull. Odin was PASS but I got bootloader screen saying Secure Check Fail : vbmeta
Here's the screenshot of Magisk fail in "Download Mode"
Can't figure out what's wrong ...
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Deleted
sammiev said:
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Click to expand...
Click to collapse
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
gokund said:
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
Click to expand...
Click to collapse
Usually the latest TWRP with the latest firmware.
Check my profile, your KG stated is ****ed. There is nothing you can do about it, there is abosulutly no way to fix this without unsoldering the eMMC and resetting it entirely. Some people on 4PDA had the same problem and found no fix. I was hopping to develop a custom rom but I cant as my kg state is prenormal. This mexican dude on youtube fixes devices with KG and FRP issues, but yeah this aint something that you can do at home. At least I learned not to buy any samsung devices in the future https://www.youtube.com/c/TeamOcmineMMCBootRepair
edit: nvm your oem is unlocked, you can just flash the vbmeta reset script via odia and everything should flash fine.
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
Can you send a screenshot of the bootloader screen?
Kenora_I said:
Can you send a screenshot of the bootloader screen?
Click to expand...
Click to collapse
I'm guessing you mean the Download screen..?
Here's the Download screen if so:
https://imgur.com/pxu0hsS
FlooferLand said:
I've been trying to install TWRP on my phone for about 3 weeks straight now and i keep running into this exact same issue.
Basically, every time I try to flash anything other than a stock ROM the flash fails and i get "Only official released binaries are allowed to be flashed(RECOVERY)" on my phone's Download screen. (Here's an pic of Odin when the flash fails)
I've tried flashing the latest carrier-unlocked stock ROM to it, and using the phone for 2 week without rebooting (was constantly connected to the internet, uptime was around 300 hours before i attempted to flash TWRP again). I've also tried some solutions I've found on the XDA forums (like flashing the nougat bootloader to my phone, and changing back the time by a month) but nothing appears to work.
I also got the phone used if that's any useful info.
The "OEM Unlock" option was also enabled for some reason after enabling Developer Options. And i also made the mistake of resetting the phone via the recovery menu since i didn't know the previous owner's Samsung account password to remove it from the phone (I'm guessing that's the thing that initially triggered it?)
The phone is also from Spain (but i flashed a stock ROM from my country so it should be fine?) and i have a SIM inserted into it if it's relevant.
I also very much don't care if KNOX trips or not. I don't plan on using any Samsung-made apps ever again since I wanna install a FOSS (free and open-source) ROM to my phone and I don't plan to *ever* sell this phone either.
HUGE thank yous to anyone who finds a solution
Click to expand...
Click to collapse
You did run fastboot OEM unlock?
or
fastboot flashing unlock
Kenora_I said:
You did run fastboot OEM unlock?
or
fastboot flashing unlock
Click to expand...
Click to collapse
I don't think my phone even has fastboot
I tried booting it into recovery and selecting to apply an update with ADB, I've also tried it at the "Waiting for update" screen.
Fastboot just gets stuck saying < waiting for any device >
The OEM unlock checkbox is already checked in Developer Options.
I don't think the S8+ needs another way to enable OEM unlock other than the checkbox in Developer Options.
EDIT: Here's the output of adb logcat --regex rmm after booting into Android if that's helpful(?) (I have no idea how to use Logcat):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly
Kenora_I said:
you did install fastboot drivers? Sometimes if you connect with a usb 3.0 port it dosent work properly
Click to expand...
Click to collapse
I've seen a lot of people say the S8+ doesn't have fastboot, there's also no "Reboot to fastboot" option in the recovery menu
Apparently Samsung's RMM server (https://rmm.samsung.com/) appears to be dead (SSL certificate expired and the entire server seems to not work)
So i'm wondering if there's a way to actually spoof the data the server sends, basically blocking Samsung's server and making my own DNS that resolves to my own server sending it's own data.
My problem then is, how would i even know what data my server is supposed to send? And would that even be possible?
I'm very much out of ideas XD
I also found this post (and i have a continuation file for my own phone so in theory it should work?) but it requires the use of iRoot and some proprietary sketchy Windows program. And iRoot and all of these one-click root apps have been known for injecting malware system-level into devices.
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Nice work! tbh I'd never think of that lol,
FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse
FlooferLand said:
FIXED IT!!
The time trick actually worked.
All i had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!
Click to expand...
Click to collapse
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
The same goes. I have tried everything, and it seems that the post here suggests that we now entirely depend on Samsung to get the site certificate sorted out
Link pasted here for those who don't trust shortened links: https://forum.xda-developers.com/t/...d-expired-certificate-whats-next-lol.4403393/
JuanMat97 said:
The same problem, i tried everything, chImera, date, nothing works. Please help me @FlooferLand !
Click to expand...
Click to collapse
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.
FlooferLand said:
I very much have no clue how it worked for me XD
It's very much possible, you just have to continously try.
I've heard rumors that if you have a Snapdragon chip instead of an Exynos, the RMM is doomed to lock until Samsung resolves their issue. But idk anything about that so i can't really confirm it XD.
I would recommend upgrading to Android 9 and doing the thing i said tho, that worked for me.
Also make sure that your ROM is from the country your SIM card is from, very important.
My phone was originally from Spain, and having a ROM that was made in Spain seemed to caused the RMM to continuously trip out since my SIM wasn't from Spain, so it essentially detected my phone as stolen or smth. You can find official ROMs on something like SamFW.
If this still doesn't work, try waiting 7 days again, then doing the thing i said.
Click to expand...
Click to collapse
friend please, could you say, step by step and in an orderly manner what you did? for example when you said "The time trick actually worked.
All i had to do was turn back the time by like a year" 1-¿have you done that after a flash, a hard reset, or just rebooted without deleting anything?, and also when you said "reboot, enter recovery mode" 2-¿what you did was restart directly to recovery, or restart the system and then restart it again to recovery? and lastly in the part where you said "re-enable OEM unlock, spam the update phone button" 3-¿"re-enable", if you said "re" it means that before reactivating it you already had it activated, right? 4-¿"spam button" by that you mean pressing many times, but, did you have the automatic updates box enabled or not, and... how many times did you touch the update button? thanks in advance, I would appreciate if you answer the 4 questions
which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass
which ROM were you using when you did theses steps to unlock? I've tried the 168hs+ method almost now and it didn't worked, then I found your post and tried doing this method changing the date and rebooting cleaning the partition but until now I couldn't achieve it, can you help me pleass
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99% sure the methods will work for any mediatek version of this phone just make sure to use your correct firmware
the tools included will allow you to :
Enable OEM Unlock +Unlock the Bootloader
Create Scatter Firmware
Unbrick your device if stuck in Brom/Da mode
Root Your Device / Install TWRP
Enter Brom Mode
and more
All instructions are included inside the main folder of tools, seriously... and i mean seriously...please read the 3 or 4 different guides/methods to see which ones you actually need to do. Some are not needed depending on your end goal. I spent a month making every error possible and testing things so you dont have to so save yourself the trouble and read through
Ill do my best to answer any questions or issues you might have but please...please use your eyeballs and google.. i really dont want to have to answer questions like "how flash magisk" etc. Google is there.. it is your friend , use it. XD
A12 Toolkit.zip | by Privyetcyka for Galaxy A12 Nacho
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Thank you, I hope I can figure it out with the translator, I went to try ..
fackstrot said:
Thank you, I hope I can figure it out with the translator, I went to try ..
Click to expand...
Click to collapse
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you
PrivyetCyka said:
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you
Click to expand...
Click to collapse
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware
fackstrot said:
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware
Click to expand...
Click to collapse
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included
PrivyetCyka said:
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included
Click to expand...
Click to collapse
I followed the steps, I was inattentive myself) but still ran into a problem
when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error
well, if I put it from SM-A125W, then the rollback error
Will that work for the Samsung Galaxy A13
Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.
Ansemseekerofdarkness said:
Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.
Click to expand...
Click to collapse
I have no idea which directions your directions your talking about the only ones I wrote are the ones in the main folder , probably with a bunch of exclamations. I can't remember and don't have the file with me right now but as far as unlocking the bootloader you just need to get the phone to accept different firmware. Try flashing Sm-a125w Canadian version XAS
fackstrot said:
when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
Click to expand...
Click to collapse
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included
PrivyetCyka said:
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included
Click to expand...
Click to collapse
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center
fackstrot said:
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center
Click to expand...
Click to collapse
Nothing is supposed to happen if nothing happens that is good . Just leave the phone connected how it is and use a mediatek unlocking tool
When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!
ronnieshane1 said:
When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!
Click to expand...
Click to collapse
Change date to 25 may 2022 to get working
Ok... im trying to repair mi phone and failed i follow exactly as i seen in the readme instructions on the unbrick folder and nothing... i got 2 errors in relation of super.img (im trying to flash the last android 11 firmware on the phone A125MUBS3BVF1) if i uncheck the super the phone flash correctly but doesn't boot so what next...?
fackstrot said:
Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error View attachment 5664401
Click to expand...
Click to collapse
And now i had this error i think using the format all + download relocks the bootloader sp flash tool is asking me to download signed images i can't exit from that so i give up and buy another mainboard
My last reply...
I uploaded some images to get BROM working on A125M this zip includes
Preloader and PGPT files from 4 firmwares
Android 10 Binary 1 (AUC1)
Android 11 Binary 1 (BUF9)
Android 11 Binary 3 (BVF1)
Android 12 Binary 3 (CVH3)
Plus i will modify this post because im uploading CVH3 firmware for SP Flash tool flash (Includes the scatter) pls disable the auth using mtkmeta or the python coded program (used 3.7.9 and worked using the shell)
PGPT and Preloader images