Newsmy NU3001-01-H - Full NAND backup with RKFLASHTOOL for Windows - Android Head-Units

Dears,
I'm trying to do a full NAND backup on Windows with rkflashtool 5.1 (I can succeed on Ubuntu, but on Windows I have several errors).
Drivers are OK because I can read and write NAND with any other tools, but I need rkflashtool because it's the only one I know able to read and write the whole NAND to a single file from command line.
I'm on Windows 10 x64 build 1607.
On NU3001-01-H (CPU RK3188) NAND size is 7456MB with 512kB blocks, so
7456MB x 1024 = 7634944kB
7634944kB / 512kB = 14912 blocks = 0x3A40 blocks
Running as user or admin
rkflashtool r 0x0 0x3A40 > dump.bin
or
rkflashtool r 0 14912 > dump.bin
I'm returned
C:\Users\TSS\Downloads\SCS\Tools\Windows\rkflashto ol-5.1-win32-bin>rkflashtool.exe r 0x0 0x3A40 > dump.bin
rkflashtool: info: rkflashtool v5.1
libusb: 0.000000 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.000000 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.015627 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.062504 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.062504 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.062504 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.078130 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.093755 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.093755 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.109382 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.109382 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.125008 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.140633 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.140633 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.140633 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
libusb: 0.156259 warning [init_device] could not get node connection information for device '\\.\USB#VID_04F2&PID_0841&MI_01#7&7E2D85&0&0001': [87] Parametro non corretto.
libusb: 0.171886 error [init_device] device '\\.\USB#VID_046D&PID_C52B&MI_01#7&22AD43FB&0&0001 ' is no longer connected!
libusb: 0.171886 error [init_device] device '\\.\USB#VID_0BDA&PID_0161&MI_01#7&1E43E1E2&0&0001 ' is no longer connected!
rkflashtool: fatal: cannot open device
I really don't know what to do.
Any suggestions?
Thanks and best regards

How did you get ur pc to detect ur HU ?

Hi there.
I simply powered it on with reset hole pressed, then I had drivers installed and checked it's correctly listed in the devices manager.
Thanks.

Dang wish it wasnt that easy lol.
Ok guess my unit is trashed
My pc wont recognize it and it wont power on at all.

Related

[Q] pls help anyone has got any solution to this problem?

http://forum.xda-developers.com/showthread.php?p=32877250#post32877250
Here is a part of log from RSD lite:
04/22/12 01:53:07 Multi upgrade started for 1 phones
04/22/12 01:53:07 [Device ID: 0] Flashing phone.
04/22/12 01:53:20 ERROR: Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F - on device ID 0.
04/22/12 01:53:20 ERROR: Flash failure: Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F (Error Code: e003009f),
Detailed Error Details: Direction of the Error=1000, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
04/22/12 01:53:20 [Device ID: 0] Phone[0000]: Error sending TI ROM data packet request. Device API Error: 0xE003009F
04/22/12 01:53:20 ERROR: Failed flashing process. - on device ID 0.
04/22/12 01:53:20 Multi upgrade finished.

[Q] Android Tethering tool

