Output.
Code:
# cat cpuinfo
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 : 15d49065530121b
# ./mknvfblob -W -K f9eedc62fffa476f885650f7e5befa2d --blob test.blob --bctin n7.bct --bctr testr.bct --bctc testc.bct --blin bootloader.grouper.XBT --blout test.ebt
mknvfblob
---------
Encrypting BL 'bootloader.grouper.XBT' to 'test.ebt'...done.
Generating encrypted recovery BCT from 'n7.bct' to 'testr.bct'...done.
Generating encrypted create BCT from 'n7.bct' to 'testc.bct'...done.
Generating blob file 'test.blob'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.I'm unsure. I only have grouper. Read through this thread and others that are "bricked" related to see if it's possible.
Output.
Code:
# cat /AndroidRoot/cpuinfo
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 : 15d3f19194c0004
# ./mknvfblob -W -K af207fe108734b6099b474834a13832a --blob test.blob --bctin n7.bct --bctr testr.bct --bctc testc.bct --blin bootloader.grouper.XBT --blout test.ebt
mknvfblob
---------
Encrypting BL 'bootloader.grouper.XBT' to 'test.ebt'...done.
Generating encrypted recovery BCT from 'n7.bct' to 'testr.bct'...done.
Generating encrypted create BCT from 'n7.bct' to 'testc.bct'...done.
Generating blob file 'test.blob'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.Output.
Code:
# cat /AndroidRoot/cpuinfo
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 : 15d483bf2180208
# ./mknvfblob -W -K dc63cfe3e1bb4b54831ef85a7e56c38c --blob test.blob --bctin n7.bct --bctr testr.bct --bctc testc.bct --blin bootloader.grouper.XBT --blout test.ebt
mknvfblob
---------
Encrypting BL 'bootloader.grouper.XBT' to 'test.ebt'...done.
Generating encrypted recovery BCT from 'n7.bct' to 'testr.bct'...done.
Generating encrypted create BCT from 'n7.bct' to 'testc.bct'...done.
Generating blob file 'test.blob'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.ok, very big thanks..
say, tell me what I'm doing wrong... perdistory - the tablet passed out and went into an eternal reboot, stood in the docking station for 9 years.
sudo ./nvflash --setbct --create --configfile flash32.cfg --bl test.ebt --bct testr.bct --blob test.blob --go
lsusb
sudo ./nvflash --resume --download 7 twrp-3.5.2_9-0-tilapia.img --go
lsusb
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.23.img - on this the tablet freezes, whatever I do. Open belly robot -) is present.
I have been dealing with this for more than a month now. I think the memory is out of order.
Привет из России ) Hi from Russia.
say, tell me what I'm doing wrong... perdistory - the tablet passed out and went into an eternal reboot, stood in the docking station for 9 years.
sudo ./nvflash --setbct --create --configfile flash32.cfg --bl test.ebt --bct testr.bct --blob test.blob --go
lsusb
sudo ./nvflash --resume --download 7 twrp-3.5.2_9-0-tilapia.img --go
lsusb
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-tilapia-4.23.img - on this the tablet freezes, whatever I do. Open belly robot -) is present.
I have been dealing with this for more than a month now. I think the memory is out of order.
Привет из России ) Hi from Russia.
Output.
Code:
# cat /AndroidRoot/cpuinfo
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 : 015d4b3406200805
# ./mknvfblob -W -K 39fb823c2b97400e88f0a711146c9ba0 --blob test.blob --bctin n7.bct --bctr testr.bct --bctc testc.bct --blin bootloader.grouper.XBT --blout test.ebt
mknvfblob
---------
Encrypting BL 'bootloader.grouper.XBT' to 'test.ebt'...done.
Generating encrypted recovery BCT from 'n7.bct' to 'testr.bct'...done.
Generating encrypted create BCT from 'n7.bct' to 'testc.bct'...done.
Generating blob file 'test.blob'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.
Hello
I would be very grateful for your help
b'68656c6c6f2c20776f726c640a00'
hello, world
68656c6c6f2c20776f72
[=] Chip UID: 0x15d262e56101c14
Thanks a lot!
I would be very grateful for your help
b'68656c6c6f2c20776f726c640a00'
hello, world
68656c6c6f2c20776f72
[=] Chip UID: 0x15d262e56101c14
Thanks a lot!
I'm fairly sure you did the above incorrectly because what's left is nearly not long enough. The string we want is AFTER hello world. See post #1 again.
Very sorry, you are completely correct
hello, world
b'6539722e9fb2410b94f12a3e84a0f4c7141c1056'
6539722e9fb2410b94f12a3e84a0f4c7
[=] Chip UID: 0x15d262e56101c14
Thanks again!
hello, world
b'6539722e9fb2410b94f12a3e84a0f4c7141c1056'
6539722e9fb2410b94f12a3e84a0f4c7
[=] Chip UID: 0x15d262e56101c14
Thanks again!
Output.
Code:
# cat /AndroidRoot/cpuinfo
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 : 15d262e56101c14
# ./mknvfblob -W -K 6539722e9fb2410b94f12a3e84a0f4c7 --blob test.blob --bctin n7.bct --bctr testr.bct --bctc testc.bct --blin bootloader.grouper.XBT --blout test.ebt
mknvfblob
---------
Encrypting BL 'bootloader.grouper.XBT' to 'test.ebt'...done.
Generating encrypted recovery BCT from 'n7.bct' to 'testr.bct'...done.
Generating encrypted create BCT from 'n7.bct' to 'testc.bct'...done.
Generating blob file 'test.blob'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.Hi, my friend ask me for help with bricked Nexus 7.
Device sbk: d03a67d4662441b4ae62eba12f359b14
Chip UID: 0x15d456da347fe11
Many thanks for your help.
Device sbk: d03a67d4662441b4ae62eba12f359b14
Chip UID: 0x15d456da347fe11
Many thanks for your help.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
14Thanks to @Jirmd for letting me use his post as a reference.
Original post: https://xdaforums.com/nexus-7/general/unbrick-nexus-7-tegra-3-device-t4078627
Alternative Method:
1. https://github.com/tofurky/tegra30_debrick
2. https://xdaforums.com/t/tutorial-ge...-without-another-n7-or-tegra30-device.4305955
(Both methods do not require another Nexus 7)
Requirements:
1. Linux-based OS (I use Ubuntu 18.04)
2. NvFlash and Wheelie (You can download the Linux version down below)
3. A USB cable (A good and sturdy one)
4. Nerve of steel lol
5. Must have APX driver installed.
6. Another Nexus 7 (Ask someone that have it or ask me)(MUST BE ROOTED AND HAVE TWRP RECOVERY INSTALLED)
7. ADB (platform-tools)
1. DUMP SBK VIA USB
Step 1: Download fusee-launcher for Nexus 7 from this link and extract it to a folder:
http://www.mediafire.com/file/sgwsa79idk24z8u/fusee-launcher-n7.zip/file
Step 2: Open a terminal inside of the folder then type:
Wait for it to complete. After that, type:Code:sudo apt-get install python-usb python3-usb
Step 3: Connect your device to a USB 3.0 port (REQUIRED). You can check for connection using "lsusb". There must be a "NVidia Corp" in the list.Code:pip install pyusb
Step 4: Type:
Something like this should appear:Code:sudo ./fusee-launcher.py –tty dump-sbk-via-usb.bin
Search for the line "hello, world" inside of your log. It looks like this in this example: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' 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
The last 8 characters are not your SBK. This is the first 8 numbers of your Device ID. Delete this and delete the b' at the start and also the ' at the end.Code:hello, world b'e57de3bab6cb499d874d5772cb219f0101042c20'
The result should look like this:
Congratulation, you have successfully dump your device SBK via USB.Code:e57de3bab6cb499d874d5772cb219f01
2. GETTING YOUR CPU UID
Step 1: Download Wheelie and NvFlash then extract it to a folder.
Step 2: Download this broken blob.bin file (REQUIRE)
http://www.mediafire.com/file/32cxvjv2wajokqf/blob.bin/file
Then place it inside of the Wheelie and NvFlash folder.
Step 3: Open a terminal inside of the folder then type:
After that, something like this should appear:Code:./wheelie --blob blob.bin
Search for "Chip UID", remove the "0x" at the beginning. The result should look like this:Code:Wheelie 0.1 - Preflight for nvflash. Copyright (c) 2011-2012 androidroot.mobi ======================================== [=] Chip UID: 0x98254853062001158 [-] Incorrect SBK or SBK type selected. nverror: 0x4.
Congratulation, you got your chip UIDCode:98254853062001158
3. GENERATE BLOB FILES USING ANOTHER NEXUS 7
Step 1: Download MkNvfBlob from this link:
https://github.com/GeorgeMato4/nvcrypttools/blob/forN7/precompiled/precompiledN7.tar.xz
Note: Extract this to your Nexus 7.
Step 1.1: Reboot into TWRP recovery.
Step 2: Open a terminal inside of you ADB folder then type:
After that:Code:adb shell
Type this command after that:Code:su
Last one:Code:mkdir /AndroidRoot
Pull the cpuinfo file using this command:Code:cat /proc/cpuinfo > /AndroidRoot/cpuinfo
Note: You could copy your cpuinfo file to your PC using MTP (IDK how to do this so search Google lol)Code:adb pull /AndroidRoot
Open your ADB folder and there should be a AndroidRoot folder with a cpuinfo file inside of it.
Open cpuinfo using a Text Editor. Something like this should be inside:
Replace the Serial line with your Chip UID.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
After that, place the cpuinfo file back to the /AndroidRoot folder on your device using this command:
After you are done, don't close the ADB windows.Code:adb push AndroidRoot /
Step 3: Download bootloader.xbt:
https://github.com/GeorgeMato4/nvcrypttools/blob/forN7/bootloaders/bootloader.grouper.XBT
And BCT for your device:
https://github.com/GeorgeMato4/nvcrypttools/blob/forN7/bct/n7.bct
And copy these two files to the /AndroidRoot folder on your device.
Step 4: Type this command on the ADB windows:
After that, type:Code:cd /AndroidRoot
After that, type:Code:chmod 777 ./mknvfblob
Wait for it to do its job.Code:./mknvfblob -W -K <your SBK> --blob /AndroidRoot/test.blob --bctin /AndroidRoot/n7.bct --bctr /AndroidRoot/testr.bct --bctc /AndroidRoot/testc.bct --blin /AndroidRoot/bootloader.grouper.XBT --blout /AndroidRoot/test.ebt
After that, go to your /AndroidRoot folder and copy all the file that just got generated (testr.bct, testc.bct. test.ebt, test.blob) to your PC using the adb pull command on Step 2
Congratulation, you have successfully generate blob for your bricked device.
4. UNBRICK YOUR DEVICE (The fun part
)
Step 1: Boot your bricked device into APX mode either using Power button or Power + Vol UP.
Step 2: Open a terminal inside of the folder where you place your NvFlash folder (move the blob file inside of that folder, all of them)
Step 3: Open a terminal inside of your Wheelie and NvFlash folder. Type:
If you got this command:Code:sudo ./nvflash --bl test.ebt --bct testr.bct --blob test.blob
Then try this one instead:Code:command error: no command found
If you got the NvError, its fine.Code:./nvflash --setbct --create --configfile <your flash.cfg> --bl test.ebt --bct testr.bct --blob test.blob
Something like this should appear (the first command):
A Google Logo should appear on your device screen with the text "Battery is too low" on the upper left corner. Unplug the battery and replug it. After that, plug it into a wall charger for atleast 4 hour.Code:Nvflash v1.13.87205 started Using blob v1.13.00000 chip uid from BR is: 0x0000000000000000015d2bc285340e0f rcm version 0X30001 System Information: chip name: unknown chip id: 0x30 major: 1 minor: 3 chip sku: 0x83 chip uid: 0x0000000000000000015d2bc285340e0f 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: 0 sending file: recovery.bct - 6128/6128 bytes sent recovery.bct sent successfully downloading bootloader -- load address: 0x80108000 entry point: 0x80108000 sending file: bootloader.ebt - 2146912/2146912 bytes sent bootloader.ebt sent successfully waiting for bootloader to initialize bootloader downloaded successfully
Step 4: Unplug the battery and boot into APX mode again using the button combination.
Step 5: Type this command while holding down the Vol DOWN button:
Replace "boot.img" with your ROM boot.img file. If you download another boot.img that isn't for your ROM, your device will bootloop.Code:sudo ./nvflash --resume --download 8 boot.img
Step 6:
Type:
Replace "bootloader.img" with your bootloader.img file name (You could get it inside of the Factory Image)Code:sudo ./nvflash --resume --download 4 bootloader.img
And after its done, your device should technically unbrick now. But I still recommend you re-flash stock ROM.
Step 7: The final step
Boot into your OS using the command below:
If your device boot back into APX mode, maybe you have done something wrong. Try again.Code:sudo ./nvflash --resume --go
If you got a Google logo on your device then congratulation! Your device is now unbricked.
Note: If step 7 didn't work, try booting this recovery image using this command:
Link for the recovery image is in the "Links" section.Code:fastboot boot flatline_grouper.img
Note: To get into Fastboot, add the "--go" line at the end of the command in Step 5
HOLD DOWN VOL DOWN while doing this command, you should get into fastboot atCode:sudo ./nvflash --resume --download 8 boot.img --go
After you are in the Flatline recovery, navigate to the "Advanced" section using the VOL buttons. Select it using the POWER button.
Select the "wheelie" at the end of the list.
Select "I agree".
After that, select "Step 1: Flash AndroidRoot.mobi custom bootloader." IGNORE Step 2 because it won't gonna work anyways.
Your device should reboot and the Google logo should appear, that means that your device is unbricked.
Note: If you wanted to flash stock ROM, open the "image-*******.zip" inside of the factory image and open the android-info.txt file. Edit the "require-bootloader" line to "4.13". After that, it should work.
Links:
flash.cfg: http://www.mediafire.com/file/j90hc1dfz58aytq/flashcfg.zip/file
flatline_grouper.img: https://www.mediafire.com/file/z1jvgy6km33f7bf/flatline_grouper.img/file
Wheelie, NvFlash and platform-tools (For ADB) (Works for both Linux and Windows): https://www.mediafire.com/file/0nuy4indgvagq3v/nvflash-and-platformtool.zip/file
Download the Factory Image for your Nexus 7 incase you want to re-flash stock ROM (nakasi or nakasig): https://developers.google.com/android/images#nakasi
That is. If you need any help, message me.
Update: After a few days of troubleshooting, fixing and updating my post, it seems like the step to unbrick your Nexus 7 2012 may depends on how did you brick it, what OS version you are running or the condition of your device. So you may have to "think outside the box" sometimes in this guide.
Update #2: Some helpful advice from @Jirmd with some minor change:
In my case, this command also gives me the nverror 0x4 but it also did something to my Nexus 7 as it was required for the next step.
Update #3: Updated the guide and removed some unessacery steps.
Update #4: Updated.2Hi, enderzip...
I've been keeping track of the recent developments regarding bricked Nexus 7's, APX mode and nvFlash, here on XDA. There's currently quite a few threads on this topic.
As I understand it, you've been motivated by a desire to recover data from your bootloader bricked Nexus 7. So my question is simple...
'Have you been successful?'
Have you actually resurrected a bricked Nexus 7 with no functioning bootloader AND with no originally created flatline wheelie blobs?
If so, you have done what I thought could not be done! I tip my hat to you, with your tenacity and your technical understanding of the complex issues involved.
If I had a Linux system myself, I'd be half-minded to dig out my old Nexus 7, deliberately bugger up the bootloader, and follow your instructions for the sheer technical challenge!
--------------------------------------
Some general thoughts...
The Nexus 7 is old (c.2012), and likely not many people use it anymore, but that's not what's important here. What is important is the persistence, the huge technical ability, and the sheer bloody minded refusal ~ by some ~ to let their Nexus 7 die... to go into what the poet Dylan Thomas called that 'good night'...
"Do not go gentle into that good night,
Old age should burn and rave at close of day;
Rage, rage against the dying of the light."
https://poets.org/poem/do-not-go-gentle-good-night
And in so doing, mayhap enderzip and others, have provided potential clues for other devices, other hardware, other phones or tablets, when faced with similar hard brick problems. One can but hope.
The above post by enderzip is technically way beyond me, and I have no immediate use for it, but it's a fundamental distillation of everything XDA stands for - namely, experimentation and creativity.
It's basically, amazing!
Thanks enderzip
Rgrds,
Ged.2
Output.
Code:# cat cpuinfo 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 : 15d07874d3ff807 # ./mknvfblob -W -K 4b0ec989167f4beb996ff9d88bdc0022 --blob test.blob --bctin n7.bct --bctr testr.bct --bctc testc.bct --blin bootloader.grouper.XBT --blout test.ebt mknvfblob --------- Encrypting BL 'bootloader.grouper.XBT' to 'test.ebt'...done. Generating encrypted recovery BCT from 'n7.bct' to 'testr.bct'...done. Generating encrypted create BCT from 'n7.bct' to 'testc.bct'...done. Generating blob file 'test.blob'...done. Adding create BCT to blob file [wheelie]...done. Adding recovery BCT to blob file [wheelie]...done. Adding bootloader to blob file [wheelie]...done. Adding odmdata to blob file [wheelie]...done. Adding chip id to blob file [wheelie]...done.2It’s possible to do this trick on Windows. USB 3.0 is NOT required!
1. DUMP SBK VIA USB (Windows)
Step 1. Install the libusbK driver:
Download Zadig installer https://zadig.akeo.ie/
Connect your device to USB. You should see a device labeled "APX" in the Device Manager.
Open the Zadig executable. Select "APX" in the device dropdown list (you may have to enable "List All Devices" in the Options menu). Change the selected driver to libusbK using the arrow icons to the right of Zadig's window. Click "Install Driver" (or "Replace Driver").
Step 2. Install Python for Windows. If you have a 64-bit system, download "x86-64" installer from https://www.python.org/downloads/windows/
Step 3. Download fusee-launcher for Nexus 7 and extract it to a folder.
Replace fusee-launcher.py with the fixed file https://gist.githubusercontent.com/...d4ba1cf3d6232b545ba4c91aed0/fusee-launcher.py
Step 4. Reconnect your device (just in case).
Open a command prompt inside of the folder then type:
Find SBK key in the log (refer to the main tutorial).Code:python.exe fusee-launcher.py --tty dump-sbk-via-usb.bin
2. GETTING YOUR CPU UID (Windows)
Step 0. Replace APX driver:
Download and extract Universal Naked Driver https://xdaforums.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339
Open the Device Manager, uninstall the libusbK driver (APX device), then install the extracted one.
Step 1. ...
Tested on PC with USB 2.0 ports, Windows 7, Python 3.8.3, Zadig 2.5
But I don't have a second device.
Could someone generate the Blob file for me? Pretty please?
SBK: 3344ff475dce4fb19f0808c496dbc8eb
Chip UID: 015d8bed314c06031
Yes, I have successfully unbrick my Nexus 7 WITHOUT any type of blob file i have generated before.Hi, enderzip...
I've been keeping track of the recent developments regarding bricked Nexus 7's, APX mode and nvFlash, here on XDA. There's currently quite a few threads on this topic.
As I understand it, you've been motivated by a desire to recover data from your bootloader bricked Nexus 7. So my question is simple...
'Have you been successful?'
Have you actually resurrected a bricked Nexus 7 with no functioning bootloader AND with no originally created flatline wheelie blobs?
If so, you have done what I thought could not be done! I tip my hat to you, with your tenacity and your technical understanding of the complex issues involved.
If I had a Linux system myself, I'd be half-minded to dig out my old Nexus 7, deliberately bugger up the bootloader, and follow your instructions for the sheer technical challenge!
--------------------------------------
Some general thoughts...
The Nexus 7 is old (c.2012), and likely not many people use it anymore, but that's not what's important here. What is important is the persistence, the huge technical ability, and the sheer bloody minded refusal ~ by some ~ to let their Nexus 7 die... to go into what the poet Dylan Thomas called that 'good night'...
"Do not go gentle into that good night,
Old age should burn and rave at close of day;
Rage, rage against the dying of the light."
https://poets.org/poem/do-not-go-gentle-good-night
And in so doing, mayhap enderzip and others, have provided potential clues for other devices, other hardware, other phones or tablets, when faced with similar hard brick problems. One can but hope.
The above post by enderzip is technically way beyond me, and I have no immediate use for it, but it's a fundamental distillation of everything XDA stands for - namely, experimentation and creativity.
It's basically, amazing!
Thanks enderzip
Rgrds,
Ged.
And no, you should thank @Jirmd instead of me. If he didn't post his thread, my Nexus is still probably a paperweight.
