Database Users

[HELP] I would like to go into developer options but I can not

Hello to all,
first of all sorry for my English, i'm using google translate, I do not know if you can help me here.
I bought this jewel from Gearbest and arrived yesterday.
I would like to unlock the bootloader and root it following this wonderful guide , but I can not get into developer options, I get the error "the settings application crashed abnormally"
I wanted to do this via the toolkit, but in EDL mode the phone is not recognized, maybe because in developer options I have to select the OEM UNLOCK.
The only good thing is that it recognizes usb debugging mode (at least I think) because I see the debug notification icon.
I can not understand where it came from, I went into bootloader mode but did not release me information.
From the onscreen screen I can only provide these info:
model number zte a2017g
version android 6.0.1
kernel version 3.18.20
build number zte a2017gv1.0.0b11
baseband version th.2.0.c1.9-00050-m8996faaaanazm
The MiFlavor version is 4.0
The smartphone does not receive OTA updates. I downloaded the global version (b05) of Nougat, the update with Android started I did not find it (I renamed the rom file in update.zip and put in the root of the SD CARD). I tried through recovery mode but it does not do anything to me, it's as if the smartphone was locked in everything and for everything.
I'm doing well ? How do I update when I download the rom? Can you please help me? Is there any system to interact with this smartphone and unlock it? I do not want to keep a phone that I can not update and root it.
Thanks in advance to who will help.

UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?

SuDGLaD said:
UPDATE:
I tried to manually install the downloaded ROM, but in recovery mode it does not flash the new rom ... the phone does not even try it !!!
It's as if the phone was locked in everything and I only have to keep the installed rom.
Some idea ?
Click to expand...
Click to collapse
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!

JTruj1ll0923 said:
Hey I would recommend clearing the data for settings if you can. To do this go to your launcher, find the settings icon and either drag or hold down or do whatever it takes to get to the app info. I haven't used stock in a long time so idk. But then go into storage and clear data. Then go and try again.
I do have one question though. How did you get usb adb debugging enabled if you didn't get into developer options at all?
For the second half of your question you won't be able to flash anything without first unlocking the bootloader and flashing TWRP onto the device. For the devices recovery idk which one you meant, but it needs to be TWRP. Good luck!
Click to expand...
Click to collapse
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?

SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
What rom are you trying to install? Usually you will be absolutely fine.

SuDGLaD said:
Thanks to my friend, without doing anything, suddenly, he made me enter the developer options menu.
I've been able to do the rest.
Now I have the phone with unlocked bootloader, root and TWRP installed.
Do not ask me how I got the debug without going into the menu, I could not answer you ... it will remain a mystery !!!
I take advantage of your availability: can I flash the zip of the official ROM through TWRP? Or is there a risk that the phone goes into brick mode?
Click to expand...
Click to collapse
JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done

JTruj1ll0923 said:
What rom are you trying to install? Usually you will be absolutely fine.
Click to expand...
Click to collapse
Thanks :good:
Choose an username... said:
You can't flash an official zip through TWRP, it will just fail. No brick.
Edit: didn't read OP lol. If you want to update, you have to flash the stock recovery (there are stock recovery flashable zips on the Download Center) then install the update, then get TWRP again. Or you can install a custom ROM (I recommend one based on stock MiFavor 5.0, I think that the best one is ADM Team V3 (the one that's not based on B13), this way you can simply download, flash in TWRP, and you'll be done
Click to expand...
Click to collapse
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).

SuDGLaD said:
Thanks :good:
Thanks mate !!
I installed the rom that you suggested to me, I find it very good, but this phone has very poor support (MiFavor).
Click to expand...
Click to collapse
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...

Choose an username... said:
Very poor support? It's going to get Android O, and it's got at least 1 update per month (officially). It's unclear whether that ROM you installed will be updated since it's based on an older version, but the latest (B13) breaks a bunch of stuff like Google Play Games, Maps, the GPS works awfully...
Click to expand...
Click to collapse
No no ... do not get me wrong.
My reference is to rom, MiFlavor is really bad. I come from 3 Xiaomi smartphones and I can assure you is another world.
The smartphone is really nice and well balanced (apart from the just enough battery) and I would replenish it a thousand times. :fingers-crossed::good:

Screen Not Responsive After Flash ..... +

