Hey folks,
So i got my Atrix from RMA today, it has a new mainboard, had WLAN errors before. Tried to unlock it with ihop_bell.sbf, like last time, but it failed. Now it says failed to boot 1, the bootloader is still locked, because fastboot does not know oem unlock.
I can enter fastboot mode. If I start and press volume down it says something about nvflash for 0.5 secs and turns off. RSD detects it as SE Flash Olympus and I can start flashing, but it always fails at "Switching to BP Pass trough mode".
So what now, is it hardbricked?
Before flashing did you check your FW version (i.e. Build number/version) to see what type it was, sometimes after installing new parts they will turn it on and test it to see how it works and may hit update while at it to make sure it is ready to go out of the box
Should be the German Retail 2.3.4, did not check it though. Just made sure the WiFi Error is gone.
Uh, you might have wanted to check. You always want to ensure software revision numbers before attempting the unlock. Even some retail updates can have minor build changes that could result in your bootloader unlock bricking your phone.
So moto-fastboot is not responding to the CMD "oem unlock"? I am just going over all the info to see if I can help, I have had the "Failed to boot #" issue with a multitude of Moto's (CDMA and GSM, and my global Photon) I have also been able to fix them. Was your device fully charged before attempting the SBF flash? that will kill an SBF flash and possibly the phone.
---------- Post added at 01:29 PM ---------- Previous post was at 01:20 PM ----------
It would also appear that FTB 1 is related to not having atleast 50% charge available during the flash. You may want to get a battery charger for it and charger the phone and attempt a flash from there. This thread has a little info in it (if you read the on topic stuff) http://forum.xda-developers.com/showthread.php?t=1491788 . Good luck my friend, I know how it feels, If you have any questions let me know.
Edit: If you can get fastboot to atleast give you info on any bootloader variables (fastboot getvar <variable request>) then you may be able to find out if their was a software revision, i am unsure at this time
OMG!
After I tried flashing the international unlock like 5 times more again and the same error ocurred, I tried to unlock in fastboot after ur last post and IT WORKED
TBH I am a little bit confused, because 1 hour ago it(the unlock) did not work and really can not understand what was wrong before. Still on the same battery.
Now it is unlocked and the message is gone, I can enter e.g. the RSD mode or the recovery.
Maybe it had to do with battery indeed, I dont know, just happy that it works again. Thanks for posting mate!
Haha, That's good. Hope it stays going well for you. I hated when I flashed pudding and it failed then ran the OEM unlock code just to see if it would continue, sure enough it did. Glad to hear it is fixed
Related
hi, here I am again to ask:
I installed about 2 hours, never restart the phone, the FW: V20C_00 EUR.
I tried to unlock the bootloader but when I reboot instead of giving me the scermata release, I simply restarts.
Question: What firmware should I install? and where can I download?
Thank you very much again for your patience
A lot of people are in your shoes, and this is not fully figured out yet. Some people recently suggested adb version may have something to do with it. Look for their posts for discussion and possible solution. We don't need another post on this.
Meanwhile, you can try again, at least for a few more times (30 min to 1hour waiting with phone on network needed for each try). I got my unlocked the "last time" I would like to try before giving up.
mrmathematica said:
A lot of people are in your shoes, and this is not fully figured out yet. Some people recently suggested adb version may have something to do with it. Look for their posts for discussion and possible solution. We don't need another post on this.
Meanwhile, you can try again, at least for a few more times (30 min to 1hour waiting with phone on network needed for each try). I got my unlocked the "last time" I would like to try before giving up.
Click to expand...
Click to collapse
hello, today I had an idea, I plugged the phone in fastboot mode by following this guide: http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
I tried if the phone was plugged in, all ok I found. I tried to type the command "fastboot oem unlock" it gives me an error. Now, do you think you could use fastboot to unlock the bootloader?
tonysgh89 said:
hello, today I had an idea, I plugged the phone in fastboot mode by following this guide: http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
I tried if the phone was plugged in, all ok I found. I tried to type the command "fastboot oem unlock" it gives me an error. Now, do you think you could use fastboot to unlock the bootloader?
Click to expand...
Click to collapse
Negative.
Not all OEM allow that command. LG fastboot don't even allow getvar all.
Motorola G4 XT1625
Minor Problem: Phone will not start normally, only boots into Fastboot mode.
Minor Problem: Phone is oem Locked
Major Problem: I never went into "settings" on the phone and ENABLED OEM UNLOCKING.
Question: Is it possible to get this phone flashed with stock ROM?
A little background. Not a developer, phone started acting up a few days ago, shutting down or rebooting on its own, do not remember anything such as an update or my clearing of the cache occurring in that time frame, but I was still hoping it was a software issue that would work itself out. Now the phone fails during start up and reports this
STARTUP FAILED
ERROR: Failed to pass validation , backup to fastboot.
It does mention I should use Software Repair Assistant to recover the phone, which correct me if I'm wrong , only works with Verizon phones. I did try the SRA, it connected to the phone, but would stall about halfway through.
I have found much info on this forum regarding unlocking the bootloader of this phone, I have installed on Moto tools on my PC, requested and received an unlock code, connected to the phone and can send commands via command line. Unfortunately when I send the oem unlock the phone responds that I need to enable development mode in settings, which I cannot get to because the phone wont boot to the OS. Is there an easy way around this that I'm just not seeing?
In the end the problem may be hardware related, I just hate to give up on it so easily. Contacted Motorola about the device, as it turns out the unit was 6 days out of warranty ( that's if you use the Amazon ship date, it was only actually 2 days out if you use the activation date). Their response was as expected, sorry can't help you, thanks for being a Motorola customer, have wonderful day, next........
MSC 1/24/18
Hello,
As the title says, I'm wanting to root my new CAT S61. Anyone managed to unlock the bootloader yet? I've played around with it but haven't had any luck so far.
+1, Me too. Just started debating them on facebook, to maybe have some pressure on to unlock the bootloader the nice way. Until that I am ready to donate. I really miss htc sense, coming from 10-year htc spree.
I have had a few email and chat exchanges with them but haven't made any progress in getting them to provide any help in unlocking the bootloader but I still have my fingers crossed. And yes, I miss htc sense also.......I didn't think I would. FYI, I downloaded Nova Launcher and I set to look much like sense.
I've also been on to their support team looking for assistance with this..... Massively unhelpful...
I asked them about possibilities of unlocking the bootloader (I usually void every warranty covering computer equipment I own within days of owning devices) and I was told along the lines of "No. This will void the warranty so we would not allow this on the device.".... Its MY device and MY warranty to void ffs!
Really gets on my tits the attitude they took.
Anyway, am thinking that unlocking the bootloader may end up like a long wait and a bit of a chore; however if anyone is able to get a dump of the stock image it would surely be possible to patch the image with Magisk then "fastboot flash" it back onto the Cat S61?
This should at least give SU access (for busybox and all that lovely stuff) as well as keeping all the FLIR/proprietary laser/VOC sensor stuff.
EDIT: I've got in touch with Bullitt Group directly instead of going through Cat, and am awaiting a reply from them regarding acquiring a factory image I can play around with... Hopefully they will be able to supply it to me!
Regarding unlocking the bootloader, I haven't tried myself yet (because I haven't got around to getting my laptop OS installed again... That's another story entirely involving bad decisions with Kali lol) but if you boot the phone into bootloader mode (power on the device by using either volume up or volume down and power button or the adb reboot bootloader command via USB). Then you may be able to use the fastboot flashing unlock command to unlock the bootloader...
I really miss the sense freestyle themes, where there is no grid and you pick a theme with background image(can be changed) and stickers (just some themed icons with different sizes). Then you place your stickers and assign apps to them. I myself used an archtecure theme, where there were stickers varying feom minimalistic monopoly houses up to vertically big skyscrapers and horizontally long trains. For my gf I made nature theme with nice summer bliss and clouds, deers, rabbits, butterflies and birds. Its just so customizable. I hate being restricted to grids or standard sizes icons or their 2x, 4x and so on.
k46tank said:
I have had a few email and chat exchanges with them but haven't made any progress in getting them to provide any help in unlocking the bootloader but I still have my fingers crossed. And yes, I miss htc sense also.......I didn't think I would. FYI, I downloaded Nova Launcher and I set to look much like sense.
Click to expand...
Click to collapse
---------- Post added at 06:29 PM ---------- Previous post was at 06:23 PM ----------
I just received a 130MB OTA, I hope it was not a security update, casting me out of the gang, when someone finds the cure for the older build. The build LTE_D0201121.0_S61_0.040.02 gave me Flir Youtube streaming option.
luc1fer said:
I've also been on to their support team looking for assistance with this..... Massively unhelpful...
I asked them about possibilities of unlocking the bootloader (I usually void every warranty covering computer equipment I own within days of owning devices) and I was told along the lines of "No. This will void the warranty so we would not allow this on the device.".... Its MY device and MY warranty to void ffs!
Really gets on my tits the attitude they took.
Anyway, am thinking that unlocking the bootloader may end up like a long wait and a bit of a chore; however if anyone is able to get a dump of the stock image it would surely be possible to patch the image with Magisk then "fastboot flash" it back onto the Cat S61?
This should at least give SU access (for busybox and all that lovely stuff) as well as keeping all the FLIR/proprietary laser/VOC sensor stuff.
EDIT: I've got in touch with Bullitt Group directly instead of going through Cat, and am awaiting a reply from them regarding acquiring a factory image I can play around with... Hopefully they will be able to supply it to me!
Regarding unlocking the bootloader, I haven't tried myself yet (because I haven't got around to getting my laptop OS installed again... That's another story entirely involving bad decisions with Kali lol) but if you boot the phone into bootloader mode (power on the device by using either volume up or volume down and power button or the adb reboot bootloader command via USB). Then you may be able to use the fastboot flashing unlock command to unlock the bootloader...
Click to expand...
Click to collapse
LTE_D0201121.0_S61_0.040.02 is the build I'm on as well, so don't worry too much... However I've been on this build since sometime in July, so don't know why you've only just got the OTA ?
Anyway, the other thought I have been having is trying to port across a custom recovery from the Motorola Moto X4. Same chipset, same RAM, same board and same screen resolution, so it just might work... Once I get hold of a flash dump and unlock the bootloader that is ? I'm getting a bit ahead of myself!
Just received another OTA, September 1st patch, LTE_D0201121.0_S61_0.046.02. Radio is LTE_D0201121.1_S61 after the update. This one was larger, but I forgot to screenshot the exact changes and size.
luc1fer said:
LTE_D0201121.0_S61_0.040.02 is the build I'm on as well, so don't worry too much... However I've been on this build since sometime in July, so don't know why you've only just got the OTA ?
Anyway, the other thought I have been having is trying to port across a custom recovery from the Motorola Moto X4. Same chipset, same RAM, same board and same screen resolution, so it just might work... Once I get hold of a flash dump and unlock the bootloader that is I'm getting a bit ahead of myself!
Click to expand...
Click to collapse
Is any progress?
I am not a programmer, and can not help anything. Looking forward good news!!
Hi there, also looking forward for root, will hopefully get the phone end of the year...
ogghi said:
Hi there, also looking forward for root, will hopefully get the phone end of the year...
Click to expand...
Click to collapse
I will not buy it until it is rootable.
Nope, no luck as of yet... Nothing I seem to try is giving me any options or progress.
Rather frustrated carrying round 2 devices lol one for root apps and the s61 for everything else!
Still impressed at the phone though, VERY utilitarian!
Hey there, I will get my S61 tomorrow.
Was hoping for any root idea, but will hopefully survive without until we have the privilege to get it
... and there is no option in the programmer options (unlock bootloader)?
Did not stumble upon such a function yet.
The most annoying thing without root is missing a good ad blocking. dns66 seems to work, but there are still plenty of ads in apps that get through...
Also having potentially all power unlocked would be great!
So no news here I guess?
To enter bootloader:
1.switch of your phone
2.press volume down
3.conect the power cable
Does anyone refer to this thread?
https://forum.xda-developers.com/apps/magisk/how-to-install-magisc-twrp-locked-t3599926/page2
I've been looking at this phone for some time. I was able to get a Moto Z2 Force from Verizon into EDL mode with simple commands, so I'm wondering if you can unlock this bootloader just by telling it to unlock.
You would put the device into fastboot mode (by going to the bootloader, instructions were posted above i think), and then try some commands like this
fastboot flashing unlock
or
fastboot oem unlock
also check if in developer settings there is a toggle for Allow bootloader unlock or OEM unlock or w/e they call it.
if this works I highly suggest figuring out a way to grab the entire system to make a backup before you do anything. there's no twrp yet but it can't be too difficult to compile, but i dont have this $1000 waste of money to do any of this. i hope this post helps someone
james35888 said:
Does anyone refer to this thread?
https://forum.xda-developers.com/apps/magisk/how-to-install-magisc-twrp-locked-t3599926/page2
Click to expand...
Click to collapse
This doesn’t work since the boot loader is locked (stock boot loader has not been released on the web to my knowledge)
---------- Post added at 01:55 AM ---------- Previous post was at 01:38 AM ----------
Knuxyl said:
I've been looking at this phone for some time. I was able to get a Moto Z2 Force from Verizon into EDL mode with simple commands, so I'm wondering if you can unlock this bootloader just by telling it to unlock.
You would put the device into fastboot mode (by going to the bootloader, instructions were posted above i think), and then try some commands like this
fastboot flashing unlock
or
fastboot oem unlock
also check if in developer settings there is a toggle for Allow bootloader unlock or OEM unlock or w/e they call it.
if this works I highly suggest figuring out a way to grab the entire system to make a backup before you do anything. there's no twrp yet but it can't be too difficult to compile, but i dont have this $1000 waste of money to do any of this. i hope this post helps someone
Click to expand...
Click to collapse
Are these commands on a computer through ADB?
The only options I had on the phone were:
-Start
-Recovery Mode
-Restart Bootloader
-Power Off
-Boot to QMMI
-Boot to FFBM
Hi,
I looked a bit into the process of rooting on this device. It would be cool to get it rooted. I guess this process is in theory simple. But we should focus on the first problem:
Why is the option "OEM unlock" hidden in the developer Menu? Are there ways to make that option usable? If anyone has an idea how to make this option usable, we could get to the next step. Thanks to anyone who has an contribution.
Edit: some additional info
C:\adb\platform-tools>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
Finished. Total time: 0.000s
CatS61:/ $ getprop | grep oem
[ro.oem_unlock_supported]: [true]
[sys.oem_unlock_allowed]: [0]
Hello,
Let me tell you my story and perhaps someone will come up with a miracle solution for my problem.
I was trying to flash my device so: I opened developer options and enabled enabled USB debugging.
I though this was enough, but in the middle of the process I got some errors like "Preflash validation failture". So I went back and discovered that I had the fastboot locked and that in order to unlock it I should get a code from Motorola. I got the code, but when I was going to unlock it, I got another error saying that I can't unlock my flash boot since I didn't enable the check "Enable OEM Unlock" and at that moment was when I discovered I was screwed.
Someone said, that I was just a matter of downloading a Stock room, and repeat the process but I have downloaded tons of them and no luck.
At this point, I would try anything just to be able to open my phone in recovery mode because I can't do anything with it is dead,
I have read tons and tons of posts and all off them lead me to the same point, flash through fastboot repeat all the commands, but I have been there almost 100times. I'm about to get crazy.
If someone knows something, I will really appreciate it.
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
marceloariel said:
I am new to this, my phone also seemed unusable and with the application "miflash" through windows, I put the official rom and came back to life.
It also happened to me that I had to change the USB port on the PC so that it didn't fail me ...
(I am using a translator)
Click to expand...
Click to collapse
Thanks for the reply. I actually tried this as well but it did not work. MiFlash just appears to be running the flash_all_lock.bat script on Windows and it failed because the bootloader was not already unlocked according to its debug logs when I ran it. I should have mentioned that above.
Not sure if it will help but did you try a factory reset?
Press and hold the Power+Volume Down buttons untill you see the android with the no command. Press and hold the Power button. Press and release the Volume Up button once then release the Power button. Then you should see some recovery options.
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
dephekt said:
I followed the instructions here to unlock the A3 bootloader and these instructions to install TWRP and Magisk.
After toying around with things, losing Google Play certification and having push notifications in doze/app standby mode stop working, I decided to revert things back to stock and relock the bootloader.
Before modifying things, my phone was running the EU ROM with the November security patch: V10.3.12.0.PFQEUXM. I went here and downloaded the stock image archive for that version.
I use Linux, so I ran the flash_all_lock.sh script and everything seemed to work without any issues. There were no error messages and all the images seemed to be flashed successfully. At the end of the steps, the script locked the bootloader and the phone rebooted. It then showed the Android One logo for a second then immediately went into fastboot mode. I rebooted it again and this cycle repeated. If I tell fastboot to continue, I get this error:
Code:
$ fastboot continue
resuming boot...
FAILED (remote: Failed to load image from partition: Load Error)
finished. total time: 0.001s
I tried to reflash the images again, but I understandably get an error because the bootloader is locked now. Naturally, I tried to run the fastboot commands to unlock it again, but that also fails, presumably because I can't boot into the OS to toggle the developer option's "Allow OEM unlocking" switch:
Code:
$ fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.000s
At this stage, I throw up my hands in failure and presume the device is now totally bricked. After taking a few days to relax about it, I figured I would ask on here if anyone has any thoughts that could help. I fully expect the handset to need replaced and will accept the responsibility for breaking it, although I don't know how I managed to break it.
Is there some way to unlock the bootloader now when I'm not able to actually boot into Android to toggle the option to allow unlocking it? Is the device just FUBAR at this stage? I feel like there would be some way to fix this, but I'm at a loss as to how without some help.
Click to expand...
Click to collapse
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
sensig said:
Try
Code:
$ fastboot set_active a
. This is an issue with the flashing script. Before the line fastboot $* flashing lock command it should have fastboot $* set_active a. Your phone is not booting to system partition because the bootloader wasn't told which partition (a/b) to boot from.
Click to expand...
Click to collapse
The issue is caused by fastboot rom containing dummy system_b image and flashing script "forgetting" to force partition A as active. If a phone has B as an active partition and someone uses flash_all_lock.bat script, the phone's screwed. No idea what brought Xiaomi to this "brilliant" idea, not only there is a higher chance to brick the phone, but the zip file is also unnecessarily larger.
With locked bootloader it isn't possible to switch active partition anymore, so the phone is a (semi)brick. EDL mode is usually used to reflash locked bootloaders.
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
There are two commands for setting active partition, depending on the fastboot version. It's either old
fastboot set_active a
or newer
fastboot --set-active=a
debilinkredibile said:
Idk, but I was flashing stock again after failed attemp to flash pixel experiance.Partition was set to B, after flash it wont boot, but I dont know why fastboot set_active b wouldnt work so I had to flash TWRP get into twrp set partitoin to A and flash stock rom again. Try that
Click to expand...
Click to collapse
if you open flashing script file (.bat or .sh) in a text editor, you will see that fastboot is flashing system.img to system_a partition and system_other.img to system_b partition. That system_other.img is a dummy image and is not bootable. You either:
Option 1: Set active partition to A before running any stock flashing script.
Option 2: Replace system_other.img to system.img in the script.
Option 3: Force partition A after flashing userdata.img and before any lock or reboot command.
dephekt said:
In can't get the phone to boot into recovery. Holding power and volume down just speedily reboots the phone into fastboot over and over. Using the volume up button instead just reboots the phone very fast. I never see the no command android.
Click to expand...
Click to collapse
I am in the same exact position with my Mi A3... did you ever resolve this and if so how?
mewcatchew said:
I am in the same exact position with my Mi A3...
Click to expand...
Click to collapse
What causes led to this behavior ?
htn711 said:
What causes led to this behavior ?
Click to expand...
Click to collapse
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting). If I didnt know any better i'd think Xiaomi does this on purpose. I will never buy another Xiaomi.
Click to expand...
Click to collapse
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
mewcatchew said:
Stock rom was flashed in slot B instead of A and "flash all lock option" was checked off in mi flash (default setting).
Click to expand...
Click to collapse
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
garylawwd said:
You can't blame xiaomi for your negligence.
If you don't know what you are doing then either don't do it or ask people here on the forums or do some research yourself.
Of course xiaomi are going to have the flash all lock option enabled by default because the only time people would really use mi flash is to completely revert back to stock.
All information on miflash online will tell you make slot a active slot before flashing in mi flash.
Most manufacturers are the same nowadays anyway it's not just xiaomi.
All relevant information is there you just didn't read it/weren't careful when you flashed.
Don't ever be afraid to ask a question here on the forums if your not sure, you will get help even if you think the question is too noob or stupid.
You can always try get your system up and going through edl mode but you will need someone with a verified xiaomi account to help you.
Always read the relevant information before trying anything on your device.
To say you won't buy xiaomi again is silly seeing as it was a mistake on your behalf, "I cut my finger so that means all knives are crap" is kinda how it sounds
Click to expand...
Click to collapse
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
---------- Post added at 02:40 PM ---------- Previous post was at 02:30 PM ----------
htn711 said:
Due to the fact that i am a beginner in this business i also had my first encounter with the locked situation.
Did you read this: https://forum.xda-developers.com/showpost.php?p=81533691&postcount=22
...like garylawwd mentioned read/understand what you are doing BEFORE you do it.
After playing around with this device and read nearly everything about this topic here at xda i can say:
everything you need to know is here.
Click to expand...
Click to collapse
Did you read my posts? I get "locked state error" with fastboot commands. I can reboot bootlader in fastboot, and it tjust reboots into fastboot - thats just about all i can do. It wont let me change anything, can only get info and reboot...
mewcatchew said:
Theres always a fanboy in the crowd. Whoever programmed the batch file at Xiaomi made an error on wich slot it shouldve been flashed to. I've flashed devices a 100 times and never had an issue like this until i got a Xiaomi.
Now did I miss I needed to be on slot A? Yes I did. Still its Xiaomi's error for releasing botched firmware. How exactly do I find someone with EDL authorized account in US? If you have one, or if you can point me to someone who has one i'd be happy as a clam.
As a side note, my mother is from Cork.
Click to expand...
Click to collapse
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
garylawwd said:
Not a fanboy by any stretch of the imagination I just don't see it as an error on there behalf. They gave all relevant information on how to flash.
Someone already pointed out in a different thread of a guy that has the account here on XDA but I can't remember where I seen it. @_mysiak_ can you please let this guy know who has the verified mi account.
I hope you can get your device up and going and I do understand how frustrating this must be but it is fixable.
Hey maybe you can come visit Ireland with your mother and we can sort out the device then :laugh: joke
Click to expand...
Click to collapse
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
Ya I wouldn't go trusting some random Russian site either. I don't think there is anything you can do without either
A) going into edl and using a verified mi account
B) bringing it to a service centre (which nobody wants to do)
In fastboot you can't get any commands to work now right? Your device is fully locked again?
mewcatchew said:
mysiak did message me and I messaged the guy he pointed me to, havent gotten a response. Also pointed to a russian site that i dont trust.
Click to expand...
Click to collapse
That Russian site is run by the XDA guy from what I understood. There are other paid services which have Xiaomi service accounts, I only pointed you to the cheapest "verified" eshop. Just Google another one if you don't trust Russians. All of them will need to connect to your PC over Teamviewer and do the flashing, you will just follow the instructions (connect the phone, reboot it etc.).