Database Info

Intel Android Devices Root / Temp Recovery Session

Intel Android Devices Root / Temp Recovery Session
social-design-concepts said:
Disclaimer:
Before you proceed to the rooting instructions below, please read this disclaimer:
XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You understand and agree that you are doing this at your own risk.
as for warranty the rule of thumb is if you root you should always consider your warranty voided : i will make no claim otherwise on the subject.
i am just a simple hobbyist from Cinti. OH USA i have no intention to buy devices or users getting mad that they were under some impression this wouldn't void the warranty.
if you root you should always consider your warranty voided
Click to expand...
Click to collapse
Tethered Temporary CWM / TWRP Recovery Session :
Note : This is a Temporary CWM / TWRP Recovery Session for some Intel Devices with locked bootloaders.
This recovery is not installed to the devices and has to be launched from a computer ( tethered ) each time you need to access the CWM / TWRP Recovery. . .
WARNING : This Temporary CWM / TWRP Recovery Session is for some Intel Devices with locked boot loaders.
It is not intended for installing custom roms as if the devices has a locked bootloader the device will fail to boot the unsigned images
Intel Fastboot Tethered Temporary Recovery Session Launcher download :
Current Version : IntelAndroid-FBRL-07-24-2015.7z
Generic Instructions for use better instructions coming later just wanted to get the thread up :
notes :
make sure you have downloaded and installed the adb / fastboot drivers for your device . . .
make sure you have enabled developer options / adb debugging under settings on your device . . .
make sure you have download the latest : UPDATE-SuperSU-vX.Xx.zip and place it on your internal or external_sd
1 : download and extract IntelAndroid-FBRL-07-24-2015.7z some where on your computer.
2 : double click the launcher.bat file to start , type " ACCEPT " case sensitive without quotes to continue
check that the tool is reporting as either :
DEVICE STATUS: ADB-ONLINE
DEVICE STATUS: FASTBOOT-ONLINE
If " DEVICE STATUS: UNKNOWN " please check your cable connection and driver installation under Windows Device Manager
If " DEVICE STATUS: UNAUTHORIZED " please check if your devices is displaying an authorization prompt be sure to check Always allow from this computer and then press ok
3 : select the trigger to launch the Temporary CWM Recovery Session support fastboot oem triggers are :
T1 oem startftm ( very few devices support this command , but its the original used so )
devices supported : coming soon
T2 oem backup_factory ( limited devices support this command )
devices supported : coming soon
T3 oem stop_partitioning ( should work on alot of kitkat builds )
devices supported : coming soon
T4 oem stop_partitioning ( probably works on all devices that are supported (Jellybean , KitKat , Lollipop) )
devices supported : coming soon
4 : after selecting the trigger your device should reboot in to fastboot and begin to copy files to your device
note : if your device hangs at the waiting-for-device screen and you see droidboot CMD Waiting on your devices double check that the fastboot driver installed correctly.
note : if you see unknown oem command the trigger isn't supported by your device.
5 : The temporary cwm recovery session should be started at this point select install zip from the recovery menu using vol up / vol down to navigate and power to select
6 : select install zip from sdcard / external_sd depending on where you placed the file and select the UPDATE-SuperSU-vX.Xx.zip you downloaded earlier
7 : confirm the installation
8 : after install completes reboot your device
note :
some devices have limited space under /system and the supersu app wont install
if you don't see the supersu app on your device attempt to install it from the playstore
more than likely the su binary installed correctly but there want enough room on the device for the app.
This recovery uses the CWM Recovery @vampirefo built for the Dell Venue 8 3830 NoModem original thread : Dell Venue 8, CWM, unsecure boot/recovery
You know it's annoying to find this on so many other forums. with other people taking credit for it. sad face : (
APPRECIATE MY WORK, I DON'T DRINK, SO CLICK HERE DONATE NOW AND BUY ME COFFEE
XDA:DevDB Information
Intel Android FBRL, Tool/Utility for the Android General
Contributors
social-design-concepts
Version Information
Status: Stable
Created 2015-07-28
Last Updated 2015-07-28

