My uncle bought 2 S7 from ebay to India for me.
One of them has FRP locked and the seller can't obviously give me his gmail to unlock it.
Is there anything I can do to bypass it or do I have to send it back to USA?
Aakarsh99 said:
My uncle bought 2 S7 from ebay to India for me.
One of them has FRP locked and the seller can't obviously give me his gmail to unlock it.
Is there anything I can do to bypass it or do I have to send it back to USA?
Click to expand...
Click to collapse
Flash combination firmware then flash back to stock software using home csc
kpwnApps said:
Flash combination firmware then flash back to stock software using home csc
Click to expand...
Click to collapse
am not sure if it has oem unlocking enabled :3
FRP lock on B4 and DRK Issues
I'm also encounter FRP Lock. SM-G930F
After one year of flashing and modding I have it for the first time and I don't now why. I remove every account before change room.
Before thats happend I was on TeamExyKings Note FE 9 Port
But I have missing IMEI problem and I go through standard steps
(Don't do this step if you not sure what you risk) Go to revovery and clean /efs partition
Flash combination firmware I have newest with U4 COMBINATION_FA60_G930FXXU4ASA2.zip
then Flash flash latest original firmware SM-G930F_1_20190307135001_4lzy042ysi_fac.zip
but because I have DRK Issue, after firmware boot up ang go to erasing phase then reboot and show "no command" on blue screen
When that happens I usually flash go with steps below:
flash twrp
repair data to remove encryption
no-verify zip script to bypass DRK
flash some rom and have clean working phone..
Now I've done the same but after adding Google account and syncing and app updates phone reboots and show pink words ( I don't remember what they ware)
I've red on others post that usually steps were
Flash combination
factory reset from inside and flash original firmware .
Bootloader still have FRP: ON
when try to flash twrp i have : custom binary block by frp lock
Now all its run on my phone is Custom binary with wifi without root because Kongoroot and cf-root don't work.
Can some one help me ?
jaqjacek said:
I'm also encounter FRP Lock. SM-G930F
After one year of flashing and modding I have it for the first time and I don't now why. I remove every account before change room.
Before thats happend I was on TeamExyKings Note FE 9 Port
But I have missing IMEI problem and I go through standard steps
Go to revovery and clean /efs partition
Flash combination firmware I have newest with U4 COMBINATION_FA60_G930FXXU4ASA2.zip
then Flash flash latest original firmware SM-G930F_1_20190307135001_4lzy042ysi_fac.zip
but because I have DRK Issue, after firmware boot up ang go to erasing phase then reboot and show "no command" on blue screen
When that happens I usually flash go with steps below:
flash twrp
repair data to remove encryption
no-verify zip script to bypass DRK
flash some rom and have clean working phone..
Now I've done the same but after adding Google account and syncing and app updates phone reboots and show pink words ( I don't remember what they ware)
I've red on others post that usually steps were
Flash combination
factory reset from inside and flash original firmware .
Bootloader still have FRP: ON
when try to flash twrp i have : custom binary block by frp lock
Now all its run on my phone is Custom binary with wifi without root because Kongoroot and cf-root don't work.
Can some one help me ?
Click to expand...
Click to collapse
Why'd you even think clearing EFS partition is a good idea? :/
iOrpheus06 said:
Why'd you even think clearing EFS partition is a good idea? :/
Click to expand...
Click to collapse
I know it's not good idea but if you don't have IMEI and no serial number its only way I know to have it back. Outside backup that I have but I need twrp to flash it
jaqjacek said:
I know it's not good idea but if you don't have IMEI and no serial number its only way I know to have it back. Outside backup that I have but I need twrp to flash it
Click to expand...
Click to collapse
You don't have to mess up your efs by wiping it clean just to get your IMEI back because flashing stock firmware alone is usually enough to fix IMEI issues. Posting this to prevent confusions that may lead to serious problems.
iOrpheus06 said:
You don't have to mess up your efs by wiping it clean just to get your IMEI back because flashing stock firmware alone is usually enough to fix IMEI issues. Posting this to prevent confusions that may lead to serious problems.
Click to expand...
Click to collapse
I've edited my post to avoid any more unnecessary conversation.
My IMEI problems are not not ordinary. Before FRP lock on every rom my IMEI wen't and go back according to moon cycles. Probably hardware issues.
Now please if you have any advice how to fix FRP Lock on B4 booloader from inside COMBINATION rom or from download mode i'm all ears.
jaqjacek said:
I've edited my post to avoid any more unnecessary conversation.
My IMEI problems are not not ordinary. Before FRP lock on every rom my IMEI wen't and go back according to moon cycles. Probably hardware issues.
Now please if you have any advice how to fix FRP Lock on B4 booloader from inside COMBINATION rom or from download mode i'm all ears.
Click to expand...
Click to collapse
Flashing all stock (CSC and not Home_CSC) has always worked for me from the beginning till today (last frp **** happened 3 weeks ago) and yeah my IMEI is still there.
Flashing old ROMs and flashing OLDER cp version can mess up your IMEI. That happened to me about a year ago and all I ever had to do was to flash stock rom (from whichever source you trust) via Odin.
It's the cleanest and safest way to get rid of FRP lock imo. I don't even know why anyone would bother using a combination rom as they require more effort to get your phone to work as intended.
Again, just put your phone into download mode, plug it into a PC, download stock firmware (from Sammobile, Samfirm, updato, or whichever source you trust), open Odin, and flash it there.
At least, this should work fine if you still have your efs partition working fine.
jaqjacek said:
Can you give some steps to follow ?
Click to expand...
Click to collapse
You cant repair efs without a backup. If you really deleted the efs partition no go back anymore without touching the motherboard.
And flashing firmware wont reset frp
Flashed 4 different Original firmware with CSC or HOME_CSC already.
That isn't a problem. firmware show android and erasing phase
Problem is*that after 25% Erasing ste and second reboot Phone stack on "no command" screen stays on it for a while and reboot itselfs and do the same over and over again.
I've reed somewhere thats are DRK issues I'm not a expert in this but usually i flash twrp then install no-verify zip and phone goes buck to live.
Now I have something like 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"
}
I't not a picture of my phone I don't have it on me right now but its very similar.
Thats why I flash Custom binary because its wipes everything and boots up. In other Guide from this forum I've reed that if you run factory reset from Custom binary FRP goes away buts probably samsung fix it in B4 bootloader.
I've don't want to go into /efs mangling because it is very dangerous I only write that I done it before and I'ts always works and If you do not need to do it don't
Now I need a way to skip "no command" screen or some twrp.img thats goes through FRP Lock to flash no-verify script or any magical way to boot up Original System.
Related
[HELP] Knox Warranty Void tripped while flashing official stock ROM
Hello, just bought a new Galaxy S6 with SFR France firmware. Downloaded and installed my country firmware (Romania) to get rid of SFR bloat. flashed via Odin (Knox was 0), reboot to recovery then it showed error dm-variety failed or something like that. I wiped system and cache, reboot again, waited and configured the settings and just to be sure I rebooted the phone in Odin mode and it showed Knox Warranty Void 1 (0x0400). why did that happened? Didn't try to root or install custom firmware, only official stock firmware from sammobile. anything I can do in this case?
Pray that somebody comes up with a workaround or reset (and nobody will notice it on warranty claim). Similiar thing happened to men since then I use custom ROMs.
I hope someone comes with a solution for this. I'll pay for it. Hate it because it happened to me.
What does that code stand for anyway? (0x0400) is it something like an error code or something?
really? flashing through odin up the knox?? that's new, at least to me...
hajyihia said:
really? flashing through odin up the knox?? that's new, at least to me...
Click to expand...
Click to collapse
Yes. no root, no custom ROMs/kernel/recovery. I only needed a stock official ROM with no carrier bloat whatsoever. and this is what happened.
Addix64 said:
Yes. no root, no custom ROMs/kernel/recovery. I only needed a stock official ROM with no carrier bloat whatsoever. and this is what happened.
Click to expand...
Click to collapse
there has to be something wrong, i had a galaxy S4, and i flashed many stock roms and it never upped the knox....can someone more professional explain or confirm that? because i was planning to flash a stock rom through odin to get the latest update....
hajyihia said:
there has to be something wrong, i had a galaxy S4, and i flashed many stock roms and it never upped the knox....can someone more professional explain or confirm that? because i was planning to flash a stock rom through odin to get the latest update....
Click to expand...
Click to collapse
Every time I install the stock firmware KNOX stays 0x0.
The only time I install the stock firmware is when my phone is in a bootloop.
It works every time--no issues whatsoever.
Odin should be the safest program in the world.
Snowby123 said:
Every time I install the stock firmware KNOX stays 0x0.
The only time I install the stock firmware is when my phone is in a bootloop.
It works every time--no issues whatsoever.
Odin should be the safest program in the world.
Click to expand...
Click to collapse
yeah, that's weird, did you try it on your S6? thanks
I can't post pictures yet so I can show to you. After flashing the ROM, reboot to recovery to perform system wipe..at the bottom of the screen where normally it shows applying the CSC, instead it wrote something like "dm-variety failed". Wiped, reboot to write the new firmware, check odin mode and there it was: Knox Warranty Void 1 (0x0400)
hajyihia said:
yeah, that's weird, did you try it on your S6? thanks
Click to expand...
Click to collapse
I actually own the galaxy s6 edge. I have tried it and have never once gotten a single issue.
No fix for this at all?
Sent from my SM-G920F using XDA Free mobile app
There is no fix at this moment for sure. I also flashed ROM(ania) and other stock roms and never had problems, maybe accidentally you tried to flash the carrier romania rom, not the stock one.
Anyway, there isn't anything you can do at this moment, but at least you can install some custom roms and make this phone fly.
http://www.sammobile.com/firmwares/download/54541/G920FXXU2COH2_G920FOXX2COH2_ROM/ this is the ROM I flashed. it's not my first time flashing with Odin. had the S4, Note 3 and Note 4, never had problems while flashing official stock ROMs.
{
"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"
}
Weird, i saw some people also saying that they triped knox flashing stock roms. I don't really know the technical details about s6 but my only ideea is that your SFR rom had a different partition scheme(usually carrier roms have different PIT files) and installing a stock rom which also has a different partition scheme and maybe that''s what triggered the knox. I bought mine directly unlocked from emag and i can freely flash stock roms.
Your phone was locked and then unlocked via code or you bought it directly unlocked?
Phone was locked and unlocked via code. I use it on Digi Mobil network.
Sent from my SM-G920F using XDA Free mobile app
If I flash the SFR rom back, will it do something to the knox flag?
Sent from my SM-G920F using XDA Free mobile app
No Adi, it won't. Sorry.
Sent from my SM-G920F using Tapatalk
Well..bad luck. gonna have to wait for a fix.
Addix64 said:
Well..bad luck. gonna have to wait for a fix.
Click to expand...
Click to collapse
Which will never come, since the Knox counter is an eFuse, so once it is set to 0X1, then only Samsung can set it back to 0 (probably by replacing HW or the mainboard).
Hello senior and moderators I am confused about combination File.. I install and check inside only setting and some more function any body can guide me about this and how to fix a problem in combination file..pls guide.:crying:
please answer
same problem i want to know what is the combination rom
go here
http://forum.gsmhosting.com/vbb/f891/combination-answered-2096852/
Question About Combination roms
Please,
Would I loose files and videos stored in my phone when I flash a combination rom ?
Can I have acess to them, copy them on a pc before flashing stock rom ?
Hello,
How can I select the appropriate combination files for G928F ?
For example the last is better, please can you help me (I need it for imei repair, write certs) ?
I've another question:
after have flashed a combination files and have made the work on it (for example imei repair), have we to reflash original firmware ?
Thanks
https://shell.boxwares.com
here you can find all Samsung Combination files for Free
Hello,
I need help to downgrade my S7 edge (SM-G395F) from Android 7.0 Nougat to Android 6.0.1 Marshmallow.
I try everything and always show me "SW REV. CHECK FAIL. DEVICE: 2, BINARY: 1".
Android security patch level: 1 January 2018
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: OFF
Secure Download: Enabled
WARRANTY VOID: 1 (0x030c)
RP SWREV: B: 2 K: 0 S: 0
{
"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"
}
Which "COMBINATION" file I should to use? … pls help me
-
janalam143 said:
Hello senior and moderators I am confused about combination File.. I install and check inside only setting and some more function any body can guide me about this and how to fix a problem in combination file..pls guide.:crying:
Click to expand...
Click to collapse
Hi there,
Combination files are basically used for testing purposes in the Samsung devices. These files are there to make sure that the functionality of your device is error-free before making its final release. These files are created by Samsung company and are found in only their devices.
Coming to next part, your question didn't exactly clear the problem you are having with these files? If you are missing them, you can download them by Google for free. If anything else is bothering you, do specify the proper details regarding the issue.
Thanks
Does someone know where i can get the Combination for G955FXXU3CRGH ?
Thank you!
Procedure
techeligible3322 said:
If you have combination firmware, then no need to buy any paid tool to remove frp lock, resolving issue of your device.
simple flash with COMBINATION FIRMWARE, and after that flash via STOCK ROM,
STOCK ROM: is a default firmware, that is built in by device manufacturer. that also can be downloaded from forums or by google it.
Combination ROM Advantages:
Its help you to repair imie number in some models like S7 S7 Edge S6 S6 Edge…
Its very useful in bypass samsung account in too many models.
Its very useful in bypass Google account in too many models.
Its very useful for downgrade in some models.
Its help you to enable usb debugging.
its help to remove any security FRP / Reactivation Lock from Samsung like 2016-2017
You will flash your device via Odin Software, which can be downloaded from here
Click to expand...
Click to collapse
I have the following phone that I'm trying to get FRP bypass: 6.01. (October 2016) Android Marshmallow / Galaxy S7 SM-G935V
I flashed combination ROM onto it already, so all I have to do now is flash the original stock firmware onto it to complete the FRP bypass? There's no need to make that OEM Unlock option show up?
darien217 said:
I have the following phone that I'm trying to get FRP bypass: 6.01. (October 2016) Android Marshmallow / Galaxy S7 SM-G935V
I flashed combination ROM onto it already, so all I have to do now is flash the original stock firmware onto it to complete the FRP bypass? There's no need to make that OEM Unlock option show up?
Click to expand...
Click to collapse
I know this is an old post but answering for people who has the same question.... oem unlock is to be able to flash non official files like twrp or a modified firmware. to flash stock firm just flash with odin and that's all.
xxspokiixx said:
I know this is an old post but answering for people who has the same question.... oem unlock is to be able to flash non official files like twrp or a modified firmware. to flash stock firm just flash with odin and that's all.
Click to expand...
Click to collapse
Thank you, now I know in case I have to deal with Samsung phones again.
Greetings folks recently my note 4 got network error IMEI and SN are fine but stuck to Emergency calls only not registered on network ,so can I use combination file to fix this problem EFS related? as some folks mentioned it can be used to fix issues on the contrary i flashed a newer modem via odin and it happened dont have efs backup
Its work for binary blocked by OEM LOCK?
My phone get a text " Costum Binary blocked by OEM LOCK. (boot.img) or (recovery.img) and didn't boot into menu and recovery,only to download mode,can this Combination Frimware fix it?
anyone help me i have to remove lockscreen of my samsung j210f and i have thought first to enable adb by flashing combination files am scared my data will be lost am confused about the combination files
Wrong Information
This site does not have all combination firmware < Sorry but misinformation just waste time and energy some of us do not have by the time we get to this point for helping us with our phones.
This is the Method how i Root my Galaxy A12 .
This method is very easy if you take your time. THIS WILL ALSO WIPE YOUR DEVICE. I AM NOT RESPONSIBLE FOR ANY DEVICE OR SD CARD DAMAGE.
BEFORE PROCEEDING, UNLOCK BOOTLOADER.
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE.
1. Download the firmware for your device.
2. Load Zarchiver from playstore.
3. Open Zarchiver and locate the firmware you downloaded.
4. Click on the firmware, a menu will appear at the bottom. You will then have option to extract.
5. Extract the firmware and you will have files..AP..BL..CP..CSC..and HOME_CSC. The only file we need is AP
6. Click on AP file and rename AP_A125FXX.md5 to AP_A125FXX.tar - so your just highlighting the file and removing md5 so it only says .tar at the end.
7. Once you have renamed AP file click and again you will be given the option to extract. Once extracted, locate boot.img.lz4
8. Then extract boot.img.lz4 leaving you with boot.img
9. You should have Magisk manager installed on device. Use Magisk to patch the boot.img. once patched locate magisk_patched.img and rename to boot.img
10. Return to Zarchiver locate the patched boot.img and compress to boot.tar.
11. Move compressed boot.tar to computer and rename to boot.img.tar
12. Put device in download mode, open Odin and put the boot.img.tar in AP and click start. Once odin says pass, your device will boot to stock recovery and you will have to do a factory reset so save anything you need before doing this.
13. Once Device boots - RE-install Magisk Manager and follow prompts.
Congatulations, Youre Rooted Now.
{
"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"
}
It worked! Thank you so much for this tutorial!
Will This Affect OTA Updates (Will OTA Functionality Work After Root) And Will OTA Updates Unroot My Phone
cldkrs said:
BEFORE PROCEEDING, UNLOCK BOOTLOADER
Click to expand...
Click to collapse
can you please give a walk through on this , just starting out and need some help
cl3vin said:
can you please give a walk through on this , just starting out and need some help
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/how-to-unlock-bootloader.4244757/
But, does only flashing TWRP instead just need an OEM bootloader unlock, and doesn’t need to follow those above firmware steps like rooting on a stock ROM?
Just rooted my phone yesterday, by the way Safety net fails the basic integrity test, i guess there's no way to circumvent this since this device uses Hardware Backed attestation to detect an unlocked bootloader.
28.3.2021: Download of patched boot.img.tar failed with error:
SW REV CHECK FAIL : [boot]Fused 1 > Binary
Only official released binaries are allowed to be flashed : boot
KG STATUS : PRENORMAL was the culprit. For naive users inexperienced with Samsung devices like myself might be usefull to have warning in the rooting guide to avoid PRENORMAL state and link to instructions how to do it.
Update 8.4.2021: To get rid of PRENORMAL state is enough to wait for a week with sim, active data connection and maybe also logged into google account. Do not reboot or disconnect network during wait time. Check the OEM ulocking state in developer settings time to time (to trigger status verification on Samsung servers).
Flashing unofficial binary succeeded afterwards.
Sources:
https://milankragujevic.com/how-to-avoid-rmm-state-prenormal-when-unlocking-samsung-phones
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
After using Odin to flash a Magisk modified version of boot.img.lz4, my smartphone stayed in a boot loop. After flashing the unmodified version of boot.img.lz4 (uncompressed and tarred) I could boot again and I could also turn of OEM Unlocking in the development options. So I returned the Smartphone to the seller, giving the true reason.
Hi, where I can found the firmware for my Galaxy A12 (SM-A125F/DSN) for the root?
forumarbeit said:
Hi, where I can found the firmware for my Galaxy A12 (SM-A125F/DSN) for the root?
Click to expand...
Click to collapse
You can download it on SamMobile
forumarbeit said:
Hi, where I can found the firmware for my Galaxy A12 (SM-A125F/DSN) for the root?
Click to expand...
Click to collapse
cldkrs said:
[...]
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE.
[...]]
Click to expand...
Click to collapse
Download Samsung Galaxy A12 SM-A125F firmware
Download the latest Samsung firmware for Galaxy A12 with model code SM-A125F. Check out our free download or super fast premium options.
www.sammobile.com
Thanks @jkaltes, I download the firmware from sammobile.
After install is then an new OS on my rooted mobile phone or stays the same original OS only with root rights?
How can I unlock the bootloader?
cldkrs said:
BEFORE PROCEEDING, UNLOCK BOOTLOADER.
Click to expand...
Click to collapse
thanks for your feedback.
Ive tried searching for my firmware on sammobile however im not finding it. Its model sm-a125u doesnt even show up on their list.
fixapixa said:
Update 8.4.2021: To get rid of PRENORMAL state is enough to wait for a week with sim, active data connection and maybe also logged into google account. Do not reboot or disconnect network during wait time. Check the OEM ulocking state in developer settings time to time (to trigger status verification on Samsung servers).
Flashing unofficial binary succeeded afterwards.
Sources:
https://milankragujevic.com/how-to-avoid-rmm-state-prenormal-when-unlocking-samsung-phones
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
Click to expand...
Click to collapse
IF I get one of these things - I'm understanding (?) though we can get root - in order to keep root, one has to have a google acct?
2nd Q? is after the "wait to clear PRENORMAL" can the google acct be removed?
3rd Q? Can the phone be set up using WiFi (before buying a SIM) (?) then after the wait, put the SIM in? (reason I've asked is my carrier SIM "does ****" ...)
4th Q? Does the device need to be CARRIER unlocked to UL bootloader -- otherwise, I should buy a fully unlocked one, right?
Thanks in advance
VW
1) I guess it's not necessary to keep google account. Haven't confirmed myself however.
2) After unlocking the bootloader you should restart to system, connect to network and let the device verify status with Samsung servers. This way you avoid PRENORMAL status (without waiting) and will be allowed to flash patched AP. After the flash your device will be wiped so any existing google account is deleted anyway but after first boot into system you have to connect to network once again else device gets locked and you can start over. After your device succesfully synchronises itself with Samsung servers, you can disconnect from network and I don't see reason why you would need to have Google account if you don't want one.
3) You'll have to find out yourself. Personally I think that if you follow process from 2), wifi might be enough and no Google account would be needed at all but I cannot confirm that. In worse case if anonymity is paramount for you, just plug in some cheap prepaid SIM if such things are still availabe in your country and throw it away afterwards.
4) By carrier do you mean AT&T, Vodafone and such? No idea about your provider. Devices from open market are unlockable for sure but try to search the forum whether anybody encountered trouble with your provider.
As I wrote before, I have no previous experience with Samsung so I followed linked instructions and didn't experiment. If you want to help others, try to find out yourself and don't forget to report your findings here
fixapixa said:
..... if anonymity is paramount for you, just plug in some cheap prepaid SIM if such things are still availabe in your country and throw it away afterwards.
4) By carrier do you mean AT&T,
Click to expand...
Click to collapse
Thanks so much - Yeah, I'm that "anonymity paramount" user... Replacing a Blackberry Passport only because of that diabolical VoLTE...
Carrier = MetroPCS-T-Mobile
HOPEFULLY I'll be back with MetroPCS (runs on T-Mobile towers) by this time tomorrow ... If they'll re-activate the Passport. I've got a fallback android if that fails, but...
They might refuse the devices I have, and the A21 seems the best option in my price range, Rather than suffer from "bought in Store" sabotaged unit, I'll get one FACTORY unlocked.
US Carriers have gotten pretty evil, I've suddenly learned "Better the Devil you KNOW than meet a new one"
Thanks again for the feedback - VW
fixapixa said:
28.3.2021: Download of patched boot.img.tar failed with error:
SW REV CHECK FAIL : [boot]Fused 1 > Binary
Only official released binaries are allowed to be flashed : boot
KG STATUS : PRENORMAL was the culprit. For naive users inexperienced with Samsung devices like myself might be usefull to have warning in the rooting guide to avoid PRENORMAL state and link to instructions how to do it.
Update 8.4.2021: To get rid of PRENORMAL state is enough to wait for a week with sim, active data connection and maybe also logged into google account. Do not reboot or disconnect network during wait time. Check the OEM ulocking state in developer settings time to time (to trigger status verification on Samsung servers).
Flashing unofficial binary succeeded afterwards.
Sources:
https://milankragujevic.com/how-to-avoid-rmm-state-prenormal-when-unlocking-samsung-phones
https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
Click to expand...
Click to collapse
I am on samsung a10, I cant unlock my bootloader as my kg status is PRENORMAL. I have waited more than 168 hours for the oem unlock option to appar however nothing happend. I found that to unlock the bootloader I need to have my kg state to be normal. I have no idea what to do, i have tried reflashing may times, did all the updates and still nothing. Is there absolutely any hope?
cldkrs said:
This is the Method how i Root my Galaxy A12 .
This method is very easy if you take your time. THIS WILL ALSO WIPE YOUR DEVICE. I AM NOT RESPONSIBLE FOR ANY DEVICE OR SD CARD DAMAGE.
BEFORE PROCEEDING, UNLOCK BOOTLOADER.
YOU CAN FIND THE FIRMWARE YOU NEED ON SAMMOBILE.
1. Download the firmware for your device.
2. Load Zarchiver from playstore.
3. Open Zarchiver and locate the firmware you downloaded.
4. Click on the firmware, a menu will appear at the bottom. You will then have option to extract.
5. Extract the firmware and you will have files..AP..BL..CP..CSC..and HOME_CSC. The only file we need is AP
6. Click on AP file and rename AP_A125FXX.md5 to AP_A125FXX.tar - so your just highlighting the file and removing md5 so it only says .tar at the end.
7. Once you have renamed AP file click and again you will be given the option to extract. Once extracted, locate boot.img.lz4
8. Then extract boot.img.lz4 leaving you with boot.img
9. You should have Magisk manager installed on device. Use Magisk to patch the boot.img. once patched locate magisk_patched.img and rename to boot.img
10. Return to Zarchiver locate the patched boot.img and compress to boot.tar.
11. Move compressed boot.tar to computer and rename to boot.img.tar
12. Put device in download mode, open Odin and put the boot.img.tar in AP and click start. Once odin says pass, your device will boot to stock recovery and you will have to do a factory reset so save anything you need before doing this.
13. Once Device boots - RE-install Magisk Manager and follow prompts.
Congatulations, Youre Rooted Now.
View attachment 5244935
Click to expand...
Click to collapse
i flow this setup bue i can root heeeeeeeellp i need open bootloder ??
Just to elaborate on the Bootloader unlocking.
You will always need to connect to the internet, either wifi or sim card data.
Open Developer Options, Enable OEM unlock. (without internet, this option won't appear under developer)
boot to Download mode , confirm OEM unlock. This will wipe your phone.
go through start up, just skip everything, you phone will be wiped again anyway.
Connect to the internet, Open Developer Options, check that the "Enable OEM unlock" is greyed out!
By doing so, your bootloader is now unlocked. So yes, don't miss any steps stated above.
Samsung has a service called VaultKeeper to prevent unoffical firmware. Checking the "Enable OEM unlock" option is greyed out after Bootloader unlock will ensure the VaultKeeper to accept unoffical firmware. This requires internet connection. I suggest you to give the phone more time to check bootloader unlock state if you have a very slow / unstable internet connection.
If the outcome of the above steps does not appear to be true for you, your phone maybe cannot unlock bootloader.
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded
wouldnt there be a way through twrp or brom mode?
tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
Nope you can try brom mode but i dont trust if works
If you buy a samsung device depending of the device (like this A12 and the MTK imei bug) is not a good idea to upgrade
tekkitheidiot said:
wouldnt there be a way through twrp or brom mode?
Click to expand...
Click to collapse
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help
I tryed to downgrade via TWRP flashing baseband and BL
Now my A12 is DEAD and i dont had a box to repair it (after flash i see the security error screen and flashed again the Binary 3 BL once odin tell me passed the phone doesn't booted again)
I just wanted to get the imei working because the firmware on the binary 3 (11 and 12) android system uses all my ram memory trying to get the signal working
F*** *** Samsung and mediatek next time i bought an exynos or qualcomm variant
tekkitheidiot said:
i want to install a custom gsi, but it keeps bootlooping. wanted to install buf9 firmware but i cant bc its on sw_rev3 so it doesnt work. any suggestions?
Click to expand...
Click to collapse
The last rom that i used on my A12 was pixel experience and worked perfectly on binary 3 android 11 based firmare (A125MUBUS3BVF1) just installed TWRP with nulled vbmeta flashed the image as system (not as super) and wiped the data (not advanced wipe) rebooted and the gsi was booted (only bugs mentionated on the thread and the touch bug)
Allehandro said:
That's samsung for you, once you've upgraded Binary version there's no going back.
As for the brom mode, samsung has locked their phones out of that mode. I don't know if accessing it through access points works but you could try to see if it can help
Click to expand...
Click to collapse
i can access brom mode if that helps
tekkitheidiot said:
i can access brom mode if that helps
Click to expand...
Click to collapse
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.
Allehandro said:
How'd you do it?
Technically since I've always known that I can't access brom on my samsung I've never tried to understand what you can do with it.
Click to expand...
Click to collapse
i downgraded to the earliest binary 3, then used test points. worked perfectly
tekkitheidiot said:
i downgraded to the earliest binary 3, then used test points. worked perfectly
Click to expand...
Click to collapse
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
its relatively easy tbh. just be careful around the volume buttons, but everything else is okay. there arent too many cables to rip
Allehandro said:
I was only planning yo use the brom mode to use the MTK META Utility which is developed by Mediatek themselves for fixing imei to see if I can fix the imei issue with it but I couldn't enter brom mode and I'm afraid of opening the back cover
Click to expand...
Click to collapse
Its easy to open but be careful with the power/fingerprint sensor flex i think the testpoint is near of the charger flex in the mainboard (i see youtube tutorials to access to Brom mode and preloader)
{
"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"
}
Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.
LAST_krypton said:
Hello,
If you're going to be performing a downgrade, you'll have to have the SCATTAR firmware with all of the old loaded certificates and tokens. Flash is going to be performed via BROOM (fused ROM code) useing SP_FLASH_TOOL.
Regarding the IMEI issue, that I'm not able to help with. And it is pain to work with, maybe you the MODEM file could help bout dbout it. You might have to go diging through firmware sites.
Thats it.
Stay safe,
Krypton.
Click to expand...
Click to collapse
where would i find this scattar firmware?
tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
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%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working
MauriJ2001 said:
SM-A125U Multitool Kit (Root/TWRP/Unlock/Unbrick)
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%...
forum.xda-developers.com
Maybe this can help you only you need to download a firmware (don't try to flash a binary 2 or binary 1 firmware if you do that you phone will get a hardbrick and the sp flashtool will give the 0xC0020029 or the anti roolback error)
Pd: dont forget to change the date to 25/05/2022 to get the mtkmetatool working
Click to expand...
Click to collapse
ill look through it. thanks
tekkitheidiot said:
where would i find this scattar firmware?
Click to expand...
Click to collapse
You generate it your self
To unlock bootloader on these the easiest way is to convert it to an a125w xac by flashing the a125w bl files. Unlock bootloader with seccfg. Then flash ap, cp, and csc from a125w with odin and when it boots up it should show as a125w. Also in download mode it shows the same. My imei says unknown but i believe thats caused by unlocking bootloader so if you relock it after converting it should go back to normal. Playing with mtk modem tool to rewrite imei. Tried using xposed imei changer but didnt seem effective.
Phone: Redmi Note 11 Pro (IMEI search shows model number 21091116C sticker that came with phone shows model number 21091116SG not sure if this matters)
I have accidently patched and written the wrong boot.img to my phone after poorly attempting to setup Magisk to get google pay working on this phone
Am now stuck with the phone either booting to recovery window or I Can enter fastboot
Device bootloader is locked and i do not have a Xiaomi account linked to phone, trying to flash what i believe is ROM using MiFlash tools but fails since bootloader is locked, attempted to unlock using mediatek unlocker tools and cant manage to get this to work either
Feels like there's nothing i have not tried at this point have 20 chrome tabs open, downloaded so many different ROMs and followed heaps of different methods without any success
Edit: Account had not been linked to phone yet
Apologies if this is not posted in the correct format/section believe its right from the rules
Any help would be really apprechiated
I would think MiFlash should still work on a locked BL from EDL. What specific error do you get on MIFlash?
@orangekid thanks for the reply
Tested with multiple Global and CN roms "error:FAILED (remote: not allowed in locked state)
{
"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"
}
Are you in fastboot or EDL?
just reflash the original unpatched boot.img in fastboot.
I have currently the problem that im stuck in poco boot logo, when I flash patched-boot.img. reflashing unpatched boot.img makes it boot again.
orangekid said:
Are you in fastboot or EDL?
Click to expand...
Click to collapse
Fastboot with the orange "FASTBOOT" display
seedlord said:
just reflash the original unpatched boot.img in fastboot.
I have currently the problem that im stuck in poco boot logo, when I flash patched-boot.img. reflashing unpatched boot.img makes it boot again.
Click to expand...
Click to collapse
I tried flashing heaps of different stock ROM boot.img's but must not be able to find the original not sure, believe its a CN phone that had a Global ROM installed when i brought it but could be wrong
Connor.- said:
Fastboot with the orange "FASTBOOT" display
Click to expand...
Click to collapse
Ok you might need to get the phone in EDL mode. If you cannot do it thru fastboot (I think newer phones might not be able to) you might have to remove the back cover and use tweezers to do it thru test point (google or youtube test point EDL for your phone).
Then once in true EDL you can try flashing again with the tool. If you still cannot due to no authorization or locked BL or whatever, you might need to extract the stock image and use a patched firehose file to trick MIFlash tool.
I can try to look but it looks like these guys have a collection as well over here:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
I know this is a lot but my thing is in the future if you are going to modify your phone like kernel patching or anything of the sort you need to unlock your BL first. Just trying to point you in any direction that can resurrect your device.
Believe me I have been in weird situations, such as last year when I somehow flashed a bad file on my OnePlus 9 and the ONLY solution was to literally flash an Indian OnePlus 9 Pro (different device, different region) ROM on my phone from EDL, so my point is there's almost always something you can do unless you want to say screw it and send it in for repair.
I would remove the back of the phone and leave it off, because whatever you're going to do might require test point EDL until you actually get something to flash and boot. At this point I guess it can't really get any worse.
orangekid said:
Ok you might need to get the phone in EDL mode. If you cannot do it thru fastboot (I think newer phones might not be able to) you might have to remove the back cover and use tweezers to do it thru test point (google or youtube test point EDL for your phone).
Then once in true EDL you can try flashing again with the tool. If you still cannot due to no authorization or locked BL or whatever, you might need to extract the stock image and use a patched firehose file to trick MIFlash tool.
I can try to look but it looks like these guys have a collection as well over here:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
I know this is a lot but my thing is in the future if you are going to modify your phone like kernel patching or anything of the sort you need to unlock your BL first. Just trying to point you in any direction that can resurrect your device.
Believe me I have been in weird situations, such as last year when I somehow flashed a bad file on my OnePlus 9 and the ONLY solution was to literally flash an Indian OnePlus 9 Pro (different device, different region) ROM on my phone from EDL, so my point is there's almost always something you can do unless you want to say screw it and send it in for repair.
I would remove the back of the phone and leave it off, because whatever you're going to do might require test point EDL until you actually get something to flash and boot. At this point I guess it can't really get any worse.
Click to expand...
Click to collapse
Thanks for this, i believe its a Mediatek processor not qualcomm unfortunately but EDL pins dont look too hard to access was suprised to see how easy it is to remove the glass back. I'm in talk with the store i purchased it from at the moment so will see how this goes before falling back to pulling the phone apart (only recieved it last Friday )
Realistaclly i am happy with MIUI it works fine for me only intention was to bypass safetynet with magisk so i can use it for contact payments everything else I had already setup just how i like it
Also I would try this maybe?
My experience unbricking a Xiaomi Redmi Note 11 Pro 5G (China) - Hovatek Blog
The Xiaomi Redmi Note 11 Pro (China) is an Android 11 device powered by the MediaTek Dimensity 920 chipset. In
www.hovatek.com
Also you can try this:
[No auth collection] Xiaomi No Auth Firehose Files for Qualcomm based phones.
What is this file? As we all know that Xiaomi has blocked offline flashing with authentication to flash their device. This files will ultimately help you to fix the Mi Account Authorization issue and hence unbrick your Xiaomi device via EDL mode...
forum.xda-developers.com
Tou should never try to flash anything on a phone with lovked bootloader. Even if you had patched the correct boot.img you would have ended with a brick because your bootloader is locked.
Michael P. said:
Tou should never try to flash anything on a phone with lovked bootloader. Even if you had patched the correct boot.img you would have ended with a brick because your bootloader is locked.
Click to expand...
Click to collapse
well it wasnt locked when i first tried