Unable to restore phone. When you run msm, the list of ports is empty. I've tried reinstalling drivers, running another msm and nothing helps.
I even tried installing on a new Windows. Are there any other recovery options? I have now installed the zephyrus project, but I want to install nameles. Is there a way to install nameles on top of the zephyrus project?
Pengccc said:
click enum
Click to expand...
Click to collapse
did not help
Related
Ok, so there are all these Android guides out there intended for 'native' android devices, that tell you to 'boot to recovery' to install something.
Up until now with SD/RAM builds we couldn't do that, so we had to improvise (preboot dirs, ADB, whatever).
Now that we have NAND, will it be possible to follow those guides to the letter? Do we have a 'recovery mode'? Can we use ROM Manager etc?
See http://forum.xda-developers.com/showthread.php?t=898913
taizh21038 said:
See http://forum.xda-developers.com/showthread.php?t=898913
Click to expand...
Click to collapse
Just did, thanks.
Now I'm just waiting for Rom Manager support
So, first off, I went to flash the new CM 10. 1 nightly, but in order to do so, I had to wipe dalvik and cache (as you all know). However, somehow the wipe also wiped out my internal storage, and made it impossible to flash the new rom. It also wiped my old rom, so now I'm left with just the recovery (i'm using TWRP v2.2.0) and no OS. I've tried plugging it into my computer and moving the rom back onto the root folder so I can flash it again, but the computer (win 7) won't recognize it as a device. It's just in the "unspecified" section titled GT-P7510. I've tried mounting through TWRP and everything, to know avail. Help! How can I move a rom back onto the root folder to save myself, when the computer won't even recognize it as an actual drive?! AH!
Installed proper drivers of tab.
It will Connect properly.
Then you move any ROM to root amd install via recovery.
TheBlackWolf said:
Installed proper drivers of tab.
It will Connect properly.
Then you move any ROM to root amd install via recovery.
Click to expand...
Click to collapse
I tried, didn't work. Unless I have the wrong drivers. (highly doubt it)
jercubsfan said:
I tried, didn't work. Unless I have the wrong drivers. (highly doubt it)
Click to expand...
Click to collapse
If nothing woks, I would think flashing via Odin is the last resort.
Btw I had problem with installing the right drivers before. Instead of trying to look for the specific drivers I have simple installed Kies which ensures the drivers are installed.
sarbashrestha said:
If nothing woks, I would think flashing via Odin is the last resort.
Btw I had problem with installing the right drivers before. Instead of trying to look for the specific drivers I have simple installed Kies which ensures the drivers are installed.
Click to expand...
Click to collapse
I never thought of that!!!! Thank you so much! I'll try it once I get home. Is there a specific version of Odin I need? I know it's Odin3; but what version? Thanks again!
jercubsfan said:
I never thought of that!!!! Thank you so much! I'll try it once I get home. Is there a specific version of Odin I need? I know it's Odin3; but what version? Thanks again!
Click to expand...
Click to collapse
Yes you will need specific versions and specific files.
Search sticky threads.
They help always.
So...last night Loki was trying to help me. My Omate wasn't allowing me to flash anything. After Loki's suggestions didn't work, I thought taking my Omate back to stock would hopefully fix the device and allow me to flash something. However, after following Loki's reset to stock guide, now not only will my Omate not turn on, but my computer will not recognize the device nor will Flash Tool.
So, what should I do? What could I have done wrong?
kp12584 said:
So...last night Loki was trying to help me. My Omate wasn't allowing me to flash anything. After Loki's suggestions didn't work, I thought taking my Omate back to stock would hopefully fix the device and allow me to flash something. However, after following Loki's reset to stock guide, now not only will my Omate not turn on, but my computer will not recognize the device nor will Flash Tool.
So, what should I do? What could I have done wrong?
Click to expand...
Click to collapse
Win7 or 8
Sent from my HTC One using Tapatalk
mghtymse007 said:
Win7 or 8
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Update: I removed the battery and now it turns on. However, I still am unable to flash stock (or any other ROM) still.
Win 7
My win7 system requires a reinstall of the flash drivers after a few flashes. Remove the current driver, restart and do a reinstall of the driver. Or do it manually.
Sent from my HTC One using Tapatalk
mghtymse007 said:
My win7 system requires a reinstall of the flash drivers after a few flashes. Remove the current driver, restart and do a reinstall of the driver. Or do it manually.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've been knee deep in drivers all day - which drivers are you referring to? The MTK ones (for stock flashing)? Koush?
Sweet baby Cheesus, it just worked.
I don't know why...
kp12584 said:
Sweet baby Cheesus, it just worked.
I don't know why...
Click to expand...
Click to collapse
Good for you. I meant the MTK 65XX VCOM drivers.
Win7 and these drivers, along with the configuration can cause the flash tool and drivers to be touchy at times. Sometimes a restart and reinstall is all is takes.
Sent from my HTC One using Tapatalk
My phone has an older version of TWRP and I want to update it so that I can update to Viper Sense 6.0 and I can not do so. I believe I need to reinstall adb and fastboot drivers, how would I go about that (where can I find the correct drivers)? I am on Windows 8.1.
dkris2020 said:
My phone has an older version of TWRP and I want to update it so that I can update to Viper Sense 6.0 and I can not do so. I believe I need to reinstall adb and fastboot drivers, how would I go about that (where can I find the correct drivers)? I am on Windows 8.1.
Click to expand...
Click to collapse
try this thread, worked for me
http://forum.xda-developers.com/showthread.php?t=2757414
mopartonyg said:
try this thread, worked for me
http://forum.xda-developers.com/showthread.php?t=2757414
Click to expand...
Click to collapse
This works for me until I go into fastboot, still doesn't recognize my device. Will the Win. 8 drivers for the USB 3.0 thing work since I have 8.1?
dkris2020 said:
This works for me until I go into fastboot, still doesn't recognize my device. Will the Win. 8 drivers for the USB 3.0 thing work since I have 8.1?
Click to expand...
Click to collapse
I have 8.1 also with usb 2.0, did yiu try the section for usb 3.0 in the thread?
dkris2020 said:
My phone has an older version of TWRP and I want to update it so that I can update to Viper Sense 6.0 and I can not do so. I believe I need to reinstall adb and fastboot drivers, how would I go about that (where can I find the correct drivers)? I am on Windows 8.1.
Click to expand...
Click to collapse
Download the newest twrp image to your phone. Then go to the market and download flashify. It's a free app and it will flash the image for you from your phone. Worked perfect for me on my DNA. It's one way to just avoid using a computer to flash an image. Try that and report back.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
dkris2020 said:
This works for me until I go into fastboot, still doesn't recognize my device. Will the Win. 8 drivers for the USB 3.0 thing work since I have 8.1?
Click to expand...
Click to collapse
Try installing PDAnet, it's installed some blanket drivers that have helped me out of recognition issues in the past!
Hi, I managed my Pixel 6 to unlocked but I can't root it with Magisk, I've tried many times to patched the boot image but I'm not sure if I got the right one. My build number is SD1A.210817.036
Can anyone guide me through this?
Thank you.
Here is a guide:
[CLOSED] Firmware is out! Get your root on!
Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image. Any update method can be...
forum.xda-developers.com
trai_th said:
Hi, I managed my Pixel 6 to unlocked but I can't root it with Magisk, I've tried many times to patched the boot image but I'm not sure if I got the right one. My build number is SD1A.210817.036
Can anyone guide me through this?
Thank you.
Click to expand...
Click to collapse
Did you already disable Verified Boot?
V0latyle said:
Did you already disable Verified Boot?
Click to expand...
Click to collapse
i followed this mostly 80% and i tried myself 20%. the way i did the patched file, i used another mobile to patched it and then copy to p6 folder then patched.
Root Google Pixel 6/Pro via Magisk Patched Boot [Android 13]
In this comprehensive tutorial, we will show you detailed steps to root your Pixel 6 device by flashing the Magisk patched boot.img.
www.droidwin.com
trai_th said:
i followed this mostly 80% and i tried myself 20%. the way i did the patched file, i used another mobile to patched it and then copy to p6 folder then patched.
Root Google Pixel 6/Pro via Magisk Patched Boot [Android 13]
In this comprehensive tutorial, we will show you detailed steps to root your Pixel 6 device by flashing the Magisk patched boot.img.
www.droidwin.com
Click to expand...
Click to collapse
I would recommend against that - always use the same device you're going to use the boot image on.
Please refer to my guide here.
V0latyle said:
I would recommend against that - always use the same device you're going to use the boot image on.
Please refer to my guide here.
Click to expand...
Click to collapse
I've tried to do that many times but it won't work for me...
trai_th said:
I've tried to do that many times but it won't work for me...
Click to expand...
Click to collapse
What exactly are you having problems with?
You said you followed 80% of the instructions; what did you NOT do?
V0latyle said:
What exactly are you having problems with?
You said you followed 80% of the instructions; what did you NOT do?
Click to expand...
Click to collapse
my laptop doesn't recognize my mobile phone I don't know why, Maybe the W11 so i trued on W10 then it's connected. after that i followed the step in that website.
trai_th said:
my laptop doesn't recognize my mobile phone I don't know why, Maybe the W11 so i trued on W10 then it's connected. after that i followed the step in that website.
Click to expand...
Click to collapse
You need the Google adb driver.
vandyman said:
You need the Google adb driver.
Click to expand...
Click to collapse
I'm on root now
trai_th said:
my laptop doesn't recognize my mobile phone I don't know why, Maybe the W11 so i trued on W10 then it's connected. after that i followed the step in that website.
Click to expand...
Click to collapse
Install this driver (as @vandyman said) for W11.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Lughnasadh said:
Install this driver (as @vandyman said) for W11.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Click to expand...
Click to collapse
thanks i just got it rooted
trai_th said:
I'm on root now
Click to expand...
Click to collapse
Glad it worked out.
I went through the same issue with Windows 11 and the Pixel 6. The Google driver was needed.
On another note; I have been using Windows 11 DEV the last few months and having fun with my Pixel 5 A12-beta without the Google driver.
The only answer I can come up with.
Is the difference is in the Pixel 6s chip set.
vandyman said:
Glad it worked out.
I went through the same issue with Windows 11 and the Pixel 6. The Google driver was needed.
On another note; I have been using Windows 11 DEV the last few months and having fun with my Pixel 5 A12-beta without the Google driver.
The only answer I can come up with.
Is the difference is in the Pixel 6s chip set.
Click to expand...
Click to collapse
no idea, man.