Hi. I apparently got so lazy, I missed the LineageOS + micorG version 19 upgrade. To be clear, I'm on version 18, and 20 is now out. I went to their build page, and it's not paginated, and all I see is version 20. I'm happy to skip a version if it's safe and nothing will break. But I'm guessing that is not the case, or would probably be preferable to be extra safe, that I shouldn't skip a version.
Does anyone know where I can get the version 19 image?
prot0byte said:
Hi. I apparently got so lazy, I missed the LineageOS + micorG version 19 upgrade. To be clear, I'm on version 18, and 20 is now out. I went to their build page, and it's not paginated, and all I see is version 20. I'm happy to skip a version if it's safe and nothing will break. But I'm guessing that is not the case, or would probably be preferable to be extra safe, that I shouldn't skip a version.
Does anyone know where I can get the version 19 image?
Click to expand...
Click to collapse
Looks like it's here! Hope this helps.
@ethical_haquer Thank you. This does help. When I have a chance to try this I will, and let you know. I can start a new thread if this follow up question is misplaced or inappropriate for this. But by chance, can you tell me. If I'm upgrading from 18 to 19, is it necessary to also do the firmware upgrade as well? I thought I recalled doing this last time. But the LineageOS documentation doesn't seem to say that it's required. I am planning on not only upgrading LineageOS, but the version of Android too. I think this means "Yes, I do need to do the firmware as well". Right?
prot0byte said:
@ethical_haquer Thank you. This does help. When I have a chance to try this I will, and let you know. I can start a new thread if this follow up question is misplaced or inappropriate for this. But by chance, can you tell me. If I'm upgrading from 18 to 19, is it necessary to also do the firmware upgrade as well? I thought I recalled doing this last time. But the LineageOS documentation doesn't seem to say that it's required. I am planning on not only upgrading LineageOS, but the version of Android too. I think this means "Yes, I do need to do the firmware as well". Right?
Click to expand...
Click to collapse
Researching.........
prot0byte said:
@ethical_haquer Thank you. This does help. When I have a chance to try this I will, and let you know. I can start a new thread if this follow up question is misplaced or inappropriate for this. But by chance, can you tell me. If I'm upgrading from 18 to 19, is it necessary to also do the firmware upgrade as well? I thought I recalled doing this last time. But the LineageOS documentation doesn't seem to say that it's required. I am planning on not only upgrading LineageOS, but the version of Android too. I think this means "Yes, I do need to do the firmware as well". Right?
Click to expand...
Click to collapse
If you look at lineage.microg.org, click on "Installation", and then scroll down some it says:
Upgrade
To upgrade from one LineageOS for microG major version (15.1, 16.0, 17.1 or 18.1) to another, follow the instrucions for your device here.
Click to expand...
Click to collapse
As you can see, the link is broken, but the upgrade instructions for your device should work just fine. Just remember to flash the right packages.
Thank you. So yeah, that's the thing. I did see this, but the upgrade doc says nothing about flashing anything, just sideloading the Lineage zip. Also, it says nothing about upgrading the firmware.
So I sort of maintain my own documents for situations like this, where the last time I did this from 17 -> 18. I specifically noted that I had to also upgrade the firmware myself. THEN AFTER that was done, I could upgrade the LineageOS. I also recall their older version of docs (which was recent when I was doing the 17 -> 18) it said you had to do this step. But I can't see the historical versions of their docs, so I can't link it to you or prove it. But now their recent ones don't mention it all. Or maybe I'm just crazy and it didn't have this.
My fear is that, since I can't see what their docs where like from 18 -> 19 (the one I'm trying to do in order to upgrade to 20 next, because I was lazy and didn't do it in time) what if for the specific upgrade I'm trying to do, it also requires manually upgrading the Android firmware. And for some reason the upgrade to 20 does not?
You don't happen to know in your experience of upgrading LineageOS if you ever had to upgrade the Android Firmware separately, do you?
Related
Hello everyone.
Is there a one true guide to installing a ROM on my Note 3? I'm running a T-Mobile N-900T. It seems that after browsing the web, I've seen so many different ways to install a ROM that I'm extremely hesitant to try one on the off-chance that it is no longer supported and may brick my device. This is a non-warrantied phone (bought it on Swappa) so I only get once chance if I end up Hard Bricking it, so my fear level is at the absolute highest.
I wanted to run Eclipse Note 3 TW Rom (found here: http://forum.xda-developers.com/showthread.php?t=2620723) because it's a nice simple ROM that retains S-Pen function and removes all the bloat and stuff. However, I noticed that it says "This is based off of 4.4.2 NC2 for Verizon Wireless." Does this mean it won't work with a T-Mobile Note 3?
This is as far as I got in towards the process before I stopped due to something unexpected:
1) TowelRoot. Rooted it and confirmed with the Root app that it was indeed rooted.
2) Downloaded SuperSU. I installed the binary using the Normal mode since I didn't have CWM or TWRM at the time. It asked me to disable KNOX and it looks like it was fine. I restarted it.
This is where I stopped. After I installed it, it asked me to confirm if I want to confirm allowing Freedom and SetCPU. I did and it continuously started spamming the notification that it was allowed for 20 minutes.
I went into the SuperSU program to see what's wrong and it then told me that the Binary could NOT be found and that I may have to flash my rom back to get it back to normal. It then gave me the error that something was wrong on my phone and that I might have to install something called Samsung Kies to make it better.
I pretty much freaked out at this point and de-installed SuperSU out of fear that I might screw up my phone. Now I'm extremely fearful to do anything without seeing some sort of de facto guide on what to do next.
If it helps, here's the phone information I have. I know that different ROM flashing methods are used for various kernels.
Model: SM-N900T
Android Version: 4.4.2
Baseband: N900TUVUCNB4
Kernel: 3.4.0-660648 | [email protected] #1 | Wed Feb 12 21:31:27 KST 2014
Build Number: KOT49H.N900TUVUCNB4
SE for Android Status: Enforcing | SEPF_SM-900T_4.4.2_0005 | WED FEB 12 21:31:01 2014
Security Software Version: MDF v1.0 Release 2
I have a 128GB Samsung SDXS MicroSD. The phone recognizes 119 GB of it which I know is normal.
Any help or direction would be most appreciated. The world of Flashing has so many roads that my head is spinning and my fear is that I will turn this phone into a $500 brick because I followed the wrong guide.
Thank you.
Best way of flashing a new rom is using "Odin".
dodoqq said:
Best way of flashing a new rom is using "Odin".
Click to expand...
Click to collapse
Thanks.
I do understand that and I have the program, but I can't find any SOLID documentation. I see all these different guides out there and I'm scared that I'm going to pick the wrong one. The ages vary as well, so I don't know if they are still relevant or not.
Not only that, I don't believe that just Odin is enough. There are also prerequisites that are required before I can just up and use Odin. That'st he part that I would hope a decent guide out there would provide me.
A bit early by a few minutes but, Bump for help.
Any information or leads would be terrific.
Thank you.
Nanaya Shiki said:
A bit early by a few minutes but, Bump for help.
Any information or leads would be terrific.
Thank you.
Click to expand...
Click to collapse
Contact me on Google+, I can help you with this and calm you down about it.
It's +NicholasPhilipChum
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
CKR83 said:
I'm pretty new to the Android phones. I bought a Samsung Galaxy Note 8 tablet about a year ago, and I absolutely love it -- which was the only reason why I considered an Android phone when it came time to upgrade. That might have been a mistake.
The phone I chose was a Galaxy S5 from AT&T.
For many reasons I won't go into (and that many of you probably know) Kitkat is awful. Removing SD card access removed one of the most important reasons that I bought the phone. So, I decided to root the thing.
I read a bunch of info on how to root, and, eventually downloaded and tried to use towelroot only to discover that AT&T/Google have blocked all functionality of that program. My build is, unfortunately, the latest build -- July 22 2014 (or there abouts).
Now, I'm not sure if the phone was given to me with that update -- I only got the thing on Sunday. Maybe it was, maybe not. Dunno. So I have a couple of questions.
If I were to factory reset the phone, would that roll back these "Security" OTA updates that were pushed onto the phone? I'm pretty sure there was at least one after I got the thing. I've spent a fair amount of time setting the phone up, but I'll do it again if a factory reset would allow me to root the phone and return the SD card functions.
Is there a way to push an earlier version of the ROM onto the phone. I'm guessing not, since I think I read that AT&T helpfully locked the bootloader.
Finally, does anyone know of any way to root this device if neither of the two paths I presented above will work?
Thanks for any help. If I can't restore the SD card functionality, I'll probably just return the phone. That would be a bummer because I was really excited about it.
Click to expand...
Click to collapse
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Rooting Help?
fgth90 said:
For rooting, go there http://forum.xda-developers.com/showthread.php?t=2696537
or there http://forum.xda-developers.com/showthread.php?t=1980683
Follow tuto or ask here.
You have to give more info (S5 model, firmware...)
Good luck
Franky
Click to expand...
Click to collapse
I see that there are tutes here, and am wading through the 50+ pages of forum posts to find what I need. However, my worry is that none of this stuff will work because of the new firmware. Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Thanks all the pertinent info, I think.
Because the update was so new, I don't think there's a way to root this anymore. People keep telling me to use ODIN and to download an earlier ROM (and I now have ODIN and an earlier ROM -- hopefully from a good source, but I have no idea if it is), but my impression is that this latest AT&T "security" update keeps you from reflashing the ROM because of the bootloader lockout.
Any further help would be appreciated.
Thanks
CKR83 said:
...
Any further help would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
As I told you, the only method working for me (because of towelroot non working) is cf auto root.
Check periodicaly here http://autoroot.chainfire.eu/ to see if your model is listed.
I had just a look and it's not listed yet.
If it is, flash by odin and look if root works.
If not, you've got to flash by odin the same rom again (keep your original file on pc), you'll loose nothing, and report this fails on chainfire to test other solution.
Good luck
Franky
CKR83 said:
Here is all the info that I have on my phone:
Galaxy S5 AT&T US version (SAMSUNG-SM-900A)
Android 4.4.2
kernel version 3.4.0-2178781 [email protected] #1 Tuesday July 22
Build # KOT49H.G900AUCU2ANG3
SE for Android Status
Enforcing SEPF_SAMSUNG-SM-G900A_4.4.2_0018 Tuesday July 22
Security Software version:
MDF v1.0 Release 3
VPN v1.4 Release 1
Click to expand...
Click to collapse
Not only build number and kernel version, you need to check your Bootloader version with Phone INFO ★Samsung★ app (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
vndnguyen said:
Not only build number and kernel version, you need to check your Bootloader version with (in the FIRMWARE INFO section).
Bootloader version is one of the important info to check when you are going to root or flashing custom rom.
Click to expand...
Click to collapse
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Does that help any? People keep telling me I need to use ODIN and flash this, that or the other thing. Those comments would probably be more helpful if I knew more about this stuff, but my reading has lead me to believe that ODIN won't work with certain version of the bootloader. Or is that wrong?
CKR83 said:
Hey that looks like a great utility. Thanks! The bootloader is G900AUCU2ANG3
Did you every get your post July 2014 AT&T GS5 rooted?
If so, please drop me an email.
Thanks
TPG
Click to expand...
Click to collapse
No unfortunately not....
Sent from my SAMSUNG-SM-G870A using XDA Free mobile app
It's been a while since I last did this, and I'm afraid I'm quite confused...
I am running a custom ROM (Bliss Beta 6) but remembered that updating my ROM doesn't update my baseband/modem.
Are baseband and modem the same thing?
https://support.t-mobile.com/docs/DOC-10398
Using this site here I see that my current baseband (G900TUVU1CNK2) is super outdated. It tells me that G900T3UVU1FOG6 or G900TUVS1FOL1 are the latest, but I don't get why there are two. Which one should I install?
All that being said, can I install using TWRP and a zip, or do I need to ODIN it?
Any help would be appreciated, as I said I've done this before but can't find any updated tutorials that explain the questions I'm asking (I've tried searching google and XDA, if I missed something obvious I would appreciate a link!).
cheers
More research has helped me answer my own question! Sharing what I've found in case anyone else comes across this thread:
Baseband and Modem are effectively the same thing in this context.
G900T3UVU1FOG6 was released in August 2015 and has the fix for stage-fright.
G900TUVS1FOJ4 was released in November 2015
G900TUVS1FOL1 is pretty much brand new (released in December 2015) so there's not a lot on it. This is the one I'm going to try installing.
Followed the instructions from this thread http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400 to figure it out.
More use information found here:
https://ohthehugemanatee.org/blog/2...m-slash-baseband-firmware-on-a-samsung-phone/
lioncat55 said:
More research has helped me answer my own question! Sharing what I've found in case anyone else comes across this thread:
Baseband and Modem are effectively the same thing in this context.
G900T3UVU1FOG6 was released in August 2015 and has the fix for stage-fright.
G900TUVS1FOJ4 was released in November 2015
G900TUVS1FOL1 is pretty much brand new (released in December 2015) so there's not a lot on it. This is the one I'm going to try installing.
Followed the instructions from this thread http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400 to figure it out.
More use information found here:
https://ohthehugemanatee.org/blog/2...m-slash-baseband-firmware-on-a-samsung-phone/
Click to expand...
Click to collapse
i've been wondering this myself, so did you update your baseband & is there any change in battery or signal quality? (or i guess stagefright detector?)
also wondering if downgrading is no problem or if it affects anything like that (which stock samsung or other device kernels/ROMs do, sometimes blocking root etc)
Hey, so I actually updated to G900TUVS1FOL1 using ODIN. It nuked everything and installed regular TouchWiz which I wasn't a fan of, but I have no problem installing my own ROM later.
If you're doing the T-Mobile one, then there is no issue with rooting, installing kernels, custom ROMs, etc. I don't really know about "downgrading" the baseband or modem, but I don't think you would need to in this case.
Note that if you have Verizon or At&T you probably want to be SUPER careful, because they lock down everything.
lioncat55 said:
Hey, so I actually updated to G900TUVS1FOL1 using ODIN. It nuked everything and installed regular TouchWiz which I wasn't a fan of, but I have no problem installing my own ROM later.
If you're doing the T-Mobile one, then there is no issue with rooting, installing kernels, custom ROMs, etc. I don't really know about "downgrading" the baseband or modem, but I don't think you would need to in this case.
Note that if you have Verizon or At&T you probably want to be SUPER careful, because they lock down everything.
Click to expand...
Click to collapse
it's a g900t yes
i am going to look into upgrading it more directly rather than the complete samsung image... maybe... so you're confirming the official tmobile samsung 5.1.1 complete installation still lets you flash TWRP then cyanogen without a problem? i came from november 2014 samsung 4.4 to CM originally
kn00tcn said:
it's a g900t yes
i am going to look into upgrading it more directly rather than the complete samsung image... maybe... so you're confirming the official tmobile samsung 5.1.1 complete installation still lets you flash TWRP then cyanogen without a problem? i came from november 2014 samsung 4.4 to CM originally
Click to expand...
Click to collapse
yes, I installed G900TUVS1FOL1 with Odin, had root and TWRP installed just fine (couldn't get xposed to work because it was not a deoxdex rom of course). I just installed BlissPop ROM last night which is based on CM13. So yes, it didn't lock me down or anything.
Hi I'm looking for h915 users of the Canadian v20 that have successfully rooted their phones. I have many questions and concerns to ask concerning the h915.
I don't know if in 2018, will there still be h915 Users since not much developments for the h915.
Welcome to the small group of Canadian 915 users. Allow me to summarize your information quickly.
If you have received the latest security patch pushed OTA, you're unfortunately out of luck and can not safely root your V20. I unfortunately downloaded the update before I even reached home during the day I purchased mine... Boy, do I regret that terribly. I want root so terribly bad.
Secondly, if you have NOT run the latest security patch, you can flash the US 996 version and successfully achieve root without any problem. The only issues that may arise are baseband incompatibilities, but those are easily corrected by flashing back a 915baseband.zip found here in the forum.
To clarify the aforementioned security patches; In your settings -> software info ... you'll find 'Android Security Patch Level'. If it reads May 1, 2017 then you're out of luck. That bumped your software version from something like H91510d to H91510q. If I'm not mistaken, I believe '10d' was the latest software version released by LG that would allow us to cross flash software versions. Later versions are patched up and locked down.
If you're v10d then hallelujah for you brother!
*If anyone has a correction on this info, please chime in!*
murph187 said:
Welcome to the small group of Canadian 915 users. Allow me to summarize your information quickly.
If you have received the latest security patch pushed OTA, you're unfortunately out of luck and can not safely root your V20. I unfortunately downloaded the update before I even reached home during the day I purchased mine... Boy, do I regret that terribly. I want root so terribly bad.
Secondly, if you have NOT run the latest security patch, you can flash the US 996 version and successfully achieve root without any problem. The only issues that may arise are baseband incompatibilities, but those are easily corrected by flashing back a 915baseband.zip found here in the forum.
To clarify the aforementioned security patches; In your settings -> software info ... you'll find 'Android Security Patch Level'. If it reads May 1, 2017 then you're out of luck. That bumped your software version from something like H91510d to H91510q. If I'm not mistaken, I believe '10d' was the latest software version released by LG that would allow us to cross flash software versions. Later versions are patched up and locked down.
If you're v10d then hallelujah for you brother!
*If anyone has a correction on this info, please chime in!*
Click to expand...
Click to collapse
I was told that you can use lgup to downgrade to h91510e or h91510d since h91510q doesn't have anti-rollback features. So if thats the case I still have the option to start ?
darkknight200 said:
I was told that you can use lgup to downgrade to h91510e or h91510d since h91510q doesn't have anti-rollback features. So if thats the case I still have the option to start ?
Click to expand...
Click to collapse
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means ?.
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!
murph187 said:
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means ?.
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!
Click to expand...
Click to collapse
I would wait for Oreo to come to v30 and g6 before getting excited. Who knows, their Oreo update suppose to come in March and still hasn't.
As for rooting, im still hesitant to pull the trigger. I still need to find out if my LTE on freedom mobile is going to be affected even after restoring the basebands.
darkknight200 said:
I would wait for Oreo to come to v30 and g6 before getting excited. Who knows, their Oreo update suppose to come in March and still hasn't.
As for rooting, im still hesitant to pull the trigger. I still need to find out if my LTE on freedom mobile is going to be affected even after restoring the basebands.
Click to expand...
Click to collapse
https://forum.xda-developers.com/v20/how-to/h915-guide-fix-lagg-signal-root-lg-v20-t3699540
Freedom/wind functioning just fine according to this thread.
As for the V30; Oreo beta release is already out to the entire country of South Korea for the V30, for a few weeks. A small select few of American users have already received this beta as well.
G6; China has already been testing 8.0.
Seeing as 8.1 is already released, it's highly presumed by a many sources that LG will likely skip 8.0 altogether and push 8.1 to our devices. 8.0 merely serves as a means to identify larger incompatibilitys/bugs.
i just rooted my h915 with this thread https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
it is much simpler process compared to the older dirtyelf method. The thread op was very helpful in getting through it.
darkknight200 said:
i just rooted my h915 with this thread https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
it is much simpler process compared to the older dirtyelf method. The thread op was very helpful in getting through it.
Click to expand...
Click to collapse
Thank you so much for this input brother. I'm strongly considering this now. How is your cell signal/LATE speeds? FM radio functioning correctly as well? Any odd vibrations upon bootup?
murph187 said:
Thank you so much for this input brother. I'm strongly considering this now. How is your cell signal/LATE speeds? FM radio functioning correctly as well? Any odd vibrations upon bootup?
Click to expand...
Click to collapse
hmm it turns out i can't connect to freedom mobile. Im working with the op to resolve the issue. I will update when i can get my signal working along with root.
update 1: so I was told to use lgup to install the us99610f kdz and factory reset and now I have signal again. Now I am gonna use the same process of the guide i used again to root the now converted device.
update 2: i have gone thru the guide again and have achieved root + freedom mobile signal on my phone.
update3: I have installed weta rom and it is working all fine with signal.
the op of that thread @dksoni411 will be including a separate guide for h915 users in that thread since it has additional steps to follow. In the meantime, i can help you if you want to get root on the h915.
murph187 said:
It looks like I was misinformed the entire time. Well then! Give it shot buddy, I thought that 10q was ARB enabled. According to a deeper check on my own device, it comes back ARB=0. We're all aware what that means .
Now I'm very very curious. I'd love to follow your progress and see how you make out with this my friend. There's just one last thought to keep in mind though; LG consumer relations department for their software updates has officially confirmed the next April security patch will ship Android 8.0.
Wait for a taste of the Oreo? Or root now and make the update a little more difficult in 3-4 weeks. Either way I'm half tempted to take the plunge myself now too!
Click to expand...
Click to collapse
Could you share the link where announcement was made about releasing Android Oreo for LG V20?
dksoni411 said:
Could you share the link where announcement was made about releasing Android Oreo for LG V20?
Click to expand...
Click to collapse
i made this thread https://www.reddit.com/r/lgv20/comm..._v20_canadian_update/?st=jeh88vej&sh=d1dca001.
keep in mind i asked for info on the h915 since its been stuck on may security patch.
Lge security product is suppose to be the best accurate info compared to the customer rep of lg social media accounts.
darkknight200 said:
hmm it turns out i can't connect to freedom mobile. Im working with the op to resolve the issue. I will update when i can get my signal working along with root.
update 1: so I was told to use lgup to install the us99610f kdz and factory reset and now I have signal again. Now I am gonna use the same process of the guide i used again to root the now converted device.
update 2: i have gone thru the guide again and have achieved root + freedom mobile signal on my phone.
update3: I have installed weta rom and it is working all fine with signal.
Click to expand...
Click to collapse
Did you try installing the 915 baseband.zip from post #6 for your inability to connect to freedom?
murph187 said:
Did you try installing the 915 baseband.zip from post #6 for your inability to connect to freedom?
Click to expand...
Click to collapse
no i used patched lgup to flash us99610f kdz to get working signal and then did the whole guide again to get a working signal rooted h915 phone. Afterwards no need to do any baseband installing as the signal is strong as how it was on normal h915.
Wifi calling working on freedom after root?
EnIXmA said:
Wifi calling working on freedom after root?
Click to expand...
Click to collapse
No wifi calling.
New to Samsung platforms, excuse any ignorance..
Tried to source the factory image for a new-out-of-box SM-T510 with the following details:
==
T510XXU3BTFN
samsung/gta3xlwifixx/gta3xlwifi
10/QP1A.190711.020/T510XXU3BTFN
build date jun302020
buildid QP1A.190711.020.T510XXU3BTFN
Secpatch 2020-07-01
Android 10
Bootloader U3
==
If there's anything I'm missing let me know.
The usual suspects seem to list packages *later* than that reported on the device (from recovery anyway).
It hasn't yet been fully booted yet - in case there's a way to pull the factory image from recovery/download as a clean image.
I'm looking for that factory image assuming it would be needed in case my modding and experiments (as per our kind of thing) causes breakage.
I wouldn't ask if my efforts had been successful - posting is a last resort
Ta
EDIT:
Is the device ID "T510XXU3BTFN" a constant regardless of software revision/build?
Insofar as; the designator describes the platform; and all software applicable for the platform is referred to by this ID - regardless of software version/revision.
Where software is referred to by a platform designator, I assume there's no proper case where it is applicable to a different platform ID.
If I can get confirmation on this assumption it would help me narrow down exactly what I can use from what I can find on the source sites I have located.
benryanau said:
New to Samsung platforms, excuse any ignorance..
Tried to source the factory image for a new-out-of-box SM-T510 with the following details:
==
T510XXU3BTFN
samsung/gta3xlwifixx/gta3xlwifi
10/QP1A.190711.020/T510XXU3BTFN
build date jun302020
buildid QP1A.190711.020.T510XXU3BTFN
Secpatch 2020-07-01
Android 10
Bootloader U3
==
If there's anything I'm missing let me know.
The usual suspects seem to list packages *later* than that reported on the device (from recovery anyway).
It hasn't yet been fully booted yet - in case there's a way to pull the factory image from recovery/download as a clean image.
I'm looking for that factory image assuming it would be needed in case my modding and experiments (as per our kind of thing) causes breakage.
I wouldn't ask if my efforts had been successful - posting is a last resort
Ta
EDIT:
Is the device ID "T510XXU3BTFN" a constant regardless of software revision/build?
Insofar as; the designator describes the platform; and all software applicable for the platform is referred to by this ID - regardless of software version/revision.
Where software is referred to by a platform designator, I assume there's no proper case where it is applicable to a different platform ID.
If I can get confirmation on this assumption it would help me narrow down exactly what I can use from what I can find on the source sites I have located.
Click to expand...
Click to collapse
That is not the latest by far. Use frija.exe to get the latest stock ROM.
lewmur said:
That is not the latest by far. Use frija.exe to get the latest stock ROM.
Click to expand...
Click to collapse
Thanks for the response
Yes it's the as-shipped build, but before I try to work out which of the newer builds is appropriate and won't lock-out what I'm palnning to do with Ithe device..
I need (I expect so) that factory ROM as a file - to roll back to or restore if(when) I stuff something up in my next steps (TWRP/CWM, bootloader, magisk/root, rom version upgrade and/custom rom etc)
The earliest I can find seems like the latest, which isn't what I'm seeking
benryanau said:
Thanks for the response
Yes it's the as-shipped build, but before I try to work out which of the newer builds is appropriate and won't lock-out what I'm palnning to do with Ithe device..
I need (I expect so) that factory ROM as a file - to roll back to or restore if(when) I stuff something up in my next steps (TWRP/CWM, bootloader, magisk/root, rom version upgrade and/custom rom etc)
The earliest I can find seems like the latest, which isn't what I'm seeking
Click to expand...
Click to collapse
The latest is what you need to do all of the things you want. Earlier versions won't work. The only time you need an earlier version is when a new one has just come out and the devs haven't caught up with it yet. When you do, you can often find them on Sammobile.
edit: Also, if you let it, your tablet should update itself to the latest version. So if something goes wrong, the latest is what you'd need to get it back working.
Ah cheers, my concern was a new(er) release would block the ability to do some things to the device.
I kind of expected it AFAIK it's not uncommon and mostly assumed there's be issues with rollback fuses etc and stuff you can no longer do beyond version x.xx release (BL AP etc)
I might have seen reference to this being the case in the various info's I've read - basically if you want to do XYZ (multiboot, PXE, TWRP I don't know) you have to do it before a certain release.
**lwmr** I take it unlike other mfg's platforms I've worked on it's not an issue here so I can crash on ahead and it won't bite me?
edit:: I also found it strange I guess that the FW release history seems incomplete, Sammobile doesn't IIRC even list versions from around 2019 on these tabs. Unless samsung's volume of products and releases are too much to track I wonder dunno
benryanau said:
Ah cheers, my concern was a new(er) release would block the ability to do some things to the device.
I kind of expected it AFAIK it's not uncommon and mostly assumed there's be issues with rollback fuses etc and stuff you can no longer do beyond version x.xx release (BL AP etc)
I might have seen reference to this being the case in the various info's I've read - basically if you want to do XYZ (multiboot, PXE, TWRP I don't know) you have to do it before a certain release.
**lwmr** I take it unlike other mfg's platforms I've worked on it's not an issue here so I can crash on ahead and it won't bite me?
edit:: I also found it strange I guess that the FW release history seems incomplete, Sammobile doesn't IIRC even list versions from around 2019 on these tabs. Unless samsung's volume of products and releases are too much to track I wonder dunno
Click to expand...
Click to collapse
LOL, yeah, Samsung isn't like Amazon where they are constantly trying to find ways to keep you from blocking their advertising. Trying to downgrade to previous versions can be a problem, but only because of security issues. With these ROMs and recoveries, the devs attempt to keep up with the latest stock releases and will normally specify in the OP which stock ROM they are based on. So long as you aren't attempting to install an older version of a custom ROM based on Android 9 or earlier, having the latest stock version shouldn't be a problem.
(sigh) yep it's not just Amazon
Righto I got ya thanks for the info's I'll roll with that
cheers