Database Users

What to do now?

Hi all,
Just received my G2 from warranty exchange from my Note 2 breaking, and I would like to go further with it!
I'm currently on 4.2.2 JB, and was wondering where I could find a link to get to 4.4.2 rooted? Is there a way to unroot (This is important incase I need to send it back).
I've seen a few threads, downloaded two kdz files, but just wanted to check if all I needed to do was flash that and that's all?
Thanks in advance!

You can just upgrade your phone (officially) and then root it afterwards by IOroot.
It's way too easier than the kdz method.
Also try to write a better title for your post.( No offence)

Ashrockr said:
You can just upgrade your phone (officially) and then root it afterwards by IOroot.
It's way too easier than the kdz method.
Also try to write a better title for your post.( No offence)
Click to expand...
Click to collapse
Thanks for the reply! Yeah I realised after reading it again, the title had no context xD Sorry!
I can't upgrade officially since the EE UK OTA update isn't out yet

ShahinTehShiz said:
Thanks for the reply! Yeah I realised after reading it again, the title had no context xD Sorry!
I can't upgrade officially since the EE UK OTA update isn't out yet
Click to expand...
Click to collapse
But these thread shows that they received their EE OTA update
XDA
EE Community

[Early Warning] DO NOT TAKE OTAs after upgrading to Lollipop

If you've upgraded to the new Lollipop 5.0.1 update (N910VVRU1BOAF) for Verizon Samsung Galaxy Note 4 (N910V):
MAKE SURE YOU NEVER TAKE ANY OTA
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP​
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.

Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?

^^^I'm not sure, but I've been postponing mine since the Ota was pushed.

Hibby- said:
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
Click to expand...
Click to collapse
droidx2.3.3 said:
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.

When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"

itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
I believe your looking for "SDM"

rhilway said:
I believe your looking for "SDM"
Click to expand...
Click to collapse
You are correct.

Manually updating
hsbadr said:
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
Click to expand...
Click to collapse
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated

Nameless crowd face said:
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Click to expand...
Click to collapse
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!

So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?

hsbadr said:
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
Click to expand...
Click to collapse
Thank you again man

samhainww said:
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
Click to expand...
Click to collapse
I did last night, just use Odin to flash the NJ5 firmware, when it tries to boot the first time it will bootloop. Pull the battery, replace the battery and boot to recovery (vol up+home+power) then wipe data. The phone will boot to the setup wizard for KK.

I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk

starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.

starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Click to expand...
Click to collapse
Nameless crowd face said:
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+1
Another example, some Note 3 users fall into the trap of 4.4.4 OTA update & with no option to downgrade, they lost root, custom TW ROMs, and almost everything. Now, they're waiting with Note 4 users for a root method to rejoin the party while Note 3 on 4.4.2 can be rooted using TowelRoot.

Which tool?
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
All of the debloat tools that I find require root, which are you using?

There's a script that someone wrote to disable Ota and debloat. It doesn't need root. Sacher around on here for it

So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?

As of now it makes no difference.

Stupid question, but how do you turn off automatic OTA on lollipop?

ASUS cancelled 2.19.40.18 OTA

