The rooting may or may not be working. Trying to use casual to update my phone but I get he "Noob" error, when I try to update to their bootloader I get the sboot.bin fail. Not sure where to go with this, downloading the huge 1605VRLJB file but that shoudl not be the issue. Any ideas?
For use with Verizon Galaxy Note 2 ONLY! This CASUAL is designed to assist with unlock and provide other services to Verizon Galaxy Note 2 owners.
--Suck It Verizon--
This exploit was designed by Ralekdev, AdamOutler and Rebellos, it will work with I605VRALJB. For best results you should flash Revision by AdamOutler as a baseline before attempting this exploit. See XDA-Developers.com for more. Link: http://goo.gl/a1HMS
mkdir failed for /data/local/tmp, File exists
Pushing dependencies
Pushing su binary...
4727 KB/s (91980 bytes in 0.019s)Pushing SuperSU app...
5042 KB/s (996704 bytes in 0.193s)Pushing Exynos-Abuse exploit
4835 KB/s (64373 bytes in 0.013s)Pushing root script
176 KB/s (361 bytes in 0.002s)Pushing Busybox
4774 KB/s (1867568 bytes in 0.382s)Pushing viewmem
1763 KB/s (5417 bytes in 0.003s)Pushing raw exploit code
54 KB/s (56 bytes in 0.001s)Setting Permissions....
Executing Root Exploit.
[*] s_show->seq_printf format string found at: 0xC086C348
[*] sys_setresuid found at 0xC00967C4
[*] patching sys_setresuid at 0xC0096808
[!] set user root failed: Operation not permitted
Your device should be rooted. If you have upgraded past VRALJB firmware the exploit may not function properly.
CASUAL requires a reboot because we look at the memory logs after the device boots to verify proper bootloader version.
rebooting...
[x]Ready for exploit
[x]Found rooted device
[INFO] Reading 512 bytes at 0x40000200...
HellNo
IMPROPER BOOTLOADER VERSION DETECTED. FOLLOW DIRECTIONS NOOB! GUYS LIKE YOU ARE THE REASON DEVELOPERS HAVE SO MUCH PROBLEMS!!!!!! DO YOU REALIZE WHAT IT TAKES TO MAKE SOMETHING LIKE THIS COME TOGETHER?? AND HERE YOU ARE JUST TRYING TO SCREW THINGS UP.... DAMNIT! GET OFF THE INTERNET!
So uhhh....
Is there a question somewhere in there?
God bless the American people.
That looks like the old unlock process are you using the jail break method
Sent from my SGH-T889 using Tapatalk 2
kintwofan said:
That looks like the old unlock process are you using the jail break method
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Right now I have rooted based on the [GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II then tried to apply casual, which fails due to the incorrect bootloader. I am unable to restore a stock rom, and I can not change that ****ing bootloader. So right now I can not unlock with the casual method. I get that noob error. Anyway to fix this?
I'm trying the new method, assuming that is the post jan 26th post. One person recommended finding the alternative recovery with out sboot.bin. I have not found that yet, root66 seems to be the only one that is working.
Yeah I got crazy frustrated with this one. Here goes. So I booted into odin, which needed the kies driver is memory serves. Ran the Root66 in PDA. Then I rebooted my phone, went into the usb debugging and MTP for usb. Updated my phone, to VRALL4 like the normal OTA updates from VW. ran CASUAL-BackAtchaVerizon-Revision311b with java (build 1.7.0_17-b02). The damn thing went through. Not trying to run sboot.bin through odin. As far as the guides go, you need to click the generic serial to be replaced in casual. Also some guides didnt show what state the phone was in for casual. Just boot up the phone like normal. I'm trying to figure out what other snags i ran into...
casual gives error on stock rooted 4.1.1 android version
hi guys.
so i had android 4.3 and downgraded to stock rooted 4.1.1 with odin.
Root66 stock VRALJB 4.1.1 12/2/12 from this thread http://forum.xda-developers.com/showthread.php?t=2024207&nocache=1
the problem is that casual it gets stuck with this:
Uploading BOOTLOADER 100% ERROR: Failed to confirm end of file transfer sequence! ERROR: BOOTLOADER upload failed!
version used: NoYouVerizon-GalaxyNote2-CASUAL R515
tried to flash to this non rooted version with odin CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW_Rev0406_low_ship_user.tar, but fails after the start.
tried with 2 different usb cables and different usb ports but not working.
any idea guys.i need to unlock that bootloader to install a rom that has italian language for use in italy.i want to give this phone to my mom, but is from US locked.
any ideas guys?
update:
so with BackAtchaVerizon-CASUAL-Revision465b it works well till at almost at the end, says failed recovery and something and gets stuck.
-----NoYouVerizon-GalaxyNote2-CASUAL R515
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Uploading PIT
PIT upload successful
Uploading BOOTLOADER
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOTLOADER upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
[Heimdall Error Report] Detected:
Heimdall uncontinuable error; Script halted
[/Heimdall Error Report]
done
Script Complete
-----BackAtchaVerizon-CASUAL-Revision465b
Code:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading BOOT
100%
BOOT upload successful
Ending session...
Rebooting device...
Releasing device interface...
[Heimdall Success]
Your device should be rebooting into Android now.
waiting for ADB device connection...
mkdir failed for /data/local/tmp, File exists
Pushing dependencies
Pushing su binary...
5757 KB/s (91980 bytes in 0.015s)
Pushing SuperSU app...
4799 KB/s (996704 bytes in 0.202s)
Pushing Exynos-Abuse exploit
4029 KB/s (64373 bytes in 0.015s)
Pushing root script
0 KB/s (361 bytes in 1.000s)
Pushing Busybox
5083 KB/s (1867568 bytes in 0.358s)
Pushing viewmem
5 KB/s (5417 bytes in 1.000s)
Pushing pit
8 KB/s (8192 bytes in 1.000s)
Setting Permissions....
Executing Root Exploit.
[*] s_show->seq_printf format string found at: 0xC086C348
[*] sys_setresuid found at 0xC00967C4
[*] patching sys_setresuid at 0xC0096808
remounting system rw....
moving su into position
moving Superuser.apk into position
[x]Ready for exploit
Linux version 3.0.31-414933 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Sun Oct 28 13:34:23 KST 2012
[x]Found rooted device
[x]Device Verification Checks Complete
[x]Ready for exploit
Injecting Code
16+0 records in
16+0 records out
8192 bytes transferred in 0.002 secs (4096000 bytes/sec)
[x]Exploit Injection Done.
your device is now rebooting into a totally insecure download mode. Press the Volume Up buton when requested by Download Mode. You will then flash the Suck It Verizon bootloader located here: [url]http://d-h.st/DQG[/url]. Upon completion of this step, you will be rebooted into TWRP Recovery. CASUAL will wait for you to complete the insecure flash of the Suck It Verizon Bootloader. Press the Up Key before you flash the bootloader in Odin Mode.
Waiting for Downoad Mode device.......Executing Heimdall command.
Heimdall v1.4 RC2
Copyright (c) 2010-2012, Benjamin Dobell, Glass Echidna
[url]http://www.glassechidna.com.au/[/url]
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
[url]http://www.glassechidna.com.au/donate/[/url]
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Protocol initialisation successful.
Beginning session...
This device may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading recovery
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: recovery upload failed!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
[Heimdall Error Report] Detected:
Heimdall uncontinuable error; Script halted
[/Heimdall Error Report]
done
also i flashed to root66 using a pit file otherwise odin3 will fail
any help guys?
imnopro said:
any help guys?
Click to expand...
Click to collapse
Casual only works on 4.1.2, which was the last Android version on the i605 that has a bootloader that you could unlock yourself.
4.3 has a locked bootloader that will prevent you from being able to successfully downgrade the phone to any Android version before 4.3. The best you'll be able to do is use Odin to restore the phone back to stock 4.3. You can root 4.3 with SafeRoot, and then use Safestrap Recovery to run 4.3 based Roms that use the stock 4.3 kernel. You should be able to find details on how to do this by searching the threads.
Hope this helps.
mattnmag said:
Casual only works on 4.1.2, which was the last Android version on the i605 that has a bootloader that you could unlock yourself.
4.3 has a locked bootloader that will prevent you from being able to successfully downgrade the phone to any Android version before 4.3. The best you'll be able to do is use Odin to restore the phone back to stock 4.3. You can root 4.3 with SafeRoot, and then use Safestrap Recovery to run 4.3 based Roms that use the stock 4.3 kernel. You should be able to find details on how to do this by searching the threads.
Hope this helps.
Click to expand...
Click to collapse
why should i go to 4.3 if i'm on rooted root66 4.1.1 ?
check last post:
http://forum.xda-developers.com/showthread.php?p=62930543#post62930543
imnopro said:
why should i go to 4.3 if i'm on rooted root66 4.1.1 ?
check last post:
http://forum.xda-developers.com/showthread.php?p=62930543#post62930543
Click to expand...
Click to collapse
imnopro said:
hi guys.
so i had android 4.3 and downgraded to stock rooted 4.1.1 with odin.
Click to expand...
Click to collapse
I did read all of your posts. You said that your phone was on 4.3...so I'm taking that to mean that the phone was on Stock Verizon 4.3. You used root 66 to downgrade the system, but Verizon/Samsung security will not allow you to downgrade the bootloader to anything previous to 4.3. This is well documented throughout the Note 2 threads. So... Casual will not work for you because your bootloader is still on 4.3.
And just to provide more proof to what I'm telling you, go to Droidstyle's Restore guide here:
( http://forum.xda-developers.com/showthread.php?p=34891181)
and read where he says--
As most know by now, Devices that took the MJ9 4.3 OTA update permanently locked the bootloader. The previous Root and Unlock methods no longer work for this latest update. However our kind Devs developed SafeStrap for a workaround, which allows root and flashing Touch Wiz roms. Please head over to this thread for installing SafeStrap on 4.3 VRUEMJ9- http://forum.xda-developers.com/showthread.php?t=2693131
mattnmag said:
I did read all of your posts. You said that your phone was on 4.3...so I'm taking that to mean that the phone was on Stock Verizon 4.3. You used root 66 to downgrade the system, but Verizon/Samsung security will not allow you to downgrade the bootloader to anything previous to 4.3. This is well documented throughput the Note 2 threads. So... Casual will not work for you because your bootloader is still on 4.3.
Click to expand...
Click to collapse
so,android is 4.1.1 and the bootloader is 4.3...this means no custom rom on 4.3.great
at least a different sim will work on this root66 or i need to take the imei and go on some websites and pay and get the code to unlock it?
imnopro said:
so,android is 4.1.1 and the bootloader is 4.3...this means no custom rom on 4.3.great
at least a different sim will work on this root66 or i need to take the imei and go on some websites and pay and get the code to unlock it?
Click to expand...
Click to collapse
If I were you, I would probably just restore the phone to 4.3 and root it with Saferoot if you want a rooted stock ROM, but that's just me. With 4.3, you can also install Safestrap and then have some options with Custom ROM'S.... but they must be based on stock 4.3 TouchWiz and use the stock 4.3 kernel (so this means no AOSP, MIUI, etc).
Other XDA members said their Note 2 worked well in Italy (see here: http://forum.xda-developers.com/showpost.php?p=50982212&postcount=57 ).
The Verizon Note 2 is Sim/Carrier unlocked, so you should at least get voice service when you insert the Sim card. You may have to manually add APN's to get data working. Here's a good post from Max Lee that may help with changing APN settings if needed: http://highonandroid.com/android-howtos/how-to-fix-3g4g-lte-data-by-manually-setting-apn/
mattnmag said:
If I were you, I would probably just restore the phone to 4.3 and root it with Saferoot if you want a rooted stock ROM, but that's just me. With 4.3, you can also install Safestrap and then have some options with Custom ROM'S.... but they must be based on stock 4.3 TouchWiz and use the stock 4.3 kernel (so this means no AOSP, MIUI, etc).
Other XDA members said their Note 2 worked well in Italy (see here: http://forum.xda-developers.com/showpost.php?p=50982212&postcount=57 ).
The Verizon Note 2 is Sim/Carrier unlocked, so you should at least get voice service when you insert the Sim card. You may have to manually add APN's to get data working. Here's a good post from Max Lee that may help with changing APN settings if needed: http://highonandroid.com/android-howtos/how-to-fix-3g4g-lte-data-by-manually-setting-apn/
Click to expand...
Click to collapse
so i tried with one sim and works,but data doesn't,and can't configure apn because there is empty and can't do nothing.
i think i'm done with this stuff.
thanks for reply.
@mattnmag even though I didn't need your help. You definitely went above and beyond. Since he couldn't say thank you. I will, Nice explanations and good links to previous threads!
Title says it all. I haven't gotten past root because every rooter I try fails. Tried rooting on 4.5.5.1 and .2, hoping .3 would solve any issues but it didn't. Really hoping to get a custom ROM on this thing, if anyone could help, much appreciated..
WSADKeysGaming said:
Title says it all. I haven't gotten past root because every rooter I try fails. Tried rooting on 4.5.5.1 and .2, hoping .3 would solve any issues but it didn't. Really hoping to get a custom ROM on this thing, if anyone could help, much appreciated..
Click to expand...
Click to collapse
No need to pre-root. Go for one of the bootloader unlock methods and profit.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Davey126 said:
No need to pre-root. Go for one of the bootloader unlock methods and profit.
https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Click to expand...
Click to collapse
Your first link shows root as a pre-requisite? Is it still not necessary?
WSADKeysGaming said:
Your first link shows root as a pre-requisite? Is it still not necessary?
Click to expand...
Click to collapse
It is not. This post offers nice summary of the necessary steps including required files.
Davey126 said:
It is not. This post offers nice summary of the necessary steps including required files.
Click to expand...
Click to collapse
I get this error when I run get_code.bat even though running 'adb devices' shows my hdx.
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to copy 'cuber' to '/data/local/tmp/cuber': couldn't read from device
cuber: 0 files pushed. 0.1 MB/s (506072 bytes in 5.020s)
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .
WSADKeysGaming said:
I get this error when I run get_code.bat even though running 'adb devices' shows my hdx.
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to copy 'cuber' to '/data/local/tmp/cuber': couldn't read from device
cuber: 0 files pushed. 0.1 MB/s (506072 bytes in 5.020s)
error: no devices/emulators found
error: no devices/emulators found
adb: error: failed to get feature set: no devices/emulators found
error: no devices/emulators found
Press any key to continue . . .
Click to expand...
Click to collapse
Choices:
- do some basic troubleshooting to resolve the issue (first line offers a clue)
- use the 1-click method
Although preferable you do not need to execute get_code.bar prior to flashing the vulnerable bootloader (aboot) which is where the real magic lies. That said, a mistake at this stage can result in a black screen 'soft-brick' that is difficult to recover. Probably best to stick with 1-click.
Davey126 said:
Choices:
- do some basic troubleshooting to resolve the issue (first line offers a clue)
- use the 1-click method
Although preferable you do not need to execute get_code.bar prior to flashing the vulnerable bootloader (aboot) which is where the real magic lies. That said, a mistake at this stage can result in a black screen 'soft-brick' that is difficult to recover. Probably best to stick with 1-click.
Click to expand...
Click to collapse
Called in sick to work to spend the rest of the day googling my way thru this process and got it to 7.1.2
Sorry guys. I have exactly the same issue as in post #5 above. I do not want a one click type of solution. I would like to understand what the problem is and how to get the right drivers to fix the damn thing. I tried a dozen different drivers, installed correctly, with full reboots, etc, and nothing gets into that device. I use Windows 10. Thank you for any positive thought and solution.
[Thor][Apollo] Unlocking bootloader with any firmware
Hello. At first, I did not invent anything new, just checked some my guess on a other motherboard. All thanks and credits to our great developers. As always, all at your own risk. It does not work on the Fire HDX 8.9 (Saturn)! All steps in this...
forum.xda-developers.com
Reichmann aka realm mann, had the easiest guide imo.
Got a apollo unlocked and twrp'd in 30 minutes.
But take note you are expected to rename aboot file to "aboot_vuln.mbn"
And twrp to whatever the guide prints for the dd command. (I dont recall but just rename your twrp file to whatever that dd command references.)
Doesnt matter what windows. Or at least worked a treat on win7 for me. Reichmann used 10.
Make sure your key code file is generated or if you continue might be bricked judgjng from other posts.
Make sure you typed the commands exactly. Wmic commands are easy to mess up and could be confusing.
If you get an error double check every character of text.
Your disk index result number from wmic command replaces the X after Harddisk in dd command.
But if you dont get the same disk index result from all 3 wmic command or an error? Probably mistyped. Like "partiton".
Just double check and proof read.
Doesnt matter if you do mistype it as long as you retype it correctly eventually.
Hello. This is my first ever post on XDA, so please excuse any mistakes. Recently, I have been wanting to install TWRP on my Samsung Galaxy Tab S7 (Model Codename: SM-T870), however, I haven't found any .img files available, either official or unofficial. I have been able to root it using Magisk and Odin, however. My tablet is currently running Android 11 with a build number of RP1A.200720.012.T870XXU2BUC6. From what I've read online, the "2" in the "T870XXU2BUC6" section of the build number means that the Bootloader is on Version 2, meaning that I can't downgrade to software versions with a 1 in the software name (i.e. with a Bootloader version of 1). This includes Android 10, and some older versions of Android 11, even if I use the latest version of Odin and if I'm rooted. I know how to install different distros and versions of Linux for creating TWRP from scratch if need be. If someone would be willing to either guide me through the process of creating TWRP for this device, or include a link to an already existing version of TWRP for this device (remember, Android 11, Build Number: "RP1A.200720.012.T870XXU2BUC"), I would greatly appreciate it. All I ask is that the guide(s)/tutorial(s) be in layman's terms, and be step-by-step. I am not very familiar with Linux Commands, so I would appreciate some grace when replying to this post, as I may not be able to understand some terms. Thanks!
Siegemus said:
Hello. This is my first ever post on XDA, so please excuse any mistakes. Recently, I have been wanting to install TWRP on my Samsung Galaxy Tab S7 (Model Codename: SM-T870), however, I haven't found any .img files available, either official or unofficial. I have been able to root it using Magisk and Odin, however. My tablet is currently running Android 11 with a build number of RP1A.200720.012.T870XXU2BUC6. From what I've read online, the "2" in the "T870XXU2BUC6" section of the build number means that the Bootloader is on Version 2, meaning that I can't downgrade to software versions with a 1 in the software name (i.e. with a Bootloader version of 1). This includes Android 10, and some older versions of Android 11, even if I use the latest version of Odin and if I'm rooted. I know how to install different distros and versions of Linux for creating TWRP from scratch if need be. If someone would be willing to either guide me through the process of creating TWRP for this device, or include a link to an already existing version of TWRP for this device (remember, Android 11, Build Number: "RP1A.200720.012.T870XXU2BUC"), I would greatly appreciate it. All I ask is that the guide(s)/tutorial(s) be in layman's terms, and be step-by-step. I am not very familiar with Linux Commands, so I would appreciate some grace when replying to this post, as I may not be able to understand some terms. Thanks!
Click to expand...
Click to collapse
Any luck? I've yet to find any TWRP for the SM-T870
No, not yet. I've been looking as well. I've found a tool by Hovatek that can supposedly make one, and it does flash via ODIN successfully, but I can't figure out how to remove dm-verity on my SM-T870, since mine is a USER build.
I have posted a test build for the T870 here:
TWRP for the Samsung Galaxy Tab S7+ 5G (T976B)
I'm stuck in TWRP loop with the new T970XXU1ATK3 firmware won't boot to system after the update. Is there anyway to fix this issue?
forum.xda-developers.com
Please let me know if it works for you.
I tried it on my rooted stock ROM, and on ODIN, it got stuck on "file analysis". If there's a way for me to customize the stock ROM to disable vbmeta and dm-verity, please let me know, so I can hopefully try that, and then flash it again.
Siegemus said:
I tried it on my rooted stock ROM, and on ODIN, it got stuck on "file analysis". If there's a way for me to customize the stock ROM to disable vbmeta and dm-verity, please let me know, so I can hopefully try that, and then flash it again.
Click to expand...
Click to collapse
If you take a look here:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy Tab S7/S7+ Series (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
There is a vbmeta_disabled.tar that worked for me on my T870. Also, in response to your May post about a guide to building TWRP for the device, I wrote one while I was doing my build. It is posted as a response to my TWRP thread here:
[UNOFFICIAL][EXPERIMENT] TWRP for Galaxy Tab S7 Wifi
This is my first thread of this kind, so bear with me if I'm not formatting it quite right. I've run a test build of TWRP 3 for the Galaxy Tab S7 Wifi (T870) against a customized version of the kernel that shipped with the T870OXM2BUC6 firmware...
forum.xda-developers.com
I tried to make it as step-by-step as possible, but I don't know if I'd say that it's all in layman's terms. I basically only know Linux/Unix (I have not done any development on Windows for 10+ years), so it's hard for me to know what could be/needs to be simplified.
Please feel free to ask me any questions you might have and I'll be glad to help out.
OK. Thank you for linking that. I'll try my best. Wish me luck!
@bxlentpartyon Hi. I'm currently following the guide you linked earlier, and so far only a couple things haven't been working. 1) The "git checkout master" command returns "Already on 'master'". 2) The "git merge stock-11" command returns "merge: stock-11 - not something we can merge". 3) The "./run_menuconfig" command returns "bash: ./run_menuconfig: No such file or directory". I'm currently stuck on this, and so far everything else has been working perfectly. Please help!
Siegemus said:
@bxlentpartyon Hi. I'm currently following the guide you linked earlier, and so far only a couple things haven't been working. 1) The "git checkout master" command returns "Already on 'master'". 2) The "git merge stock-11" command returns "merge: stock-11 - not something we can merge". 3) The "./run_menuconfig" command returns "bash: ./run_menuconfig: No such file or directory". I'm currently stuck on this, and so far everything else has been working perfectly. Please help!
Click to expand...
Click to collapse
The issue here is partially that my write-up details everything that I did to run the build, but you won't need to do some of that, since I already pushed my kernel source tree (with the git merge bit of things already done) up to github.
What you can do is replace the:
Code:
git clone https://github.com/ianmacd/gts7xl
Step with:
Code:
git clone https://github.com/bxlentpartyon/gts7lwifi
And then skip down to the Build the Kernel step.
Honestly, though, the more I'm looking at it, I'm realizing that I should probably create a stripped down version of this whole write-up where I explain _just_ how to reproduce my TWRP build, and skip over the stuff about building the kernel and hacking up the device tree. That won't take me long to do, but it might be a day or two before I get to it. I unfortunately have to spend my week hacking on kernels for profit in order to pay for the things that I need to hack on them for fun lol.
Thank you so much!
I'm on the "building the kernel" step, and when I run "./build_t870", I get this message: "Makefile:128: *** main directory cannot contain spaces nor colons. Stop.", along with a large section of text before that. Is this an error message? what should I do?
Siegemus said:
"Makefile:128: *** main directory cannot contain spaces nor colons. Stop."
Click to expand...
Click to collapse
If you run pwd in your build directory, are there any spaces in that full path? My guess would be that's your issue.
I renamed my main foldr from "Making TWRP" to "Making_TWRP", and that did the trick. However, when I ran "./build_t870", I came across this error:
"YACC scripts/kconfig/zconf.tab.c
/bin/sh: 1: bison: not found
make[2]: *** [scripts/Makefile.lib:207: scripts/kconfig/zconf.tab.c] Error 127
make[2]: *** Waiting for unfinished jobs....
LEX scripts/kconfig/zconf.lex.c
make[1]: *** [Makefile:545: syncconfig] Error 2
make: *** [Makefile:654: include/config/auto.conf.cmd] Error 2" How do I solve this? Sorry for bothering you with all these replies, btw.
Siegemus said:
when I ran "./build_t870", I came across this error:
"YACC scripts/kconfig/zconf.tab.c
/bin/sh: 1: bison: not found
make[2]: *** [scripts/Makefile.lib:207: scripts/kconfig/zconf.tab.c] Error 127
make[2]: *** Waiting for unfinished jobs....
LEX scripts/kconfig/zconf.lex.c
make[1]: *** [Makefile:545: syncconfig] Error 2
make: *** [Makefile:654: include/config/auto.conf.cmd] Error 2" How do I solve this? Sorry for bothering you with all these replies, btw.
Click to expand...
Click to collapse
No worries. That's just because you're missing the bison package. What linux distro are you using? Most have some kind of "build essentials" package set you can install that would probably include everything you need to build a kernel. In any case, to fix that, you just need to install bison with zypper/dnf/yum/apt or whatever package manager your distro uses. In general if you see a <something>: not found error, it just means you're missing a program.
OK. Thank you! I'm currently using Ubuntu 20.04.
Hi again. For some reason, I'm now getting THIS error message after installing the bison and Ubuntu 20.04 LTS build-essential packages, like you said:
"make[2]: *** [scripts/kconfig/Makefile:69: syncconfig] Error 1
make[1]: *** [Makefile:545: syncconfig] Error 2
make: *** [Makefile:654: include/config/auto.conf.cmd] Error 2"
Ah, that's probably because of more differences between what I did and what you'll have to do with my final tree. Try:
Code:
cp arch/arm64/configs/vendor/gts7lwifi_eur_open_klugman_defconfig ./.config
In your kernel tree. I think the problem is just the missing config. I'm probably gonna have to bail for the night after this. Our air is all smoky from the Canadian wildfires and I'm real dizzy from breathing it.
OK. If you want, I can talk tommorow if anything happens. See you!
bxlentpartyon said:
Honestly, though, the more I'm looking at it, I'm realizing that I should probably create a stripped down version of this whole write-up where I explain _just_ how to reproduce my TWRP build, and skip over the stuff about building the kernel and hacking up the device tree. That won't take me long to do, but it might be a day or two before I get to it. I unfortunately have to spend my week hacking on kernels for profit in order to pay for the things that I need to hack on them for fun lol.
Click to expand...
Click to collapse
Hello. It's me again. I hope you are doing well. In hopes to prevent future error messages, and subsequent troubleshoots, would you be willing to let me know if and/or when you have created the stripped-down version of this guide on how to reproduce your TWRP build?
Yeah, I'll get that written up this weekend and let you know when it's up. I meant to do it yesterday, but I've been busy with work.