Develop Bugs

[NOW PUBLIC!] Team Codefire Presents: Project FreeGee!

Please note, this is not compatible with the JB OTA - use the app in the Play store instead for now. Thanks!
Howdy all! So, it's time for me to dig out my release thread template... you know what that means?
The LG Optimus G is now unlocked.
Both the AT&T Version and the Sprint Version have been successfully unlocked with this method.
(To answer your question, if you're wondering, we're going to work on the Canadian version next, then the Korean version)
First off, I'd like to write a few words to LG:
Dear LG, a product will rise and fall on the shoulders of it's community.
If you lock a device, and shut out your community, you lose the backing of a very vocal group of people. When you lose the backing of your community, they no longer recommend your product, and you lose money. HTC has discovered this recently.
Please support your development community, we understand product security plays a role here, but ensure that you cater to your community still.
The second you try to fight your development community by locking them out of your products is the second that I will cease to recommend your products.
Keep this in mind, and I assure you that you will find yourself on the top of the game.
With all of that said, let's get back to the goodies.
What is this?!
This is Project FreeGee, silly!
Have an Optimus G ? This project will allow you to unlock your bootloader, and install whatever you want.
Click to expand...
Click to collapse
How does this work?
For the moment, that is a trade secret. Suffice it to say that we put some ones and zeros in the right places, and good things happen.
This is also my opportunity to say do not allow any OTAs to install without asking if they are compatible. LG could possibly patch this in such a manner that makes it rather hard to ever exploit it again.
Click to expand...
Click to collapse
I'm a skeptic. I demand proof!
Alrighty, here it is:
Once again, taken with my HTC Vivid, that would rather mute me than let me speak.
Damn "nose elimination"! I am not noise, and I will not be silenced! (mmhmhmhpmhmp!!)
Click to expand...
Click to collapse
Okay, I'm game. Where do I get it?
Version 0.3 has a confirmed bug-- camera app crashes phone after a few seconds!
If you have 0.3 installed, simply download this, extract the .zip, and extract the .tar file. Inside the freegee-working directory, you'll find boot-att-freegee.img .
Boot your phone to fastboot, then fastboot flash boot /path/to/boot-att-freegee.img
I will release a quick fix .zip for flashing in CWM tomorrow.
Current Version: 0.5
Changelog:
New in v0.5 Removed LG Security check. You are now free to remove any and all apps.
http://downloads.codefi.re/thecubed/lgoptimusg/sprint/freegee/FreeGee-0.5_Sprint.zip
Currently, the download is Windows-only. I will make a OSX/Linux/Windows version soon!
Click to expand...
Click to collapse
FAQ
Can I flash an OTA after installing this?
No. Flashing an OTA could contain a new bootloader, and it would replace the one we have put on your device. If you flash the new OTA, and it replaces the bootloader but not the boot.img, you could be left in a situation where you could not boot the phone due to a security error. Once you're in that position, the only thing you can do is LGNPST back to stock-- and even then, it is possible that an OTA could enable an anti-rollback feature which would disable LGNPST.
Does this mean I can flash custom ROMs now?
Yes. However, the custom ROM must be made for your device. We're working on a decrapified stock ROM, and AOSP ROMs as well. Be patient for those to come.
Can I install a Nexus 4 system image and boot.img and have it work?
We've tested that, and the answer is no, not yet. Some work needs to be done, but once we figure it out, we'll have a quick and easy AOSP ROM.
Does this mean that we can use the Nexus 4 sources (kernel and android) ?
Short answer: Yes.
This phone is essentially a Nexus 4, with minor differences in GPIOs, memory address space, and partition table layouts.
Kernel source is iffy, since we've got Eco mode and a few other things that actually make me like the Optimus kernel more than the Nexus kernel.
However, this discussion is best suited for a new post.
How can I uninstall this?
I'm working on an easy-uninstall for this as well. Stay tuned for the links...
Click to expand...
Click to collapse
Important Information
To enter bootloader, hold volume UP and power.
Upon entering the bootloader, you will notice that there is no 'menu' to enter fastboot or recovery. Unfortunately, since the stars didn't align properly, we were unable to tell the new bootloader where to load the images that contain the menu from.
In light of that, you'll have to navigate the menu blind. Use the volume keys to change selection, and the power key to select.
The choices are (in order of pressing volume down):
Start - boot the phone normally [already selected]
Restart Bootloader - reboot into the bootloader
Recovery Mode - enter recovery (CWM)
Power Off - powers the phone off
So, to get to Recovery, you would press volume down twice then power.
If you have trouble with this, watch my video below for a demonstration.
Click to expand...
Click to collapse
Instructions!
Please note: this requires root before you can install this! If you haven't rooted your phone yet, now is the time to do so.
Also, ensure that you have ADB drivers installed. This WILL NOT WORK without them.
Before we begin: please make sure you have USB Debugging turned on, your phone is in "Charge Only" mode, and your phone's screen is on and unlocked.
This will allow you to see the root access prompt if your phone asks for it.
Download the .zip from this post
Extract it somewhere on your hard drive
Ensure your screen is on and unlocked
Run the "freegee.bat" script, and follow the instructions.
Do not run this as administrator! the install will fail if you do so.
Once the unlock is complete, check to make sure you have a "backups" folder now in the folder where you put FreeGee. If not, DO NOT REBOOT your phone.
Even a failed unlock will still show the 'congratulations you're unlocked!' text, read the output to see if you have errors!
You should not see any "adb.exe not found" errors, or "tar: invalid magic" errors. Those would be errors in the script.
An error which you can ignore is "No space left on device" after it says erasing old recovery and boot. That's just a side effect of how we clear the old images out.
Click to expand...
Click to collapse
Contact Information
"Mister Cubed, how do I talk to you?"
That's easy! Hop on IRC and join me on Freenode in #lg-optimus-g . I'm in there as IOMonster (or IOMonster_desk, or IOMonster_work, depending on where I am)
There's also a lot of other cool people in there too!
When you hop in IRC, if you've got a question, just ask it. Don't say "halp! i does brick'd my phone, and i dunno wat to does?!!", but rather "can anyone help? my phone is stuck in fastboot mode, and I can't get out of it. I flashed <xyz> and now I'm stuck here."
Asking your full question (even though it might be a long message) helps us figure out the best way to assist you, without us having to lead the conversation and ask all the questions for you.
Also, on IRC (for those of you who have never used IRC) if you say someone's name, it will 'ping' (also called 'highlight') them. This tells us that someone is talking to us. So, if you pop in IRC and say "IOMonster, it worked!", I'll get a notification, and will probably say "that's awesome!" in response.
Click to expand...
Click to collapse
Special Thanks To!
None of this would be possible without the assistance of the following people:
Shelnutt2
g33k3r
kmdm
synergy
jcase
sextape
xboxfanj
...and the support of the entire #lg-optimus-g IRC channel
A project like this is really only a sum of it's parts, and in our case, we're over 9,000!
Please make sure to tell someone on this list that they're awesome if you see them on IRC or (*gasp!*) in real life.
Click to expand...
Click to collapse
All right, that about sums up my post. Did I forget anything? Let me know below...

