Database Users

[Q] Computer doesn't recognize USB S4 Sprint

Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!

swagganation said:
Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!
Click to expand...
Click to collapse
Not sure if this will work, but there's a mobile odin you can try to use.
And you can get stock ROM there.

Salil999 said:
Not sure if this will work, but there's a mobile odin you can try to use.
And you can get stock ROM there.
Click to expand...
Click to collapse
Ii'm not rooted anymore so mobile odin doesn't work

swagganation said:
Ii'm not rooted anymore so mobile odin doesn't work
Click to expand...
Click to collapse
Try and download a ROM that is pre-rooted. Maybe that will work!

Salil999 said:
Try and download a ROM that is pre-rooted. Maybe that will work!
Click to expand...
Click to collapse
Do you know how I would install a rom that's prerooted without my phone being rooted or being able to connect to a computer via usb?

swagganation said:
Do you know how I would install a rom that's prerooted without my phone being rooted or being able to connect to a computer via usb?
Click to expand...
Click to collapse
You're should have a custom recovery installed... At least that way you wouldn't need your computer. Otherwise you'd have to do it through Odin, but like you said in the OP, you can't connect to USB. Is your device rooted?

swagganation said:
Hello!
I think I somehow deleted a crucial file...
Okay, so my phone won't connect to my computer anymore. I am using Windows 8 so aside from Windows 8 automatically downloading the drivers on its own, I took additional steps and downloaded the drivers directly from samsungs site. I've tried using different ports, different usb cables and different computers. All that happens is a lightning bolt telling me my phone is charging.
My phone used to be rooted. When I noticed the problem, I unrooted the phone and tried restoring the phone. (I tried booting in recovery and doing it that way as well as restoring it through settings).
I've downloaded just about every app that has the word 'mount' in it to see if it will help and nothing happens.
Every time I restore my phone, the first thing that pops up is a notification saying that samsung link has stopped working. I'm on android 4.2.2
Whenever I've restored my phone in the past, I've always been successful but that was also because I was able to flash a factory ROM through odin on my computer.
When I put the phone in developer mode, it shows in the corner:
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
Root checker says I am not rooted so I'm guessing that the BINARY and STATUS is coming up as custom because I am not fully unrooted (however, I had the problem of not being able to connect via usb when I was rooted).
If you have any ideas, I will definitely try them!
Oh, one more thing. Before my phone stopped connecting to my computer, I purchased additional batteries for my phone. I say this because It had been a fairly long time before I realized that my phone wouldn't connect to my computer because I no longer used my computer to charge my phone. And I say that because when I was rooted, I used titanium backup as well as CMW and neither was able to restore my phone back to a time that the usb worked again.
Okay, I think that's it. It's a lot of details but I didn't want to waste anyone's time coming up with ideas if I had already tried one.
Thank you!
Click to expand...
Click to collapse
IF you can get to download mode Then jump over to this thread. Download the zipped file (from first or second post), extract the file - just to the .tar.md5 file.
While waiting for the download charger your phone to at least 50%
Also download Odin 3.x. get that here. unzip one of the Odins - I've been using 3.07
To launch Odin make sure you right-click and choose run as administrator!
Once Odin is launched go to the PDA box and select the .tar.md5 file you downloaded.
Make sure you have NOT selected re-partition. you can leave auto reboot and f.reset time checked though.
Now get into download mode - Power button + Home key + Volume down. Hold until you are asked to confirm going into download mode by selecting up volume.
Plug your phone into your computer and a com port should show in Odin3.
If it does then select start and wait till it finishes completely - it will say pass; your phone will actually reboot too.
Go through setup and there you go. new phone.
Then to root just use CF-Autoroot

