Related
Okay here we go,
Thanks @pikeylfc for testing. :good:
Rootable Permissive Verity/RIC disabled.
Marvelous Super-Huge Thanks to
@AndroPlus for his kernel source
and helping me out with the kernel.elf situation.
This is in line with AndroPlus's sources at the time I cloned and compiled originally 9th March 2016 for the Z5 premium.
The kernel souce is the same for this device, the kernel was compiled last night.
Download
sxz3plus_ivy_MM_Rootable_Permissive_boot.img
It seems the dsds model may not be unlockable at least in one instance so far.
I'm going to leave this image in place however.
sxz3plus_ivy_dsds_MM_Rootable_Permissive_boot.img
This is for Marshsmellow, it's not rocket-science.
flash by normal means
This image is setup with the bootrec scenario. That information is covered in AndroPlus work and threads.
My defconfigs are attached.
Use @Chainfire 's latest SuperSU, this version will apply root to the boot.img (system-less root).
I do not intend any further effort outside of this.
ATTENTION: I don't have a recovery build for ivy. I don't own the device. The only reason i sorted the kernel for root is because the kernel source is the same from the z3+/z4 to the z5.
Someone who owns the device will have to start picking up proper development. Sorry.
I am still looking for confirmation as to whether or not the bootloader for the dsds model is unlockable, or if there is
some sort of country restriction that applies.
m
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
Click to expand...
Click to collapse
Yes that's what I did
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
Click to expand...
Click to collapse
k,
hi, instead of the "usual" kernel binary + dtb image
this package uses a compressed and concatenated kernel-dtb.
So where the "usual" setup results in a 20+mb kernel binary and a 700+kb - 2mb dt.img [depending]
the resulting image-dtb.gz generated during kernel compilation comes down to roughly 8.3mb total.
And since the ramdisk itself is largely text files with few small compiled binaries in sbin, the ramdisk itself
can be compressed from 13.1mb, uncompressed in this case, down to 6.9mb with gzip compression.
With lzma compression the ramdisk would be 2.8mb
m
Super. Install went perfect. Works as expected. Also flashed -arm64-custom-build-by-wanam-20160211.zip
Gravity works fine. I only tried few mods I used regularly.
Thanks for getting is available. I've been keep searching for past few days since upgrade.
Sent from my E6553 using Tapatalk
krusir said:
The size is like almost 50% of the previous boot-251. Is it correct, wondering why size shrink so much.
30920704 Sep 12 2015 boot-251.img
16293888 Mar 14 14:20 sxz3plus_ivy_MM_Rootable_Permissive_boot.img
Can you confirm the steps?
# Get into flastboot download mode
fastboot flash boot sxz3plus_ivy_MM_Rootable_Permissive_boot.img
fastboot boot recovery.twrp.2.8.7.0.img
in TWRP, flash SuperSU-v2.66.zip
reboot system
Click to expand...
Click to collapse
Hi, I'm a noob regarding root on the Z3+ so I would be very grateful if someone could explain a bit more detailed who this installation should be carried out?
I never rooted my device on lollipop, but I guess that in order to be able to flash this kernel, the bootloader must first be unlocked?
I assume that the procedure has not changed because of the update to MM, so i guess I could find the steps somewhere here in the Z3+/Z4 forum (of course if you want to explain those steps as well I wont protest )
Thanks in advance,
Andreas
Thank you so much! Now I finally got the iOS emojis ♥
Install was easy, boot time was same as normal!
bobboviking said:
Hi, I'm a noob regarding root on the Z3+ so I would be very grateful if someone could explain a bit more detailed who this installation should be carried out?
I never rooted my device on lollipop, but I guess that in order to be able to flash this kernel, the bootloader must first be unlocked?
I assume that the procedure has not changed because of the update to MM, so i guess I could find the steps somewhere here in the Z3+/Z4 forum (of course if you want to explain those steps as well I wont protest )
Thanks in advance,
Andreas
Click to expand...
Click to collapse
Andreas,
provided your device is single sim, just flash the img as normal using fastboot. As per OP this is for the MM firmware release.
If your device is dual sim [dsds] let me know and i will post a dsds version AFTER you post the kernel.sin image from the ftf firmware archive for your device.
NO MEGA! DIE CLOUD DIE !!
m
Its not that complicated, but yes, your bootloader must be unlocked. Once you have that sorted, just use flashtool to flash the firmware (you can download the one you want from within flashtool using xperifirm) by installing fastboot and flashmode drivers (those are in the folder you installed flashtool; on anything above Win8 youll need to turn off driver verification to install these drivers, just google that if you dont know how it works), then choosing flashmode, selecting the firmware and falshing it. If you want to do a clean install, just check all the Wipe settings. Two questions will come up while flashing, just click yes on both.
Then you put the phone into fastboot mode (oh and have supersu on the SD card helps) and once again using flashtool, flash the img file from this thread. Then hotboot into the bootable TWRP, found in some other thread here. The phone will restart into TWRP and there you choose install and install the superSU.zip you copied to your SD card before.
If you dont understand parts of what I said, reconsider if youre really so much into gaining root OR ask
Oh gosh. Do I need to unlock my phone first? Mine is dual sim, I'll post the kernel tomorrow, it's 2 a m here, sorry.
alexander43c said:
Oh gosh. Do I need to unlock my phone first? Mine is dual sim, I'll post the kernel tomorrow, it's 2 a m here, sorry.
Click to expand...
Click to collapse
Good deal :good:
I was waiting for someone with a dsds model to respond.
Again, post it to where i can get it.
NO MEGA! DIE CLOUD DIE !!
m
And yes, always now and forever, you will need to unlock your bootloader.
works perfect here! finally marshmallow, root and xposed! thank you very much !!!
oh and drmrestore.zip also works great! much better camera pictures, x-reality works etc! i'm really excited
Anyone else with system storage being shown as 16 GB?
moonbutt74 said:
Good deal :good:
I was waiting for someone with a dsds model to respond.
Again, post it to where i can get it.
NO MEGA! DIE CLOUD DIE !!
m
And yes, always now and forever, you will need to unlock your bootloader.
Click to expand...
Click to collapse
Here you go.
is gg driver ok by the way?
https://drive.google.com/open?id=0B80b07NYd46FYU5HWEdtaXoydm8
You need to set the sharing option!!!
moonbutt74 said:
You need to set the sharing option!!!
Click to expand...
Click to collapse
I've done that after you tried to get the link. Sorry for the inconvenience. I'll check it again
Sent from my E6533 using Tapatalk
And now you need to post the correct link!!!
alexander43c said:
I've done that after you tried to get the link. Sorry for the inconvenience. I'll check it again
Sent from my E6533 using Tapatalk
Click to expand...
Click to collapse
Okay good :good:
What is the device codename and model number?
derp nevermind , i have too much going on at once xD
moonbutt74 said:
Okay good :good:
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B80b07NYd46FYU5HWEdtaXoydm8
here you are
Has anyone read about Dirty Cow yet?
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
I read over on the V20 forums that one developer was able to get it to root his Note 7 that he refused to return. Surely it can work on the Note 5!?
jellybear456 said:
Has anyone read about Dirty Cow yet?
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
I read over on the V20 forums that one developer was able to get it to root his Note 7 that he refused to return. Surely it can work on the Note 5!?
Click to expand...
Click to collapse
I've said earlier if someone could compile it for me I would give it a try, I am no developer so I really don't know what I'm doing when I comes to that but I know enough to find my way through cmd an adb
Surely since no one has written a reply someone must be working on this, I'm pretty techy but I am in no way shape or form a dev but I am down to help, test or give input where I can.
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
dpwguenther said:
I've said earlier if someone could compile it for me I would give it a try, I am no developer so I really don't know what I'm doing when I comes to that but I know enough to find my way through cmd an adb
Click to expand...
Click to collapse
Message me good sir.
Also the biggest problem is SELINUX is set in bootloader.
Now that it's been proven drammer can flip the memory on the note 5 (tested myself with their test app) we should be able to set SELinux to passive with the right knowhow and then root with dirty cow.
Unfortunately I am not a dev nor do I know how to code android but this all looks promising. Hopefully all the devs haven't moved on from this device (like I'm sure most of us will when our contracts are up).
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Jspex said:
Now that it's been proven drammer can flip the memory on the note 5 (tested myself with their test app) we should be able to set SELinux to passive with the right knowhow and then root with dirty cow.
Unfortunately I am not a dev nor do I know how to code android but this all looks promising. Hopefully all the devs haven't moved on from this device (like I'm sure most of us will when our contracts are up).
Sent from my SAMSUNG-SM-N920A using XDA-Developers mobile app
Click to expand...
Click to collapse
We can already set SELINUX to permissive. The problem is the bootloader sets the kernel to enforcing on everyboot.
TechNyne66 said:
We can already set SELINUX to permissive. The problem is the bootloader sets the kernel to enforcing on everyboot.
Click to expand...
Click to collapse
We cannot set SELINUX in MM..? All the dirtyc0w scripts work fine to get run-as or farm on system of the phone as long as you compile with arm64-v8a. But SELINUX makes dirtyc0w completely useless when trying to drop to root shell...
straby187 said:
We cannot set SELINUX in MM..? All the dirtyc0w scripts work fine to get run-as or farm on system of the phone as long as you compile with arm64-v8a. But SELINUX makes dirtyc0w completely useless when trying to drop to root shell...
Click to expand...
Click to collapse
We can't do anything with MM. I can try to compile whatever if you can get me the files.
If you are still on lollipop with eng kernel tether root. Can you try to pull boot pull boot and recovery
http://forum.xda-developers.com/general/security/farm-root-recovery-image-pulling-t3490089
I can already flash boot and recovery but the att crap that no one seams to understand WILL lock the phone out untill you do a full odin. However maybe some way can work as we haven't tried all but a simple flash of custom recovery to the recovery portion will not work.
What about rowhammer
TechNyne66 said:
I can already flash boot and recovery but the att crap that no one seams to understand WILL lock the phone out untill you do a full odin. However maybe some way can work as we haven't tried all but a simple flash of custom recovery to the recovery portion will not work.
Click to expand...
Click to collapse
i was asking if you could pull the original recovery from the phone, not flash it. I just wanted to get a look at it...
straby187 said:
i was asking if you could pull the original recovery from the phone, not flash it. I just wanted to get a look at it...
Click to expand...
Click to collapse
Yes we already have stock recovery. If you want to message me in the morning I can send it to you.
how is it looking for this new method, I feel like we are really close.
killernos said:
how is it looking for this new method, I feel like we are really close.
Click to expand...
Click to collapse
I can't get a single thing to work. Seams like KEXEC is out best bet and we need to focus all efforts on this. All we need is a custom kernel with kexec support and I can test to see if it will load. I have tried and tried for hours on hours to get a kernel to compile with no success.
I'm new here. Some may know who I am some may not. I just got my note 5 last week after my v10 took a ****......what's kexec and what's the error when compiling
Sent from my SAMSUNG-SM-N920A using Tapatalk
MysteryEmotionz said:
I'm new here. Some may know who I am some may not. I just got my note 5 last week after my v10 took a ****......what's kexec and what's the error when compiling
Click to expand...
Click to collapse
If you have to ask then compiling a kernel is probably beyond your experience (it's well beyond mine and I work in I T )
dezborders said:
If you have to ask then compiling a kernel is probably beyond your experience (it's well beyond mine and I work in I T )
Click to expand...
Click to collapse
You know what your right. I'm just go back into the shadows and continue boot to help. A quick search on xda would have shown you in plenty capable.
PS...When compiling a kernel it normally gives you some kinds of error message so you know where to start lookin
Sent from my SAMSUNG-SM-N920A using Tapatalk
MysteryEmotionz said:
You know what your right. I'm just go back into the shadows and continue boot to help. A quick search on xda would have shown you in plenty capable.
PS...When compiling a kernel it normally gives you some kinds of error message so you know where to start lookin
Click to expand...
Click to collapse
My bad lol no offence intended
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
jayreed1 said:
Hey all,
Since I first unlocked my 10, I've been trying to get a Lineage/CM based rom on the thing with no success. I typically get either a boot loop, or a hard reset to the HTC logo.
Unless people are just lying, CM/Lineage on the Sprint 10 should be possible as I've read many posts claiming so.
I've tried a variety of things including different versions of TWRP from 3.0.3-0 to 3.0.3-6, and multiple Lineage/CM based roms.
One supposition is that my current MM firmware is to blame. I think this may well be the issue; however, I don't know how (if it's even possible) to get my 10 to 2.** firmware, as Sprint has not released this yet.
I just S-Offed my phone, and I'm currently S-Off, Boot Unlocked.
I don't have a Windows computer, but I'm capable of using adb and fastboot. I'm also comfortable using command line tools.
Help!!! Haha, I'm so frustrated with this device!
Thanks in advance!
Click to expand...
Click to collapse
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
tabp0le said:
You need to first flash the firmware for an unlocked device. Then you can RUU back to Sprint and install LOS. @andybones made a custom firmware zip specifically for Sprint to do this.
Click to expand...
Click to collapse
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
jayreed1 said:
Hey,
Thanks for your response.... I can't seem to find his Sprint specific zip. He's quite prolific!
I've found what I believe is the us Unlocked:
2PS6IMG_1.80.617.1_R_firmware.zip
Here
Could you either point me to his zip, or could you verify that if I remove all but firmware from this zip, I should be able to accomplish the same task?
Thanks again!
Click to expand...
Click to collapse
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
andybones said:
Please read this entire thread. You'll find my detailed guide in Post #3. There are also posts in Page #2 with Sprint user (@mcwups1) that will help you out, and possibly reach out to him about his experience, and if he has any tips for you. He is a good man.
Click to expand...
Click to collapse
I read the entire post as you recommended, and I believe I now know how to proceed.
Unfortunately, I've ran myself clear out of free time.
I'll give this a go and report back as soon as I get a few free hours again--probably Friday or so.
Thanks a million!
You guys are very welcome.
Please proceed at your own risk (as with any flashing).
I've tried to make the guide I used as clear as possible and will certainly help if anything is unclear, but keep in mind nougat wasn't out at the time it was created. I don't foresee any issues as really the main thing that is making it boot was anyone that had flashed the us unlocked firmware at any point in time, and I believe people are still converting, The guide is really flashing the us unlocked firmware then back to your (Sprint) RUU.
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
jayreed1 said:
Woot!
This worked. I'm now running los with pico gapps and su.
Thanks all.
For anybody that follows in my path, I'm running arch linux, and the android tools package in extras was all I needed (this was a concern of mine).
I grabbed @andybones' modified vzw zip and simply changed the mid and cid to match my phone in the android text file within.
I then flashed the double modded zip.
Next, I flashed the sprint modified (recovery removed) firmware only ruu.
Los booted fine after this; however, I had no lte. So, I rebooted to boatloader, and erased modems 1 & 2.
Finally!!#?! This has been the most frustrating device I've owned to date, but I'm sitting pretty now.
Thanks again everyone!
Click to expand...
Click to collapse
Nice! Great to finally see some feedback from a sprint user. Wanted to try this myself before I upgrade to nougat firmware. Only thing I'm confused about is you having to erase modem 1&2. What does that mean?
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
jayreed1 said:
For clarification I didn't end up on nougat firmware either. Sprint hasn't released that. Just nougat rom with MM firmware.
After flashing only 3G and cell signal work.
I found in another post (can't find to credit) that a possible fix was to erase modemst1 and modemst2.
To do this, reboot to bootloader.
-> adb reboot bootloader
Then use fastboot to erase modemst 1&2
-> fastboot erase modemst1
-> fastboot erase modemst2
-> fastboot reboot
Also, the lines in the android text file that need to be changed should become.
modelidnum: 2PS640000
cidnum: SPCS_001
Fin
Click to expand...
Click to collapse
Awesome thanks! Sprint released Nougat OTA yesterday and OMJ extracted firmware that we can flash. Sprint Nougat RUU isn't out yet though waiting for it on HTC's site. Check it out on Sprint HTC 10 XDA dev page. If you flash the firmware and everything still works fine please let me know. Should be trying this if I have time tonight. Have a lot of homework :silly:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
andybones said:
I believe there has been a new method found that only involved flashing 1 .img from the US Unlocked firmware that will save a lot of trouble.
If I can find the post I will link it here.
EDIT:
https://forum.xda-developers.com/showpost.php?p=71137922&postcount=866
Click to expand...
Click to collapse
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Sent from my Sprint HTC 10 using Tapatalk
Click to expand...
Click to collapse
Very welcome, least I can do.
Nice work on finding the difference. Will certainly save alot of trouble for many!
guys right now what i have to do?
* i updated my htc 10 sprint till the last MM ota, i didn´t make nougat update
* i unlocked my bootloader and install unoficial twrp that i found here
* i have last viper rom
what should i do so i can install other custom roms because right now i can´t pass the boot logo
i´m s off
---------- Post added at 05:27 AM ---------- Previous post was at 05:19 AM ----------
i just need to flash this?
Attached Files
File Type: zip rfg_3.imgs.zip - [Click for QR Code] (1.91 MB, 12 views)
The Fer-Shiz-Nizzle said:
Thanks, for spreading the word. If it works for others....on Sprint/Verizon...I could make a guide
Click to expand...
Click to collapse
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
beastlymonkey said:
I tried flashing the rfg_3 image on Sprint but got failed (remote: 35 ru_partition_not_support rfg_3). I'm S-OFF and unlocked bootloader. Do you know what may be going on? I'm currently running stock ROM after running nougat RUU with magisk. Thank you.
Click to expand...
Click to collapse
Are you flashing it while in Download mode or bootloader?
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
Are you flashing it while in Download mode or bootloader?
Click to expand...
Click to collapse
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
beastlymonkey said:
Download. I ran the command "fastboot flash rfg_3 US_UL...img" sorry on mobile forgot exact name
Click to expand...
Click to collapse
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Sent from my Sprint HTC 10 using Tapatalk
The Fer-Shiz-Nizzle said:
I thought I flashed it from Download mode, but I just tried it, and got the same error. Then I reboot to bootloader, and tried again and it flashed successfully. So you need to do it from bootloader
Click to expand...
Click to collapse
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
beastlymonkey said:
Cool thanks! I thought you can only do fastboot in download mode? I'll try again later and will let you know. Thanks again
Click to expand...
Click to collapse
Yeah I know TWRP is flashed from Download mode, but some stuff apparently still use the bootloader.
Sent from my Sprint HTC 10 using Tapatalk
Here are the binaries for fastboot you can use on your device. The reason I'm posting them here is because they can really useful if you happen to flash something wrong while on the go. You need another device to connect to via USB to use them.
I cant really post source because I didn't keep it, since I compiled in aosp env, but I can explain how to compile them if anyone really wants. I did made these a while ago but I never tested them until I had to today, because I flashed a kernel while waiting in line behind the 4 slowest human beings in existence at Walmart. To my surprise, it worked I figured I'd have to add a USB library like I had to for adb, but apparently not.
Normally I wouldn't bother posting these, but our device is so finicky that I figure someone else might need them at some point. I didn't change any of the source code of fastboot from the 8.1 branch.
Download : https://androidfilehost.com/?fid=673791459329068348
Reshare or do whatever you want with them.
Make sure pixel 2 is the device that gets the direct USB-C connection.
Finally, don't be dumb with them, act like an adult, and if you get errors there's a good chance I'm not going to go back to fix them so post the relevant line in code that leads to whatever error you get if you want me to help or look at it.
Very cool!
You people flashing things on-the-go which can potentially render your device inoperable until you get fastboot access confuse me haha. But I guess that's JustXDAThings.
Just watch what you flash and use anykernels, not boot images. The Pixel 2 bootchain isn't as fragile as you think once you flash TWRP into the ramdisk. Protect TWRP and you'll hopefully never need to fastboot from a companion device.
MishaalRahman said:
You people flashing things on-the-go which can potentially render your device inoperable until you get fastboot access confuse me haha. But I guess that's JustXDAThings.
Click to expand...
Click to collapse
YOLO.
The way I see it, there are two kinds of developers, the kind that need testers because they have no idea what they're doing, and the kind that test themselves, because they are the only ones that know what they're doing.
I'm about to yolo flash a taimen build I just made, it will most likely fail, but that log and debug info I get from it will be valuable lol.
Good on you to carry around 2 phones though. I ain't got that luxury. Haha so I'm still screwed.
jlee08517 said:
Good on you to carry around 2 phones though. I ain't got that luxury. Haha so I'm still screwed.
Click to expand...
Click to collapse
Well anything that has an arm arm64 arch, like tablets and chromebooks would work too. So it's just convenient, ironically there's code for tcp connections in fastboot, so that's interesting...
Surge1223 said:
Well anything that has an arm arm64 arch, like tablets and chromebooks would work too. So it's just convenient, ironically there's code for tcp connections in fastboot, so that's interesting...
Click to expand...
Click to collapse
I had a device that made use of that fastboot over tcp protocol ;p
Moto G3 Prototype. Comically, it was actually a boot mode with an extended LK (as in when I used a non-proto boot image, the feature was not operable).
The ARM version doesn't seem to work. I get "illegal instruction" no matter what command I try to use.
TheSt33v said:
The ARM version doesn't seem to work. I get "illegal instruction" no matter what command I try to use.
Click to expand...
Click to collapse
@TheSt33v
I've got an older armeabi build that should work for you. Check my Odds and Ends thread, or grab it from the Magisk Modules repo.
osm0sis said:
@TheSt33v
I've got an older armeabi build that should work for you. Check my Odds and Ends thread, or grab it from the Magisk Modules repo.
Click to expand...
Click to collapse
Is it new enough that it will flash the Pixel 2 XL? It doesn't work with older versions.
TheSt33v said:
Is it new enough that it will flash the Pixel 2 XL? It doesn't work with older versions.
Click to expand...
Click to collapse
Well you can try, but probably not then. You'll just need to use a newer device as the host device to flash from.
@Surge1223 I realize this is an older thread but I'm going to ask anyways because after searching around, most I can find are x64 files. I've ordered an arm based Chromebook, am I correct in that this is what's needed to get fastboot and adb working? Thanks
@Surge1223
Just wondering if there's any chance of getting this updated?
The current version is broken, at least, on the Pixel 3. Just tried to use my old Nexus 5X to Update my Pixel with the January update. Going to be computer-less for a while starting next week and was hoping I could use the Nexus for updates.
I bypassed the version check in the flash-all.sh file and tried to run it. Bootloader and radio updated fine. But system (along with product and vendor) were a complete no go. Boot image also updates just fine.
Basically I suspect any simple flashes will work, other than that - nope.
At least it didn't brick the device in any way. I ended up with a December system, vendor, and product along with an updated modem, bootloader, and Magisk patched kernel which all booted fine. Normal update via computer worked so at least I'm good for this month.
Not expecting anything, just hoping maybe you'll update this sometime in the near future.
Thanks for your consideration.
jcmm11 said:
@Surge1223
Just wondering if there's any chance of getting this updated?
The current version is broken, at least, on the Pixel 3. Just tried to use my old Nexus 5X to Update my Pixel with the January update. Going to be computer-less for a while starting next week and was hoping I could use the Nexus for updates.
I bypassed the version check in the flash-all.sh file and tried to run it. Bootloader and radio updated fine. But system (along with product and vendor) were a complete no go. Boot image also updates just fine.
Basically I suspect any simple flashes will work, other than that - nope.
At least it didn't brick the device in any way. I ended up with a December system, vendor, and product along with an updated modem, bootloader, and Magisk patched kernel which all booted fine. Normal update via computer worked so at least I'm good for this month.
Not expecting anything, just hoping maybe you'll update this sometime in the near future.
Thanks for your consideration.
Click to expand...
Click to collapse
Yeah new devices use fastbootd to update vendor system product vbmeta and dtbo, I'll try to update it soon, I'll try to hook it up before next week for ya though.
Surge1223 said:
Yeah new devices use fastbootd to update vendor system product vbmeta and dtbo, I'll try to update it soon, I'll try to hook it up before next week for ya though.
Click to expand...
Click to collapse
I normally wouldn't ask, and if you can't (for whatever reason) that's fine. But you did say you'd try to get this updated. New security patches are due out Monday and it would be real nice if I could apply them ?
If not, I'll live. Thanks, no matter what.
Surge1223 said:
Here are the binaries for fastboot you can use on your device. The reason I'm posting them here is because they can really useful if you happen to flash something wrong while on the go. You need another device to connect to via USB to use them.
I cant really post source because I didn't keep it, since I compiled in aosp env, but I can explain how to compile them if anyone really wants. I did made these a while ago but I never tested them until I had to today, because I flashed a kernel while waiting in line behind the 4 slowest human beings in existence at Walmart. To my surprise, it worked I figured I'd have to add a USB library like I had to for adb, but apparently not.
Normally I wouldn't bother posting these, but our device is so finicky that I figure someone else might need them at some point. I didn't change any of the source code of fastboot from the 8.1 branch.
Download : https://androidfilehost.com/?fid=673791459329068348
Reshare or do whatever you want with them.
Make sure pixel 2 is the device that gets the direct USB-C connection.
Finally, don't be dumb with them, act like an adult, and if you get errors there's a good chance I'm not going to go back to fix them so post the relevant line in code that leads to whatever error you get if you want me to help or look at it.
Click to expand...
Click to collapse
Sorry for bumping an old thread but would you be willing to explain how to compile or upload the fastboot and adb binaries of the latest platform tools? I have a PineBookPro that's running arm64 architecture and was looking for them in the repos but the ones I could find were for api23 and would very much like api30 so I could revive my old p2xl. Thank you for your contribution.
Fe Mike said:
Sorry for bumping all old thread but would you be willing to explain how to compile or upload the fastboot and adb binaries of the latest platform tools? I have a PineBookPro that's running arm64 architecture and was looking for them in the repos but the ones I could find were for api23 and would very much like api30 so I could revive my old p2xl. Thank you for your contribution.
Click to expand...
Click to collapse
Not sure if this helps...I'm on the newest version of Platform tools, I have a pixel 2 xl and have no issues.
cubzfan68 said:
Not sure if this helps...I'm on the newest version of Platform tools, I have a pixel 2 xl and have no issues.
Click to expand...
Click to collapse
It may, are you using fastboot from op on the phone from another arm device or a PC?
Fe Mike said:
It may, are you using fastboot from op on the phone from another arm device or a PC?
Click to expand...
Click to collapse
I use it from a pc
If you mess up your device I'm not responsible, it works for me, and for others. I will help as much as i can, but it is on YOU, the user to follow the prerequisites and read carefully. This zip was created in collaboration with @TxanMoe and myself
This zip can be used to return to the stock rom(for the most part, you'll still have fastboot,root,twrp) as long as you can get into TWRP recovery on the device. It also flashes the modem bands needed for working Sprint LTE(bands 25,26,41, ect.."all the Sprint bands")
Prerequisites:
1. Activate with Sprint first if you intend to use the converted US998 on Sprint!
2. You already crossflashed to US998 if not follow the guide here "Frankenstein method" [https://forum.xda-developers.com/lg...sflashing-t3780969/post76510671#post76510671]
3. You followed the bootloader unlock, root, TWRP "WTF" thread here https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
(US998 to LS998) Downloads: (Sprint LS998 system,boot,modem)* MAKE SURE TO FLASH MAGISK, NO-VERITY OPT ENCRYPT, AND RCD DISABLER BEFORE LEAVING RECOVERY!!*
Sprint 20b
https://drive.google.com/file/d/1aQojUcchnEruHwnecfaVGToxZbmj-UX3/view?usp=drivesdk
Sprint 21a(may security patch)
https://drive.google.com/file/d/1JCalyu7mt8DW6wMWbgGViqj0oi9eUSr7/view?usp=drivesdk
*Instructions*:
a. Make a backup in TWRP of system,boot,and data before proceeding!
b. Reboot to TWRP and wipe data (factory data reset)
c. Install the SPRINTLS998.zip (20b or 21a)from TWRP (Do NOT leave recovery yet)
d. Flash Magisk, no verity encrypt, and RCD disabler(you should already have these files if you followed the WTF thread)
e. Reboot
d. Once booted up you need to connect to WiFi. go to settings, update profile and prl. Reboot
quantemplation said:
For anyone who flashes back to Sprint but needs to edit the APNs still, you can type this in command prompt(from PC)
Code:
adb shell
su
am start -n com.lge.hiddenmenu/com.lge.hiddenmenu.ModemProtocol.ModemProtocolMain
Then go to PDP Setting
Then go to APN setting
Click to expand...
Click to collapse
be sure to thank his post here
https://forum.xda-developers.com/showpost.php?p=76633700&postcount=45
JonnyTrulove said:
@JWnSC thanks to the help of some of you great people in this thread I have had the chance to do this conversion twice now. Both times it worked great but I did have to update the APN settings before getting mobile data to work for me. I know you were kind enough to include screenshots of the right APN settings but I just wanted to share that both times I used the ##SCRTN## dialer code to force OTA provisioning and it worked, so I thought you may want to add that option to your first post. Might be a good option for someone that's in hurry to get connected.
Only negative I can think of is that you would not have tethering unless you were subscribed or you manually added the "Dun" provision to the APN later.
Just wanted to share in case you thought it was worth adding to your original post. If not, no biggie. Thanks
Click to expand...
Click to collapse
Special thanks:
@TxanMoe for finding the bootloader exploit and helping me along the way
@ChazzMatt for his in depth Guides and help in this forum
@SGCMarkus for TWRP recovery for this device and all the roms he provides
@quantemplation
@JonnyTrulove
and to any others I may have missed..
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP(wipe data) install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
SilverZero said:
I'll give this a real-world run-through tomorrow when my new LS998 arrives.
Click to expand...
Click to collapse
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
JWnSC said:
I tested it myself to make sure it works. Working on creating a full back to stock zip for warranty exchange ect.. Will post that after I test and know all is well.
Click to expand...
Click to collapse
Yeah...it sucks we need this...sprint not allowing access to kdz is a load of bs...it is much appreciated that we have you helping to support us sprint users...i am looking back at my past lg phones now to see if i can find the process of creating a working kdz...one of the people i think in the g2 or g3 forums actually created a kdz using the untouched signed lg files and it was fully flashable to get back to 100% stock...i don't know if too much has changed since then to do this again...but it would be nice to have for some...me...i won't be doing anything that removes my bootloader unlock and root...but those with warranty may want to have that ability...thanks to all that have contributed to making this a great device...i missed root on a level people outside these forums may never understand
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
cre4per said:
Could you tell me if i could switch out your LS998 bins for h933 ones? also on my dump from lgup can i just change _com6 to .bin ?
Click to expand...
Click to collapse
Right. change "_COM#" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
JWnSC said:
Right. change "_ whatever com #" to ".bin" should be fine as long as the rsa keys match for the devices you are flashing. Don't flash nougat to Oreo or vice versa
Click to expand...
Click to collapse
perfect will give it a try, hoping this will let me get volte back on mydevice
JWnSC said:
Here is a zip for warranty exchange ect...*NOT Recommended* (you will lose root, TWRP)
https://drive.google.com/file/d/19FHVNn6TS5ybdNIziL1nyKPWcIc_RN0t/view?usp=drivesdk
From TWRP install the FACTORYSPRINT.zip reboot device, update prl and profile, reboot, do a system update
It works. I tested it
Click to expand...
Click to collapse
Could you lock the bootloader after this? Or will it show an error?
guapinoy said:
Could you lock the bootloader after this? Or will it show an error?
Click to expand...
Click to collapse
Bootloader would still be unlocked but the message after every boot would disappear and you won't be able to enter fastboot. (After you do the system update)
I thought after installing the latest update it would lock the bootloader...it didn't, but it did remove the text after every boot saying to lock bootloader and you won't be able to enter fastboot after. Activating developer options will show the boot is still unlocked. It does change the software info to LS99821a instead of US99820a
To lock the bootloader, you could probably flash the other Sprint zip(without flashing magisk ect..) and just sprint recovery or the factory zip. Reboot to bootloader from twrp and lock it that way. Then do the Sprint system update *I have to do more testing tho I don't recommend doing this until it's tested*
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
You can't update profile/ prl on US998 firmware(or at least I couldn't). Backup your setup and try DotOS if you already have working lte. This thread is mainly for users to get lte back. I'm not running the stock Sprint firmware. I switched to stock firmware first to get lte working and switched back to us998 rom.
If you wipe data and flash the SprintLS998.zip you won't have any issues. It already contains the Sprint modem, system, and boot. No need to flash the modem from the other thread.
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Lurien said:
Will flashing the sprint zip only have bands 25,26 &41?? I'm in an area with band 13 also.. Thanks.
Click to expand...
Click to collapse
???
If you flash the Sprint modem you'll have all the Sprint bands.
It's just the US998 does not have LTE bands 26 & 41. So you have to flash the Sprint modem to get them. If the LS998 normally has LTE band 13, then you'll have that.
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
jamesd1085 said:
Have any of our few sprint users taken latest update and tried to bootloader unlock and root their devices?...just wondering if they actually managed to patch it yet...
Click to expand...
Click to collapse
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
JWnSC said:
I tested the latest update, it installed. I dumped the modem, system and boot from it. I can make a zip from it later. My bootloader was still unlocked tho. I plan to lock it and test..been putting it off, don't want to get stuck on stock haha. I need my phone this week. I'll test this weekend. After the latest update it removed the bootloader warning and I couldn't enter fastboot but the bootloader still showed unlocked under developer options.
Click to expand...
Click to collapse
How did you install? Because twrp is there it failed on mine
jamesd1085 said:
How did you install? Because twrp is there it failed on mine
Click to expand...
Click to collapse
I flashed the factory back to stock.zip and went to settings, system update.
Not worth it imo...I was testing the factorysprint.zip to make sure it worked. I can make a flashable zip later(to only include system, modem,boot)..I don't think much changed. Looks like it was just an update to disable fastboot and access to recovery
Omatter4 said:
I have followed WTF thread for my Spring LS998. I have also flashed the modem.bin. I have working LTE on US99820a. I went to try and update PRL and Profile but clicking the buttons does nothing at all. Is this common? Also, i noticed that text messaging are received intermittently. They come in, in bunches, but only immediately after I send out a text. has this happened to anyone else?
I'm assuming if i flash the SPRINTLS998.zip, it will correct this issue, but I don't want to if there is no need and there is a fix. I want to try out DotOS, but don't want to carry my texting and MMS issues over from my current U99820a setup.
Click to expand...
Click to collapse
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
SilverZero said:
The first time I tried the profile and PRL updates they took a while to actually launch. Not sure if yours would if you just waited a bit longer (like a minute). I would try that and then the Sprint zip (that's actually more likely to fix your issue).
Click to expand...
Click to collapse
I had to connect to wifi when i updated profile...it kept telling me to contact carrier when i tried to update through data connection