I have installed USB tunnel and Super User on my nexus 4.
Have enabled USB debugging mode.
Connected by phone to my windows XP laptop and started Android Tethering Tool on my laptop.
USB tunnel didn't ask for super user permission.
Getting the below error logs. Kindly help me to rectify it.
Thanks in advance.
10-10 18:11:57:812 W/D UsbThread : ReadBytes : Connection Closed Gracefully.
10-10 18:11:57:812 W/I Tool version : 3.14
10-10 18:11:57:812 W/I adb.exe
10-10 18:11:57:812 W/I aapt.exe
10-10 18:11:56.66 A/I **************************************************
10-10 18:11:56.66 A/I UsbThread9.run() -> input.read returns -1
10-10 18:11:56.66 A/E UsbThread9.run() -> unexpected disconnection
10-10 18:11:56.66 A/I UsbThread9 : usbServerSocket : Waiting for the host to connect
10-10 18:11:57:952 W/I Android Debug Bridge version 1.0.31
10-10 18:11:59.26 A/I UsbThread : thread main : wait current UsbThread to terminate 0
10-10 18:11:59.26 A/I UsbThread9.run() needToBeClosed is true
10-10 18:11:59.27 A/E shell : Exception while trying to run: '/data/data/service.tracetool/app_bin/busybox21 ps' Error running exec(). Command: [su] Working Directory: null Environment: null
10-10 18:11:59.27 A/I UsbThread9 : thread stopped
10-10 18:12:00:624 W/I Wait java service
10-10 18:12:00:734 W/I waiting android server connection ... 1
10-10 18:11:59.94 A/I TunnelController : thread stopped
10-10 18:12:01:140 W/I Waiting for connection
10-10 18:12:00.28 A/I UsbThread10 : usbServerSocket : Waiting for the host to connect
10-10 18:12:01:812 W/E UsbConnected exception Socket Error # 10054
Connection reset by peer.
10-10 18:12:02:812 W/E UsbConnected exception Socket Error # 10054
Connection reset by peer.
10-10 18:12:03:812 W/E UsbConnected exception Socket Error # 10054
Connection reset by peer.
10-10 18:12:04:812 W/E UsbConnected exception Socket Error # 10054
Connection reset by peer.
10-10 18:12:05:812 W/E UsbConnected exception Socket Error # 10054
Connection reset by peer.
10-10 18:12:06:812 W/E UsbConnected exception Socket Error # 10054
Server List
DNS List
172.23.201.20[default]
172.23.202.12

[SOLVED] S4 i337M - Help Installing Custom Recovery