My computer stopped recognizing my S4 recently, too. Odin wouldn't see it, couldn't connect it as a drive, etc. It had not been very long between when it worked and when it didn't, and I had installed a bunch of new Java stuff for (JDK7, Netbeans, Eclipse, etc). Tried the wife's S3 and same deal. So I uninstalled my Samsung drivers and Kies and booted my Win7 laptop. Reinstalled drivers, no joy. Reinstalled Kies and let it do all it's updates and that fixed the issue. Rooted, MDL, stock rom.

jejb said:
My computer stopped recognizing my S4 recently, too. Odin wouldn't see it, couldn't connect it as a drive, etc. It had not been very long between when it worked and when it didn't, and I had installed a bunch of new Java stuff for (JDK7, Netbeans, Eclipse, etc). Tried the wife's S3 and same deal. So I uninstalled my Samsung drivers and Kies and booted my Win7 laptop. Reinstalled drivers, no joy. Reinstalled Kies and let it do all it's updates and that fixed the issue. Rooted, MDL, stock rom.
Click to expand...
Click to collapse
When uninstalling old drivers make sure you go to Device manager and go to View >Sho Hidden devices and remove them too! Remove everything - all left over devices, all software and even directories for said software; Revo uninstaller works well.
Also try a brand new USB cable. Though that may not be it, I've seen that alone solve all kinds of problems! Really just a brand new cable.

If you haven't tried this already, try and make sure USB debugging is enabled?

Need root without computer, bootloader unlocked...

I have checked at least hundred threads now, but my problem seems unique! (First time this happened to me )
When I connect my N7 (WiFi, 32 GB) to my laptop (Win 8.1), it says "USB device not recognized - The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." In Device Manager, it is like the image attached, no other recognition for the device. Upon selecting Properties, It says "Code 43" in status, also says "A request for the device descriptor failed". That happened with 2 computers; I used 2 cables (both worked previously). So it means N7's USB port is somehow malfunctioning. But it gets charged as well as ever!!
This started after I tried an OTA update of 4.4 earlier (the download had not completed, but a prior small update (1-3 MB) was installed).
Now, I have Android SDK (latest version) and installed those google USB driver and platform-tools. I have NRT 1.7.9 (which worked for me previously). But I cant get my N7 to answer to ADB requests. [highlight]Upon connecting USB, it says "Charging (USB)" but no option regarding PTP or MTP appears.[/highlight] I have developer tools installed. I followed the instructions given in NRT about ADB installation to the letter but still no progress. I have tried a factory reset too.
BTW, I dont have a custom recovery flashed. It vanished along with the precious root privilage.
Now the N7 is in Android 4.3 (JWR66Y), bootloader is unlocked, SuperSU is Installed (but do not work due to having no root access and I cant even Uninstall it for the same reasons!!!). Now the OTA update also do not work mysteriously (it downloaded the 4.4.2 update and went on to install it, but as the bar started filling, it only said "error" and stopped!!! no explanations whatsoever!!!!). I will be very happy any of the followings:
[highlight]1. root without computer (wireless ADB is also welcome),
2. working OTA, or anyhow the 4.4.2 update
3. working ADB connection with my laptop.[/highlight]
Any help will be very helpful... Thank you in advance...

If you can not communicate via USB hardware, then using fastboot is not an option (obviously). And so therefore the lock state of your bootloader is quite irrelevant, too.
Even if you were to get adb over tcp (WiFi) working, that doesn't get you much, as an adb login shell on a stock ROM is just an unprivileged user; it's not much different from using a terminal emulator app (from a privilege escalation point of view).
The only other thing left is an exploit (privilege escalation) method that runs under the stock ROM. Something similar to that Motochopper exploit from some time ago. I suppose that particular hole was plugged; whether or not a new exploit exists, I can't tell you.
You could always just send the tablet back for repair. Seems like not having a working USB port is pretty crippling to someone who wants to root, flash ROMs, copy backups off the tablet, etc.

Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...

