A few days ago, the display of my phone broke and became unusable because the touchscreen isn't working anymore. So i tried to backup my files and since i can't use my display anymore to unlock the phone I tried using adb instead. But at some files the pulling fails with the error code "(FILEPATH): remote read failed I/O error". After that the whole pulling process stops.
Does anybody know how to fix that?
I'm rooted with magisk and I'm able to use root in adb.
~Lukas
Related
whats up guyz im new/old to this forums new/old means , i dont get online to much
well i have been tweaking a little bit with my droid DNA and found out some work around for some problems people might be having trying to unlock their bootloaders
the first problem i encountered was the adb killing process , adb is out of date . there is a little work around for this , that worked with me and my friend s DNAs to resolve this we just killed the adb daemon with this command
adb kill-server
then we started the server with the command
adb start-server
allright . the only way you will not get that error of adb out of date is , if you see adb starting on some port . i forgot the port number, but thats the only way you will not be getting the error ..
the second problem i encountered in the process of unlocking my phone was the restore update not finishing , which was caused by the bug of adb out of date error. once you resolve the problem with the adb bug out of date error , then you will be able to restore the phone successfully
but hold on , there is another problem some people might be getting , when you execute the command " adb restore backup.ab " if your device is taking to long to finish the restore and the window is behind looping, dont worry about it just wait couple of minutes control -c on the window looping and control -c on the window that you waiting on the restore to finish ... i tried that couple of times then i figure that the restore did go thru ..
some people might be getting an error with this command "adb shell mv /data/DxDrm /data/DxDrm_org" if you getting the error that says failed to blah blah blah permission denied , the cause for of that error is that the restore didnt go thru . if you got that error you can reboot safely , your device is not bricked yet lolz ..
when you get to the section that you have to repeat the exploit again , you gonna start getting the error again with the adb killing the process out of date thingy , dont worry just redo the work around i posted above , i control c the restore window and the loop window
couple of times just to make sure it was working fine , and it did . it was working fine
sorry for my english guys . i just wanted to point out those little flaws in the process of unlocking the bootloader , just in case some people get the same errors , they wont have to break their heads with it ... blessed be ..
Minor audible...
I was using the video made by DroidModderX and was able to get through it basically step by step with one minor hiccup. One the step where you start the first command prompt to do that "loop of errors" and move to the second command prompt, my system had an error doing this until I unplugged the phone and plugged in again. That wasn't mentioned in the tutorial but worked great once I did that part. It seemed like ADB got a little screwed up or something but, once I unplugged/ replugged it all worked normally. One other thing I noticed was that in the video (he uses a mac) the first command prompt continues to "loop" until you hit CRTL + C and on mine as soon as did the command in "prompt 2" the loop stopped on its own although all of the commands still worked as planned. I was doing this on Windows7 32bit. Hopefully that makes sense or is helpful to someone...
all you had to do was kill, then restart adb? that's not doing the trick for me, damn
EDIT: I got mine to work by uninstalling HTC Sync, it has an adb.exe file that was causing the error
I was able to leave HTC Sync installed but I had to uninstall Droid Explorer from my Incredible days. Only then did the ADB out of date error stop.
I used this before with HTC Sync. Maybe that is why I was able to keep it installed.
The attached zip is from http://visualgdb.com/adbfix/
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
mewrius said:
So I'm trying to get my device back to stock so I can ship my device to someone I sold it too but somehow I'm running into issues.
I installed Terrasilent kernal and custom rom on my US 4.0 way back last spring and never had to connect my device to a computer since. Well now obviously I have to and am trying to do it off a new laptop I recently purchased.
My steps so have gone like this.
1. Downloaded and installed Samsung Drivers
2. Downloaded and installed C++ Redistrubiutable from: http://www.microsoft.com/en-au/download/details.aspx?id=30679
(I only got the bottom one. Did I need all 3?
3. Downloaded Latest Heimdall
4. Ran zadig and updated the one Samsung device that showed up
5. Ran Heimdall and loaded the pit and recovery files from this thread http://forum.xda-developers.com/showthread.php?t=1531850
But every time I get some sort of error.
The latest error being
Beginning session...
ERROR: Failed to begin session!
Releasing device interface...
After trying reinstalling drivers and such I've also ran into this error
error: failed to access device. libusb error: -12
Am I missing a very simple step? Somehow even though Heimdall won't flash anything I've also managed to get my device soft bricked.
Sadly I don't remember having such issues when I originally rooted my device and flashed it. Any ideas? I'd really love to get this device shipped out to the person it was sold to.
Click to expand...
Click to collapse
Did you installed the drivers while you were in download mode? Maybe this would solve your actual issues. Also if you used a different port, you need to reinstall the drivers once again AFAIK.
Hi everybody. i just got some problems with my wifi, i try to fix it for 3 days with every fixer but nothing. i tried everything, and i got this message in logcat
WifiStateMachine: failed to load driver'
WifiStateMachine: driver failed state
with an nother program i got the message :Cannot open "/data/.cid.info": No such file or directory
Anyone had this problem? i looked on google for the problem but i didnt find it...
I have galaxy i9103
So, I was sort of thinking that at least rooting and OTA blocking with the handy hdx toolkit would be easy but I don't get the impression that it is working. My Firmware is 13.3.2.3.2 and I used towelroot via the toolkit. This is what I see when I root. (aren't allowed to post links/images yet so it's only a non-clickable link to the image, sorry)
i.imgur.com/GLtVd1R.jpg
As you can see, there are some error messages. It also asks me to select 'make it rain' but there is nothing on my device to actually select and it continues on without my input. It then says 'please wait until device reboots' but my device continues to be entirely unimpressed and doesn't reboot, not even a bit. In short, while the root *appears* to be doing something, I don't think it actually does because it can't find the stuff it needs. On the next screen it checks if the rooting worked but it only gets me another error message saying /system/bin/sh: su: not found
help, please?
You can download and install towelroot manually.
As for OTA updates, you can rename /system/etc/security/otacerts.zip to anything else (i.e. otacerts.zip.bak); that should block them.
I couldn't leave well enough alone despite @EncryptedCurse excellent advice and managed to troubleshoot it and get it working in the toolkit after all. In case someone has similar troubles (Error 2 and Error 3 are what I got at different times) here's how I got it working (in Windows 7):
-In the device manager I uninstalled the adb driver (with adb enabled the kindle is listed twice in the device manager, you should unistall the drivers of the one that *isn't* listed under portable devices) and restarted the computer. Edit: On second thought: I'm not sure if that uninstall worked. I think I needed to use uninstaller.exe in C:\Program Files (x86)\Amazon.com\Kindle Fire\Drivers to really remove the driver.
-Then I disabled ADB in the kindle. I also shut down my antivirus (not sure if it made a difference but some people have reported interference). Then I used the toolkit to install adb drivers again (in the instructions there it says to have adb enabled while doing this but if you get error messages while rooting try it this way.).
-Now I rebooted the computer again (this is important), checked that antivirus was still activated, checked that Bluestacks was *also* still shut down (having it or another emulator open leads to a complete different error message, I have learned ) and tried rooting with the toolkit again. It worked with no troubles.
My 7840 stopped working suddenly. It would only give me a gray screen. Upon repeated reboot attempts, it came up with a screen that said "erasing....." It was unlocked and rooted. But it took a tremendous amount of work trying everything I could find to get the OS installed. Which, I finally did. using this post from anggusss, http://forum.xda-developers.com/showpost.php?p=61719794&postcount=18. But the resultant system was highly unstable. Nearly every google app would "unfortunately" close making it nearly impossible to restore the tablet from a titanium backup. The google play services would stop about every minute and the play store would quit during installs. So then I tried using xBigReddx's suggestion (http://forum.xda-developers.com/dell-venue/general/venue-8-7840-developer-files-posted-t3144232) But the intel platform flash tool fails no matter what I try. For example, If I load Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397.zip and try to flash flash-DDO_BB.xml, I get
11/22/16 15:57:27.985 WARNING: Bootloader DnX file not specified in flash configuration ("os_dnx" key)
before I start the flash. Then after I do start it, It fails at 3% with the errors
11/22/16 15:59:27.881 ERROR : Automatic reboot is not supported on this device, please reboot the device manually
11/22/16 16:00:09.013 ERROR : [Port 2/1] Command `"C:\Program Files (x86)\Intel\Platform Flash Tool Lite\xfstkFlashTool.exe" "-1" "F:\packages\Android\Dell\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\dnx_fwr_blackburn_qs_rd_opensource.bin" "F:\packages\Android\Dell\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\ifwi_blackburn_qs_rd_opensource.bin" "" "F:\packages\Android\Dell\Dell_Venue_8_7840_Lollipop_5.0.2_qs_rd_opensource-blankphone-userdebug-1397\droidboot_dnx.img" "0x80000c27" "none" "none" "0"` failed
11/22/16 16:00:09.013 ERROR : [Port 2/1] Flash failed (Command type: Ifwi)
As suggested by johnsag49, in http://forum.xda-developers.com/dell-venue/general/root-howto-dell-venue-8-7840-t3282532, I retried it about a dozen times. It never succeeded.
As I said, the phone was unlocked, but the fastboot screen does not show that (I've attached a picture of it). If I try to unlock it again with "fastboot OEM unlock", I get
RESULT: FAIL(unknown OEM command)
If I try "fastboot flashing unlock" or any other command of that ilk I get
RESULT: FAIL(unknown command)
I've been yelling obscenities out loud for some hours (days) now trying to get this working.
If you have any idea what is wrong and how I can fix it, I would be forever grateful. Thank you!
Have you received help on this matter? Do you still need insight?