yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] DawG^:
Thanks Yasmani, I'll try it out. I rolled back to 2.0.0 but I'll clear all data and download 2.1.0.

I just hate to bother you again for a new token, I hope you don't mind 🙈.

Thanks for your great work and keep supporting this app (which is a shame google has removed it from their store).
[Android Apps and Games] lassetth:
I made my payment via PP and forgot to give my mail, lars@theander.cc and system ID. Can you help? Thanks!
[Android Apps and Games] shankai:
is this app still working? if it's working which version?
[Android Apps and Games] yasmanillanes:
Yes, the app is still being supported. The latest version can be obtained from the app's website.
[OnePlus 7T Questions & Answers] adobrakic:
The camera on Snapchat is super zoomed in compared to normal. I searched on Google, and it seems to be because Snapchat uses video (instead of photo) camera and takes a screenshot of the viewfinder.

Is there a fix for this that we can implement? I don't mind rooting/Magisk/Xposed. I checked the working Magisk modules thread here, but found nothing related to Snapchat.

Thank you!
[OnePlus 7T Questions & Answers] DerDavid01:
The problem is, that Snapchat is using the fullscreen viewfinder (I think its 19.5 : 9) and in the camera app it 4:3.... thats the problem and sadly there are currrently (ever since) no fixes :(
[Nexus 7 General] enderzip:
Helppp, im keep getting this problem

log:

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
[Nexus 7 General] enderzip:
when i do "lsusb" it show nothing, help!

edit: nvm fix this too
[Nexus 7 General] Jirmd:
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.
[Nexus 7 General] enderzip:
"pip3 install pyusb" didnt work. This is all it show:

fusee-launcher-n7$: lsusb
fusee-launcher-n7$:

What OS are you using to unbrick Tegra 3? Linux or Windows?

edit: fix it
[Nexus 7 General] enderzip:
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
[Nexus 7 General] Jirmd:
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.
[Nexus 7 General] enderzip:
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
[Nexus 7 General] enderzip:
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

enderzip@DESKTOP-D7PCU13:/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
[Nexus 7 General] Jirmd:
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.
[Nexus 7 General] enderzip:
what? so im meant to get that error 3?
[Nexus 7 General] Diego_992:
Hello [MENTION=10406705]Jirmd[/MENTION] 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
[Nexus 7 General] Enplat:
in list Nvidia corp.

Run Command on

sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin

Invalid payload path specified!

help me...
[Nexus 7 General] Diego_992:
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.
[Nexus 7 General] Enplat:
enplat@enplat-System-Product-Name:~/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.
enplat@enplat-System-Product-Name:~/Downloads/fusee-launcher-n7$ pip install pyusb
Collecting pyusb
Installing collected packages: pyusb
Successfully installed pyusb-1.0.2
enplat@enplat-System-Product-Name:~/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
enplat@enplat-System-Product-Name:~/Downloads/fusee-launcher-n7$ sudo ./fusee-launcher.py --tty dump-sbk-via-usb.bin
Invalid payload path specified!
enplat@enplat-System-Product-Name:~/Downloads/fusee-launcher-n7$

I already did it.....
[Nexus 7 General] enderzip:
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
[Nexus 7 General] Diego_992:
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.
[Nexus 7 General] Enplat:
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

enplat@enplat-System-Product-Name:~/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.....
[Nexus 7 General] enderzip:
Try my already maked fusee-launcher

You may have to install pip using: pip install pyusb
[Nexus 7 General] Jirmd:
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.
[Nexus 7 General] steffenm82:
Hello, I'm a bit lost with this guide. I was able to get SBK and Chip ID (see below), but not to generate required blob, using my spare Nexus 7 device. Would some one be able to generate the blob file with below information, or guide into the right direction to generate the blob file myself using my spare Nexus 7 device?

SBK 53df4f7f69f641c9a3ffacf2a41937fa

CHIP ID 015d16897a500403

If I understood correct then commands below are used to flash created blob file to device...

Nvflash command --ebt is not known for nvflash. Is this a typo?

./nvflash --btc testr.bct --ebt test.ebt --blob test.blob --go

Nvflash command --resore is not known for nvflash. Is this a typo?

./nvflash --resrore --download 4 bootloader.img --go

Many Thanks in Advance Steffen

P.S.: [MENTION=10406705]Jirmd[/MENTION] I will send you my email via pm...
[Nexus 7 General] gormatrax:
I was able to obtain my SBK and my chip id but I sadly do not own any other Tegra devices. Would someone be as kind as to generate a blob file with the following info?

SBK: d2037f94caca4f249ad21d7f721957e4

CHIP ID: 015d25689b3c1019

Tegra device id (if necessary): 19103c9b68255d01

The device is an ASUS Nexus 7 2012 with 16GB memory.

I had this tablet through my whole childhood and I would love having it back. I wouldn't mind sending a couple bucks to anyone willing to make a blob for me.

Thanks a lot for this post, it brought me hope after seeing tons of articles saying that it is impossible to rewrite the bootloader from APX without blobs...
[Nexus 7 General] enderzip:
ok i will do that for you, send me your email.

---------- Post added at 02:41 AM ---------- Previous post was at 02:40 AM ----------

I can generate blob for you if you needed.
[Nexus 7 General] enderzip:
Here is you blob gormatrax.
[Nexus 7 General] enderzip:
Here is your blob gormatrax.

Edit: Somehow my reply got duplicate twice lol
[Nexus 7 General] steffenm82:
Just send you my email address. Thanks ? for your support :)
[Nexus 7 General] steffenm82:
Thanks for generating the blob files :)

