Related
I've tried the official unlock and it says can't verify. I tried every tutorial to get around that, activated SIM, going on i.mi.com, etc. I even contacted support US, Hong Kong support, and India support and they all gave me the same garbage auto replies.
I've tried unofficial unlock (2 different methods I believe) and none of them worked. I'm losing my mind.
Does anyone know if there's a different or updated method for Kate? Last time I tried to unlock was 2.5 weeks ago
Somewhere along the line of flashing fastboot roms my network started bugging out. It constantly connects and disconnects, and there's no LTE. I don't think I've ever loaded a bad rom so I don't know how this happened but I think I can troubleshoot that if I can at least get a custom recovery on this stupid thing.
Thanks in advance
I had problems at first too.i flashed global beta thru updater on phone.went to dev options then mi unlock status and linked phone to my account.unlocked first try after that.
marcukial said:
I had problems at first too.i flashed global beta thru updater on phone.went to dev options then mi unlock status and linked phone to my account.unlocked first try after that.
Click to expand...
Click to collapse
By Global beta do you mean global dev?
I'll give it another try
I just gave up and used this method: https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
You might need to flash an older version of MIUI. I think I used 6.11.3 - currently running Resurrection Remix 5.8.0 with Radon Kernel with locked Bootloader without a problem (well, other than the typical Nougat bugs)
Endzeitkind said:
I just gave up and used this method: https://forum.xda-developers.com/redmi-note-3/how-to/method-to-flash-twrp-recovery-unlock-t3473294
You might need to flash an older version of MIUI. I think I used 6.11.3 - currently running Resurrection Remix 5.8.0 with Radon Kernel with locked Bootloader without a problem (well, other than the typical Nougat bugs)
Click to expand...
Click to collapse
I found a 6.11.3 fastboot rom but when going to flash it says it cant find flash_all_except_storage.bat. And I looked that up and apparently it means it's not a fastboot rom, which is false because the other roms ive flashed didnt hvae storage.bat either.
Mi PCsuite also isnt pulling up the phone in recovery mode so that's useless.
Im about to throw this phone in the garbage honestly. Ive tried just about everything.
I tried the method you mentioned about replacing the recovery image but it didnt work at all
EDIT: Found another rom that works with the updater, but it gave me an error saying its an older version of MIUI. seriously this is pretty ridiculous
rasheemo said:
I've tried the official unlock and it says can't verify. I tried every tutorial to get around that, activated SIM, going on i.mi.com, etc. I even contacted support US, Hong Kong support, and India support and they all gave me the same garbage auto replies.
I've tried unofficial unlock (2 different methods I believe) and none of them worked. I'm losing my mind.
Does anyone know if there's a different or updated method for Kate? Last time I tried to unlock was 2.5 weeks ago
Somewhere along the line of flashing fastboot roms my network started bugging out. It constantly connects and disconnects, and there's no LTE. I don't think I've ever loaded a bad rom so I don't know how this happened but I think I can troubleshoot that if I can at least get a custom recovery on this stupid thing.
Thanks in advance
Click to expand...
Click to collapse
follow this thread.
http://xiaomitips.com/guide/unlock-redmi-note-3-bootloader-without-official-permission/
I have unlocked bootloaders of my 2 phones (1 kenzo, 1 kate), in process of unlocking I was getting error while flashing it was giving me the error of "no system storage" (Not remembered whole message).
when that error occurs to me I got stucked on bootloop then I get jumped directly to "step 18" in both device's unlocking.
in the end I was done an additional step which was about to flash recovery through fastboot.
To flash TWRP recovery through fastboot
just execute the below command if you get your unlocked you device bootloader.
"fastboot flash recovery filename.img"
then just get into recovery mode and flash your desired custom rom.
I have follwed same procedure twice and it worked for me, hope so that it'll help you.
Best Of Luck.
https://forum.xda-developers.com/redmi-note-3/how-to/bootloader-unlock-snapdragon-t3530395
follow this.
OK. I'm running the Moto Z unlocked 64GB version. Everything is stock. I unlocked the bootloader, and then flashed a custom logo to get rid of the "Unlocked bootloader" warning screen. Now the phone will not get past the new logo that I flashed. What can I do? I can get into fastboot or recovery, or boot twrp from fastboot(stock recovery still installed)
How can I get my phone to boot? Even if I have to live with the unlocked bootloader warning I'm cool with that. Please help!
Willing to pay $20 paypal or google wallet to anyone that can help me get my phone back working....
SixShots said:
OK. I'm running the Moto Z unlocked 64GB version. Everything is stock. I unlocked the bootloader, and then flashed a custom logo to get rid of the "Unlocked bootloader" warning screen. Now the phone will not get past the new logo that I flashed. What can I do? I can get into fastboot or recovery, or boot twrp from fastboot(stock recovery still installed)
How can I get my phone to boot? Even if I have to live with the unlocked bootloader warning I'm cool with that. Please help!
Click to expand...
Click to collapse
You should be fine, I'm assuming you flashed that boot logo without installing a custom kernel to disable force encryption and here's how I flashed stock when i did something similar.
This is exactly what I did from a bricked phone. I got a strange "error" message after flashing this that looks like the no command error, but after holding power it rebooted to Nougat.
Using Minimal adb and Fastboot:
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash system system.img_sparsechunk.13
fastboot flash system system.img_sparsechunk.14
fastboot flash system system.img_sparsechunk.15
fastboot flash system system.img_sparsechunk.16
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Hope this helps!
I used the Mexican Nougat firmware from here, I'm on 32GB UK model though. https://firmware.center/firmware/Motorola/Moto Z/Stock/XT1650-03/
Just don't flash a MM one if you're coming from Nougat, that will not work. And remember to check the number of system chunks it may not be 16 for whichever firmware you use.
I'm currently downloading the stock MM firmware in hopes that it helps, gotta love living in the middle of nowhere with a 3mb DSL connection :-\
So basically I can't flash a logo unless I flash the kernal first?
Secondly, With this stock MM that i'm downloading, once I flash all of it using fastboot it should be back to stock completely except still have the "Bootloader unlocked" warning, yea?
SixShots said:
I'm currently downloading the stock MM firmware in hopes that it helps, gotta love living in the middle of nowhere with a 3mb DSL connection :-\
So basically I can't flash a logo unless I flash the kernal first?
Secondly, With this stock MM that i'm downloading, once I flash all of it using fastboot it should be back to stock completely except still have the "Bootloader unlocked" warning, yea?
Click to expand...
Click to collapse
Okay so you haven't ever been on Nougat? Just making sure because when you OTA to Nougat there's no way back.
I think so, to be honest I only changed the boot logo after I flashed LineageOS so I'm not sure.. but you need to disable forced encryption by flashing custom kernel to modify system files without it getting stuck booting up. I went through this myself when i first unlocked it, this is what fixed it for me. Good luck!
Yup it should be back to stock but still unlocked bootloader.
supacrazyguy42 said:
Okay so you haven't ever been on Nougat? Just making sure because when you OTA to Nougat there's no way back.
I think so, to be honest I only changed the boot logo after I flashed LineageOS so I'm not sure.. but you need to disable forced encryption by flashing custom kernel to modify system files without it getting stuck booting up. I went through this myself when i first unlocked it, this is what fixed it for me. Good luck!
Yup it should be back to stock but still unlocked bootloader.
Click to expand...
Click to collapse
No I'm on Nougat now, But when I tried to flash one of the Nougat zip's from the post above it stated that I needed to have either 6.0* something OR 7.* something. Which made me think I could flash the 6.0 as an OTA, is that wrong?
I have the XT1650-03, which version of Nougat should I be pulling from that post? The one I got was obviously the wrong one :-\
SixShots said:
No I'm on Nougat now, But when I tried to flash one of the Nougat zip's from the post above it stated that I needed to have either 6.0* something OR 7.* something. Which made me think I could flash the 6.0 as an OTA, is that wrong?
I have the XT1650-03, which version of Nougat should I be pulling from that post? The one I got was obviously the wrong one :-\
Click to expand...
Click to collapse
Okay if you've updated to Nougat there's no way a MM firmware will work, thanks to Moto updating the bootloader making it incompatible. Where was the message that said you needed something? Did you unzip the file and flash each chunk in fastboot?
I think Rogers was a good option, i also have XT1650-03. Maybe try the Retmx like i did.
supacrazyguy42 said:
Okay if you've updated to Nougat there's no way a MM firmware will work, thanks to Moto updating the bootloader making it incompatible. Where was the message that said you needed something? Did you unzip the file and flash each chunk in fastboot?
I think Rogers was a good option, i also have XT1650-03. Maybe try the Retmx like i did.
Click to expand...
Click to collapse
Well... I was able to download and flash the entire ROGERS version, My phone will boot to the Cyan M logo screen and then instead of the animation "ring ring hello moto" the screen just goes black. Eventually it connects to my computer but I can't find a way to turn the screen on or do anything. Downloading the RETLA version to see if that works since I'm pretty sure that was what was on the phone to begin with... *sigh*
SixShots said:
Well... I was able to download and flash the entire ROGERS version, My phone will boot to the Cyan M logo screen and then instead of the animation "ring ring hello moto" the screen just goes black. Eventually it connects to my computer but I can't find a way to turn the screen on or do anything. Downloading the RETLA version to see if that works since I'm pretty sure that was what was on the phone to begin with... *sigh*
Click to expand...
Click to collapse
Ah I don't know why that is, as i said I'm at sure what's best for your model sorry. The easy flash to Nougat guide link i sent you may be better, but yeah if you know it came with RETLA then give that one a try :good:
I think your best bet is to try that RETLA firmware.
I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat. It's slightly older than the TELUS build that's newer and comes with some bug fixes, including one that resolves an issue where the 2 HP CPU cores "park" after some time of use, although I've heard of some issues when using that build with some devices. Mine's a bit iffy, but otherwise seems to run quite nicely.
Once flashed, if you wanna flash system mods, do not boot just yet. Flash or boot into TWRP and try the following kernel
https://forum.xda-developers.com/moto-z/development/kernel-turbo-z-custom-kernel-moto-z-t3493354
This disables forced-encryption and dm-verity (the latter is what's responsible for your phone refusing to boot). Additionally, you can flash SuperSU using the following method.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
D13H4RD2L1V3 said:
I think your best bet is to try that RETLA firmware.
I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat. It's slightly older than the TELUS build that's newer and comes with some bug fixes, including one that resolves an issue where the 2 HP CPU cores "park" after some time of use, although I've heard of some issues when using that build with some devices. Mine's a bit iffy, but otherwise seems to run quite nicely.
Once flashed, if you wanna flash system mods, do not boot just yet. Flash or boot into TWRP and try the following kernel
https://forum.xda-developers.com/moto-z/development/kernel-turbo-z-custom-kernel-moto-z-t3493354
This disables forced-encryption and dm-verity (the latter is what's responsible for your phone refusing to boot). Additionally, you can flash SuperSU using the following method.
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113
Click to expand...
Click to collapse
At this point i'm just trying to get my phone to boot lol. I wish I had read more to begin with... Knowing that unlocking the bootloader now breaks the safety net for Android Pay(it didn't with Moto X) is making me worry that it will also cause my Wells Fargo Mobile app to not work. At which point I might as well not even have the phone.
As of now I am able to flash the RETLA version but once I get past the Cyan M logo screen the screen goes blank and does not turn on even though my computer is recognizing that it's there. I'm about to try flashing the RSD rogers MM firmware(without the gpt and bootloader commands) and then sideloading Nougat to see if that gets me anywhere. If i can get it to boot normally I can at least sell it(at a loss) and buy another one. But I need it to at least boot up that way I don't have to sell it for 100 bucks lol. Any other ideas are welcome but I feel like i stepped in quicksand and the more I struggle with it the worse it's getting.
SixShots said:
At this point i'm just trying to get my phone to boot lol. I wish I had read more to begin with... Knowing that unlocking the bootloader now breaks the safety net for Android Pay(it didn't with Moto X) is making me worry that it will also cause my Wells Fargo Mobile app to not work. At which point I might as well not even have the phone.
As of now I am able to flash the RETLA version but once I get past the Cyan M logo screen the screen goes blank and does not turn on even though my computer is recognizing that it's there. I'm about to try flashing the RSD rogers MM firmware(without the gpt and bootloader commands) and then sideloading Nougat to see if that gets me anywhere. If i can get it to boot normally I can at least sell it(at a loss) and buy another one. But I need it to at least boot up that way I don't have to sell it for 100 bucks lol. Any other ideas are welcome but I feel like i stepped in quicksand and the more I struggle with it the worse it's getting.
Click to expand...
Click to collapse
Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat.
An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break.
Also, Magisk can help with SafetyNet, though it needs root access.
D13H4RD2L1V3 said:
Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat.
An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break.
Also, Magisk can help with SafetyNet, though it needs root access.
Click to expand...
Click to collapse
My issue with that is I can't figure out which firmware was made for my device. I thought it was the RETLA version but apparently I was wrong. Is there any way to figure out which one i need? I have all of the info from my getvar command in fastboot but it's not giving me any info(that i understand) that will point me in the direction of the correct firmware.
I'm currently downloading the rogers MM firmware to see if i can flash back to MM and then sideload nougat but I don't know if that's going to do any good considering that the screen won't load right now with the Nougat firmware I have on it.
SixShots said:
My issue with that is I can't figure out which firmware was made for my device. I thought it was the RETLA version but apparently I was wrong. Is there any way to figure out which one i need? I have all of the info from my getvar command in fastboot but it's not giving me any info(that i understand) that will point me in the direction of the correct firmware.
I'm currently downloading the rogers MM firmware to see if i can flash back to MM and then sideload nougat but I don't know if that's going to do any good considering that the screen won't load right now with the Nougat firmware I have on it.
Click to expand...
Click to collapse
Try RETUS if it fails?
I'm crossing my fingers hoping that the ROGERS firmware can help.
D13H4RD2L1V3 said:
Try RETUS if it fails?
I'm crossing my fingers hoping that the ROGERS firmware can help.
Click to expand...
Click to collapse
You mean the RETUS 6.0 firmware? And basically go through the same thing as the ROGERS firmware (flash mm without GPT and bootloader) and then try to upgrade? I haven't been able to find a RETUS 7.0 firmware anywhere yet so I assume that's what you mean...
SixShots said:
You mean the RETUS 6.0 firmware? And basically go through the same thing as the ROGERS firmware (flash mm without GPT and bootloader) and then try to upgrade? I haven't been able to find a RETUS 7.0 firmware anywhere yet so I assume that's what you mean...
Click to expand...
Click to collapse
Yeah.
Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine.
I'm still crossing my fingers in the hopes that your Z will make it through.
D13H4RD2L1V3 said:
Yeah.
Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine.
I'm still crossing my fingers in the hopes that your Z will make it through.
Click to expand...
Click to collapse
Well... to be honest the only reason I wasn't planning on rooting or using a custom ROM was because of the whole not working with android pay/wells fargo deal. If Magisk will help with that then that's definitely an option as well... Especially right now considering that I can't get ANYTHING to work if i can root, install a stock ROM and use magisk to hide the safetynet I'm totally fine with that as well. Any ideas?
SixShots said:
Well... to be honest the only reason I wasn't planning on rooting or using a custom ROM was because of the whole not working with android pay/wells fargo deal. If Magisk will help with that then that's definitely an option as well... Especially right now considering that I can't get ANYTHING to work if i can root, install a stock ROM and use magisk to hide the safetynet I'm totally fine with that as well. Any ideas?
Click to expand...
Click to collapse
Well, to even get Magisk and root to work, you need a working firmware.
The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working.
But somehow, it's not displaying anything.
Sadly, the best piece of advice I can give right now is to try to flash a full firmware, especially one that was made for your device just to be safe. Motorola support probably won't be of much help since your warranty is void, though some did have success in the past, but I'd say that you might not get too much from them.
dm-verity is a pain, so I don't understand why it's not disabled when the bootloader is unlocked.
D13H4RD2L1V3 said:
Well, to even get Magisk and root to work, you need a working firmware.
The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working.
But somehow, it's not displaying anything.
Sadly, the best piece of advice I can give right now is to try to flash a full firmware, especially one that was made for your device just to be safe. Motorola support probably won't be of much help since your warranty is void, though some did have success in the past, but I'd say that you might not get too much from them.
dm-verity is a pain, so I don't understand why it's not disabled when the bootloader is unlocked.
Click to expand...
Click to collapse
So right now my best course of action is to start with the MM firmware and work my way forward either way. Can I root/install stock 7.0 ROM/magisk from the MM firmware even if I'm keeping the 7.0 gpt and bootloader?
SixShots said:
So right now my best course of action is to start with the MM firmware and work my way forward either way. Can I root/install stock 7.0 ROM/magisk from the MM firmware even if I'm keeping the 7.0 gpt and bootloader?
Click to expand...
Click to collapse
Well, here's the problem.
If you're on the 7.0 GPT and bootloader, you're out-of-luck. Because Moto has changed the rules on those to not accept Marshmallow-based firmware. Trying to flash a MM firmware will result in failure. Trying to downgrade the bootloader may cause your device to be F.U.B.A.R.
If you're still on the MM bootloader, just use the steps outlined earlier in the thread to flash N and then use the instructions and threads I linked to flash both the custom kernel and root access. If everything goes well, your Z should come back to life with those sweet-sweet notification shade goodness.
My mum gave me her malfunctioning SM-T820.
It's stuck in a boot loop, only showing the first logo and rebooting.
I can make it boot to a black screen by pressing Home+VolUp+Power, but not into Recovery.
Pressing Home+VolDown+Power brings up Donwload mode.
I tried flashing new firmware, but always get errors - probably because it says "OEM LOCK: ON".
Is there any way to go past this and flash any working firmware to the device?
OEM Unlocking is only for flashing custom firmware/binary. You should be able to flash stock no problem. Could you attach screenshots?
Sorry for misspelling in the username, was a dumb kid back then.
Edit: If you want, I can give you the latest BTU CTA1 firmware that I have. That might work
666anoymous666 said:
Edit: If you want, I can give you the latest BTU CTA1 firmware that I have. That might work
Click to expand...
Click to collapse
That would be great!
I already tried both stock and custom ROMs, but none worked.
Pls, Send me latest BTU CTA1 firmware plz
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...)
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
CrustyBurger33 said:
Hello,
I was installing different custom ROMS for this phone, then reverted back to Stock ROM. It updated itself, and IMEI got erased somehow.
Is there any way possible to flash a custom ROM, or even custom recovery using MSMDownloadTool? I had a global version N10, so it was sim unlocked and bootloader unlockable, and I do actually have my IMEI on the back of my box, but can't put it into my phone as I have to root it. But I can't root it because the bootloader is now locked, and the bootloader is now locked because there is no IMEI......
This leaves me locked out of fastboot, so the only option is edl, which works just fine. However, only MSMDownloadTool is compatible with this mode, and it only installs Stock ROMs.
I tried extracting the .OPS files, replacing the stock recovery with twrp (and then renaming it to recovery.img), repacking the .ops then installing it. It installs, but then never boots and is just stuck in edl mode until I reflash the normal stock rom with the stock recovery.
What Do I do?
Thanks
Click to expand...
Click to collapse
If your bootloader was relocked, encryption and partition checking were enabled again.
TWRP would only cause your phone to register as modified and lock itself...and due to streamlining of a lot of functions, you can't even use the dialer to enter the menu needed.
Best you can do is totally wipe everything on your phone and generate a new android ID. (You have to do this from the actual OS instead of recovery though. Recovery format uses predetermined instructions. The format option from the android settings panel has a different set of instructions and one of them is to generate a new android ID, which includes IMEI)
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
CrustyBurger33 said:
Thanks for the reply, although im kinda confused by your answer. How do I generate a new android ID? (what does that even mean lol). I checked in my settings and I can't find any "format option"
Click to expand...
Click to collapse
Android ID is what determines your phone is the phone it claims to be when pinging google services.
Move any files you want to keep to somewhere safe. Format your phone, android will push you a new id number. It won't fix your IMEI, but it'll keep your phone from being absolutely useless in the process.
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
ninjasinabag said:
After your phone is formated and has booted back into the OS, you can enable adb. Adb into fastboot, use fastboot to determine if your device is still bootloader unlocked using the fastboot oem device-info command
Click to expand...
Click to collapse
I tried everything you said, reset everything, still no IMEI, and even if the Android ID is different it hasn't really changed anything. Just to be clear, when I flashed the stock ROM earlier, everything worked as intended apart from the SIM card (which doesnt work at all) and the WiFi (which keeps dropping after 5 seconds of connection). Those problems persist even now.
Guess I'll be messing around with the SMT mode in MSMDownloadTool since I've already lost my IMEI, see what I can do from that. If there's anything I do actually end up finding out, I'll post it on xda.
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
CrustyBurger33 said:
Update
I installed an update by download a zip, installed update via settings. System rebooted to complete update, and somehow the oem unlock option opened!!
From this point, fixing it will be pretty straight forward I think
Thanks for your help
Click to expand...
Click to collapse
Nice! If everything is working properly besides the IMEI at this point, there's a couple of PC applications you can use.
I'd recommend write dual imei, not gonna post a link since IMEI fudging is against the rules (even if you're just trying to repair your IMEI)
Use the IMEI that's on your device sticker or on your phone packaging specifically.
Either way, hoping you get your phone back up to 100%.
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Honestly, check with OnePlus if you're under the 1 year warranty window. This sounds like an issue that can really only be fixed with a replacement device.
CrustyBurger33 said:
As it turns out, it's not easy at all. My WiFi has exactly the same issue... keeps dropping, No SIM card, no baseband version. What's crazy is that I have rooted, and even repaired the IMEI via a tool. If I read the IMEI via the tool (and different ones just to be sure), they will all show the IMEI the same as the one that I wrote (which were the original ones).
But for some reason the phone still doesnt recognize it. I reboot it. Same story. The tool recognizes, the phone doesn't. I know for a fact that the issue cannot be hardware, at least for WiFi. If it was, it wouldn't connect to any network, but it does, and then disconnects after a few seconds. I think I have been all over every post on the internet regarding this issue, but still no luck.
Click to expand...
Click to collapse
Hi I have a similar problem.. My phone oneplus 8t is stuck in 'SMT Download failed error' mode. I was tryimg out custom roms which has caused this. My phone says can only be fixed via SMT Download mode. Can you help me out using the SMT download mode? I have tried MSM Tool normally to unbrick my phone but it doesn't work.
hello @nightfury04
If you have a Oneplus 8T you have to download the appropriate MSMDownloadTool (specifically for it) and make sure the version is correct too. Is your phone global/ locked to a carrier?