Related
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]
*EDIT*
Disregard PSA, SunShine works on SU4TL-44 and SU4TL-49 now.
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
Where is this or what is this beta u speak of?
Sent from my XT1254 using XDA-Developers mobile app
hm,i only choose to update the offical mm...but thx to warning us
gangrenius said:
Where is this or what is this beta u speak of?
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a soak test.
No! It's a OTA update. You should have it right now. Check for updates. I just installed it last night with no problems. I installed a stock rom. Ran the update, Then rooted again. Simple
@ChazzMatt is speaking of the Marshmallow soak test. @smooth781 is speaking of the Droid Turbo OTA that is still 5.1 (23.21.49.en.US). Both were mentioned in op.
jcase said:
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
gangrenius said:
Where is this or what is this beta u speak of?
Click to expand...
Click to collapse
ChazzMatt said:
It's a soak test.
Click to expand...
Click to collapse
smooth781 said:
No! It's a OTA update. You should have it right now. Check for updates. I just installed it last night with no problems. I installed a stock rom. Ran the update, Then rooted again. Simple
Click to expand...
Click to collapse
Please actually read the thread before replying. The op clearly mentioned the 6.0 beta and someone asked about it. I answered.
6.0 beta = the Marshmallow soak test.
The Marshmallow soak test is by invitation only and is not an OTA update. Emails went out several days ago.
One of the Quarks (XT1225) already has Marshmallow, and now the Verizon Droid Turbo is being tested for Marshmallow. Chop Chop action is removed in official Marshmallow ROM, or at least it was by the final soak test of the Brazil XT1225 Soak Test #3. It was still there in Soak Test #1.
It's also being removed from the Marshmallow custom ROMs (CM13 and Resurection Remix), at least until the CM dev figures out why Motorola removed it and if it's safe to put back.
Thanks to XDA devs, we've had Marshmallow for months now -- no thanks to Motorola.
ChazzMatt said:
It's also being removed from the Marshmallow custom ROMs (CM13 and Resurection Remix), at least until the CM dev figures out why Motorola removed it and if it's safe to put back.
Thanks to XDA devs, we've had Marshmallow for months now -- no thanks to Motorola.
Click to expand...
Click to collapse
Do you have any idea what the rationale is for removing it from CM, and therefore RR? Why would a feature like this be considered "unsafe?" I use it pretty regularly and if the next RR update implements this, I will not be updating.
@baybutcher27, what are your thoughts on this?
TheSt33v said:
Do you have any idea what the rationale is for removing it from CM, and therefore RR? Why would a feature like this be considered "unsafe?" I use it pretty regularly and if the next RR update implements this, I will not be updating.
@baybutcher27, what are your thoughts on this?
Click to expand...
Click to collapse
Motorola removed it from the Quark Marshmallow ROM, final soak test #3.
CM dev then removed it -- at least for now. Resurrection Remix is CM based.
Skrilax_CZ said:
The reason is proprietaries have been updated to soak #3 as well. It'll keep it disabled until I learn more about why it was disabled.
Click to expand...
Click to collapse
It may be added back in the future.
Wait, Would I be able to update? I've unlocked the bootloader, and am rooted on stock rom.
What would I need to do?
KOAO said:
Wait, Would I be able to update? I've unlocked the bootloader, and am rooted on stock rom.
What would I need to do?
Click to expand...
Click to collapse
I assume if your bootloader is unlocked and you are rooted that you have TWRP custom recovery. Pretty sure OTA would fail. But that's not a bad thing. You don't want to be the one to find out the OTA locks your bootloader permanently. (Probably wouldn't, since you are already unlocked, and having custom recovery will prevent the OTA from installing -- but still you don't want to be the one to find out this time Verizon did something very sneaky.)
If your bootloader is unlocked, you would manually flash the eventual official Marshmallow XT1254 update manually -- not taking it as an "OTA". There will be download links available here on XDA. And you would wait until others have done it first.
Or you would flash a custom Marshmallow ROM, again manually -- either one by @computerfreek274 which would be stock-based (not available yet) or a CM13-based ROM (CM13 or Resurrection Remix) or an AOSP-based ROM (Mokee).
We already have three custom Marshmallow ROMs for ALL Quarks -- CM13, Resurrection Remix, Mokee and Motorola recently finalized stock ROM for the other Quark, the XT1225.
As soon as Motorola/Verizon get their act together for the XT1254/XT1250, you will have a stock Marshmallow ROM available to flash for the XT1254 and @computerfreek274 will also release a "stock-based" ROM for people to flash -- if you want to stay with pure stock or stock-based.
My cell standby battery drain has taken a turn for the worse since updating the modem. It worked fine (comparatively) in the past. Anyone else have this issue? I'm going to flash back the old modem and see if it fixes things.
Edit: Yup, flashed back to 44 and it's back to normal.
drizzzzzz said:
My cell standby battery drain has taken a turn for the worse since updating the modem. It worked fine (comparatively) in the past. Anyone else have this issue? I'm going to flash back the old modem and see if it fixes things.
Edit: Yup, flashed back to 44 and it's back to normal.
Click to expand...
Click to collapse
Yeah, the OTA update was basically worthless -- just an excuse to prevent Sunshine from working to unlock the bootloader.
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
i need relock the bootloader , my power botom is broke somebody knows how i can relock it , thanks
sorry for my bad english...
jorgkrkmo said:
i need relock the bootloader , my power botom is broke somebody knows how i can relock it , thanks
sorry for my bad english...
Click to expand...
Click to collapse
Don't lock it. Leave it unlocked, even if you send it in.
is there a chance sunshine will be updated to unlock the new version as well?
rhcreed said:
is there a chance sunshine will be updated to unlock the new version as well?
Click to expand...
Click to collapse
Theres a "chance" but a very slim one. The sunshine devs are not going to pour time and effort into it, but if they do find an exploit they will update it
rhcreed said:
is there a chance sunshine will be updated to unlock the new version as well?
Click to expand...
Click to collapse
The exploit they used has been closed.
Wynnded said:
The exploit they used has been closed.
Click to expand...
Click to collapse
can the phone be reverted to an unlock able version?
rhcreed said:
can the phone be reverted to an unlock able version?
Click to expand...
Click to collapse
No. Stock firmware with locked bootloader is not downgradeable.
People were told from the very beginning NOT to take the update unless your bootloader was unlocked first. Not just in this thread but several others.
Anyone who took the SU4TL-49 update with a locked bootloader does not care about unlocking their bootloader.
1) the Sunshine exploit has been available since November 2015. People have had six months to unlock their bootloaders! Why is it suddenly important now?
2) the Android SU4TL-49 update only showed up less than two weeks ago (early May 2016). It's the first firmware update since the exploit was released.
3) People were warned Android SU4TL-49 would close the Sunshine exploit. But even common sense would tell people that -- knowing control freak Verizon and their locked down bootloaders.
Hi All,
I'm a little confused as to where us U firmware users stand with Nougat. I've seen differing reports of what the known plan is with this. I believe some are saying we're waiting for Verizon to release it to the 935u, otherwise I'm reading that we're on a quarterly update schedule and won't be seeing anything until April.
I bought my 935V from VZW and flashed over to unrooted U firmware - actually by using the normal flash method and then doing a firmware restore from verizon's utility to get full unroot. Not exactly a typical method, but it gave me peace of mind knowing everything is completely stock U.
Everything is running great so I'm not in urgent need of an update for any reason, but would like to see some new features.
Lemme know if anyone has any clues here as for what to expect. Thanks in advance!
Not exactly sure what you mean by going full "unroot".. unless you ment, you wanted the U firmware for a smoother "root" can you please clarify bubby?
---------- Post added at 05:56 AM ---------- Previous post was at 05:51 AM ----------
Action123 said:
Hi All,
I'm a little confused as to where us U firmware users stand with Nougat. I've seen differing reports of what the known plan is with this. I believe some are saying we're waiting for Verizon to release it to the 935u, otherwise I'm reading that we're on a quarterly update schedule and won't be seeing anything until April.
I bought my 935V from VZW and flashed over to unrooted U firmware - actually by using the normal flash method and then doing a firmware restore from verizon's utility to get full unroot. Not exactly a typical method, but it gave me peace of mind knowing everything is completely stock U.
Everything is running great so I'm not in urgent need of an update for any reason, but would like to see some new features.
Lemme know if anyone has any clues here as for what to expect. Thanks in advance!
Click to expand...
Click to collapse
But anyway, lol. You are correct of the U FW being released somewhere around April. Verizon isn't responsible for U firmware, Samsung is.. I'm actually surprised Verizon released before U
vsn4 said:
Not exactly sure what you mean by going full "unroot".. unless you ment, you wanted the U firmware for a smoother "root" can you please clarify bubby?
---------- Post added at 05:56 AM ---------- Previous post was at 05:51 AM ----------
But anyway, lol. You are correct of the U FW being released somewhere around April. Verizon isn't responsible for U firmware, Samsung is.. I'm actually surprised Verizon released before U
Click to expand...
Click to collapse
Good to know. Thanks.
I had to root in order to flash U FW, but the root process we have for GS7 is really process heavy and battery draining. I wanted an unrooted version of the U firmware with no bullsh*t and good battery life so I unrooted and restored using the software tool.
Action123 said:
Good to know. Thanks.
I had to root in order to flash U FW, but the root process we have for GS7 is really process heavy and battery draining. I wanted an unrooted version of the U firmware with no bullsh*t and good battery life so I unrooted and restored using the software tool.
Click to expand...
Click to collapse
Ah Gotcha, sorry I misunderstood the op. Maybe give the T or V carrier FW a spin till U gets released? I haven't upgraded yet but am tempted. Been using stang 5.0 rom and been pretty impressed. I'd say I would recommend it even with the faults of the eng boot.
I also believe I seen a "no root no bull**** playstore Nougat rom" by jkruse, or something to that effect. If that's something your into
Lots of cry babies over in the Samsung forums. I can see why everyone is so upset but Samsung never promised faster updates for unlocked variants over carrier models. I'm content waiting at least until April for the nougat release of the 935u. Screw Verizon bloat. It's not worth putting up with it for Nougat.
There are some articles with Samsung's new commitment for monthly security updates on unlocked devices. This should mean that the 935U will get Nougat this month with March security update.
junear said:
There are some articles with Samsung's new commitment for monthly security updates on unlocked devices. This could mean that the 935U will get Nougat this month with March security update.
Click to expand...
Click to collapse
Fixed.
Expect nothing. Never get disappointed.
Magnus_CA said:
Lots of cry babies over in the Samsung forums. I can see why everyone is so upset but Samsung never promised faster updates for unlocked variants over carrier models. I'm content waiting at least until April for the nougat release of the 935u. Screw Verizon bloat. It's not worth putting up with it for Nougat.
Click to expand...
Click to collapse
Well, sorta agree with you. I'm patiently waiting for the U update to 7.0, but in the mean time I'm running the Verizon update on a backup device. I can't really enjoy 6.0.1's UI after having Grace UX.
G935U Nougat (G935UUEU4BQD2) is now available!
check samfirm and sammobile for downloads of firmware G935UUEU4BQD2 (7.0)!
jtash01 said:
check samfirm and sammobile for downloads of firmware G935UUEU4BQD2 (7.0)!
Click to expand...
Click to collapse
Smart Switch PC can also do an in-place update to 7.0. It's the April security patch.
I've downloaded the nougat U firmware and can't get it to install over the latest VZW firmware, the one that came out in the last few days. Has anyone been able to, if so please outline your steps.
I have U firmware on Verizon s7 edge works as charm. Use latest Odin to install the firmware
seemcity said:
I have U firmware on Verizon s7 edge works as charm. Use latest Odin to install the firmware
Click to expand...
Click to collapse
which is latest odin I've tried 3.10 3.11 3.12
gunnyman said:
I've downloaded the nougat U firmware and can't get it to install over the latest VZW firmware, the one that came out in the last few days. Has anyone been able to, if so please outline your steps.
Click to expand...
Click to collapse
I would flash the full Odin package for U 6.0 and then use Smart Switch PC to update to 7.0.
http://updato.com/firmware-archive-select-model?record=08ABA51C2C6F11E7963AFA163EE8F90B
Can anyone on an UDP confirm if you can tether the unlocked software of the 935u on 7.0 nougat now that it is out?
RyanEJ25 said:
Can anyone on an UDP confirm if you can tether the unlocked software of the 935u on 7.0 nougat now that it is out?
Click to expand...
Click to collapse
Yes i have the original UDP and the tethering option works. How ever i cant get the verizon video calling to work??
So from what I'm getting, to install (if I'm on Verizon Nougat), flash Unlocked 6.0 first, then smart switch to 7.0? Also, I read that someone had been having issues with using LTE while in a phone call, can anyone confirm? And what happened to all the other fix files, since I remember the first time flashing the unlocked software required more subsequent flashes as well.
Can someone post the links for the latest fastboot ROMs for potter? I've been looking for them for two days and I couldn't find them. It'd be nice if someone could post full fastboot ROMs of all variants or if there's already a thread in here, kindly let me know. I'm looking for the fastboot ROM for Indian variant and yes I have looked a free threads here.
psychopac said:
Can someone post the links for the latest fastboot ROMs for potter? I've been looking for them for two days and I couldn't find them. It'd be nice if someone could post full fastboot ROMs of all variants or if there's already a thread in here, kindly let me know. I'm looking for the fastboot ROM for Indian variant and yes I have looked a free threads here.
Click to expand...
Click to collapse
We don't have it... All Moto firmware is leaked, they don't just give it away, and we might get it a few weeks after the OTA comes out, months, or sometimes never, we don't know.
If/when we get it, I'm sure it I'll be posted here and at http://firmware.center
acejavelin said:
We don't have it... All Moto firmware is leaked, they don't just give it away, and we might get it a few weeks after the OTA comes out, months, or sometimes never, we don't know.
If/when we get it, I'm sure it I'll be posted here and at http://firmware.center
Click to expand...
Click to collapse
So if I update to the latest version and something goes wrong and I flash the older build, will everything be fine? I heard that downgrading causes problems in Motos. Is that true?
psychopac said:
So if I update to the latest version and something goes wrong and I flash the older build, will everything be fine? I heard that downgrading causes problems in Motos. Is that true?
Click to expand...
Click to collapse
I am not going to lie, it is true in some cases... we know that you cannot downgrade the bootloader, no matter what you do, so sometimes if you downgrade everything else but gpt.bin and bootloader.img (two things that can't be downgraded, partition table and bootloader), it has been known to cause bricking in some devices if you take an OTA later, and sometimes it doesn't.
For example, the Moto X Style/Pure Edition you could upgrade and downgrade on a whim between Lollipop and Marshmallow with not problem, take OTA's or whatever and it was fine... Then along came Nougat... if you downgraded from Nougat to Marshmallow, then took the Nougat OTA again it was instant hard brick (completely unrecoverable). My point is we don't know until someone tries it... :/
acejavelin said:
I am not going to lie, it is true in some cases... we know that you cannot downgrade the bootloader, no matter what you do, so sometimes if you downgrade everything else but gpt.bin and bootloader.img (two things that can't be downgraded, partition table and bootloader), it has been known to cause bricking in some devices if you take an OTA later, and sometimes it doesn't.
For example, the Moto X Style/Pure Edition you could upgrade and downgrade on a whim between Lollipop and Marshmallow with not problem, take OTA's or whatever and it was fine... Then along came Nougat... if you downgraded from Nougat to Marshmallow, then took the Nougat OTA again it was instant hard brick (completely unrecoverable). My point is we don't know until someone tries it... :/
Click to expand...
Click to collapse
That's a bummer. Anyways I hope that no one bricks their phone
I'm not well versed in this realm of rooting, but I've rooted my V20 (H918) and I'd like to update to the latest version possible and not lose root. I think it involves using some kdz file or something and flashing that, is that right? Let me know, thank you.
Wrong, you have to use this @runningnak3d tutorial to go back to root...but so far, even if you are on H91010T, you can roll back and root. ARB has not yet been implemented on this phone, so you're good to use any rooting method you see fit in this forum. Enjoy!
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
jreed3786 said:
Wrong, you have to use this @runningnak3d tutorial to go back to root...but so far, even if you are on H91010T, you can roll back and root. ARB has not yet been implemented on this phone, so you're good to use any rooting method you see fit in this forum. Enjoy!
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Click to expand...
Click to collapse
I think you may be responding to the wrong thread? I wasn't asking how to root, I've already rooted my phone. Also, I said I have a H918, not a H91010T.
Mr December said:
I think you may be responding to the wrong thread? I wasn't asking how to root, I've already rooted my phone. Also, I said I have a H918, not a H91010T.
Click to expand...
Click to collapse
Oops!!!! LOL! That darn 8 looked like a 0! My bad, bro! LOL. Late night!!!
You can use kdz writter to upgrade to kdz with new security updates. You will not lose root.
jreed3786 said:
Wrong, you have to use this @runningnak3d tutorial to go back to root...but so far, even if you are on H91010T, you can roll back and root. ARB has not yet been implemented on this phone, so you're good to use any rooting method you see fit in this forum. Enjoy!
https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Click to expand...
Click to collapse
Wait i thought ARB was implemented on the lg v20 already, does that mean if i am on H91810Q, (T-Mobile) i don't have ARB yet?
jreed3786 said:
Oops!!!! LOL! That darn 8 looked like a 0! My bad, bro! LOL. Late night!!!
Click to expand...
Click to collapse
Haha, it's alright, man.
shomi1417 said:
You can use kdz writter to upgrade to kdz with new security updates. You will not lose root.
Click to expand...
Click to collapse
Thank you, I'll research this and see how to go about this.
do not use anything kdz to flash... you will lose root! you need to flash a TWRP flashable zip to update and keep root
dimm0k said:
do not use anything kdz to flash... you will lose root! you need to flash a TWRP flashable zip to update and keep root
Click to expand...
Click to collapse
Thank you! That would've been atrocious. Can you point me to a guide that explains this? I'd hate to make a rookie mistake like I would've made and accidentally update the firmware past 10J.
Mr December said:
Thank you! That would've been atrocious. Can you point me to a guide that explains this? I'd hate to make a rookie mistake like I would've made and accidentally update the firmware past 10J.
Click to expand...
Click to collapse
I don't know what version of H918 you're on now, but if I'm not mistaken 10k is the last one that you can still mess up and still get root back by downgrading to an earlier version, root and then upgrade. any version after 10k will increment ARB to 1 whereby you will not be able to get root if you lose it. that said, the latest version out now is 10s and if you have root then you should also have TWRP. here's my guide for updating to the latest versions while keep root https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312. looking at this now, I haven't posted the 10s update file, which I will do now... keep in mind that if you update to 10s that if you lose TWRP you'll be fscked and stuck without root, which at this point could be permanently.
EDIT: 10s is a go! original post updated with link. also removing the older versions from Google Drive to free up space... if they're still needed, PM
dimm0k said:
I don't know what version of H918 you're on now, but if I'm not mistaken 10k is the last one that you can still mess up and still get root back by downgrading to an earlier version, root and then upgrade. any version after 10k will increment ARB to 1 whereby you will not be able to get root if you lose it. that said, the latest version out now is 10s and if you have root then you should also have TWRP. here's my guide for updating to the latest versions while keep root https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312. looking at this now, I haven't posted the 10s update file, which I will do now... keep in mind that if you update to 10s that if you lose TWRP you'll be fscked and stuck without root, which at this point could be permanently.
EDIT: 10s is a go! original post updated with link. also removing the older versions from Google Drive to free up space... if they're still needed, PM
Click to expand...
Click to collapse
Man that is awesome news! Thank you for linking me to your guide. I will do it tonight when I have the time! My current version is 10J, btw.
Mr December said:
Man that is awesome news! Thank you for linking me to your guide. I will do it tonight when I have the time! My current version is 10J, btw.
Click to expand...
Click to collapse
if you're willing to take on the risk then go ahead... I did and am still rooted. just ask questions if you have any doubts
Will this work for the Verizon model?
dimm0k said:
if you're willing to take on the risk then go ahead... I did and am still rooted. just ask questions if you have any doubts
Click to expand...
Click to collapse
Hey, I followed the instructions per your thread and successfully installed 10s and kept root! The bad news is that I did a factory reset immediately after and now it keeps bootlooping into TWRP. Any idea how to fix this? Sadly I didn't make a backup because my microsd card was too small and I didn't have the patience to wait til tomorrow and go out and buy one, really hope I didn't kick myself in the ass and brick my phone. :crying:
Edit:
I was able to find a fix by following these instructions:
"I had this happen to me after installing TWRP for the first time. It would keep rebooting to TWRP. This was after making sure I flashed SuperSU as well. Eventually in a moment of "might as well see what will happen" I rebooted then held down the power button and volume down. Got to the option if I wanted to factory reset my phone which I did which booted into TWRP. Rebooted to system from there which got me out of the TWRP Bootloop."
I also set my phone up again and can confirm that 10s is still good with root! Thanks for the guide and work, man. Much appreciated!