Now I'm receiving the following error when trying to flash the device, the device is switching off automatically afterwards. Could you help me on this?

*Command: sudo ./nvflash --bct testr.bct --bl test.ebt --blob test.blob --go
Nvflash v1.13.87205 started
Using blob v1.13.00000
chip uid from BR is: 0x0000000000000000015d16897a500403
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d16897a500403
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 17
sdram config strap: 1

downloading bootloader -- load address: 0x80108000 entry point: 0x80108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
[Nexus 7 General] enderzip:
You need to reflash the partition first i think. Go see my tutorial for how to do that.

https://xdaforums.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-blob-bin-t4083879

The command to reflash partition is at Step 4 part 4
[Nexus 7 General] gormatrax:
Enderzip you are absolutely amazing. The blob works! Thank you so so much for this.
[Nexus 7 General] Enplat:
I'm really sorry, but can I ask you a favor, too?

sbk : 9c57bd03c653490b986aeccde5a520df

Chip UID: 0x15d32205f140600

device id : 0006145f

device is Nexus7 3G, Tilapia

Blob file is not generated.

please, help me.

Thank you,
[Nexus 7 General] enderzip:
Here is your blob Enplat.
[Nexus 7 General] Enplat:
enplat@enplat-System-Product-Name:~/Downloads/precompiledN7/precompiled$ ./nvflash --bct testr.bct --bl test.ebt --blob test.blob --go
Nvflash v1.13.87205 started
Using blob v1.13.00000
chip uid from BR is: 0x0000000000000000015d32205f140600
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d32205f140600
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
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
bootloader downloaded successfully
enplat@enplat-System-Product-Name:~/Downloads/precompiledN7/precompiled$ ./nvflash --resume --download 4 bootloader.img --go
Nvflash v1.13.87205 started
[resume mode]
sending file: bootloader.img

I waited an hour, but there was no reaction.

./nvflash --resume --download 4 bootloader.img --go

./nvflash --resume --download 8 boot.img --go

The same goes for this command.

help me....
[Nexus 7 General] enderzip:
Why did you send the bootloader.img? You have to send the boot.img first.

./nvflash --resume --download 8 boot.img --go

And also, hold down the Vol Down button before and after pressing Enter. Don't release it until the Fastboot screen appear on your screen.

If it stuck at sending boot.img then try another USB port or another USB cable

Also, it seems like you are using a Linux Subsystem on Windows instead of a full Linux like Ubuntu. Make a bootable Linux OS then live boot it on your PC.

Or maybe im just stupid :)

Try this with the Windows Command Prompt instead of Linux Terminal.
[Nexus 7 General] Enplat:
./nvflash --resume --download 8 boot.img --go
Nvflash v1.13.87205 started
[resume mode]
sending file: boot.img

I waited here for about an hour, but there was no response.

take out the cable, Below is what it says.

- 65536/5308416 bytes sentdata send failed NvError 0x8
command failure: partition download failed