Hey,
I've been on quite a journey since I attempted to flash the Treble rom for newbies. My phone eventually ended up as DFU'd but, I brought it back to life after a following the DFU Unbrick - Disassembly guide. After doing this, the screen was not responsive to touch at all at the Welcome screen of the EDU ROM. So, my adventure continued as I took the phone apart several times again to make certain things were connected, not damaged, etc..
After flashing TWRP I concluded the screen itself must be fine because I could use TWRP using the screen/touch. I have since tried flashing several different roms, tried many combos of unlocking the bootloader (again, because I assume it was already unlocked due to the bootloader warning screen of can not check for corruption message), tried flashing bootstack and the stock rom from DrakenFX. Used MiFlash, EDM Tool to flash various items.
Each time and currently, when it boots to the Welcome screen it does not respond to touch.
Can anyone please help me with this?
Thank you!

I remember this happened to me some years ago with a different phone, and it was a bad flash.
I resolved it by flashing the stock firmware again.
What did you flash with MiFlash? Stock firmware untouched? You must do this, try with B35 untouched. Don't flash stuff with TWRP.

Untouched? Is there anything on here like that?

https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011

bornlivedie said:
https://androidfilehost.com/?fid=962187416754472312 B35 A2017U
https://androidfilehost.com/?fid=746010030569960045 B10 A2017G
https://www.androidfilehost.com/?fid=818070582850490196 B14 A2017CN
Those are "untouched" system images. Replace recovery.img with a proper TWRP version before flashing:
https://androidfilehost.com/?fid=673956719939822011
Click to expand...
Click to collapse
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!

djprez said:
Yeah, unfortunately the very first link (since I am in the USA and have a U version) is the very stock EDL version I used with MiFlash rightg after I was successful getting the phone out of DFU. I have tried flashing it twice after and still nothing.
Thank you for helping!!!
Click to expand...
Click to collapse
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support

bornlivedie said:
Sad to hear that... Maybe you can try again? Who knows, with a little bit of luck...
Or try another version, like this one:
https://www.androidfilehost.com/?fid=890129502657579386
btw, did you try every single spot in your screen while in TWRP? Maybe some pins in the connector are broken and some parts work and others doesn't?
And for the sake of it, you could try discharging your battery completely.
Last thing I can think of... is to restore the stock recovery and apply the official update via sdcard:
https://www.dropbox.com/s/xy7nd252f3rcm5y/338450B3220A2017UV1.1.0B35(SD card software).zip?dl=0
It was taken from here:
https://www.zteusa.com/axon-7#support
Click to expand...
Click to collapse
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard

djprez said:
Yeah, the entire screen works perfectly in TWRP. I disassembled it several times before when I thought I may have put it back together wrong or damaged something so, the battery was removed those several times therefore, no power.
I'll try the stock above. I'm actually trying another stock rom atm --- flashing from sdcard
Click to expand...
Click to collapse
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.

djprez said:
Well, EUREKA! I found I had saved the first files you were supposed to load when the Axon was first unlocked ( file name STEP_1_3-B20_FULL_OTA). Flashed it and the screen works fine. Now, I have to remember how to update it...lol I've unlocked the bootloader in Developer mode and I should be on my way..... fingers crossed.
Click to expand...
Click to collapse
Strange.
Nevertheless, congratulations. Happy for you.

Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!

Restore to stock firmware your phone came shipped with.After that update trough ota or sd card package and maybe dont flash Treble again,its broken

djprez said:
Well, it's great that I now know the screen/hardware is fine but, I am unable to get any further than version B20. OTA doesn't work, the other files to flash (STEP_4-B20_to_B27 and STEP_5-B27_to_B29) won't flash and get aborted due to it expecting a certain version. I've tried DrakenFX Bootstack and then Stock System and it boots to the Welcome screen but the screen is no longer responsive again.
I have been at this all day again and it's shaping up another all night too. I am so baffled!
Click to expand...
Click to collapse
i wish i had seen this sooner, because i have this same exact problem on one of my boards. it will update perfectly to any of the MM sd card update files (see rootjunkys bl unlock video, thanks @Tomsgt) but the board/phone will not retain touch functionality on anything higher than mm b29. i had lost my imei on that board, and actually swapped to another one despite eventually regaining it simply bc i wanted to be on Oreo ROMs. if you find a fix, id love to know about it. i flashed and reflashed every update, sd card versions, edl versions, and OTA updates to no avail. Nougat or above, touchscreen didnt work... mine was a gold a2017u. good luck, man. im glad im not crazy.

