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
Related
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.
phone will arrive tomorrow. need to know haha
Nothing yet. I got my phone and I've unlocked the bootloader in preparation, but so far no news of recoveries. I have no idea how long this takes because I've never been an early adopter before...
randman2011 said:
Nothing yet. I got my phone and I've unlocked the bootloader in preparation, but so far no news of recoveries. I have no idea how long this takes because I've never been an early adopter before...
Click to expand...
Click to collapse
Could you check the key combination needed to cold boot in to fastboot mode please. Im assuming its volume down and power together from a shut down.
Thanks, Mark.
It is.
randman2011 said:
It is.
Click to expand...
Click to collapse
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.
mskip said:
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.
Click to expand...
Click to collapse
It is encrypted with no option to disable it.
mskip said:
Thanks, last question before I can release my Toolkit for this device. Is forced encryption enable by default on this device (if you don't know then you can find the answer in Settings, Security)? If so I can easily enable the no encryption option in the Unified Android Toolkit.
Mark.
Click to expand...
Click to collapse
You have a custom recovery and / or modified boot image for the Nexus 5X?!
oscillik said:
You have a custom recovery and / or modified boot image for the Nexus 5X?!
Click to expand...
Click to collapse
No sorry there isn't one available yet but all options apart from recovery based ones are enabled including disabling forced encryption and flashing stock images (or parts of).
I have to go out now but have uploaded the Toolkit and will make a new thread in the Original Android Development section when I get back in a few hours.
Mark.
Waiting for custom recoveries! OP2 got custom recovery faster
mskip said:
No sorry there isn't one available yet but all options apart from recovery based ones are enabled including disabling forced encryption and flashing stock images (or parts of).
I have to go out now but have uploaded the Toolkit and will make a new thread in the Original Android Development section when I get back in a few hours.
Mark.
Click to expand...
Click to collapse
modified boot image - bullhead-mdb08i-boot.zip http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
i did a factory reset after i fastboot flashed the boot image for encryption to be off. https://goo.gl/photos/Wq6bMCqD1XVBWQdQ9
dees_troy said he might be able to take a stab at making a recovery later today, if he can get around to it and figure it out, rooting should be easy. otherwise i was thinking about repacking the system.img with su and seeing if that works.
{
"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"
}
renzyyy said:
modified boot image - bullhead-mdb08i-boot.zip http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
i did a factory reset after i fastboot flashed the boot image for encryption to be off. https://goo.gl/photos/Wq6bMCqD1XVBWQdQ9
dees_troy said he might be able to take a stab at making a recovery later today, if he can get around to it and figure it out, rooting should be easy. otherwise i was thinking about repacking the system.img with su and seeing if that works.
Click to expand...
Click to collapse
I have a no encyption patched stock kernel included in the Toolkit with automation to make it easier for the average user.
You can certainly repack the system image to include root but if you are publishing it you will also need to include chainfires patched kernel (the one you linked to) to flash with the modified system image or the system will go in to a bootloop (requirement of Android 6 root at the moment. I may look at it later but I have no Nexus 5X to test anything on.
I have published the new Toolkit with the Nexus 5X added and made an xda thread *HERE*.
One thing, does the Nexus 5X suffer from the same problem as other Nexus devices, where the USB mode switches back from PTP mode (for adb commands) back to Charging only on EVERY reboot. Its a pain in the ass and always switches back even if the mode is set in developer options.
Mark.
roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625
renzyyy said:
roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse
I'll give you a cookie for that root
just a word of advice - make sure your phone is already running build MDB08I, and not any other build, before you flash that modified boot img: I just tried flashing it, and it just sticks on boot animation. My Nexus 5X is currently running MDA89E
renzyyy said:
roooooooot!
---------- Post added at 03:38 PM ---------- Previous post was at 03:00 PM ----------
Dees_Troy posted the recovery btw, http://forum.xda-developers.com/showthread.php?t=1943625
Click to expand...
Click to collapse
Any idea if it is safe to re-enable encryption after flashing the modified boot.img, factory wipe, TWRP flash?
bqq100 said:
Any idea if it is safe to re-enable encryption after flashing the modified boot.img, factory wipe, TWRP flash?
Click to expand...
Click to collapse
my guess is that you can, but then you wont be able to use recovery again. dont quote me on that, ive never tried re-enabling it.
oscillik said:
just a word of advice - make sure your phone is already running build MDB08I, and not any other build, before you flash that modified boot img: I just tried flashing it, and it just sticks on boot animation. My Nexus 5X is currently running MDA89E
Click to expand...
Click to collapse
I modified the mda89e and mda89f stock boot images for no-force encryption and re-packed them for use with the android toolkit. If you have MDA89E try flashing *THIS* image and see if it fixes the bootloop problem.
Mark.
mskip said:
One thing, does the Nexus 5X suffer from the same problem as other Nexus devices, where the USB mode switches back from PTP mode (for adb commands) back to Charging only on EVERY reboot. Its a pain in the ass and always switches back even if the mode is set in developer options.
Mark.
Click to expand...
Click to collapse
Yes it still makes you do that Although my N6 did not require it to be toggled after every reboot like the N5X does. It needs to be in PTP to get ADB commands to work, on my windows machine that is, not on the Mac.
mskip said:
I modified the mda89e and mda89f stock boot images for no-force encryption and re-packed them for use with the android toolkit. If you have MDA89E try flashing *THIS* image and see if it fixes the bootloop problem.
Mark.
Click to expand...
Click to collapse
The link doesn't seem to work , need a username and password.
Hayth said:
The link doesn't seem to work , need a username and password.
Click to expand...
Click to collapse
He put it up as an sftp:// (protocol for secure ftp) link. Try this one instead: http://skipsoft.net/tempuploads/boot_images/boot-noforce-encrypt-mda89e-bullhead.img
{
"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"
}
LG-VS996 20D ROMHello everyone
Users have requested that i can make a flashable Zip for the VS996. Hope it will be supported as with my other roms.
Rom ist Untested. Use it at your own risk! When somebody Tell me it Works then I will edit it
This Rom is 100% Stock. TWRP 3.2.1-0 must first be installed as with Nougat Roms. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. I changed the Boot.img, so you do not have to reinstall TWRP. . .
I had made this for users who can not get ota's because they have Custom Recovery / Root installed
Sorry for my bad english i'm out of practice
Features *Stock build made from official KDZ
*Stock Build.prop
*Unrooted
*Boot.img modified to keep TWRP
*Remove dm-verity
*Remove forceencryptInstallation What you need *Unlocked Bootloader [How to do]
*Working TWRP installed [Link to unofficial TWRP]
*When you need Root, Latest Magisk [Download]
*VS99620D(TWRP).zip [Download]
How to install When you are on Nougat: Reboot to recovery using button combo or reboot app (need root)
flash this TWRP.img Download reboot and Backup Dalvik,ART, Cache, System & Data (include not your internal memory) and Boot
in to your external sd or copy the backup from internal sd to your PC!
From Oreo: Install TWRP with this guide but with this img
For clean install: Wipe Dalvik/ART, Cache, System and Data (Recommend)
You can also keep your data by dirty flashing the zip. *Not tested!!!*
Flash VS99620D(TWRP).zip
then Magisk zip when you need root
Reboot System
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no
Here you can find my other [Downloads.] There are IMG´s, KDZ´z and more!
Rom Version
Android Version: 8.0
Android security patch level: 2018-05-01
Build date: 2018-06-14
MD5 SUMS:
Code:
[SIZE="4"][B][COLOR="Black"]boot.img 83cb7cabbd00f350c1a45b98d3f18313
modem.img 7c1d10c66f4a78ab583b0475537e33d0
persist.img 72aef7ed23519596ffc383c293f44474
rct.img 15bc82584049ec3a7c62d921c2897267
system.img 1a7ff1e9a2a664688a3c02b4857d3936
abl.img dcfe3827b4cb01b5016cd3751d6d78b3
apdp.img 60c2f929d5448404903c8a5f6c6599af
cmnlib.img 29acea73f83c2f4ec26d5d2898cd8b28
cmnlib64.img 1ca80dd965ba9cfdfaf0605fdc21ba6c
devcfg.img 6249eb8903db67633873845caf05c438
factory.img 15bc82584049ec3a7c62d921c2897267
hyp.img 20cbbea9743d6aa98ac2ecce4de28b5f
keymaster.img 8c27f3fdc8e1ffddecd2648d2e971658
laf.img 977a4de4b9cb6627a439eb53efb734a0
logfs.img c040a889d66a4f120f502f89b551f42b
msadp.img db354ccaabab3047db144fe04170560a
pmic.img dce34045db2954afbbbe6a5c81bb5634
raw_resources.img 8158fdcbf5f694db7dfcc032cc5d3b54
rpm.img 31e00d62598147a46f312c540cd0c5d4
sec.img 51963cce13001dc4d34baef78b1f9c3a
storsec.img 388d0392f31278d6b0f2a651ad3ef1da
tz.img f7daaa57bfa6ab5a71dfff4901b5d27e
xbl.img 74d1de6992b67e6a808616c8904585cd[/COLOR][/B][/SIZE]
Credits:
@autoprime
@SGCMarkus
@Chainfire
@topjohnwu
@Me :laugh:
Don´t forget to hit the thanks-button if you like my work! :good:
You want to help me with a [donation?] Feel free to make it.
Thanks so much OP!!! Will DL and test!, Will report back.
EDIT>>>>IT WORKS! Thanks OP!
Thanx! donation sent :good:
Visual Voicemail! Visual Voicemail! Visual Voicemail!
OMG!
OMG!
OMG!
Seriously, thanks Westwood24!
Downloaded and installed. Got a Verizon update notification and switched back to DotOS. I flashed everything that needed to be flashed and still got the Verizon update notification.
Can I flash this in TWRP to a "US998" (frankensteined from LS998 hardware), or do i need to frankenstein to VS996 first? I'm on Verizon and want working WiFi calling. All of the links i've read for WiFi calling have been dead ends.
d3structive_pyr0 said:
Can I flash this in TWRP to a "US998" (frankensteined from LS998 hardware), or do i need to frankenstein to VS996 first? I'm on Verizon and want working WiFi calling. All of the links i've read for WiFi calling have been dead ends.
Click to expand...
Click to collapse
Yes.
---------- Post added at 07:54 AM ---------- Previous post was at 07:52 AM ----------
WebDev28 said:
Downloaded and installed. Got a Verizon update notification and switched back to DotOS. I flashed everything that needed to be flashed and still got the Verizon update notification.
Click to expand...
Click to collapse
Because there is a newer update. You dont have to install it. You could also just freeze the OTA app with titanium, and no more notification.
Just dirty flashed everything is working fine. Noticed Verizon must have removed OEM bootloader unlock in developer options. Root and TWRP are fully functional. I get an app closure called quality data log service but that must be a Verizon thing also no big deal.:good:
4stringenator said:
Just dirty flashed everything is working fine. Noticed Verizon must have removed OEM bootloader unlock in developer options. Root and TWRP are fully functional. I get an app closure called quality data log service but that must be a Verizon thing also no big deal.:good:
Click to expand...
Click to collapse
It is a Verizon thing. You can freeze it using titanium, or just delete the app. Problem solved.
WebDev28 said:
Downloaded and installed. Got a Verizon update notification and switched back to DotOS. I flashed everything that needed to be flashed and still got the Verizon update notification.
Click to expand...
Click to collapse
You don't have to install the update. Just freeze in Titanium. It's "stock" Verizon except for custom recovery, so there will be some customization you have to do yourself.
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
4stringenator said:
Just dirty flashed everything is working fine. Noticed Verizon must have removed OEM bootloader unlock in developer options. Root and TWRP are fully functional. I get an app closure called quality data log service but that must be a Verizon thing also no big deal.:good:
Click to expand...
Click to collapse
Yes, and you also do not get the bootloader unlock warning --even though the bootloader is still unlocked.
UPDATE!!! got it to work. i had to format date before flashing in twrp. setting up phone now. may add this into the how to install as a "if you get this error do this" for others that may run into this and panic like i did lol thanks again for making this!!!!
i get this image after flashing (not my picture just found on google but its the same thing but with white background)
wiped everything in twrp then installed. installed fine. after verizon boot animation i get this ill click reset phone and i just get taken into twrp. i will do a factory reset. doesn't help. i did the hold power and volume down to get into the reset phone menu chose to reset. just takes me back to twrp.
I set aside time today to port my converted LS998 from US998 to VS996. Everything went smoothly. Since I had the time, I dirty flashed first to see how/if it would work. I figured if it didn't go well, I would just do a clean install, but so far (4 hrs), I haven't yet seen had any noticeable problems. I froze the FOTA app, which I'm hoping is the correct one to prevent future Verizon updates.
From what I can tell, the VS996 ROM added the following apps:
Android Wear
Caller Name ID
Cloud
Hellp
Hum
Mobile Hotspot
NFL Mobile
Security and Privacy
Slacker Radio
ThinkFree Viewer
Email
Messaging
Voicemail
The items that went missing:
lg mobile (Switch?) ... don't know what the full app name is
Smart Clean(ing?) ... again, missing the full name
Smart World
Quick Help
Tasks
Safety Net reports invalid response in Magisk for a US998 flashing this rom
BHB78 said:
Safety Net reports invalid response in Magisk for a US998 flashing this rom
Click to expand...
Click to collapse
Just a Magisk Manager issue that appeared recently. SafetyNet Helper reported everything as fine.
my.ads0 said:
I set aside time today to port my converted LS998 from US998 to VS996. Everything went smoothly. Since I had the time, I dirty flashed first to see how/if it would work. I figured if it didn't go well, I would just do a clean install, but so far (4 hrs), I haven't yet seen had any noticeable problems. I froze the FOTA app, which I'm hoping is the correct one to prevent future Verizon updates.
From what I can tell, the VS996 ROM added the following apps:
Android Wear
Caller Name ID
Cloud
Hellp
Hum
Mobile Hotspot
NFL Mobile
Security and Privacy
Slacker Radio
ThinkFree Viewer
Email
Messaging
Voicemail
The items that went missing:
lg mobile (Switch?) ... don't know what the full app name is
Smart Clean(ing?) ... again, missing the full name
Smart World
Quick Help
Tasks
Click to expand...
Click to collapse
Wifi Calling. does that work??
johnp357 said:
Wifi Calling. does that work??
Click to expand...
Click to collapse
Confirmed WiFi Calling works.
my.ads0 said:
I set aside time today to port my converted LS998 from US998 to VS996. Everything went smoothly. Since I had the time, I dirty flashed first to see how/if it would work. I figured if it didn't go well, I would just do a clean install, but so far (4 hrs), I haven't yet seen had any noticeable problems. I froze the FOTA app, which I'm hoping is the correct one to prevent future Verizon updates.
From what I can tell, the VS996 ROM added the following apps:
Android Wear
Caller Name ID
Cloud
Hellp
Hum
Mobile Hotspot
NFL Mobile
Security and Privacy
Slacker Radio
ThinkFree Viewer
Email
Messaging
Voicemail
The items that went missing:
lg mobile (Switch?) ... don't know what the full app name is
Smart Clean(ing?) ... again, missing the full name
Smart World
Quick Help
Tasks
Click to expand...
Click to collapse
BHB78 said:
Confirmed WiFi Calling works.
Click to expand...
Click to collapse
outstanding... I will give this a spin. any other warnings or cautions?
johnp357 said:
Wifi Calling. does that work??
Click to expand...
Click to collapse
BHB78 said:
Confirmed WiFi Calling works.
Click to expand...
Click to collapse
What he said!
Had to go into Settings-->Advanced Calling to turn it on, but I can confirm that WiFi Calling shows up when making a call while connected to my home router. Visual voicemail is working too. Those are the 2 main reasons for me wanting to switch from US to VS.
Additionally, as has been mentioned in other threads, my phone now finds and gets the Verizon signal more quickly on this rom than the US998 one. Whereas I used to have to wait for the phone to fully boot to desktop and (seemingly having to wait for most) background processes to finish, I now get full signal immediately upon hitting the desktop.
johnp357 said:
outstanding... I will give this a spin. any other warnings or cautions?
Click to expand...
Click to collapse
Yes, lost of service and wifi w/ Magisk Beta install. Seemed to work fine otherwise, until beta install. Then reboots to have loss of service and disabled wifi. Restored state previous to Magisk beta install corrected this.
johnp357 said:
outstanding... I will give this a spin. any other warnings or cautions?
Click to expand...
Click to collapse
I have no warnings to offer.
Nandroid just in case.
I wiped dalvik cache before flashing.
I flashed VS996 zip.
I wiped dalvik cache again.
I forgot to flash magisk, so I had to adb reboot, wiped dalvik, flashed magisk, wiped dalvik and that was it. I could just be lucky, but everything's went smoothly for me.
---------- Post added at 08:41 PM ---------- Previous post was at 08:39 PM ----------
BHB78 said:
Yes, lost of service and wifi w/ Magisk Beta install. Seemed to work fine otherwise, until beta install. Then reboots to have loss of service and disabled wifi. Restored state previous to Magisk beta install corrected this.
Click to expand...
Click to collapse
I installed latest stable 16 as stated in OP and everything seems fine on my end.
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.zipSuperSU_System_12_28_22.zipPhhs_SuperSU_S8_S9_Series.zip3. 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
@ECHO OFF
:: Copyright 2012 The Android Open Source Project
::
:: Licensed under the Apache License, Version 2.0 (the "License");
:: you may not use this file except in compliance with the License.
:: You may obtain a copy of the License at
::
:: http://www.apache.org/licenses/LICENSE-2.0
::
:: Unless required by applicable law or agreed to in writing, software
:: distributed under the License is distributed on an "AS IS" BASIS,
:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
:: See the License for the specific language governing permissions and
:: limitations under the License.
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot --slot all flash bootloader bootloader-raven-slider-1.2-8739948.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot --slot all flash radio radio-raven-g5123b-102852-220720-b-8851166.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot --slot all update image-raven-tp1a.220624.021.zip
echo Press any key to exit...
pause >nul
exit
Click to expand...
Click to collapse
I just used this script to upgrade to android 13, and during flashing I got this message. Please reply as soon as you can to help, i tried
Click to expand...
Click to collapse
fastboot --slot all update image-raven-tp1a.220624.021.zip
Click to expand...
Click to collapse
and i got the same error.
View attachment 5689079
Use flashtool. It's safer and easier
fil3s said:
Use flashtool. It's safer and easier
Click to expand...
Click to collapse
Ok, I have managed to flash it. I removed the --slot all and it flashed. Should I reboot and flash the other slot now. As for the flashtool, I didn't use it because of this slot business, otherwise I normally use that.
Flashtool will do all required work. I would use that to fix the device if it were me
fil3s said:
Flashtool will do all required work. I would use that to fix the device if it were me
Click to expand...
Click to collapse
So you think I should just go into flash tool, and "update", as I would normally? Just select the 13 public branch and flash it with wipe, force flash, and lock bootloader off? Like this?
{
"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"
}
Divine Bicycle said:
So you think I should just go into flash tool, and "update", as I would normally? Just select the 13 public branch and flash it with wipe, force flash, and lock bootloader off? Like this?View attachment 5689131
Click to expand...
Click to collapse
Tick wipe device and force flash a13
fil3s said:
Tick wipe device and force flash a13
Click to expand...
Click to collapse
You think I should wipe my device? I don't really want to do that
Divine Bicycle said:
You think I should wipe my device? I don't really want to do that
Click to expand...
Click to collapse
I would myself. But it's up to you, if it fails, is go back and wipe it and force flash.
fil3s said:
I would myself. But it's up to you, if it fails, is go back and wipe it and force flash.
Click to expand...
Click to collapse
So, let me check (sorry for repeating myself, I really can't afford to lose my phone, not just because of money but because without it I can't go anywhere at all), you think I can try the Android Flash tool to flash Android 13 again, without wiping or force flashing the partitions. However if that fails, which would be a non-brick failure, just like what happened then, I could wipe the device, correct?
Divine Bicycle said:
So, let me check (sorry for repeating myself, I really can't afford to lose my phone, not just because of money but because without it I can't go anywhere at all), you think I can try the Android Flash tool to flash Android 13 again, without wiping or force flashing the partitions. However if that fails, which would be a non-brick failure, just like what happened then, I could wipe the device, correct?
Click to expand...
Click to collapse
Flashtool is pretty reliable. It's your responsibility. I wouldn't try to keep data personally. I'd just focus on flashing it so it works. A wipe will work for sure.
fil3s said:
Flashtool is pretty reliable. It's your responsibility. I wouldn't try to keep data personally. I'd just focus on flashing it so it works. A wipe will work for sure.
Click to expand...
Click to collapse
Ok, I will try. I really hope this doesn't brick it.
fil3s said:
Flashtool is pretty reliable. It's your responsibility. I wouldn't try to keep data personally. I'd just focus on flashing it so it works. A wipe will work for sure.
Click to expand...
Click to collapse
It seems to have worked, I will now use the factory image to create a patched Magisk image and boot that. Then use direct install to install it. Will report back. The phone has booted successfully.
Ok, Magisk is working, trying to check the versions of slots a and b, not entirely sure how to do that. Also trying to install the kirisakura kernel.
@fil3s @V0latyle Thanks for your help, I have successfully installed the Kirisakura kernel, and everthing seems to be working. My device just restarted itself and did the progress bar logo as if it updated itself? but came back to normal without bootlooping or any other weird stuff. Maybe this should be put as a warning: If you get this error, don't use --slot all? That would have prevented me from freaking out haha.
Divine Bicycle said:
@fil3s @V0latyle Thanks for your help, I have successfully installed the Kirisakura kernel, and everthing seems to be working. My device just restarted itself and did the progress bar logo as if it updated itself? but came back to normal without bootlooping or any other weird stuff. Maybe this should be put as a warning: If you get this error, don't use --slot all? That would have prevented me from freaking out haha.
Click to expand...
Click to collapse
You're welcome! Enjoy.
Divine Bicycle said:
@fil3s @V0latyle Thanks for your help, I have successfully installed the Kirisakura kernel, and everthing seems to be working. My device just restarted itself and did the progress bar logo as if it updated itself? but came back to normal without bootlooping or any other weird stuff. Maybe this should be put as a warning: If you get this error, don't use --slot all? That would have prevented me from freaking out haha.
Click to expand...
Click to collapse
I don't think that had anything to do with it, I'm not sure what issue you had.
V0latyle said:
I don't think that had anything to do with it, I'm not sure what issue you had.
Click to expand...
Click to collapse
Here's the issue.
Divine Bicycle said:
View attachment 5689175
Here's the issue.
Click to expand...
Click to collapse
Right, I don't think flashing to both slots caused this.
V0latyle said:
I don't think that had anything to do with it, I'm not sure what issue you had.
Click to expand...
Click to collapse
View attachment 5689175
Here's the issue IGNORE THIS : just realised I sent this twice. I smol brain
Well, the only difference once I got it to work in the command was removing --slots all, I even tried redownloading the platform tools which did nothing.
V0latyle said:
Right, I don't think flashing to both slots caused this.
Click to expand...
Click to collapse