Supported Devices List / Trigger
Supported Devices List / Trigger
Acer :
B1-730 T2
B1-730HD T2
A1-830
A1-840FHD T3
A1-840 (HD) T3
Asus :
ME170C T2 & T3
ME176C T2 & T3
Dell :
Venue 7 3730 / Venue 8 3830 All Triggers Should Work
Venue 7 3740 / Venue 8 3840 T3
Venue 7 3741 / T3
Venue 8 7840 T3
Iview :
i700 T2 & T3
Kurio :
Xtreme 7 Only had a chance to test trigger T3
Odys :
intellitab 7
Nabi:
Dreamtab model IN08A trigger T3 reported working
Prestigio :
MultiPad Thunder 7.0i
Tesla :
L7 Tablet T3
Tesco :
Op3n Dott 8 T2 & T3
Toshibia :
Excite 7 T3

Links to devices specific threads / forums
Links to devices specific threads / forums
If you have created a devices specific thread / forum for your devices please PM the link so that i can post a link to it here to make it easier to help new users . . . . Please put Intel Device Specific Thread in the supject . Thank You .

The Concept / Source Code
The Concept / Source Code

Collected Device Dumps / Captured OTA Updates
Collected Device Dumps / Captured OTA Updates

Generic / Tips for Unbricking
Generic / Tips for Unbricking

Ahh!
Just my luck lol. Had a feeling I would end up bricked for some reason, maybe I jinxed myself.
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!

GeeKerGurL said:
Just my luck lol. Had a feeling I wouls end up beicked for some reason, maybe I jinxed myself.
Try to manually boot to droidboot
Anyways... everything was going ok, I selected trigger 3 to try first, reboots to droidboot (with "waiting for fastboot command") then I select recovery and get android dude laying down with a red exclamation point coming out his belly and it just said "no command" now I am soft bricked, only getting the USB symbal with the white line under it. Please help!
Click to expand...
Click to collapse
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app

social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?

GeeKerGurL said:
Yeah 3830. Thanks a bunch. Now what do I have to do to remote? I am on a win7 PC with 1gig that is so slow I wanna scream. Also I am in another timezone so how long would that be from now?
Click to expand...
Click to collapse
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app

social-design-concepts said:
1 hour 30 minutes
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Okie dokie. Ill be here.

social-design-concepts said:
We can remote around 1130pm est and I'll get you running v8 correct?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Woot!!!YA! no need, I got it back all by myself just had to boot with vol down and go back through the process and everything copied fine and worked this time! :good: thanks a ton for offering to help me though buddy!
BTW trigger 3 works for the 3830 V8 no modem
WOOOHOOOOHOOOOWOOOO! root check cleared, I am SOO happy to finally have root on this thing. Besides my minor hiccup for whatever reason this method was pie too! YAHOO. I went from about to cry to jumping around happy like a crazy person haha.

recovery fstab
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.

whgarner said:
What needs to be change for jb 4.2.2?
I am able to open and edit the file.
b.g.
Click to expand...
Click to collapse
recovery.fstab may or may not need to be edited for some devices especially if the device doesn't use by label partitioning. What device do you have?
Sent from my XT907 using XDA Free mobile app

asus aa3-600
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.

Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?

tomtom1265 said:
Hi, SDC
I know this has been ask before, I searched and couldn't find the answer though, I would like to get the source code for the launchers , I use the Linux version of this method, cause I don't have windows, and would like to convert the recovery.launcher triggers and so forth into a shell script rather that use binary file.
If you have a shell script already can you post it if not, can you post or give me a link to your binary files source code?
Click to expand...
Click to collapse
I'm going to post the source after I finish getting the thread put together I just wanted to get it up yesterday.
As for doing it through shell scripts the reason its binary is because if /system is mounted or any prebuilt binary has a dependency on a shared library it makes it extremely difficult some times impossible to stop services and unmount /system and such.
But I hope to have everything finish by the end of the day.
Sent from my XT907 using XDA Free mobile app

whgarner said:
I have an asus aa3-600-ur10
android 4.2.2
Intel Celeron J1850 Quad-core 2 GHz
21.5" Full HD (1920 x 1080) 16:9
Intel HD Graphics with Shared Memory
2 GB, DDR3 SDRAM
500 GB HDD
The problem I'm having is no usb debugging, only debugging via lan. I can get adb to work but not working with fastboot in the bootloader(droidboot). I have a post about it in this section, search for "aa3-600"
b.g.
Click to expand...
Click to collapse
You use Linux or windows? If Linux, you may need to use my fastboot binary, anyway if using Linux while in fastboot mode use terminal type lsusb.
Do you see your device listed?
Sent from my T1 using XDA Free mobile app