Thanks to all of u guys for all your hard work!

Here is some proof, this is fully working...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the blurry images, took these from my old OG Evo... But can say its fully unlocked!!!
Nice work thecubed, and shellnut2 on this, thanks for keeping our freedom alive!!!

Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app

Tyederian said:
Does the sprint launch OTA prevent this from working?
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
I've already run the OTA, and had no issues unlocking, or rooting after the OTA...

I am so excited! I cannot wait to get this thing unlocked! :victory:

Sweet super excited

Awesome! Will be donating to the team on pay day thanks guys!
Sent from my PG86100 using xda premium

That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!

Wow! Many thanks to all the devs for their hard work and to the beta testers for their willingness to let their phones be guinea pigs. Very much looking forward to this!
Sent from my LG-LS970 using Tapatalk 2

jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
$55 they charged me $99 and some tax on top of it. how did you pull that off?

Super sweet you guys are awesome!!

Christmas came early this year.
Sent from my LG-LS970 using xda app-developers app

New build is up!
Fixed a typo in my code haha

awesome job, big thanks to everyone.
And I second that $55 question.

jblazea50 said:
That's awesome. Just got the phone today from Best Buy for $55 and excited to get the bootloader unlocked and wait for the AOSP Jelly Bean roms.
Thanks devs!!!
Click to expand...
Click to collapse
How on earth did you get it for $55?

tabormeister said:
How on earth did you get it for $55?
Click to expand...
Click to collapse
Had signed up for phone freedom to get $50 gift card back in February.

So I just ran this and had a couple little panic moment!!
1. While reading the script, SU poped up and I missed the "Grant SU" button on the phone. I still got the backup folder but nothing was in it. I then thought it worked, rebooted, and nothing.
The second time I ran this, I got to the "Grant SU" button in time and all went GREAT!!! This time I had files in the backup folder.
2. When I rebooted into recovery, I tried to make a backup. I hit the backup button and got some message that said "Can't mount backup path". So i tried the backup to internal SD and it worked.
Figured I'd write this in case anybody else had the same moment's I did.
The files on the backup folder are very differnt from what I'm used to so hopefully I did it correctly. I noticed there was an option in CWM to choose the backup format after I'd made my backup, so I'm not sure which format is correct for Restore. I guess I used the default which is .dup.
Thank you very much dev's for this!!!!!:laugh:
---------- Post added at 05:54 AM ---------- Previous post was at 05:25 AM ----------
DO NOT use the camera!!!! It'll crash your phone!!!
I read about it in the ATT section just now, but it's too late for me. So I guess we have this bug also.
OK...so not quite a crash. Held the volume down button and power together and got it to reboot.
Now we just need to have a way to recover our phones if/and/or when we do crash our phones. I know the devs are working on this, as obviously they are the bomb!!!

Tease: Two things brewing that hopefully will be up today. Both directly related to this

Shelnutt2 said:
Tease: Two things brewing that hopefully will be up today. Both directly related to this
Click to expand...
Click to collapse
I'm sure hoping you're referring to my post above. I get alittle wiggy if I don't have a way to fix my phone myself.

N5X shows only colorful static when turned on

Hi,
I am having a serious problem with my Nexus 5x:
After installing the new AOSPA today, I wiped data, cache and dalvik and then tried to boot the phone (up to that point, everything was ok). Instead of showing the usual "google" logo with the warning about the unlocked bootloader , the screen just shows some colorful static (i'll attach a photo of that).
So, I can't boot the phone. It's recognized in fastboot mode by the computer, but the screen doesn't show anything. Same goes for recovery (TWRP), I can talk to the phone via ADB but the screen remains black.
I've tried everything I can, including reverting the software to stock (see Heisenberg's guide) but without wiping the personal data.
Do you have any idea what I could do to get my phone back except relocking the bootloader and sending it in for repair?
Thanks a lot!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: RMA'd the phone, they had to replace the screen / touch unit (obviously) and the camera (?) for some reason

dbahn25 said:
Hi,
I am having a serious problem with my Nexus 5x:
After installing the new AOSPA today, I wiped data, cache and dalvik and then tried to boot the phone (up to that point, everything was ok). Instead of showing the usual "google" logo with the warning about the unlocked bootloader , the screen just shows some colorful static (i'll attach a photo of that).
So, I can't boot the phone. It's recognized in fastboot mode by the computer, but the screen doesn't show anything. Same goes for recovery (TWRP), I can talk to the phone via ADB but the screen remains black.
I've tried everything I can, including reverting the software to stock (see Heisenberg's guide) but without wiping the personal data.
Do you have any idea what I could do to get my phone back except relocking the bootloader and sending it in for repair?
Thanks a lot!
Click to expand...
Click to collapse
This looks like a display failure unfortunately. I don't know if there's anything more you can do except RMA since you flashed the factory image. Could you post the file name of the AOSPA rom zip that you flashed?
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
This looks like a display failure unfortunately. I don't know if there's anything more you can do except RMA since you flashed the factory image. Could you post the file name of the AOSPA rom zip that you flashed?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Oh no :crying: how could that be from just flashing a new rom (+ gapps)? I didn't do anything differently from all the other times I flashed my ROM..... Was it really just bad luck?
I flashed the AOSPA build from 6/6/16 (pa_bullhead-6.0-20160606-signed.zip) with BaNkS gapps (BaNkS_Dynamic_GApps_6.x.x_6-7-16_23_51.zip)
I guess it'd be best to lock the bootloader for the RMA, wouldn't it?

