No Permissions In ADB Push Mode? - ZenFone 2 Q&A, Help & Troubleshooting

So I am very new to this phone (obviously) and I had it rooted ASAP, like an idiot. Then I proceeded, when I saw an update, to un-root, then take the update. Error. Ok, well then I look around and see that you should be able to sideload the OTA, but when I try to sideload through the stock recovery it tells me I do not have proper permissions from the device. I have looked around and not seen anything about this, possibly I am blind @[email protected] , I would like to get the update so I can unlock the boot loader. Does anybody know what to do in this situation or ran into the same problem and fixed it? Thanks in advance.

xploitnt said:
So I am very new to this phone (obviously) and I had it rooted ASAP, like an idiot. Then I proceeded, when I saw an update, to un-root, then take the update. Error. Ok, well then I look around and see that you should be able to sideload the OTA, but when I try to sideload through the stock recovery it tells me I do not have proper permissions from the device. I have looked around and not seen anything about this, possibly I am blind @[email protected] , I would like to get the update so I can unlock the boot loader. Does anybody know what to do in this situation or ran into the same problem and fixed it? Thanks in advance.
Click to expand...
Click to collapse
Use this guide, it worked for me from a rooted firmware to the latest 2.19 firmware:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835

cmendonc2 said:
Use this guide, it worked for me from a rooted firmware to the latest 2.19 firmware:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Click to expand...
Click to collapse
Thank you fine sir I'll give it a shot after I fix this stupid S6 Edge I just bricked LOL :silly:

cmendonc2 said:
Use this guide, it worked for me from a rooted firmware to the latest 2.19 firmware:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Click to expand...
Click to collapse
Thank you for the push in the right direction. I am up, running, updated, and TWRP'd

Related

[Q] Please help me get a usable phone again

