Hi!
Has anyone installed the update OTA on a rooted g pad?
Is it safe to do it or it's not possible?
How can I install the update if I am rooted and keep my root?
goldengutz13 said:
Hi!
Has anyone installed the update OTA on a rooted g pad?
Is it safe to do it or it's not possible?
How can I install the update if I am rooted and keep my root?
Click to expand...
Click to collapse
I have seen people reporting problems in other threads here on XDA. Here in the US they haven't yet released the OTA update. If this is anything like my experience with my phone (a GS3). OTA update of a factory rom when rooted often does seem to cause problems. The only device I haven't had problems with taking an OTA when rooted were a Nexus device (Nexus 7) and something running CyanogenMod.
muiriddin said:
I have seen people reporting problems in other threads here on XDA. Here in the US they haven't yet released the OTA update. If this is anything like my experience with my phone (a GS3). OTA update of a factory rom when rooted often does seem to cause problems. The only device I haven't had problems with taking an OTA when rooted were a Nexus device (Nexus 7) and something running CyanogenMod.
Click to expand...
Click to collapse
so I have to unroot it first, install update then root again?
I have a related question - how to unroot and install OTA??
I tried to install, but it didn´t work, tablet said there´s no OTA for rooted devices.
I unrooted using SuperSU, but the situation is still the same.
Dekxster said:
I have a related question - how to unroot and install OTA??
I tried to install, but it didn´t work, tablet said there´s no OTA for rooted devices.
I unrooted using SuperSU, but the situation is still the same.
Click to expand...
Click to collapse
I used the LG Support Tool method which involves putting the tablet into download mode and doing the update recovery procedure in the LG Support Tool. This (after a long download process) should result in a tablet which is identical to what came in the box. (in the US the procedure currently installs 4.2.2). When it finished the download and install, it reboots the tablet, if you then are stuck in a boot loop, simply do the key combination for a factory reset and it then should boot.
The unroot procedure via SuperSU does seem to leave something behind that the OTA still detects...
If you need further details I have another post in one of these threads detailing exactly what I did...
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
goldengutz13 said:
so I have to unroot it first, install update then root again?
Click to expand...
Click to collapse
That is what I plan on doing once the US version is released, however it is potentially a little more complicated since I have heard that LG has patched the LOKI vulnerability which means no custom roms or custom recovery until a new boot loader vulnerability is found, or until you revert to the original boot loader instead of the new one in the 4.4.2 release (if possible)...
muiriddin said:
That is what I plan on doing once the US version is released, however it is potentially a little more complicated since I have heard that LG has patched the LOKI vulnerability which means no custom roms or custom recovery until a new boot loader vulnerability is found, or until you revert to the original boot loader instead of the new one in the 4.4.2 release (if possible)...
Click to expand...
Click to collapse
Nah. You can bet that within 48 hours after the US version is released, there will be a flashable build available with root and recovery.
Subtleone said:
Nah. You can bet that within 48 hours after the US version is released, there will be a flashable build available with root and recovery.
Click to expand...
Click to collapse
True, more than likely a flash-able version will exist once someone makes it.
It already has a work around for loki by reinstalling the old aboot
http://forum.xda-developers.com/showthread.php?t=2698267
Just do steps 2 and 3.
Works fine on mine
Sent from my LG-V500 using xda app-developers app
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
I think the issue with this procedure is the recovery / bootloader, not the rooting itself. Still, you will most likely end with an unbootable OS. You are better off flashing via recovery a perfectly stock, pre-rooted image, like this http://forum.xda-developers.com/showthread.php?t=2707363
Trunkam said:
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
Click to expand...
Click to collapse
When you use the lg tool (pc software) did it automatically download the kitkat update?
Did you encounter any issue when you used lg tool?
Trunkam said:
I upgraded Via OTA my rooted lgpad and when it rebooted... stuck in recovery.
So i had to flash with lg tool.
I did not lose any data but a bit of time.
My suggestion is to flash with lg tool and then root again.
sent from tablet
Click to expand...
Click to collapse
So you did NOT unroot first?
Steps you did were: (with rooted only g pad)
Update via pc lg tool
Root using IOROOT25.zip method
This correct?
goldengutz13 said:
When you use the lg tool (pc software) did it automatically download the kitkat update?
Did you encounter any issue when you used lg tool?
Click to expand...
Click to collapse
I had to click on "recover" Something sorry I have no my PC now.. I left it at work. But I think you'll find.
U got some option and considering lgpad did not boot after update.. I had only one.
It's the procedure that you got to follow after you set gpad in download mode.
No issue at all, just one thing: after rooting you will have to flash a custom recovery if you need, because flashing with lg, flash even lg stock recovery.
erwaso said:
So you did NOT unroot first?
Steps you did were: (with rooted only g pad)
Update via pc lg tool
Root using IOROOT25.zip method
This correct?
Click to expand...
Click to collapse
No I did not unroot.. But only because I did not think about it. And that's the reason why gpad was not able to boot to system and I had to flash it via lg software.
I set gpad in download mode,,then flash via lg software, root with ioroot and finally flashed with flashify custom recovery
Hope to have helped guys
Now I'll go to sleep!
tapatalked..
I updated to version 4.4.2 Via OTA my rooted gpad and not had any problems
Steps:
1- factory reset
2- update via OTA
Attention: I think the rom has to be original (no eliminated sys apps with titanium or other) because it goes check the integrity of the rom (4.2.2)
------------------------------------------------------------ Edit --------------------------------------------------------------------------
3- Rooted with IOroot25
I've done an OTA update on my rooted G Pad, no issues either. I didn't do a factory reset, just did the update.
I updated my rooted v500 2 days ago using LGs PC software. The process took around 45 minutes and resulted in a successful KitKat update, however I no longer have root. I have a few strange issues with random unmounting of the SD card, which happened about 4 times while Play Music was copying 2gig of on device songs to it. I also seem to have lost quiet mode - maybe it's been moved out of the sound settings menu - would appreciate a comment if anyone knows where it is.
Sent from my LG-V500 using Tapatalk
Hugo-PT said:
I updated to version 4.4.2 Via OTA my rooted gpad and not had any problems
Steps:
1- factory reset
2- update via OTA
Attention: I think the rom has to be original (no eliminated sys apps with titanium or other) because it goes check the integrity of the rom (4.2.2)
Click to expand...
Click to collapse
I froze a few apps using rom toolbox, think that would matter?
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
GePeKo said:
I updated my rooted v500 2 days ago using LGs PC software. The process took around 45 minutes and resulted in a successful KitKat update, however I no longer have root. I have a few strange issues with random unmounting of the SD card, which happened about 4 times while Play Music was copying 2gig of on device songs to it. I also seem to have lost quiet mode - maybe it's been moved out of the sound settings menu - would appreciate a comment if anyone knows where it is.
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
The development section has a thread on IOROOT and it works. Have at it! I'll do this whole thing when the kids nap lol
erwaso said:
I froze a few apps using rom toolbox, think that would matter?
Click to expand...
Click to collapse
with frozen apps you shall have no problems.
Related
Greetings,
I have the Lg g pad running 4.2.2 and today i received an update (OTA) . Anyone knows what oa this update and second i am root and i cant install it because after reboot for installation i am going to custom recovery. Any way to sideload this update with out going back to full stock unroot?
Edit: i tried to reboot several times the devixe bit getting always to TWRP . I tried to restore full img but the same also i wiped data . I keep gettong to custom recovery trying to install the ota. Any ideas?
Cheers Vatis
OTA V50010B Screenshot
vatis24 said:
Greetings,
I have the Lg g pad running 4.2.2 and today i received an update (OTA) . Anyone knows what oa this update and second i am root and i cant install it because after reboot for installation i am going to custom recovery. Any way to sideload this update with out going back to full stock unroot?
Edit: i tried to reboot several times the devixe bit getting always to TWRP . I tried to restore full img but the same also i wiped data . I keep gettong to custom recovery trying to install the ota. Any ideas?
Cheers Vatis
Click to expand...
Click to collapse
Here is the screenshot, it seems its only a lg apps update.
vatis24 said:
Greetings,
I have the Lg g pad running 4.2.2 and today i received an update (OTA) . Anyone knows what oa this update and second i am root and i cant install it because after reboot for installation i am going to custom recovery. Any way to sideload this update with out going back to full stock unroot?
Edit: i tried to reboot several times the devixe bit getting always to TWRP . I tried to restore full img but the same also i wiped data . I keep gettong to custom recovery trying to install the ota. Any ideas?
Cheers Vatis
Click to expand...
Click to collapse
If you have custom recovery and root the ota update obviously wont work. I had asked the developer of root for our devices for the otas and this is what he had said:
dalingrin said:
My suggestion, if you want to keep root don't take an OTA.
If you really want to stay with stock LG then you'll want to flash updates via custom recovery. The community will take the updates from LG and make them flashable with TWRP or CWM.
Click to expand...
Click to collapse
so you ll have to wait for someone to make this update a flashable zip.
katsika said:
If you have custom recovery and root the ota update obviously wont work. I had asked the developer of root for our devices for the otas and this is what he had said:
so you ll have to wait for someone to make this update a flashable zip.
Click to expand...
Click to collapse
Thanks file katsika for the reply .
The problem i stucked now in TWRP
I tried to restore system with no suceess , i tried to flash a new rom .zip ,installed fine but booting the TWRP always
Cheers
Vatis
vatis24 said:
Thanks file katsika for the reply .
The problem i stucked now in TWRP
I tried to restore system with no suceess , i tried to flash a new rom .zip ,installed fine but booting the TWRP always
Cheers
Vatis
Click to expand...
Click to collapse
Yeah there is a script that runs when you do a OTA. My buddy had to completely restore to stock using download mode to fix his. You may get lucky with doing a factory wipe but sounds like flashing a new rom didn't even help... Look through the forums and find the thread that guides you through doing a regular restore (this will restore you to the original software. You will be unrooted and your recovery will go back to stock. This means you can do the OTA if you so desire. Just keep in mind it may block Loki and root)
joshuadjohnson22 said:
Yeah there is a script that runs when you do a OTA. My buddy had to completely restore to stock using download mode to fix his. You may get lucky with doing a factory wipe but sounds like flashing a new rom didn't even help... Look through the forums and find the thread that guides you through doing a regular restore (this will restore you to the original software. You will be unrooted and your recovery will go back to stock. This means you can do the OTA if you so desire. Just keep in mind it may block Loki and root)
Click to expand...
Click to collapse
Thanks for the reply mate,
Yeah i will do like that , but surely there is a way somewhere to remove the boot loop , from TWRP you can remove edit files.
So if someone with more knowledge tell us where the OTA files give the command to boot to recovery we can remove it.
Cheers
vatis24 said:
Thanks for the reply mate,
Yeah i will do like that , but surely there is a way somewhere to remove the boot loop , from TWRP you can remove edit files.
So if someone with more knowledge tell us where the OTA files give the command to boot to recovery we can remove it.
Cheers
Click to expand...
Click to collapse
Post your problem in twrp's thread. Drgravy replies often and he knows more than anyone what to do in a situation like yours.
Thanks all for your help ....
I unbricked the device with FlashTool.1.0.54 , i flashed the original firmware , the strange thing this did not wipe my data, only removed Custom recovery and root.
Cheers
Vatis
For your information i am on rooted stock rom (without custom recovery) and made the ota update and everything seem's to work fine (i didn't lost root)
Thanks a lot!!
achilleas8095 said:
For your information i am on rooted stock rom (without custom recovery) and made the ota update and everything seem's to work fine (i didn't lost root)
Thanks a lot!!
Click to expand...
Click to collapse
Yes the problem fot the.ota is the custom recovery not root
achilleas8095 said:
For your information i am on rooted stock rom (without custom recovery) and made the ota update and everything seem's to work fine (i didn't lost root)
Thanks a lot!!
Click to expand...
Click to collapse
can you please give us a feedback of the OTA, whats changed,impressions ,thought,anything...thanks
Sent from my Thrive using Tapatalk 2
Yeah, i also downloading ota update, i do not know yet what to expect...
Sory guys, no kit kat yet! This is the change (?)
athankar75 said:
Sory guys, no kit kat yet! This is the change (?)
Click to expand...
Click to collapse
what are we looking at exactly:banghead:????maybe brightness correction????
Sent from my Thrive using Tapatalk 2
afrikanac said:
what are we looking at exactly:banghead:????maybe brightness correction????
Sent from my Thrive using Tapatalk 2
Click to expand...
Click to collapse
the software version is v50010b from v50010a
Perhaps the update is by region. I cannot seem to initiate update via OTA or LG PC Suite.
afrikanac said:
can you please give us a feedback of the OTA, whats changed,impressions ,thought,anything...thanks
Sent from my Thrive using Tapatalk 2
Click to expand...
Click to collapse
To be honest I didn't mention any chances , sure they (lg) updated their apps but I haven't notice any system chances , but then again I can't take it from my kids and wife hands!!!!
Just tried the update to a stock (but rooted) Gpad
At 3% installing, error 0x13E
After booting, a samsung-like:laugh: message:
"This device is suspected in rooting. Software update is not available for rooted device"
Fortunately this tablet is not mine... This tablet needs a "google edition" update ASAP
Maybe somebody could cook this update into a package that can be flashed by people who are on stock, but rooted?
I am on stock, rooted, but the update went fine.
Sent from my LG-V500 using Tapatalk
Device was rooted with PurpleDrake, works fine on D85110c, but I'd like the new OTA. I get the OTA notification all the time, but I can't get it to "take". It says installing, reboots and I'm still on the old one. I had Xposed installed with some modules, but uninstalled it all. Any tips on how to make the OTA work, and can I just use PurpleDrake after the OTA to re-root?
Thanks for your patience with the noobtastic post.
I am also freshly rooted with PurpleDrake on 10c with twrp installed. Because of the OTA update, I am not flashing any ROMs until I figure out what to do. I am using a G3 851 on AT&T, so I'm not sure what an update will do. Will it mess with my unlock or APN settings? I'm coming from an HTC M7, so still trying to get myself mentally sound on this device before I just go flash happy all over the place. I'd like to flash a custom rom, but weary if I should update first. I see the zone rom is for the new update, so I guess I'd have to update to run his ROM. Skydragon is still 10c I believe. Any ideas? Sorry to hijack your thread. Lol
Guys, you really should search the forums for an answer. There are numerous threads in regards to the OTA as wll as guides. Your are lucky that the OTA did not apply while rooted. If you happen to also have a custom recovery installed you could have caused yourself a bootloop and would have been stuck. Search option is your friend.
In any case, it is pretty easy to update. Use the link I provided below to install download and install the latest 10m ROM. Just make sure you have everything backed up first, as the preferred method is to wipe everything. I just completed this myself this weekend and all went smooth. Once installed, just root again with PurpleDrake. Installing the permroot appears like it fails and the window closes, but it indeed applies root. You will then just need to download SU and Busybox. Additionally if you want custom recovery, use TWRP manager from play store and install the latest 2.8.01 recovery. Again, all easy if you read the threads. Good luck
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
whodatfan said:
I am also freshly rooted with PurpleDrake on 10c with twrp installed. Because of the OTA update, I am not flashing any ROMs until I figure out what to do. I am using a G3 851 on AT&T, so I'm not sure what an update will do. Will it mess with my unlock or APN settings? I'm coming from an HTC M7, so still trying to get myself mentally sound on this device before I just go flash happy all over the place. I'd like to flash a custom rom, but weary if I should update first. I see the zone rom is for the new update, so I guess I'd have to update to run his ROM. Skydragon is still 10c I believe. Any ideas? Sorry to hijack your thread. Lol
Click to expand...
Click to collapse
I also amd running the Tmobile 851 on AT&T. After update it's no different than what you did the first time, just setup and re-enter the appropriate APN settings. Reboot and your done / back on AT&T network.
OK I think I may be stuck. I gave my phone to wife to check something on the internet and when the notification came up for the update she accepted it. Then handed me my phone back because it got stuck on the TWRP loop. Is there anything to do to get out of this loop? I tried restore from one of my back saves without any luck. Never mind I was able to install the stock ROM in TWRP and got out of the boot loop. Trying to fix and get root and TWRP back now to restore one.
cbb77 said:
Guys, you really should search the forums for an answer. There are numerous threads in regards to the OTA as wll as guides. Your are lucky that the OTA did not apply while rooted. If you happen to also have a custom recovery installed you could have caused yourself a bootloop and would have been stuck. Search option is your friend.
In any case, it is pretty easy to update. Use the link I provided below to install download and install the latest 10m ROM. Just make sure you have everything backed up first, as the preferred method is to wipe everything. I just completed this myself this weekend and all went smooth. Once installed, just root again with PurpleDrake. Installing the permroot appears like it fails and the window closes, but it indeed applies root. You will then just need to download SU and Busybox. Additionally if you want custom recovery, use TWRP manager from play store and install the latest 2.8.01 recovery. Again, all easy if you read the threads. Good luck
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
I also amd running the Tmobile 851 on AT&T. After update it's no different than what you did the first time, just setup and re-enter the appropriate APN settings. Reboot and your done / back on AT&T network.
Click to expand...
Click to collapse
Well. I didn't read this post, before.
I had a G3 D855 V10a rooted with Purpledrake and installed TWRP recovery.
This eveninig I autoupdated my phone to V10g...
After download and reboot, my phone goes into bootloop: it starts only on recovery.
What I have to do, now???
Thanks.
aparty said:
Well. I didn't read this post, before.
I had a G3 D855 V10a rooted with Purpledrake and installed TWRP recovery.
This eveninig I autoupdated my phone to V10g...
After download and reboot, my phone goes into bootloop: it starts only on recovery.
What I have to do, now???
Thanks.
Click to expand...
Click to collapse
Flash back to stock and start over.
Can you explain me what I have to do exactly?
Or can you suggest a guide?
I'm into panic... and I don't found any info, probably due to panic!!!
Help me! Thanks.
aparty said:
Can you explain me what I have to do exactly?
Or can you suggest a guide?
I'm into panic... and I don't found any info, probably due to panic!!!
Help me! Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Step by Step guide with several options
Toneman07 said:
http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Step by Step guide with several options
Click to expand...
Click to collapse
Well, from TWRP recovery I wipe cache, then I use info in this post
http://forum.xda-developers.com/showpost.php?p=55367233&postcount=1
The phone reboot, it seems to apply update, but it restarts with V10a....
I haven't update, but I have my phone!!!
Thank you so much!
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work?
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol. How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Anthony-m said:
I rooted this tablet last week (just rooted, I left it stock) and this morning I notice there is a system update waiting to be installed. I am reading Lollipop is starting to roll out in Asia somewhere now but I am in the US lol. I thought it wasn't possible to get OTA updates once you root? If I allow this to update will I get unrooted, would it even work? .
Click to expand...
Click to collapse
Simply rooting a device doesn't keep it from TRYing to update via OTA. Rooting can prevent an OTA from succeeding, plus can hard or soft brick if you try to take an OTA, although usually only if you've gone beyond just rooting by installing a custom recovery or changing the contents of any partition besides Data by, fire example, downgrading your bootloader (aboot.img) or modem, running a custom kernel, debloating system apps, etc.
There are at least three variants of the G Pad 8.3. I have the VK810.4G, which do you have?
I know on the VK810.4G, Verizon just released a very, very minor update from LG build #23A to 24A. Still KitKat.
I foolishly allowed it to update after checking in Supersu to not allow the root to be lost and now I keep booting directly into TWRP lol.
Click to expand...
Click to collapse
There's the main problem, you had a custom recovery installed. OTAs are applied with the stock recovery, that's why it (probably soft) bricked it.
How do I wipe this tablet from TWRP so that it is fully stock again (NO ROOT)? I see a factory reset option in TWRP do I need to include all the partitions in the advanced wipe or is just the normal wipe method enough? Or will this not work at all? I already tried to restore the phone using TWRP to my backup and that didn't seem to work.
Click to expand...
Click to collapse
You might not be able to fix it from TWRP. You could try @autoprime 's fix recovery zip available the same page his flash2 scripts are. You'll have to Google:
autoprime flash2
Click to expand...
Click to collapse
.
Otherwise, you'll have to restore to 100% stock unrooted and start from scratch. Two methods.
One is using LG's official Mobile Tool, which will download the latest official ROM in KDZ format (takes 20+ minutes to download) and flash it with your tablet in Download mode (probably with the tablet off, hold both up and down volume buttons in and while holding them, turn the tablet on.
I've got to go do something so hopefully someone else will help further or I can get back to you later, dont know when though.
Good luck!
Sent from my VK810 4G
I did the TWRP terminal commands from the thread listed below and it got me right out of that jam...
http://forum.xda-developers.com/lg-g-pad-83/help/vk810-download-mode-boot-loop-t2991512
OK now that I am up and running fine the system update message keeps popping up. This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Anthony-m said:
... This time I KNOW not to try and upgrade while rooted. Is there any way I can stop the tablet from constantly giving me the upgrade message? Can I do anything from TWRP to stop this?
Click to expand...
Click to collapse
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
DeanGibson said:
Don't install TWRP. I was rooted (w/ stock recovery) with 23A, and the OTA update worked fine (still rooted).
Click to expand...
Click to collapse
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Anthony-m said:
TWRP is already installed..
Can I uninstall TWRP, keep root , do the update and then reinstall TWRP? If so how? Is there any other way around this issue, any way of not having the tablet continue to ask me to upgrade? Thanks BTW...
Click to expand...
Click to collapse
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
DeanGibson said:
Yes, you can do that, but I don't know the steps. Others here do.
Why do you want TWRP? I thought the usual reason was to install custom ROMs (in which case you won't receive any OTA updates). If you just want to root, it's an unnecessary complication (as you have discovered).
Click to expand...
Click to collapse
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Anthony-m said:
Thanks Dean, and yes I do agree with you about it being a complication. I was always under the assumption if I rooted a phone that I needed to also use some sort of recovery god forbid I had an issue with the phone not booting up or something so I could possibly fix the issue, make a backup/install a backup etc. Maybe I will ****can it if someone will tell me how to do so without losing my data or root.
Click to expand...
Click to collapse
FYI I just froze the update using Titanium backup pro and my problem is solved for now..
Just a question that jumped out of curiosity.
Why does the Zenfone bootloop on applying OTA on rooted firmware??
The 2.18 OTA zip has patch files to system apps. I dont see why it should cause bootloop on a rooted device which has all the system apps intact?
And on unrooting, OTA works perfectly. What is the reason?? How does the OTA zip understand that the device has been rooted even if no system apps have been tampered with?
Anyone with knowledge on this please post your reply.
Thank you in advance.
black.pearl said:
Just a question that jumped out of curiosity.
Why does the Zenfone bootloop on applying OTA on rooted firmware??
The 2.18 OTA zip has patch files to system apps. I dont see why it should cause bootloop on a rooted device which has all the system apps intact?
And on unrooting, OTA works perfectly. What is the reason?? How does the OTA zip understand that the device has been rooted even if no system apps have been tampered with?
Anyone with knowledge on this please post your reply.
Thank you in advance.
Click to expand...
Click to collapse
Its probably an OEM root check at runtime, if runtime detects an SU binary the zygote runtime will halt, this could be confirmed with a logcat while booting, its a guess here but im pretty sure thats whats going on.
does this always happen? i mean, is there a way to root the device without getting a boot loop after applying OTA?
SquallDNA said:
does this always happen? i mean, is there a way to root the device without getting a boot loop after applying OTA?
Click to expand...
Click to collapse
I think the other question to be asked is why a fresh install of the pre-rooted firmware allows an OTA to go through with no problems...
I have installed a pre-rooted image on 2 phones now and then done the OTA update.
It seems to check for something altering the system AFTER the firmware is flashed as a pre-rooted firmware does in fact have supersu already installed and will allow the OTA update to work (or at least that has been my experience with 2.18.40.X and 2.19.40.18.).
ultramag69 said:
I think the other question to be asked is why a fresh install of the pre-rooted firmware allows an OTA to go through with no problems...
I have installed a pre-rooted image on 2 phones now and then done the OTA update.
It seems to check for something altering the system AFTER the firmware is flashed as a pre-rooted firmware does in fact have supersu already installed and will allow the OTA update to work (or at least that has been my experience with 2.18.40.X and 2.19.40.18.).
Click to expand...
Click to collapse
what happened after OTA update? did it went boot looping?
asus obviously doesn't want thier devices rooted.
Booted fine, no bootloop or other problems and updated to latest firmware. Either I lucked out and got 2 aberrant Zenfone 2's that update fine with the pre-rooted image or there is some other factor involved.
Just a quick note, I re-flashed a pre-rooted image over the old system. It was the same firmware version, 19.40.18 over 19.40.18 so it essentially just reset to how the pre-rooted image was before supersu was updated. OTA worked fine like this.
ultramag69 said:
Booted fine, no bootloop or other problems and updated to latest firmware. Either I lucked out and got 2 aberrant Zenfone 2's that update fine with the pre-rooted image or there is some other factor involved.
Just a quick note, I re-flashed a pre-rooted image over the old system. It was the same firmware version, 19.40.18 over 19.40.18 so it essentially just reset to how the pre-rooted image was before supersu was updated. OTA worked fine like this.
Click to expand...
Click to collapse
that's awesome. which variant of zf2 do you have? i'm using 551 2gb 1.8ghhz variant under 2.19.40.22.. if you dont mind, can i have the exact same root tutorial you followed?
SquallDNA said:
that's awesome. which variant of zf2 do you have? i'm using 551 2gb 1.8ghhz variant under 2.19.40.22.. if you dont mind, can i have the exact same root tutorial you followed?
Click to expand...
Click to collapse
I have a 4gb 64gb 2.3ghz and a 4gb 32gb 1.8ghz zenfone 2. Both work fine. As I said though I have unlocked the bootloader and rooted prior to doing it this way. It may be the bootloader goes through a check.
Way I rooted was to install the pre-rooted image a long time ago but when I have OTA'd I used the temporary CWM to reroot with latest supersu.
Once I found we could put TWRP on the Zenfone 2 I unlocked the bootloader and then installed TWRP 2.8.7.0(?) though I believe reflashing the pre-rooted image back on may have removed this.
I was using this for a while when the new OTA came out. As I had updated SuperSU I reflashed the pre-root image for the firmware installed (I believe it was 2.19.40.18) then installed the OTA from settings.
When the OTA came out for 2.19.40.22 I reflashed the pre-rooted image on again (2.19.40.20 this time) and then ran the OTA update from the settings again. No boot-loops or anything else wrong... Been running fine since on both though I got the flashing bug and flashed the custom rom SuperZen on my 1.8ghz 32gb Zenfone 2. Again no problems but I haven't tried reverting that back yet...
ultramag69 said:
I have a 4gb 64gb 2.3ghz and a 4gb 32gb 1.8ghz zenfone 2. Both work fine. As I said though I have unlocked the bootloader and rooted prior to doing it this way. It may be the bootloader goes through a check.
Way I rooted was to install the pre-rooted image a long time ago but when I have OTA'd I used the temporary CWM to reroot with latest supersu.
Once I found we could put TWRP on the Zenfone 2 I unlocked the bootloader and then installed TWRP 2.8.7.0(?) though I believe reflashing the pre-rooted image back on may have removed this.
I was using this for a while when the new OTA came out. As I had updated SuperSU I reflashed the pre-root image for the firmware installed (I believe it was 2.19.40.18) then installed the OTA from settings.
When the OTA came out for 2.19.40.22 I reflashed the pre-rooted image on again (2.19.40.20 this time) and then ran the OTA update from the settings again. No boot-loops or anything else wrong... Been running fine since on both though I got the flashing bug and flashed the custom rom SuperZen on my 1.8ghz 32gb Zenfone 2. Again no problems but I haven't tried reverting that back yet...
Click to expand...
Click to collapse
thanks man. i found this, http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596, and i believe you used the 1st method of rooting. i prefer using the 3rd method.
SquallDNA said:
thanks man. i found this, http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596, and i believe you used the 1st method of rooting. i prefer using the 3rd method.
Click to expand...
Click to collapse
I used both 1 and 3... Flashed pre-rooted image then downloaded OTA using system settings and flashed with system update. Didn't download the OTA and copy tophone as system update did this for me...
SquallDNA said:
what happened after OTA update? did it went boot looping?
asus obviously doesn't want their devices rooted.
Click to expand...
Click to collapse
I do not think so.
Why would Asus bother with what YOU do with YOUR phone.
Bootloops are caused if you delete something from the /system directory or modify something on which the system depends upon (e.g. v4a, busybox, etc)
As long as you do not touch any system stuff, Asus wouldn't bother. If they wanted their phones to strictly remain untouched, they wouldn't have released bootloader unlocking tools for the previous gen devices.
[email protected] said:
I do not think so.
Why would Asus bother with what YOU do with YOUR phone.
Bootloops are caused if you delete something from the /system directory or modify something on which the system depends upon (e.g. v4a, busybox, etc)
As long as you do not touch any system stuff, Asus wouldn't bother. If they wanted their phones to strictly remain untouched, they wouldn't have released bootloader unlocking tools for the previous gen devices.
Click to expand...
Click to collapse
They haven't released bootloader unlock tool for the Zenfone 2. By your logic they do care until they release that, then it should no longer matter...
Hi, I was fed up with my stock, slow, German 855 and wanted to root and flash CloudyG3 2.3.
First I tried Purple Drake lite but it aborted after the phone rebooted. Then I tried LG One Click Root 1.3 and this seemed to work.
Next on my list was flashing a recovery. I followed this: [RECOVERY][TWRP][D855] TeamWin Recovery with modem support and flashed the .img via flashify.
Now the phone does not boot. It says "Secure bootig error. Cause: Boot certification verify." after that the screen turns off and the notification LED flashes red and blue. I tried factory reset but I end up at the same error message.
I started panic googling and was about to try this: http://forum.xda-developers.com/showpost.php?p=59970974&postcount=6 but because OP had a slightly different problem and I don't want to make it any worst, I thought I ask for verification first.
What did I do wrong? I stuck to tutorials from the FAQ (apart from one click root which seemed to work). Am I supposed to flash stock firmware via ADP download mode now?
Thanks!
CutterSlade001 said:
Hi, I was fed up with my stock, slow, German 855 and wanted to root and flash CloudyG3 2.3.
First I tried Purple Drake lite but it aborted after the phone rebooted. Then I tried LG One Click Root 1.3 and this seemed to work.
Next on my list was flashing a recovery. I followed this: [RECOVERY][TWRP][D855] TeamWin Recovery with modem support and flashed the .img via flashify.
Now the phone does not boot. It says "Secure bootig error. Cause: Boot certification verify." after that the screen turns off and the notification LED flashes red and blue. I tried factory reset but I end up at the same error message.
I started panic googling and was about to try this: http://forum.xda-developers.com/showpost.php?p=59970974&postcount=6 but because OP had a slightly different problem and I don't want to make it any worst, I thought I ask for verification first.
What did I do wrong? I stuck to tutorials from the FAQ (apart from one click root which seemed to work). Am I supposed to flash stock firmware via ADP download mode now?
Thanks!
Click to expand...
Click to collapse
@CutterSlade001, seems like you are already rooted. Did you try pulling out the battery and then powering on again? Once you are sure you are rooted, you can try using various methods available on XDA or try searching AutoRec on the play store for installing twrp. It's meant for rooted lollipop devices. Hope this helps.
Sent from my LG-D855 using Tapatalk
ravi.vydianathan said:
@CutterSlade001, seems like you are already rooted. Did you try pulling out the battery and then powering on again? Once you are sure you are rooted, you can try using various methods available on XDA or try searching AutoRec on the play store for installing twrp. It's meant for rooted lollipop devices. Hope this helps.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Yes pulling the battery does nothing but to give me the ability to look at the error again.
I get that i am supposed to install twrp. But how to safely make the phone operational again?
Or can I only use ADB at hte moment? Yes rooting worked.
Thanks for your hint at AutoRec I will try that once the phone works again.
CutterSlade001 said:
Yes pulling the battery does nothing but to give me the ability to look at the error again.
I get that i am supposed to install twrp. But how to safely make the phone operational again?
Or can I only use ADB at hte moment? Yes rooting worked.
Thanks for your hint at AutoRec I will try that once the phone works again.
Click to expand...
Click to collapse
I presume you can get into download mode? If you can use flashtool to go back to stock then root your device then use Autorec.
Download mode seems to work. Slowly downloading factory image now...
So rooting via one click was not the problem? Not using Autorec was?
I will follow this then after factory flash and reset and root via oneclick?
Thanks a lot for your help! I got it working again.
But now I am back to KitKat and Autorec requires Lollipop. OTA says there is no update and I got all sorts of junk on the phone from other carriers.
Is there a factory Lollipop image I missed?
CutterSlade001 said:
Thanks a lot for your help! I got it working again.
But now I am back to KitKat and Autorec requires Lollipop. OTA says there is no update and I got all sorts of junk on the phone from other carriers.
Is there a factory Lollipop image I missed?
Click to expand...
Click to collapse
@CutterSlade001 seems like you got hold of a kk firmware file instead of lp. You should be able to the appropriate lollipop version for your phone model. After that, just flash once again and then use one click root plus recovery options available in XDA.
Sent from my LG-D855 using Tapatalk
ravi.vydianathan said:
@CutterSlade001 seems like you got hold of a kk firmware file instead of lp. You should be able to the appropriate lollipop version for your phone model. After that, just flash once again and then use one click root plus recovery options available in XDA.
Click to expand...
Click to collapse
Thanks for all your Help! I did that and it worked! I only found Lollipop .kdz files so I used the 2014 flash tool. After that, everything worked as expected. I am now running CloudyG3 2.3 and am Happy so far. But I did a clean install with only the bare minimum of apps for now and the stock firmware ran smooth for a few weeks also. Always buy the version with 3 GB RAM instead of the one with 2 GB RAM and a "free" LG G Watch.
CutterSlade001 said:
Thanks for all your Help! I did that and it worked! I only found Lollipop .kdz files so I used the 2014 flash tool. After that, everything worked as expected. I am now running CloudyG3 2.3 and am Happy so far. But I did a clean install with only the bare minimum of apps for now and the stock firmware ran smooth for a few weeks also. Always buy the version with 3 GB RAM instead of the one with 2 GB RAM and a "free" LG G Watch.
Click to expand...
Click to collapse
@CutterSlade001 glad that it worked for you ?
Sent from my LG-D855 using Tapatalk
cutterslader ..... please tell me how could u solve the problem. I have the same problem and i couldnt get to download mod because the screen is black and not functional. please help me, I am losing my phone. it is lg g3 d858hk
khalfan1984 said:
cutterslader ..... please tell me how could u solve the problem. I have the same problem and i couldnt get to download mod because the screen is black and not functional. please help me, I am losing my phone. it is lg g3 d858hk
Click to expand...
Click to collapse
Please let me know if you could fix this, I have the same problem