i have a problem with my moto g4 plus / moto g4 i was trying to unlock bootloader and trying to install twrp in my phone but i didnt succefully install twrp or unlock bootloader now i only show blank screen .. i cant entered in fast-boot or recovery mood when i press volum + or power button its show boot mood options when i select any option its just goes blank and nothing happend.. when i press volume down + power button its not responding and nothing happen ... when i connect with pc/laptop it conneting and reconneting and in device manager it only show mediatek android usb com something like this ...... please help me
Can you tell us the procedure you were following to unlock your bootloader and try to flash TWRP?
When you press volume down and power key, do you see the normal fastboot screen (not sure what you mean by boot mode options)? Do you see text like AP Fastboot Mode (secure), a green Android like this image? https://i.ytimg.com/vi/Ei3vCdq3jn0/maxresdefault.jpg
Sounds like you may have to try a cache wipe or factory reset, or a stock ROM re-flash. Can you tell us what stock ROM you had on your device before attempting to unlock your bootloader?
EDIT - wait, you're seeing Mediatek Android USB...? Can we see a screen shot of the Device Manager for your device please?
i try multi procedures but at end i try fastboot oem unlock and after this i start my phone its not starting and only moto logo appears after this i try to flash twrp by fastboot flash recovey twrp.img and when i install i start in recovery mode its stuck on recovery screen and after some time rebbot and stuck in boot loop
MZaib74 said:
i try multi procedures but at end i try fastboot oem unlock and after this i start my phone its not starting and only moto logo appears after this i try to flash twrp by fastboot flash recovey twrp.img and when i install i start in recovery mode its stuck on recovery screen and after some time rebbot and stuck in boot loop
Click to expand...
Click to collapse
Hmm, that's very odd - so you requested the unlock key from Motorola, booted your device to the bootloader, entered the key with 'fastboot OEM unlock <the unlock key>', did your device then erase itself and then reboot? Similar to what is described in this guide: https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2
Also, did your bootloader look like this : https://i.ytimg.com/vi/Ei3vCdq3jn0/maxresdefault.jpg or like this : https://i2.wp.com/blogthetech.com/w...Fastboot-Mode-on-MTK.jpg?resize=819,369&ssl=1
What concerns me is that you mentioned your device is presenting itself to your computer as a Mediatek device (rather than Motorola or Qualcomm). Can you confirm this with a screenshot of your Device Manager and confirm you do have a Moto G4/G4 Plus?
{
"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"
}
echo92 said:
Hmm, that's very odd - so you requested the unlock key from Motorola, booted your device to the bootloader, entered the key with 'fastboot OEM unlock <the unlock key>', did your device then erase itself and then reboot? Similar to what is described in this guide: https://forum.xda-developers.com/showpost.php?p=67031801&postcount=2
Also, did your bootloader look like this : https://i.ytimg.com/vi/Ei3vCdq3jn0/maxresdefault.jpg or like this : https://i2.wp.com/blogthetech.com/w...Fastboot-Mode-on-MTK.jpg?resize=819,369&ssl=1
What concerns me is that you mentioned your device is presenting itself to your computer as a Mediatek device (rather than Motorola or Qualcomm). Can you confirm this with a screenshot of your Device Manager and confirm you do have a Moto G4/G4 Plus?
Click to expand...
Click to collapse
MZaib74 said:
Click to expand...
Click to collapse
That image isn't showing up, you have to upload the image to XDA or another image host, we can't see into your C:\ drive...
i dont know how to upload image here
echo92 said:
That image isn't showing up, you have to upload the image to XDA or another image host, we can't see into your C:\ drive...
Click to expand...
Click to collapse
and its not like which is shown in links sent by you ... its have only three options recovery mood fastboot mood and normal mood when i select any of these my phone screen goes blank and nothoing hapend
MZaib74 said:
i dont know how to upload image here
Click to expand...
Click to collapse
MZaib74 said:
i dont know how to upload image here
Click to expand...
Click to collapse
Upload the image to https://imgbb.com or tiny pic http://tinypic.com then once uploaded, there should be a shareable link which you can paste here.
If you have Google drive or Microsoft one drive, then you could upload to there and share the file link.
---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------
MZaib74 said:
and its not like which is shown in links sent by you ... its have only three options recovery mood fastboot mood and normal mood when i select any of these my phone screen goes blank and nothoing hapend
Click to expand...
Click to collapse
So your bootloader screen looks more like this? https://blog.hovatek.com/bpyeki/uploads/2015/01/MTK_Phone_entering_boot_mode.jpg
Where did you buy the phone from?
echo92 said:
Upload the image to https://imgbb.com or tiny pic http://tinypic.com then once uploaded, there should be a shareable link which you can paste here.
If you have Google drive or Microsoft one drive, then you could upload to there and share the file link.
---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------
So your bootloader screen looks more like this? https://blog.hovatek.com/bpyeki/uploads/2015/01/MTK_Phone_entering_boot_mode.jpg
Where did you buy the phone from?
Click to expand...
Click to collapse
yes exectly this i buy from local market in Pakistan second hand not box packed
MZaib74 said:
yes exectly this i buy from local market in Pakistan second hand not box packed
Click to expand...
Click to collapse
MZaib74 said:
yes exectly this i buy from local market in Pakistan second hand not box packed
Click to expand...
Click to collapse
Ah, that's a boot screen from a phone with MediaTek processors. This matches with you mentioning that the Device Manager on Windows is detecting a MediaTek USB connection (the MediaTek preloader USB vcom). I see it's the same as what you uploaded.
The big problem here is that genuine Moto G4/G4 Plus devices come with Qualcomm Snapdragon 617 CPUs, not MediaTek, and don't present themselves as MediaTek devices to a computer. Unless you've been mistakenly sold a Moto E4/E4 Plus (which have MediaTek CPUs in them), on the available evidence thus far, I'm concerned you may have bought a fake clone G4/G4 Plus.
It could be that someone has somehow flashed MediaTek firmware onto a Moto G4/Plus, but I'm not sure if that is even possible, as the Snapdragon bootloader would likely block such a firmware flash. A boot screen from a genuine Moto G4 that is not modified was shown here: https://i.ytimg.com/vi/Ei3vCdq3jn0/maxresdefault.jpg You'd normally get to this by powering off, then hold the power and volume down keys together.
I don't have any experience repairing such devices, and the guides here only will help you with Snapdragon/genuine Moto G4 devices. All I can do is point to guides like this https://www.engineerthink.com/blog/...ediatekmtk-android-phone/?PageSpeed=noscript' and hope you can find some firmware for this particular device. I hope that posting here https://forum.xda-developers.com/android/help might get you some assistance as well.
EDIT - What happens if you select normal mode, does your device boot?
Otherwise, I hope you can get your money back.
By the way thanks alot for helping me
is chaning of mother board will help me or not ??
i forget to tell you one thing my phone not showing in pc permanently its detected and flash for 1 sec and disappers from device manager and doing this process continusly
MZaib74 said:
is chaning of mother board will help me or not ??
Click to expand...
Click to collapse
Changing the motherboard, if there are spare motherboards that will fit your device, will be expensive, and may cost more than what you paid for the device. Are you hoping to try putting in a Moto G4 motherboard? Also, we don't know if the other components in the device are genuine or possible fakes as well, so you may have a genuine motherboard but low quality parts (e.g. the camera) that will impair your experience.
I'd try selecting normal mode in that boot list, see if you can get it booting again. Or perhaps try a factory reset from recovery, if you're willing to do so (as this will wipe your data).
Apologies about this - the evidence you've presented matches up unfortunately. I hope that you can get a refund from the seller for selling a non-genuine device if you so choose.
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
MZaib74 said:
i forget to tell you one thing my phone not showing in pc permanently its detected and flash for 1 sec and disappers from device manager and doing this process continusly
Click to expand...
Click to collapse
Hmm, can you check if the USB cable is plugged in fully and securely, and in a fully working USB port on your computer? Does it keep happening if you keep the device still, or get worse if you move the device around whilst still plugged in?
i try nothing happend when i connect another phone work fine
i dont know what to do know i think its better to leave it
Related
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
{
"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"
}
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Hey @korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Premie said:
Hey korockinout13!
1st of all, thanks for this, I have hard bricked my ME70cx and I needed a solution...
Unfortunately it is not working... I have followed your instructions but I keep getting the error "Windriver Error: 0x20000015, Timeout expired"
I have reinstalled the drivers (iSOC and Intel USB) but nothing changes, the same error keeps appearing.
You say "The trick seems to be pressing the flash button before the USB logo appears." BUT the start flash button is only clickable AFTER the USB logo appears
Any help shall be appreciated
Click to expand...
Click to collapse
I literally faught that error for a whole day. I tried 5 different computers, all had that issue. Usually my tablet would connect and disconnect once before the logo came up. Within that brief window, I was able to start the flash and it worked. I'm pretty sure that's what did it. If you aren't seeing this, turn up your PC's volume and listen for the USB sounds.
This whole thing is pretty annoying, but when it works, it works.
Thanks
I shall keep going at it until it works or I find another solution.
PLEASE help me!
korockinout13 said:
This guide will help you unbrick your hardbricked MeMo pad or possibly other device. For the purpose of this guide, hardbricked will refer to a device's software being damaged to the point where standard procedures and utilities (adb, fastboot, recovery, etc.) will not be able to make the device functional again. In order to be hardbricked, you essentially need to erase or damage the bootloader. Without the bootloader, you can't use fastboot or recovery since all of those things require the bootloader. This guide addresses that situation (your device should be displaying nothing but the USB logo, as seen in the attachment). If you have a working bootloader and can run fastboot commands, THIS GUIDE IS NOT FOR YOU and will only possibly make things worse.
This guide is directed towards the ME170CX, which is also apparently called the ME70C or KO1A; however, the same process should work for other MeMo Pad devices and even other Intel devices. I cannot provide much help for other devices, so try at your own risk.
Do not follow this guide unless it is your last hope or you know what you are doing. I am not responsible for any damage you cause to your device in any way.
We will use the Intel Phone Flash tool, which can be used with a variety of Intel devices to flash firmware. You can use the Manufacturing Flash Tool instead if you'd like.
Here are the steps:
Obtain and install all drivers and software from the bottom of this post.
Download the factory image zip from the manufacturer's website; make sure it matches your device before flashing!. Extract the contents of the zip. Extract the contents of ifwi.zip into the same folder.
Plug in the device and open the Phone Flash tool. In the Phone Flash Tool window, click on "Custom Flash" on the left and pick "system (blankphone)" from the Type dropdown.
For each of the first four files, pick the one that matches:
CLVp_CSAX_FWR_DnX_20.3E.bin for FW DnX
IFWI_v64.25_CSAX_PROD.bin for IFWI
CLVp_CSAX_OS_DnX_20.3E.bin for OS DnX
fastboot.img for OS Image (this doesn't seem right, but it worked for me)
Once the four images are in place, click "Register flash file". At this point, your device should be displayed in the white rectangle on the page and the start flash button should now be clickable. Press the button, and flashing will commence. If you see "Windriver Error: 0x20000015, Timeout expired" in the console, try rebooting the device and flashing before the USB logo comes up (the device will appear in the Flash Tool before the logo comes up).
After a few seconds, you should see the Intel splash screen and you will be taken to droidboot. From there, it should be fairly easy to recover the device.
If you encounter any issues or corrections, please respond to this thread and let me know. Also, I was getting tons of driver errors (Windriver Error: 0x20000015, Timeout expired) the second time I tried to do this. The trick seems to be pressing the flash button before the USB logo appears.
I discovered most of this information from these two resources:
https://www.youtube.com/watch?v=jh89aiepcjQ
http://www.asus-zenfone.com/2014/11/how-to-unbrick-zenfone-5-and-zenfone-6_8.html
REQUIRED DRIVERS AND SOFTWARE
iSocUSB Driver
Intel USB Driver for Android Devices
Intel Phone Flash Tool
Click to expand...
Click to collapse
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Nandr0idC0nsumer said:
Hello,
My device has a screwed up boot partition, but not the bootloader. My question is, how do I get this to flash without going into the USB mode?
Click to expand...
Click to collapse
If you have a working boot loader, you don't need to do this.
korockinout13 said:
If you have a working boot loader, you don't need to do this.
Click to expand...
Click to collapse
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Nandr0idC0nsumer said:
Then how do I unbrick my device? I need to flash a new boot partition.
Some background: I installed the Lollipop update, then flashed the kitkat boot and fastboot IMG files (your average stupid Ryan). Can't get into fastboot anymore
Click to expand...
Click to collapse
What happens instead of fastboot mode?
korockinout13 said:
What happens instead of fastboot mode?
Click to expand...
Click to collapse
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Nandr0idC0nsumer said:
"Fastboot Starting...
Fastboot Starting#1...
Fastboot Starting#2...
Fastboot Starting#3..."
Hangs there until rebooting after about 2 minutes."
Click to expand...
Click to collapse
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
korockinout13 said:
Hmm... I don't know what that is. Looks like you're in the same boat as me. I am also trying to force a way in to this mode.
Click to expand...
Click to collapse
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Nandr0idC0nsumer said:
Only thing I can think of is using "adb sideload" and making a ZIP to flash lollipop boot.img and droidboot.img
---------- Post added at 05:49 PM ---------- Previous post was at 05:28 PM ----------
Any other thoughts on what I could try? Leaving to eat in about an hour, and if this ain't fixed by then, I'll probably bring this to bestbuy as well
Click to expand...
Click to collapse
You have adb? That's not possible unless you are getting past the boot loader.
korockinout13 said:
You have adb? That's not possible unless you are getting past the boot loader.
Click to expand...
Click to collapse
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Nandr0idC0nsumer said:
Booting normally results in an "error" screen. randomly spamming vol up+vol down+power (SPAM!) brings up recovery, then do "apply update from adb." it puts it in a special adb where you can only use adb sideload
Click to expand...
Click to collapse
Hm... seems like you should be able to work with that if you have something flashable.
korockinout13 said:
Hm... seems like you should be able to work with that if you have something flashable.
Click to expand...
Click to collapse
Returned the tablet at Best Buy to get "fixed" (come on bestbuy, I know you mean replaced.) Thanks for your help
Repair
Hi,
I think i can help you out because i worked with the intel tool for weeks now to find a solution to root the me581cl.
Go to my thread and download a newer version of intelPhone tool.
http://forum.xda-developers.com/general/help/root-downgrade-asus-me581cl-t3075678
If you crashed your tab totaly, you must put the 4 OS IFWI,dnx files like in the first post and then also boot.img, fastboot.img, recovery.img.
Uncheck only the ifwi folder, but select it before. So its possible to check blank phone and on demand flash.
Then click start flash and the files get loadet up. Now push vol+ and vol- togehter and plug in the device.
(device must be off before you plug it in. If not, press 10 sec the power button.)
The reest you can read in my thread. A downgrade from Android 5 to 4.4 is also possible.
Good luck
Guys, my ME176CX is shafted after completing the L update, it boots to the android with the red exclamation box...i can get past this by using the volume + & power and arrive in the recovery. from there I have tried the wipe cache/wipe userdata (doesn't help) also i tried to adb sideload one of the roms in the collection of roms thread. no good. ideas??
Any solution?
I have a ME176CX, I upgraded the SO I got the message "it said 'Unable to detect power status' for me was weird but I keep going pressing the volume button it started but in the black screen with this message:
"FastBoot Starting...
FastBoot Starting...#1
FastBoot Starting...#2
FastBoot Starting...#3" I don't know what to do, It doesn't move from this screen.
Man I'm living in Venezuela a bad country to get damaged any gadget everything is 5 times expensive who your country and without any help in our soil by ASUS.
is this solution applicable to non-intel memopad? (e.g. me172V)
playinghier said:
is this solution applicable to non-intel memopad? (e.g. me172V)
Click to expand...
Click to collapse
No, this is very specific to the Intel chipset.
So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?
potemkinbuster said:
So my G2 D800 is currently stuck on Fastboot mode but whenever I run the command "Fastboot devices" it only shows the device as "?", which I thought meant that it had issues recognizing it because of corrupted drivers.
After doing some searching, I decided to download Google USB drivers and LG device drivers, but sadly the computer installs the device as "ADB Google Interface" or "Fastboot Google Interface" and not as an LG device, and this makes the device to show as "?" when the "Fastboot devices" command is run.
I also tried the "ADB devices" command and it came back with a empty line where the G2 should appear.
Just for the record, the G2 cannot enter into Download mode nor Recovery Mode.
Is there a way of making my device show up properly?
Click to expand...
Click to collapse
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?
the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.
wulsic said:
ADB devices doesn' t work as it' s in fastboot mode. The ? doesn' t matter fastboot should work.
There are also plenty of guides here in general how you can fix your problem. you need to use the fastboot flash command to flash the proper files to get everything working again. I suggest to erase download mode partition first and get your phone booting/working recovery again. Cause if you did something wrong you could always still enter Fastboot mode by entering download mode because the download mode will be missing so it will go to fastboot.
So fastboot is detected else there wouldn' t be a ?
Click to expand...
Click to collapse
I've tried this, but it takes forever and when it comes back with a response it only says (ERROR TOO MANY LINKS), which makes the use of fastboot commands useless
albatron34 said:
the only solution for your case is to use testpoint solution to get the download mode (fastboot dont work) i have the same problem before.
Click to expand...
Click to collapse
I wishi I could make it get into download mode xP
Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!
potemkinbuster said:
Ok, I will keep updating this and hopefully if I find the solution, I might be able to help others with the same case as me.
So far I've tried:
*Flashing all *.img files of my model (D800).
-If you are able to finally enter Download mode, but when you try to flash the ROM you can't because of a wrong model, please check here for a solution.
*Since the method above did not work for me, I had to "destroy" download mode to get back into Fastboot mode so I could Flash TWRP recovery image file.
This has caused my phone to stop being recognized by the PC, which means that when the fastboot commands are run, I cannot get it to work as the computer doesn't know the exact location of the phone (USB, Vendor ID, Details about phone).
To try to make it appear again, I redownloaded the drivers, fastboot files and even went as far as installing manually the drivers through Linux, but none of this seem to work.
As of now, the phone cannot be recognized, but I won't give up until I find a solution!!!
Click to expand...
Click to collapse
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb
I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.
wulsic said:
Did you also tried linux to run the fastboot command as root? Or did you saw the device in device manager in windows?
If all the things don't work then you might need to do the hard brick fix method.
It also may sounds odd but check oe the device is maybe recognized in adb
Click to expand...
Click to collapse
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either
Godra said:
I ve had same problem as op does. What I did is next:
1. Opened phone and shortened those two capacitors to force phone in QHUSB_BULK mode. (there is tutorial on XDA how to do it)
2. After I connected it to PC it showed many partitions (as it supposed to do)
3. Followed this video https://www.youtube.com/watch?v=_d5b_osUTug
4. Flashed .kdz of choice using flashtool
Im in u hurry now but ask if you need anything else and Ill anwer you when I get home.
Click to expand...
Click to collapse
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...
potemkinbuster said:
I tried with Linux and it wasn't identified.
When I used the "lsusb" command I would get back a google device connected as the vendor ID.
ADB doesn't recognize it either
Click to expand...
Click to collapse
so it partly like works, perhaps you can still get it to work but else you must do the hardbrick fix method from general. I can't say much other things how you could fix it if fastboot mode doesn't work recovery not then you must use that.
potemkinbuster said:
I'd try this, but I don't have a guide good enough to show me which capacitor I should deal with...
Click to expand...
Click to collapse
Yeah, its a bit tricky when doing it first time but its not that hard. I used this tutorial to open phone and short those capacitors. You just have to remove almost all conectors (but camera one) and remove everything to get to SoC.
I did try to shorten capacitors and removes all connectors but i suppose to shorten them when i put back connectors exept the battery , the probleme whene i reattach them i can no longer see the capacitors @@
There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.
Godra said:
There is that small metal piece that is glued to one of those conectors I have removed to be able to access capacitors.
Click to expand...
Click to collapse
that small metal piece is the volume boutton , and it seemd that they are not removable
No, there is one bellow it but it might be different in your phone. What version of G2 do you have?
Godra said:
No, there is one bellow it but it might be different in your phone. What version of G2 do you have?
Click to expand...
Click to collapse
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"
kakashi_senpai said:
I have a g2 d802 32g , and I faild trying to shorten the capacities , there is no clear tut to do it
note : in fastboot devices , my lg is recognized as an "?"
Click to expand...
Click to collapse
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.
Godra said:
So exactly same device as mine. And mine device was recognized as "?" as well. I have tried all drivers and yet it didnt work.
Is your phone still opened?
There is one small hole on each side of back of device from which you can see LCD. When you successfuly shorten capacitors youll see purple-like color which means display got power although if you flip your phone your screen will look like its not on. After that you connect battery conector and unplug USB and your device should (well, mine at least did) be in bulk mode.
Click to expand...
Click to collapse
this is a pic from my phone can u please show where to put the wire please
{
"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"
}
kakashi_senpai said:
this is a pic from my phone can u please show where to put the wire please
Click to expand...
Click to collapse
Well first you need to remove the buttons plate as it's located underneath that. See the images if you don't know what I mean:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
The only video perhaps available I searched through the thread was this:
https://www.youtube.com/watch?v=15krGmydqgQ&feature=youtu.be
It isn't very clear with the unbricking situation but I unbricked my phone using the images too, Just try to read and see the images and you should be able to unbrick it only you need a thin wire kinda not too large. I couldn't find a smaller wire so it took me like 15 minutes to get it unbricked as I also had some fail attempts.
Yes sir thats my probleme , I tryd to remove the buttons plates but they are stuck with both side , in the video u gave , they are separated
---------- Post added at 10:59 PM ---------- Previous post was at 10:04 PM ----------
well i succeeded to remove button plate , and my device was read as bulk mode. and now i reattached battery and unplug usb connector, now i put back buttons ? and plug it again or what i do exactly ?
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
{
"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"
}
Device; LG G2 D802 32GB
Some one please?
DroidsRugly said:
ok this was my sister's phone & i screwed it up. i rooted it with towel root while i was backing it up with auto rec & then it asked me to go into recovery mode & when i tapped on it, booom not working since. the device is showing grey lines & computer is not picking it up & yes i have the drivers installed, LG Flash tools & tried powerbutton+volume button trick with no avail. please help me, she'll gonna kill me(literally)
it is like this.
Device; LG G2 D802 32GB
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
This is why I worry messing around with my G2
Have you tried long holding the power button?
Sent from my Nexus 6 using Tapatalk
Same thing here. Any answers? I can hold the power button and it turns off for a second then turns itself on and these lines show up again. Same setup after using AutoRec on 4.4.2 rom.
This is a known problem. Have LG send you a new one
blastagator said:
This is a known problem. Have LG send you a new one
Click to expand...
Click to collapse
Sadly way outside the warranty. So it's pretty much toast?
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
Make sure you're phone is fully charged. I had a problem entering download mode with low battery. I also had to try different usb ports on my laptop for whatever reason.
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
walkingagh said:
Computer won't recognize the device at all, and it won't enter download mode. So I am not sure I can TOT back without that functionality.
Click to expand...
Click to collapse
And sadly this was my phone. I switched for a while and was coming back and wanted an upgrade to the software. I hadn't updated from 4.4.2 as it had sat in a drawer, then did AutoRec (which I thought I had done before) and boom phone is completely unusable.
---------- Post added 27th December 2015 at 12:07 AM ---------- Previous post was 26th December 2015 at 11:55 PM ----------
dark_prince said:
Take the battery out, recharge it through an external charger.
Also enter download mode via inserting USB Cable (Make sure u have LG United driver installed) and keeping Volume Up button pressed for the whole time until Downlaod mode appears on screen, or atleast the screen is on with those lines.
In case of success (i-e. phone shows signs of life), go to Device Manager in ur PC and see if Android Device is connected. Use LG Flash tool 2014 to flash kdz back to normal or try the tot method just in-case your phone is D802/LS/VS variant which doesn't need download mode tbh, just healthy battery.
Click to expand...
Click to collapse
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
walkingagh said:
I can get signs of life (the bars), and windows makes the "you plugged something in and it worked" sound, but there is nothing in device manager despite having the LG drivers installed. Battery is healthy, I used the phone for a day or so to watch videos and stuff. I was working on it there. I think I need to try a different computer.
Click to expand...
Click to collapse
Expand under "Ports Com Ports & LPT"
And you will see LGE Com Port Device.
Just flash the kdz away if u see so. otherwise go through the tot method if u see the com port devices to change the com port address to com41 and then flash tot.
I tried this on Windows 10, Windows 8.1, Windows 8 and Windows 7 (all 64-bit versions) and it worked on all of those. Even with USB 3.0 supported laptop.
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
wzedlare said:
Your device is at fastboot mode at background, so use fastboot to erase and flashing img files.For example:
fastboot erase laf.img
fastboot flash laf laf.img
you just need your stock img files
Click to expand...
Click to collapse
Any good tutorials on fastboot? And those files come from a bootstack correct?
stan54 said:
did you try to TOT back to stock?
btw, why were you rooting and messing with your sister's phone in the first place?
Click to expand...
Click to collapse
Same problem with me tried Kdz Method. But no luck any idea? It's been 3 months em using it like this. Any help?
Sent from my LG-D800 using Tapatalk
So pretty stuck at this point as well. KDZ method stalls at 60%.
UPDATE FASTBOOT WORKING! Took forever to figure out the drivers, but it's working. I have no clue what to do now.
Fastboot won't recognize the device though I have the fastboot driver installed and running. Any ideas?
TOT is just kinda giving up on me. Still chasing down any leads, but the phone feels pretty borked at this point.
Update: Now in download mode! Man this has been crazy. TOT working! Okay so here is how I did it.
First, I downloaded google's ADB drivers and installed the LG drivers as well. I am not sure which one did it. Then I plugged my phone in and went to device manager. For me, it had an unrecognized device and fastboot wasn't working. So I had to manually assign the driver.
Right click on the device and update driver > Let me choose > all devices > Google > LGE mobile ADB interface.
Now fastboot should be working.
Then I used the srktool_2.1. Option 4 then option 4 again, select model number. It reboots to black screen. From there I was able to completely power off (10 second hold on power button). And when it booted back up all the drivers installed. I was able to TOT back to stock using this guide. http://forum.xda-developers.com/showthread.php?t=2432476. KDZ might work as well.
Unfortunately the screen damage looks to be permanent. But I think this is worth more now than it was 30 minutes ago!
Hi guys,
It turned out this script can't really unlock the bootloader. Although I didn't see it, my phone must have come with an unlocked bootloader.
I did another test on the same script but for Redmi 4X and the result was the same - can't unlock the bootloader.
So the moderators can delete this topic as it now serves no purpose. There are other topics for flashing TWRP and rooting the phone.
I am sorry for misleading you guys...
Here's how to install TWRP and SuperSu.
I'm not responsible if you brick your phone or lose data. I did a test on mine and all worked fine.
Info found here - (https://www.gizdev.com/root-xiaomi-mi-5s-unlock-bootloader/).
What you need:
1. Mi Flash Tool - Link(or just the ADB driver - Link)
2. Flasher ToolKit for Mi 5s - Link.
3. USB Debugging enabled in Developer Options
Install the Mi Flash Tool or the ADB drivers. Windows might tell you the drivers cannot be verified. Click on Yes to continue with the installation.
Unzip the Flasher ToolKit files to a folder on your computer.
Start with FLASHER TOOLKIT Capricorn.bat.
{
"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"
}
Hit Enter and this is what you'll see:
First you need to unlock the bootloader, so click on 3. Bootloader Utility. - This only really checks if the bootloader is locked or not. Nothing else.
The program will inform that hitting Enter will restart the phone in Bootloader mode.
Once there the unlocking will begin and you'll see this:
Now the phone will restart.
Once it boots up Android, you can continue with the next step - installing TWRP. Now it's a good time to transfer the SuperSu zip file to your phone. In Downloads for example.
Select the first option - Flash ZCX-TWRP 3.0.2.X for Mi 5s.
The image will be transferred and the phone will be restarted in Recovery mode. It might take a while to load TWRP for the first time, be patient.
Now that you're in TWRP, click on Install, select the SuperSU zip file. Once flashed, go back to Reboot, System.
If something fails:
-The ADB drivers didn't work for me so I installed Mi Flash and unplugged/plugged the phone in the USB.
Check in Device Manager if the ADB drivers are loaded for your Mi 5s. If you don't see anything saying ADB, unplug the phone and plug it back in the USB. Or try another USB port. Or try uninstalling the current drivers and reconnect the phone again.
-If you've closed the Flasher ToolKit and you try to start it again, but nothing happens, open Task Manager and kill/end task the adb.exe *32 process.
- If your phone restarts in Recovery, but all you see is the TWRP logo for minutes, give it about 10 minutes. If nothing changes, restart the phone by pressing and holding the power button. Have you unlocked the bootloader first?
It might have been a good idea to take a camera and shoot every step of the process, but I was testing it to confirm it's working. Hence most of the screenshots are from the web.
Anyway, that's what I can think of right now. If I'm missing something or you can't get it to work, let me know.
yes do it plz
Yes, it's a great ideea. Do it pls.
it will be a good start to have a guide here, you should give all the ways you know, including the first step to unlock by contacting xiaomi, however if you find a guide for a certain section you can link to it (or copy it and add a link so it won't be broken) .
It would also be nice to have a guide for major roms, with some optional steps that not all are aware of, like switching to f2fp
Should be ready now. The good thing is that you don't need to contact Xiaomi to unlock the bootloader.
ok so i did everything you told me
but i fail
first i press the 3 and everything was ok my device is unlocked no problem and its restart automatic
next i go to fast boot... and when i press 1 its show me twrp is install
but after that noting happens ... i press vol up and power its go to mi recovery
my phone is on fast boot i check that with cmd
dont know way
eny idea what to do
eny other method ? can i install with mi flash tool ?
im so confuse
Did you see the TWRP logo when the recovery was supposedly installed? Repeat again the TWRP installation and let's see what will happen.
unicastbg said:
Did you see the TWRP logo when the recovery was supposedly installed? Repeat again the TWRP installation and let's see what will happen.
Click to expand...
Click to collapse
no noting show up ? eny other method ?
frozenline said:
no noting show up ? eny other method ?
Click to expand...
Click to collapse
I'd say the recovery image is not getting transferred to your phone. Do you see a confirmation that the img file was sent over? It usually states how much time it took to transfer over.
unicastbg said:
I'd say the recovery image is not getting transferred to your phone. Do you see a confirmation that the img file was sent over? It usually states how much time it took to transfer over.
Click to expand...
Click to collapse
yes exactly its not transferring
---------- Post added at 03:34 PM ---------- Previous post was at 03:01 PM ----------
ok i did it problem was the adb i install naked adb driver its on know...ok so how i install custom rom? its like my other phones but something new in mounting it seed read only ? i had to change that or something? witch to wipe?
When starting TWRP the very first screen asks if you want to mount the partitions in read only mode or full access. And a check box to never show this again. Have you seen that? If not, try to update TWRP to 3.1.x.x, don't remember the exact version, you can find it here, in the Mi 5s section of the forums.
If you get that working, installing a new OS is pretty easy - go to Install, select the ZIP file with the new OS and follow the instructions. You might want to wipe cache and dalvik to avoid force closures after that.
Usually instructions on how to install a specific OS version are found in that OS's forum section.
i all ready do that bye rename and replace the new twrp in the flash kit folder everything is don... what is the best rom right now to install?
That's really up to your preference. I'm on global developer 7.5.25. Some use LOS.
i tried your guide, but i cant unlock bootloader. After i select option 3, the phone restarts and the bunny appears but after that i only receive the message attached.
Can somebody tell me what i do wrong?
What's your current MIUI version?
I'm on 8.2.1.0 and on computer i have Windows 10. I enabled usb debugging and type on add device account
Trimis de pe al meu MI 5s folosind Tapatalk
To be honest I'm not really sure why it doesn't work for you. The phone restarts, so you have the adb drivers.
Here's a little something that deserves a shot - the very first post - http://en.miui.com/forum.php?mod=viewthread&tid=525726&extra=page=1&page=2&mobile=2
I'd love to hear back from you if that worked or not.
i make a request to xiaomi to unlock bootloader and they aproved it in 6 hours, so i will try with mi unlock tool when i get home today. i keep you informed. thx
In managed to unlock with official metod.
Trimis de pe al meu MI 5s folosind Tapatalk
I've taken a look at the code in the script and this method WILL NOT unlock your bootloader. This is only useful for flashing TWRP and rooting a phone, if your phone IS ALREADY UNLOCKED. The third picture provided in the original post is incorrect and that will not be printed on the screen. The script does not attempt
Code:
fastboot oem unlock-go
at any point.
You will probably have to go through the official unlock process.
hi team, i just bought a new oneplus 6T from china with Hydrogen OS, i changed it to Oxygen OS
but somehow it erased completly and stuck on fastboot bootloop, no bootloader, no recovery no system
i tried MsmdownloadTooln the laptop reconizes the phone but the operation stuck also on "param preprocessing"
please any help i would be greatful :crying::crying:
ritork said:
hi team, i just bought a new oneplus 6T from china with Hydrogen OS, i changed it to Oxygen OS
but somehow it erased completly and stuck on fastboot bootloop, no bootloader, no recovery no system
i tried MsmdownloadTooln the laptop reconizes the phone but the operation stuck also on "param preprocessing"
please any help i would be greatful :crying::crying:
Click to expand...
Click to collapse
Hey there I recently had the same problem with a OnePlus 6T... What I did was I installed everything manually using the ADB tools, in fastboot mode. Everything worked fine afterwards. Follow this guide, it will hopefully help.(It helped me ;D)
https://www.google.com/amp/s/forum....-stock-fastboot-roms-oneplus-6t-t3862516/amp/
Ethos001 said:
Hey there I recently had the same problem with a OnePlus 6T... What I did was I installed everything manually using the ADB tools, in fastboot mode. Everything worked fine afterwards. Follow this guide, it will hopefully help.(It helped me ;D)
https://www.google.com/amp/s/forum....-stock-fastboot-roms-oneplus-6t-t3862516/amp/
Click to expand...
Click to collapse
thanks for ur respond
i did this command "flash-all-partitions" but it showed me only "failed respond"
{
"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"
}
ritork said:
thanks for ur respond
i did this command "flash-all-partitions" but it showed me only "failed respond"
Click to expand...
Click to collapse
Make sure to have unzipped the compressed android file from the guide(whichever you decided to donwload) in the same folder as your ADB and Fastboot tools.
If it is still not working... try to manually flash everything in fastboot mode, that is what I did...
Download the latest version of android pie provided in the link from the guide( Google drive or Android Filehost), and then make sure to unzip the compressed file in the same folder where you installed your ADB and Fastboot Tool. Make sure a TWRP recovery image is in the same folder. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Then, what you should do is to follow the guide where it says:
MANUAL FLASH: Windows - OSX - Linux
Get back to me after you finished. Read twice, execute once :good:
Ethos001 said:
Make sure to have unzipped the compressed android file from the guide(whichever you decided to donwload) in the same folder as your ADB and Fastboot tools.
If it is still not working... try to manually flash everything in fastboot mode, that is what I did...
Download the latest version of android pie provided in the link from the guide( Google drive or Android Filehost), and then make sure to unzip the compressed file in the same folder where you installed your ADB and Fastboot Tool. Make sure a TWRP recovery image is in the same folder. (https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482)
Then, what you should do is to follow the guide where it says:
MANUAL FLASH: Windows - OSX - Linux
Get back to me after you finished. Read twice, execute once :good:
Click to expand...
Click to collapse
Thanks a lot my friend
It works now after the second try
Thank u very much .. i really apreciate ur support mate
ritork said:
Thanks a lot my friend
It works now after the second try
Thank u very much .. i really apreciate ur support mate
Click to expand...
Click to collapse
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Thanks again mate <3
Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Hey, i want to flash oxygenos on my chinese variant with hydrogenos. could you help me with the installation in order to avoid this kind of problems(bootloop,brick etc.)?
HackerGames197 said:
Hey, i want to flash oxygenos on my chinese variant with hydrogenos. could you help me with the installation in order to avoid this kind of problems(bootloop,brick etc.)?
Click to expand...
Click to collapse
PM me
Gracie mille !!! First brick and i hope never again but you where there.. Huge thanks.
Download the TOOL ALL IN ONE and if it says fastboot device connected, I think you'll be fine. Make sure right below that you choose OnePlus 6T. Then just download and flash the full rom and it fixed mine, I had the same problem.
bigmikey307 said:
Download the TOOL ALL IN ONE and if it says fastboot device connected, I think you'll be fine. Make sure right below that you choose OnePlus 6T. Then just download and flash the full rom and it fixed mine, I had the same problem.
Click to expand...
Click to collapse
Thanks a lot.
Would you share the link of the TOOL ALL IN ONE?
I also have the same bootloop issue.
Micheal86 said:
Thanks a lot.
Would you share the link of the TOOL ALL IN ONE?
I also have the same bootloop issue.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Hope this helps
I have the same problem
PLeaseeee help me I have a rooted oneplus 6t. I performed a backup and wipe in hope to clear a problem and am now stuck in fastboot mode. Im pretty sure as I tried to reboot it said no os detected, and then I got stuck. I have tried to install the latest oxygen os by manualling flashing 4 files. all tutorials i read have bootloader and other files while i just have - system_matrix , system_manifest , vendor_matrix, vendor_menifest (XML files by the way). I have flashed these files and rebooted only to go back to the fastboot screen.
Ethos001 said:
Hey bud you are welcome ;P
I know how frustrating it was, as I have been in the exact same situation... Took me like 4 hours to figure it out ;D
Glad to help
Click to expand...
Click to collapse
Bro please help me I didn't not much about this things but ill do flashing and customisation i bricked my Oneplus 6t its stuck on bootloader ill try msm tool also its shows param preprocessing ?
And my bootloader is also locked how can i solve this problem pls help me
For anyone running into a similar problem these are the steps I used
1. Download and extract files
a. Qualcomm drivers
b. MSM Oneplus 6t download Tool
2. Disable Driver Signature Enforcement by restarting your pc whilst holding shift, Choose trouble shoot, then going into more recovery ,select Advanced Options > Startup Settings > and then click on Restart.
3. Now PC will restart and Now you will see a list of startup settings that you can change. Select option 7 ‘Disable Driver Signature Enforcement’ by clicking f7
4. Now switch off your phone (by navigating through fast boot options)
5. While switched off hold both vol up + down for 5secs before connecting to your pc. *Your pc should recognise a phone is connected however nothing will be displayed on your phone*
6. Open device manager from start- Under Other devices there should be your phone (although it will be called smthn else), right click that and select update drivers
7. Browse computer for driver software and select folder with extracted QUALCOMM drivers (for me it was called unbrick).
8. The open the MSM application (run as admin tho) it should say device connected
9. Press start and you download should start- if error occurs or download stops unplug, power on, power off and the plug it again, now it should be fine.
10. Wait for download to finish and then your phone should be rebooted
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
mohitgaba14 said:
Bro please help me I didn't not much about this things but ill do flashing and customisation i bricked my Oneplus 6t its stuck on bootloader ill try msm tool also its shows param preprocessing
And my bootloader is also locked how can i solve this problem pls help me
Click to expand...
Click to collapse
Look at the post above