Same message even if you wait for an hour.

Same message even if you wait ten minutes.

Two Ubuntu PC's are in use (live boot), and cables and ports are constantly changing.

What is the problem?.....
[Nexus 7 General] enderzip:
Try this on Windows instead.
[Nexus 7 General] Enplat:
PS O:\precompiledN7\precompiled> ./nvflash --setbct --create --configfile flash32.cfg --bl test.ebt --bct testr.bct --blob test.blob
Nvflash v1.13.87205 started
Using blob v1.13.00000 (x86>5艱
chip uid from BR is: 0x0000000000000000015d32205f140600
rcm version 0X30001
System Information:
chip name: unknown
chip id: 0x30 major: 1 minor: 3
chip sku: 0x83
chip uid: 0x0000000000000000015d32205f140600
macrovision: disabled
hdcp: enabled
jtag: disabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 17
sdram config strap: 1

sending file: testr.bct
- 6128/6128 bytes sent
testr.bct sent successfully
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
bootloader downloaded successfully
setting device: 0 18
failed executing command 11 NvError 0x120002
command failure: create failed (bad data)
bootloader status: specified device is invalid (code: 6) message: nverror:0x4 (0x4) flags: 0

PS O:\precompiledN7\precompiled> ./nvflash --resume --download 8 boot.img --go
Nvflash v1.13.87205 started
[resume mode]
sending file: boot.img
- 65536/5113856 bytes sent

No further progress is made here.

I think it's going to be hard...

Thank you...ㅠㅠ
[Nexus 7 General] enderzip:
Are you using Linux Subsystem or Command Prompt? I have never seen anyone stuck while sending the boot.img . Can you check the connection between your PC and your device? Maybe try a USB 3 or 2 port

Also try switching the port after a error or freeze.
[Nexus 7 General] aleks444:
Hello, help me please, I have no other Tegra devices,Would someone be as kind as to generate a blob file(sorry for my English)

SBK: f9558e0344224facbc6370fbaa9c43f4

Chip UID: 15d46d927201e11

I can not revive his second year

Thanks in advance!!!
[Nexus 7 General] enderzip:
Here is your blob files, aleks444.

Also, you don't have to post this in 2 different threads lol
[Nexus 7 General] aleks444:
Thank you !!!, sorry that twice...
[Nexus 7 General] willjames:
Thanks for all the amazing work everyone, particularly Jirmd and Enderzip!

Would someone be kind enough to generate me a blob, please?

SBK: 54344e30212e4faeb24a31faa4f56172

CHIP ID: 0f410a0001440200

Tegra device ID (if necessary): 04083c45824a5d01

ASUS Nexus 7 2012 with 16GB memory.

Really appreciate it - would never have been able to do anything other than paperweight the Nexus without it!
[Nexus 7 General] Saturation.mvp:
Hi,

Thanks for the great work (very apprecited).

If you may create a blob for me.

My device info are listed below:

sbk : f7afcf6fe1544a34834174aa2aa95b9d

tegra_id : 02f6379256285d01

chip_id : 0x15d28569237f602
[Nexus 7 General] enderzip:
Here is your blob.
[Nexus 7 General] perapiche:
Hi!

Can you generate my nexus blob's file please?

Sbk: 774ec65fb2c49fb922de7e8d0ba4b15

Chip UID: 015d3b65f964200e

Tegra Device ID: 0e2064f9653b5d01

ASUS Nexus 7 2012 32 Gb memory

Thank you in advance!
[Nexus 7 General] enderzip:
The SBK is missing a character.
[Nexus 7 General] perapiche:
b774ec65fb2c49fb922de7e8d0ba4b15
[Nexus 7 General] PopoyeSailor:
Chip ID can be found inside the tablet by removing the Back Cover.

Hi Everyone,

Additional Info:

Chip ID can be found inside the tablet on a sticker beside the power connector. The UUID on the sticker is your Chip ID:

Its really wonderful what everyone is trying to do here. Really appreciate it. Especially Jirmd & enderzip

Can somebody please create a blob file for me too.

My IDs are as follows:

Chip ID: 015d3c263328240d

SBK: 1cc907f73ab44e70ac6cf760282ab18e

My Gmail: popoyesailor913@gmail.com

Thanks in advance.

My Terminal Window Info:

-------------------------------------------------------------------------------------------------------------------------------------------------------

My Chip ID:

Waiting for device in APX mode...

[=] Chip UID: 0x15d3c263328240d

My SBK:

hello, world

b'1cc907f73ab44e70ac6cf760282ab18e0d242833'

--------------------------------------------------------------------------------------------------------------------------------------------------------
[Nexus 7 General] enderzip:
Sorry but I am busy all the time so maybe Thursday next week.
[Nexus 7 General] PopoyeSailor:
That`s ok. No hurries, no worries. I really appreciate what you are doing here. Please take your time.
[Nexus 7 General] enderzip:
Here is your blob
[Nexus 7 General] PopoyeSailor:
Hi enderzip,

Thank you so much.
[Nexus 7 General] Pedros97:
Generate blob please

Can somebody please create a blob file for me too.

My IDs are as follows:

Chip ID: 15d456da33c1215

SBK: 7e52658281164da19097567e634deade

Tegra id: 15123ca36d455d01

ASUS Nexus 7 2012 3g with 32 Gb memory

My Gmail: pedros279@gmail.com

Thanks in advance.
[Nexus 7 General] PopoyeSailor:
Hi enderzip,

Thank you so much for helping. My tablet is up and running.

These commands seem to have done the trick:

./nvflash --bct testr.bct --bl test.ebt --blob test.blob --go

After that, press and hold VOL-DOWN while executing the command below. Do not release until the command is finished. It'll only take a few seconds to finish. This should make it enter into Fastboot mode.

sudo ./nvflash --resume --download 8 boot.img --download 4 bootloader.img

If you notice the above code, I have sent both boot.img and bootloader.img in a single line. Sending those files separately one after the other didn't work for me.

The boot.img and bootloader.img are from factory stock rom.
[Nexus 7 General] perapiche:
thanks!

I was able to fix my equipment satisfactorily, thanks for your work and time!
[Nexus 7 General] enderzip:
Sorry for my late reply but im currently very busy so maybe tommorrow or Wednesday.
[Nexus 7 General] Pedros97:
Thank your very much , no worries. I really appreciate your work are doing here.

My nexus dead other 2 years[emoji1] .Another days or month its ok.
[Nexus 7 General] fxsheep:
[MENTION=10406705]Jirmd[/MENTION] Sorry for a bit off topic, but since you have ported the bootrom exploit to tegra30 and nexus7, can we extend it further, e.g. booting an open source bootloader like u-boot which supports the Nvidia Cardhu, or something like UEFI (Asus Vivotab RT shares similar specs) to boot into windows?

The biggest problem is that grouper doesn't have a known good way to access the UART without disassembling the device. I tried to chainload u-boot from stock bootloader, ending up dying at relocation, even if I did a relocate ahead. It's probably because the kernel loading address is not known. I also tried to boot UEFI but it dies after MMU is enabled, probably because my memory isn't mapped correctly.

Can you provide some hints, like serial debugging etc.?
[Nexus 7 General] fxsheep:
[MENTION=10406705]Jirmd[/MENTION]

A good news to everyone is that there is actually no need to have another Nexus7/t30 device at all.

jevinskie has already provided an nvaes-non-device.c which implements the same ability as nvaes on device (except software-based, without hardware acceleration, no fused keys availability).

So in order to generate the blobs w/o another N7, clone nvcrypttools, then vim/nano the Makefile:

there is a line starts with CROSS_COMPILE which is for cross-compiling to the device. Delete the arm-linux*** after it, so you'll get it compiled on PC.

Dont forget to apt install libmbedtls-dev ,as this one is for the non-device crypto.

Then type make.You'll still have some errors, but that doesn't matter.The mknvfblob has been compiled successfully. After this you can follow normal steps just on your PC instead of a real device.Optionally modify mknvfblob.c so that you can specify another cpuinfo file other than /AndroidRoot/cpuinfo .

The reason why we are required to use flatline and even a custom bootloader on the device to create the blob is that in early days the SBK cannot be dumped easily. But it's 2020 now and there's fusee-gelee to dump it from your device(and you have to if you bricked without creating a blob in advance) With the SBK, since the algorithm is well-known AES, it's not necessary to rely on the hardware engine, so there's no such "device required" rule.