dbahn25 said:
Oh no :crying: how could that be from just flashing a new rom (+ gapps)? I didn't do anything differently from all the other times I flashed my ROM..... Was it really just bad luck?
I flashed the AOSPA build from 6/6/16 (pa_bullhead-6.0-20160606-signed.zip) with BaNkS gapps (BaNkS_Dynamic_GApps_6.x.x_6-7-16_23_51.zip)
I guess it'd be best to lock the bootloader for the RMA, wouldn't it?
Click to expand...
Click to collapse
On the P.A website and Google post it says they highly recommend using open gapps perhaps Ur issue is related to that??? I'm no expert is there anyway u can sideload the ROM and open gapps via adb ???
Sent from my Nexus 5X using XDA-Developers mobile app

dog121 said:
On the P.A website and Google post it says they highly recommend using open gapps perhaps Ur issue is related to that??? I'm no expert is there anyway u can sideload the ROM and open gapps via adb ???
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
No... they say you should use banks instead of open gapps since those might make problems. That's the reason I didn't use the open gapps
I'm not sure about the sideloading though, I've never done that. Do you have a guide for me?

dbahn25 said:
No... they say you should use banks instead of open gapps since those might make problems. That's the reason I didn't use the open gapps
I'm not sure about the sideloading though, I've never done that. Do you have a guide for me?
Click to expand...
Click to collapse
Have a look at this...
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I suggest you get the latest update that just came out via Google updates for Nexus 5x and give that a whirl....
I hadn't realised that P.A changed the gapps yesterday they were using open gapps...
Sent from my Nexus 5X using XDA-Developers mobile app

dog121 said:
Have a look at this...
http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/
I suggest you get the latest update that just came out via Google updates for Nexus 5x and give that a whirl....
I hadn't realised that P.A changed the gapps yesterday they were using open gapps...
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
Alright, thanks! Unfortunately, I've already shipped my phone back to repair / replacement. But I wonder, is there any advantage of using sideload over using fastboot to flash the stock image?
Also I don't think it would've worked since I couldn't have enabled sideload without seeing anything on screen (it was completely black while in recovery).

dbahn25 said:
Also I don't think it would've worked since I couldn't have enabled sideload without seeing anything on screen (it was completely black while in recovery).
Click to expand...
Click to collapse
It can be done, just need to look at screenshots someone else posts of the recovery menu and count.

Unofficial Build Thread... (Magisk, TWRP, etc.)

By request this is now the Unofficial Build Thread
This thread has been created to help clear up the confusion in the official threads.​
That's right, everything here is just built. I am not the author of this code, I simply build current commits and provide them after having tested them myself on the most current Google provided factory images. I do not test these on betas. I will update this OP with more detailed instructions as deemed necessary.
Ok, so no more :good: Magisk is fixed :good: tomfoolery because I don't believe it anymore... From now on I am just going to provide solutions and assume that official is going to be broken again. What I am referring to is the dtbo image being patched and displaying the nasty "operating system on your device has been modified" message on every boot.
I have been told by typically competent developers that removing dtbo patching is stupid and makes no sense. I have been told that we cant run low level audio mods etc without it being patched. BlaBlaBla... Well, I can run everything I want without it being patched. Viper works, and anything else I have tried has worked. So, enough with that. More information on dtbo here...
I personally hate the message, and if you are here then you probably hate it too. So, if you like the message and want to keep it... Leave.
Unless something changes (oh and I am sure it will again) we only need a Magisk Manager app that does not patch dtbo without our permission. That is what I compile and provide. In the future if the actual root zip starts patching again, I will compile that too. But for now, it is just the app...
Here we go again...
1.) Uninstall official manager app
2.) Install this one. ...Unofficial Magisk Manager...
3.) If dtbo was patched and you are seeing the message then reboot to bootloader and 'fastboot flash dtbo dtbo.img' (factory dtbo)
4.) You are done.
Currently 15.2 root does not patch dtbo, Magisk Manager does.
I will release new modified Magisk Manager apps here as new commits are made. It is not necessary to update right away as there are rarely earth shattering changes released and most of the time the commits do not even apply to our device. I will compile new builds in as timely of a manner as I can. If something major does drop, it will be quick.
Happy New Year!!!​
Join the Telegram Group!
https://t.me/Pixel2XLXDA​

Reserved
...Because everyone else does it....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
...Look HERE for stuff...
*until google tells me otherwise*
(I don't care if you share/take credit for/mirror bla bla bla)
Suggestions
1.) Be current but not to current... (Run current non-beta factory images)
2.) Make sure you are running current adb/fastboot binaries. (Provided)
3.) Make sure your usb/usb-c cable is not from Toys R Us (They don't carry one : See Amazon)....
4.) You are not on a PS/1 (My first system )
5.) Don't exhibit behavior similar to mine...
..WIP..

Right on man. Thanks.

thedude420 said:
...Because everyone else does it....
...Look HERE for stuff...
*until google tells me otherwise*
(I don't care if you share/take credit for/mirror bla bla bla)
Suggestions
1.) Be current but not to current... (Run current non-beta factory images)
2.) Make sure you are running current adb/fastboot binaries. (Provided)
3.) Make sure your usb/usb-c cable is not from Toys R Us (They don't carry one : See Amazon)....
4.) You are not on a PS/1 (My first system )
5.) Don't exhibit behavior similar to mine...
..WIP..
Click to expand...
Click to collapse
#3 made me chuckle. :laugh::laugh::laugh::laugh::laugh:
On a serious note though, I tried flashing this last night and my phone would not stop rebooting on its own. It would restart and would just reboot. I tried grabbing some logs but the app (MatLog) would just load and not show any output.
Will probably see if I can try again and see if anything changes. Will also try the APK method you mentioned in the Magisk 2XL thread.