Hi guys
I bought an S4 i337M used but in really mint condition. The first thing I noticed is that USB Debugging isn't working good, sometimes it connects, sometimes the device says unathorized (but no message appeared on the phone), charging is working, also HDMI Out and connection in Download Mode, maybe I need a reflash of stock ROM? I'm in Linux and haven't such errors before (I had a S4 from Sprint two days and no problem)
Already rooted with towelroot method but I want to install CWM even if it voids my warranty (don't have much time left anyway) but when I try to install with Heimdall I get this error
Code:
ERROR: Failed to send file part packet!
In Odin, the process start but freezes (presumably is the same that happens with heimdall)
I have read a lot but can't find proper information, with the latest firmwares, can't we flash custom recovery using heimdall/odin? should I go for the Loki method? or safestrap? I don't know where to go from here, any advice is apreciated.
Thanks
The full output from Heimdall is
Code:
Initialising connection...
Detecting device...
Manufacturer: "Sasmsung"
Product: "MSM8960"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 0100
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 82
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 01
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #1 failed. Result: -9
WARNING: Control transfer #2 failed. Result: -9
WARNING: Control transfer #3 failed. Result: -9
WARNING: Control transfer #4 failed. Result: -9
WARNING: Control transfer #5 failed. Result: -9
WARNING: Control transfer #6 failed. Result: -9
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
0%ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send file part packet!
ERROR: RECOVERY upload failed!
Ending session...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.
ERROR: Failed to receive session end confirmation!
Releasing device interface...
Re-attaching kernel driver...
Thanks for taking the time to see this
For someone experiencing this: solved it by installing ROM Manager through Google Play, I installed non touch CWM first but then paid for touch version to help devs (in that step Knox Warranty Void is 0x0). I made a Nandroid and then installed CM 11 and it worked good. For my surprise Knox Warranty Void still shows 0x0 .
I'll share the steps I made in a new thread if that works for someone else with a i337m

Droid RAZR M: Qflash Utility Help

QFLASH Problem
What the hell .. squint emoticon
"No data read from USB. This may not be an error. Trying again..."
if anyone knw about it so Guide me .i am very close :|
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>python 8960_blankflash.py
Emergency download enumeration detected on port - com3
Starting qflash!
Executing command qflash.exe -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloa
der_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM3
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
dmss_go : failed to receive ACK
Error loading MPRG8960.hex into device
Blank flashing successful
Device will now enumerate in fastboot mode
D:\Downloads\Compressed\Moto.X.Unbrick\Python27>pause
Press any key to continue . .

Galaxy S4 Mini GT-I9192: Reverse Tethering Issue

Reverse Tethering Help!
Hi guys,
I have trouble when the connection is finishing.
The connection stops when the program's console asks to accept the access with SU in android, but my phone doesn't show anything.
Device: Samsung Galaxy S4 Mini (GT-I9192)
10-05 10:54:40:107 W/I Tool version : 3.19
10-05 10:54:40:107 W/I C:\Program Files\Android\android-sdk\platform-tools\adb.exe
10-05 10:54:40:107 W/E aapt.exe not found. Check config
10-05 10:54:40:300 W/I Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
10-05 10:54:40:611 W/I Your IE proxy is "192.168.0.175" on port 3128. Enabled : false
10-05 10:54:44:361 W/E aapt.exe not found. Check config
10-05 10:54:44:361 W/E could not run command
10-05 10:54:44:361 W/E C:\Program Files\Android\android-sdk\platform-tools\aapt.exe d badging installed.apk
10-05 10:54:44:362 W/E Error code 2 : O sistema não pode encontrar o arquivo especificado.
10-05 10:54:44:362 W/E aapt.exe not found. Check config
10-05 10:54:44:363 W/E could not run command
10-05 10:54:44:363 W/E C:\Program Files\Android\android-sdk\platform-tools\aapt.exe d badging "Tracetool service.apk"
10-05 10:54:44:363 W/E Error code 2 : O sistema não pode encontrar o arquivo especificado.
10-05 11:00:56.25 A/W process (9290) : Implicit intents with startService are not safe: Intent { act=service.tracetool.SocketService.ACTION (has extras) } android.content.ContextWrapper.startService:506 android.content.ContextWrapper.startService:506 service.tracetool.TTBroadcastReceiver.onReceive:41
10-05 11:00:56.34 A/I UsbThread7 : usbServerSocket : Waiting for the host to connect
10-05 10:54:46:563 W/I Wait java service
10-05 10:54:46:687 W/I waiting android server connection ... 1
10-05 10:54:47:000 W/I Waiting for connection
10-05 10:54:48:636 W/I Sending busybox21
10-05 11:00:59.68 A/E UsbThread7.run() loop error. firstByte : 39 : WTOA_copyFile
10-05 11:00:59.68 A/E UsbThread7.run() loop error. lastCommand : 32 : WTOA_setGlobalVar
10-05 11:00:59.68 A/E UsbThread7.run() loop error. Exception type : class java.io.FileNotFoundException
10-05 11:00:59.68 A/E UsbThread7.run() loop error. Exception message : /storage/emulated/0/busybox21: open failed: EACCES (Permission denied)
10-05 11:00:59.68 A/E UsbThread7.run() loop error. Exception cause : libcore.io.ErrnoException: open failed: EACCES (Permission denied)
10-05 11:00:59.68 A/E UsbThread7.run() loop error. Exception string : java.io.FileNotFoundException: /storage/emulated/0/busybox21: open failed: EACCES (Permission denied)
10-05 11:00:59.68 A/E libcore.io.IoBridge.open(IoBridge.java:409)
10-05 11:00:59.68 A/E java.io.FileInputStream.<init>(FileInputStream.java:78)
10-05 11:00:59.68 A/E service.tracetool.Api.copy(Api.java:1471)
10-05 11:00:59.68 A/E service.tracetool.UsbThread.copyFile(UsbThread.java:1944)
10-05 11:00:59.68 A/E service.tracetool.UsbThread.run(UsbThread.java:316)
10-05 11:00:59.68 A/E UsbThread7.run() -> unexpected disconnection
10-05 11:00:59.68 A/I UsbThread7 : usbServerSocket : Waiting for the host to connect
10-05 10:54:50:593 W/D UsbThread : ReadBytes : Connection Closed Gracefully.
Server List at 10-05 10:56:04:810
DNS List
8.8.8.8
8.8.4.4
4.2.2.1
4.2.2.2
208.67.222.222
208.67.220.220[default]
8.26.56.26
8.20.247.20
156.154.70.1
156.154.71.1
Click to expand...
Click to collapse
Guerrillian said:
Hi guys,
I have trouble when the connection is finishing.
The connection stops when the program's console asks to accept the access with SU in android, but my phone doesn't show anything.
Device: Samsung Galaxy S4 Mini (GT-I9192)
Click to expand...
Click to collapse
Hi! I have no idea how to fix the issues above, but if you are interested in a Reverse Tethering solution that might work more reliably, you might want to try ReverseTethering NoRoot, an app I have developed. I have opened a dedicated thread over here: http://forum.xda-developers.com/android/apps-games/app-reversetethering-noroot-t3316716

Categories

Resources