I have been on a plain rooted 4.1.2 rom for years. I now need to update for a couple apps I use to work. Can someone give me some brief feedback and point me in the right direction so I can update my phone without locking the bootloader?
I like the plain set up I have now, so maybe I just need to update to the highest version without locking BL. Thanks.
I thought about trying this---> File: cm-10.1-20130315-NIGHTLY-d2vzw.zip, but all links that I've found are dead. Anyone know where I might find this file? Thanks
CM is dead. The leftovers rose from the ashes as Lineage OS.
Look them up. Pretty stable.
Jump straight into Marshmallow or Nougat. I'm still on CM12.1 Lollipop, but the newer stuff should work fine. There are threads for all of it, so do good reading before you start.
Thanks for answering my thread. I haven't messed around with my phone in years. I guess what you're saying is since I've never took the OTA 4.3, I can load an advanced CM without locking my bootloader.
phonetool....thanks for the input. I tried Nougat but I had issues with my 3G data and a couple other little things.
I decided to go with 12.1 Lollypop and it is great. All my apps work and 3G fires right up.
Related
This is my first post on this site, though I have trolled these forums since I got my smartphone. I have learned a lot too!
Currently my phone is a rooted Maxx HD (xt926) running JB 4.1.1. From what I have read on the forums, going to 4.1.2 might break my root and WILL keep me from going back to ICS using a tool I found on this site (Matts tool I think its called). I have decided its not worth the upgrade until someone gets root with a stock JB instead of with ICS then a JB upgrade.
I am glad I caught it in time. The updater started the 4.1.2 download so I turned off wifi and data to stall it. I couldn't cancel the download. I have Titanium Backup and froze Updater 4.1.1. This took my downloading notification away completely. Now if I try to do an update, it says an update is currently downloading, however I have no notification or any sign something is actually downloading, so I think that stopped it.
I am hoping this doesn't mess up future OTA updates should I defrost and try again.
This isn't a question so much as I didn't see a thread that covered stopping OTA notifications with this phone after a search. This procedure seemed to work great so far. This is probably such a simple thing to veteran android users that it probably wasn't posted, or I didn't find the post. I am hoping this will help other noobs. Or if this won't work or breaks something else, hopefully someone will point it out.
Hey community,
after updating my 5.0 LTE 32 Shield Tablet some month ago and rooting it, I came to the conclusion that I don't really need root, but would like to continue receiving OTAs and have a device that just works.
Prio1:
Have a tablet with the latest updates installed.
Prio2:
As 1, but rooted.
I have made a apps+sysapps backup with Titanium.
What do you recommend as the next step?
Thank you very much.
All the best, Esshahn
Some additions:
1. I noticed I'm actually having 5.0 on my Shield. It's the 5.0.1 update plus the nVidia stuff that comes up all the time in the notification center.
I really just want to undo all root and whatnot actions and have a right out of the box experience on my Shield. I already did some stupid stuff (factory reset) and therefore lost my personal data anyway, so there's nothing to lose.
I noticed this forum isn't really active. If anyone doesn't know the answer, but could point me to the right forum for help that would be nice too.
Thank you
flash the full OTA through recovery: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
then reinstall supersu through recovery, no factory reset needed
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Esshahn said:
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Click to expand...
Click to collapse
you can flash the full OTA through TWRP or CWM, no idea why it won't work with stock recovery though
the update supposedly fixes the graphics glitches that appear in various apps on update 2.1, that might be a good reason to update
Thank you!
Actually, since I didn't have CWM installed anymore, I just sideloaded the latest OTA, which worked nice.
Hey guys,
So I went from B145>B148 and now I'm stuck. Can't root or go >B304>B312>B327...what I'm saying is, I'd rather go back to B145. I was very much fine with that version (rooted w/ KingUser then removed and installed w/ SuperSu). Everything else fine. Just wanted to see if there was any difference on B148, not too excited to go LP.
Any ideas how to go back down B145??
thanks!! :good::good:
Anything, anyone?
Downgrade firmware? Something?
Solved!
Alright, so with only a bunch of page views and no real help from anyone here on the forum...I was able to finally figure everything out on my own.
I was originally at C00B145 (and rooted, loved it), got curious with everyone talking bout the many other upgrades so >C00B148 (lost root, hated it. Stuck on firmware, couldn't root and for some reason could't go further), probably just me. Decided and risked on V100R001C900B308 rollback (success) but stuck again on temp transition, couldn't go anywhere. Failed on B137, B137SP03, B141, B145, and B148.
Solved: Re-flashed V100R001C900B308>C900B300 (rollback)>MT7-L09C900B324, backup recovery, system restore>kingroot, then installed SuperSU (deleting kingroot).
Rooted MT7-L09C900B324 5.1. Now, the only thing I'm missing so far is the Motion Control, which I only deal with the slider (not a big deal to me). I really like the double-window, knuckle/screenshot, and the few other interesting new features. Lots of ppl saying they don't have 4g available, but mine's fine...can switch between 3G/4G.
I did use two different region's firmware for the solve. No lags, and actually has good fluid response. Gonna keep on 5.1 for at least a week and see what's good on battery life, response and features...if I like it'll stay, otherwise I had no problem on B145 and might just go back down to KK.
Cheers!
jfer671
I recently made a terrible mistake in toying with downgrading back to Marshmallow from Nougat which resulted in the sad hard-bricking of my device. The Nougat bootloader somehow allowed stock Marshmallow to boot and when I decided to accept a security OTA, it must have patched the bootloader and didn't notice that the bootloader was the incorrect version. The second that OTA had applied, my poor MXP had died and it never turned back on. So now I'm here to present a couple of things I feel that I should drop off before I leave this device forever because I had a couple of projects in the works that might be cool for you all to check out.
I have one build of Lineage 15 that I slapped together using HashBang173's kernel and device config and the other sources provided by the Android Oreo WIP page. The last time I was able to get it to boot, it had some serious Bluetooth force closing problems, but there were a ton of changes since I last made a new build. I was never able to see any sort of improvement since I couldn't flash and test the build so if you're looking to try out this build, be my guest. Just flash at your own risk as usual and if you do, you will have to erase userdata before you will be able to wipe anything in TWRP again due to some bug that crashes TWRP.
My second build is for a Nougat build of PureNexus. I was getting really antsy while waiting for a build to come in from HashBang that he mentioned that he'd make a while ago, but since that never ended up coming, (as far as I know) I made one myself. I slapped this build together with the PureNexusProject-Mod sources, I haphazardly put together my own device config, and the build succeeded. However, with the same sad result, I was never able to run this build myself and I have it here abandoned. Again, try it at your own risk because I have put no testing into this at all.
I'm very saddened to leave this device because I really loved everything about it, (minus some of the motorola inconveniences along the way) and I put so much into my little device over the past two years. I guess it's about time to move on anyways :crying:
BUT WAIT, there's more. I have been able to revive my Moto X Pure using this thread over here: https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
I'm constantly checking the thread to help people who are running into problems. It was a godsend to me so I'm more than willing to help others
Download
I just installed your Lineage 15 build. Bluetooth keeps crashing, and camera doesn't work. I managed to stop bluetooth crash by deleting it from system files. Thanks for your work and I hope to see more from you.
Hi All,
I have a two Relays that have served me well, and I enjoyed having them, but the time has come to pass them on to someone else. Before I do that, I'd like to update them to the most recent versions of stable-release software that is available for them.
For Cyanogen, I have:
cm-11-20150831 (this is stable)
cm-11-20160523 (this is a nightly build)
For recovery I have:
philz touch 6.48.4
I'd like to replace Philz with a newer TWRP, but the Relay is no longer listed on the TWRP website. I'm also wondering if there was ever a stable CM release newer than the one I have.
Does anyone have sources for the above?
Thanks.
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
mrigancb said:
Is there any one still developing for this device? If so, is it possible to get Android Go on it.. might just breathe new life into it and bring it upto date..
Click to expand...
Click to collapse
Although I'm not a developer I have been working on my SGH T699 from T Mobile. You may already know of the JellyBean and before. Recently I've noticed new builds for the samsung Galaxy S Relay 4G like the Validus 5.0.2 or the Fat Toad. I haven't tried those yet I was trying for a higher version. With 8.0 Oreo it requires partitioning and I need to brush up on that. So I went lower to the 7.0 or the 7.1 Nougat. I started noticing a lot of broken or old links so I had to resort to fishing the internet for most of the packages apparently lost in XDA. I pretty much have all of them and was just starting to try a few out when I ran into problems like I want to keep using the keyboard and Wifi calling or a related Wifi issue. It also crashed, went into bootloop or even soft bricked within a few days. The Roms and packages I've found are highly unstable and I see many had flashing issues. So far I've been tricking my device into taking the flash and even then it doesn't hold long. I'd like 6.0 MarshMallow if I can, maybe 7.1 if they ever get stabler that'd be great. But so far the ROMs for the Galaxy S (relay) are fairly horrible to say the least. I get the impression these so-called developers aren't testing their ROM creations more than 5 minutes and then handing them off to noobs who may be very likely to brick their device trying to get it in and running, only to have it crash repetedly! Or worse, hard-bricked.
I like this device. I think I'll keep working on it.
Casper Young.