Aaron061992 said:
Thank you for the replying...
Actually I lack warranty as I bought this from eBay weeks before it was officially available in India. Therefore I kept that repair thing as a last resort. I am now trying it through Linux. And being a noob there, its going too slow. However I have got the ADB working and detecting the device, so its not a port issue (I dont know why the hell windows was so adamant on that point!)... But I am yet to figure out how to flash the image... thank you for the tip over wi-fi, i was actually hoping to wait for it...
Click to expand...
Click to collapse
Well that is very different than having a broken USB port.
You probably noticed in your search that this forum is littered with thousands of reports from users complaining about their Windows drivers. It gets pretty old, frankly. (No drivers are needed at all for Linux or Mac OS/X).
Here is a suggestion that I made in another thread just a few days ago about using fastboot under Linux - in your case, you will be on your way after installing a recovery, e.g.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-grouper.img
I even attached the most recent version of the (Android SDK Linux) fastboot to that post.
Note that you don't even need a dual-boot PC or PC with a semi-permanent Linux install; you can do the whole thing with one of those "Live CD" boots and a USB stick.
good luck

[Q] Tmobile D801 will not boot FIXED

Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now

zaft1 said:
Just switched over to Tmobile from Sprint and before even signing into google i went ahead and tried to root my phone. Rooting was a success. Used Flashify to flash twrp recovery. Downloaded rooted stock D80110G rom and began debloating it (like I did with the Sprint version) and then booted to recovery, wiped twice, flashed and reboot. Well, now it will just keep rebooting back to recovery and thats it!
I still have access to download mode
still have access to custom recovery
Did not do a nand backup unfortunately
cant mount in twrp because computer no longer recognizes phone!
shows up under unknown devices as LG D801
Tried the stock recovery using LG Flash tool posted in generals but ran into the "can not update because of your device policy" or something like that. Reinstalled and tried it again many times, even switching languages and countries (the last step)
Tried using the ubuntu method posted by partager.info but even ubuntu does not recognize the device. Matter of fact nothing even happens when i plug the phone in.
Tried reinstalling drivers, tried on 2 different laptops (one windows 8.1, one windows 7, and an ubuntu usb boot) and my desktop computer (windows 8.1) and am just unable to mount using twrp because none of them recognizes it!
tried using the adb sideload but twrp just stays trying to load adb sideload forever and adb terminal cant even find the connected usb device.
Tried factory reset but that just takes me to twrp.
I've redownloaded the rooted stock rom and left everything as is. I'm assuming I just need to get it onto the phone somehow so I can flash it.
I have an otg cable but not quite sure how to work it wit twrp or if that's even an option; I've just purchased it.
I feel like I've exhausted my options. Anything else I can try?
Thanks in advance.
EDIT: Should've just used Titanium to debloat instead of trying to do a fresh install! I know I know
Figured it out! not sure how to delete this thread now
Click to expand...
Click to collapse
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!

mnb91 said:
Hi, I have the exact same problem as you. Did you end up using otg? how did you finally end up getting a rom in your device and flashing it? I sent you a pm hope fully you see it. please respond im desperate!
Click to expand...
Click to collapse
Hey sorry, I haven't been on the site for a couple days.
I used the flashtool to go back to stock. Had to enter download mode and work from there. The big issue I was having was a driver issue. Uninstalled every driver related to android and then reinstalled after a restart and that did the trick. For some reason android phones are giving me a lot of driver issues on windows 8.1
follow these steps here but make sure you read a chunk of the thread as the steps in the main post are not complete
http://forum.xda-developers.com/showthread.php?t=2432476

After 10 hours of failing finally side loaded lollipop

I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.

ImjuzCY said:
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
Click to expand...
Click to collapse
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck

Zaphodspeaks said:
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Click to expand...
Click to collapse
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway

ImjuzCY said:
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
Click to expand...
Click to collapse
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.

Zaphodspeaks said:
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Click to expand...
Click to collapse
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.

ImjuzCY said:
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
Click to expand...
Click to collapse
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins

