Nevermind, it just seemed to need another reboot (the first didn't quite do it)
Hi, I just flashed CM 11 and all but 1 thing seems to be working properly.
When I try to connect to the device through adb (via cable or a wireless adb application) adb cannot find any devices.
The results of lsusb are here
Code:
Bus 002 Device 003: ID 1058:1140 Western Digital Technologies, Inc.
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
Bus 006 Device 002: ID 046d:0a1f Logitech, Inc.
Bus 006 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
It looks like the computer isn't recognizing the kindle at all.
Is there any way that adb isn't enabled in CM 11 (I can't find the option anywhere)? Or do I need to associate the device with adb somehow?
Thanks for any help
EtagAwesome said:
Nevermind, it just seemed to need another reboot (the first didn't quite do it)
Hi, I just flashed CM 11 and all but 1 thing seems to be working properly.
When I try to connect to the device through adb (via cable or a wireless adb application) adb cannot find any devices.
The results of lsusb are here
Code:
Bus 002 Device 003: ID 1058:1140 Western Digital Technologies, Inc.
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
Bus 006 Device 002: ID 046d:0a1f Logitech, Inc.
Bus 006 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
It looks like the computer isn't recognizing the kindle at all.
Is there any way that adb isn't enabled in CM 11 (I can't find the option anywhere)? Or do I need to associate the device with adb somehow?
Thanks for any help
Click to expand...
Click to collapse
ok well um incase you didnt already do this, to turn on adb its in settings>developer options, but to get the developer options to show up you need to tap on the build number around 10 times in the about tablet area of settings. Once you do this you can enable adb, though i will say that is odd i figured that a lab126 device would atleast showup with lsusb even if adb is disabled for the mtp device. Try plugging the device in and running a dmesg and see if its even recognizing it as plugged in there.
stunts513 said:
ok well um incase you didnt already do this, to turn on adb its in settings>developer options, but to get the developer options to show up you need to tap on the build number around 10 times in the about tablet area of settings. Once you do this you can enable adb, though i will say that is odd i figured that a lab126 device would atleast showup with lsusb even if adb is disabled for the mtp device. Try plugging the device in and running a dmesg and see if its even recognizing it as plugged in there.
Click to expand...
Click to collapse
I think it just needed a power cycle. After a reboot adb seems to be working. And I do now have a lab126 in the lsusb
Code:
Bus 002 Device 033: ID 1949:0007 Lab126
Bus 002 Device 003: ID 1058:1140 Western Digital Technologies, Inc.
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
Bus 006 Device 002: ID 046d:0a1f Logitech, Inc.
Bus 006 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Thanks anyways for your help!
Hi
My Xperia Z1 is hard bricked
won't boot ( earsed everything)
batter is empty (is it chrges while fastoob or flash mode?)
trying to flash new software but sometimes says ERROR 31 device you connected pc is not fuctioning (sry bad english)
i tryed Flashtool, EMMA, PC Companion, SUS
my problem here is how to install new soft
McP6ts said:
Hi
My Xperia Z1 is hard bricked
won't boot ( earsed everything)
batter is empty (is it chrges while fastoob or flash mode?)
trying to flash new software but sometimes says ERROR 31 device you connected pc is not fuctioning (sry bad english)
i tryed Flashtool, EMMA, PC Companion, SUS
my problem here is how to install new soft
Click to expand...
Click to collapse
Using Linux. Type this command on Terminal
Code:
lsusb
Is this output come
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 0fce:519e Sony Ericsson Mobile Communications AB
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0bda:0139 Realtek Semiconductor Corp. Card reader
Bus 001 Device 004: ID 058f:a014 Alcor Micro Corp. Asus Integrated Webcam
Bus 001 Device 003: ID 13d3:3304 IMC Networks
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
Hi,
i can't get ADB running. I activated it in the developer options and tried also checking and unchecking the usb 2 option.
On my Computer i'm running Linux Mint 17.1.
When imt checking for adb devices it's just an empty list.
I also tried this Instruction but it didn't help.
I really don't know what to do.
nme1337 said:
Hi,
i can't get ADB running. I activated it in the developer options and tried also checking and unchecking the usb 2 option.
On my Computer i'm running Linux Mint 17.1.
When imt checking for adb devices it's just an empty list.
I also tried this Instruction but it didn't help.
I really don't know what to do.
Click to expand...
Click to collapse
connect the device to a usb port and show the output of command
Code:
lsusb
Tommmii said:
connect the device to a usb port and show the output of command
Code:
lsusb
Click to expand...
Click to collapse
Code:
Bus 002 Device 003: ID 1532:010e Razer USA, Ltd
Bus 002 Device 004: ID 2b4c:1015
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1210:25f4 DigiTech
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
while
Code:
Bus 002 Device 004: ID 2b4c:1015
is my Phone
Also my Phone doesn't ask for the permissions for the PC to connect with ADB.
And I tried switching between mtp and ptp.
nme1337 said:
Code:
Bus 002 Device 003: ID 1532:010e Razer USA, Ltd
Bus 002 Device 004: ID 2b4c:1015
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1210:25f4 DigiTech
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Click to expand...
Click to collapse
what's in your file /etc/udev/rules.d/51-android.rules ?
Tommmii said:
what's in your file /etc/udev/rules.d/51-android.rules ?
Click to expand...
Click to collapse
****, somehow i'm the biggest idiot i misspelled and wrote 1013 instead of 1015.
feel so dump now. i was looking so often at it and didn't realize... sry
So many Thank for : Android Root Team
Code:
https://github.com/AndroidRoot
So many Thank for: Jevinskie
Code:
https://github.com/jevinskie
My github
Code:
https://github.com/GeorgeMato4/nvcrypttools/tree/forN7
required: Use linux based OS.!!!!
First time:
To make your encrypted blob for your Tegra3 Device ( Nexus7/tf201/tf300/tf700) you need another working tegra3 Device.
I am sorry for that, but i was going with easys possible way. I will solve this, but not now.
But, when you give me information (sbk and cpuid) , i will try create blob for you. And , if will be your device restored, please, help others with same problem.
How get sbk from your bricked device?
Download from Jevinskie Github page source code.
Code:
https://github.com/jevinskie/fusee-launcher
Unzip and make it. (Open in folder with source code command line and type “make” )
It is need install pyusb with command “pip install pyusb”.
It is need connected device to usb v3.
Check if is device in apx mode with command “lsusb”. In list must be Nvidia corp.
Run Command on sudo “./fusee-launcher.py –tty dump-sbk-via-usb.bin”
You get something like this:
Code:
05f4a5d01'
Stack snapshot: b'0000000000000000100000003c9f0040'
EndpointStatus_stack_addr: 0x40009f3c
ProcessSetupPacket SP: 0x40009f30
InnerMemcpy LR stack addr: 0x40009f20
overwrite_len: 0x00004f20
overwrite_payload_off: 0x00004de0
payload_first_length: 0x00004de0
overwrite_payload_off: 0x00004de0
payload_second_length: 0x0000c7b0
b'00a0004000300040e04d0000b0c70000'
Setting rcm msg size to 0x00030064
RCM payload (len_insecure): b'64000300'
Setting ourselves up to smash the stack...
Payload offset of intermezzo: 0x00000074
overwrite_payload_off: 0x00004de0
overwrite_len: 0x00004f20
payload_overwrite_len: 0x00004e5c
overwrite_payload_off: 0x00004de0
smash_padding: 0x00000000
overwrite_payload_off: 0x00004de0
Uploading payload...
txing 73728 bytes total
txing 4096 bytes (0 already sent) to buf[0] 0x40003000
txing 4096 bytes (4096 already sent) to buf[1] 0x40005000
txing 4096 bytes (8192 already sent) to buf[0] 0x40003000
txing 4096 bytes (12288 already sent) to buf[1] 0x40005000
txing 4096 bytes (16384 already sent) to buf[0] 0x40003000
txing 4096 bytes (20480 already sent) to buf[1] 0x40005000
txing 4096 bytes (24576 already sent) to buf[0] 0x40003000
txing 4096 bytes (28672 already sent) to buf[1] 0x40005000
txing 4096 bytes (32768 already sent) to buf[0] 0x40003000
txing 4096 bytes (36864 already sent) to buf[1] 0x40005000
txing 4096 bytes (40960 already sent) to buf[0] 0x40003000
txing 4096 bytes (45056 already sent) to buf[1] 0x40005000
txing 4096 bytes (49152 already sent) to buf[0] 0x40003000
txing 4096 bytes (53248 already sent) to buf[1] 0x40005000
txing 4096 bytes (57344 already sent) to buf[0] 0x40003000
txing 4096 bytes (61440 already sent) to buf[1] 0x40005000
txing 4096 bytes (65536 already sent) to buf[0] 0x40003000
txing 4096 bytes (69632 already sent) to buf[1] 0x40005000
txing 4096 bytes total
txing 4096 bytes (0 already sent) to buf[0] 0x40003000
Smashing the stack...
sending status request with length 0x00004f20
The USB device stopped responding-- sure smells like we've smashed its stack. :)
Launch complete!
b'4445414442454546'
DEADBEEF
b'3030303030303030'
00000000
b'3030303030303030'
00000000
b'3034303030303930'
04000090
b'4634314330433241'
F41C0C2A
b'3133333731333337'
13371337
b'3535353535353535'
55555555
b'3430303033303030'
40003000
b'3430303035303030'
40005000
b'4141414141414141'
AAAAAAAA
b'3131313131313131'
11111111
b'3030303030303236'
00000026
b'3232323232323232'
22222222
b'68656c6c6f2c20776f726c640a00'
hello, world
b'e57de3bab6cb499d874d5772cb219f0101042c20' (This is SBK)
Traceback (most recent call last):
File "./fusee-launcher.py", line 823, in <module>
buf = switch.read(USB_XFER_MAX)
File "./fusee-launcher.py", line 530, in read
return self.backend.read(length)
File "./fusee-launcher.py", line 134, in read
return bytes(self.dev.read(0x81, length, 3000))
File "/usr/local/lib/python3.6/dist-packages/usb/core.py", line 988, in read
self.__get_timeout(timeout))
File "/usr/local/lib/python3.6/dist-packages/usb/_debug.py", line 60, in do_trace
return f(*args, **named_args)
File "/usr/local/lib/python3.6/dist-packages/usb/backend/libusb1.py", line 833, in bulk_read
timeout)
File "/usr/local/lib/python3.6/dist-packages/usb/backend/libusb1.py", line 936, in __read
_check(retval)
File "/usr/local/lib/python3.6/dist-packages/usb/backend/libusb1.py", line 595, in _check
raise USBError(_strerror(ret), ret, _libusb_errno[ret])
usb.core.USBError: [Errno 110] Operation timed out
You need this two number: Tegra with Device ID: b'01042c205f4a5d01
and
hello, world
b'e57de3bab6cb499d874d5772cb219f0101042c20'. This is not real sbk.
Sbk have only 32 number. Your sbk is only “e57de3bab6cb499d874d5772cb219f” and after this number is first 8 number from tegra device id.
Congratulation, you get sbk.
I test dump-sbk-via-usb on nexus 7 and on asus TF300. I thing this will work on other device.
How get chip id?
Download wheelei from this page:
Code:
https://github.com/AndroidRoot/androidroot.github.io/tree/master/download
and download some bad blob.bin or my blank blob.bin
Reboot your device and connect to your pc. Check if is this on apx mode with command “lsusb”.
With sudo run “./wheelie --blob blob.bin ”
You get cpu id and 0x4 error (bad blob format).
Format cpu id for grouper is like this 0x15d4a5f202c0401
Chip id is 015d4a5f202c0401.
Tegra Id from dump-sbk-via-usb is cpu id, but on bad format. 01042c205f4a5d01 vs 015d4a5f202c0401.
I have another Tegra3 device: How build blob?
Try my precompiled mknvfblob. Download from :
Code:
https://github.com/GeorgeMato4/nvcrypttools/tree/forN7/precompiled
precompiledN7 is for Nexus,
precompiledCardhu is for other device.
Type:
mkdir /AndroidRoot
cat /proc/cpuinfo > /AndroidRoot/cpuinfo
Cpuinfo file look like this:
Code:
Processor : ARMv7 Processor rev 9 (v7l)
processor : 0
BogoMIPS : 1993.93
processor : 1
BogoMIPS : 1993.93
processor : 2
BogoMIPS : 1993.93
processor : 3
BogoMIPS : 1993.93
Features : swp half thumb fastmult vfp edsp neon vfpv3 tls
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 9
Hardware : grouper
Revision : 0000
Serial : 015d4a5f202c0401
Where Hardware is type of chip-set, can be grouper (for Nexus 7 2012) or cardhu (for TF 201/300/700) and serial is chip id. Change this number with your chip id.
Now, untar my precompilated mknvfblob.
From
Code:
https://github.com/GeorgeMato4/nvcrypttools/tree/forN7/bct
download btc file for your device
Code:
https://github.com/GeorgeMato4/nvcrypttools/tree/forN7/bootloaders
download bootloader.xbt for your device
and take this files to AndroidRoot folder.
If you have on your device working linux, type :
./mknvfblob -W -K e57de3bab6cb499d874d5772cb219f01 --blob /AndroidRoot/test.blob --bctin /AndroidRoot/testa.bct --bctr /AndroidRoot/testr.bct --bctc /AndroidRoot/testc.bct --blin /AndroidRoot/bootloader.blob.XBT --blout /AndroidRoot/test.ebt
Where: e57de3bab6cb499d874d5772cb219f01 is your bsk
testa.bct is your bct.
bootloader.blob.XBT is your bootloader bct.
If you have android, use adb shell command.
how this work?
When you use blob.bin (test.blob) with “./wheelie --blob blob.bin ”
You get error 3 reciever.
But this is not problem.
Run command with sudo:
./nvflash --btc testr.bct --ebt test.ebt --blob test.blob --go
after run this, restore bootloader.
./nvflash --resrore --download 4 bootloader.img --go
Where number 4 is partition with bootloader and bootloadr.img is bootloader for your device.
Helppp, im keep getting this problem
log:
Code:
Traceback (most recent call last):
File "./fusee-launcher.py", line 692, in <module>
pid=arguments.pid, os_override=arguments.platform, override_checks=arguments.skip_checks)
File "./fusee-launcher.py", line 490, in __init__
self.dev = self._find_device(vid, pid)
File "./fusee-launcher.py", line 526, in _find_device
return self.backend.find_device(vid, pid)
File "./fusee-launcher.py", line 156, in find_device
import usb
ImportError: No module named 'usb'
edit: nvm fix it
when i do "lsusb" it show nothing, help!
edit: nvm fix this too
enderzip said:
when i do "lsusb" it show nothing, help!
Click to expand...
Click to collapse
lsusb show command not found ?
Then try command sudo apt-get install usbutils
and try lsusb again
or
Nvidia Corp is not in list ?
Then you not start on apx mode.
power button + volume up.
or
Do you install pyusb with command : pip install pyusb ?
try use command: pip3 install pyusb.
Jirmd said:
lsusb show command not found ?
Then try command sudo apt-get install usbutils
and try lsusb again
or
Nvidia Corp is not in list ?
Then you not start on apx mode.
power button + volume up.
or
Do you install pyusb with command : pip install pyusb ?
try use command: pip3 install pyusb.
Click to expand...
Click to collapse
"pip3 install pyusb" didnt work. This is all it show:
Code:
fusee-launcher-n7$: lsusb
fusee-launcher-n7$:
What OS are you using to unbrick Tegra 3? Linux or Windows?
edit: fix it
ok after spending a day trying to dump sbk, i finnaly did it.
First, you need to have ubuntu. WINDOWS WILL NOT WORK. Make a bootable ubuntu usb and live boot it or install it
Second, open temernial inside of the fusee-launcher-n7 folder
Thirdly, type: sudo apt-get install python-usb python3-usb. If it say cant locate package, open Software and Update and check the 4 first box
Lastly, type: pip install pyusb
After that, type: sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin and you are good to go
enderzip said:
ok after spending a day trying to dump sbk, i finnaly did it.
First, you need to have ubuntu. WINDOWS WILL NOT WORK. Make a bootable ubuntu usb and live boot it or install it
Second, open temernial inside of the fusee-launcher-n7 folder
Thirdly, type: sudo apt-get install python-usb python3-usb. If it say cant locate package, open Software and Update and check the 4 first box
Lastly, type: pip install pyusb
After that, type: sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin and you are good to go
Click to expand...
Click to collapse
Im so sorry, I forget to write this first. I use debian based os more than 10 years. I forgot then exist something like windows.
I will edit my first post.
im not getting error 3 receiver in nvflash it just stuck at sending file 100%
but my nexus 7 display a GOOGLE LOGO!!! with the "battery is too low" text on the upper left corner
idk what to do next
am i suppose to use the ./nvflash.exe command instead of the wheelie.exe one?
your guide is so confuse
---------- Post added at 04:38 AM ---------- Previous post was at 04:25 AM ----------
now im stuck on "waiting for bootloader to initialize" after the ./nvflash --bct command
Code:
[email protected]:/mnt/c/Users/EnderZip/Desktop/Nexus 7 recovery stuffs/ehr$ sudo ./nvflash.exe --bct testr.bct -
-bl test.ebt --blob test.blob --go
[sudo] password for enderzip:
Nvflash v1.13.87205 started
Using blob v1.13.00000ommon½╣·┌√¬
chip uid from BR is: 0x0000000000000000015d2bc2ad43f602
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d2bc2ad43f602
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 1
device config fuse: 17
sdram config strap: 1
downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
sending file: test.ebt
- 2146896/2146896 bytes sent
test.ebt sent successfully
waiting for bootloader to initialize
I write something about error 3 on wheelie, for people, who want start nvflash sessions with wheelie (like nvflash preloader) . This mean for people who know quide for wheelie and nvflash from AndroidRoot team. But how i see, it is not real good idea. If you want, write your own nvflash guide.
Jirmd said:
I write something about error 3 on wheelie, for people, who want start nvflash sessions with wheelie (like nvflash preloader) . This mean for people who know quide for wheelie and nvflash from AndroidRoot team. But how i see, it is not real good idea. If you want, write your own nvflash guide.
Click to expand...
Click to collapse
what? so im meant to get that error 3?
Hello @Jirmd I have an issue with your post...it is very well explained but i cannot create the blob.bin for my 32Gb Nexus 7 , because i do not have a working tegra to get the cat/proc/cpu info and i cannot run the mknvfblob command it gives me and error that cannot execute, maybe because i am missing some files. Like the test.blob testa.blob testr.blob If I paste you the sbk and CPU ID will you please create a blob for my N7?
Found a Tegra with Device ID: b'1710282806495d01'
Hello World
b'87e2b3998fc0483c86931785736d7cbe17102828'
SBK 87e2b3998fc0483c86931785736d7cbe
CHIP ID 015d490628281017
Paste you this completely so i make sure it is correct.
Many Thanks
in list Nvidia corp.
Run Command on
sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin
Invalid payload path specified!
help me...
Enplat said:
in list Nvidia corp.
Run Command on
sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin
Invalid payload path specified!
help me...
Click to expand...
Click to collapse
You need to download the COMPLETE fusee launcher from github. Install python 3 via adb. Run the make command. Then install the pip command thingy. And run the command sudo ./fusee...bla...bla from the folder where fusee is located on your system.
The_Pacifier said:
You need to download the COMPLETE fusee launcher from github. Install python 3 via adb. Run the make command. Then install the pip command thingy. And run the command sudo ./fusee...bla...bla from the folder where fusee is located on your system.
Click to expand...
Click to collapse
Code:
[email protected]:~/Downloads/fusee-launcher-n7$ sudo apt-get install python-usb python3-usb
[sudo] password for enplat:
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-usb is already the newest version (1.0.0-1).
python3-usb is already the newest version (1.0.0-1).
0 to upgrade, 0 to newly install, 0 to remove and 42 not to upgrade.
[email protected]:~/Downloads/fusee-launcher-n7$ pip install pyusb
Collecting pyusb
Installing collected packages: pyusb
Successfully installed pyusb-1.0.2
[email protected]:~/Downloads/fusee-launcher-n7$ lsusb
Bus 001 Device 004: ID 058f:6361 Alcor Micro Corp. Multimedia Card Reader
Bus 001 Device 003: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0a5f:0157 Zebra
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 004: ID 04b4:0510 Cypress Semiconductor Corp.
Bus 004 Device 019: ID 0955:7330 NVidia Corp.
Bus 004 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 004 Device 002: ID 04a9:2737 Canon, Inc. MF4410
Bus 004 Device 012: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 004 Device 008: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
Bus 004 Device 011: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 004 Device 009: ID 1516:8628 CompUSA Pen Drive
Bus 004 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/Downloads/fusee-launcher-n7$ sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin
Invalid payload path specified!
[email protected]:~/Downloads/fusee-launcher-n7$
I already did it.....
Enplat said:
Code:
[email protected]:~/Downloads/fusee-launcher-n7$ sudo apt-get install python-usb python3-usb
[sudo] password for enplat:
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-usb is already the newest version (1.0.0-1).
python3-usb is already the newest version (1.0.0-1).
0 to upgrade, 0 to newly install, 0 to remove and 42 not to upgrade.
[email protected]:~/Downloads/fusee-launcher-n7$ pip install pyusb
Collecting pyusb
Installing collected packages: pyusb
Successfully installed pyusb-1.0.2
[email protected]:~/Downloads/fusee-launcher-n7$ lsusb
Bus 001 Device 004: ID 058f:6361 Alcor Micro Corp. Multimedia Card Reader
Bus 001 Device 003: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0a5f:0157 Zebra
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 004: ID 04b4:0510 Cypress Semiconductor Corp.
Bus 004 Device 019: ID 0955:7330 NVidia Corp.
Bus 004 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 004 Device 002: ID 04a9:2737 Canon, Inc. MF4410
Bus 004 Device 012: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 004 Device 008: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C
Bus 004 Device 011: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 004 Device 009: ID 1516:8628 CompUSA Pen Drive
Bus 004 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected]:~/Downloads/fusee-launcher-n7$ sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin
Invalid payload path specified!
[email protected]:~/Downloads/fusee-launcher-n7$
I already did it.....
Click to expand...
Click to collapse
[email protected]:/mnt/c/Users/EnderZip/Desktop/nexus 7 stuff lol/Nexus 7 recovery stuffs/fusee-launcher-n7/fusee-launcher-n7$ sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin
2020-04-11 16:44:07,350 INFO:usb.core:find(): using backend "usb.backend.libusb1"
No TegraRCM device found?
Click to expand...
Click to collapse
check for the dump-sbk-via-usb.bin file inside of your fusee-launcher folder
if there is no dump-sbk-via-usb.bin file inside of your folder, open a terminal inside of that folder then type: make
after done that type : pip install pyusb
then: sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin
and that might gonna solve your problem
I was going to say the same as Enderzip, i do not see the make command. You just need to type make in the fusee folder just the word make alone. Be sure you download ALL the folder from github, by just hitting the green Download button.
I am really sorry.
1. On GitHub, I downloaded it and extracted it. (by just hitting the green Download button)
2. I ran the terminal from that folder and entered the make command
[email protected]:~/Downloads/fusee-launcher-n7$ make
arm-none-eabi-gcc -mtune=arm7tdmi -mlittle-endian -fno-stack-protector -fno-common -fno-builtin -ffreestanding -std=gnu99 -Werror -Wall -Wno-error=unused-function -fomit-frame-pointer -g -Os -DENTRY_POINT_ADDRESS=0x4000A000 intermezzo.S -c -o intermezzo.o
make: arm-none-eabi-gcc: Command not found
Makefile:38: recipe for target 'intermezzo.o' failed
make: *** [intermezzo.o] Error 127
Am I doing something wrong?
I say thank you.....
Enplat said:
I am really sorry.
1. On GitHub, I downloaded it and extracted it. (by just hitting the green Download button)
2. I ran the terminal from that folder and entered the make command
[email protected]:~/Downloads/fusee-launcher-n7$ make
arm-none-eabi-gcc -mtune=arm7tdmi -mlittle-endian -fno-stack-protector -fno-common -fno-builtin -ffreestanding -std=gnu99 -Werror -Wall -Wno-error=unused-function -fomit-frame-pointer -g -Os -DENTRY_POINT_ADDRESS=0x4000A000 intermezzo.S -c -o intermezzo.o
make: arm-none-eabi-gcc: Command not found
Makefile:38: recipe for target 'intermezzo.o' failed
make: *** [intermezzo.o] Error 127
Am I doing something wrong?
I say thank you.....
Click to expand...
Click to collapse
Try my already maked fusee-launcher
You may have to install pip using: pip install pyusb
enderzip said:
Try my already maked fusee-launcher
You may have to install pip using: pip install pyusb
Click to expand...
Click to collapse
thank you enderzip. im back from hospital now. so, i will solve your request for encrypted blob. please, send me your email address on pm. enderzip will write new tutorial for unbrick.