Asus zenfone 2 ZE551ML
so i'm currently stuck with no os on my device ( internal storage totally empty )
all tho i have twrp recovery 3.0.0-0 Installed but twrp is not reading/showing sd card and neither it is accepting pen drive by otg cable !!
i tried adb sideload but adb is not recognizing my device, so i tried to update the drivers manually by going in device manager but i can't find my device even there ( no portable or other device showing up when connecting the usb )
so i'm totally stuck with twrp now please help
thankyou !!
Related
I carelessly wiped the system in TWRP, now i have a big problem -"no OS ".Unfortunately,it can't mount USB driver by OTG and device can't be detected what ever in Recovery or bootloader mode . so I can't flash a new rom into it.What can I do now ?I have switched many PC with different OS ,windosw xp ,7 ,8 ,but none of them can recognize my device which make me can't install driver for it.What can I do now ?
lonelystar21 said:
I carelessly wiped the system in TWRP, now i have a big problem -"no OS ".Unfortunately,it can't mount USB driver by OTG and device can't be detected what ever in Recovery or bootloader mode . so I can't flash a new rom into it.What can I do now ?I have switched many PC with different OS ,windosw xp ,7 ,8 ,but none of them can recognize my device which make me can't install driver for it.What can I do now ?
Click to expand...
Click to collapse
Just flash the factory image and start from scratch.
http://forum.xda-developers.com/showthread.php?p=45671279#post45671279
You can also get drivers that will work with TWRP here:
http://forum.xda-developers.com/showthread.php?t=2391236
lonelystar21 said:
I carelessly wiped the system in TWRP, now i have a big problem -"no OS ".Unfortunately,it can't mount USB driver by OTG and device can't be detected what ever in Recovery or bootloader mode . so I can't flash a new rom into it.What can I do now ?I have switched many PC with different OS ,windosw xp ,7 ,8 ,but none of them can recognize my device which make me can't install driver for it.What can I do now ?
Click to expand...
Click to collapse
This is the driver you need in order to use ADB while in recovery in addition to the Google Driver or else you would see "Flo" under Unknown Devices in your computer device manager. Or you can restore the stock 4.3 ROM via fastboot.
the problem is it won't come out as "flo" or unknown devices when i connect to PC , it just nothing happen , that's the problem :crying::crying:
Hi Guys,
Please help me, i have installed adb, usb drivers also tried with vcom drivers but sp tool not detecting my phone.
when i connect phone switch on and usb debugging on device manager shows it (ADB and device in portable both) but switch off phone does not come in device manager (in my magnus /A1117 mtk preloader device used to come but nothing for this device).
Tried on both win7 and win8.
Not rooted or unlocked bootloader yet, want to get working sptool first before going for root.
Thanks in advance.
did you find solution for this my device on pc mtk preloader also not detecting ... but fastboot works ?? how to get back to total stock
------------
the problem is solved i just don't know how to delete this thread
-----------
in fact the device is still not yet recognized under twrp but does work under bootloader mode, it's just it's not adb connection but fastboot connection that i got confused
for anyone who have a similar problem, you might find it helpful in the following links that i tried before i realized my stupidness...
http://sciologness.com/download/903...-configuration-descriptor-request-failed.html
http://adbdriver.com/downloads/
http://developer.samsung.com/technical-doc/view.do?v=T000000117 // this is the samsung page, but after installation you might find in your usb driver compatibility list something like "samsung adb interface" and that might do the trick
--------------original post-----------------
hey guys,
i just followed this page to root my device
http://forum.xda-developers.com/pixel-c/general/guide-unlock-bootloader-install-custom-t3307183
everything went fine until i flashed the xceed kernel.img for my stock rom...
and when booted into twrp and connect to pc meanwhile, the tablet it's not recognzied via usb anymore, and it says 'unknown usb device' error code 43. the tablet can either be rebooted into the system or recognized under the bootloader mode
i tried to install the google usb driver manually but it says
'This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)'
anyone please help
i don't think it's the problem of my cable or the connecting ports...
my os is win10 64
thanks all
G
Greetings every one ..
I have a half dead Oneplus 3 Unlocked + Rooted
here is my problem
there is no OS in it and i flash TWRP many times via ADB and wont boot to it
and i tried to flash the stock recovery V2.0 and done successfully
the sideload mode Recognize my OP3 but when i try to flash the Oxygen Rom it Gives me cannot read
also i tried the Unbrick Tool when the device is connect it showing me Qualcomm hs-usb qdloader 9008
but when i power up the tool as administrator it showing me (no device)
see here : https://www.youtube.com/watch?v=BIbagVAXJJk
Thanks .
on the unbrick guide try method 2 but completley power off the device and count to 10 when holding the vol up button THEN plug the device in. i had that issue also. if you get errors or for some reason it dosnt show up again try on a diffrent pc it will work
Try method 2. BTW "cannot read" error has to do with faulty ADB drivers, get the platform ones
I did instal the right ADB drivers in fact
still no luck
The ones from platform tools? Since that "cannot read" error has nothing to do with your device. Have you tried renaming it? Rebooting your PC? Last one did wonders for me for some stupid reason.
Hi,
I also had this message of "can not read" in sideload mode, this problem often happens with Windows 10, so I used Windows 7 on another pc and it was OK.
I tried Windows 10 & 8.1 & 7 & XP
still The same problem
What if you flash Twrp and boot into it? Then u can adb push the filemm
I tried via fastboot and its done right
but when i reboot into the new TWRP recovery its stuck in the boot oneplus as same like the Video shown up
book an appointment with oneplus live chat so a service tec can fix it and if they ask if it was rooted say no
Hi,
If you access TWRP, install the Official Oneplus Recovery 4.0.2
In TWRP click "intaller" then choose "install image" and select the file you will have to copy to the phone in recovery mode.
Then restart in recovery mode, choose english, then "adb sideload mode"
From there you should be able to flash your phone with an official Nougat zip.
Do the under windows 7.
It is necessary to install the Oneplus USB drivers and ADB tool on your PC before any manipulation.
Finally I solved the problem
like i said B4 my phone wont boot into TWRP by any chance
i traid all the Officials TWRP one and they stuck on the boot image or power the phone off
i flashed a modified twrp (blu_spark 3.0.3-x) thanks for this beautiful smart man eng.stk if im not wrong
and thank you all for the help
i had similar issue...with several phones.. download Malwarebytes trial version and run it...i had a few stealth root tool kit viruses.causing my system to have a hiccup....
Hello ,
I am realative newbie at upgrading roms ,even though I've been doing it for few years.
I got the latest twrp onto my device ,but somehow couldn't get a rom from recovery onto the device and whatever I did
Now my device is not showing on ADB ,as far as I can see I don't even have a bootloader on it anymore.
I've managed to open it up and get EDL working and the device is showing up on COM9 . Mi flash only lists the device under com and not under recovery.
Is there anything I can do to salvage ,
Thanks in advance.
Hello,
you can try to use an USB-OTG adapter to flash an image from a USB pen drive. Of course you SHOULD try to avoid use MIflash and use a adb and fastboot tools from a Linux computer. Test if it works properly or not the detection of the device. If not... maybe you burnt the usb chargingboard like happened to me( a tip to recognize this: it won't fast charge) , so the fix will be to replace the board.