nexus_man12 said:
#3 made me chuckle. :laugh::laugh::laugh::laugh::laugh:
On a serious note though, I tried flashing this last night and my phone would not stop rebooting on its own. It would restart and would just reboot. I tried grabbing some logs but the app (MatLog) would just load and not show any output.
Will probably see if I can try again and see if anything changes. Will also try the APK method you mentioned in the Magisk 2XL thread.
Click to expand...
Click to collapse
Flash factory Nov images without -w to save your data then start over with twrp beta 2 and this magisk...

thedude420 said:
Flash factory Nov images without -w to save your data then start over with twrp beta 2 and this magisk...
Click to expand...
Click to collapse
Thanks dude for the prompt response. I'll give it a shot later today.

nexus_man12 said:
Thanks dude for the prompt response. I'll give it a shot later today.
Click to expand...
Click to collapse
Rite on! Here it is flash-all.bat. Not trying to be a douche but I once made changes to this file, flashed then realized that I did not save them prior... Ended up with a brand new device, it was great... Obviously this would only work with Nov factory images for Google "taimen" 8.0.0 ((OPD1.170816.025, Nov 2017) (not tested with the verizon ones..))
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-taimen-tmz10n.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-taimen-g8998-00122-1708311414.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot update image-taimen-opd1.170816.025.zip
echo Press any key to exit...
pause >nul
exit

Any word on ROMs being built for xl2? I'm waiting with bootloader til there are some ROMs
Sent from my Pixel 2 XL using Tapatalk

What do you mean? Waiting with bootloader?
Sent from my Pixel 2 XL

patt2k said:
Any word on ROMs being built for xl2? I'm waiting with bootloader til there are some ROMs
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I don't get it either. Unlock your bootloader now and get it over with. Going to have to wipe your data at some point. Also note that unlocking critical is NOT necessary. Just do a 'fastboot flashing unlock' and your good to go.
As far as ROMS go, I am not really sure. Syncing googles source tree today then I am going to do some test builds. Then go from there. They are coming :good:

thedude420 said:
I don't get it either. Unlock your bootloader now and get it over with. Going to have to wipe your data at some point. Also note that unlocking critical is NOT necessary. Just do a 'fastboot flashing unlock' and your good to go.
As far as ROMS go, I am not really sure. Syncing googles source tree today then I am going to do some test builds. Then go from there. They are coming :good:
Click to expand...
Click to collapse
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Sent from my Pixel 2 XL

abuttino said:
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Click to expand...
Click to collapse
The dev site says "may be necessary"... I have never unlocked critical and have not had one problem. Only thing I can tell it does is allow modifications to the actual bootloader which we do not need to do.

abuttino said:
Critical isn't required for a factory image flash? I wonder why they put the instructions on the site
Sent from my Pixel 2 XL
Click to expand...
Click to collapse
it's needed if there's an updated bootloader in the factory image.
8.1 DP1 has an updated bootloader so Unlock Critical is needed to fastboot flash that.

drewski_1 said:
it's needed if there's an updated bootloader in the factory image.
8.1 DP1 has an updated bootloader so Unlock Critical is needed to fastboot flash that.
Click to expand...
Click to collapse
Really? Google bootloader's will not flash without critical unlocked???

thedude420 said:
Really? Google bootloader's will not flash without critical unlocked???
Click to expand...
Click to collapse
It seems that way.
Sent from my Pixel 2 XL

Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
So it appears Substratum theme was causing Magisk Manager crashing issues. I recommend not theming Magisk Manager!

Thanks for the effort and time put into this thread! Looking forward to having the time to sit down and play
Seriously though, the hard work is very much appreciated!

thedude420 said:
Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
Click to expand...
Click to collapse
What are the circumstances? I'm running out with nothing happening yet. Can you help me reproduce it? Maybe we can figure something out.

CyberpodS2 said:
What are the circumstances? I'm running out with nothing happening yet. Can you help me reproduce it? Maybe we can figure something out.
Click to expand...
Click to collapse
Yeah, I have some stuff I need to do for the wife but then I will get some time and collect logs etc...

thedude420 said:
Latest Unofficial Magisk Build
Magisk-14.5
Or attached to OP
So it appears Magisk Manager 5.4.2 is crashing. I would suggest sticking with 5.4.1 and disabling update notifications in settings for now.
Click to expand...
Click to collapse
No crashing here. Did you try wiping data?
Sent from my Pixel 2 XL

can't boot twrp

PROBLEM SOLVED USE LATEST TWRP BUILD BUT BE CAREFUL WITH FLASHING ROMs COZ THEY STILL DOES NOT SUPPORT THIS SCREEN PANEL​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tried both dummy image and straight up booting nothing works
just flashing miui with unlocked sign and then just straight nothing
official twrp
arb 4
it just not booting
edit: just flashed latest dev rom and still nothing
here are some dmesg logs and hardware:
https://i.imgur.com/giIki1W.png
https://i.imgur.com/v8jyDkQ.png
https://i.imgur.com/UAcukty.png
https://drive.google.com/open?id=1M8V80-gKEpnxRgy1-iUGt9Oj76RDqGD2

I was having the same issues using a Windows PC. I tried on my Mac this morning and worked right away.
Maybe try using Ubuntu Live if you don't have a Mac available.
1. Download TWRP
From Terminal:
2. Install Android Platform Tools
Code:
sudo apt-get install android-platform-tools
3. Reboot phone to bootloader(fastboot) I find it easiest just to use ADB
Code:
adb reboot bootloader
4. Change directory to Downloads
Code:
CD Downloads
5. Use Fastboot to boot to TWRP
Code:
fastboot boot twrp-3.2.3-1-whyred.img
If you need to transfer downloaded files to your phone from Mac/Linux, just use adb push in terminal. (note, file names and directories are case sensitive)
Code:
adb push [I]complete-file-name.zip[/I] /sdcard/
I know this is a big hassle, but still better than nothing

