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
Related
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.
Hi all,
I recently decided on trying my hand at rooting my s5, have done my research and this is where i wanted to take my phone, and where to come for help.
Ive gone through Odin v3.07 and no COM's would register, i tried tool kit but it wouldn't start after i installed drivers and such, there was a third one i found through threads in here as well but to no avail, nothing has proved any results.
so this is where you all can swoop in and save the day, when I used Odin (which seems to yield the furthest results) the only trouble im having is opening my phone in the ID:COM section. When I plug my s5 into my linux mint 10.something hp notebook (which could be the whole problem all together), with a v2 or v3 usb it registers as gFTP and I can do very little with the files there. like i noted above, toolbox didnt even open, nor could i even figure out what to do with the third thing i tried using. so, my last resort, a community that actually knows what they're doing...
What advice/guidance can you all pert to me? what do you think the problem might be? do i need to perform a factor reset to root my phone? is it the operating systems i am working on? i tried briefly on a mac osx 10. something and now am on a linux mint.
i am not very tech savy but can pick things up fairly quickly, so pretend im dumb and give explicit detail and i will pick up what you miight be talking about more easily.
P.S. I am NOT a robot lol
I have been searching through different android support pages today and everyone seems to resolve their rooting issues easily. though their solutions dont seem to provide me with any answers. i can list any info needed for further diagnostics, but to label a few outright, i have enabled usb debugging in developer mode, tried different usb ports and before/after phone is in downlaod mode, i have SM_G900P 4.4.4 and anything else you need, to help me
Hello!
This is my first post, but I have found this forum incredibly helpful, and I am hoping to provide a little help myself (and maybe get a little along the way)
I just unboxed a new Nexus 7 (Amazon order within the last 7 days). My purpose for this particular device was to be a dedicated Nethunter device so that I can perform some work related functions with it.
After fiddling for about 2 days with not being able to get the darn thing rooted, I figured out that the lastest/official TWRP builds DO NOT work with the brand new Nexus 7's! This essentially renders things like NRT useless unless you happen to know that you need a very specific custom recovery - (thanks to another thread here on this forum) I figured out that I had to flash a custom multi rom version of TWRP in order to get the device rooted. The intersting thing, this thread was full of people with BRAND new nexus devices . . . not older (by older I mean 3 months or more)
Well, the problems continued. Once I got Nethunter going I was not able to get any external wifi card enabled. More searching as revealed that alot of people are having this issue with lollipop and that the general recommendation is to downgrade to KitKat.
Ok Ok . . so I decided to say "screw lollipop, I'll flash back to 4.4.4"
Yeah . . .well . . . no luck there. No matter what version of bootloader I flashed, and no matter which version of KitKat I tried, I couldn't get any of them to boot past the google initial boot screen. With the recovery mode complaining about not being able to mount /cache /recovery . . .etc - I tried flashing them several different ways and ever from different computers. I even tried downloading the stock images multiple different times.
So . .that brings me to the point of this. It appears that Nexus devices ordered in the last 60 days must have some type of hardware revision change that is making things pretty complicated
I am curious if anyone else is seeing strange things like this?
I can get a rooted version of 5.1.1 going no problem, but I am "stuck" with this weird issue with the external cards, and the weird issue where I cant downgrade.
Thanks for listening
Also, just to add real quick, this device is a 16GB wifi model. The bootloader is claiming a Hardware version of "Rev_E"
I dont have another Nexus 7 to look at, but I wasn't sure if Rev_E was of importance.
Thanks
Hello, guys! It's now my 2nd post asking the exact same help. I'm very desperate to fix my phone : Asus Zenfone 5.
I have been looking for solutions for a long time, I'm not easily quit on googling. So far, this problem is one that haven't been fixed and very unlikely to be fixed
I have contacted many people including that Taiwan guy who is an expert on Zenfone 5 (forgot the name) and I'm EXTREMELY DESPERATE
I know this problem might be similiar with other case, but this one seems to be rare, because I have not found the solution.
Here is the timeline before my device got soft-bricked :
1. I upgraded to Lolipop with a different version of it's recovery, but still worked.
2. One day, ANR Keeps reporting that SystemUI has stopped. Rebooted and the phone went bootloop.
3. (probably the problem) I flashed wrong version of recovery (I think it was kitkat's recovery) and after then, I'm not able to get into DROIDBOOT.
I have tried several ways :
1. Sending package to my phone over ADB Sideload (It says something like error mounting blabla)
2. Flashing with xFSTK (It says something about driver, and I googled it. Found everyone with the same problem, endless solutions)
3. Downloaded about 1 gig of files (DEBRICK Files) and still, gets stuck somewhere.
So anyone have a solution for me, please?? I'm totally desperate right now, I lost hope. Never had this kind of problem, the thing is that so far, I never had such never-solved case in my life, I will always
find a solution from Google even that would take a long time. I have been searching passively for about 8 months, and I got none of those works
I will be very thankful if anyone would try to help this problem, I will bring detailed information you want, because I don't have solutions left.
Sorry for bad English
Thank You so much!
Christ, I was sure that I ticked it as a Q/A.
how to help? you are just telling about softbrick.
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.