Related
I flashed my phone with kate_global_images_7.5.19_20170519.0000.00_6.0_global in order to unlock the bootloader via mi unlock. The phone has successfully connected to mi cloud and can be located on the i.mi.com website. If I go into developer options and tap on the button to bind the phone to my account for unlocking it just keeps telling me to try again in another couple of minutes. This seems to be a really common problem and I haven't been able to find a solution. Any ideas? Thanks.
Same here. Been waiting for 5 days now after getting permission. Still fails to bind. This whole official unlock way is a total POS. It even says after you are granted permission you can unlock right away but that's not true at all. I also have SE and dev rom btw.
maybe try to flash miui 8 via fastboot..
i used fastboot rom miui 8 , miflash (not xiaomiflash) ver 2016, and unlock ver 1.1..
Augesvarer said:
maybe try to flash miui 8 via fastboot..
i used fastboot rom miui 8 , miflash (not xiaomiflash) ver 2016, and unlock ver 1.1..
Click to expand...
Click to collapse
MIUI 8 what? The dev rom 7.x is MIUI 8. Do you mean dev or stable? I was on MIUI 8 stable before but it didn't help.
my issues, evrytime i flashed miui rom, my imei isn't showing up (i need to official unlock to flash lastest los)
i tried some rom dev 7.x.x.x , but i cant login mi account via wifi.
then, i flashed this rom with miflash 2016 (mine is kenzo)
http://en.miui.com/thread-439892-1-1.html
and it works, i can unlock my phone without imei..
Augesvarer said:
my issues, evrytime i flashed miui rom, my imei isn't showing up (i need to official unlock to flash lastest los)
i tried some rom dev 7.x.x.x , but i cant login mi account via wifi.
then, i flashed this rom with miflash 2016 (mine is kenzo)
http://en.miui.com/thread-439892-1-1.html
and it works, i can unlock my phone without imei..
Click to expand...
Click to collapse
I think the "can not bind" problem is specific to Kate. The IMEI problem with your Kenzo phone is probably a separate issue.
dwl99 said:
I flashed my phone with kate_global_images_7.5.19_20170519.0000.00_6.0_global in order to unlock the bootloader via mi unlock. The phone has successfully connected to mi cloud and can be located on the i.mi.com website. If I go into developer options and tap on the button to bind the phone to my account for unlocking it just keeps telling me to try again in another couple of minutes. This seems to be a really common problem and I haven't been able to find a solution. Any ideas? Thanks.
Click to expand...
Click to collapse
Try this
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
it work perfectly and i have successfully unlock my kate and flash latest LOS.
abe_long said:
Try this
https://forum.xda-developers.com/redmi-note-3/how-to/successfully-officially-unlocked-redmi-t3543150
it work perfectly and i have successfully unlock my kate and flash latest LOS.
Click to expand...
Click to collapse
Thanks for the reply but I need to have the latest dev ROM to allow LineageOS to flash - it checks for the most recent firmware.
dwl99 said:
Thanks for the reply but I need to have the latest dev ROM to allow LineageOS to flash - it checks for the most recent firmware.
Click to expand...
Click to collapse
Yes i know.first you use the older version miui to unlock the bootloader.after that just reflash to latest dev rom.make sure you checked CLEAN ALL.it will not lock your bootloader.
abe_long said:
Yes i know.first you use the older version miui to unlock the bootloader.after that just reflash to latest dev rom.make sure you checked CLEAN ALL.it will not lock your bootloader.
Click to expand...
Click to collapse
Thanks, I tried this but got stuck in a bootloop.
dwl99 said:
Thanks, I tried this but got stuck in a bootloop.
Click to expand...
Click to collapse
At which step does the bootloop come..?i also having bootloop after flash the twrp but it can be solve by flash the lazy flash zip
abe_long said:
At which step does the bootloop come..?i also having bootloop after flash the twrp but it can be solve by flash the lazy flash zip
Click to expand...
Click to collapse
I flashed kate_global_images_6.7.14_20160629.0000.25_6.0_global_1b43c8f07f and then started to get bootloops. I didn't get as far as flashing TWRP.
dwl99 said:
I flashed kate_global_images_6.7.14_20160629.0000.25_6.0_global_1b43c8f07f and then started to get bootloops. I didn't get as far as flashing TWRP.
Click to expand...
Click to collapse
After flash,try to wipe data and cache in recovery.then reboot your device.if after 5 min still looping,try to force reboot.
abe_long said:
After flash,try to wipe data and cache in recovery.then reboot your device.if after 5 min still looping,try to force reboot.
Click to expand...
Click to collapse
I thought of that but I couldn't get the phone to boot into recovery - Power and Vol+ opened a screen with a picture of the phone with a cable being plugged into it rather than recovery
dwl99 said:
I think the "can not bind" problem is specific to Kate. The IMEI problem with your Kenzo phone is probably a separate issue.
Click to expand...
Click to collapse
Just try unlocking via mi unlock and tell us ignore the message
Androbots said:
Just try unlocking via mi unlock and tell us ignore the message
Click to expand...
Click to collapse
Doesn't work - complains that the deivice isn't bound to the account
There is no point trying anything. Nothing works. I have a 3 month long email chain with xiaomi support, which ended by them saying I should contact the direct seller. Basically they washed their hands. I ended up sending my device to a guy, who has a xiaomi service licence, and he managed to unlock it officially with his code.
If you cannot bind your account and device for two weeks with multiple tries, you should just give up on the "mainstream" unlock procedure. It will never work, and the only thing that comes out of it is slowly bulding rage.
It's not worth it.
smash1986hu said:
There is no point trying anything. Nothing works. I have a 3 month long email chain with xiaomi support, which ended by them saying I should contact the direct seller. Basically they washed their hands. I ended up sending my device to a guy, who has a xiaomi service licence, and he managed to unlock it officially with his code.
If you cannot bind your account and device for two weeks with multiple tries, you should just give up on the "mainstream" unlock procedure. It will never work, and the only thing that comes out of it is slowly bulding rage.
It's not worth it.
Click to expand...
Click to collapse
Sounds like good advice. My Note 4 has arrived now so I think I'll just flash the stock MIUI ROM & ebay it.
smash1986hu said:
which ended by them saying I should contact the direct seller
Click to expand...
Click to collapse
What if I bought it directly from their online store? Do I contact them back?
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
crimsonrommer said:
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
Click to expand...
Click to collapse
thanks, it worked for me. appreciate.
Your welcome.
What did u even use to root?
What build is this for?
It works with me....Thank you so much.
this works also on 320fn?
fraizzo said:
this works also on 320fn?
Click to expand...
Click to collapse
Sadly not
JustAnotherAndroid said:
What did u even use to root?
Click to expand...
Click to collapse
I used magisk
Sands207 said:
What build is this for?
Click to expand...
Click to collapse
I don't remember
Is this process can unlock the phone from sprint ?
No, call sprint, then ask to unlock
crimsonrommer said:
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
Click to expand...
Click to collapse
Simply turning off usb debugging will not throw your phone into a boot loop normally unless ou had some bad hardware or custom settings.. Only time ive seen that happen is by using data from other models. Easy way to get past it is to just take out your battery for a bit, replace it then boot into upload mode. Next youll have to try various combos releasing the buttons and presing again quickly to get back to the download mode. Alternatively boot into TWRP/STock recovery, use AT+ Commands or use a application that will boot back.
Awesome you found a little trick to simplify it ! Keep it up!
EDIT: Ohh i see.. you are on a custom rom / binary? I still have yet to have this happen but to a J700 with SynexOS on it.. Ill give this a try.
Hello
Im on Android 9 beta, but I want to rollback. Huawei released a few days a 150 rom for rollback, I downloaded from FF but I don't know how to flash. Im on stock rom, locked bootloader and no root. The rom contains 2 files.
zulykat said:
Hello
Im on Android 9 beta, but I want to rollback. Huawei released a few days a 150 rom for rollback, I downloaded from FF but I don't know how to flash. Im on stock rom, locked bootloader and no root. The rom contains 2 files.
Click to expand...
Click to collapse
You would install it through the Beta app.
zulykat said:
Hello
Im on Android 9 beta, but I want to rollback. Huawei released a few days a 150 rom for rollback, I downloaded from FF but I don't know how to flash. Im on stock rom, locked bootloader and no root. The rom contains 2 files.
Click to expand...
Click to collapse
Try with eRecovery, it might work.
The beta app doesn't have any option to flash, it's only for report bugs. The eRecovery doesn't have a restore option neither.
I opened a chat with huawei and they told me to restore using Hisuite with a "back to another version" option, but this option doesn't exist in the app.
zulykat said:
The beta app doesn't have any option to flash, it's only for report bugs. The eRecovery doesn't have a restore option neither.
I opened a chat with huawei and they told me to restore using Hisuite with a "back to another version" option, but this option doesn't exist in the app.
Click to expand...
Click to collapse
Can you post a screenshot with the eRecovery screen?
To access eRecovery, you must connect usb cable first, then power on the device with Power +Volume UP combo.
Pretoriano80 said:
Can you post a screenshot with the eRecovery screen?
To access eRecovery, you must connect usb cable first, then power on the device with Power +Volume UP combo.
Click to expand...
Click to collapse
Ah, I tried with the normal recovery.
I've tried using erecovery but it fails searching for the rom
Hi,
Did you manged to solve it i am having the same problem
Actually, how did you get beta?
If you used FH you would have to use that to roll back as you're not approved for Beta.
hey guys I have a SM-g965f and 960F, I'm trying to see if the bootloader will let me install twrp after 7 days
imgur.com/a/9cBiSEQ
please help thank you!
Those screenshots dont mean anything.if you have oem unlock option, when you dont go into odin mode as soon as you press factory reset button you will have to wait another 7 days.
Sent from my Galaxy S9+ using XDA Labs
gsser said:
Those screenshots dont mean anything.if you have oem unlock option, when you dont go into odin mode as soon as you press factory reset button you will have to wait another 7 days.
Sent from my Galaxy S9+ using XDA Labs
Click to expand...
Click to collapse
ok so my S9 did pop that earlier today, when I hit it, it ask for my phone to be reset, which I did, when I boot back into download mode, it says OEM unlock off but prenormal mode is still on?
S9ROOT said:
ok so my S9 did pop that earlier today, when I hit it, it ask for my phone to be reset, which I did, when I boot back into download mode, it says OEM unlock off but prenormal mode is still on?
Click to expand...
Click to collapse
Then you have to keep your device on 168 hours again like i am doing...
Sent from my Galaxy S9+ using XDA Labs
gsser said:
Then you have to keep your device on 168 hours again like i am doing...
Sent from my Galaxy S9+ using XDA Labs
Click to expand...
Click to collapse
the problem is, when that prenormal state is off, can you flash a custom binary? because from what I have seen, samsung lock it down pretty hard now, but I cant find a definite answer that you can flash after 7 days.}
I have no problem waiting, but I just want to know if there are peopel out there with the upgraded bootloader can still custom recovery, due to this new implementation, it seems like if its not an official binary from Samsung you cant flash anything at all. OEM unlock is just to unlock the phone without utilizing your email.
S9ROOT said:
the problem is, when that prenormal state is off, can you flash a custom binary? because from what I have seen, samsung lock it down pretty hard now, but I cant find a definite answer that you can flash after 7 days.}
I have no problem waiting, but I just want to know if there are peopel out there with the upgraded bootloader can still custom recovery, due to this new implementation, it seems like if its not an official binary from Samsung you cant flash anything at all. OEM unlock is just to unlock the phone without utilizing your email.
Click to expand...
Click to collapse
like i said it will be useless in pie because there are no custom binaries(TWRP) for pie.
it is most likely will be done with oreo firmware. There is no point of waiting for rmm state normal in pie. if you have a pie compatible custom recovery then fiine you can wait but we dont have pie compatible recovery(as far as i know).
Like i said before i have waited 7 days after i enabled oem unlock in pie, after the reset i waited 7 days more but rmm state didnt went to normal state.
gsser said:
like i said it will be useless in pie because there are no custom binaries(TWRP) for pie.
it is most likely will be done with oreo firmware. There is no point of waiting for rmm state normal in pie. if you have a pie compatible custom recovery then fiine you can wait but we dont have pie compatible recovery(as far as i know).
Like i said before i have waited 7 days after i enabled oem unlock in pie, after the reset i waited 7 days more but rmm state didnt went to normal state.
Click to expand...
Click to collapse
you are not making sense right now, I am not in android 9 Pie, I am still in oreo.
S9ROOT said:
you are not making sense right now, I am not in android 9 Pie, I am still in oreo.
Click to expand...
Click to collapse
Edit, got confused over some threads sorry. I am on 60 hours, still no oem unlock toggle appeared. We can only ask who had to wait after toggling oem unlock on.
Overall, gotta wait 7 more days for rmm state, no promises but nothing else to do... until then no custom binary can be flashed
Bootloader lock and account frp is off but rmm is blocking custom binaries, so when you have rmm state normal, you will be able to flash twrp.
Sent from my Galaxy S9+ using XDA Labs
dang I wish somebody has the answer to this....someone gotta done this before.
S9ROOT said:
dang I wish somebody has the answer to this....someone gotta done this before.
Click to expand...
Click to collapse
1 week wait is understandable but after factory reset is just bull****. Literally they are making anything they can to prevent roms and kernels...
Sent from my Galaxy S9+ using XDA Labs
Anyone know how to downgrade os? I'm on android 11.
Your bootloader must be unlocked. Once that is done, flashing an older firmware should be relatively trivial using Odin.
I just did it. Flashed android 10 from 11. Flash an unlocked frp if its locked. Use Odin3 v3.14 patched. Make sure you use right csc code
Is this the same procedure for all samsung? I've done this to my galaxy s10, but instead of odin i flashed a backup of android 10 using twrp (currently i'm using the latest bootloader) and the phone is now in bootloop.
I resell phones so I'm not super familiar with twrp, but sing patched Odin to downgrade works like a charm.
In patched odin flash ap, bl cp csc and user data. Even if you're frp locked that will get you past it. Use android 10 build date 20210626133126 samfw
jayvee1 said:
I resell phones so I'm not super familiar with twrp, but sing patched Odin to downgrade works like a charm.
Click to expand...
Click to collapse
Do you know if flashing the system using odin it deactivate the oem unlock? (aka RMM State: Prenormal) because after the system installation i need to install twrp
GamingSoldier said:
Do you know if flashing the system using odin it deactivate the oem unlock? (aka RMM State: Prenormal) because after the system installation i need to install twrp
Click to expand...
Click to collapse
I just answered that in the post about the yours. We typed at the same time
jayvee1 said:
I just answered that in the post about the yours. We typed at the same time
Click to expand...
Click to collapse
So, what your thoughts about this: https://samfw.com/blog/what-is-bit-binary-value
If for some reason my flashing system to bypass oem lock was a one off there are multiple other ways. You could flash a single partition using Medusa. Or read Thread 'V60 Bootloader Unlock and Magisk Root' https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ and you'll learn how to Fastboot flash oem unlock. That works, I did it on a V60
So when flashing look at the 5th number of the baseband is a 5 then you can flash anything 5 or higher. If you flash a 4 you're going to break it. If you flash a 7 you can always go back down to 5
jayvee1 said:
If for some reason my flashing system to bypass oem lock was a one off there are multiple other ways. You could flash a single partition using Medusa. Or read Thread 'V60 Bootloader Unlock and Magisk Root' https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/ and you'll learn how to Fastboot flash oem unlock. That works, I did it on a V60
Click to expand...
Click to collapse
Well, that explains it all, LG phones and Samsung are very different, with a samsung there is this thing called "Binary" or "SW Rev" meaning that if you have a binary 10 installed on your device and try to install the binary 9 it will not flash or if you force-it to flash your phone won't boot in to the system (only in download mode), every new android version it changes the binary, so in samsung it's only possible to downgrade the android version if you use a rom that is compatible with the latest binary
jayvee1 said:
So when flashing look at the 5th number of the baseband is a 5 then you can flash anything 5 or higher. If you flash a 4 you're going to break it. If you flash a 7 you can always go back down to 5
Click to expand...
Click to collapse
I have a galaxy s10 g973f and i just had updated to the latest bootloader, when i tried to install the older one the phone didn't boot anymore and i had to do some things to get back it working again
I look at the
GamingSoldier said:
I have a galaxy s10 g973f and i just had updated to the latest bootloader, when i tried to install the older one the phone didn't boot anymore and i had to do some things to get back it working again
Click to expand...
Click to collapse
I look at th csc code. If I flash and it bootloops then I reflash something else. You rarely break a phone permanently. Sometimes I have no clue what the original firmware was or im combining different pieces. So reflash the csc that works and eventually everything will work out.
GamingSoldier said:
Do you know if flashing the system using odin it deactivate the oem unlock? (aka RMM State: Prenormal) because after the system installation i need to install twrp
Click to expand...
Click to collapse
it doesn't but i followed this and it works. https://www.hardreset.info/devices/...02s/faq/bootloader-unlock/samsung-bootloader/
Hum quite interestig this post I have A715F/DS with frp lock. and android 11 stock-I'm planing to downgrde to adroid stock 10 (cant do anything) I will be able to do that (download firmware/botloader with frp locked) or I will brick it?Bettar to use last Odin version r the last Odind version ptched?
helen2 said:
Hum quite interestig this post I have A715F/DS with frp lock. and android 11 stock-I'm planing to downgrde to adroid stock 10 (cant do anything) I will be able to do that (download firmware/botloader with frp locked) or I will brick it?Bettar to use last Odin version r the last Odind version ptched?
Click to expand...
Click to collapse
i have a whole complete ao25q with patched magisk and a debloater if you want me to upload with pit files. I'm using the newest Odin Version
MiniNinja2024 said:
i have a whole complete ao25q with patched magisk and a debloater if you want me to upload with pit files. I'm using the newest Odin Version
Click to expand...
Click to collapse
that is realy knde from u I funt "hopefull a solution "to keep knox 0x0 (just for install app as patypal) a A710F_Fix_Open_OEM that they say reset the frp (hope will not brick handy) I will let u know!
MiniNinja2024 said:
i have a whole complete ao25q with patched magisk and a debloater if you want me to upload with pit files
Click to expand...
Click to collapse
helen2 said:
that is realy knde from u I funt "hopefull a solution "to keep knox 0x0 (just for install app as patypal) a A710F_Fix_Open_OEM that they say reset the frp (hope will not brick handy) I will let u know!
Click to expand...
Click to collapse
kk, keep me updated and i will look around for ya also
MiniNinja2024 said:
kk, keep me updated and i will look around for ya also
Click to expand...
Click to collapse
so that file is oeM but modded s no chance nw I will try to dwngrade the I wll try t flas Samsung service rom