daggorlad said:
I was having the same issues using a Windows PC. I tried on my Mac this morning and worked right away.
Click to expand...
Click to collapse
it doesn't work
after fastboot boot twrp.img screen flashes miui logo and unlocked for couple seconds and then goes black

NiNoX14 said:
it doesn't work
after fastboot boot twrp.img screen flashes miui logo and unlocked for couple seconds and then goes black
Click to expand...
Click to collapse
Sounds like you were having a slightly different issue than I was. Mine was just sticking on downloading image. Sorry it was of no help.

daggorlad said:
Sounds like you were having a slightly different issue than I was. Mine was just sticking on downloading image. Sorry it was of no help.
Click to expand...
Click to collapse
thanks
no problems
i don't know why my phone don't want to be like the others

NiNoX14 said:
thanks
no problems
i don't know why my phone don't want to be like the others
Click to expand...
Click to collapse
maybe try using XMT to reflash MIUI 10 then reattempting

NiNoX14 said:
thanks
no problems
i don't know why my phone don't want to be like the others
Click to expand...
Click to collapse
I have the same problem, Please Help me!!!

NiNoX14 said:
thanks
no problems
i don't know why my phone don't want to be like the others
Click to expand...
Click to collapse
twrp unzip run install
https://drive.google.com/open?id=1XLncxs4UDcSxiefQomwT4yZpWthwfAES
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
duckiemhy said:
I have the same problem, Please Help me!!!
Click to expand...
Click to collapse
use twrp in link

raptorddd said:
twrp unzip run install
https://drive.google.com/open?id=1XLncxs4UDcSxiefQomwT4yZpWthwfAES
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
use twrp in link
Click to expand...
Click to collapse
still black screen after flashing
nothing happens

bump

NiNoX14 said:
bump
Click to expand...
Click to collapse
Which HW do you have? (phone).
Which FW?
On my case, during the first boot after TWRP, the only way I could boot in recovery was using the buttons:
fastboot.exe flash recovery twrp\twrp.img (should say sending recovery okay, writing recovery okay, it did for you)
fastboot.exe reboot
quickly hold volume UP + power button (how until it should show TWRP, if it shows some chinese boot, redo the fastboot flash)

htchd2sucks said:
Which HW do you have? (phone).
Which FW?
On my case, during the first boot after TWRP, the only way I could boot in recovery was using the buttons:
fastboot.exe flash recovery twrp\twrp.img (should say sending recovery okay, writing recovery okay, it did for you)
fastboot.exe reboot
quickly hold volume UP + power button (how until it should show TWRP, if it shows some chinese boot, redo the fastboot flash)
Click to expand...
Click to collapse
there is screenshots of hardware in OP