Sorry to bump an old(er) thread I started. I wanted to ask if anyone has found a solution to this issue yet?
I have since tried updating using OTA to Nougat and the screen doesn't respond so, I had to flash back to Marshmallow B29. Thank you to anyone who might have an idea!

[SM-T585] Unable to root, multiple methods

Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.

Smellfungus said:
Hi guys,
So, this is a last resort. I've followed a number of different guides and methods, but nothing has worked. The closest "success" I've had is with a Chainfire auto root; it flashes, it breaks Knox, but I still don't have SU. Could it be because I don't have an SD card? I saw it as a prerequisite in some guide but didn't really put much stock in it as that was a single mention which also involved loading it with verity, which I'm more interested in removing.
I've also tried twrp, which that looked like it had bricked my device, though I managed to recover it by flashing the auto root again. I'm speculating that it's something to do with the latest updates, but really I'm just clueless and frazzled after 4+ hours of wracking my brains. I'm not sure what other info you'd find helpful anymore without going full splurge, so I'll keep it sweet and let you question me or berate me for my vile, witholding ways as you see fit. Any help is greatly appreciated!
Edit:
My SU checker says that I've not got the binaries or root user account. The .tar from firmware.mobi is only 54mb. I tried turning off suhide, but changed no other options. Trying to use fastboot straight up fails, the device isn't recognised after adb booting (despite having tried the correct drivers and some random others multiple times over.) I've been unable to locate a release for the T585 on twrp site, though a version is out there on these forums from a year or so back.
Click to expand...
Click to collapse
The only way I know of to successfully root a Tab A is by flashing TWRP and then using it to flash SU or Magisk. What version of TWRP are you using and what version of Odin? Using the correct ones won't brick a T585.

When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:

Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.

webzo said:
I am about to try this.... was you device on Android 7 (nougat) or Android 8 (Oreo) when you did this?
Thanks for your time.
Click to expand...
Click to collapse
I honestly don't remember
But it should work on either one - only difference now is that we have an official recovery that can be downloaded from twrp.me directly :highfive:

Nimueh said:
When I got my Tab A a couple of weeks ago I did a LOT of reading first ... but then it took less than 24 hrs from receiving it to having it rooted + running RR Oreo
Following the guide HERE I enabled OEM Unlocking and installed Odin.
Using Odin I flashed twrp-3.2.3-4-gtaxllte-OMNI6.tar from HERE.
Using the freshly installed TWRP I flashed RR-O-v6.2.1-20181210-gtaxllte-Unofficial.zip from HERE, Gapps from HERE and the latest Magisk from HERE.
That was it - rooted and ready to go :victory:
The first guide pretty much covers all the steps you need, I simply used a different TWRP version. You can't brick your device flashing TWRP unless you flash something that's not for your device. Make SURE to enable OEM Unlock first - and don't use SuperSU but Magisk.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.

webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.

webzo said:
Ok, so I went ahead and tried with the latest TWRP (3.3.1.1), RR (v7.0.2).
Everything seemed to go well..... except, tablet is now stuck in boot animation. It won't startup.
I double checked and I don't think I missed any steps.... Any ideas on what I can try?
Thanks.
Click to expand...
Click to collapse
Update:
I tried to restore the backup via TWRP and ended up with a "unable to mount /system" error.
My /system partition was showing zero size.
Many wipes and restores didn't help.
Eventually, what seemed to help was to choose repair the system partition, change file system to FAT, change file system back to ext4. Saw it in a youtube video- https://www.youtube.com/watch?v=T-7neHzSIvc
After /system error was fixed, I did an install of RR again and it went smooth.
All is well now.
Hope this helps someone.

webzo said:
Does this need twrp-3.2.3-4-gtaxllte-OMNI6.tar to go from Oreo to Pie?
I am not finding -OMNI.tar anywhere. All links are dead.
Can I use a newer version of TWRP?
Thanks.
Click to expand...
Click to collapse
Back then we had no working official version and the Omni6 one was the only one without issues. Now we have the official and it should work just fine.
No idea why you had those problems, but I'm glad you got it all sorted

Hard brick Mi A1?

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

OnePlus 6T - Can't unlock bootloader nor get into Android

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.