Hello friends,
I would kindly ask you to try to help me un-brick my Mi Pad 5 (nabu). Thanks in advance.
First of all, let me give you some info what happened and what I have/haven't tried:
HOW IT GOT BRICKED:
1. Installed Awaken OS, it went great and fast and was setting up the tablet
2. Installed Magisk Module and activated it, it went great
3. Started installing modules which I use, it went great
4. Found a post on Awaken OS thread from the user nabulsi08 about some modules that he uses and decided to try Mi Sound and Miui Core which he attached and claimed that it was safe to use with that ROM.
5. My tablet was connected to my computer via USB and it asked to re-confirm that I would like to have USB debugging ON, but I ignored the notification in hurry and rebooted the device in order to activate mentioned modules.
6. Phone got stuck on MI logo, not forwarding to boot animation of the ROM at all.
WHAT HAVE I TRIED:
1. I have tried to clean re-install the ROM, but now, when I wanted to check ADB devices, it is not showing my device at all since USB debugging was left unticked.
2. I was able to enter FASTBOOT and downloaded Mi Flash Tool (latest version and also tried several older versions) and Fastboot ROM (both v13 and v12.5), installed all drivers, started flashing the Fastboot ROM(s) but it was all successfully done in less then 3 seconds and nothing was changed, still stuck on MI logo.
3. The same thing whichever option I select - Clean all / Save user data / Clean all and lock in Mi Flash Tool
4. Found some tutorials online, changed the location of Fastboot ROM to C:/, renamed the rom to short name, nothing helped, 1-3 seconds and it says success but nothing changes
5. Also tried to change USB cable, USB port, nothing helped.
6. Also tried copping all files from IMAGE folder to ADB folder and tried starting flash_all.bat script but it does not start at all.
7. CMD command fastboot devices shows my device, but command adb devices does not show anything (again, due to the USB debugging off)
8. After something that I did, not sure what, I think that I was able to restore stock recovery, as I now can see the recovery screen (with TWRP it is not possible, you do everything via CMD) and options like Wipe Data, Mi Assistant, etc.
9. Found online a way to enter EDL mode (if I am not wrong), it restarts from fastboot and enters the recovery screen but the tablet is again visible in Mi Flash Tool just like when you are in fastboot mode, tried flashing Fastboot ROM from EDL as well, again 1-3 seconds and ''success'' without any actual success.
WHAT WAS NOT TRIED:
1. I do not know how to flash file by file from IMAGE folder using CMD as you need to know what file represents what exactly (for example: fastboot flash system ____________,img, - not sure which file represents system, and this is the case for all files). My knowledge is not that high.
2. I am using Windows 11, I will try tomorrow on Windows 10 as well, maybe that will fix the issue.
3. Whichever is not mentioned above and you suggest
My device is not shown under Device Manager of Win11. All drivers installed as requested by Mi Flash Tool.
I am not sure if this is soft or hard brick of the device, seen online that if you are able to enter Fastboot and/or Recovery it should not be hard brick of the phone/tablet, but really not sure because of that USB Debugging thing. I have had so much similar issues in the past with Xiaomi and with other brands of phones, but was always able to fix the issues with online tutorials. In this case, I think that I tried almost everything that I have found, but nothing helps. Just wanted to mention that before Awaken OS, I was using ArrowOS for several months, and just wanted to change and try Awaken as I have seen that it gets good feedbacks from users. Also, it is not needed to mention but I will anyway, bootloader is unlocked, but you knew that since I was doing the customizations already.
So guys, all in all, I spent 3 full days trying everything I was able to find, in a very cold room where my PC is located without any success, but I might be able to catch a cold. I would really need your help, assist, support, suggestions.
Thank you all in advance for reading this awfully long post and for your kind suggestions.
I had a similar problem when going from AwakenOS (without magisk) to MIUI.
It seemed impossible to flash with different methods, though fastboot mode working on the tablet.
Finally I was able to restore MIUI (fastboot version) with the latest Mi Flash Pro (Win10), see here.
UniNick said:
I had a similar problem when going from AwakenOS (without magisk) to MIUI.
It seemed impossible to flash with different methods, though fastboot mode working on the tablet.
Finally I was able to restore MIUI (fastboot version) with the latest Mi Flash Pro (Win10), see here.
Click to expand...
Click to collapse
I have also tried that Mi Flash Pro, today, but on Win11, it gets me to the same place with Mi Flash Tool, and I again have the same issue - done in less then 3s and false "success". Thanks anyhow, I will be able to try with Win10 tomorrow, maybe it makes some difference.
Shoomyrovich said:
Hello friends,
I would kindly ask you to try to help me un-brick my Mi Pad 5 (nabu). Thanks in advance.
First of all, let me give you some info what happened and what I have/haven't tried:
HOW IT GOT BRICKED:
1. Installed Awaken OS, it went great and fast and was setting up the tablet
2. Installed Magisk Module and activated it, it went great
3. Started installing modules which I use, it went great
4. Found a post on Awaken OS thread from the user nabulsi08 about some modules that he uses and decided to try Mi Sound and Miui Core which he attached and claimed that it was safe to use with that ROM.
5. My tablet was connected to my computer via USB and it asked to re-confirm that I would like to have USB debugging ON, but I ignored the notification in hurry and rebooted the device in order to activate mentioned modules.
6. Phone got stuck on MI logo, not forwarding to boot animation of the ROM at all.
WHAT HAVE I TRIED:
1. I have tried to clean re-install the ROM, but now, when I wanted to check ADB devices, it is not showing my device at all since USB debugging was left unticked.
2. I was able to enter FASTBOOT and downloaded Mi Flash Tool (latest version and also tried several older versions) and Fastboot ROM (both v13 and v12.5), installed all drivers, started flashing the Fastboot ROM(s) but it was all successfully done in less then 3 seconds and nothing was changed, still stuck on MI logo.
3. The same thing whichever option I select - Clean all / Save user data / Clean all and lock in Mi Flash Tool
4. Found some tutorials online, changed the location of Fastboot ROM to C:/, renamed the rom to short name, nothing helped, 1-3 seconds and it says success but nothing changes
5. Also tried to change USB cable, USB port, nothing helped.
6. Also tried copping all files from IMAGE folder to ADB folder and tried starting flash_all.bat script but it does not start at all.
7. CMD command fastboot devices shows my device, but command adb devices does not show anything (again, due to the USB debugging off)
8. After something that I did, not sure what, I think that I was able to restore stock recovery, as I now can see the recovery screen (with TWRP it is not possible, you do everything via CMD) and options like Wipe Data, Mi Assistant, etc.
9. Found online a way to enter EDL mode (if I am not wrong), it restarts from fastboot and enters the recovery screen but the tablet is again visible in Mi Flash Tool just like when you are in fastboot mode, tried flashing Fastboot ROM from EDL as well, again 1-3 seconds and ''success'' without any actual success.
WHAT WAS NOT TRIED:
1. I do not know how to flash file by file from IMAGE folder using CMD as you need to know what file represents what exactly (for example: fastboot flash system ____________,img, - not sure which file represents system, and this is the case for all files). My knowledge is not that high.
2. I am using Windows 11, I will try tomorrow on Windows 10 as well, maybe that will fix the issue.
3. Whichever is not mentioned above and you suggest
My device is not shown under Device Manager of Win11. All drivers installed as requested by Mi Flash Tool.
I am not sure if this is soft or hard brick of the device, seen online that if you are able to enter Fastboot and/or Recovery it should not be hard brick of the phone/tablet, but really not sure because of that USB Debugging thing. I have had so much similar issues in the past with Xiaomi and with other brands of phones, but was always able to fix the issues with online tutorials. In this case, I think that I tried almost everything that I have found, but nothing helps. Just wanted to mention that before Awaken OS, I was using ArrowOS for several months, and just wanted to change and try Awaken as I have seen that it gets good feedbacks from users. Also, it is not needed to mention but I will anyway, bootloader is unlocked, but you knew that since I was doing the customizations already.
So guys, all in all, I spent 3 full days trying everything I was able to find, in a very cold room where my PC is located without any success, but I might be able to catch a cold. I would really need your help, assist, support, suggestions.
Thank you all in advance for reading this awfully long post and for your kind suggestions.
Click to expand...
Click to collapse
Hey,
firstly as long as you can enter Fastboot Mode, your device isn't completly Hard Bricked. In WHAT I'VE TRIED I see that you tried flashing the stock ROM. This was the solution that came into my mind first and actually it should be the only solution to unbrick your device. 3 seconds and succes? This should take like 450 seconds. The device Manager doesn't to recognize your device you said. That's weird but if the Mi Flash Tool recognizes the device in Fastboot Mode, flashing should work anyway. The Windows Version should not be the problem. I've done that with Win 10 and 11. It's hard to say what to do now and that's why I would ask you to tell me if you have Discord. You could share the screen. It would be much easier for me to see what the problem is and I can write with you there. And please try installing the latest Mi Flash Tool from here: https://xiaomiflashtool.com/ Download the latest Version with the Label NEW. Extract the folder into C:, not the extracted folder into another folder. Hope we will get your device working again soon.
nabulsi08 said:
Hey,
firstly as long as you can enter Fastboot Mode, your device isn't completly Hard Bricked. In WHAT I'VE TRIED I see that you tried flashing the stock ROM. This was the solution that came into my mind first and actually it should be the only solution to unbrick your device. 3 seconds and succes? This should take like 450 seconds. The device Manager doesn't to recognize your device you said. That's weird but if the Mi Flash Tool recognizes the device in Fastboot Mode, flashing should work anyway. The Windows Version should not be the problem. I've done that with Win 10 and 11. It's hard to say what to do now and that's why I would ask you to tell me if you have Discord. You could share the screen. It would be much easier for me to see what the problem is and I can write with you there. And please try installing the latest Mi Flash Tool from here: https://xiaomiflashtool.com/ Download the latest Version with the Label NEW. Extract the folder into C:, not the extracted folder into another folder. Hope we will get your device working again soon.
Click to expand...
Click to collapse
Hello, I have the discord, but haven't used it for a long time, let me try to connect and then I will edit my response and let you know my username and we can talk.
Shoomyrovich said:
Hello, I have the discord, but haven't used it for a long time, let me try to connect and then I will edit my response and let you know my username and we can talk.
Click to expand...
Click to collapse
Okay. I've edited the Comment with the Modules too so hopefully nobody gets the same issue as you.
Shoomyrovich said:
Hello, I have the discord, but haven't used it for a long time, let me try to connect and then I will edit my response and let you know my username and we can talk.
Click to expand...
Click to collapse
I have created a Server you can join so you can share your Screen. Just join this: https://discord.gg/ufD9dsZ7
nabulsi08 and myself tried several different roms and things to fix it but without luck. After the call I managed to find Win10 PC and now it is going, 500s elapsed and counting hopefully, it will be done, but now I get more and more optimistic. It was just about Windows. Do not do the flashing on Win11.
Shoomyrovich said:
nabulsi08 and myself tried several different roms and things to fix it but without luck. After the call I managed to find Win10 PC and now it is going, 500s elapsed and counting hopefully, it will be done, but now I get more and more optimistic. It was just about Windows. Do not do the flashing on Win11.
Click to expand...
Click to collapse
Windows 11 may not to be to blame.... Were you using a Ryzen pc/laptop originally? That can sometimes affect things, was the Windows 10 device Intel based? Also using USB 2.0 rather than 3.0 can affect things too...
So dude, what's the verdict... Are you fixed now?
reg66 said:
Windows 11 may not to be to blame.... Were you using a Ryzen pc/laptop originally? That can sometimes affect things, was the Windows 10 device Intel based? Also using USB 2.0 rather than 3.0 can affect things too...
So dude, what's the verdict... Are you fixed now?
Click to expand...
Click to collapse
Completely opposite. First win11 computer was intel based, i3 processor, and fhe second one, Win10 was AMD Based - Ryzen 5 processor. Finally, everything went fine and the issue was solved. Really couldn't believe that that can make a difference.
Shoomyrovich said:
Completely opposite. First win11 computer was intel based, i3 processor, and fhe second one, Win10 was AMD Based - Ryzen 5 processor. Finally, everything went fine and the issue was solved. Really couldn't believe that that can make a difference.
Click to expand...
Click to collapse
Oh wow, to my knowledge ryzen can sometimes be the issue. Surprised it came down to a windows 11 issue, but we live and learn! I'm also on awaken with a windows 11 pc, hope I don't have the same issues when i change...
Really glad you're up and running again tho bud. Happy flashing
reg66 said:
Oh wow, to my knowledge ryzen can sometimes be the issue. Surprised it came down to a windows 11 issue, but we live and learn! I'm also on awaken with a windows 11 pc, hope I don't have the same issues when i change...
Really glad you're up and running again tho bud. Happy flashing
Click to expand...
Click to collapse
Thank you so much bro. I am currently on the stock MIUI 14 but I know myself, will root it and customize for sure, but probably change to to Awaken at the end again but no more sound magisk modules for me...never ever .
Shoomyrovich said:
Thank you so much bro. I am currently on the stock MIUI 14 but I know myself, will root it and customize for sure, but probably change to to Awaken at the end again but no more sound magisk modules for me...never ever .
Click to expand...
Click to collapse
Not encouraging you to, but I was using Magisk Delta when I had the same issue with Miui Core module. After changing to Magisk 26 official all was good again and have Miui Core plus MiSound module working now for Dolby...
Shoomyrovich said:
Thank you so much bro. I am currently on the stock MIUI 14 but I know myself, will root it and customize for sure, but probably change to to Awaken at the end again but no more sound magisk modules for me...never ever .
Click to expand...
Click to collapse
Just want to say I am sorry again. Still don't know what the issue was. I've tried to figure it out. @reg66 seems to have no issues with any of those Modules too.
reg66 said:
Not encouraging you to, but I was using Magisk Delta when I had the same issue with Miui Core module. After changing to Magisk 26 official all was good again and have Miui Core plus MiSound module working now for Dolby...
Click to expand...
Click to collapse
I have edited the Comment with the Modules so everybody knows that I am not responsible for any bricks. I've mentioned that it doesn't seem to work with Magisk Delta too.
Shoomyrovich said:
Completely opposite. First win11 computer was intel based, i3 processor, and fhe second one, Win10 was AMD Based - Ryzen 5 processor. Finally, everything went fine and the issue was solved. Really couldn't believe that that can make a difference.
Click to expand...
Click to collapse
I have to say that I don't think Windows was the issue. I've flashed everything on both Windows Versions several times and never had any issue. It may be the PC that has something that causes this problem. At least we got your device working again.
Related
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Dulu93 said:
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Click to expand...
Click to collapse
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
k0rax said:
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
Click to expand...
Click to collapse
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
i dont think so.. tried a few different cables
Dulu93 said:
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Click to expand...
Click to collapse
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
k0rax said:
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
Click to expand...
Click to collapse
i can only find die x.15 version but i think it should be enough. the problem is that ze2 is not reacting to pc commands when in bootloader.. so i can not operate in with fastboot commands and asus flash tool requires fastboot mode
maybe my last option is to flash my phone via intel phone flash tool which operates via the soc. but i dont have the necessary files. as i remember i would need some flash.xml and image
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Dulu93 said:
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Click to expand...
Click to collapse
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
---------- Post added at 06:29 AM ---------- Previous post was at 06:21 AM ----------
k0rax said:
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
Click to expand...
Click to collapse
This did:
Make sure you go to settings-->apps-->default apps and select the dialer as your default application to make calls.
k0rax said:
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Click to expand...
Click to collapse
thank you very much for your help.
the first point chaning it to 4 zeros did the trick. i was able to reinstall the bootloader.
but i still dont have connectivity via fastboot. im sure all drivers are installed and even on linux i cant see my phone. what is that special google driver?
k0rax said:
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Click to expand...
Click to collapse
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Dulu93 said:
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Click to expand...
Click to collapse
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
k0rax said:
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
Click to expand...
Click to collapse
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
k0rax said:
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
Click to expand...
Click to collapse
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
You can leave flash tool and xfstk open same time. I flashed with xfstk, waited some time and moves between the bootloader options. Make sure no residual adb or fastboot exes are running. Then unplug the phone and plug it back in. Then it will show up. Select the option you have and click start. See if the bootloader shows any life or incoming partitioning happening . If that doesn't work reboot to bootloader scroll around in it to make sure it's loaded , it brings in the correct serial intermittently. But I don't think it's necessary.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
So xfstk reboots
Xfstk round two no reboot scroll around
AFT
Unplug USB from phone and reconnect
Should show up .
Then click start. Did it give an error with that X?
Look at processes and see if it's launched adb or fastboot
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
I think you're close - it's flashing what's needed, and recognized the phone, although it did for me also but fastboot didn't work until the drivers with adb and fastboot. The last things I would think is reinstall the Google adb fastboot drivers with the phone connected to the USB port that got you this far, and if there is some serial no verification, look for .14 version of AFT.
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3485186
Having the exact same Problems with my OP3 running everything stock 3.2.7 expect for the fact the device is unlocked...
Would love to hear how the problem can be solved!
ELoTRIX said:
http://forum.xda-developers.com/showthread.php?t=3485186
Click to expand...
Click to collapse
Hmmm Windows 7.
I can most certainly try that but the real question now is; how the hell did it work previously on my Windows 10 machine and refuses to work now? But at least I have a solution to try out, in the mean time! Thanks!
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
I am having a similar issue. I have a brand new OP3. Everything stock. I'm attempting to unlock the bootloader and have found that while ADB recognises the phone, Fastboot doesn't. I'm pretty sure it's a driver issue and I have no idea how to fix.
Hello
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
abhi0502 said:
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Click to expand...
Click to collapse
I'm afraid you've missed the point, my friend.
If the phone does not get detected in the fastboot, it means I cannot flash anything, period. No original TWRP, no modified TWRP.
I had this exact issue and fixed it.
Fastboot would never see my device, no matter which driver package I tried or no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers, which blocks the fastboot driver. If you're seeing "Kedracom" or "Android Device" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. Here's the howto for Win10: http://www.howtogeek.com/167723/how-...igned-drivers/
Once you've done this, on the next reboot you can do a forced install of the unsigned fastboot drivers you downloaded for the OP3. And simply rebooting your computer restores the security feature.
It's mostly because of the windows security over unsigned drivers.. Try the above method or just the cmd way..
Sent from my Xiaomi Mi 5 using XDA Labs
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Raeffion said:
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Click to expand...
Click to collapse
First of all, TWRP doesn't work.
This link would help you to restore your device
https://forum.xda-developers.com/oneplus-7t/how-to/op7t-unbrick-tool-to-restore-device-to-t3994835
Raeffion said:
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Click to expand...
Click to collapse
I had a similar, but not as terrible experience when first attempting to get root on the 7T using the patched boot images that you used. I tried several other patched boot images, but none of them would allow the device to boot. I downloaded the full update of 10.0.5, then extracted the boot.img and it allowed me to boot the device again. Then I patched it in Magisk Manager, and everything went fine and I have root. If you have fastboot access, you can try booting your device using these images with the command fastboot boot boot.img or fastboot boot magisk_patched.img to see if your device even boots up from the images. I got stuck booting from partition b at one point, and used the command fastboot getvar current-slot to see the active partition, then I used the command fastboot --set-active=a to set partition a instead. If those commands fail then you need to update to the latest adb and fastboot and the commands will work.
This is the stock boot.img for the H1905 7T update version 10.0.5:
https://www.dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
This is the Magisk patched version of the same boot.img:
https://www.dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
SkippRunning said:
If you have fastboot access, you can try booting your device using these images with the command fastboot boot boot.img or fastboot boot magisk_patched.img to see if your device even boots up from the images.
Click to expand...
Click to collapse
I've attempted both, I was still in a bootloop sadly.
SkippRunning said:
I got stuck booting from partition b at one point, and used the command fastboot getvar current-slot to see the active partition, then I used the command fastboot --set-active=a to set partition a instead. If those commands fail then you need to update to the latest adb and fastboot and the commands will work.
Click to expand...
Click to collapse
My current partition was still in partition A.
Aswin08 said:
This link would help you to restore your device.
Click to expand...
Click to collapse
My first try with the unbrick tool didn't even sense my phone. I saw the FAQ and then tried to find the Qualcomm drivers in my device manager to no avail, although I did find Kedacom drivers which I could not even attempt to flash over since Windows told me that the driver I was trying to push was out of date. Here is my original post on that thread:
Raeffion said:
I see neither QDLOADER 9008 nor QHUSB_BULK in my device manager and my device is not detected by the MSMDownloadTool. I do see, however, a Kedacom USB device in my device manager titled "Android Bootloader Interface". I just want to be sure that I should download the driver you provided onto my phone before I brick it any further.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
As you can see, I did not yet mention that I still tried pushing the driver since I haven't had a reply yet. I don't want to double-post there but I'm getting no luck elsewhere. I really want this tool to work, is there some way to force push these drivers or is that a bad idea? If it is, any other ideas?
EDIT: Nevermind. I think it's bricked pretty good, I'll probably have to give up on this. When I plug it in, it only goes to bootloader, doesn't boot into recovery, system, or even show the battery percentage when charging. Bootloader hasn't been giving me many options either since the commands I've tried aren't going through. Updating ADB right now, don't know if it's likely that it's causing issues right after I already updated it.
Raeffion said:
I've attempted both, I was still in a bootloop sadly.
My current partition was still in partition A.
My first try with the unbrick tool didn't even sense my phone. I saw the FAQ and then tried to find the Qualcomm drivers in my device manager to no avail, although I did find Kedacom drivers which I could not even attempt to flash over since Windows told me that the driver I was trying to push was out of date. Here is my original post on that thread:
As you can see, I did not yet mention that I still tried pushing the driver since I haven't had a reply yet. I don't want to double-post there but I'm getting no luck elsewhere. I really want this tool to work, is there some way to force push these drivers or is that a bad idea? If it is, any other ideas?
EDIT: Nevermind. I think it's bricked pretty good, I'll probably have to give up on this. When I plug it in, it only goes to bootloader, doesn't boot into recovery, system, or even show the battery percentage when charging. Bootloader hasn't been giving me many options either since the commands I've tried aren't going through. Updating ADB right now, don't know if it's likely that it's causing issues right after I already updated it.
Click to expand...
Click to collapse
Are you starting the programs as an Administrator?
SkippRunning said:
Are you starting the programs as an Administrator?
Click to expand...
Click to collapse
Yeah, tried it again for good measure. Is there any chance I could get this issue resolved spending less than $100 by sending it to a OnePlus repair center or elsewhere? I'm not sure they do software repairs such as this, I didn't purchase a warranty since I figured I'd root this phone and I no longer know my IMEI since I can't access the phone to check.
Raeffion said:
Yeah, tried it again for good measure. Is there any chance I could get this issue resolved spending less than $100 by sending it to a OnePlus repair center or elsewhere? I'm not sure they do software repairs such as this, I didn't purchase a warranty since I figured I'd root this phone and I no longer know my IMEI since I can't access the phone to check.
Click to expand...
Click to collapse
Ive never sent my devices in for service so Im not sure about that. The fact that you have access to fastboot still though makes me think that you arent totally screwed yet. When I had stuff go wrong and I went to use to MSM tool, I didnt have the proper drivers installed, and my device never showed up in device manager. After installing a different set of drivers and rebooting my pc, the device showed up in device manager under the Ports section. I was able to get back into my device without the unbrick tool by switching the active partition. Did you say you already checked your active partition with command fastboot getvar current-slot? If you are on slot a, have you tried setting slot b as the active and seeing what happens? This is the command fastboot --set-active=b.
Here is a driver for the unbrick tool to recognize your device that might work for you. https://www.dropbox.com/s/lgt1qanfqs8pvbe/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0
SkippRunning said:
Did you say you already checked your active partition with command fastboot getvar current-slot? If you are on slot a, have you tried setting slot b as the active and seeing what happens? This is the command fastboot --set-active=b.
Click to expand...
Click to collapse
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
SkippRunning said:
After installing a different set of drivers and rebooting my pc, the device showed up in device manager under the Ports section. I was able to get back into my device without the unbrick tool by switching the active partition.
Here is a driver for the unbrick tool to recognize your device that might work for you.
Click to expand...
Click to collapse
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
EDIT: I installed the driver but nothing has changed from before. The MSM tool still doesn't detect my phone, I made sure it was run as Administrator. My device drivers are still Kedacom which I attempted to update the driver using a file on my computer once again and Windows wouldn't allow it. Am I simply looking in the wrong place to manually install this driver? My device manager is set to view devices by type and plugging in my phone causes only the Kedacom USB device to appear, so I assume I don't have QDLOADER 9008 or QHUSB_BULK devices listed there. I can provide screenshots of my device manager window if it helps.
Raeffion said:
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
Click to expand...
Click to collapse
Hooray! Almost haha! It is the worst feeling when you mess up your brand new device, but as long as I have fastboot I dont stop trying to fix my mistakes. You should be able to fix it for sure.
---------- Post added at 04:35 AM ---------- Previous post was at 04:21 AM ----------
Raeffion said:
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
EDIT: I installed the driver but nothing has changed from before. The MSM tool still doesn't detect my phone, I made sure it was run as Administrator. My device drivers are still Kedacom which I attempted to update the driver using a file on my computer once again and Windows wouldn't allow it. Am I simply looking in the wrong place to manually install this driver? My device manager is set to view devices by type and plugging in my phone causes only the Kedacom USB device to appear, so I assume I don't have QDLOADER 9008 or QHUSB_BULK devices listed there. I can provide screenshots of my device manager window if it helps.
Click to expand...
Click to collapse
On my pc, I didnt have any issues with the drivers, but when I was helping a friend over TeamViewer trying to do the same thing you are trying to do, the drivers just didnt help no matter what and it wasnt listed in the device manager. I was able to make it show properly on his pc by using the steps explained in this article. https://docs.microsoft.com/en-us/wi...boot-configuration-option?redirectedfrom=MSDN After restarting his pc, the device showed up properly in device manager with test mode enabled.
Are you able to access adb now, or still only fastboot?
SkippRunning said:
Are you able to access adb now, or still only fastboot?
Click to expand...
Click to collapse
I embarrassingly don't even really remember all the specifics about how ADB works, although I don't think I have access since I'm in a bootloop when I launch Android. Unless I have access to ADB via fastboot or recovery, I don't think I do.
SkippRunning said:
On my pc, I didnt have any issues with the drivers, but when I was helping a friend over TeamViewer trying to do the same thing you are trying to do, the drivers just didnt help no matter what and it wasnt listed in the device manager. I was able to make it show properly on his pc by using the steps explained in this article. After restarting his pc, the device showed up properly in device manager with test mode enabled.
Click to expand...
Click to collapse
Yeah I had no idea what Windows test mode was. Before I rebooted just now to install the drivers you provided, I actually launched into Windows test mode with no command from me telling Windows to. I thought Windows invalidated my license yet again tbh, glad to know it didn't. I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Raeffion said:
I embarrassingly don't even really remember all the specifics about how ADB works, although I don't think I have access since I'm in a bootloop when I launch Android. Unless I have access to ADB via fastboot or recovery, I don't think I do.
Yeah I had no idea what Windows test mode was. Before I rebooted just now to install the drivers you provided, I actually launched into Windows test mode with no command from me telling Windows to. I thought Windows invalidated my license yet again tbh, glad to know it didn't. I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Click to expand...
Click to collapse
It will just make driver installing issues less likely. When you boot your phone, what happens on the screen? Does it get stuck on a certain screen or just restart over and over? You can see if adb can see your device with the command adb devices, and it should list your device. If not, try fastboot devices and it should be listed. You need to put the device into EDL mode for the unbrick tool to work, and for it to be shown in device manager. My friends device manager listed Kedacom just like yours, and I didnt do anything to that at all. I just used test mode, installed the Qualcomm drivers, put the phone into EDL mode and the unbrick tool should recognize it. If your phone is listed when you type adb devices, you can use command adb reboot edl to enter that mode needed for the unbrick tool.
Raeffion said:
I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Click to expand...
Click to collapse
Sadly my drivers haven't changed. I uninstalled and reinstalled the installation file you gave me since I first installed it via WWAN-DHCP instead of ETHERNET_DHCP. I use a VPN so I figured that may have affected the installation, although for some reason I didn't think to just turn off the VPN when I reinstalled. Regardless, I don't think my VPN or the way I installed the driver is the cause of the drivers mentioned not being found in my device manager, so I'm likely not going to bother.
Raeffion said:
Sadly my drivers haven't changed. I uninstalled and reinstalled the installation file you gave me since I first installed it via WWAN-DHCP instead of ETHERNET_DHCP. I use a VPN so I figured that may have affected the installation, although for some reason I didn't think to just turn off the VPN when I reinstalled. Regardless, I don't think my VPN or the way I installed the driver is the cause of the drivers mentioned not being found in my device manager, so I'm likely not going to bother.
Click to expand...
Click to collapse
Another problem that can cause your phone to not show up in device manager is the usb port you are using. Have you tried any other ports? Are you able to shut your phone all the way off by holding power until it turns off? If you can unplug the phone and turn it off, then hold the volume up and volume down buttons together, then plug the cable back into the phone and it should put it into EDL mode.
SkippRunning said:
When you boot your phone, what happens on the screen? Does it get stuck on a certain screen or just restart over and over?
Click to expand...
Click to collapse
It just shows the boot animation, it doesn't restart.
SkippRunning said:
You can see if adb can see your device with the command adb devices, and it should list your device. If not, try fastboot devices and it should be listed.
Click to expand...
Click to collapse
ADB shows no devices attached, fastboot shows my device.
SkippRunning said:
You need to put the device into EDL mode for the unbrick tool to work, and for it to be shown in device manager. My friends device manager listed Kedacom just like yours, and I didnt do anything to that at all. I just used test mode, installed the Qualcomm drivers, put the phone into EDL mode and the unbrick tool should recognize it. If your phone is listed when you type adb devices, you can use command adb reboot edl to enter that mode needed for the unbrick tool.
Click to expand...
Click to collapse
I seem to have been missing a vital part of information. I don't know why the term "EDL" just went over my head, I probably just associated it was fastboot mode when I looked it up. How do I get into EDL mode? Is it safe to assume the method listed here works for the OnePlus 7T?
Raeffion said:
It just shows the boot animation, it doesn't restart.
ADB shows no devices attached, fastboot shows my device.
I seem to have been missing a vital part of information. I don't know why the term "EDL" just went over my head, I probably just associated it was fastboot mode when I looked it up. How do I get into EDL mode? Is it safe to assume the method listed here works for the OnePlus 7T?
Click to expand...
Click to collapse
Fastboot mode and EDL mode are two different things. I have never used the fastboot to EDL method, but I have read about it and I assume it should work atleast on some devices. Unplugging from pc and turning the phone off, then holding both volume buttons and then plugging the cord into the device should enter EDL mode without commands.
SkippRunning said:
Fastboot mode and EDL mode are two different things. I have never used the fastboot to EDL method, but I have read about it and I assume it should work atleast on some devices. Unplugging from pc and turning the phone off, then holding both volume buttons and then plugging the cord into the device should enter EDL mode without commands.
Click to expand...
Click to collapse
I must have assumed that it was fastboot mode since when I held those buttons and plugged it in, I'd always launch into fastboot mode. Perhaps it's different with the US version? That's the version I have.
Raeffion said:
I must have assumed that it was fastboot mode since when I held those buttons and plugged it in, I'd always launch into fastboot mode. Perhaps it's different with the US version? That's the version I have.
Click to expand...
Click to collapse
The only version I have used at all is the US one. You could try holding both volume buttons for a few seconds before plugging the cable into the phone, but if that doesnt work you can try the fastboot to edl method. I have no experience with it at all though so I dont know if it works with this device or not, but you would just open the edl.cmd file and it should put the phone into edl mode.
https://www.dropbox.com/s/951fm98u5rd2kjr/FASTBOOT-EDL-MODE.zip?dl=0
SkippRunning said:
The only version I have used at all is the US one. You could try holding both volume buttons for a few seconds before plugging the cable into the phone, but if that doesnt work you can try the fastboot to edl method. I have no experience with it at all though so I dont know if it works with this device or not, but you would just open the edl.cmd file and it should put the phone into edl mode.
https://www.dropbox.com/s/951fm98u5rd2kjr/FASTBOOT-EDL-MODE.zip?dl=0
Click to expand...
Click to collapse
It just boots me into Android sadly. I don't know that there's any way to get into EDL mode for me. Possibly due to my use of the experimental TWRP and mauronofrio's Stock Fastboot ROM tool.
Raeffion said:
It just boots me into Android sadly. I don't know that there's any way to get into EDL mode for me. Possibly due to my use of the experimental TWRP and mauronofrio's Stock Fastboot ROM tool.
Click to expand...
Click to collapse
What happens if you use command fastboot boot boot_stock_10.0.5_US.img using this file?
https://www.dropbox.com/s/cl9l662xkyey5oq/boot_stock_10.0.5_US.img?dl=0
SkippRunning said:
What happens if you use command fastboot boot boot_stock_10.0.5_US.img using this file?
Click to expand...
Click to collapse
No dice.
It was only a matter of time before my first brick with this phone. Earlier this evening I tried to factory reset from TWRP and clean flash latest OOS, but it spewed out a whole bunch of partition errors. After various efforts, here's the current status: It won't boot to the OS from either slot. TWRP says no OS installed. On Slot A, it won't boot to recovery either, and the only thing I can get to is fastboot. On Slot B, I can get to TWRP recovery, but all storage is gone (and I've since done a full wipe so there's nothing on it anyway). Any attempts to do adb push or sideload result in the error "adb: error: failed to get feature set: no devices/emulators found", so I can't install anything unless there's another way I'm not aware of.
I'm trying to get into EDL by powering off the phone, then holding down both volume buttons while I plug in the USB cable. It shows up in Device Manager for about 2-3 seconds as "Qualcomm QDLOADER 9008" and then disappears for a second before going directly into fastboot. I've rebooted my computer to disable device driver signing and install the latest Qualcomm drivers per this guide, but the latest drivers are already installed. I've tried a different USB cable and a different USB port.
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
terlynn4 said:
1) Is there another way to get into EDL mode?
2) Is there anything else I can try from TWRP, adb, or fastboot?
Click to expand...
Click to collapse
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Fishawy said:
Was in the same situation few days ago on my 8 Pro not the 9 Pro. Couple of things you could try:
1. The new TWRP had a "Reboot to EDL" option in the advanced section for the first time. Check if the 9 Pro TWRP has the same.
2. My device was only going into fastboot & could boot TWRP, with the same QUALCOMM crashdump error. It would auto power-up the second a cable is inserted, I had to try many reboot-to-EDL programs out there but none worked as the device was playing up. Keep trying MSM.
3. This is weird, but it's what worked with me. The 11.0.4.4 MSM for 8 Pro failed to recognise my device altogether, it's 11.0.3.3 one that worked. With that one, it didn't read the device until maybe the 10th trial. So see if different MSM versions are available for the 9 Pro, and again keep trying MSM.
Good luck.
Click to expand...
Click to collapse
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
terlynn4 said:
Thanks for the suggestions. I did try the "Reboot to EDL" option but it didn't work for me. And I think we only have one MSM version for this model so far. I'll keep trying till it works or I figure something else out.
Click to expand...
Click to collapse
You don't have to stick to one model. You can use MSM of 11.2.2.2 EU or 11.2.4.4 India for example, then flash the stock update of a different region, as long as it's an upgrade not the same version.
I did upgrade from 11.0.6.6 AA to 11.0.8.8 EU locally on my 8 Pro. I would imagine it's the same, haven't tested it on my 9 Pro yet though.
I finally got it flashed back to OOS via TWRP and booting normally again. However, it concerns me that I couldn't ever get EDL working, in case I ever really need it. I'll have to keep working on that "just in case".
After trying several things in various orders, I reformatted /data, after which adb push started working. I was able to push the latest full .zip and after a couple more errors I was able to flash it to both slots and reinstall TWRP. I did get an error when I went to reboot that said something like "No OS installed... are you sure you want to reboot?" however it booted into the OS that time.
Anyway, thanks to those who offered suggestions. I'll update again if I ever figure out what's wrong with EDL.
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Steve0007 said:
Use All in One tools. Working really good as far as I can see. Choose Oneples 8 pro device since not updted for Oneplus 9 / Pro. There is an option to reboot to EDL thru this tool.
Click to expand...
Click to collapse
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
terlynn4 said:
Seems like a great tool... however, I just tried it and get the same behavior when I use the Reboot to EDL option. It shows up as a Qualcomm device in Device Manager for a couple of seconds and then reboots to system (now that I have a functional OS). It never shows up in MSM Tool.
Click to expand...
Click to collapse
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Samuel Holland said:
Hi, I noticed when using the 64 version of Qualcomm driver, my phone would auto boot out of EDL as soon as it would enter it. I had to use a nother version I believe is 32 bit version. That fixed the problem for me. Also usually it's the boot that is messed up when something goes wrong and replacing that will usually fix and if not; replacing correct boot and then wiping data is what worked for me.
Click to expand...
Click to collapse
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
terlynn4 said:
Well, you're definitely onto something, but there's still a missing piece. After installing 32-bit drivers I'm able to get the phone into EDL mode... screen is blank and "Qualcomm QDLoader 9008" shows up in device manager, and it actually stays there without the phone trying to boot on its own. However, the phone still doesn't show up in MSM. In device manager it has a yellow triangle and says the driver isn't signed, even though I installed it after doing the advanced reboot to allow unsigned drivers.
Where do you download the latest version of the 32-bit driver from? Maybe the one I found isn't the latest?
Click to expand...
Click to collapse
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Samuel Holland said:
I can't remember where I got it from , I believe from 8t forum? I've had it on my Google drive for quite some time. If you would like me to share it I could. I don't remember if I added to the name originally. The name on the file is
Qualcomm_USB_Host_Drivers_1.00.53_20180705_w7_w10(8t_link).exe
Click to expand...
Click to collapse
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
terlynn4 said:
I didn't find that version, but I did find a [presumably] newer version 2.1.0.3 32-bit driver that appears to work. The device now shows up in MSM Tool. Thanks for the help!
Click to expand...
Click to collapse
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Fishawy said:
Can you share a link for that updated 32-bit driver?
If what Samuel Holland suggested is valid in my case as well, that would get rid of the auto-boot issue we struggled with.
Click to expand...
Click to collapse
The one that worked for me was the 32-bit setup.exe file from this guide. I uninstalled the existing driver I had installed, rebooted, installed this driver, and then EDL worked right away.
Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
"I know that I won't get any unlock at the moment as the wait period is not over. "
You managed to start the unlock timer using the tool though?
I think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after. (you load fastboot with power - & volume?)
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
sathariel74 said:
Hey there,
sorry for the undescriptive title, but I really don't know what is going on. I received my new Poco F3 on tuesday and since then I am trying to make some progress with unlocking the bootloader. I went through the steps:
- enable developer options
- download the Flash tool from Xiaomi
- enable OEM unlock and USB debugging
- registering a new Mi account
- pairing the Mi account from the phone in Dev-Options/Mi-Unlock Status (while on data with the same SIM and phone number used in my Mi Account).
I tried it from various computers and with different cables. Somehow the phone is not detected when in Fastboot mode. Here are some things I tried (tbh - I really can't recall everthing I tried):
- installing ADB tools in Linux and Windows
- Using the XiaoMiTool V2
- installing various USB driver found in the net on WIndows
- Using an older version of the Mi Unlock Tool from their website (4.5.813.51) as there where USB drivers included.
- "unpaired" and paired my phone with the Mi Account, also detached the Mi account from the phone and reattached it.
I know that I won't get any unlock at the moment as the wait period is not over. However I expect at least that I see an error message indicating that I need to wait for X-hours longer or something. But in the various tools the phone doesn't even appear when in fastboot mode.
Using Linux and XiaoMiTool was the "most successful" method - but even here the fastboot mode was not recognized. I just got a "Service Token invalid" message - which looked like it is caused by not having a connection to the fastboot mode.
At least I now figured out that it is totally normal that devices in fastboot have "d00d" as idProduct, because this was what changed when I attached the phone in normal mode (idProduct=4ee7).
Running "adb devices" in fastboot also doesn't show anything (Windows and Linux).
I fear that I may ended up in a trap like with my first phone - the Samsung S2 i9100g - that was the "same" but different from the "normal" S2. Is there something known? Using CPU-Z I see that the CPU seems to be at least a SM8250 - so that looks promising. The Model is M2012K11AG (alioth_eea) if that helps anything.
Any hints, tips, suggestions on how to proceed are welcome I am flashing my phones since almost 10 years, so I should be able to make this work here too, right?
Thanks
Click to expand...
Click to collapse
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google... Then click on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Mother_Teresa said:
You managed to start the unlock timer using the tool though?
Click to expand...
Click to collapse
Well, I don't see any timer in the tool. However the new flash tool doesn't seem to promising (that batch one). Also in XiaomMiTool I don't see any timer. So maybe the registration is already messed up?
Mother_Teresa said:
think at first I had the same worry of it not being recognized (adb devices never worked) but as it did show in both the unlock tool and the flashtool and managed booting (fastboot boot x.img) to twrp.img recovery also after.
Click to expand...
Click to collapse
Well, this one does not work for me as it is locked...so I suppose this is a dead end at the moment. Tried this in Linux (I am more comfortable with).
Mother_Teresa said:
(you load fastboot with power - & volume?)
Click to expand...
Click to collapse
Yes, I actually do that usually (besides of the automatic Fastboot loading from XiaoMiTool).
Mother_Teresa said:
Plugging it in when booted and/or in fastboot should result in some connected sound. I trust you checked in the system devices if the device got installed/recognized?
Click to expand...
Click to collapse
Yes, it gives some connected sound in both modes (normally booted - can even mount the phone storage - and in fastboot). Not sure about the device correctly installed when in fastboot - I tried to follow some threads/videos on that but somehow it looked different for me.
X0PIRAT3 said:
I'm you're saver !!!!
Download this : https://www.mediafire.com/file/lv98wac50a2dexz/MiFlash20210226.zip/file
Extract it launch the exe then u see drivers like qualcomm,google..; Clique on install when u see a pop up in chinese close all see if fastboot is recognizing you're device
ALSO LATEST ADB AND FASTBOOT VERSION : https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Click to expand...
Click to collapse
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
sathariel74 said:
...
Thanks! I may try those out (not sure if I can make this during the weekend).
EDIT: The drivers from @X0PIRAT3 really did the trick! I just installed them and tried it. Now it says 165 hours wait time (it maybe 3 hours that I last tried to rebind my account during trouble shooting!). Thanks a lot to you 2! You are really genius!
Click to expand...
Click to collapse
Yay, well done.
I kept default MIUI and rooted with Magisk (install this in Magisk app to fix safetynet pass).
More details here.
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
sathariel74 said:
Well, I can endure a lot but not MIUI - its not my kind of android. I will go for LineageOS initially I think Lets see what surprises come up, luckily I still have my 5T.
Click to expand...
Click to collapse
Not to bash etc but what is so bad?
I installed my preferred launcher (Nova) and it works for being a familiar front-end.
Options and tweaks are mostly there these days in the settings (fe. flashlight on double-press) and if not there is root.
is it bloatware? (if so, can we fix it? )
Lineage is of course a safe bet and I probably end up trying some but I need some encouragement .
BTW: beware the Miu Flash tool not enabling 'lock device' when flashing.
edit: how to use smileys. Now it seems super happy but without it seems so serious....
Well, besides of lack of trust (which is most likely just my issue), I really dislike that "all at startscreen" quite a lot. And yes, those 20-30 apps that I was able to delete plus the 20 apps I would like to delete are another thing showing me that this ROM is not for me. Especially that memory manager stuff that enables your "high performance game experience" is a sign to better stop using MIUI. There are also some bugs (strange behaviour I saw/felt - can't even really describe) I didn't like.
I like to manage my stuff myself, even if this is more work. But I somehow know how its "glued" together. So LineageOS is what I like. Or some of the other AOSP ROMs available.