Zaphodspeaks said:
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Click to expand...
Click to collapse
Luckily i was using stock kernel. Ive disabled root beforehand and the problems i faced was all on the pc side. Evrything should be easy if my pc doesnt show so much problems. And i like to take challenges so i chose to sideload haha

Go back from Android 12?

Is there any way to go back to stock from Paranoid Android 12 besides the MSM tool? I have been unable to get my computer to recognize the phone in EDL mode with the MSM tool, not sure if it's because of my cables, lack of USB 2.0 ports or that I'm on Windows 11 but I cannot get that tool to find the phone once it's in edl mode.
Can I flash the stock Android 11 images somehow or is the ONLY way through the MSM tool? If that's my only options I guess I'm going to have to find a Windows 10 computer with 2.0 usb ports.

Bro you can also flash images through Windows Powershell..

I have an old I3 with Windows 7 on it that works well with the MSM tool. You can just hard reset your phone with it hooked up and the MSM tool will catch it and fire up. I have tried it on my newer laptop with Win 11 and other newer machines and never got it to work once. I think it has something to do the Qualcom driver that doesn't work on these newer machines.

magicmckinney said:
I have an old I3 with Windows 7 on it that works well with the MSM tool. You can just hard reset your phone with it hooked up and the MSM tool will catch it and fire up. I have tried it on my newer laptop with Win 11 and other newer machines and never got it to work once. I think it has something to do the Qualcom driver that doesn't work on these newer machines.
Click to expand...
Click to collapse
That's alright bro, you don't definitely need the Windows Powershell. Just use Cmd

magicmckinney said:
I have an old I3 with Windows 7 on it that works well with the MSM tool. You can just hard reset your phone with it hooked up and the MSM tool will catch it and fire up. I have tried it on my newer laptop with Win 11 and other newer machines and never got it to work once. I think it has something to do the Qualcom driver that doesn't work on these newer machines.
Click to expand...
Click to collapse
Win 7 can cause problems if you're going between the phones OS and fastboot, drivers can't seem to populate the same space In device manager..
It's quite odd.
Windows 10 works as expected, no need to install anything, from a fresh build of windows, just plug in your phone then turn on usb debugging and accept the prompt on your phone, copy over ADB / fastboot into a folder ok root of C (C:/ADB)
Then open a command prompt / powershell window pointed there then query ADB devices, it should work fine...then test fastboot from the same session, windows 7 will work with the phone booted to system and maybe EDL but fastboot can have issues.

GatorsUF said:
Is there any way to go back to stock from Paranoid Android 12 besides the MSM tool? I have been unable to get my computer to recognize the phone in EDL mode with the MSM tool, not sure if it's because of my cables, lack of USB 2.0 ports or that I'm on Windows 11 but I cannot get that tool to find the phone once it's in edl mode.
Can I flash the stock Android 11 images somehow or is the ONLY way through the MSM tool? If that's my only options I guess I'm going to have to find a Windows 10 computer with 2.0 usb ports.
Click to expand...
Click to collapse
Quickest way is MSM mate.
You'll need to unlock the bootloader again but besides that it's the fastest method back, plus you won't have any left over system or images from your previous phone's firmware.
Seeing as we don't yet have official android 12, you are still essentially on Android 11. It's just system images were installing..
Which is why I haven't bothered to install it yet.

Hey Zladz...... how about going back from evoX12 to evoX11? I miss root and Swift backups. This 12 works very well and it`s eye candy but if there`s a way to go back....?? My OOS base is from last spring...i think it`s 10.4.4 or something.

janitor9 said:
Hey Zladz...... how about going back from evoX12 to evoX11? I miss root and Swift backups. This 12 works very well and it`s eye candy but if there`s a way to go back....?? My OOS base is from last spring...i think it`s 10.4.4 or something.
Click to expand...
Click to collapse
Again mate MSM.. just pick the version you want to go back to.
I've only ever used 11.4.4 but I'd guess you can pick whatever you wanted.
Just be mindful when downgrading, there always a risk, although the MSM tool has never failed me.
Re: root, you can use root on 10, 11 or 12.
Follow my payload dumper/magisk guide in the guides section, the principle is exactly the same, plus bare in mind Evo 12 is still using 11 as a base, 12 hasn't been released yet.

