[Q] Tmo Samsung S4 (SGH-M919) with Google Play Edition, need help - General Questions and Answers

(this belongs elsewhere but 10 posts...)
I have a rooted S4 and just installed Dandvh's Google Play Edition v.20150919 (http://forum.xda-developers.com/showthread.php?t=2539361) rom. I used TWRP to install, wiping everything but internal storage, then flashed the rom. Installed fine, no errors. Took the usual bit of extra time to boot the first time then up and running clean and stable. The issue is that the OTA Updater app doesn't work, severely limiting my ROM options. It didn't install as part of the rom install, though I'm not sure if it's normal to just get it off the play store. I get an error message about not being compatible with the ROM and can't access it (error message screen cap below). Just in case, I wiped the phone and flashed again just to be sure, same result. The OTA Updater is important as this is where you can change kernals, audioFX stuff, toggle advanced power menus, and quite a bit more. When I used this ROM during the first part of the year OTA Updater worked just fine but I switched off in July to try another ROM so maybe something with the ROM has changed? I tried searching for any comments in the thread to indicate either that something changed with OTA Updater or if anyone else had a similar problem, found nothing. Would appreciate if anyone might know why OTA Updater isn't working or how I might correct it. Thanks.
Edit #1: I haven't changed the model number to SGH-M919 (as seen in the screen cap) in build.prop yet as if I can't get this ROM to work right I'll need to flash something else.
Edit #2: I noted in the patch notes that the ROM was updated for OTA Updater 2.4.2 and I was running 2.5.3 so I uninstalled it and installed 2.4.2. No luck there either.
Version and Build Screenshot
https://imgur.com/SQ6ie5i
Error message
https://imgur.com/TfWN7p2

Related

[Q] Updates fail from 4.1.1 to 4.1.2

Hi,
A while back I rooted and unlocked using clockwork recovery and installed bigxie_magurTA_JRO03C-signed.zip
All was good for a while until the last month where I continually receive notification to update to 4.1.2
when I choose install, it attempts to reboot and on the recovery mode, I attempt to run the /sdcard/update.zip and it fails due to signature verification failure.
When I disable the signature verification, it states it cannot open the update file as if it is corrupt or not there,
I then tried to put on cyanogen mod, and when that loaded, I could not enter in my gmail profile info.
I then installed gapps on the next attempt to install cyanogen mod 10 and although more apps (google play app) was listed, still could not enter my gmail info anywhere
i have gone back to the 4.1.1 install I mentioned earlier, and it is running fine, but I am still prompted to update, which fails every single time.
Any suggestions on how to update this, I would be happy to go with cyanogen mod, but no idea really where to start.
I searched for the same error messages I was getting, and found a few posts but not solutions or recommendations,
Also, is this going to happen for every single update from this point on since rooting and unlocking the phone? i would prefer to give up more app control if going back to stock builds means not having to give up this much time for every update.
Thanks to anyone that can help.

[Q] OTA update starts then stalls out

Hi been looking at a lot of the threads about the OTA and making it work and I haven't seen anyone with the problem I am having.
So I have gotten S-Off with the Java Card, Installed CWM Recovery, flashed root, flashed tether and extreme power savings.
I also installed AdAway and updated the gps with FasterFix. Also froze a bunch of apps with Titanium.
Those are the only things I can think of that have altered the "stock rom" but I could be missing something here.
So to install the OTA I have tried the following
I defrosted the verizon bloatware and revereted AdAway and the GPS
I reflashed the stock recovery from:
http://forum.xda-developers.com/showthread.php?t=2708291
and
http://forum.xda-developers.com/showthread.php?t=2723112
those "stock recoveries" are different file sizes but both of them produce the same following error:
The OTA starts normally and the recovery starts up and says Updating Verizon system or something like that... The progress bar gets about a third of the way there then I get the recovery screen.. sort of like this image:
http://htcevohacks.com/wp-content/uploads/2010/06/htc-evo-recovery-mode-4.jpg
but where the triangle is inside the phone icon.
From there nothing and I have to reset the phone and then get the message that the OTA failed.
The only things that I can't undo are the extreme power savings and the mobile tether.
I have also looked at this tread to find out the exact stock recovery for my edition and they don't have it specifically hosted.
http://forum.xda-developers.com/showthread.php?t=2701376
in that thread it has instructions to look up the specific recovery based on CID and mine came up with 1.12.605.11 which seems to be nowhere to be found... So bottom line I am not sure if the recovery I have flashed from the two other sources is the exact correct recovery.
Anyone else is this boat or can help me out.
I have the same issue as this. I also have the power saver on and the wifi tether update. Sounds like it might be something with one of those.
This method worked for me.
http://forum.xda-developers.com/showthread.php?t=2723159