guys
http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=14836&pid=107979
asus said they cancelled this update due to unstable update...
1st i dont know what is unstable in this version[same as previous and new bug of call screen animation
2nd lol which update came without new bugs?
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:

they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk

luisoman2000 said:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
Click to expand...
Click to collapse
ya same here..but what they will do to unlocked phones/??

ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices

ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.

ansebovi said:
guys
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
Click to expand...
Click to collapse
That was my first guess as well

TheSSJ said:
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
Click to expand...
Click to collapse
no i am asking about bootloader[can they lock it somehow if we flash next ota]
Harfainx said:
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
Click to expand...
Click to collapse
so how can we update from here after ??? need to modified by someone for flashing ???
jaysus145 said:
That was my first guess as well
Click to expand...
Click to collapse
ya my 1st thought too,, haha

ansebovi said:
so how can we update from here after ??? need to modified by someone for flashing ???
Click to expand...
Click to collapse
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.

Harfainx said:
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Click to expand...
Click to collapse
well i am from sony device..they release main update of android..and 1 bug fix,thats all...so we dont care..and no need to worry about relocking issues..
this is the first asus device...man they releasing update for every 10days..i thought we could apply just like that..but since they didnt gave unlocked bootloader tool ,i got these doubt..
and thanks for info..
so i must wait for zips which is modified for unlocked bootloader[if they trying to relock]

I honestly doubt they're going to find a way to relock it with an update, but who knows what voodoo they may come up with.
Either way, we'll grab the updates and get them ready to be flashed quickly. It's a simple process.

I highly doubt he will do anything regarding unlocking/locking bootloader. because:
1. last year they released their official tool to unlock zenfone 4,5,6 bootloader after 3-4 months of release.
2. This year when they launched the zf2 in US they hold contest and developer events via xda. Now xda is a place where no one keeps their bootloader locked. so they knew exactly where they are releasing and advertising the product.
So I dont think they would even bother about this bootloader . Maybe it is an unstable build in terms of their quality test.

Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.

joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Everthings here http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999

android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked

joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Even if your phone gets here on a newer version (it won't), you could always downgrade everything and unlock from there. =)
Shakalaka has backups of everything going back to like version 2.12 or 2.13.

MatteXperiaU said:
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
Click to expand...
Click to collapse
Problem is they can't support any ROM that isn't official on the zenfone. They'll pass you off. Like most manufacturers.

These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590

one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?

damian5000 said:
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
I downloaded the appropriate OTA the other night, so if ASUS pulls the file, I still have it and can share it on Dropbox and/or Copy.
I get the phone today! So hopefully tonight I get the OTA up to 2.18 and then wait to see what upcoming 2.20 has to offer. If we can still unlock the BL with 2.20, I will let that OTA happen. Similarly if we find out that those who unlocked their bootloaders can't take the update (at that point I will cry a little, if there is no official way to unlock BL released with the update ).
If both scenarios above are false, then I will apply my downloaded 2.19, unlock the bootloader, then accept 2.20.
Best one could do eh?
---------- Post added at 07:24 ---------- Previous post was at 07:19 ----------
ansebovi said:
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
Click to expand...
Click to collapse
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....

joel.maxuel said:
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
Click to expand...
Click to collapse
no i didnt mean it will relock,..
but the unlocked needed some file right..it modifies something right? ...and it is not present in old things..so can old fw run on unlocked bootloader? [or would it get bootloop or damage bootloader]

Stagefright updates.

Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?

They better should enable bootloader unlocking for everyone.
Then each LG user can flash his own ROM and solve security issues very quickly with the community.
Nice announcement, but the stagefrighter hole is gaping and gaping...

*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
you have unlocked the bootloader, so you have a custom recovery and could of course install any rom .
Sure at the moment there are not a lot roms available, but the official ones are however posted...
beside that, i don't think that unlocking the bootloader (and rooting the phone) will disable the OTA feature...

alain57 said:
you have unlocked the bootloader, so you have a custom recovery and could of course install any rom .
Sure at the moment there are not a lot roms available, but the official ones are however posted...
beside that, i don't think that unlocking the bootloader (and rooting the phone) will disable the OTA feature...
Click to expand...
Click to collapse
Not? On HTC OTA updates were not possible...
Yes those custom roms.... Sigh... I think we will get them if a can choose another phone[emoji3]

Or... Use an app with built in protection for that issue?

*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
As I read OTA won't work on a unlocked phone.
But you can get the KDZ and flash this - you will need to root again though...
Greetings
Medzinmann

*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
You will still be able to receive the updates, unlocking the bootloader does not stop you receiving OTA updates.

Medizinmann said:
As I read OTA won't work on a unlocked phone.
But you can get the KDZ and flash this - you will need to root again though...
Greetings
Medzinmann
Click to expand...
Click to collapse
the bootloader itself does not change anything to the OTA process
but changing the recovery may block the OTA from working ... the phone may download the update but the custom recovery may not understand it :silly:
but most of the time, people find a way to create a flashable zip to make an update for custom recovery

alain57 said:
the bootloader itself does not change anything to the OTA process
but changing the recovery may block the OTA from working ... the phone may download the update but the custom recovery may not understand it :silly:
but most of the time, people find a way to create a flashable zip to make an update for custom recovery
Click to expand...
Click to collapse
I didn't try it myself, but people in the low effort root thread wrote it didn't work.
They got an error like "update not possible - suspicious root" or something.
http://forum.xda-developers.com/showthread.php?p=62250050
I will try today and see if it works.
I could download the OTA Update, if it works I will try this evening.
Greetings
Medzinmann

Medizinmann said:
I didn't try it myself, but people in the low effort root thread wrote it didn't work.
They got an error like "update not possible - suspicious root" or something.
http://forum.xda-developers.com/showthread.php?p=62250050
I will try today and see if it works.
I could download the OTA Update, if it works I will try this evening.
Greetings
Medzinmann
Click to expand...
Click to collapse
Yeah they couldn't OTA as they had rooted, not because they had unlocked their bootloader.
OTA are still made available to people with unlocked bootloaders, just not to people who have rooted. At the end of the day you can just find the KDZ and flash it to update or make an update zip to do it from custom recovery.

IIIIkoolaidIIII said:
Yeah they couldn't OTA as they had rooted, not because they had unlocked their bootloader.
OTA are still made available to people with unlocked bootloaders, just not to people who have rooted. At the end of the day you can just find the KDZ and flash it to update or make an update zip to do it from custom recovery.
Click to expand...
Click to collapse
That might be right, but as they said a simple unroot wouldn't work.
And BTW what is the point in unlocking the bootloader when you don't want to root?
I mean custom rom maybe but they are usually rooted as well for obvious reasons etc.
Greetings
Medzinmann

Medizinmann said:
That might be right, but as they said a simple unroot wouldn't work.
And BTW what is the point in unlocking the bootloader when you don't want to root?
I mean custom rom maybe but they are usually rooted as well for obvious reasons etc.
Greetings
Medzinmann
Click to expand...
Click to collapse
Unrooting via flashing a clean image worked fine for me, got OTA and then flashed new root.

IIIIkoolaidIIII said:
Unrooting via flashing a clean image worked fine for me, got OTA and then flashed new root.
Click to expand...
Click to collapse
As I said one could always get the most recent KDZ and flash this and reroot. A working OTA would make this just a little more convenient...that's all.
Greetings
Medzinmann

Just unroot, uninstall SuperSu and fire up LG Bridge. Install update. Flash root with twrp. Finish. Did that yesterday.
Sent from outer space using telepathy

does the new update fix stagefright?

On t-mobile it did.
Sent from my LG-H811 using XDA Free mobile app

Alright so I have a problem with the touch functionality of my phone. I have an LG G4 811 T-mobile variant. The new update is supposed to resolve that but I'm not sure how to update on a rooted device with twrp installed (update stagefrieght). I'm looking for a zip file and i have not managed to find it at all. Could someone help? Also if this is misplaced please devs move it or point me in the right direction to which my question can be answered.
---------- Post added at 02:25 AM ---------- Previous post was at 02:24 AM ----------
fpsq said:
Just unroot, uninstall SuperSu and fire up LG Bridge. Install update. Flash root with twrp. Finish. Did that yesterday.
Sent from outer space using telepathy
Click to expand...
Click to collapse
and this for sure worked with you?

Yes, it worked perfectly fine for my LG G4 H815 unlocked! Now on V10d-EUR-XX. Stagefright is fixed. ****ing sim issue (com.android.phone crashes, does NOT restart itself) remains. Support is worthless. Found a workaround myself.

LG lied about that updates. They never repaired these bugs and now it has About 50 stagefright etc vurnerabilities.

What updates you say? I'm still on V20D since January LoL LG is a joke.
Στάλθηκε από το LG-H815 μου χρησιμοποιώντας Tapatalk

Downgrade 7 to 6, it's possible?

Hello how are you?
I was bothering you to ask them a question, is it possible to downgrade the Moto X Style Pure?
2 months ago I updated it to Android 7 and it was the worst mistake I could make the phone was slow it takes to open any application, its crash, I restart it 3 or 4 times a day.
Is there any way to go back to Android 6 so we can install LineageOs Oficial?
Thank you so much.
Greetings.
Sorry to use the Google translator

Yes it is possible.
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
System sparsechunk files could be more - download .zip for your model/region and you will see.
Downgrade: without gpt and bootloader partitions( don't flash 2nd & 3rd line).
After downgrade you cannot allow any ota update.

dzidexx said:
Yes it is possible.
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
System sparsechunk files could be more - download .zip for your model/region and you will see.
Downgrade: without gpt and bootloader partitions( don't flash 2nd & 3rd line).
After downgrade you cannot allow any ota update.
Click to expand...
Click to collapse
Thank You!

How's the downgrade going? i was thinking of doing the same thing. Do you have any tips and tricks?

danshop said:
How's the downgrade going? i was thinking of doing the same thing. Do you have any tips and tricks?
Click to expand...
Click to collapse
i tried the downgrade too but made the mistake of installing OTA upgrades. it totally hardbricked my phone. after a few days of trying it's still 99% unresponsive and only shows a black screen. i'm on the brink of giving it up although it pains me because it's a good phone and seeing it dead by software is not how a phone should end

kjoetools said:
i tried the downgrade too but made the mistake of installing OTA upgrades. it totally hardbricked my phone. after a few days of trying it's still 99% unresponsive and only shows a black screen. i'm on the brink of giving it up although it pains me because it's a good phone and seeing it dead by software is not how a phone should end
Click to expand...
Click to collapse
Sorry to hear that.. i feel like if you look hard enough here in the forums there's a fix for it. I was thinking of doing the same thing but i decided not too cause i don't fully understand the process.

If i downgrade from android 7 to 6 can i install manually OTA's for update it again by nougat?

liog said:
If i downgrade from android 7 to 6 can i install manually OTA's for update it again by nougat?
Click to expand...
Click to collapse
No, it will hard-brick... You must flash a full factory image.