Related
There's a bunch of threads about the bootloader unlock tool existing, not any real place to aggregate reports of problems with it. So, if you've attempted to unlock your bootloader using the official ASUS tool and are having problems, please post your situation.
Reported instances:
myself
DeathStolas
ASUS_Khang
Rattraps123
m3t4lw01f
creison
both are experiencing bootloader unlock limbo. The tool seems to have worked, but going into fastboot shows two progressive screens:
1) Unlock Successfully reboot in 5 seconds
2) FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Clearing the cache goes through the loop again. Mind you, this loop only happens when you're trying to get to the bootloader. If you go to recovery or normally boot, you won't have any issues.
However, any commands sent via fastboot fail, so the bootloader is still locked. Attached is an image of the second bootloader screen.
ASUS_Khang is already getting in touch with technical folks to investigate as well, but I figure it best to see if anyone else is having issues with the official tool.
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
I have to laugh at the fact that someone on XDA unlocked the bootloader successfully with none of these problems and then ASUS give an "Official Unlock Tool" that screws up the phone of any who uses it... In the words of Alanis Morrisett - "Isn't it Ironic"...
m3t4lw01f said:
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
Click to expand...
Click to collapse
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Same problem here. I used the official unlocker tool and it did what it said it was going to do, but... I got the mythical "Bootloader 5 sec reboot".
asus is working on a fix.
playingmax said:
asus is working on a fix.
Click to expand...
Click to collapse
I'm sure that they are, but it would be interesting to see a source for that claim.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
m3t4lw01f said:
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
Click to expand...
Click to collapse
Sounds good. Can't wait till this is all sorted out and I can continue on with installing Cyanogenmod for my SO. She is really excited since it's her first Android phone.
darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
here you go
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
look at Khang Thai (ASUS REP) reply. they are working on a fix.
Kona67 said:
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Click to expand...
Click to collapse
Same issue ... I tried without a pin .. now added a pin and it asked me for it when trying to run the app again ... but that didn't help !
Help Ausus!!!
Mine says unlock failed rebooting in 5,4,3,2,1.
any way to relock bootloader as zenfone 6,5,and 4 have
When the 5 second bootloader issue is fixed you should hear about it here first, we have an Asus employee helping us: http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
https://fsfe.org/news/2012/news-20121106-01.en.html
Enviado do meu iPhone usando o Tapatalk
Looks like a user has solved the 5 second reboot issue. Check out the rather convoluted method here: http://forum.xda-developers.com/showthread.php?p=63498472
Hello
I decided to start from scratch and installed latest stock rom with mi flash. The tool reported successful but I ended up in a boot loop. Somehow it failed when the screen came up with 'data encryption....'. I flashed it again ad the phone only vibrated when power on. I hat to do the restore point method to gain EDL mode. I flashed an older firmware. Now the screen stays black. I'm able to boot into fastboot, unlock the bootloader and install TWRP. But the screen is just blank/black.
I have a feeling it haves something to do with emmc_appsboot.mbn or boot.emmc.win
When I flash boot.emmc.win with fastboot on Slot A (I tried both slots) at least the LED turns on when the device is plugged on a USB cable. But nothing more........
I still have my backups, created by TWRP. I don't know this is in some way helpful.
I find the tool TWRP Backup Tool. It seems I could restore a TWRP backup from there. But which file should I use? My backup is a folder. There isn't any .zip or .img file.
Some ideas?
Same here
i can flash with edl mode
flash nougat rom stock for oem unlock
flash twrp ok
flash rom black screen:crying:
laugeek57 said:
Same here
i can flash with edl mode
flash nougat rom stock for oem unlock
flash twrp ok
flash rom black screen:crying:
Click to expand...
Click to collapse
can you do me a favour please? After the rom I flashed last night (yes, I guess it was a Nougat version) I was able to enter edl mode and unlock the bootloader. Today I tried other ROMs. Now, I forgot which Nougat version exactly worked for unlock boot loader. If you can post the exact version or a link would be great.
I don't think it's a hardware fault. I guess we need only the correct boot files. It should be possible to extract those files from a TWRP backup. But I can't find any hint how to do it.
If you find something that helps. please post it here. I'll do the same....
XtraWater said:
can you do me a favour please? After the rom I flashed last night (yes, I guess it was a Nougat version) I was able to enter edl mode and unlock the bootloader. Today I tried other ROMs. Now, I forgot which Nougat version exactly worked for unlock boot loader. If you can post the exact version or a link would be great.
I don't think it's a hardware fault. I guess we need only the correct boot files. It should be possible to extract those files from a TWRP backup. But I can't find any hint how to do it.
If you find something that helps. please post it here. I'll do the same....
Click to expand...
Click to collapse
Android 7.1.2 [N2G47H.7.8.23]
this version for unlocked bootloader
but after i'm always bootloops it's crazy
laugeek57 said:
Android 7.1.2 [N2G47H.7.8.23]
this version for unlocked bootloader
but after i'm always bootloops it's crazy
Click to expand...
Click to collapse
Thank you. I'll try it again. I also got bootloops, but the screen never turned on. As mentioed above, I was even able to install TWRP. And it booted into TWRP. But without a screen....
XtraWater said:
Thank you. I'll try it again. I also got bootloops, but the screen never turned on. As mentioed above, I was even able to install TWRP. And it booted into TWRP. But without a screen....
Click to expand...
Click to collapse
I try other version flash with twrp but what version for... good luck
VICTORY !!!
Flash Pixel Experience 12/17 with modem december my mi a1 debricked lol
but now i lost imei ....plus jamais xiaomi !!!
laugeek57 said:
I try other version flash with twrp but what version for... good luck
VICTORY !!!
Flash Pixel Experience 12/17 with modem december my mi a1 debricked lol
but now i lost imei ....plus jamais xiaomi !!!
Click to expand...
Click to collapse
How did you flash the OS? Because My screen is dark, so I can't see anything.
XtraWater said:
How did you flash the OS? Because My screen is dark, so I can't see anything.
Click to expand...
Click to collapse
If dark screen flash december modem but becarrefull i lost imei after
laugeek57 said:
If dark screen flash december modem but becarrefull i lost imei after
Click to expand...
Click to collapse
Thank you. I installed december rom. But screen is still black. Probably hardware defect.
XtraWater said:
Yes, the bootloader is unlocked. I'm able to enter into fastboot. From there I can flash TWRP and boot into recovery. I installed even Magisk. It seems everything to work, but the screen. I was very careful when I did the testpoint method.
Here's the result of the fastboot oem device-info:
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.047s]
Finished. Total time: 0.047s
Do you think there is still a chance to fix the device? I thought about to send the device back where I bought it. The device isn't even 2 week old. But I doubt the dealer will grant me warranty since I opened the device.
Edit: THe cellphone starts normally me thinks. If I want to boot into bootloader I have to press power and vol -
I run the TOOL ALL IN ONE which shows me immediately when a Fastboot device is detected.
Click to expand...
Click to collapse
What ROM do you install through the TWRP? Have you tried only to install a rom, without Magisk or GAPPS and wait if it boots properly?
samuro625 said:
What ROM do you install through the TWRP? Have you tried only to install a rom, without Magisk or GAPPS and wait if it boots properly?
Click to expand...
Click to collapse
After I was in bootloop (with screen) I wasn't able to unlock bootloader. So I used the Mi Flash tool. I tried different (at least 6 or 8 )versions from this site: https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
After flashing the roms, the phone only vibrated when tried to boot. It repeatedly vibrated when connected to the USB cable and charger.
Only one rom allowed me to enter fastboot and unlock the bootloader. Android 7.1.2 Nougat (N2G47H.7.8.23) ( https://xiaomifirmware.com/download/5117/ )
That's the rom which is currently on my phone.
I tried once to install the latest Oreo 8.1 with TWRP. Since my screen is black, I used the TOOL ALL IN ONE. The flash process was successful. But then again only vibration when try to boot.
Actually, in all those versions GAPPS or Magisk isn't included.
Just to mention; my Mi A1 is a MDG2. Not sure if that matters.
Without the screen, I'm kinda limited regarding to TWRP.
EDIT: I never did a backup by ADB. But I did several with TWRP. I wanted to recover one of them. But methinks, that's not possible with the TOOL ALL IN ONE.
Edit 2: I also made a TWRP backup from the Stock Oreo 8.1 version. It was the state on which the phone was delivered. I only did installation wizard like login to google account.....
The folder contains files like data.ext4.win000, data.ext4.win001, system.ext4.win000, system.ext4.win001. But once again, I don't know if this is helpful in any way.
XtraWater said:
(...)I wasn't able to unlock bootloader. (...) Only one rom allowed me to enter fastboot and unlock the bootloader. Android 7.1.2 Nougat (N2G47H.7.8.23) ( https://xiaomifirmware.com/download/5117/ ) That's the rom which is currently on my phone.
Click to expand...
Click to collapse
OK, we already know that it is with bootloader unlocked and in Nougat. That tells us 2 things: 1) It will not accept Stock Firmware until it blocks the bootloader and for now, that is not recommended. 2) You have to install a Nougat CustomROM, because to install Oreo you need to update the firmware.
XtraWater said:
I tried once to install the latest Oreo 8.1 with TWRP. Since my screen is black, I used the TOOL ALL IN ONE. The flash process was successful. But then again only vibration when try to boot.
Click to expand...
Click to collapse
Since the use of the AIO tool has not been effective, I would consider using the native firmware's own commands, especially flash_all.bat, which in theory leaves the cell phone as a factory and does not relock the bootloader.
Another aspect to keep in mind is that before decompressing the firmware file, rename it to a short one. It happened to me that a very long folder name was generated and the flashing was not completed.
Try this process with firmware N2G47H.7.8.23, using the instructions on the page that you mention, in the section "How to install Stock ROM (fastboot) on Xiaomi Mi A1"
XtraWater said:
Edit 2: I also made a TWRP backup from the Stock Oreo 8.1 version. It was the state on which the phone was delivered. I only did installation wizard like login to google account.....
The folder contains files like data.ext4.win000, data.ext4.win001, system.ext4.win000, system.ext4.win001. But once again, I don't know if this is helpful in any way.
Click to expand...
Click to collapse
For now these files are not useful, but do not erase them.
samuro625 said:
OK, we already know that it is with bootloader unlocked and in Nougat. That tells us 2 things: 1) It will not accept Stock Firmware until it blocks the bootloader and for now, that is not recommended. 2) You have to install a Nougat CustomROM, because to install Oreo you need to update the firmware.
Since the use of the AIO tool has not been effective, I would consider using the native firmware's own commands, especially flash_all.bat, which in theory leaves the cell phone as a factory and does not relock the bootloader.
Another aspect to keep in mind is that before decompressing the firmware file, rename it to a short one. It happened to me that a very long folder name was generated and the flashing was not completed.
Try this process with firmware N2G47H.7.8.23, using the instructions on the page that you mention, in the section "How to install Stock ROM (fastboot) on Xiaomi Mi A1"
For now these files are not useful, but do not erase them.
Click to expand...
Click to collapse
Ok, I did shorten the folder and file. The process flash_all.bat by itself was successful and I guess the phone rebooted. But still no screen. Still dark.
You mentioned to install a Nougat custom rom. Would you suggest a particular one?
XtraWater said:
Ok, I did shorten the folder and file. The process flash_all.bat by itself was successful and I guess the phone rebooted. But still no screen. Still dark.
Click to expand...
Click to collapse
I have a question: what images are seen on the screen? The logos of Xiaomi, the TWRP, others?
XtraWater said:
You mentioned to install a Nougat custom rom. Would you suggest a particular one?
Click to expand...
Click to collapse
Anyone who is allowed to install by TWRP, following the developer's instructions.
samuro625 said:
I have a question: what images are seen on the screen? The logos of Xiaomi, the TWRP, others?
Click to expand...
Click to collapse
Nothing. Absolute nothing. Even no LED when charging. The screen is just dead.
XtraWater said:
Nothing. Absolute nothing. Even no LED when charging. The screen is just dead.
Click to expand...
Click to collapse
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
samuro625 said:
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
Click to expand...
Click to collapse
They will see it. I tried with a common screwdriver. Since this didn't work, I bought a kit.
Well, bad luck.
However, thank you very much for your effort. That was very kind.
samuro625 said:
So, in this case, there is physical damage that I can not deal with. You could try using the warranty, but you should trust that the marks on the screws are not noticed.
Click to expand...
Click to collapse
A last question. If they replace the phone, I know, there chances are zero. Would I face the same issue if I want resurrection remix with the phone sound? Would I have to flash that modem.img?
If so, that's just not worth. It all started with that problem. Everything worked perfect but the phone.
XtraWater said:
A last question. If they replace the phone, I know, there chances are zero. Would I face the same issue if I want resurrection remix with the phone sound? Would I have to flash that modem.img?
If so, that's just not worth. It all started with that problem. Everything worked perfect but the phone.
Click to expand...
Click to collapse
Well, the truth, I never had any audio problem with calls with Resurrection Remix, and this rom I have used it in more than 6 phones of different manufacturers.
In my case, the problem of the calls was presented by flashing the modem of the version 8.1 of November, but downgrading to 8.0 was resolved.
Good luck with the cell phone, and it's a pity that it has been damaged.
It is advisable to learn to use the ADB and fastboot tools directly, rather than the AIOs.
Edit: May be this post can be usefull for you: https://forum.xda-developers.com/mi-a1/help/hard-bricked-phone-please-help-t3758606
samuro625 said:
Well, the truth, I never had any audio problem with calls with Resurrection Remix, and this rom I have used it in more than 6 phones of different manufacturers.
In my case, the problem of the calls was presented by flashing the modem of the version 8.1 of November, but downgrading to 8.0 was resolved.
Good luck with the cell phone, and it's a pity that it has been damaged.
It is advisable to learn to use the ADB and fastboot tools directly, rather than the AIOs.
Edit: May be this post can be usefull for you: https://forum.xda-developers.com/mi-a1/help/hard-bricked-phone-please-help-t3758606
Click to expand...
Click to collapse
Hello
I didn't give up so far. Something interesting happened.
I did the follow command: fastboot flash boot.emmc.win
The flash boot.emmc.win I extracted from my TWRP backup. Now, the phone rebooted and I hear a android notification. The charging LED is working too and the backlights of the buttons. When I touch the screen, the backlight of the buttons goes on. It looks like the phone is running. But, the screen is still off.
When I press the power button short, I hear the sound which indicates the screen goes off.
Tell me if I'm wrong, but with that behavior I think it isn't a hardware damage. Since still is Nougat installed, I might need a boot.emmc.win for Nougat?
We could be very close to fix the software.
EDIT: I used: fastboot boot boot.emmc.win
If I understand this correct, that way it is only temporary. So I tried:
fastboot flash boot_a boot.emmc.win
and
fastboot flash boot_b boot.emmc.win
With that, nothing happens. So, now again fastboot boot boot.emmc.win
Phone has restarted. I hear a sound. When touch the screen backligh of buttons goes on. I'm in a menu I guess. The installation wizard. I also hear the sound when I press something on the installation wizzard.
At least, that's new. Before there was nothing.
Edit 2: Might it be related to efs1.emmc.win and efs2.emmc.win ?
Edit 3: That's crazy. I touched the screen randomly and activated a 'Screen Reader' for blind people
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
cyrrel said:
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
cyrrel said:
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
Click to expand...
Click to collapse
can you explain us the procedures that you have followed to downgrade. It would be really helpful. i have tried this
method but it didn't work for me. i am facing IMEI 0/no signal issues using this method.
Thanks
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
cyrrel said:
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
Click to expand...
Click to collapse
Are your imei & mac same as original? won't the imei/mac get affected by restoring someone else efs?
I don't know about mac, but imei is ok
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
AOnePlus6TDestroyer said:
My OP6T had Ubuntu Touch (equivalent to Android 9) installed on it. When it broke, I tried to flash TWRP (version 3.3.1) to clear and reinstall Ubuntu Touch. For some reason it wouldn't boot, so I foolishly decided to flash TWRP onto every single partition. This only succeeded in breaking recovery mode. Following some advice I used the 6T MsmDownloadTool v4.0.58 (OOS v9.0.11), which fixed recovery mode, but not Android - it just showed the booting animation in a infinite loop (bootloop).
I've attached an image I found online showing the screen: bootloop
The issue is that I cannot flash in fastboot mode as the bootloader was relocked by MsmDownloadTool, *and* I cannot get into Android to enable OEM mode/USB debugging. I seem to have encountered a paradox where fastboot mode requires the permissions to be enabled in Android, but I can't boot to Android to enable those permissions, nor can I flash anything else to fix Android.
Is this possible to solve?
Click to expand...
Click to collapse
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
rogerrulez said:
You can try booting with the twrp.img. "fastboot boot name.img" using that ADB command. If that does not work the only other option is to completely retore your phone using msmdownload tool. This method will also depend on whether you have the international version or the T-Mobile version as there are different approaches depending on the type of phone. Read and study carefully how to proceed. If the msm tool does not work I'm pretty damn sure there are no other options.
Click to expand...
Click to collapse
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Only option now is to use msm tool again and hopefully get something working
Even with the bootloader locked you still should be able to boot the recocery image.
I have the 6T and 7T Pro. When I messed up my 6T my only hope was the msmdownloadtool. But make sure it's the right one.
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Brettroth said:
He can't boot into anything with bootloader locked. This is why msm tool sucks and people should stop recommending it for any little problem.
Click to expand...
Click to collapse
Are there more suitable tools for fixing a broken recovery mode? It did successfully do that.
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
How?
rogerrulez said:
When I had to use the msm download tool it did lock the bootloader. But I was able to unloack it again from the ADB command prompt at the bootloader screen by typing fastboot oem unlock. But this can only be done if it is set in developer options.
I spent alot of time trying to figure it out but later found outthat I was using the wrong msm tool.
Good luck. I hope you get it and running again because the 6T is still a very good phone.
Click to expand...
Click to collapse
Thank you! And yes, I tried that command but it is probably unset in the developer options (which I cannot reach, as Android isn't working anymore). I guess I'm using the incorrect version - how do you identify the correct one? I think I've used both the T-Mobile one and the other. I don't think the phone is T-Mobile, but I'm not sure how to identify whether it is or not.
It is very easy to convert a t-mobile variant to the international version. If you bought the phone used you would not know. One tell tale sign could be if you sim card holder supports either one or 2 sims. But that's not a sure way either because you can buy a replacement sim card holder. The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
As for the msm tool you would needd a modified version of that tool. You first use it to downgrade to Android 9. Then you have to upgrade that verion of android 9 to a slightly higher version before you are able to fully upgrade feely to 10 than 11 if you wanted.
If you have the international version pretty much and version of the msm tool would work but a modified version would be best.
However, the first step is to find out which variant you have.
When you used the msmdownload tool which version did you use, and did it finish the job ?
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
When I bricked mine I thought it was gone forever, I spent several days working on it but I was able to restore it. But I would never use the ubuntu rom on any phone that I care for.
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Brettroth said:
Wasn't sure about that. If that's the case, can you also flash from twrp then?
Click to expand...
Click to collapse
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
rogerrulez said:
No. Not without an unlocked bootloader. But booting into twrp would give you the ability to flash a ROM tho.
Click to expand...
Click to collapse
That's what I meant. Flash a ROM from twrp. Ok so if that works this guy can fix everything from there. Gonna be a hassle tho. Instead of rebooting to recovery I think you would have to shut off phone and fastboot boot back into twrp to change slots right?
Somehow I feel like that won't work but I'm not locking my bootloader to test it
rogerrulez said:
The fastet was would be to look up the IMEI # and see what variant of the 6 you have.
Click to expand...
Click to collapse
I'm afraid I can't' find it... It is dual-sim though.
rogerrulez said:
When you used the msmdownload tool which version did you use, and did it finish the job ?
Click to expand...
Click to collapse
I used a few - both T-Mobile and not. They all succeeded with (seemingly) no error, but didn't fix the bootloop.
rogerrulez said:
If you have the t-mobile vesion there is a thread on here that gives you step by step instructions to convert from t-mobile to international along with the links to download the software. And even the modified version will know what variant you have simply by not working.
Click to expand...
Click to collapse
I see, but won't that need me to be in Android to be able to run the software?
rogerrulez said:
If you are able to get into the bootloader than you have a great chance of fixing your phone. Your phone is bootlooping so that tells me you can access the bootloader screen.
Click to expand...
Click to collapse
Yup, fastboot and recovery mode work fine. The bootloader is locked though, else installing TWRP, etc. would be easy.
rogerrulez said:
When you are at this level it is very important you proceed with caution and don't just start flashing anything you can find. It will nake matters much worse.
Click to expand...
Click to collapse
Yeah...
rogerrulez said:
Even with the bootloader locked you still should be able to boot the recocery image.
Click to expand...
Click to collapse
It doesn't do it automatically. Is there another way to boot it?
Brettroth said:
Somehow I feel like that won't work but I'm not locking my bootloader to test it
Click to expand...
Click to collapse
As far as I can tell there's no way to flash TWRP without unlocking the bootloader. And there doesn't seem to be any way to do that without getting into Android. And I can't get into Android...
Someone else suggested using this tool (https://github.com/bkerler/edl) as a last-ditch attempt. I'm going to give it a try and hope for the best!
Thank you both for your suggestions.
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
yurtal said:
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
Click to expand...
Click to collapse
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
zgfg said:
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
Click to expand...
Click to collapse
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
yurtal said:
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
Click to expand...
Click to collapse
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Oh ok. Yes I'll read up on it. Thanks for your help.
zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Hey, just to follow up. I managed to get it back up and running from someone with EDL support.