Related
TMUSA, running enom. It somehow got the 2.2.1 OTA DL'd and now it nags non stop to install. I don't want it. How do I stop the nagging/prompting ?
Has any1 installed over Enom's 2.12.2 ?
I'm in the same situation here. Need to kill the nagging.
rashid11 said:
TMUSA, running enom. It somehow got the 2.2.1 OTA DL'd and now it nags non stop to install. I don't want it. How do I stop the nagging/prompting ?
Has any1 installed over Enom's 2.12.2 ?
Click to expand...
Click to collapse
He's updating the build.prop in 2.12.3 so it will be same/newer. What it means for you having already downloaded it, maybe delete it from /cache ?
rashid11 said:
TMUSA, running enom. It somehow got the 2.2.1 OTA DL'd and now it nags non stop to install. I don't want it. How do I stop the nagging/prompting ?
Has any1 installed over Enom's 2.12.2 ?
Click to expand...
Click to collapse
depending on what recovery you have.. (i use amon ra 1.0.7.1) if you attempt to flash it.. it fails signature check and wont go.. it gets the notification to go away for a while
im going to be selling my phone next week and i want to return it to stock im rooted with one touch root and runing a custom rom my question is how can i get it back i tried to flash the stock rom but it keeps failing also i keep geting the ota message will this work if i just let it install the ota update
Yes
Sent from my Nexus One
ok well i will just let it update i guess
ota update failed too any other ideas
did you remove any apps out?? if you did.. your going have to push them back into /system/app
shibby80 said:
ota update failed too any other ideas
Click to expand...
Click to collapse
try to use the pass.img to restore the phone back to stock...
shibby80 said:
ota update failed too any other ideas
Click to expand...
Click to collapse
What i did was:
- install the original FRF91 (search the forums, you will find the link)
- install (from recovery or OTA) the update
The last step also put the stock recovery on and that was it ...
xghostyxjokerx said:
try to use the pass.img to restore the phone back to stock...
Click to expand...
Click to collapse
what is this
Hi,
First of all I apologize for the extremely noob question, but I just want to be certain I wont brick my phone, so I rather ask...
I have a Nexus 1 with 2.2.2 rooted (it came just like this when I bought it, so I have no idea how it was done). The thing is I got a notification about OTA update to 2.3.3, and I wanted to update.
My question here is, how do I determine that it wont brick my phone?
(As far as I can tell its googles stock firmware with stock recovery atm)
Apply the update. If it fails, you will need to look into other means of upgrading. If it passes, you win. If it fails, and won't boot afterwards, you may need to wipe, but all should be normal afterwards.
Thanks
While we're at it, how do I 'wipe' exacly?
By installing a custom recovery, either ClockWorkMod (through ROM Manager from the market) or Amon_Ra, which is my preferred choice, but you have to flash it using adb.
Thanks guys, I've been reeding a bit more and finally figured it out.
One last question though, I see from http://forum.xda-developers.com/showthread.php?t=968396 that Gingerbread requires Hboot 0.35.0017 and Radio 32.41.00.32U_5.08.00.04.
I already have hboot-0.35.0017 but I have RADIO-4.06.00.12_7.
If I upgrade using OTA do I have to flash Radio first? Also can I use this newer radio with FRG83G?
Im sorry, Im still a bit lost on the radio stuff...
If you use the official ota it will update the radio.
Sent from my Nexus One using XDA App
albundy2010 said:
If you use the official ota it will update the radio.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Neat! And if I need to rollback to FRG83G, will the new radio version work with it?
So I updated using OTA feature and everything went smooth!
Thanks for the help guys. I really appreciate it!
BTW So far Gingerbread kicks ass!
nice to see people getting the ota..
lnxpowa said:
Neat! And if I need to rollback to FRG83G, will the new radio version work with it?
Click to expand...
Click to collapse
Yes it will.
Neat! Thanks everyone for all the help!
I'm root/soff. a new ota just came out that will fix my unusable phone. how do I take it if im root, do I have to fully unroot? or can I take it as is?
Sent from my SM-T217S using XDA Free mobile app
looks like it needs stock recovery to flash, it's not hboot format and twrp won't take it. will report back if I am able to do it
Sent from my SM-T217S using XDA Free mobile app
One of the benefits to being s-off is you don't have to take the OTA...you just flash the firmware and done.
BD619 said:
One of the benefits to being s-off is you don't have to take the OTA...you just flash the firmware and done.
Click to expand...
Click to collapse
i did that and then i was unable to take profile or prl updates :crying: it also didnt apear to have fixed the signal issue... i might not have waited enough... or it could have something to do with the unability to take prl and profile updates... anyhow ill try again from a diferent download see what happens
Did your baseband change? last four should be .0610.
If it did change then it's most likely a network issue.
BD619 said:
Did your baseband change? last four should be .0610.
If it did change then it's most likely a network issue.
Click to expand...
Click to collapse
Yes the baseband did change but the signal problem persists. i need to take the FULL ota to fix my phone (or install something else that will) regardless the radios alone aren't fixing the issue.
i tried flashing the rafios by themselves and it wouldnt update prl or profile; it also had the same signal issue. i tried the radios AND the new stock rom for it and same thing. i tried going back to stock and taking the ota and the ota wouldnt install.
Thoughs?
I'm the same root/s-off. I flash the h/k sound file did you find a way to install the latest ota update?
I cant figure out how to get the OTA either
I have S-Off im also rooted, and i have TWRP recovery, i can't get the zip to flash. I was thinking about doing a stock root recovery using the RUU, but then i thought if i do that, would i still be able to reroot using the same method? so my question is, how can i flash this zip and keep my root? or should do a stock recovery from the RUU and update and wait for another root? if any devs read this, i'd really like your help please and thank you. I currently have the stock rom with just root access and S-Off.no custom roms on here.
man.. i have the same problem bro.. smh.. hey man keep me posted if something comes up
Working via fastboot: http://forum.xda-developers.com/showthread.php?t=2759908&page=8
I am S-Off and had no issues, took 2 minutes, I followed the MikMik link
the 1.54.651.10 update.
If I'm rooted and have S on, how do i take the update?
jchtcusre1 said:
If I'm rooted and have S on, how do i take the update?
Click to expand...
Click to collapse
Settings>System Updates>HTC Software Update
BD619 said:
Settings>System Updates>HTC Software Update
Click to expand...
Click to collapse
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
I never OTA so not really sure of the process.
scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
You have to have stock recovery to take the update, which means you have to flash stock recovery first and then take the update, then repeat the rooting process.
scott_0 said:
I tried that and failed, I returned to a completely stock rooted backup from the day I rooted, downloaded the update, chose install, it rebooted to recovery, saw no stock recovery, so it brought up TWRP and thats it.........
Click to expand...
Click to collapse
you should at least have seen a green arrow circle and/or a red triangle with a "!" in the middle. if you saw the triangle that is recovery trying and failing to update. at this point if you press and releast volumeup+power it should bring up the text of what it did.
rhe12 said:
You have to have stock recovery to take the update, which means you have to flash stock recovery first and then take the update, then repeat the rooting process.
Click to expand...
Click to collapse
I am dev unlocked, rooted, s-on with twrp. If I revert to stock recovery would I be able to take the OTA then reinstall twrp?
Many thanks!
Swyped mobile from HTC One M8.
drich66 said:
I am S-Off and had no issues, took 2 minutes, I followed the MikMik link
Click to expand...
Click to collapse
I'm looking at the MikMik one, and I am just not sure if this will erase all my apps and settings. Do I need to use a backup app or should I be ok flashing this and keeping all my apps and settings?
I woke up and my phone had a message saying it was ready to update to N910TUVS2EQE2. Has anybody updated and rooted this fw yet?
I also recieved the update, I won't update for that reason. But the notification is annoying.
It's been forever since I had rooted my phone, finally updated, then had this update and installed it while it was still unrooted. But now I want to root the phone, so no one has tried it yet? Only thing I've noticed with this version is it seemed to have tried to keep a connection via wifi instead of bluetooth to my watch, which lead both of them to have some serious battery drain.
Now that I've set it back to bluetooth, let's see how well it does. The watch (Gear S2 Classic 3G) had to be charged twice in one day, it was terrible.
Unless T-Mobile has suddenly reversed a long-standing policy and locked the bootloader on a previously unlocked device (something I have not ever heard of for any device), you can still flash TWRP recovery from Odin and then flash SuperSU from recovery, which does not modify the system partition. This should just be a minor security update for Marshmallow and not an update to Nougat, which would have much bigger compatibility consequences but which should still be rootable by the above method.
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Would be great if we could get a nougat release.
ElMadre said:
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Click to expand...
Click to collapse
So let me see if I understood what you said, you installed the EQE2 and flashed TWRP, rooted it, then installed another ROM over it?
It is annoying as F!!!!! Every 6 hrs or so it nags the F!!!! outa you!
m4f1050 said:
So let me see if I understood what you said, you installed the EQE2 and flashed TWRP, rooted it, then installed another ROM over it?
Click to expand...
Click to collapse
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
ElMadre said:
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
Click to expand...
Click to collapse
Ok thanks.
t-mobile SM-910T
ElMadre said:
Yes, pretty much: I ODIN flashed QE2, did a factory restore from stock recovery (to clear out KK bits), ODINed CQ Auto Root, ODINed TWRP, and then flashed Smores ROM from TWRP. I was exclusively on FireKat ROMs since I got the phone 2.5 years ago, and Smores is by the same developer. Very lightly modded stock version of ROM.
Click to expand...
Click to collapse
where could I get the QE2 file?
Lsanc1170 said:
where could I get the QE2 file?
Click to expand...
Click to collapse
Not going to say what others say all the time, but I searched for it. (I Googled it.) If you want to easily root it and already have TWRP recovery, go to this post:
https://forum.xda-developers.com/note-4-tmobile/development/roms-10-29-2014-t2922618
If you want the ODIN version, go to this link:
https://samsunggalaxyrom.com/2017/0...sm-n910t-n910tuvs2eqe2-marshmallow-6-0-1.html
ElMadre said:
I can confirm it's rootable. I just installed it this weekend, upgrading from 4.4.4 finally. I've got SmoresV1 ROM installed over it, Xposed up and running, all good so far.
Click to expand...
Click to collapse
what is Smores Rom? what MM base does it use and what are it's features?
slaapliedje said:
It's been forever since I had rooted my phone, finally updated, then had this update and installed it while it was still unrooted. But now I want to root the phone, so no one has tried it yet? Only thing I've noticed with this version is it seemed to have tried to keep a connection via wifi instead of bluetooth to my watch, which lead both of them to have some serious battery drain.
Now that I've set it back to bluetooth, let's see how well it does. The watch (Gear S2 Classic 3G) had to be charged twice in one day, it was terrible.
Click to expand...
Click to collapse
The Gear watch battery drain problem likely isn't related to the phone update.
We've had the same problem with the Gear S3. After weeks of running fine, my S3 would do the same thing. We've been having to hard reset the watch to fix the problem.
anyone getting better or worse signal with the QE2? .... feedback?
I've looked everywhere in the threads and can't find an answer, hope you all can help.
N910T, Android 6.0.1, N910TUVS2EQE2. Everything I try and flash anything I get E: Footer Is Wrong and E: Signature verification failed. Tried Odin. Tried ADB. Tried to flash from ZIP. I unlocked the phone with the code from TMO but can't get past the loader to flash anything. Happy to provide futher details but any help would be very appreciated.
jnyfive said:
I've looked everywhere in the threads and can't find an answer, hope you all can help.
N910T, Android 6.0.1, N910TUVS2EQE2. Everything I try and flash anything I get E: Footer Is Wrong and E: Signature verification failed. Tried Odin. Tried ADB. Tried to flash from ZIP. I unlocked the phone with the code from TMO but can't get past the loader to flash anything. Happy to provide futher details but any help would be very appreciated.
Click to expand...
Click to collapse
It was the USB cable. Tried different cable and port. Tada.
f4phantomii said:
The Gear watch battery drain problem likely isn't related to the phone update.
We've had the same problem with the Gear S3. After weeks of running fine, my S3 would do the same thing. We've been having to hard reset the watch to fix the problem.
Click to expand...
Click to collapse
That did seem to help, and oddly enough one of the watch faces I'd bought that wouldn't install now installs and works fine.
jnyfive said:
It was the USB cable. Tried different cable and port. Tada.
Click to expand...
Click to collapse
Follow up. I'm able to flash TWRP. Made a backup but when I try to flash a new ROM I get error 6, error 7, or zip file errors in TWRP. When I try to flash ROM in Odin it crashes. Ideas? Is the build the issue?
Sent from my SM-G955U using Tapatalk
jnyfive said:
Follow up. I'm able to flash TWRP. Made a backup but when I try to flash a new ROM I get error 6, error 7, or zip file errors in TWRP. When I try to flash ROM in Odin it crashes. Ideas? Is the build the issue?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
what file and file name are you trying to flash and what model phone do u have and what current loaded firmware do you have?
XeoNoX said:
what file and file name are you trying to flash and what model phone do u have and what current loaded firmware do you have?
Click to expand...
Click to collapse
TMO Note 4, baseband version N910TUVS2EQE2, tried lineage-14.1-20170725-UNOFFICIAL-trltetmo.zip and RR-N-v5.8.2-20170303-trltexx-Official.zip
Sent from my SM-G955U using Tapatalk