Related
Hi guys, is there a way to unroot my phone and relock the bootloader without needing to do anything on the phone itself? The screen is broken completely and, though the phone turns on, the screen remains turned off. I do not know if my network provider will fix my phone but I thought it would be worth a shot and I want to cover all the bases before I ask.
Illiok said:
Hi guys, is there a way to unroot my phone and relock the bootloader without needing to do anything on the phone itself? The screen is broken completely and, though the phone turns on, the screen remains turned off. I do not know if my network provider will fix my phone but I thought it would be worth a shot and I want to cover all the bases before I ask.
Click to expand...
Click to collapse
Make sure you have installed Fastboot and ADB drivers..
You only need Fastboot drivers!
Boot Nexus into Fastboot mode!
Open terminal / command prompt =CMD and navigate to folder where is your fastboot files which you need...
Download Stock Google's factory image and extract the files into the fastboot folder and then open flash-all.bat (windows) or flash-all.sh (linux)
Let it finish flashing and let your nexus rest 5 minutes after installation, then pull battery off and put it back and boot into fastboot mode again
Now:
type into CMD or into terminal:
fastboot oem lock
That's it! Easy... and you don't have to see nothin' from Nexus...
Thanks for taking the time to help me out, really appreciate it. If I download mskip's Galaxy Nexus toolkit then will that give me the drivers I need?
Illiok said:
Thanks for taking the time to help me out, really appreciate it. If I download mskip's Galaxy Nexus toolkit then will that give me the drivers I need?
Click to expand...
Click to collapse
You should really drop the toolkit, if you're asking how to relock bootloader and unroot...
Concerning the drivers, there's this really nice package here, there's also instructions for windows 8.
Basically, the steps are those manumanfred told you, although if you're feeling lost, http://forum.xda-developers.com/showthread.php?t=1626895 is the thread you should look up and read several times at least the first post.
Is there a way to get pictures etc off my phone without being able to activate the screen? When I connect my phone to my computer using the USB cable, it shows as a "portable device" as per usual but when I open it up there is no storage icon and no files.
My phone doesn't have a sim in it but it does have a pattern unlock because it has a VPN saved on it. I know the phone works despite the screen being broken because when I boot it up I get a flashing LED and notification sounds for my e-mail.
Did you had USB debugging on and the PC's RSA key added to the device? Then yes, you can 'adb pull /sdcard/', it will give you a full backup of /sdcard/.
a manta wrote this.
The easiest way is to use one of the fine toolkits which will guid you through the whole process:
For Mac: http://forum.xda-developers.com/showthread.php?t=1790399
For Windows: http://forum.xda-developers.com/showthread.php?t=1392310
USB debugging might have been turned off - I can't remember fully. I recently tried to install fresh drivers as per the other poster's suggestions - will that reset the RSA key permission for my PC?
As for the toolkits, I have one but if I remember correctly the toolkit says that some traces of root will be left on the phone which is why I was inquiring about a way to unroot and relock without any traces of root having taken place.
Illiok said:
USB debugging might have been turned off - I can't remember fully. I recently tried to install fresh drivers as per the other poster's suggestions - will that reset the RSA key permission for my PC?
As for the toolkits, I have one but if I remember correctly the toolkit says that some traces of root will be left on the phone which is why I was inquiring about a way to unroot and relock without any traces of root having taken place.
Click to expand...
Click to collapse
As for the RSA key, I don't think changing drivers will matter. Try it. 'adb devices' should return your SN.
As for safely unrooting or whatever, just go back to stock through factory images: they will return your device to full stock, pronto. Use fastboot commands instead of a toolkit.
a maguro wrote this.
I have never done this manually before but in your first post I believe you linked to a guide for me to read so I'm sure I'll find the information I need from that. By the way, is there a way for me to wipe all data stored on my Galaxy Nexus after I have pulled everything from it?
My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Have you installed the LG drivers for your pc and tried the unbrick method?
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
twill1987 said:
My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Click to expand...
Click to collapse
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Yes
riki126 said:
Have you installed the LG drivers for your pc and tried the unbrick method?
Click to expand...
Click to collapse
Yes I tried that. The drivers won't install. I even used another windows 8 computer my roommate has and switched out
the usb cables, still came back "unknown device"
shabbypenguin said:
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
Click to expand...
Click to collapse
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Okay
stulzerl said:
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
twill1987 said:
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
Click to expand...
Click to collapse
I've had similar issues when i had my optimus g. I had to use a pc with xp to flasht he phone, dunno why though. You could give that a shot.
twill1987 said:
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Click to expand...
Click to collapse
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Thanks
WeActOnImpulse said:
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
Click to expand...
Click to collapse
I have tried this and unfortunately since the USB drivers aren't detected by the computer there is no way for me to flash back to stock.
Thanks for the information though, I appreciate it.
shabbypenguin said:
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Click to expand...
Click to collapse
Wow, that sounds awesome. I followed most of that. I access download mode on the device by pressing vol up and down simultaneously and plugging in the usb cable. I am more willing to try this, and if it works I will pay you from my paypal. I guess all I need now are those files to run to the sd card. I read the tutorial you posted for the samsung and downloaded the windows disk manager. I am eager to try this method, though it is admittedly very new to me.. If you can post those files, I will follow the instructions you give and pay you a little bit of money for your help!
I am a broke college student so it won't be much, but I really appreciate your response and information on this method with the qualcomm s4.
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Just wrote it to sd card
shabbypenguin said:
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Click to expand...
Click to collapse
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
twill1987 said:
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
Click to expand...
Click to collapse
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Possible hope??
shabbypenguin said:
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Click to expand...
Click to collapse
I meant I used the windows tool to write the debrick.img to the sd card. But no dice, the device isn't recognised.
However! I installed a driver clean up tool and now if I plug in the device it is recognized as Android Original ADB Interface.
The LG Flashtools even says the port is ready! But I get the error code "10" "device cannot start, A request for the USB device descriptor failed."
So now I am stuck on that instead lol. This just sucks.
that sucks about the sdcard, it must be because you arent "truly" bricked. sorry i thought it would help ya :/.
What is the driver repair tool you used? I know this thread is old but I'm having the same problem. I was trying to root my E980 and now my computer wont recognize my device. The phone works perfect, its just when I plug it in to the computer it isnt recognized. How can I fix this?
+1
Just wondering if anyone's come across a solution to this besides a sledge hammer... been having the same "Code 10: Device failed to start" when in Download Mode, though Windows finds a driver fine when the phone is stuck on the LG screen... doesn't help much, though, 'cause it won't receive adb commands. I manually installed the LG USB Composite Device driver, which added a modem and a COM port, both of which Windows recognized to be active, but the LG FlashTool USB Viewer showed no open pipes. I'm a relative noob, so please feel free to point out the obvious, like an alternative to adb that the phone can always receive or a way to brick it the rest of the way so the MicroSD trick will work.
I came across this problem like the OP and just wanna let everyone know that you have to use computer with USB 2.0 port then the driver issue would be fixed.
Hello, Friends, I wanted to unlock an LG G4 T-mobile for a customer with "Device unlock app"
after the flashing using LG Tools from z3x the phone now is a dead black screen. When I plugged into the computer I can hear the sounds it's connected but nothing is showing. Need help to turn it back on thanks. I can't even load in Download mode.
Thanks for any help.
umarmansare said:
Hello, Friends, I wanted to unlock an LG G4 T-mobile for a customer with "Device unlock app"
after the flashing using LG Tools from z3x the phone now is a dead black screen. When I plugged into the computer I can hear the sounds it's connected but nothing is showing. Need help to turn it back on thanks. I can't even load in Download mode.
Thanks for any help.
Click to expand...
Click to collapse
Can you boot to recovery? Should be the power + volume down combo until the logo comes up.
Alternatively,
Have you installed ADB and fastboot drivers?
Can ADB see your device when you're plugged into the computer? Perhaps you can get into bootloader mode through ADB if so.
Connect LG G4 to your computer.
On the PC, access the Android SDK folder (download it if you don't have it).
There, open a command prompt window by pressing shift + right click on any blank area.
In the CMD window, execute the command " adb reboot bootloader " without quotes. If you haven't enabled USB debugging, you may be out of luck.
Tried but not working
Hello, Friend Thank you very much for your time and efforts while typing this to help me out. I did but still doesn't recognize took the owner. Technically the phone is dead.
umarmansare said:
Hello, Friend Thank you very much for your time and efforts while typing this to help me out. I did but still doesn't recognize took the owner. Technically the phone is dead.
Click to expand...
Click to collapse
why you use flash tools.? you should ut use LGUP and KDZ file.
what is this app customer with "Device unlock app"
unlock what.??
umarmansare said:
Hello, Friends, I wanted to unlock an LG G4 T-mobile for a customer with "Device unlock app"
after the flashing using LG Tools from z3x the phone now is a dead black screen. When I plugged into the computer I can hear the sounds it's connected but nothing is showing. Need help to turn it back on thanks. I can't even load in Download mode.
Thanks for any help.
Click to expand...
Click to collapse
1. Point us to that dubious unlock app please!
2. Very very often an issue occurs because a user do not use the correct commands or important error messages are thrown and the user do not show. So please write EXACTLY what you do. For example the exact command to proof the connection (e.g. "adb devices") and the exact result. easiest and best way is to just make a screenshot of anything.
3. Another example is how to you try to get into download mode? There are some guides which do not work so explain what you do always helps others to help you.
I use the following method:
Pull out battery
Plugin USB cable connected to the pc
Press vol Up and keep pressed while putting battery back in place
4. To avoid driver issues you should consider to use FWUL ( https://tinyurl.com/FWULatXDA ) for anything else then kdz flashing (this requires windows)
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
1. Point us to that dubious unlock app please!
2. Very very often an issue occurs because a user do not use the correct commands or important error messages are thrown and the user do not show. So please write EXACTLY what you do. For example the exact command to proof the connection (e.g. "adb devices") and the exact result. easiest and best way is to just make a screenshot of anything.
3. Another example is how to you try to get into download mode? There are some guides which do not work so explain what you do always helps others to help you.
I use the following method:
Pull out battery
Plugin USB cable connected to the pc
Press vol Up and keep pressed while putting battery back in place
4. To avoid driver issues you should consider to use FWUL ( https://tinyurl.com/FWULatXDA ) for anything else then kdz flashing (this requires windows)
.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Hi, Thank you very much for taking your time and energy to answer me. I used Z3x to Factory the LG G4 (T-Mobile) I wanted to flash it by downgrading before to see if it could work. this is how I break the phone with the downgrading. So now the phone is not recognizing by the computer as Modem when I plugged in, I see it only as External Drive.
umarmansare said:
Hi, Thank you very much for taking your time and energy to answer me. I used Z3x to Factory the LG G4 (T-Mobile) I wanted to flash it by downgrading before to see if it could work. this is how I break the phone with the downgrading. So now the phone is not recognizing by the computer as Modem when I plugged in, I see it only as External Drive.
Click to expand...
Click to collapse
you cannot downgrade h811 it has antirollback. and in autoprime 20i thread says it bricks phone.. if it was on MM and flashed lower antirollback.
what is Z3x.???
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.
Sup boys i am scared like a mf right now.
EDIT: Forgot to mention Blankflash doest work either,
FAILED: qb_flash_singleimage()->device_open()->error opening device
So to explain the situation i used the Corvus OS GSI and its been due for a update for a while. Today i updated it with OTA.
It didnt boot, no worries GSI didnt work for me without clearing userdata, so i did that and it booted.
Now for setting up magisk i saw it had an install after OTA option, and i did that thinking it was a neat little feature, pressed Reboot
And it shut down, black screen, no response from any buttons, no response from charging, no fastboot or adb devices show up on my laptop.
Its like the motherboard suddenly died.
I have backups for everything so i am not interested in getting anything from the device, but getting the money for another phone would be a pain.
Second edit and solution:
For the probably one other guy using Linux out there, blank flash wont work, use windows and install LMSA to get the correct driver.
You can try looking into restoring your phone using Blankflash. Look for guides here on XDA or on Tg.
IF you can see your device listed in the Device Manager on PC, you can probably still save it.
And for the love of of god, NEVER update a GSI with OTA, it will never work.
Kuntitled said:
You can try looking into restoring your phone using Blankflash. Look for guides here on XDA or on Tg.
IF you can see your device listed in the Device Manager on PC, you can probably still save it.
And for the love of of god, NEVER update a GSI with OTA, it will never work.
Click to expand...
Click to collapse
qboot seems to see it but refuses to flash it, and also no OTA, noted.
KAN7A said:
qboot seems to see it but refuses to flash it, and also no OTA, noted.
Click to expand...
Click to collapse
So what did you figure out? I have the same affliction. Whether it's qboot, QTSP, fastboot or adb, it just isn't wanting to make a connection in order to flash anything.
treysky54 said:
So what did you figure out? I have the same affliction. Whether it's qboot, QTSP, fastboot or adb, it just isn't wanting to make a connection in order to flash anything.
Click to expand...
Click to collapse
First use windows, install Lenovo Rescue and Smart Assistant, this installs the correct drivers.
Reboot your PC to make sure the drivers are loaded.
And Follow the blankflash instructions aka just run the BAT file in CMD.
It will say its waiting for a device.
After that press Volume Down and Power On at the same time and remove the USB cable from the phone and insert it again and again until qboot starts to flash it (dont remove the cable too fast so you dont miss it).
This is what worked for me and i did il like a few nights ago.
You want to make sure you grab the right Blankflash too and all that.
But if your phone boots aka starts you dont really need blankflash you just have not setup something correctly or the cable itself is faulty or does not support data transfer.
KAN7A said:
First use windows, install Lenovo Rescue and Smart Assistant, this installs the correct drivers.
Reboot your PC to make sure the drivers are loaded.
And Follow the blankflash instructions aka just run the BAT file in CMD.
It will say its waiting for a device.
After that press Volume Down and Power On at the same time and remove the USB cable from the phone and insert it again and again until qboot starts to flash it (dont remove the cable too fast so you dont miss it).
This is what worked for me and i did il like a few nights ago.
You want to make sure you grab the right Blankflash too and all that.
But if your phone boots aka starts you dont really need blankflash you just have not setup something correctly or the cable itself is faulty or does not support data transfer.
Click to expand...
Click to collapse
Yeah it seems getting the button pushes right was the hardest part for me. Your button/plug idea is far superior, very nice.
treysky54 said:
Yeah it seems getting the button pushes right was the hardest part for me. Your button/plug idea is far superior, very nice.
Click to expand...
Click to collapse
Its hard to time things righ with a blank screen and no other feedback lol
That felt more natural and I am glad it helped!