Unable to restore/mount/flash in TWRP and unable to achieve dl mode in LG Flashtool

Here's to hoping someone can help me out. My phone details before I messed up: LG G3 D850, rooted, TWRP 3.0, running Fulmics 5.2 for about 1 1/2 weeks
I noticed that I was not seeing the LTE indicator on my phone. I checked the HUB and saw the BootD850-30012016 data patch and figured that I just needed to install. So I flashed it and my phone wouldn't start. I was able to boot into recovery, so I figured I would do a clean install of the ROM so I did a full wipe, accidentally wiping EVERYTHING except for my external SD.
Result was that I can access TWRP but am unable to flash any of my backups or zips from my external SD, or OTG. I can see the files, but don't have the option to "swipe". I also am unable to 'mount' or 'install'.
At this point, I noticed that AT&T has finally released the OTA for Marshmallow, so I figured I would just use LG FlashTool and totally un-root and give the update a try. (BTW, I have used the flash tool many times with no problems/issues on both my phone and my son's D855).
Unfortunately, I am getting the dreaded "unable to change to download mode" after 15 seconds. I have uninstalled and re-installed Flash Tool, the LG Drivers and all files and used every port on both of my computers (Windows 10 btw) but can't get past the download error.
So...after many hours of digging, I took a leap of faith and was able to sideload Fulmics 5.1 successfully and install the 5.2 update from the HUB. I made backup of the ROM but TWRP still won't allow me to "swipe" and install/restore. I reinstalled TWRP using Flashify and it installed version 2.8 but still no go on flashing from recovery.
I realize that I'm lucky to have been able to figure out how to get the phone back using the sideload function in TWRP, but I really do want to go back to stock and it bugs me that I am unable to use my backups.
Sorry for the novel, but I wanted to be sure to include everything I did....if anyone can help me out I would be much obliged. My 11 year old is anxiously waiting on me to figure this out before she gets this phone (I'm moving up to the HTC 10 in a couple of weeks!). She still thinks I'm 'SuperMommy' so if I can fix this I get to keep my swagger!
I was also running fulmics 5.1 and updated to 5.2 in my phone but now i was having pretty good laggs and i finally realised that the update provided by the phone was corruped so i went on the official site and downloaded the same 5.2 OTAs from there and flashed it into TWRP recovery to finally get the latest version 5.3..know that is it always advisable to flash zip file when in recovery mode using TWRP recovery...The big mistake was cleaning also the internal memory of your phone.this caused the malfunction of twrp.
The issue is that most often i have seen cases of lagg in those updating to fulmics 5.2 from the Hub .sometimes in twrp recovery the update files will not successfully wipe and then reboot system with 5.2 installed but with many lagg the file downloaded there may be corrupted and not give you permission to swipe..if you really like fulmics and still update to the latest..Try this it may help you solve your problem:1 reinstall the fulmics 5.1 go to xdadevelopers.com/fulmics follow the link given by xpirit to www.fulmics.com and download the OTA 5.2(file size maybe 46 mb).. 2.reboot your phone now in twrp recovery it should now be able swipe and install..(if not then install Twrp 3.0 and try) 3-search the files in your internal memory or wherever you have downloaded it and flash it ..4.reboot system.That should be done!! In case you want to come back to stock and cant install from Twrp then the problem is with Twrp just download the latest version that goes with your phone.
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
dcli23 said:
Thanks guys for the suggestions. I finally figured it out after a couple days of sweating and swearing. Yaneddik, you were spot on about updating from the Hub. I ended up installing TWRP 2.8.6 and re-installed 5.1 from the Fulmics website along with the updates. Everything has been working great (except for losing LTE connectivity, but that's for another thread!). I'm not inclined to update TWRP to 3.0 unless absolutely necessary, 2.8.6 works just fine for me.
Click to expand...
Click to collapse
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
SofaSpud said:
Am a newbie here but a long time rooter on my older phones. This is the first time that I've seen the Hub mentioned. Can you kindly post a link?
TIA
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Hey there....you can access the Hub after you flash the Fulmics ROM. It's where you can get your tweaks, downloads, mods, etc. You'll find it in your app drawer.

How to properly flash tulip with twrp and ota on stock?

Hello there.
I'm using tulip for few months now. One of first things that I've done, have been unlocking device, rooting it and put stock rom with root access on it. So far, so good. I did not encounter any serious glitches etc, but now I would like to finally upgrade miui to 11 (currently having 10.3).
And there's my problem. I would love to dodge making clean installation (wipe data etc) and I do not wish to risk to bootlooping my phone. I've read on some threads (older ones, but still) that you cannot simply install ota update in system, because due to changed recovery (I do have TWRP instead of fabric one) you will cause bootloop. I've tried alternative method of installing zip BY twrp, but program says, that it encounter a problem called "package expects build fingerprint (...) of tulip 0/PKQ1.180904.001/V10.3.2.0.PEKMIXM or PKQ1.180804.001/V11.0.2.0; this device has omni_tulip/tulip:8.1.0/OPM8.181105.002/1", and then sait, that in had error 7.
Is it simply wrong rom being installed and I have to choose something that is being named the same way and supports ota, or is there a way to go more swiftly through this process? If so and I should pick rom with ota - what to choose? I like deep level customisation, but compatibility with google store, being able to use store, payments and paid apps, instead of "opening them" by some lucky patchers kind of apps.
OR MAYBE I just need to change recovery from TWRP to something different - like PBRP f.e.? Just like this thread says - https://forum.xda-developers.com/re...how-to-setup-official-miui-breeaking-t3893703
Just a quick update - changing twrp to pbrp does not change anything in upgrade process - still get the same error, now just without telling me, which version do I have.
Also, what's interesting, apparently twrp said to me that I do have android 8.1, but "about phone" in system says, that its android 9 (9PKQ1.180904.001 to be exact).
That's werid, because everywhere I check, phone says "android 9" as a version of it.
Have you tried wiping system and installing?
Nitin Rai said:
Have you tried wiping system and installing?
Click to expand...
Click to collapse
Not yet. I've found method of flashing via PBRB with usage of downloaded file and one option check, but I'm not gonna try it, unless I do a backup of my apps. If that won't work, I'll perform a clean instalation and choose rom that supports ota.
well, I've tried to do this with the method, that I've described before, but this did not ended successfully. I'll look for rom with ota update possibility and then install it most likely. Apps had backup, so I lost almost nothing.
It worked. I had to download bigger patch (1.7 GB, instead of circa 700 MB, that I've tried before), I also had to use method described here -> https://c.mi.com/thread-1782169-1-1.html (pitch black recovery, instead of twrp + one tweak in options). Start after flash was very long (it took like 10 minutes or so), but it booted successfully in the end. Not sure which rom I do have after all, but as far as I remember it was so close to stock, as possible (with only few extra options and tweaks). So yea, it just works.

Cant rollback from OxygenOS 12 to 11

Hi, I have this super-weird issue - my OOS got update to v12 and since then weird things happened:
It started to suddenly and immediately turn off and I couldnt do a thing. I did hard reset and noticed that turning on Gooogle Assistant (or using the mic at all) caused these resets. So I didnt activte Assistant. Unfortunnately, this caused my mic not to work at all.
So i have given up and decided to revert to previous rom - v11. Unfortunately, that is everything but simple:
I have downloaded ROM for EU from here oneplus site and tried both OP local update tool and this weird app named my application2. Both dont seem to work and im not sure why, I checked like 5 different ROM versions and I am kind of stuck. OP Local prompts me that I cannot install lower version of package than currently installed and this other app throws me pop up with this message: "Verification failed". I tried to google it and checked here on forum and I cant find similar thread.
Could anyone help me out with this?
I just went through this. I downgraded from 12L to 11. For some reason some of the roms do not want to be used by the local upgrade app. I used a different one from the one I will direct you to and it said that I couldn't downgrade. I just had to find the right one. Go here: https://forum.xda-developers.com/t/...a-oxygen-os-repo-of-oxygen-os-builds.3930585/
Under "signed flashable zips" in the op, click "click to show content". I don't know which one you need global/India or Europe. I specifically used the global/India OnePlus7ProOxygen_21.P.41_GLO_0410_2112101753.
Use the local upgrade tool app. Downgrading will completely wipe your phone. So, make backups of your backups. If you root your phone, make sure to freeze the System Update app to get rid of the annoying update notification. So happy to have root/twrp back.
Thanks, unfortunately I have rolled back to OOS 11 and it didnt solve a thing - i keep seeing this lightning symbol and phone turns off even on full battery, I cant make phone calls because any use of mic turns off the phone immediately and I have no clue what to do next with it.

Categories

Resources