NiNoX14 said:
there is screenshots of hardware in OP
Click to expand...
Click to collapse
Well... I saw some screenshot with some HW related info but I need you to tell exactly (I don't know all devices references!)
Which phone, exactly! I saw referenced to whyred in the screenshots, but do tell!
I'm thinking maybe it's a chinese version? I saw some Russian in your text, maybe you are trying something incorrect.
Just tell, I'll try to help you now.
What is your TWRP version? I saw you renamed it in twrp.img. What is the full version?
---------- Post added at 05:55 PM ---------- Previous post was at 05:36 PM ----------
What FW is that, how do you got this 660_GEN_PACK-1.172780.3.174030.1?
It doesn't corresponds to any stable version I know...

htchd2sucks said:
Well... I saw some screenshot with some HW related info but I need you to tell exactly (I don't know all devices references!)
Which phone, exactly! I saw referenced to whyred in the screenshots, but do tell!
I'm thinking maybe it's a chinese version? I saw some Russian in your text, maybe you are trying something incorrect.
Just tell, I'll try to help you now.
What is your TWRP version? I saw you renamed it in twrp.img. What is the full version?
---------- Post added at 05:55 PM ---------- Previous post was at 05:36 PM ----------
What FW is that, how do you got this 660_GEN_PACK-1.172780.3.174030.1?
It doesn't corresponds to any stable version I know...
Click to expand...
Click to collapse
Xiaomi Redmi Note 5
whyred - short name for this phone
what else do you need ?
https://dl.twrp.me/whyred/twrp-3.2.3-0-whyred.img.html

NiNoX14 said:
Xiaomi Redmi Note 5
whyred - short name for this phone
what else do you need ?
https://dl.twrp.me/whyred/twrp-3.2.3-0-whyred.img.html
Click to expand...
Click to collapse
So it's the global version, are you sure? It matters for the FW...
I know whyred is the shortname, but in fact it's also for the RN5 pro (indian version).
So you are using the latest TWRP then...
Have you tried what I told you about holding buttons? I told you the steps, tell me exactly what you see after the reboot.

htchd2sucks said:
So it's the global version, are you sure? It matters for the FW...
I know whyred is the shortname, but in fact it's also for the RN5 pro (indian version).
So you are using the latest TWRP then...
Have you tried what I told you about holding buttons? I told you the steps, tell me exactly what you see after the reboot.
Click to expand...
Click to collapse
yes i've tried and still twrp not booting, same old blackscreen
definitely global version
but somehow my manual and other papers were in spanish or something similar anything but english
there is recovery.log: https://paste.omnirom.org/view/e2d3ea1f

NiNoX14 said:
yes i've tried and still twrp not booting, same old blackscreen
definitely global version
but somehow my manual and other papers were in spanish or something similar anything but english
there is recovery.log: https://paste.omnirom.org/view/e2d3ea1f
Click to expand...
Click to collapse
its weird because "by defaul" you shopuzld have chinese recovery...
What about micro sd card, remove any if you have.
By the way, when I hold vol up and power button for 15 seconds until I see the TWRP logo, it goes black a second after.
I know I can release the buttons and press power once again to light the screen again.
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
By the way it's possible that TWRP is too old for your latest firmware because you appears to have "xxxxx17xxxxxx" and I saw the latest stable is only "xxxxxx16xxxxxxx".
I would suggest, since you have ARBV4 and can't easily install older, to try another recovery, such as:
https://forum.xda-developers.com/redmi-note-5-pro/development/twrp-orangefox-recovery-project-t3837547
or
https://forum.xda-developers.com/redmi-note-5-pro/development/recovery-red-wolf-recovery-project-t3766997
You can see an example bug report here:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1314
FYI, there's even a workaround, to replace some blob vendor file.
I also have other issues with TWRP, I have the impression this TWRP for whyred is "paused" or even maybe stopped.
---------- Post added at 07:18 PM ---------- Previous post was at 07:01 PM ----------
I updated the thread of Whyred TWRP for you.
He has a latest version there, maybe it contains updated blobs:
twrp-3.2.3-1-whyred.img:
https://www.androidfilehost.com/?fid=1322778262904029848
https://forum.xda-developers.com/redmi-note-5-pro/development/recovery-twrp-3-2-1-0-whyred-t3766113

htchd2sucks said:
its weird because "by defaul" you shopuzld have chinese recovery...
What about micro sd card, remove any if you have.
Click to expand...
Click to collapse
i've tried without sdcard and there was no change
i have default Mi Recovery
it basically can be booted after you boot into system > turn off > use buttons to boot recovery
more logs
https://paste.omnirom.org/view/d03a276b
https://paste.omnirom.org/view/133173e9
folder with logs without sd: https://drive.google.com/open?id=1VBTmObqpUrBv9IVk29OQ-pFpmAH2eLzS

htchd2sucks said:
its weird because "by defaul" you shopuzld have chinese recovery...
What about micro sd card, remove any if you have.
By the way, when I hold vol up and power button for 15 seconds until I see the TWRP logo, it goes black a second after.
I know I can release the buttons and press power once again to light the screen again.
---------- Post added at 07:01 PM ---------- Previous post was at 06:54 PM ----------
By the way it's possible that TWRP is too old for your latest firmware because you appears to have "xxxxx17xxxxxx" and I saw the latest stable is only "xxxxxx16xxxxxxx".
I would suggest, since you have ARBV4 and can't easily install older, to try another recovery, such as:
https://forum.xda-developers.com/redmi-note-5-pro/development/twrp-orangefox-recovery-project-t3837547
or
https://forum.xda-developers.com/redmi-note-5-pro/development/recovery-red-wolf-recovery-project-t3766997
You can see an example bug report here:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1314
FYI, there's even a workaround, to replace some blob vendor file.
I also have other issues with TWRP, I have the impression this TWRP for whyred is "paused" or even maybe stopped.
---------- Post added at 07:18 PM ---------- Previous post was at 07:01 PM ----------
I updated the thread of Whyred TWRP for you.
He has a latest version there, maybe it contains updated blobs:
twrp-3.2.3-1-whyred.img:
https://www.androidfilehost.com/?fid=1322778262904029848
https://forum.xda-developers.com/redmi-note-5-pro/development/recovery-twrp-3-2-1-0-whyred-t3766113
Click to expand...
Click to collapse
orange installing from twrp so i cant use that
redwolf same - no effect
i don't know how to do this "FYI, there's even a workaround, to replace some blob vendor file."
ill be googling this, if you can link me tutorial or smthing
ill try new version of twrp later ill update this thread
thanks for help by the way

NiNoX14 said:
orange installing from twrp so i cant use that
redwolf same - no effect
i don't know how to do this "FYI, there's even a workaround, to replace some blob vendor file."
ill be googling this, if you can link me tutorial or smthing
ill try new version of twrp later ill update this thread
thanks for help by the way
Click to expand...
Click to collapse
Sorry, I don't know how to actually replace the vendor file myself. Maybe it's about extracting the content of the "twrp.img", replace the file (given in the workaround) and recreate a .img?
I haven't looked at that.
Edit:
I just tried to extract the .img, it extracts only a big file, maybe binary? I don't know how to open.
I am talking in the livechat of TWRP in freenode, for you, right now, but nobody replies to help (they hardly reply to me there).
I updated the TWRP thread to ask if it's dead or paused, the dev hasn't posted since 22 october. TWRP for whyred seems abandonned or paused.
Try Orangefox anyway, even if it's from TWRP; they have updated plenty of things, such as the "PIN/PATTERN" (an issue I have with latest TWRP, which is not in ORangeFox recovery).
Or yes, try the latest twrp-3.2.3-1-whyred.img (it has no changelogs, I don't know the changes).
---------- Post added at 07:49 PM ---------- Previous post was at 07:33 PM ----------
Looks like you created a bug report #1335 in githubTWRP, I think it's related to #1314 (if so, we will probably need to wait for an update).

2023 SM-G955U/U1/W Rev8 One Click Root/Safestrap Inject Method

Root Method For S8+ U/U1/W Series Phones Rev8 Bootloader
New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation
Paypal email is [email protected]
Before Starting This Process Get A USB2 Mini Hub You Are Most Likely Going Too Need It. Do Not Come In Here And Post This Is Not Working Until You Have Tried It With The USB2 Mini Hub!
You Must Start From Stock U Firmware. IT Seems To Be The Less Likely To Brick Your Device As Explained In The Disclaimer!​Disclaimer Please Read!!
This may brick your device there is a problem especially with s8 and note 8 models where the tz partition becomes corrupted and on some occasions after flashing combination firmware your phone will become bricked and as of now there is no way to fix it. There is no way to predict if it will happen. It doesn’t seem too happen very often on s8+ but it does occasionally happen on the other 2 models so do this at your own risk. I would say it probably happens 10 percent of the time on s8 and note 8 especially when on bit 6 or higher firmwares. S8+ it rarely happens too but it still may. If you take the risk and it happens do not pm me asking how to fix it as of time I posted this there is no way to fix it
Please Read Notes
OEM Toggle Does Nothing On US Model Phones
You will most likely need a USB 2 mini hub for Odin to work if using windows 8 or higher. I would temporarily disable windows defender or antivirus software while performing the procedure with your computer.
You cannot have root on any rom except a nougat rom also flashing custom boot images cannot be done or using systemless magisk. Hiding root or running modules cannot be done. There is no oem unlock and even if there is you cannot unlock your bootloaders or run any aosp based roms.
You can be on any firmware to achieve safestrap but to run a rooted rom you will be limited to using a special nougat android 7 rom. You can have safestrap on pie android 9 which gives you some ability to modify system files flash zips etc and have access too data and other partitions that are normally blocked but you can not run root on android 9 because root on android 9 requires a modified boot image
Anything here with a .7z extension will get unzipped before using
Anything here with a .zip extension will get flashed a zip in safestrap
Anything here with a .tar or .md5 gets flashed in odin
Anything here with a .img extension gets flashed as image in safestrap
Additional Help Can Be Found In The Telegram Channel
Telegram Channel For 8 Series Root
Downloads
Odin3_v3.14.1_3B_PatcheD.7z
SM-G955U_VZW_G955USQU8DUJ1.7z -- Stock U Firmware Flash First In Odin
SAFESTRAP_S8_PLUS_GUI_INSTALLER.7z - GUI 1 Click Method-Recommend!
Alt Method
Safestrap_S8_Plus_Cmd_Line.7z - Command Line 1 Click
Directions Once On Stock U Firmware
If using Safestrap_8_Series_Cmd_Line follow instructions on Cmd screen.
1. Download files and unzip SAFESTRAP_S8_PLUS_GUI_INSTALLER.7z
2. Plug phone into computer and allow access too phone data
3. Run the SAFESTRAP_8_SERIES.exe file. In program choose your model of phone in drop down box then click Root Button and select COMBINATION_FA70_G955USQU8ATG1.tar.md5 file too flash it is packed in the zip you downloaded from above. Everything else is automatically done for you just follow any pop up that come up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Phone will reboot too download and flash combo firmware and then reboot. Click dialog stating that it has rebooted and it will inject safestrap all automatically
5. When done you will have a minimal system with safestrap recovery
Instructions For Installing Rom
System Images
system_g955_nougat.7z - Nougat Image That Can Be Rooted
Pie With Safestrap Stock Roms Un Rooted Found Here
Canadian Roms Found Here
1. From here you will either a nougat or pie system image to your phone which will be flashed in safestrap. Reboot to safestrap using the safestrap control app once in safestrap choose wipe then advanced wipe and wipe data. Then goto home screen of safestrap using install tab and the the flash image tab at bottom. Choose system image you copied to phone. System images get flashed too system partition.
2 My nougat system images are not pre rooted if you want for root you will also need too flash a root zip in safestrap.
Root Zips For Nougat Image
EFTSU_System-v20.4_12_28_22.zip​SuperSU_System_12_28_22.zip​Phhs_SuperSU_S8_S9_Series.zip​3. You can enter safestrap anytime on nougat by simply rebooting to recovery which will enter safestrap or by using the safestrap control app
Fingerprint Fix For Nougat Roms
SM_G955U_FINGERPRINT_FIX.exe
4. If fingerprint not working reboot phone too download mode and run this SM_G955U_FINGERPRINT_FIX.exe
Pie With Safestrap Roms
Full Guide found Here
Video Tutorial
Thank You Liset Pedraza
Method In This Video To Obtain Safestrap Has Changed But The Process Of Using Safestrap Still Pertains
S8_Series_Install_Root.mp4
drive.google.com
Credits
klabit87 - Basically Everything
GSMCHEN - The root method
elliwigy -The root method
afaneh92 -Safestrap and too much too mention[/MEDIA]
oakieville - 1 click method

S8 SM_G950U/U1/W Can Be Found Below
2023 SM-G950U/U1/W Rev8 One Click Root/Safestrap Inject Method
Root Method For S8 U/U1/W Series Phones Rev8 Bootloader New 1 Click Method Brought To Everyone By oakieville He provide this free of charge so If you like maybe give him a little donation Paypal email is [email protected].com Before Starting...
forum.xda-developers.com
N8 SM_N950U/U1/W Can Be Found Below
[NEW METHOD][ROOT] [Extreme Syndicate] [Snapdragon][N950U/U1][V8 Bootloaders]
Root Method For S8/S8+ And Note 8 Series U/U1/W Series Phones Rev8 Bootloader This may brick your device there is a problem especially with s8 and note 8 models where the tz partition becomes corrupted and on some occasions after flashing...
forum.xda-developers.com
​

so if i remain at nougat i should be able to flash custom roms? Also, i'm currently facing "no service" problem on my g995u. Any ideas if going back to nougat would rectify the issue?

jrkruse said:
Rooted Nougat Rom​
This is last nougat rom made for S8 it is prerooted with flashfire and safestrap preinstalled. It has CSC stuff for all carriers added. Its debloated slightly with knox removed. Some stuff may not work but im not sure as I cannot test but this stuff may include fingerprint and or face recognition. If stuff doesnt work it probably related to using pie modems and non-hlos on a nougat rom which you have no choice.​
Downloads
system_s8plus_brb1.7z
BL_G955_NOUGAT_V7.tar.7z
Includes Fingerprint and Face Unlock fix for above nougat rom. Just flash in BL slot in odin after everything else
Magisk_System-v20.4.zip This is system magisk not the normal systemless magisk so magisk hide and modules will not work!
SuperSU_System.zip
Safestrap-4.12-T01-DREAMQLTE_PIE.zip Will boot straight to safestrap only for pie roms
Safestrap-4.12-T01-DREAMQLTE_NOUGAT.zip Will Give you the safestrap splash screen on boot
Directions
Safestrap Method
1. Extract system.img from the system_s8plus_brb1.7z and copy to phone also copy either SuperSu_System.zip or Magisk_System-v20.4.zip reboot to safestarp and flash system image
2. Flash either SuperSu_System.zip or Magisk_System-v20.4.zip
3. Reboot to download and flash BL_G955_NOUGAT_V7.tar.md5 in odin
4. If you get constant rebooting to safestrap flash Nougat safestrap zip while in safestrap
Non Rooted Pie Rom With Safestrap Can Be Found Here
Click to expand...
Click to collapse
unfortunately i got myself a bricked device. no bootloader, no recovery, no charge, nothing...

kkins95 said:
unfortunately i got myself a bricked device. no bootloader, no recovery, no charge, nothing...
Click to expand...
Click to collapse
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk

jrkruse said:
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
nope. no sign of life comming from the phone. just a flicker of white line when i hold volume down and power button. thanks for the response.

kkins95 said:
nope. no sign of life comming from the phone. just a flicker of white line when i hold volume down and power button. thanks for the response.
Click to expand...
Click to collapse
So what exactly happened?
Sent from my iPad using Tapatalk

jrkruse said:
Does computer recognize the phone as a 9008 qualcomm device in device manager of your computer
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
jrkruse said:
So what exactly happened?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
i was on a g995u1 firwmare(bootloader v7) although i was having issues with "no signal". i thought maybe if i follow your guide to return the rom back to nougat my network would return to normal.
i only flashed this file "BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V7.tar.md5".
ps. i did tick the "nand erase" in odin.
the flash completed but my phone went black and did not reboot again.. i disconnected hoping to get it back to download mode again but nothing was working. i have tried using volume down and power keys but this only causes the a little part of the screen to flicker for less than a second.
my battery was 99%. I dont have qualcomm drivers installed. i am installing one as we speak, i have seen some threads with similar issues like mine but no solutions.. thanks for your response..:crying::crying::crying:

kkins95 said:
i was on a g995u1 firwmare(bootloader v7) although i was having issues with "no signal". i thought maybe if i follow your guide to return the rom back to nougat my network would return to normal.
i only flashed this file "BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V7.tar.md5".
ps. i did tick the "nand erase" in odin.
the flash completed but my phone went black and did not reboot again.. i disconnected hoping to get it back to download mode again but nothing was working. i have tried using volume down and power keys but this only causes the a little part of the screen to flicker for less than a second.
my battery was 99%. I dont have qualcomm drivers installed. i am installing one as we speak, i have seen some threads with similar issues like mine but no solutions.. thanks for your response..:crying::crying::crying:
Click to expand...
Click to collapse
It happens once in awhile for no reason. Nand erase may have had something too do with it. I never use nand erase except if going back too totally stock from a modified system. I responded too your pm. You’re phone can probably be fixed with edl files but you are going too have too take your phone apart and jump some test points to make phone enter edl mode
Sent from my iPhone using Tapatalk

jrkruse said:
It happens once in awhile for no reason. Nand erase may have had something too do with it. I never use nand erase except if going back too totally stock from a modified system. I responded too your pm. You’re phone can probably be fixed with edl files but you are going too have too take your phone apart and jump some test points to make phone enter edl mode
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
ive been searching for the edl points for the s955u but to no avail. ive taken apart my phone but cant find any reference online for the edl test points. i dont want to start testing randomly because something i have no idea about might happen..

kkins95 said:
ive been searching for the edl points for the s955u but to no avail. ive taken apart my phone but cant find any reference online for the edl test points. i dont want to start testing randomly because something i have no idea about might happen..
Click to expand...
Click to collapse
I use to have pics and stuff but I lost them on a hard drive that failed. I can tell you they are on the bottom side of the board and you have to pry back a metal heat shield to get too them
Sent from my iPhone using Tapatalk

jrkruse said:
I use to have pics and stuff but I lost them on a hard drive that failed. I can tell you they are on the bottom side of the board and you have to pry back a metal heat shield to get too them
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
kindly help identify them if visible or point out what i am to do next. thanks alot....

kkins95 said:
kindly help identify them if visible or point out what i am to do next. thanks alot....
Click to expand...
Click to collapse
You have to take board out and flip it over. The points are on the bottom side
Sent from my iPad using Tapatalk

jrkruse said:
You have to take board out and flip it over. The points are on the bottom side
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
OK, Thanks for the response. i see two large heat sinks with the larger one at the top and the smaller at the bottom. i assume the points would be hidden underneath the bottom sink. now i have to figure out a way to pry those metals off... so much work..lol..

Will this work on all V7 Bootloaders?
I am currently on DTF4 and noticed your on the Verizon page you posted for the DTB3 Bootloader. Thanks for your time and efforts.

jrkruse said:
This method is brought to you entirely by @elliwigy He is the reason for this exploit and method.
With that being said, Extreme Syndicate Root is now available!
Click to expand...
Click to collapse
jrkruse said:
Rooted Nougat Rom​
Click to expand...
Click to collapse
Thanks this worked for me! Is there a guide on how to reverse everything if I wanted to make the phone normal again? Like it would be factory out of the box?

lonewolf1738 said:
Thanks this worked for me! Is there a guide on how to reverse everything if I wanted to make the phone normal again? Like it would be factory out of the box?
Click to expand...
Click to collapse
Just flash stock firmware in odin
Sent from my iPhone using Tapatalk

I have version 8 files so will make stuff when I get a chance
Sent from my iPhone using Tapatalk

@NateNMad
yeah its on the same bootloader G955USQU7DTF4

[ROOT] [Extreme Syndicate] [Snapdragon][G955U/U1][V7 Bootloaders]
If anyone is thinking on updating phones now is the time. The method of unlocking bootloaders on US variants works one s10/s20 and n10/n20 phones. Read the whole article too get info and yes it works I have a bootloader unlocked sm-g975u s10+ with twrp and magisk installed.
https://www.xda-developers.com/samsung-galaxy-note-20-ultra-root-us-unlocked-snapdragon-865/
Sent from my iPhone using Tapatalk