Related
I unlocked the bootloader, root, but when i plug in my xperia play holding search button i get:
18/049/2011 19:49:21 - INFO - <- This level is successfully initialized
18/049/2011 19:49:34 - ERROR - Device connected in normal mode.
18/049/2011 19:49:34 - ERROR - Drivers need to be installed for connected device.
18/049/2011 19:49:36 - INFO - Device connected with USB debugging off
I have to do this if i want clockworkmod recovery and install doomlord kernel right? Please help me i'm trying to learn as fast as i can
Thats flashtool, it has nothing to do with fastboot :|
Sent from my R800i using Tapatalk
AndroHero said:
Thats flashtool, it has nothing to do with fastboot :|
Click to expand...
Click to collapse
And? How do I install a custom kernel? To flash the kernel i have to be in fastboot mode :S but my crappy w7 makes a sound like *du-du-du* and not *du-di!* like when you connect an usb cable
To flash a custom kernel, you use the android sdk. Copy the boot.img to the same folder as fastboot.exe fire up a command prompt. Hold back on device and connect usb cable, then type "fastboot flash boot boot.img into the prompt.
Sent from my R800i using Tapatalk
doesn't work, I hold back and plug in the phone, but it's flash mode; and when i type fastboot flash boot boot.img it just says < waiting for device > and after around 50 sec it exit from flash mode what am i doing wrong?
hold down the search button when turning on...
search button for fastboot mode and back button for flashmode. Use gordongate drivers if you intend to flash. They are supplied with the the flashtool package.
i've installed gordon's gate drivers and the pc recognize the phone in flash mode but fastboot mode still not working
here's the log, first i tried with flash mode and then with fastboot mode but it says error:
20/019/2011 17:19:43 - INFO - <- This level is successfully initialized
20/019/2011 17:19:51 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
20/019/2011 17:19:52 - INFO - Device Status: NOT FOUND
20/019/2011 17:19:53 - INFO - Finished Fastboot Toolbox
20/023/2011 17:23:07 - INFO - Device connected in flash mode
20/023/2011 17:23:49 - INFO - Device disconnected
20/024/2011 17:24:02 - INFO - Device connected with USB debugging off
20/024/2011 17:24:09 - INFO - Device disconnected
20/024/2011 17:24:18 - ERROR - Device connected in normal mode.
20/024/2011 17:24:18 - ERROR - Drivers need to be installed for connected device.
20/024/2011 17:24:20 - INFO - Device connected with USB debugging off
Are you running Windows 7, I had a nightmare with the usb drivers-even the Gordon gate one didn't work-I found the solution in the arc forum, sorry but I can't find the post I think users name was lollylops, check your device manager to see if you have s1boot driver problem if so then you need the different drivers
Sent from my R800i using xda premium
yes i'm running windows 7, and i've found this: http://forum.xda-developers.com/showthread.php?t=1274199 and downloaded drivers for s1boot fastboot from that thread. Now, how do I install them? I've an x86 folder, ethernet, modem, usbwin, i386.... i've no idea, but i think we're close
Celluciano said:
yes i'm running windows 7, and i've found this: http://forum.xda-developers.com/showthread.php?t=1274199 and downloaded drivers for s1boot fastboot from that thread. Now, how do I install them? I've an x86 folder, ethernet, modem, usbwin, i386.... i've no idea, but i think we're close
Click to expand...
Click to collapse
no offence but if you don't no how to install drivers on windows you should not unlock your bootloader
Sent from my R800i using Tapatalk
fma965 said:
no offence but if you don't no how to install drivers on windows you should not unlock your bootloader
Click to expand...
Click to collapse
no offence but i've already unlocked my bootloader with test point
Unfortunately I have the memory of a goldfish, I think that you have to put the phone into fastboot then goto device manager on the pc and update the drivers for s1boot by pointing to where you have put the drivers,
Sent from my R800i using xda premium
fma965 said:
no offence but if you don't no how to install drivers on windows you should not unlock your bootloader
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I had a nightmare with this, it seems some versions of Windows 7 are fussy with certain fastboot drivers, it sound like the op is struggling the same way I did, I was close to giving up until I came across drivers that worked
Sent from my R800i using xda premium
Ok i managed how to install them through device manager. I select the folder but it says (translated to english) : "Device's driver has been found, but an error occurred during the installation. Android ADB Interface - Impossible to find the specified file. WHAT!?
EDIT: PROBLEM SOLVED here's how: http://forum.xda-developers.com/showthread.php?t=1299729 i dowloaded drivers from here and they worked but now i've some QUESTIONS:
1)With unlocked bootloader (i kept drm certificates) and root, can i update trough OTA?
2)Now i'm going to flash doomlord kernel: has it the recovery integrated?
Celluciano said:
Ok i managed how to install them through device manager. I select the folder but it says (translated to english) : "Device's driver has been found, but an error occurred during the installation. Android ADB Interface - Impossible to find the specified file. WHAT!?
EDIT: PROBLEM SOLVED here's how: http://forum.xda-developers.com/showthread.php?t=1299729 i dowloaded drivers from here and they worked but now i've some QUESTIONS:
1)With unlocked bootloader (i kept drm certificates) and root, can i update trough OTA?
2)Now i'm going to flash doomlord kernel: has it the recovery integrated?
Click to expand...
Click to collapse
I think you would be safer flashing firmware from here, ota will, probably brick your own.
Doomlord kernel has got recovery, after installing boot up and when the doomlord picture appears
Keep tapping the back button
Sent from my R800i using xda premium
Hi guys,
Rooted Oneplus 3 is soft bricked. Please help me!!! :crying:
:crying:Quick desription: Fastboot formatted it. My PC detects it.
Tried to Fastboot flash latest TWRP ("twrp-3.0.2-0-oneplus3.img") via CMD Prompt.
After that I get a message saying that the processed was "finished" (within 0.802s!).
Now I reboot+volume down and bootloop continues. Phone starts, I see the normal warnings I used to get after rooting it. Then I see the Oneplus logo for a fraction of a second and then it boots again and the process repeats itself.
I think it may be worth mentioning that the reason all this happened is an encryption problem that occurred while I was flashing a rom update with TWRP: After the flashing finished, got an error saying "unable to mount storage". Wiped cache+dalvik and then restarted. Got a black screen that did not display any signs of life after several minutes. Then turned it off and on by long press on the power button. Then I got an error saying that the encyption process was disrupted and that I have to wipe my phone (strange given that I did not select any encryption button in TWRP). Anyhow, then I fastboot formatted the phone and that's it.
Thank so much for anyone who can help!!!
fastboot flash recovery recovery.img (I recommend blu_spark's TWRP) reboot to recovery, if it doesn't work, try:
fastboot boot recovery recovery.img
See if you boot to recovery and then try flashing a custom ROM.
Hi Fobos, thanks for responding quickly.
I tried using fastboot boot command (with twrp-3.0.2-0-oneplus3.img). No luck with that.
Also, didn't find a downloadable blu_spark *.img version for twrp recovery. would you be so kind to add a link?
Thank you.
Now I think it's hard bricked ( Help!!!
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
ppppp44 said:
Phone just stopped responding. Mostly doesn't respond. Occasionaly turns on for a nano second, flashes the +1 logo and turns off. Most of the time it doesnt even do that any more when I press (long / short press) the power button!
Somebody help, please!!
Click to expand...
Click to collapse
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Kayembe said:
Keep calm and breath in. I was in the same situation.
Take a breath.
So, you have 2 ways depending on what you want. You can either go back to full stock with a flashing tool or you can install a custom recovery and then installing a custom rom (or stock one). I suggest the flashing tool.
Just follow the steps here: https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306 and if you have any question come back here and ask them.
Good luck.
Click to expand...
Click to collapse
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
anup807 said:
Recoveryhttps://forum.xda-developers.com/devdb/project/dl/?id=24575
First format recovery by using command
fastboot format recovery
then flash recovery using
fastboot flash recovery "recovery.img"
Click to expand...
Click to collapse
Hi Anup!
Thanks for the link to the Blu_Spark version of TWRP.
On CMD Prompt, tried to format recovery, console stopped responding. "Fastboot format recovery"...Just stops responding
Also tried "Fastboot delete recovery". I get a message saying "deleting recovery..." then also stops responding. Nothing happens from there.
I tried to use the OPO3 Root Toolkit. It does detect the fastboot device, but when I try to flash or boot or do anything else other than detection, it is unable to find the device. Says operation failed.
What now? :crying:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Check your cable (try another one), even reinstall your adb drivers on your machine (if Windows).
Let the device charge for 30 minutes at least then retry (charge with new cable too).
ppppp44 said:
Hey Keyembe, thanks for the reply...
Tried to follow the instructions you posted. Did everything to allow unsigned drivers to be installed. Disabled it on from the advanced boot settings, and - when that didn't work, also running on test mode. Neither options work:
In the device manager I right click the android device (currently in fastboot mode), which is installed with Google drivers. I try to update the driver software to the unsigned driver and I get an error saying it's not compatible with my system (Win10 Pro) and that I should make sure it is compatible with an x64 based system.
What now?
Tx
Hey! Thanks for the reply...
Click to expand...
Click to collapse
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Machiel187 said:
You could look through this post if nothing else helps.
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Click to expand...
Click to collapse
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Kayembe said:
Firstly, plug your phone on your computer in recovery mode or fastboot mode.
When you go in cmd and you type "adb devices" do you get anything?
If that works and you still can access recovery, you can install stock rom available on the OnePlus site. Here's a link : http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_4.1.3/
Boot into recovery, then install from adb.
Click to expand...
Click to collapse
Hey Kayembe,
I only get to fastboot mode. No Adb device detected. No recovery mode available.
ppppp44 said:
Thanks mate, followed the instructions on this post. I never get the device to be detected as Qualcomm. All I get is "Android Phone". I did install the Qualcomm drivers despite the warning I got for installing unsigned drivers. Installation went OK. When I go to the device manager again I still identifies the device as android phone. Also when I click "Have Disk" and select the qualcomm drivers I get an error saying they are incompatible with the device or with an x64 based system (regardless of them being signed or not).
Any ideas?
thanks again..
Click to expand...
Click to collapse
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Machiel187 said:
Strange. Are you sure you turned off Driver Signature Enforcement?
When you hold the power button 10 seconds and plug the phone in, it should not be on. The screen should stay black. (looks like its off)
So make sure it's not trying to boot, because then it probably shows up as Android Phonee again.
Click to expand...
Click to collapse
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
ppppp44 said:
That's exactly what happens but when it's not in fastboot mode [ either after 10 seconds power button press or after i see the +1 logo (black screen)] - phone is not detected by my pc.
Yeah I'm sure about the driver signature enforcement. It's definitely off.
What am I doing wrong?
Thanks
Click to expand...
Click to collapse
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
ok I somehow managed to flash Blu_Spark Twrp and got it to work.
Within TWRP, flashed OnePlus3Oxygen_16_OTA_051_all_1704112009_2521.zip
and also SuperSU.zip, and no_verity.zip.
Getting some errors.
Device still doesn't boot.
Attaching the log TXT here.
I am desperate... please help.,..
Puddi_Puddin said:
I'm going to do a unbrick in a few hours.. Make sure Driver Enforcement is off. If you go to device manager and right click on it you can change the drivers somewhere so it shows up as described in the post..
Make sure you use method 2.
Click to expand...
Click to collapse
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
try "default_password" for the password
ppppp44 said:
BTW, Now when I enter recovery mode on TWRP I am asked to put in a password to decrypt data. I don't have any such password any tried to go over the process of reformatting the device and flashing twrp again. that didn't make this decryption message go away...
((
Click to expand...
Click to collapse
Go to Fastboot type 'fastboot erase userdata' (you have to reflash OOS tho.. Make sure you are on the latest TWRP. I'm not a fan of Bluspark but his TWRP is currently more up 2 date.
Hello everybody!
I tried update my phone with new firmware, but I installed (with flash tool) a wrong firmware (not HT17 'Pro' firmware, installed HT17 version). Problem is..the smartphone is dead, no switch on, no charge, the smartphone is stopped nothing happen. Tried with a different version of the SP Flash Too, and with the old correct firmware, but nothing. What can I do? Thanks for answer
Kheled said:
Hello everybody!
I tried update my phone with new firmware, but I installed (with flash tool) a wrong firmware (not HT17 'Pro' firmware, installed HT17 version). Problem is..the smartphone is dead, no switch on, no charge, the smartphone is stopped nothing happen. Tried with a different version of the SP Flash Too, and with the old correct firmware, but nothing. What can I do? Thanks for answer
Click to expand...
Click to collapse
Mtk is almost unbrickable,
- what is msg from SP Flashtool when you tried to flash to unbrick?,
Possible solutions, try one by one;
- you must try with the last version to come back again correct partitions,
- you can try first with only files scatter-txt and preloader to restore your partitions first, then flash again all other files
- sometime ago when connected to sp flash tool my device don`t recognice properly and I made it with some trick, first extract battery a few seconds then put it again, connect terminal usb to device and at same time you hold both vol(+) and (-) connect to pc, with the option "Download" clicked previously (Move all necessary files to folder of SP Flash Tool to short the transmission time.
- And also you can flash system, boot via fastboot, put your device in fastboot mode first, generally with pwr + vol(-) at same time, you get three options; recovery, fastboot and reboot
- You can try enter to recovery, put first your rom (zip) in a sdcard and then update via recovery if you are not rooted, I hope help you
SubwayChamp said:
Mtk is almost unbrickable,
- what is msg from SP Flashtool when you tried to flash to unbrick?,
Possible solutions, try one by one;
- you must try with the last version to come back again correct partitions,
- you can try first with only files scatter-txt and preloader to restore your partitions first, then flash again all other files
- sometime ago when connected to sp flash tool my device don`t recognice properly and I made it with some trick, first extract battery a few seconds then put it again, connect terminal usb to device and at same time you hold both vol(+) and (-) connect to pc, with the option "Download" clicked previously (Move all necessary files to folder of SP Flash Tool to short the transmission time.
- And also you can flash system, boot via fastboot, put your device in fastboot mode first, generally with pwr + vol(-) at same time, you get three options; recovery, fastboot and reboot
- You can try enter to recovery, put first your rom (zip) in a sdcard and then update via recovery if you are not rooted, I hope help you
Click to expand...
Click to collapse
It's work now! Thanks for your help! OMG! I'M happy now
"- sometime ago when connected to sp flash tool my device don`t recognice properly and I made it with some trick, first extract battery a few seconds then put it again, connect terminal usb to device and at same time you hold both vol(+) and (-) connect to pc, with the option "Download" clicked previously (Move all necessary files to folder of SP Flash Tool to short the transmission time." - that was the solution
Kheled said:
It's work now! Thanks for your help! OMG! I'M happy now
"- sometime ago when connected to sp flash tool my device don`t recognice properly and I made it with some trick, first extract battery a few seconds then put it again, connect terminal usb to device and at same time you hold both vol(+) and (-) connect to pc, with the option "Download" clicked previously (Move all necessary files to folder of SP Flash Tool to short the transmission time." - that was the solution
Click to expand...
Click to collapse
Always check that USB cable... I had the same thing happen. I flashed on a cable I didn't know was screwed up and BAM Brick... Fixed the cable issue and it worked.
---------- Post added at 11:19 AM ---------- Previous post was at 11:18 AM ----------
solarsoap said:
Always check that USB cable... I had the same thing happen. I flashed on a cable I didn't know was screwed up and BAM Brick... Fixed the cable issue and it worked.
Click to expand...
Click to collapse
I usually take the flash information from mktools and not spflash..
Mytools make a good fast scatter file and block backup.
I use the Spflash to snatch ROM and flash etc..
I can get my Zenfone 2 up to the fastboot screen, but no further.
Under PC device manager is shows "Android-Phone" as the device, but no drivers loaded.
I've tried a few different drivers, but even though they seem to install OK, "Android-Phone" (in device manager) still won't show as having a driver.
Some threads say I have to enable Android Debugging, but how to do that when the ONLY screen I can get on the phone is fastboot??
Help???
Boowho??
You can try this.
1. Uninstall all drivers for phone you installed on PC, then reboot.
2. Disable antivirus on PC then install standard Intel android device usb drivers. You can download them from Asus website. Then reboot again.
3. Connect phone to PC in fastboot mode.
4. In the device manager you should see "Asus android device" under which "Asus android bootloader interface".
5. Check connectivity in minimal adb & fastboot software (you can get it from XDA) by command "fastboot devices" without quotes. It should answer "some number<space>fastboot".
If all is ok then you can flash raw stock firmware in fastboot mode & update it to latest version OR unlock bootloader, flash TWRP & install custom rom.
Thank you Sanesh. I got all the img/bin files successful now. However, the ZF2 has this issue when you select recovery from bootloader screen it gives dead android. You can then (extra step) hold power and VOl + and get into stock recovery. This is a flaw in the original firmware, I think.
BUT, this extra step is causing TWRP not to be entered. Stock recovery is OK, but not TWRP.
I had to recover the phone using the SOC drivers; before that TWRP worked perfectly.
Thanks
Have you unlocked bootloader ? Unlock bootloader first then flash twrp using giovix92 method. Then reboot to recovery.
Thanks. Turned out I was using a twrp image that is only for marshmallow. I still use lollipop. Every thing is now back to where it was before I had to recover the thing using the SOC method.
Lesson learned. un-root before trying to upgrade to MM.
Hello,
I tried to install a GSI rom on my phone, but I encountered a lot of problems, I couldn't erase the system because it said "system" partition was not found. So I tried many things like editing the partitions. But now, my phone is stuck in bootloop, and I can't enter recovery mode or fastboot mode.
Please help :/
lonyyy_ said:
Hello,
I tried to install a GSI rom on my phone, but I encountered a lot of problems, I couldn't erase the system because it said "system" partition was not found. So I tried many things like editing the partitions. But now, my phone is stuck in bootloop, and I can't enter recovery mode or fastboot mode.
Please help :/
Click to expand...
Click to collapse
Hi!
I struggled with this for a while as well but I found what works for me.
first, make sure you have the proper drivers installed ( just google MTK drivers and you'll find plenty of links for auto-installers ).
you gotta bypass the auth and flash with sp flash tool.
for the bypass:
I use MTK META Utility v75 ( again, google and you'll find it ).
click "disable Auth", then plug in your phone while holding volume up button. If it doesn't disable the BRom protection, you gotta use libusb to install the device filter.
Once the auth is disabled, use sp flash tool to flash the stock firmware.
first, in options, click connections, select the right comport.
in format, click the "format all except bootloader". VERY IMPORTANT YOU CLICK THIS.
next in download select the download agent and scatter file ( found inside the fastboot stock rom folder ).
Check everything EXCEPT PRELOADER and click download
RadixMalum said:
Hi!
I struggled with this for a while as well but I found what works for me.
first, make sure you have the proper drivers installed ( just google MTK drivers and you'll find plenty of links for auto-installers ).
you gotta bypass the auth and flash with sp flash tool.
for the bypass:
I use MTK META Utility v75 ( again, google and you'll find it ).
click "disable Auth", then plug in your phone while holding volume up button. If it doesn't disable the BRom protection, you gotta use libusb to install the device filter.
Once the auth is disabled, use sp flash tool to flash the stock firmware.
first, in options, click connections, select the right comport.
in format, click the "format all except bootloader". VERY IMPORTANT YOU CLICK THIS.
next in download select the download agent and scatter file ( found inside the fastboot stock rom folder ).
Check everything EXCEPT PRELOADER and click download
Click to expand...
Click to collapse
Thank you ! But how can I do this, my phone is stuck in a bootloop?
lonyyy_ said:
Thank you ! But how can I do this, my phone is stuck in a bootloop?
Click to expand...
Click to collapse
if you do the whole bypass thingy it's gonna skip certain boot-checks which causes the loop, putting it in a different mode. from there, sp flash tool can access the device.
you can also just hold down the volume up button and then plug in the usb, 9/10 the bypass utillity will catch the BRom
RadixMalum said:
Hi!
I struggled with this for a while as well but I found what works for me.
first, make sure you have the proper drivers installed ( just google MTK drivers and you'll find plenty of links for auto-installers ).
you gotta bypass the auth and flash with sp flash tool.
for the bypass:
I use MTK META Utility v75 ( again, google and you'll find it ).
click "disable Auth", then plug in your phone while holding volume up button. If it doesn't disable the BRom protection, you gotta use libusb to install the device filter.
Once the auth is disabled, use sp flash tool to flash the stock firmware.
first, in options, click connections, select the right comport.
in format, click the "format all except bootloader". VERY IMPORTANT YOU CLICK THIS.
next in download select the download agent and scatter file ( found inside the fastboot stock rom folder ).
Check everything EXCEPT PRELOADER and click download
Click to expand...
Click to collapse
So the BROM protection is now deactivated, but I can't find any COM port in the connection panel. And what is the fastboot stock rom folder ? I need to download the stock rom of Xiaomi 11T?
lonyyy_ said:
So the BROM protection is now deactivated, but I can't find any COM port in the connection panel. And what is the fastboot stock rom folder ? I need to download the stock rom of Xiaomi 11T?
Click to expand...
Click to collapse
alright I'm guessing you'll first need to add the device filter for the port.
download libusb, run it and click add filter. while you have the phone in bypass mode, you should see a mediatek device in the list. add that one.
and yeah. but you can just download it from mi.com!
RadixMalum said:
alright I'm guessing you'll first need to add the device filter for the port.
download libusb, run it and click add filter. while you have the phone in bypass mode, you should see a mediatek device in the list. add that one.
and yeah. but you can just download it from mi.com!
Click to expand...
Click to collapse
Ok, thanks ! I'm downloading the ROM, but in libusb, it doesn't recognize my device...
RadixMalum said:
alright I'm guessing you'll first need to add the device filter for the port.
download libusb, run it and click add filter. while you have the phone in bypass mode, you should see a mediatek device in the list. add that one.
and yeah. but you can just download it from mi.com!
Click to expand...
Click to collapse
Soo... libusb wasn't working, but I figured out that I have like one minute to flash, during this time, it recognizes the com port etc...
First, it says "lib da not match" in download-agent, then in scatter-loading file it says "the scatter file contains an unsupported version"...
lonyyy_ said:
Hello,
I tried to install a GSI rom on my phone, but I encountered a lot of problems, I couldn't erase the system because it said "system" partition was not found. So I tried many things like editing the partitions. But now, my phone is stuck in bootloop, and I can't enter recovery mode or fastboot mode.
Please help :/
Click to expand...
Click to collapse
Sir, from indonesia? I just flash vbmeta with spflashtool, or python brom mode . Sorry bad english
Okay, thanks everyone! I got my phone working again by using mtkclient python and mi flash tool!
RadixMalum said:
Hi!
I struggled with this for a while as well but I found what works for me.
first, make sure you have the proper drivers installed ( just google MTK drivers and you'll find plenty of links for auto-installers ).
you gotta bypass the auth and flash with sp flash tool.
for the bypass:
I use MTK META Utility v75 ( again, google and you'll find it ).
click "disable Auth", then plug in your phone while holding volume up button. If it doesn't disable the BRom protection, you gotta use libusb to install the device filter.
Once the auth is disabled, use sp flash tool to flash the stock firmware.
first, in options, click connections, select the right comport.
in format, click the "format all except bootloader". VERY IMPORTANT YOU CLICK THIS.
next in download select the download agent and scatter file ( found inside the fastboot stock rom folder ).
Check everything EXCEPT PRELOADER and click download
Click to expand...
Click to collapse
Hey,
My friend is trying to follow your reply in order to get her phone out of bootloop.
Not sure if you are aware but if you google for "MTK META Utility v75" as you instruct people to do... you get a wall of spam uploads which are zip files with passwords on... which gives the impression that basically every spammer wanting to get a virus onto your computer, or youtuber wanting to force you to watch their videos, is uploading crap marked as "MTK META Utility".
Perhaps you could actually provide links to trustworthy software or make a topic with a proper guide for people to follow, instead of just a reply to someone's question?
lonyyy_ said:
Okay, thanks everyone! I got my phone working again by using mtkclient python and mi flash tool!
Click to expand...
Click to collapse
Please can you tell me how?? I am having the same problem and my phone is just rebooting constantly but I cant open fastboot. Please or I don't know if my phone is dead
I have some experience with rooting this device and I can tell you that this device can install TWRP but it doesn't boot system after install ikr sad