I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
tn6 said:
I decided to try cyanogenmod on my SGH-I747 but have had so many issues I would be happy at this point if I could just get a working phone again.
I started with a 4.3 OTA-updated phone. I rooted the phone, then tried to install the latest 10.2 ROM. I also tried 10.1. I used CWM: I would have preferred the latest version but the best I could find that was not an .img file (I used Odin) was in the 5.x range. In both cases I hit what I believe is a bootloader error ("assert failed: ... Status 7"). At this point the phone is wiped with no recourse. I attempted to install the stock boot image for the I747, but after doing so the phone will no longer boot.
EDIT: I am able to get to downloading mode. I am afraid to use it to install stock firmware b/c of a post I found here claiming that downgrading from 4.3 OTA (e.g., to 4.1) will brick the phone.
Click to expand...
Click to collapse
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Worked, I think
MrHaPpY66 said:
i actually had the same problem earlier today. what i did was use odin to install clockworkmod recovery. after it reboots, hold VOLUME UP and HOME at the same time. if you have a micro sd handy, download any of the two updates here http://forum.xda-developers.com/showthread.php?t=2498233 place them on you sd card and in recovery format cache and factory reset/data. then highlight "install zip from sd card" or something that sounds relevant. select the zip you placed on your sd card earlier and there.
Click to expand...
Click to collapse
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
tn6 said:
Thank you. The phone now boots to a white screen with an AT&T symbol. How can I install either a stock or custom ROM without ruining everything again?
Click to expand...
Click to collapse
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
No luck
MrHaPpY66 said:
i think this should be a help http://forum.xda-developers.com/showthread.php?t=2539313
Click to expand...
Click to collapse
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
tn6 said:
That appears to be the standard tutorial for rooting/flashing. I did it anyway, even though didn't the file you had me install before already root the phone? In any event, I ran CF-root and then I attempted to install CM 10.2 and it failed: "failed to verify whole-file signature." I believe that was the first error I hit in the beginning of this exercise. Additionally, now I get an error on the welcome screen that says "Unfortunately, SuperSU has stopped."
Click to expand...
Click to collapse
for the supersu, you probably need to go update it on the market or disable KNOX
assert failed... getprop("ro.bootloader")
MrHaPpY66 said:
for the supersu, you probably need to go update it on the market or disable KNOX
Click to expand...
Click to collapse
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
tn6 said:
Thanks for the suggestion. I went back to the no-KNOX file you pointed out earlier. I assume that is the same type of file as the CF-Root so I assume I don't need to install CF-root anymore after installing the no-KNOX file. So now I follow the tutorial from your second response minus the root step. I no longer get the SuperSU error. However, I still can't load a ROM. I get the same "assert failed... getprop("ro.bootloader... Status 7" that I mentioned in my first post. When I googled this in the first round, I saw several posts saying it means I had a bad bootloader. That is when I tried to flash the stock bootloader, which nearly hardbricked the phone. Do the two files you initially posted include a bootloader file?
Click to expand...
Click to collapse
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
MrHaPpY66 said:
i think they contained the mj2 bootloader and modem. hmm i've been doing a little snooping around and i found this. http://forum.xda-developers.com/showthread.php?t=2540998 the thing is i still don't understand how to go from leaked (mj2) to the official release (mjb) maybe updating to this will help
Click to expand...
Click to collapse
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
tn6 said:
I'm worried about switching bootloaders. This post seems to indicate that doing so after I installed 4.3 OTA will brick the phone. Does anyone know if that is true?
http://forum.xda-developers.com/showthread.php?t=2321310
Click to expand...
Click to collapse
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
MrHaPpY66 said:
ohh ho ho it's true alright. the new 4.3 bootloader, i'm guessing it is mjb, doesn't allow any downgrades. Downgrades of any kind will absolutely give you a nice, good brick. anyways do you understand how to go from 4.3 leaked to 4.3 official?
Click to expand...
Click to collapse
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
resolved
tn6 said:
No idea. I went ahead and tried to install the I747UCDLK3_aio.tar.md5, which I hoped was a 4.3 bootloader (don't know how you are supposed to tell). The error I got was this was another failure--this time saying the package was for d2att and this is a d2spr. My phone is definitely not a sprint phone. Some posts say I have to update the build.prop file, but I don't know how I can do that before a ROM is even installed.
Click to expand...
Click to collapse
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
tn6 said:
I realized that many of the errors I was getting seemed to be tied to cyanogenmod or stock. So I downloaded Hyperdrive and it installed with zero hiccups or errors. I have a working phone again.
Thank you for your helpful insights.
Click to expand...
Click to collapse
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
MrHaPpY66 said:
you're welcome and i glad i was a help to you. anyways where'd you get hyperdrive? i've been trying to get my phone back to official stock and off the leaked one.
Click to expand...
Click to collapse
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
tn6 said:
I downloaded hyperdrive from the official spot: http://forum.xda-developers.com/showthread.php?t=2106830. I wouldn't have minded going back to stock, but clearly that was not going to happen any time soon.
Click to expand...
Click to collapse
so how's the rom so far? probably going to get it myself.
MrHaPpY66 said:
so how's the rom so far? probably going to get it myself.
Click to expand...
Click to collapse
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
tn6 said:
Zero issues. Worked great all day with no problems. Plus I am now able to tether and use the mobile hotspot, features that I couldn't get to work on the stock rom even with foxfi or similar apps.
Click to expand...
Click to collapse
so i see it's a lot better than stock. i'll install it as soon as i can and thanks for the link to the rom

[Q] lg g gpad ota update (lg fw)

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

[Q] Where to find SU binaries for P600?

Hi All!
I'm stuck in the state where I cannot complete root after update. I have no idea why this happened. I used autoroot first time on a stock. Everything worked like a charm. However In order to install update I have installed xposed and few modules to hide reset flag. After that I was able to update stock. Problem is that after this running autoroot and installing stock recover does not help. I not getting root despite the fact that I see instalation successfully completed and other people report success.
So question is - were to get SU binaries for P600 and where to put them? I'm able to reboot in TWRP using ADB if this matter.
I would also glad to reflush latest stock, but I do not know how to do it, because KIES says i'm up to date.
Any help will be greatly appreciated.
CNemo7539 said:
Hi All!
I'm stuck in the state where I cannot complete root after update. I have no idea why this happened. I used autoroot first time on a stock. Everything worked like a charm. However In order to install update I have installed xposed and few modules to hide reset flag. After that I was able to update stock. Problem is that after this running autoroot and installing stock recover does not help. I not getting root despite the fact that I see instalation successfully completed and other people report success.
So question is - were to get SU binaries for P600 and where to put them? I'm able to reboot in TWRP using ADB if this matter.
I would also glad to reflush latest stock, but I do not know how to do it, because KIES says i'm up to date.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
Have you tried updating Supersu from play store
lsherif said:
Have you tried updating Supersu from play store
Click to expand...
Click to collapse
Yes, I did. It says that binaries are not found.
CNemo7539 said:
Yes, I did. It says that binaries are not found.
Click to expand...
Click to collapse
Have you tried flashing SU zip? You should be good to go after flashing :good:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
22sl22 said:
Have you tried flashing SU zip? You should be good to go after flashing :good:
http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
Click to expand...
Click to collapse
Thank you! Now I'm rooted again!

[Q] [IMPORTANT] Is there any way I can root htc one m8 Lolipop 5.0?

Someone if you know and tested it, can I root my htc one m8 device having the new firmware updated 5.0.1 lolipop??
Please anwser and if there is a way please send a link
THANKS A LOTTT!!
It's exactly the same as before.
Look for how do I root here,
http://forum.xda-developers.com/showthread.php?t=2711073
You unlock bootloader. Flash a custom recovery... I suggest twrp. It will ask you when you exit if you want to root. Say yes.
Boot into android, install supersu if it or superuser aren't there already. (from play store)
Or just flash recovery . Install a rom , likely rooted already.
?
Darth said:
It's exactly the same as before.
Look for how do I root here,
http://forum.xda-developers.com/showthread.php?t=2711073
You unlock bootloader. Flash a custom recovery... I suggest twrp. It will ask you when you exit if you want to root. Say yes.
Boot into android, install supersu if it or superuser aren't there already. (from play store)
Or just flash recovery . Install a room, likely rooted already.
Click to expand...
Click to collapse
thanks for that but when I did it in my phone it says su binary out of date! what can I do now?
Can you explain everything you did, beginning to end. And exactly when/where you get that message?
I had already TWRP in my phone so I download your files. Opened the recovery and I did from there (install). When it finished rebooted the device and after that when i did a root check it said root access not properly install or sometihing
Koukosftw said:
I had already TWRP in my phone so I download your files. Opened the recovery and I did from there (install). When it finished rebooted the device and after that when i did a root check it said root access not properly install or sometihing
Click to expand...
Click to collapse
Open the SuperSU app, and it will prompt you to install the binaries. Select yes, of course.
i did that too nothing happened :/
xunholyx said:
Open the SuperSU app, and it will prompt you to install the binaries. Select yes, of course.
Click to expand...
Click to collapse
This ^^^^
If it asks to update with a "normal" and "twrp/cwm" option... Try normal first. The other option if that doesn't work.
Darth said:
This ^^^^
If it asks to update with a "normal" and "twrp/cwm" option... Try normal first. The other option if that doesn't work.
Click to expand...
Click to collapse
I tried the normal it didnt work, how I do the second, I pressed it but nothing happened!
I don't think you have twrp installed anymore, or not properly. You've flashed it with fastboot, since updating to lollipop? How did you update to lollipop?
Normal, I never had root before. Upgraded my phone to 5.0 and then i tried to root it
Rooted fine here with normal method. Just had to update super su.
OK, can you please walk us through exactly what steps to Root you took. From the beginning. And we'll see what happened.
?
i havent been able to find the option to disable fast boot so i havent even tried yet but if anyone has let me know
chinkyarmour said:
i havent been able to find the option to disable fast boot so i havent even tried yet but if anyone has let me know
Click to expand...
Click to collapse
Settings > Power > Fast boot
xunholyx said:
Settings > Power > Fast boot
Click to expand...
Click to collapse
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
chinkyarmour said:
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
Click to expand...
Click to collapse
They must have taken the option out. It didn't boot any faster for me anyways. Not since 4.4.2
chinkyarmour said:
its not in lollipop
but i did it just now and rooted anyway
https://www.youtube.com/watch?v=WuHFcGvUjwA
followed this method again no problem
Click to expand...
Click to collapse
SO GUYS, ITS ME THAT I CREATED THIS THREAD! PROBLEM SOLVED. I ALREADY HAD TWRP AND DOWNLOADED THE Update-supersu file from the above youtube video (links) and I did it with recovery mode. I DONT KNOW BUT THE PREVIOUS supersu I installed couldnt update the su binary. This one did it. PROBLEM SOLVED AND I ROOTED MY 5.0.1 LOLIPOP DEVICE.
THANKS GUYS FOR EVERYTHING REALLY HELPFUL!!!

What Steps Do I Take To Update From 2.19.40.20?

So I've stayed at 2.19.40.20 because I wanted to wait to see if a better way to unlock the bootloader would be found, but I've given up and unlocked my bootloader (the unoffical way).
I want to get up to speed and update to the latest OTA.
Can I just flash the latest one or do I need to download every one til the newest update and sideload them individually?
If I have to do each one can I just load them one after the other, or do I need to reboot the phone and let it fully load to the OS for every update?
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
DiGecko said:
I did side load the latest one when I was coming from the 18 something that came with my phone. Loading the full 1.1gig firmware did the trick.
Click to expand...
Click to collapse
Azdinflash said:
So just for clarification, to take me from 2.19.40.20 to 2.20.40.139 I should just flash the latest Stock ROM from the ASUS site?
Click to expand...
Click to collapse
Yes that should do it.
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
The_wolf88 said:
Yes that should do it.
Click to expand...
Click to collapse
Azdinflash said:
I was seriously dreading having to update, but this shows that my worries were unfounded, thanks!
I don't need to unroot as I'm flashing the whole rom, right?
Click to expand...
Click to collapse
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
DiGecko said:
You need to unroot and make sure you are sideloading the whole 1.1 gig one.
Click to expand...
Click to collapse
Does unrooting include removing Xposed?
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Wait, if I flash the 1.1 gig stock ROM, do I lose everything in the internal memory?
DiGecko said:
Yes, and don't try to install it after you get to 139 firmware, as far as I know it still causes bootloop.
Click to expand...
Click to collapse
I did a little digging, and it seems that the bootloop was fixed a few days ago:
http://forum.xda-developers.com/zenfone2/general/guide-to-install-xposed-installer-t3116476/page26
J M L said:
There's a new Xposed out, v78, which claims to fix a bootloop on 5.0 roms due to a security fix. I haven't tried it yet because I'm running a backup. Here is the thread and changelog.
We want the sdk21-x86 version.
Installed with no problem in TWRP with the flash able zip. Took a few minutes to boot, but seems to be working.
Click to expand...
Click to collapse
Good to know. No, you would not loose anything, at least I did not. Everything migrated over without any issues.
So I've gotten through sideloading the current version with no hiccups. Booted into system fine, it's the right version in the About section, and my internal memory came through intact.
I've flashed TWRP, and booted into it to install SuperSU when I got this message: "TWRP may have detected an unmodified system partition"
It explains that I can keep it as read only and make it easier to take official updates, but then TWRP will not be able to stop the stock ROM from replacing it and will not offer to root my device.
Should I keep it "Read Only" or should I allow the modification?

Categories

Resources