I was in the process of taking my Nexus 7 back to stock yesterday it started giving errors from fastboot. My device is completely wiped clean. Can't boot into recovery since there isnt one, there is no system to boot into, etc. I tried to install 4.2.2 via the toolkit and manually from fastboot and I keep getting errors. The most recent one is no such device or address found. The only the only thing that I have been successful in doing this entire time is oem lock and unlock. I read somewhere else that someone had a similar issue and that fixed it. I have tried every different port on my laptop and every different cable I can find. I haven't used the OEM ASUS cable since i cant find it, but I think it is at work so that the last one I can think of.
Can anyone offer any help or solutions? I've had the worst luck int he last three days with my devices. I've never had a potential bricking issue since my G1 and now i can't seem to avoid them. Any help is greatly appreciated. I can provide screenshots of the errors if that would help as well.
EDIT
Turns out it wasn't a bad device or any of the million cables. It was a bad laptop. I was finally able to get the drivers to install on my win8 desktop and it all went as it should.
Related
Alright, Wow a lot has changed here since I got the Note 4!! I no longer use it since I got the A9 from HTC after this one went kaput. Heres the sitch'.....I am super frustrated since the issue I have is a lot like many others ive read all over the internet with just one difference...the USB is not being recognized so I can't use Odin....yes I have tried many different computers, cables etc....the thing was and is still new bout 6 months old before i messed it up so I cant believe that something would or could have easily fried the USB port already. Nothing I have done comes to mind where that could have occurred and could be bad luck getting bad port from the start but unlikely...SO....making it worse is I can boot to stock recovery and the weirdest thing happens when I try to pick any option other than wipe cache or factory reset....it comes up and says dm verity failed, whatever option i chose is disabled!! WTH??? I have been in this awhile so this isnt my first rodeo by far and I have yet to see this.
My question is....HOW can this be fixed...counting out replacing the USB port(that may not be the major cause), I am not sure JTAG will work....most other options all require some sort of PC to Mobile connection to be working and I can't ever get QPST through QXDM to see it( i may be doing it wrong or missing a step....possible since Ive found most instructions to be missing vital information, especially for some of us who may be more green), AND Ive tried creating bootable sd card to use in download mode. The latter option is also very hard to find complete information on process and files needed to properly do so pertaining to this specific variant. The stock recovery i think woukld be the best bet but HOW CAN I ENABLE the options in recovery that are now disable???
I apologize to anyone annoyed if I am asking a question that is often asked.....bear in mind I have another handset I am working on that is completely different that takes up way more time lol, I have searched for weeks on this issue and nothing substantial can be found thanks to to much incomplete information given out AND no one seems to know how to fixed the recovery issue or even had it. Any help will be totally appreciated.....Thanks
I have been going nuts as of late trying to figure what happened with my Moto G4+. It was working fine, could connect to my pc no problem, then all of a sudden out of the blue, nothing. It only connects as a charger. I've checked it with different USB cables, different ports, even 3 different computers. Still will only connect as a charger. I've even tried it in recovery mode, still not recognized by any computer. I have not restored the phone as of yet due to a ton of pictures and whatsapp chats that I need to save. I have installed Xender to start to move some stuff off the phone, but I'm not too sure that a factory restore would help this. I have read that it could be a USB issue with the phone, either the port or the chip it uses itself. While I know I can replace the port, the chip is beyond what I have equipment for. I have turned on developer mode, and its set the USB mode to MTP by default, I've tried changing it to PTP as well, but the phone will only charge and is never recognized by the pc. All software and drivers have been updated, uninstalled thoroughly, reinstalled multiple times to no avail.
Is there any chance that this IS some form of software thing? Or am i just going to have to use the Zender app to move things between my phone and pc from now on. Until I can possibly send it off to Lenovo since it IS under warranty.
Any help is appreciated.
Just got off the phone with Lenovo/Motorola, and they are giving me the option that I wasn't wanting to hear, do a complete factory reset on the phone after removing the account information from the phone. Gee, that's what I was trying to avoid. Looks like I'll have to figure a way to completely back up the phone via wireless and hope I can save all my data needed to restore it later.
Will be trying the factory reset, but I'm not feeling very good about this at the moment. Will update later when I can get this done. But in the meantime, please suggestions.
Thank you again.
Provide some more info about what ROM you're running, etc... The more info you can provide about your situation, the more likely you're gonna be helped.
What ROM:
Stock? If so, what version and security patch?
Custom ROM? If so, which one and build date..?
I also have the xt1644 and don't have any issues whatsoever connecting to my Laptop, granted I run Linux on my personal PC. I also have zero trouble connecting to the PC's at my work which all run Windoze.
You mentioned you've tried connecting to your PC thru Recovery, so I would have to assume you have TWRP installed, no? If so, which version and by whom?
I'm running full stock room, no mods, build NJPS25.93-14-4, security patch of March 1, 2017. As for the recovery mode, that was the stock recover/bootloader. To where it should be raw adp mode. Even in that mode it is never seen by the computers I've tried. I can't install the newest security update because it won't mount internal nor external memory. I'm at work at the moment and if you need any more information, please let me know.
Thank you
rainfellow said:
I'm running full stock room, no mods, build NJPS25.93-14-4, security patch of March 1, 2017. As for the recovery mode, that was the stock recover/bootloader. To where it should be raw adp mode. Even in that mode it is never seen by the computers I've tried. I can't install the newest security update because it won't mount internal nor external memory. I'm at work at the moment and if you need any more information, please let me know.
Thank you
Click to expand...
Click to collapse
Did the factory reset work? As I'm suffering from a similar problem
Have not done the reset yet, still finding the best way to back up everything, plus finding the time. Will be doing it sometime this weekend though
I just did the compete factory reset, and as i feared, it made no difference. So all my data is gone (saved what I could) and will have to figure a way to get a backup phone working while I have to send off the phone for repair. At least it's under warranty.
I have the same problem. I didn't do the factory reset (yet), but you confirmed my fear, the factory reset won't fix it. Too bad my phone isn't under warranty anymore.
Did you send it for repair?
What was the problem after all?
My XT1640 seems to be falling apart. Bluetooth stoped working out of the blue. Can't read SD card anymore and now USB connection isn't working.
My apologies for not doing a follow up post. I was able to send it back to Lenovo and the replaced the phone so it's back up and running fine. If it's out of warranty, then I'm not sure what avenue you can take aside from maybe finding one that's got severe screen damage but a good non blacklisted board and change it out. Aside from that, I can't tell you what they found wrong with it. I would assume the usb chip may have gone out, but without knowing the fate of my original phone, I can't say.
Hi all,
I'm just about at my wits end here. I have a Note 4 (N910W8) with a failed USB connection and I would really like to root it. The underlying goal is to remove/disable all samsung bloatware.
WRT the USB, I have tried adjusting developer options, *#0808#, updating drivers, changing cables, changing PC's, etc. I've tried everything I could find online. Recently, I took it to a local shop and learned that the problem is not with the USB port/board, but the motherboard itself. I'm not going to pay to replace it. I have googled far and wide. As far as I can tell, this phone will never again connect to a PC via USB. So, download mode and Odin are out.
I have tried TowelRoot, KingoRoot, and other apk's, but I am on Android 6.0.1 (MMB29M/GLW-N910W8VLS1DPK1) so all of these exploits have been patched.
I am able to boot into (stock) recovery mode, so I thought I'd try recovering via SD card, however that doesn't work either. First I get a loading screen of the mascot with a spinning wireframe polygon in his belly and the message "installing system update". Then after ~15 seconds, the mascot is on his back with a red warning symbol over his belly, and the text "No Command." is displayed. I'm not sure what that's all about, because I have the latest update installed.
Any attempts to install CF-Autoroot or another recovery firmware (ie https://samsung-firmware.org/model/SM-N910W8/region/GLW/ , or https://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538, etc) from SD (in recovery mode) have been met with the same error messages:
E:footer is wrong
E:signature verification failed
I'm not sure why because at least some of these recovery firmwares claim to be official builds. Granted, they are older versions (downgrades), but are signed nonetheless.
I have tried installing TWRP or CWM so I can disable signature verification, but AFAIK the device must already be rooted to install these (which seems like a bizarre catch-22, but maybe I'm confused) so that's a no-go.
It certainly feels like I have explored every possible avenue, but I have one remaining idea. Perhaps if the phone doesn't want to downgrade, I could force its hand by carefully soft-bricking the current rom in a controlled manner, then performing a recovery from SD with an official 4.4.4 KitKat build, and finally, using the towelroot/kingoroot/etc exploit to gain root access.
I mean, why else would there be a recover-from-SD option in the stock recovery menu? There must be a way to get it to accept a recovery build...
It's a last resort. But I'm willing to try it. The phone boots up, but is so bloated and laggy that it's practically unusable. Still. Am I missing anything? Surely there's some way to skip the USB / Odin method. What do you guys think? Is it time to go hulk on this thing? Is there any hope left? Curious to see how much further this rabbithole can go.
Cheers and thanks guys.
I've searched for ways to soft-brick, but have not come across anything. The bootloader appears to be locked, which is odd because I thought that only applied to Verizon variants.
I have recently downloaded an ADB/fastboot package for windows so I could attempt ADB over WiFi, however I can't establish a connection. I thought I'd do some more poking around on the phone side, so I installed some Wireless ADB apps. They all indicate a root is required, so I think that might be a dead end. I also connected to a ubuntu machine. Nothing. The phone charges, but both the PC and Ubuntu machine show zero signs of any connection at all.
There has to be some kind of SD-based solution to this. You can boot a computer from an SD card / USB stick and use that to access files (on an unencryped partition), and I'd be happy to do that here and delete those bloatware APK's directly... but I guess phones don't behave like other computers.
I've picked all the low hanging fruit. A part of me believes that there are some sneaky hacker ways to get at this without USB (ie some sort of rootkit) but that's way beyond my abilities. I'm going to take a break and attack this again once I have fresh ideas.
I'm in the same boat (busted usb port), does your phone still fast charge? Mine stopped fast charging.
I too have the same problem, except with the Note 10.1 2014. I know that is a different forum, but if you find a solution, it might be adaptable to my problem. I too have exhausted all other options as described above. Please someone, there must be a way to root via SD card instead of Odin. Help us please!
Me too. I have a Note Pro 12.1 running Lollipop. USB is busted and I've already replaced the port and ribbon, so it must be the motherboard. I mainly need it for Titanium backup, so I don't have to reinstall large games over my limited connection.
I have the same problem. Note 4 N910H. Not recognized by pc, stopped fast charging shows usb charging in battery settings. AFAIK I just re-rooted the phone before it went bust. There is no solution except changing the motherboard. Also this problem seems to be quite common.
Got a model A846L that wont boot past the alcatel logo, normally I would just toss the phone but it belongs to older friend of the family who lost her husband earlier this year. You can guess im here because we need the pictures from the phone, Yes....
Done tried clearing device cache and connecting via ADB, cant get either to work. Im not a total expert but I am very experienced in flashing ROMs and working with phones.
However this one has me at a lost, looking for advice or maybe something I havent tried or though about trying. Im running win10 but do work with Ubuntu with android software. So no tools are to far fetched.
Thanks.
Hi all
As the title says. I've run into problems trying to flash a new ROM.
I used TWRP to flash a custom ROM but didn't like it so wanted to go back to stock. I'm not sure/can't remember what happened (been up till 4am for 2 nights trying to fix it), but it's now stuck. I can get into DL mode (pale blue/turqoise screen) and have tried flashing various stock ROMS but am running into problems that may be driver related.
I don't/have nevwer has Kise installed. I have tried various Samsung USB drivers. Some seem to have been invisible, but the one I'm using now (can't remember version but it's a few vesions old) is visible in Windows 7 device manager as Samsung modem which says it's working (for what that's worth). When I plugged the device in, the taskbar popped up to say the driver was installing.
I've tried a few versions of Odin. They all say <added> in the dialogue box, and 0:[com4] is added to the little box above and changes colour. I'm assuming that means that Odin can see the device ok?
After browsing for the stock ROM BL, AP, and CSC files, they get checked for MD5 which all seems ok, and then when I start Odin, nothing much happens, a few lines of text - file analysis, setup connection, and if I'm lucky it gets to NAND write start... and then nothing. I left it in that state last night and 10 hours later nothing had happened.
I'm hoping that this is something simple but I've exhausted my knowledge and need some help.
Most important question: Is this device recoverable? If not, there's no point in banging my head against the wall.
Secondly, am I on the right track or do I need to be doing something else? (if so, please point me in the right direction)
Is this as simple as the drivers not working right and should I continue to try different driver versions along with different USB sockets and cables? (tried a few cables including what I think is the unused OEM one). Is there a way to check that the driver is actually working or is its presence in device manager the only indication?
I've tried several Odin versions also.
Nothing I've tried has got past the NAND write, and I only managed to get that far last night.
How long approx should it take to flash and is there any progress indication on either Odin or device? (There's no point in waiting an hour if I should see something happening within 2 minutes, I may as well cancel and try something else)
I'm sorry for having to ask because I know to some of you, this may seem a simple problem and you may roll your eyes, but I really have tried everything I know and need to know if there is a chance what I've been doing will suddenly work or if I need to do something else or give up entirely. I never ask for help on a forum without trying my best to research and solve the problem.
TIA
Edit
I tried again, and left it showing at NAND writing, and after annhour or two, it completed, but failed. I don't know if this is a time out thing or whether it tried and failed. Without knowing if I'm on the right track there' s no point in repeating the same actions that are going to fail.
Must admit, expected some kind of response by now.
You may not have all the answers but if you may have part of one answer. I don't have anything to lose because the device will be going into landfill unless something happens.
cecr said:
Must admit, expected some kind of response by now.
You may not have all the answers but if you may have part of one answer. I don't have anything to lose because the device will be going into landfill unless something happens.
Click to expand...
Click to collapse
Boot into recovery and factory reset. Then, with the latest stock ROM available, flash only the AP and BL modules. If Odin shows "added" when you plug in the cable, then the driver is working. Have you tried a different USB cable?
Did you try using the latest patched Odin? If it says added then the driver is working so it can't be a driver problem. It usually doesnt take more than 10 minutes to flash stock rom so don't wait an hour. As @lewmur said try flashing just the BL and AP files and try different USB cables and sockets also avoid using a USB hub.