Guys,
I need any help possible although I fear I may be beyond recovery. Basically my Galaxy Nexus is bricked, I had been running 4.0.4 (IMM76D) on it. The phone is rooted and unlocked.
When switching the phone on, all I get is Google and the unlocked keypad. Will not progress further. I can boot into fastboot mode, and sometimes into recovery however although I have files showing on the SD, when I choose them I get a message declaring the path empty.
My main issue is that the handset is not recognised by my computer (running windows 7 and also since yesterday a dual boot of Ubuntu). This results in my Nexus toolkit and the AdamOutler tool being of no use as they do not recognize the device.
Any help/advice will be greatly appreciated as I'm at my wits end.
p.s. I have looked through other threads and even posted this message on one of the threads but recived no replies, hence the new post
Google splash screen = not bricked.
Power+DownVol from a power-off state...does this boot you into odin?
If so...flash an odin file.
You'll lose all of your data/sd contents =/ but at least it'll boot.
But the fact that you can boot into "fastboot" but not access it is bothersome to me.
Have you used fastboot before? (not a toolkit?)
It really SHOULD recognize...
In ODIN mode in shows the droid with a 'downloading...do not turn off target' message however i've left it in this state for hours and nothing happens, I cannot access it from my laptop either to push files to flash etc.
Data appears to be completely wiped from the handset
install the adb drivers http://pdanet.co/bin/PdaNetA302.exe (32bit win 7) or http://pdanet.co/bin/PdaNetA302x64.exe (64bit win 7)
and try fastboot devices after it has been installed.
I can't get into the device to activate USB debugging though?!
try this then.
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Wait...
Are you just leaving it in odin mode?
You have to plug the phone in and use the program "ODIN" to flash a stock image.
Just making sure!
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.
Hi all, so this is my first post and a last resort attempt at recovering my phone, after hours of googling and downloading everything suggested by various forums, and still being stuck... Sorry for the long post, just trying to list all my attempts to fix it.
So, I've been on stock 5.0 Lollipop (v20n) for a long time, with the only issue being that android OS suddenly will decide for no good reason to make my phone super hot and drain my whole battery in 2 hours flat... Nothing that worked for other people worked for me, so yesterday I decided f*ck it, i'm gonna root and flash Fulmics 5.0, using this: http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 (tried the classic method).
Everything went as per instructions, until I went "Send_Command.exe \\.\COM12 < reboot" and the phone got stuck in a bootloop...
So in other words, my phone is not rooted yet (thus nandroid/titanium backup was not made), TWRP was not installed (so i cant reflash stock kitkat). Latest LG drivers are installed (v4.1.1.0 from http://lgusbdriver.com/windows/lg-usb-driver-v4-1-1-0). Adb and fastboot are installed (http://forum.xda-developers.com/showthread.php?p=48915118#post48915118).
I can boot into download mode (Volume up + plugging in my usb cable), but i cant get adb or fastboot to see my device, when i try to flash twrp.img though command prompt! Downloaded the LG Flash tool 2014 to try and reflash stock kitkat 4.4.2 v10E, but it also can't see my device!! LG PC Suite can't see my phone when trying to connect...
I have removed the LG drivers from device manager and reinstalled the 4.1.1.0 drivers several times, but everytime i plug in my cable Windows (7 ultimate) tries (and fails) to install some drivers for it, even though i installed them already.
I tried to do a factory reset (holding volume - and power button, releasing and pressing them again when i see the LG logo), it gives me the option of doing a reset, but it goes back to the bootloop.
I have installed the Android SDK files (https://developer.android.com/studio/index.html), not the whole 1187mb SDK bundle, just the 144mb installer_r24.4.1-windows.exe. But i cant get my pc to see my device!
Went to a friends house and installed the LG drivers on his pc, installed adb and fastboot (as above), opened a command prompt in the folder where the adb and fastboot dll's are, and neither "adb devices" nor "fastboot devices" lists my phone.
What am i doing wrong???
TL;DR LG G3 d855 stuck in bootloop, but can boot into download mode, no root, twrp recovery not installed, LG drivers and adb fastboot installed on pc, adb refuses to see my device but windows tries (and fails) to install some drivers when i plug the cable in. Factory reset didn't work. Need help please!
So I bricked my FireTV last night during an upgrade to rbox's latest fw...
Short story is, it got to the Amazon app optimization after the flash fine so I went back to the computer to start working on the second box while it did it's thing. I mistakenly sent the reboot recovery command to the box that was optimizing itself. I didn't notice I was sending the command to the wrong box until I saw that my second unit was not rebooting to recovery.
Needless to say, it now no longer boots to any logos, and does not turn on at all (no light when plugged in, not even for a split second).
What are my options to unbrick? I'm taking a guess that the SD reader/eMMC method is the only one. If so, is it possible to retain an unlocked bootloader/etc with this method? I've read you'd lose it, but I'm not familiar.
If someone could point me in the right direction that'd be awesome. I tried google but it's filled with loads of outdated or unrelated information (mostly debricking if the amazon logo appears) or info from when the initial hardware root method came out.
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
sparkd said:
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
Click to expand...
Click to collapse
At least you can connect with USB! I get no connection at all to the pc with a A-A cable.
I would suggest for you trying to get the timing right and initiate the fastboot commands right when the device is recognized.
You people need to reflash your partitions, this happened to me months ago. Can't search for the thread now, I think the steps were in the FireTV1 5.0.5.1 thread...
my device bootloader is not unlocked. I was following the steps to downgrade firmware in an attempt to unlock the bootloader.
in Win7 Control Panel > System > Device Manager the FireTV1 appears as QHSUSB_DLOAD - i think I am also going to try this ... http://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
thanks for the advice ldeveraux, ill take a look.
Ordered the eMMC adapter from exploiteers. This is likely the only way I'll be able to fix this as the USB A-A cable is not detecting my FTV
Well I managed to get my device talking with an A-A USB cable while waiting for my eMMC adapter. So now to flash
Is there a way to recover with this method without losing the ability to unlock the bootloader? Bootloader was unlocked prior to the brick.
UPDATE: annnddd it didn't work for me. Was getting I/O errors while writing and now the device no longer gives me partitions in /dev/. The usb device still shows up however.
how did you get the /dev/ partition to appear ?
which linux distro did you download / install as I cannot see any partitions on my device
did you use the linux in a VM ? & did you have the windows drivers installed beforehand ?
thanks
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Raeffion said:
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Click to expand...
Click to collapse
First of all, TWRP doesn't work.
This link would help you to restore your device
https://forum.xda-developers.com/oneplus-7t/how-to/op7t-unbrick-tool-to-restore-device-to-t3994835
Raeffion said:
I hadn't tried rooting my phone until recently since I didn't trust myself, should have gone with my gut and waited longer since this is the only half decent phone I've got. I tried flashing mauronofrio's magisk patched boot image for 10.0.3 without realizing my phone had updated to 10.0.5. I didn't think to fastboot boot because it's been so long since I've rooted a phone. Afterwards, all of my network protocols such as wifi and mobile data no longer worked and although I could text, I could not call or receive calls. So, in an attempt to fix the issue, I used the experimental TWRP via fastboot boot in order to flash 10.0.3 since I could not find a boot image for 10.0.5 which didn't work. Then, I stumbled upon this post and downloaded the pre-compiled files with which to flash the stock fastboot roms. Obviously, I was very upset with myself for failing to read and process this information thoroughly enough and for that very reason I ended up making a far more rash decision in order to repair this issue. I ran the flash-all bat once with no difference, and a second time to get stuck in a bootloop. I have access to fastboot and the stock recovery, I can fastboot flash still, but I haven't been able to come up with a solution. If I did, I wouldn't trust myself to carry it out without confirmation from someone else. Anyone feeling generous enough to help?
Click to expand...
Click to collapse
I had a similar, but not as terrible experience when first attempting to get root on the 7T using the patched boot images that you used. I tried several other patched boot images, but none of them would allow the device to boot. I downloaded the full update of 10.0.5, then extracted the boot.img and it allowed me to boot the device again. Then I patched it in Magisk Manager, and everything went fine and I have root. If you have fastboot access, you can try booting your device using these images with the command fastboot boot boot.img or fastboot boot magisk_patched.img to see if your device even boots up from the images. I got stuck booting from partition b at one point, and used the command fastboot getvar current-slot to see the active partition, then I used the command fastboot --set-active=a to set partition a instead. If those commands fail then you need to update to the latest adb and fastboot and the commands will work.
This is the stock boot.img for the H1905 7T update version 10.0.5:
https://www.dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
This is the Magisk patched version of the same boot.img:
https://www.dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
SkippRunning said:
If you have fastboot access, you can try booting your device using these images with the command fastboot boot boot.img or fastboot boot magisk_patched.img to see if your device even boots up from the images.
Click to expand...
Click to collapse
I've attempted both, I was still in a bootloop sadly.
SkippRunning said:
I got stuck booting from partition b at one point, and used the command fastboot getvar current-slot to see the active partition, then I used the command fastboot --set-active=a to set partition a instead. If those commands fail then you need to update to the latest adb and fastboot and the commands will work.
Click to expand...
Click to collapse
My current partition was still in partition A.
Aswin08 said:
This link would help you to restore your device.
Click to expand...
Click to collapse
My first try with the unbrick tool didn't even sense my phone. I saw the FAQ and then tried to find the Qualcomm drivers in my device manager to no avail, although I did find Kedacom drivers which I could not even attempt to flash over since Windows told me that the driver I was trying to push was out of date. Here is my original post on that thread:
Raeffion said:
I see neither QDLOADER 9008 nor QHUSB_BULK in my device manager and my device is not detected by the MSMDownloadTool. I do see, however, a Kedacom USB device in my device manager titled "Android Bootloader Interface". I just want to be sure that I should download the driver you provided onto my phone before I brick it any further.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
As you can see, I did not yet mention that I still tried pushing the driver since I haven't had a reply yet. I don't want to double-post there but I'm getting no luck elsewhere. I really want this tool to work, is there some way to force push these drivers or is that a bad idea? If it is, any other ideas?
EDIT: Nevermind. I think it's bricked pretty good, I'll probably have to give up on this. When I plug it in, it only goes to bootloader, doesn't boot into recovery, system, or even show the battery percentage when charging. Bootloader hasn't been giving me many options either since the commands I've tried aren't going through. Updating ADB right now, don't know if it's likely that it's causing issues right after I already updated it.
Raeffion said:
I've attempted both, I was still in a bootloop sadly.
My current partition was still in partition A.
My first try with the unbrick tool didn't even sense my phone. I saw the FAQ and then tried to find the Qualcomm drivers in my device manager to no avail, although I did find Kedacom drivers which I could not even attempt to flash over since Windows told me that the driver I was trying to push was out of date. Here is my original post on that thread:
As you can see, I did not yet mention that I still tried pushing the driver since I haven't had a reply yet. I don't want to double-post there but I'm getting no luck elsewhere. I really want this tool to work, is there some way to force push these drivers or is that a bad idea? If it is, any other ideas?
EDIT: Nevermind. I think it's bricked pretty good, I'll probably have to give up on this. When I plug it in, it only goes to bootloader, doesn't boot into recovery, system, or even show the battery percentage when charging. Bootloader hasn't been giving me many options either since the commands I've tried aren't going through. Updating ADB right now, don't know if it's likely that it's causing issues right after I already updated it.
Click to expand...
Click to collapse
Are you starting the programs as an Administrator?
SkippRunning said:
Are you starting the programs as an Administrator?
Click to expand...
Click to collapse
Yeah, tried it again for good measure. Is there any chance I could get this issue resolved spending less than $100 by sending it to a OnePlus repair center or elsewhere? I'm not sure they do software repairs such as this, I didn't purchase a warranty since I figured I'd root this phone and I no longer know my IMEI since I can't access the phone to check.
Raeffion said:
Yeah, tried it again for good measure. Is there any chance I could get this issue resolved spending less than $100 by sending it to a OnePlus repair center or elsewhere? I'm not sure they do software repairs such as this, I didn't purchase a warranty since I figured I'd root this phone and I no longer know my IMEI since I can't access the phone to check.
Click to expand...
Click to collapse
Ive never sent my devices in for service so Im not sure about that. The fact that you have access to fastboot still though makes me think that you arent totally screwed yet. When I had stuff go wrong and I went to use to MSM tool, I didnt have the proper drivers installed, and my device never showed up in device manager. After installing a different set of drivers and rebooting my pc, the device showed up in device manager under the Ports section. I was able to get back into my device without the unbrick tool by switching the active partition. Did you say you already checked your active partition with command fastboot getvar current-slot? If you are on slot a, have you tried setting slot b as the active and seeing what happens? This is the command fastboot --set-active=b.
Here is a driver for the unbrick tool to recognize your device that might work for you. https://www.dropbox.com/s/lgt1qanfqs8pvbe/QDLoader HS-USB Driver_64bit_Setup.zip?dl=0
SkippRunning said:
Did you say you already checked your active partition with command fastboot getvar current-slot? If you are on slot a, have you tried setting slot b as the active and seeing what happens? This is the command fastboot --set-active=b.
Click to expand...
Click to collapse
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
SkippRunning said:
After installing a different set of drivers and rebooting my pc, the device showed up in device manager under the Ports section. I was able to get back into my device without the unbrick tool by switching the active partition.
Here is a driver for the unbrick tool to recognize your device that might work for you.
Click to expand...
Click to collapse
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
EDIT: I installed the driver but nothing has changed from before. The MSM tool still doesn't detect my phone, I made sure it was run as Administrator. My device drivers are still Kedacom which I attempted to update the driver using a file on my computer once again and Windows wouldn't allow it. Am I simply looking in the wrong place to manually install this driver? My device manager is set to view devices by type and plugging in my phone causes only the Kedacom USB device to appear, so I assume I don't have QDLOADER 9008 or QHUSB_BULK devices listed there. I can provide screenshots of my device manager window if it helps.
Raeffion said:
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
Click to expand...
Click to collapse
Hooray! Almost haha! It is the worst feeling when you mess up your brand new device, but as long as I have fastboot I dont stop trying to fix my mistakes. You should be able to fix it for sure.
---------- Post added at 04:35 AM ---------- Previous post was at 04:21 AM ----------
Raeffion said:
I did try setting the active partition to slot b as well, I was getting pretty much the same errors as attempting to boot from an image file. Although, I just now tried setting the partition to b and it worked. I'll try rebooting the phone to partition b now as well.
EDIT: Thankfully, setting the partition to slot b worked! My phone now has access to system and recovery once again and boots as normal. I am still in a bootloop though, so I'm attempting to install the drivers now.
Awesome, installing those drivers right now. The link provided in the beginning of the thread for the MSM Tool just wouldn't work for me since my device was detected as something that wasn't mentioned in the entirety of the thread so I couldn't install it directly via device manager as directed. This should hopefully get me up and running on the tool, I'll update this post once the drivers are installed hopefully.
EDIT: I installed the driver but nothing has changed from before. The MSM tool still doesn't detect my phone, I made sure it was run as Administrator. My device drivers are still Kedacom which I attempted to update the driver using a file on my computer once again and Windows wouldn't allow it. Am I simply looking in the wrong place to manually install this driver? My device manager is set to view devices by type and plugging in my phone causes only the Kedacom USB device to appear, so I assume I don't have QDLOADER 9008 or QHUSB_BULK devices listed there. I can provide screenshots of my device manager window if it helps.
Click to expand...
Click to collapse
On my pc, I didnt have any issues with the drivers, but when I was helping a friend over TeamViewer trying to do the same thing you are trying to do, the drivers just didnt help no matter what and it wasnt listed in the device manager. I was able to make it show properly on his pc by using the steps explained in this article. https://docs.microsoft.com/en-us/wi...boot-configuration-option?redirectedfrom=MSDN After restarting his pc, the device showed up properly in device manager with test mode enabled.
Are you able to access adb now, or still only fastboot?
SkippRunning said:
Are you able to access adb now, or still only fastboot?
Click to expand...
Click to collapse
I embarrassingly don't even really remember all the specifics about how ADB works, although I don't think I have access since I'm in a bootloop when I launch Android. Unless I have access to ADB via fastboot or recovery, I don't think I do.
SkippRunning said:
On my pc, I didnt have any issues with the drivers, but when I was helping a friend over TeamViewer trying to do the same thing you are trying to do, the drivers just didnt help no matter what and it wasnt listed in the device manager. I was able to make it show properly on his pc by using the steps explained in this article. After restarting his pc, the device showed up properly in device manager with test mode enabled.
Click to expand...
Click to collapse
Yeah I had no idea what Windows test mode was. Before I rebooted just now to install the drivers you provided, I actually launched into Windows test mode with no command from me telling Windows to. I thought Windows invalidated my license yet again tbh, glad to know it didn't. I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Raeffion said:
I embarrassingly don't even really remember all the specifics about how ADB works, although I don't think I have access since I'm in a bootloop when I launch Android. Unless I have access to ADB via fastboot or recovery, I don't think I do.
Yeah I had no idea what Windows test mode was. Before I rebooted just now to install the drivers you provided, I actually launched into Windows test mode with no command from me telling Windows to. I thought Windows invalidated my license yet again tbh, glad to know it didn't. I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Click to expand...
Click to collapse
It will just make driver installing issues less likely. When you boot your phone, what happens on the screen? Does it get stuck on a certain screen or just restart over and over? You can see if adb can see your device with the command adb devices, and it should list your device. If not, try fastboot devices and it should be listed. You need to put the device into EDL mode for the unbrick tool to work, and for it to be shown in device manager. My friends device manager listed Kedacom just like yours, and I didnt do anything to that at all. I just used test mode, installed the Qualcomm drivers, put the phone into EDL mode and the unbrick tool should recognize it. If your phone is listed when you type adb devices, you can use command adb reboot edl to enter that mode needed for the unbrick tool.
Raeffion said:
I don't think I'm in test mode now, so I'm giving that a go right now. My computer takes a while to warm up so I'll let you know the results in a bit.
Click to expand...
Click to collapse
Sadly my drivers haven't changed. I uninstalled and reinstalled the installation file you gave me since I first installed it via WWAN-DHCP instead of ETHERNET_DHCP. I use a VPN so I figured that may have affected the installation, although for some reason I didn't think to just turn off the VPN when I reinstalled. Regardless, I don't think my VPN or the way I installed the driver is the cause of the drivers mentioned not being found in my device manager, so I'm likely not going to bother.
Raeffion said:
Sadly my drivers haven't changed. I uninstalled and reinstalled the installation file you gave me since I first installed it via WWAN-DHCP instead of ETHERNET_DHCP. I use a VPN so I figured that may have affected the installation, although for some reason I didn't think to just turn off the VPN when I reinstalled. Regardless, I don't think my VPN or the way I installed the driver is the cause of the drivers mentioned not being found in my device manager, so I'm likely not going to bother.
Click to expand...
Click to collapse
Another problem that can cause your phone to not show up in device manager is the usb port you are using. Have you tried any other ports? Are you able to shut your phone all the way off by holding power until it turns off? If you can unplug the phone and turn it off, then hold the volume up and volume down buttons together, then plug the cable back into the phone and it should put it into EDL mode.
SkippRunning said:
When you boot your phone, what happens on the screen? Does it get stuck on a certain screen or just restart over and over?
Click to expand...
Click to collapse
It just shows the boot animation, it doesn't restart.
SkippRunning said:
You can see if adb can see your device with the command adb devices, and it should list your device. If not, try fastboot devices and it should be listed.
Click to expand...
Click to collapse
ADB shows no devices attached, fastboot shows my device.
SkippRunning said:
You need to put the device into EDL mode for the unbrick tool to work, and for it to be shown in device manager. My friends device manager listed Kedacom just like yours, and I didnt do anything to that at all. I just used test mode, installed the Qualcomm drivers, put the phone into EDL mode and the unbrick tool should recognize it. If your phone is listed when you type adb devices, you can use command adb reboot edl to enter that mode needed for the unbrick tool.
Click to expand...
Click to collapse
I seem to have been missing a vital part of information. I don't know why the term "EDL" just went over my head, I probably just associated it was fastboot mode when I looked it up. How do I get into EDL mode? Is it safe to assume the method listed here works for the OnePlus 7T?
Raeffion said:
It just shows the boot animation, it doesn't restart.
ADB shows no devices attached, fastboot shows my device.
I seem to have been missing a vital part of information. I don't know why the term "EDL" just went over my head, I probably just associated it was fastboot mode when I looked it up. How do I get into EDL mode? Is it safe to assume the method listed here works for the OnePlus 7T?
Click to expand...
Click to collapse
Fastboot mode and EDL mode are two different things. I have never used the fastboot to EDL method, but I have read about it and I assume it should work atleast on some devices. Unplugging from pc and turning the phone off, then holding both volume buttons and then plugging the cord into the device should enter EDL mode without commands.
SkippRunning said:
Fastboot mode and EDL mode are two different things. I have never used the fastboot to EDL method, but I have read about it and I assume it should work atleast on some devices. Unplugging from pc and turning the phone off, then holding both volume buttons and then plugging the cord into the device should enter EDL mode without commands.
Click to expand...
Click to collapse
I must have assumed that it was fastboot mode since when I held those buttons and plugged it in, I'd always launch into fastboot mode. Perhaps it's different with the US version? That's the version I have.
Raeffion said:
I must have assumed that it was fastboot mode since when I held those buttons and plugged it in, I'd always launch into fastboot mode. Perhaps it's different with the US version? That's the version I have.
Click to expand...
Click to collapse
The only version I have used at all is the US one. You could try holding both volume buttons for a few seconds before plugging the cable into the phone, but if that doesnt work you can try the fastboot to edl method. I have no experience with it at all though so I dont know if it works with this device or not, but you would just open the edl.cmd file and it should put the phone into edl mode.
https://www.dropbox.com/s/951fm98u5rd2kjr/FASTBOOT-EDL-MODE.zip?dl=0
SkippRunning said:
The only version I have used at all is the US one. You could try holding both volume buttons for a few seconds before plugging the cable into the phone, but if that doesnt work you can try the fastboot to edl method. I have no experience with it at all though so I dont know if it works with this device or not, but you would just open the edl.cmd file and it should put the phone into edl mode.
https://www.dropbox.com/s/951fm98u5rd2kjr/FASTBOOT-EDL-MODE.zip?dl=0
Click to expand...
Click to collapse
It just boots me into Android sadly. I don't know that there's any way to get into EDL mode for me. Possibly due to my use of the experimental TWRP and mauronofrio's Stock Fastboot ROM tool.
Raeffion said:
It just boots me into Android sadly. I don't know that there's any way to get into EDL mode for me. Possibly due to my use of the experimental TWRP and mauronofrio's Stock Fastboot ROM tool.
Click to expand...
Click to collapse
What happens if you use command fastboot boot boot_stock_10.0.5_US.img using this file?
https://www.dropbox.com/s/cl9l662xkyey5oq/boot_stock_10.0.5_US.img?dl=0
SkippRunning said:
What happens if you use command fastboot boot boot_stock_10.0.5_US.img using this file?
Click to expand...
Click to collapse
No dice.