Good day people of the internet and this forum..
I'm not sure if this is the good place to ask for help, you can move this topic if you consider it put in the wrong section but don't delete it please, however any help would be appreaciated... So there's the problem:
I got a ZTE Blade L110 to repair or mostly, wishing to flash a custom recovery (TWRP to be clear) to it and from what I heard not only it will straight work by "Unlocking the OEM" from the Developer Options, but I also heard I must unlock it via restarting it into "Fastboot Mode" by ADB or via booting it from the "Recovery Mode" if not the ADB option. Althought whenever it is on the Fastboot mode, and I also connected the phone to the computer, it gets connected as I installed the drivers myself. The "fastboot devices" command in the cmd it also recorgnizes it but whenever I want to type in "fastboot oem unlock" in the cmd prompt screen it just shows out "..." in which in that step it should show anything in the phone's screen like a screen confirmation but nothing, it remains the same screen statistically as from booting into bootloader along with the white ZTE splash screen and showing in the left top corner "fastboot mode" along in a black sqaure background for the text... And the only way to stop it is by unplugging the phone and plugging it in again the USB cable and throwing me an error of "FAILED: Too many links" or something like that but didn't anything to the phone thought.. However some commands such as "fastboot reboot" works and so on but not the ones which needs prompt confirmation / authorization from the phone as it doesn't pop up anything as said above.
I'm also going to share out some screens so you might not get confused that easily from what I said above:
{
"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"
}
As if you can see, it is EXACTLY at the same time process, so basically as I mentioned many times above it doesn't show anything on the screen on the phone apart from that same screen before doing anything to it.
And also if my driver showoff is required, you're welcome
I also tried to uninstall the driver too but it won't work and it will show out "fastboot_Gadget" as device name with an error in it as no drivers were found for it..
I also tried different set of drivers, even non-signed and signed ones but didn't changed anything
Weirdly I also tried different ADB / Fastboot tools but the ones from the SDK source didn't even bothered to show out "..." whenever I executed the "fastboot oem unlock" or "fastboot unlock(ing) flash" command it simply just didn't showed anything after and it simply threw the same error of "too many links" one after some time not even touching or doing anything.
So on the screen above I'm using the "15 seconds ADB / Fastboot" one with all options marked as yes including the driver installation ones as the other ones won't work or sort of...
I'm not sure if it is from my drivers or the phone itself or the firmware from it, as it is its stock one. Thus I also ran the cmd even as administrator and not before, both ways but didn't changed ****.
And also lastly I found out a silimar case to the one I got from another forum and another user by searching in google:
https: //android.stackexchange.com/questions/187159/what-is-csc-fastboot-mode-and-how-to-get-rid-of-it
(you'll have to remove the space in between the "https:" and the "//" in order to get the link as I cannot post it straight due to account limitations)
Thanks for reading and I hope someone can come up with a solution or anything as soon as possible.
Seriously, no one?
I'm going to be honest, am I wasting my time there for nothing or nobody knows regarding that? No I don't mean to say it from hate but I neither want this to get a reply per month to be serious. This is a serious case to me and also it could help the others people who faces such issues.
ho lo stesso problema
---------- Post added at 12:49 AM ---------- Previous post was at 12:46 AM ----------
potete aiutarmi per favore
Related
So i was searching around and couldnt find actual answers on how to get rid of that annoying ass sticky bit factory fastboot menu when phone powers up. So i decided to take matter in my own hands and learn a little bit about adb and fastboot commands etc.. Typed in some commands in a certain order and BOOM sticky bit no longer gets in the f-ing way ^^ this should work on any android powered phone seeing how it doesnt go to any specific phone. So far i learned that it works on the xpirea (how ever you spell it) and the droid razr m consumer and dev edition. so here we go.
MAKE SURE YOU HAVE USB DEBUGGING ENABLED
Files to download:
Android.zip: http://www.mediafire...0imf9xv2uicwkbh
Latest usb drivers: http://www.motorola....motodev_lp.html
STEPS
1. Power up your phone completely.
2. extract the folder in the android.zip file to your local disk. just drag the folder to local C: or whatever your main HD is
3. hold left shift and right click on the folder and click on pen command window here"
4. plug in your phone if you havnt done so already
5. in the command window type: adb devices ( this makes sure your phone is connected and it'll show its serial number under List of devices attached.
6. once it shows the serial number type in these commands ( these are in order)
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase userdata
fastboot erase cache
fastboot reboot
and walla phone will reboot like when you first got it ^^
{
"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"
}
Your links are broken.
This seems cool. But I don't know what menu you are talking about, perhaps more clarity, as I'd like to know what causes this menu to be shown and if I am just missing it somehow. Curious to know if this fix may aid me in the future. As probably are some other users.
Also probably helpful for you to note that fastbooylt erase userdata will clear user settings.
Sent from my XT907 using xda app-developers app
Thank you...
Your steps got me out of the sticky mess...
Hello
Sorry if this was a very noob topic
I done lots of flashing new ROM or back in stock process but i almost gave up this time
My phone status are
No OS
TWRP installed
Can boot to recovery
PC can't recognize the phone
Typing ADB devices shows empty list
Typing Fastboot devices also shows empty lines
30% battery left
I recently try to install the Lollipop version for my phone but it turns out that the zip are behaving like OTA (yep the title of the zips are OTA)
What i mean is it returned my recovery to stock
Without thinking much further i did 'fastboot flash recovery TWRP2810.img' thing (Yes i rename recovery image that way so it will be more convenience for me) and wipe all partition in the phone through the TWRP without problems
One thing i forgot is to "refresh" all ADB and Fastboot driver for my phone on the PC
Now my phone states are "No OS" and "PC doesn't recognize my phone" wether in ADB (obvious cause i can't boot with no OS so no USB debugging for me) and Fastboot (Enter Bootloader is OK, enter TWRP is OK too)
I already try the WUG step for installing the needed driver but no success since my PC can't recognize my phone
Try on 4 PC at my office and all of them are ignoring my phone
What should i do now, please, any help will be appreciated since its already the time i ussualy already at home
Thank You Very VERY MUCH for any help I can get.
unsungkhan said:
Okay, here's what you do.
Download the ADB drivers first, from here [URL="link"]http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
unsungkhan said:
Extract the zip.
Once you're done extracting, boot your phone into bootloader mode, plug in USB, should show up as an unrecognized device.
Device manager from control panel, select device, properties, driver, update device driver, browse my computer, let me pick, all devices, have disk, navigate to where you extracted zip, select inf file, adb interface.
Should work.
Click to expand...
Click to collapse
[/URL]
Thank you Sir
I managed to fresh install my XP and continue with your instructions
I don't know why but it gave me this
{
"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"
}
I already try other driver but still a no go?
Do you happen to know other way around for tricking this Sir?
Please lock this unuseful thread
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
unsungkhan said:
Before locking the thread, can you repeat all the steps and try with ADB Composite Device instead of ADB Interface?
Also, did you try changing USB ports, sometimes these things get a little troublesome because of faulty USB ports.
Last but not the least, you could also try a change of cables.
Click to expand...
Click to collapse
#late_post
i've been able to resurrect my phone finally
after those steps i found Universal Naked Driver and it works
Thank You very MUCH Sir :laugh:
Hello.
I've repaired a nexus 4 screen and digitizer but I got it back because my friend can't recover access from a forgotten pattern lock.
He is running stock android 5 lollipop and he doesn't get the email recovery option when he inputs wrong pattern. I've searched even in google support but I didn't find a solution to recover his photos.
My main concern is to recover files and photos!!! There isn't a reason to suggest a factory reset....
--Phone Status---
Boot loader seems unlocked "Locked state is marked as unlocked in bootloder in red letters" while secure boot is enabled in green letters
USB debugging seems OFF: There is no android device listed in device manager. I only get a music player in disk drives which is empty.
adb devices command in bootloader recognises it
When entering to recovery I get the message "no command" along with the icon of an android under repair.
No dropbox no google+ photos backup
---What I've tried---
UPDATE: Managed to flash TWRP 2.7.1.0 I can see the files but since usb flash drive doesn't work I can't copy the files...
Android Device manager: Returns error that the phone is already locked and there is no need to apply new password.
Tried about 30 wrong patterns and it didn't came up the google mail recovery option.
Tried during a phone call to see the files but I only managed to turn on WiFi.
{
"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"
}
When you say the USB flash drive doesn't work, do you mean the USB port in the phone?
MTP doesn't always work in TWRP, meaning it won't show up as a normal usb drive on a pc. ADB will still work though, you have to set up ADB on your computer, boot into twrp on the phone and use 'adb pull' to copy the files to the computer. On windows you will need to download adb and the drivers, I use http://www.koushikdutta.com/post/universal-adb-driver
I'm trying to install the drivers for adb but I cannot find the right one.
Edit: Also it cannot be detected from boot loader now. I'll try in a pc that already has been connected and worked.
I have adb and fastboot installed already and worked with this and my own phones.
Edit: It seems to be a lost cause the phone fell down many times. Don't bother maybe I'll solder a usb port first... if it is possible with my less than basic equipment.
There are many methods on the following page,
http://forum.xda-developers.com/showthread.php?t=2620456
The way I did it was an alternative version of method 5 while in twrp.
Method 5 - alternatively, Mount system in twrp and delete the file /data/system/gesture.key
If it asks for a pattern on boot just try any random pattern it should let you in. I did this when a version before lollipop was installed but there is no reason it shouldn't work on lollipop as the same file is saved in the same location, just checked.
Using adb
adb shell rm /data/system/gesture.key
Click to expand...
Click to collapse
I've run into a rather odd issue with fastboot. It seems that any command entered comes back with the following:
ERROR: Couldn't create a device interface iterator: (e00002bd)
There is no issue with adb, and I have tried re-installing both platform-tools and the entire SDK, but no luck. I don't run into this problem in Windows either, so I'm wondering just what is going on. If anyone has any thoughts, I'd appreciate the help!
Edit: On further analysis, it looks like it has something to do with OSX. I've disable SIP and gatekeeper, and the issue still persists, so it looks like I'll just have to use windows for fastboot! A minor gripe.
Have the same issue on El Capitan. It's probably related to the recent OS updates.
I have this problem too. Strangely enough, my wife also has a mac running El Capitan and Fastboot is working without problems. I even copied the binary across from her machine to check that, but it's still throwing out that error.
So it's something about our computers. Any ideas?
having the same issue on El Capitan as well. sub'd for an update on how to resolve this.
managed to unlock using the skipsoft tool
Same issue here (El Capitan, Nexus 5).
Weird how so many people seem to have this problem, but not everybody. Why not? What varies between our computers? OP mentioned SIP, I know I had to screw around with this to enable TotalFinder's features to work with El Cap.
But a quick search shows that it is in fact not totally disabled on this computer. I'm going to give that a shot and report back!
EDIT: Nope, like OP, disabling SIP and Gatekeeper has made no difference.
EDIT 2: Also, ADB works just fine. These are both the binaries from the latest SDK
I am having this same issue, have been searching around for some fixes, thinking I might have messed up my bash or something, but after resetting it the iterator error just keeps spitting back at me
{
"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"
}
I just upgraded my OS X El Capitan to the latest 10.11.2 beta (15C31f) and fastboot works again.
Interesting. So you think it's connected, then?
i can't confirm yet, but Fastboot might be fixed with this latest update on OSX 10.11.2 beta (15C31f)
i do not have my 6P on me, but when i do fastboot devices, i no longer get an error (nothing connected though)
steveo17 said:
i can't confirm yet, but Fastboot might be fixed with this latest update on OSX 10.11.2 beta (15C31f)
i do not have my 6P on me, but when i do fastboot devices, i no longer get an error (nothing connected though)
Click to expand...
Click to collapse
Confirming that after the OSX upgrade, error message no longer appears.
Yep. error message resolved. El Capitan appears to have been having the trouble.
thanks for the update guys
So you've got to use the beta version of os x to fix this? Any idea what they changed that could have affected fastboot?
years later and this problem is back with macOS 10.14.4...
"Couldn't create a device interface iterator"
getting the same, any solution ?
Same issue on macOS 10.14.4
Yeah looks like something has changed with 10.14.4. Having the same too
Try giving the "fastboot devices" command while mobile in in boot loader mode.
If it finds your device then you can go ahead with "fastboot oem unlock"
Yeah fastboot anything doesn't currently work. Someone changed something in the Matrix (the OSX one).
I ended up booting up my linux box and was able to do what I needed to.
Hello everybody.
I wanted to unlock an BTV-DL09 [ Android 7 EMUI 5.04 EU ], but I'm stuck like the_wing was.
Modem no found !
Phew, got it unlocked! Moments of terror when entering the commands on the cmd...
A few mentions where I got stuck that may help someone else:
Regarding point 3:
In case your model has LTE (i.e. BTV-DL09), you actually should have a dialer application that you have to use instead of the calculator app, which didn't work for me. This is also mentioned in the DC unlocker app. In case you do it with the dialer, you have to enter following code: *#*#2846579#*#*
Regarding point 4:
Inside the "DC unlocker" app, I also got the "device not found" error, and I was wondering why. Two things I noticed:
- To enable USB debugging, it was not sufficient for me to activate the switch in the developer options, as the default USB mode for me is "charging only". I had to change it to i.e. "Device File Manager (MTP)" by tapping on the notification and then re-activate USB debugging in the developer options (which turned off after switching to MTP mode) to get USB debugging working.
- After enabling "manufacturer mode", the mode was turned off as soon as I quit the menu. So I had to stay in the menu to make sure manufacturer mode is on.
- You can check your device manager in Windows to see if the current mode is active: When doing USB debugging, the device "Android Composite ADB Interface" should show up under "Android Phone" list, whereas when you turn on manufacturer mode, some COM ports should show up under "Ports (COM and LPT)"; the one DC unlocker is searching should be named "Android Adapter PCUI". If you got some devices with not properly installed drivers you should consider installing HiSuite software on Windows first.
Regarding point 8
- When I bought the credits for DC unlocker for PayPal, I had to click on a link arrived to the PayPal e-mail for confirming your account. I then still got the "Server login error", but closing and reopening DC unlocker eventually fixed it.
Hope this helps! Happy unlocking to everybody!
Click to expand...
Click to collapse
I have installed Hisuite and Huawei data card driver.
Impossible to activate Device File Manager (MTP) and manufacturer mode, one deactivates the other, I do not know if this is the problem, but according to the tutorials it is a must.
I have a hard time understanding where the problem comes from, I even tested different USB cable, Win 7 and Win 10, I really did everything, but I'm dried.
{
"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"
}
I finally managed to unlock the bootloader, DC unlocker did not show me information from the tablet, but despite this, I could go to the next step and proceed with the unlocking, it is because of a msie security update according to Valdemaras on cd-unlocker forum, thanks to him.