dladz said:
Again mate MSM.. just pick the version you want to go back to.
I've only ever used 11.4.4 but I'd guess you can pick whatever you wanted.
Just be mindful when downgrading, there always a risk, although the MSM tool has never failed me.
Re: root, you can use root on 10, 11 or 12.
Follow my payload dumper/magisk guide in the guides section, the principle is exactly the same, plus her in mind Evo 12 is still using 11 as a base, 12 hasn't been released yet.
Click to expand...
Click to collapse
Thanks again ! I was hoping that i don't have to go back OOS again but i have time enough to do that. I'am going to use your patched image to root because i'am on BA. Easier that way

janitor9 said:
Thanks again ! I was hoping that i don't have to go back OOS again but i have time enough to do that. I'am going to use your patched image to root because i'am on BA. Easier that way
Click to expand...
Click to collapse
Ah yep you can definitely do that..
If you want the patched boot image for magisk 23 for Evo 6 (android 11) then here it is.
Only ever boot it though, then click magisk / install / install directly - this will make it permanent, with booting an image, soon as you reboot it'd revert the changes made by what you booted.

janitor9 said:
Thanks again ! I was hoping that i don't have to go back OOS again but i have time enough to do that. I'am going to use your patched image to root because i'am on BA. Easier that way
Click to expand...
Click to collapse
You could maybe jump back to the previous version of Evo, I personally haven't done this but in theory it should work... Any issues though and you'll need to further m format anyway, so up to yourself

dladz said:
You could maybe junk back to them previous version of Evo, I personally haven't done this but in theory it should work... Any issues though and you'll need to further m format anyway, so up to yourself
Click to expand...
Click to collapse
Tried go back with "adb sideload" previous version,cleaded data but it booted with 12
To be clear....Now i have to MSM to 11.0.4.4 (that one i downloaded) and should i let it update to latest firmware 11.0.10.10 and then unlock bootloader and do the usual stuff?

janitor9 said:
Tried go back with "adb sideload" previous version,cleaded data but it booted with 12
To be clear....Now i have to MSM to 11.0.4.4 (that one i downloaded) and should i let it update to latest firmware 11.0.10.10 and then unlock bootloader and do the usual stuff?
Click to expand...
Click to collapse
Yep that's what I do. Bare in mind that the MSM tool will relock your bootloader, so that will need to be unlocked, then either root on 4.4 or update and then root.
If you choose to root when on 4.4. Don't reboot after installing the firmware, open magisk first then install, then install after OTA.
That will retain root after the 4.4 to 10.10 update

dladz said:
Yep that's what I do. Bare in mind that the MSM tool will relock your bootloader, so that will need to be unlocked, then either root on 4.4 or update and then root.
If you choose to root when on 4.4. Don't reboot after installing the firmware, open magisk first then install, then install after OTA.
That will retain root after the 4.4 to 10.10 update
Click to expand...
Click to collapse
Hi again! Used payload dumber to exract EvoX 6 and all went so fast and easy. Now i have root again with latest EvoX . Didn`t have to go back with MSM
Thank you for your brilliant guides and beeing such helpfull person always!!

janitor9 said:
Hi again! Used payload dumber to exract EvoX 6 and all went so fast and easy. Now i have root again with latest EvoX . Didn`t have to go back with MSM
Thank you for your brilliant guides and beeing such helpfull person always!!
Click to expand...
Click to collapse
No worries man, I'm happy you got sorted...
Hope it all works as it should.