Root!
Thank you for this!
I successfully rooted my V8 3830 KK4.4 V1.33 no modem with T3 - in about 4 mins. tops.
FYI:
I connected and launched the launcher from the IntellAndroid-FBRL folder. Typed ACCEPT and got the green screen. Chose T3. The tablet rebooted into fastboot and files where loaded, But then fastboot turned red and said "device unauthorized" when CWM popped onto my tablet. (maybe it's suppose to do that, DK) and yes, US debugging was on, I flashed the SU zip, rebooted, all is well. SU updated and working fine. I was able to remove all the crapwear. :laugh:
thank you SDC!

Quick question - Do any of the intel devices have unlocked bootloader?? Thought I read somewhere somebody was able to install a factory 4.3 or 4.2 on a Dell venue and the bootloader unlocked?

[Completed] [Q] AT command to get Cell Information (CID,LAC,RSS,...)

Hi,
I'm new in this forum and I don't really know where to write this post. I would like to know if there is any AT command to obtain Reference cell information and Neighbour cell information, such as, +UCELLINFO in the ublox modules in the motorola.
Could I get somehow the information via AT command, extended Qualcomm or via other method? I alredy can execute commands.
Using AT+CCLAC I obtained the following results.
Code:
&C
&D
&E
&F
&S
&V
&W
E
I
L
M
Q
V
X
Z
T
P
\Q
\S
\V
%V
D
A
H
O
S0
S2
S3
S4
S5
S6
S7
S8
S9
S10
S11
S30
S103
S104
+FCLASS
+ICF
+IFC
+IPR
+GMI
+GMM
+GMR
+GCAP
+GSN
+DR
+DS
+CMEE
+WS46
+PACSP
+CFUN
+CLCC
+VZWMRUE
+VZWMRUC
+VZWAPNE
+VZWRSRP
+VZWRSRQ
+CNMPSD
+CBST
+CRLP
+CV120
+CHSN
+CSSN
+CREG
+CGREG
+CEREG
+CSCS
+CSTA
+CR
+CEER
+CRC
+CGDCONT
+CGDSCONT
+CGTFT
+CGEQREQ
+CGEQMIN
+CGEQOS
+CGCONTRDP
+CGSCONTRDP
+CGTFTRDP
+CGEQOSRDP
+CGQREQ
+CGQMIN
+CGEREP
+CGPADDR
+CGDATA
+CGCLASS
+CGPIAF
+CGSMS
+CSMS
+CMGF
+CSAS
+CRES
+CSCA
+CSMP
+CSDH
+CSCB
+FDD
+FAR
+FCL
+FIT
+ES
+ESA
+CMOD
+CEMODE
+CVHU
+CSQ
+CBC
+CPAS
+CPIN
+CMEC
+CIND
+CMER
+CGATT
+CGACT
+CGCMOD
+CPBS
+CPBR
+CPBF
+CPBW
+CPMS
+CNMI
+CMGL
+CMGR
+CMGS
+CMSS
+CMGW
+CMGD
+CMGC
+CNMA
+CMMS
+CHUP
+CCFC
+CCUG
+COPS
+CLCK
+CPWD
+CUSD
+CAOC
+CACM
+CAMM
+CPUC
+CCWA
+CHLD
+CIMI
+CGMI
+CGMM
+CGMR
+CGSN
+CNUM
+CSIM
+CRSM
+CCLK
+COPN
+CPOL
+CPLS
+CTZR
+CTZU
+CLAC
+CLIP
+COLP
+CDIP
+CTFR
+CLIR
+VTS
+ICCID
+CUAD
+CEAP
+CERP
+CSTF
+CSDF
+CEN
+CNMPSD
+CKPD
+CTSA
+CFUN
+CMAR
+CDIS
+CRSL
+CSO
+CSS
$QCSIMSTAT
$QCPBMPREF
$CREG
$CCLK
$QCCNMI
*CNTI
$QCCLR
$QCDMR
$QCDNSP
$QCDNSS
$QCTER
$QCSIMAPP
$QCPINSTAT
$QCPDPP
$QCPDPLT
$QCPWRDN
$QCDGEN
$QCPDPCFGE
$BREW
$QCANTE
$QCRPW
$QCSQ
$CSQ
$QCSYSMODE
$QCCTM
$QCBANDPREF
^PREFMODE
^SYSINFO
^SYSCONFIG
^CARDMODE
^DSCI
$QCVOLT
$QCHWREV
$QCBOOTVER
$QCDEFPROF
$QCMRUE
$QCMRUC
$QCAPNE
$QCPDPIMSCFGE
$QCCLAC
^SPN
$QCRMCALL
$QCDRX
$QCRSRP
$QCRSRQ
$QCACQDBC
$QCATMOD
$QCCOPS
^MODE

Updates [21/05/2015]:
In the attached file:
http://forum.xda-developers.com/attachment.php?attachmentid=3323307&stc=1&d=1432152310
+MCELL & +MCI are suitable for the needed task, but I'm not able to use the code before I reset the phone and the result of the commands was a 4 (no sense for me) and after the reboot an ERROR code appears.
Do I need to follow a certain command sequence or to active some concrete register??
I read about the AT+MODE=2 command to allow the execution of motorola extended commands. In my case this commands does not exist but AT^MODE is in the AT+CCLAC list. However, the unique possible values are (0-1) and I tried both and nothing happened with the +MCELL and +MCI commands and still return an ERROR code.
Thanks in advance.

jgoyao said:
Updates [21/05/2015]:
In the attached file:
http://forum.xda-developers.com/attachment.php?attachmentid=3323307&stc=1&d=1432152310
+MCELL & +MCI are suitable for the needed task, but I'm not able to use the code before I reset the phone and the result of the commands was a 4 (no sense for me) and after the reboot an ERROR code appears.
Do I need to follow a certain command sequence or to active some concrete register??
I read about the AT+MODE=2 command to allow the execution of motorola extended commands. In my case this commands does not exist but AT^MODE is in the AT+CCLAC list. However, the unique possible values are (0-1) and I tried both and nothing happened with the +MCELL and +MCI commands and still return an ERROR code.
Thanks in advance.
Click to expand...
Click to collapse
Could you provide some additional info?
Program you are using?
Device you are connecting to? Is it a MOTO G 4G LTE 1st Gen?
have you see this thread?
[A][SGS2][Serial] How to talk to the Modem with AT commands by E:V:A

TWRP 2.8.7.0

TWRP from 4pda.ru http://4pda.ru/forum/index.php?showtopic=651024&view=findpost&p=41082834
developers:
https://github.com/vm03
https://github.com/zombah
features:
backup EFS (IMEI code)
backup persist (bt and wifi mac address).
repo
https://github.com/cm-nokia-x2
compiled TWRP
https://yadi.sk/d/so1LALyUhUrSc
mirror from me on Google Disk https://drive.google.com/folderview...p1NkRTcDc0OEtwZkhTMEN0cm5XSVljNnc&usp=sharing

Hey buddy...i know it can be flashed through fastboot but i don't know the procedure...will you plz help me flashing this?

Use Advanced Nokia X2 Tool
Sent from my NokiaX2DS using XDA Free mobile app

Advanced Nokia X2 Tool is closed source program. I NOT recommend use Advanced Nokia X2 Tool.
For install TWRP you must:
1. install drivers for Nokia X2 from Microsoft official site (They will install with http://www.microsoft.com/ru-ru/mobile/support/faq/?action=singleTopic&topic=FA142987 or you may install separately http://forum.xda-developers.com/nokia-x2/general/direct-links-lumia-software-recovery-t3051923)
2. get adb util from Android SDK (install adb through manager and use searching by folders "adb") https://developer.android.com/sdk/index.html
2.1 Hot keys: Win + R
2.2
Code:
cmd
End press Enter key
2.3 Then change dir to adb folder
Code:
d:
chdir d:\blabla\
(i mean adb.exe must be in folder "blabla", for example)
3. turn off phone
press Volume Down + Power button 10 seconds (fastboot mode for Nokia X2)
connect usb cable
4. use command for installation
Code:
fastboot -i 0x0421 flash recovery twrp-2.8.7.0-20150625-ara.img
-i 0x0421 it's Nokia X2 product code for adb configuration.
in old archived page http://web.archive.org/web/20141002...ary/nokia-x/getting-started/device-setup.html
or on new page http://developers.apps.opera.com/nokia-x/getting-started

Did you think why it is closed source?
Sent from my NokiaX2DS using XDA Free mobile app

symbuzzer said:
Did you think why it is closed source?
Click to expand...
Click to collapse
Did you have link on source code on GitHub with open source license?

I meant did you know why it is closed source?
- It has 3rd party commercial and illegal feature like creating Qualcomm radio configuration file.
- It has a lot of additional 3rd party closed-source binaries which it's creators don't want to leaks it's command parameters.
- This app isn't freeware, it is donationware. So it is a commercial app.
- It isn't included any open source binary (except recoveries)
- Finally on XDA, there are a lot of code stealers.
So why should I do this tool open source?
I wrote nearly 1200 lines code, I add clickable bat feature which there isn't any app like this on XDA, I spent days to enhance it.
Please make emphaty with me.
Sent from my NokiaX2DS using XDA Free mobile app

This tool just send commands to adb util. I am sure this tool just execute command like
Code:
fastboot -i 0x0421 flash recovery twrp-2.8.7.0-20150625-ara.img
or
Code:
install <path-to-apk>
or use super user for special actions
Code:
su <my-super-user-command>
etc http://developer.android.com/tools/help/adb.html#commandsummary
or just deletes "bad" .apk
I mean it's program just use TWRP or CWM from another real developers and adb. That program very simple for yours closed source reason.
Maybe (de)odexing it's important for someone but exists another most open ways for that .
I would remind you; smartphone it's very personal and important thing (contacts, emails, passwords) for using closed source programs for modify firmware without code review. (i mean Google Play Market review .apk code and I have some confidence
big companies have a risk if they use "bad" functions in programs (like send statistic). Yes, in spite of this, they collect static, but they very restricted.
I don't know what yours (or another) program doing with my smartphone. And i don't want use reverse engineering for that.

Hahaha Only these commands ha?
It can modify imei too did you know?
Is there any program to create Qualcomm Configuration File with IMEI do you know?
This is most powerful tool for Nokia X2. If you want to secure your phone, I recommend to don't install Twrp which is based on insecured kernel.
If you don't trust my tool, please don't use only. If you want to nobody doesn't use it, you should find and share it's vulnerabilities.
And I repeat again, please don't use my tool.
If I can find your phone's specific data eg imei, imsi, mac address, I will add next version of my tool that brick-bootloader trap for your device which is only fixed with jtag .
Sent from my NokiaX2DS using XDA Free mobile app

"this program uses real developers things"
Really? I prefer that because it is simple and safe. I could flash "my" insecured kernel and perform these actions too. But I didn't prefer this method due security issues.
Next update (v3.00); I add perform all commands directly on phone not via any recovery. So no need to "real developer's things" anymore.
Maybe you will respect my work.
Signature:
Symbuzzer
Fake Developer
Sent from my NokiaX2DS using XDA Free mobile app

You can falsh this File....Via rocovery..
It will flash the new Twrp..

Take take it seriously bro ! Ignore him !
Sent from my NokiaX2DS using XDA Free mobile app

[Kernel][Nethunter][Testing][Want Help][CM-14.1][Monitor Mode]Nexmon

So,I was packing up my stuff in my house to move to Hostel when I found a network adapter.In the past I owned one for my Kali Pentesting.Then I gave it up for Exams and never saw it again.Now I had free time and wanted to mess with the college hostel's WiFi.But due to the rules I am not allowed to bring in any "Level 3" devices such as Laptops PC's.All had to be done on a Mobile which should be cheap and When the time comes disposed of easily.I tried buying a Nexus 5 devices but couldn't find in my price range (50$).So instead I bought the Note 3(Great Success)Now all I needed was a Patched kernel.I was going to build one using the cm-14.1 official sources.But while I was searching for solution I found Nexmon.I tried the firmware for bcm4339 using the app on /system/etc/WiFi/bcmdhd_sta.bin and entered the command su and nexutil -m2 and after that LD_PRELOAD=/system/lib/libfakeioctl.so airodump-ng wlan0 in the terminal whi and It worked(Greater Success)Now the I needed to run some tools which only worked in ChrootThis was no easy task.I again needed a Patched kernel.So,I followed the official guide to patch the kernel.I patched and built the kernel flashed it but found that my network adapter was obsolete.So,The only option remained was to use the Inner wireless card which supported injection and all the stuff(Not Natively).For the sake of research I Used Hijacker and used the setting for precommand as LD_PRELOAD=/system/lib/libfakeioctl.so and was able to capture/Decrypt/Crack Handshakes successfully against my own network.Now I am uploading here my compiled kernel with only one patch applied kernel.It's literally the cm kernel with only one patch.I need help in achieving 2 things.
1-Enable native monitor mode without LD_PRELOAD
2-Enable monitor mode internally in chrooted Kali.
Here is the boot.img just flash it and test it with external mode.
I will keep you updated on my Discovery in achieving the 2 above things.Any help would be welcomed.I should mention here that My profession isn't Computer related or any tech stuff.I am studying Medicine and Surgery along with a Speciality in Heart.So,You can't except me to do anything related to code.Again this is a testing build which I have tried on LOS14.1 and booted but couldn't verfiy the wlan1 status due to the fact That I don't currently have a wireless card.So,If you phone blew up,,Established communist empire,Robbed a bank,Tried to invade Russia,Attacked Samsung HQ or do anything I won't be responsible.
HERE'S THE LINK to the latest built nethunter(No chroor)cm13
https://drive.google.com/file/d/1IN1PQdq8Jk9UxOnH9G-gl1yk7X6ylHXr/view?usp=drivesdk

FIND 1
Cloned CM-14.1 repo
Cloned GCC 4.9 repo
Modified the build_kernel.sh for EUR(N9005)
Patched using:
wget http://patches.aircrack-ng.org/mac80211.compat08082009.wl_frag+ack_v1.patch
patch -p1 < mac80211.compat08082009.wl_frag+ack_v1.patch
Built using
sh build_kernel.sh
Success!
Made boot.img
Here's it :https://drive.google.com/file/d/1Hixwje3rSz4z9E6D7GuRhgItyJ3EsBW7/view?usp=drivesdk
FIND 2
Cloned Xenial Jairus's repo.
Built ralink,realtek and atheros capable devices.
Working
Log:3 androifilehost approved my request
This is xenial kernel by jairus with little chunks removed
Huge thanks to @Jairus980 for the amazing kernel
Here is the link1 https://www.androidfilehost.com/?w=files&flid=285679
I have ralink which works perfectly.Furthermore there is a folder named ZImages which contain and will contain All the zImages which I will ever create for this device.Just Dowoad android kitchen unpack lineageboot.img or the @Jairus980 kernel img and replace the zImages with mine.
Side note.Most of the kernel Images doesn't work.
Side Side Note:
The Note 3 is a dead device and the only reason I am working on it is the fact that I wanted to test some things before I tear apart my main device.
Side Side Side note
I will only be working on hlte aka hltexx aka hlteur aka N9005 aka The Samsung Galaxy Note 3 Internation Snapdragon Variant.
If you accidentally brick your phone,Blew it up,Damaged your PC,Blew Up your House,Established Communism or Invaded Russia for that Matter and Point finger at me I will laugh at you.Furthermore Black Holes,Accidently ending up solving the antilife equation or summoning a wish granting dragons are Issues I can help with.
Thanks XDA for teaching me stuff

Links added
Sent from my Pixel 3 XL using Tapatalk

Exynos BootROM exploit question

Hi all,
I see that unsigned "raw binary aarch64 executables" can be run using the recently developed tool here:
https://github.com/frederic/exynos-usbdl
My question is - does this open up the possibility to get a mainline u-boot.bin (and using that, mainline linux kernel) running on the Exynos S7? That would be exciting...
Thanks all,
Jack K

no, because it only bypasses FLASH signature checking, but exynos bootrom always checks on boot if it is oem signed bootloader or some other custom bootloader. mainline linux MAYBE could be possible for just one boot, because it will stay in memory of course, but don't think that there will be some super new and super cool technology that will allow to change bootrom, because that won't happen, bootrom is placed directly in cpu memory, only way to change bootrom is to change the cpu

On the contrary all you need is the bootROM as uboot. If you were to want the phone running on a linux environment you could always port a linux build into a gsi or create a multiboot script. Or even more crafier yet you could make an OTA with an alternate fstab?