Hello guys, I just unlocked bootloader and try to flash twrp on my brand new OPT. The problem is that osx doesn't recognize the device (./adb devices find nothing).
So when I try to flash recovery it does it, but it doesn't work at the same time.
Any idea to solve this? Where I can find drivers for mac?
Thanks!
edit: I managed to let the device recognized, but even if I flash twrp, I have the stock recovery.
Related
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Added:
If you can't find a patched version, flash cwm or philz recovery with fastboot, adb is working on both of those. You just need a rrcovery image and do
"fastboot flash recovery <recovery-file>.img"
In fastboot mode.
let's try it out!
nvan7891 said:
There was a bug in a bunch of recent twrp releases that causes adb to not work in recovery. Patched versions have been made, try finding one for your device.
Click to expand...
Click to collapse
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
alkkade said:
I ****ed up my phone today I did full wipe (formatted internal storage too, so i can't flash any rom in recovery because there is nothing) and now i've been searching hours someone who can help me? In TWRP i can't mount anything to my pc (i do not know why?) AND adb says me "devices not found" or something like that so can't push any zip-file to my phone via adb sideload. Is there any way to reapir my phone? can someone help me? Thanks alot!
Click to expand...
Click to collapse
i dont know how to fix your problem but i know how u can change the devices not found
install on your computer pdanet driver.
p.s.
i ****ed up my phone as well today i publish a post i will be thankfull if look on my problem.thanks.
alkkade said:
So u mean i need to flash new recovery version? how i can do it when my adb isn't workin? thanks!
Click to expand...
Click to collapse
See the edit to my first response. Fastboot is done in fastboot mode, not recovery, so you should be good. You just need the basic .img file of cwm or philz recovery.
If you are on win 7 try this:
http://adbdriver.com/downloads/
(Adb driver installer)
Run it when you turn adb sideload on in G2 and connect it to PC.
If it fails you still can go buy somewhere USB OTG cable (few bucks) and flash ROM from usb stick like me.
It appears that accessing fastboot pn the lg g2 is not so simple. Sorta like samsung phone deal, where a manufacturer download is used instead. From what I gather, recovery might need to be wiped to access fastboot, which you could do from terminal in twrp, but thats risky. Apparently, a lot of people have gotten stuck in fastboot mode. Best bet would be to reflash stock firmware through lg download mode. Also see this thread for a method to return to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2432476
Once you are back to stock, just reroot and flash revovery, etc.
downloadmode should still work. go back to any kdz for your version
also source and versions post next time
hi everybody, i hope, that someone can help me,
i thought i should root my Z1 and it was not a problem via windows (via LINUX i couldnt even find the device via "adb devices")
it was not a problem. first i installed twrp, but everytime when i restarted the recoverymenu, twrp went away and the default recovery menu started. so i installed CMR and it was not a problem. so far everything okay. but than i thought i should install the current nighlies of cynagonMOD and the problems started
when i try CMR to installed the current nightlies, i get the error
""this package is for device:Z1 ; this device is jfltexx" nomatter if its the nightly from 13.11.2015 or 14.11.2015
under windows, when i start adb devices, the device will be found
adb devices
List of devices attached
529e86fb device
and when i try to start into fastboot, it is possible. but when i'm in fastboot-modus
i can do anything. nothing happens. whatever i try, i get the feedback "waiting for devices"
any idea? can someone tell me, whats the problem is?
@update: when im in CMR, windows shows my ZUK z1 as GT-I9505 (i guess its samsung right?) how can i deinstall CMR and install TWRP (cause via fastboot its not possible)
Do you use fastboot with the -i switch followed by the device ID?
at the first time yes. but now its not possible. im now really frustrated, cause now im in the boot animation loop and can do nothing. even not able to upload any zip files to restore the zuk cyagon OS . any idea how i can install now the normal version of the phone again? i can only enter CMR
Edit: I forgot to write that the device is an MX4 normal 32gb(not pro)
So my situation is like this :
In accordance with this guide:
http://forum.xda-developers.com/meizu-mx/general/news-cm12-1-normal-mx4-t3210491
I installed Flyme OS 4.2.8.2A installed the custom recovery and succesfuly flashed CM 12.1.
But than I had a problem with my messages app that couldn't be fixed simply
so I decided to reflash Stock and than CM 12.1.
After doing so the phone is now bricked and the situation is such:
*its stuck in an infinite bootloop
*Recovery doesn't work
*Fastboot does work and recognizes my device when I type in "fastboot devices"
*ADB does not recognize my device
*When plugging in the device turned off it just charges and doesn't pop up
Only when I plug it in fastboot it recognizes it as an ADB HTC Dream device.
Things I've tried:
I tried to erase previous recovery and flash a new recovery
but I keep getting security error 0x2017
so I figure my bootloader is locked.
I tried unlocking using commands I found on the internet but they all seem to be wrong.
I get "remote: unknown command" for all the following commands:
*"fastboot flashing unlock_critical",
*"fastboot flashing get_unlock_ability"
*and "fastboot oem unlock don't work".
I've also tried this guide : http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039
but the program doesn't even seem to recognize my device after I push "start" it doesn't do anything.
I despratley need your guys help and I'm even willing to pay a nice sum on paypal to anyone
that has any ideas on how to solve this.
I'm specificaly looking for some way to unlock bootloader or get my device properly recognized so I can reflash a rom..
Thanks in advance for any of your help.
Anybody? Willing to pay..
If anybody has any solution I'm willing to pay on Paypal.
Any advice will be of help..
Thanks.
From what I've gathered all Meizu devices have a locked/stripped fastboot. But have you tried through SP Flash Tool? worth a shot.
Try using CM instead of ubuntu in this thread:
http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-how-to-flash-ubuntu-touch-t3210039
If you can connect your phone with those drivers and have a PID=2000(preloader), you should be able to write to anything, or you'll have PID=0003 and can't write a thing.
Not much but maybe? I'm waiting for a new motherboard to get mine up and running
The thing is I tried installing the drivers
but it doesn't seem to do anything with the drivers at all
unless its in fastboot.
How did you order a motherboard?
I'm starting to think maybe I should send it to Meizu to fix since i'm still under warranty
and make up a story about flashing stock..
Reflashed with uboot patched??????
Hiya. I managed to unlock bootloader/install twrp and root and went to see if i can put it back to stock.
When i try and sideload the stock firmware, my pc wont recognize adb while it's in sideload mode but it does in normal state.
I also get these errors (see pics)
I have tried installing all the drivers/changed usb ports but now i have no clue what it can be.
Any help please?
Thanks
PS. Using Windows 10
I'm having the exact same issue and I'm also really interested in a solution for this. Also tried uninstalling and reinstalling the drivers and switched USB Ports. The device gets detected without any problems in fastboot mode but as soon as I switch to Sideload Mode in stock recovery, Win 10 shows me this error and doesn't detect my device for sideloading.
Temporarily I could flash TWRP and sideload the zip via TWRP and cmd but I would also like to be able doing it without TWRP again.
Thanks in advance.
Can't anybody help us?
Just download the latest Android Studio software it contains the last ADB driver, i had the same issues after installing reboot, and ADB sideload will work !
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
I accidently formated everything in twrp and ended without OS and was stuck in custom twrp. I tried to flash stock recovery and that went ok. Now whatever i do i cant sideload stock zip file using adb. Fastboot is recognized but adb is not. When connected to pc shows error. I have tried to install, reinstall all sorts of drivers but all the same. Is there a way to get back to stock using fastboot commands manualy? Please help !!
Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.
himanshuladia said:
Use fastboot to flash twrp again and then flash the stock rom. You can transfer the stock rom to the device by connecting it to your PC while being in TWRP.
Click to expand...
Click to collapse
You mean stock twrp or custom because i have stock but when connected i cant copy files on device because it is not recognized by PC
Del.
TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.
himanshuladia said:
TWRP is always a custom recovery. What you currently have is the stock oxygen OS recovery. Flash TWRP again and boot into twrp. Then, while being in TWRP, conmect your phone to PC.
Click to expand...
Click to collapse
Ok will try !
Del.
Finaly i did it after a few hours of trying to find a solution and figuring out why my PC doesn't recognize phone in adb I tried on an old PC with win7 installed and sideload went smooth like butter on first attempt. I have tried on two computers with win10 installed, tried with all sorts of USB cables, usb on computer 3.0 , 2.0, tried all sorts of drivers and nothing helped. I hope that someone else will have a benefit of this post and sort of a solution if he will have the same issue. Thanks to everyone that tried to help out!