Related
Hi guys,
I know how rooting and flashing works but I've been using HTC devices since the nexus one so there are some differences I just want to make sure of. I got my 6P yesterday, I unlocked the bootloader and flashed TWRP. I wanted to gain root but Im not sure about flashing the modified boot img and the vendor thing.
My build was K but I got an OTA before unlocking the bootloader which updated to L. Anyway I don't know why I just formatted every thing in TWRP instead of the factory reset and I lost the OS X_X I tried to restore my nandroid with no luck. Anyway I got the factory img (MDB08L) from google dev and flashed used 'flash-all.bat' in the bootloader, the phone is running fine right now but I would like to update to the latest firmware 6.0.1+root since im not getting any OTA.
I would like to install CleanCore(6.0.1), the guide is
-> Flash Bootloader & Radio (as needed)
-> Flash CleanCore
-> Flash Modified Boot (named angler-xxxxxx-boot.zip)
-> Flash SuperSU or SuperSU Beta
-> Flash latest vendor.img (ROM & Vendor builds need to match!)
1. Should I use MMB29M factory img and flash 'flash-all.bat' like I did with the L build for the first step? then I flash new recovery?
-Flashing the rom through the recovery
2. so after I flash the rom I boot into the bootloader and flash the modified boot img with fastboot flash boot boot.img right?
3. then I go back to recovery and flash SU which I should download before.
4. vendor img is flashed in recovery too or fastboot?
Sorry for the hassle I just want to make sure.
One more thing, in this guide http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 at step 9, OP flashes the factroy img files separately (bootloader,radio,etc), is there a problem with using flashall.bat?
Thanks in advance and sorry for my noobish questions.
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Enddo said:
If you want to keep your data while doing this process, then yes, using the flash-all.bat is a problem. However, if you are fine with reverting back to stock(where you have to activate Android and reinstall all of your apps) then the flash-all.bat file is just fine.
That guide in the thread you linked walks you through how to update without losing data. After doing all of that, you'll just need to install TWRP and SuperSU again(do the latest systemless supersu though)
Click to expand...
Click to collapse
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
mr.dj26 said:
Thanks for the help.
I have rooted my stock rom and gained root. I also installed exposed so i'll be fine without a custom rom for some time. There has been a report that some cameras aren't working on 6.0.1 with root so I'll wait for a while.
Thanks again
Click to expand...
Click to collapse
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Enddo said:
I'm pretty sure those reports are because they used the SuperSU root method that didn't auto patch the boot image(which is the version(or two versions) behind the current version of SuperSU). This is happening because people are updating to 6.0.1, but the patched SuperSU boot image is for 6.0 and the 6.0 boot image conflicts with 6.0.1
As long as you use the latest version of SuperSU then you won't have any trouble with the camera
Click to expand...
Click to collapse
Thanks for the info
Hi all,
I am sure that I am missing a step here, but I am stuck. Please keep in mind, that I am slightly out of my element, but I can follow directions real well.
My S4 was on 4.4.4 and I finally got around to getting CM13 for it and that installs just fine with no errors. However; GAPPS will not install and I am not able to root the phone.
The version of TWRP that I have installed is slightly dated [2.5.0.2], but since I am flashed to 6.0.1 and unable to succesfully root I cannot apply the latest img for TWRP.
I have wiped Dalvik Cache / System / Data & Cache
via TWRP > Install and the selected cm-13.0-20161114-NIGHTLY-jflteatt.zip
The install has no errors, but upon reboot, I am prompted that "Root Permissions appear to be lost" and I SWIPE To Fix Root"
With a fresh install of CM13, I have enabled the developers options [tapping on build 7 times] , via these options I have enabled root access for Apps and ADB and lastly I have enabled USB Debugging.
At this point, I am not sure what to do to ensure that the phone is rooted. I have tried Kingo Root, Towel Root and they all fail.
This is why I suspect that I am doing something wrong and out of sequence and would appreciate some help.
The model # is the sgh-i337 from AT&T?
audit13 said:
The model # is the sgh-i337 from AT&T?
Click to expand...
Click to collapse
Yes, this is the AT&T version and it turns out that I was doing everything correctly; however since the version of TWRP was an older version. It would flashing the OS alright, but the GAPPS was having problems.
After flashing BETA-SuperSU-v2.67-20160121175247.zip [still not seeing a SU or App in the Application drawer.]
I was able to install, run Flashify and was able to update TWRP to the latest .img file.
Then I did:
Wipe, data, cache, dalvik, system
Install ROM
Install gapps (Pico version)
Rebooted
I then had a working phone and GAPPS was working.
gamerscircle said:
Yes, this is the AT&T version and it turns out that I was doing everything correctly; however since the version of TWRP was an older version. It would flashing the OS alright, but the GAPPS was having problems.
After flashing BETA-SuperSU-v2.67-20160121175247.zip [still not seeing a SU or App in the Application drawer.]
I was able to install, run Flashify and was able to update TWRP to the latest .img file.
Then I did:
Wipe, data, cache, dalvik, system
Install ROM
Install gapps (Pico version)
Rebooted
I then had a working phone and GAPPS was working.
Click to expand...
Click to collapse
Well you might have old bootloader (ADB/MDL) since you can install the TWRP as a custom recovery. Majority of AT&T S$ i-337 here has a newer bootloader and we could not install the custom recovery like TWRP since the bootloader is locked.
I was thinking of suggesting to use the motor-chopper or loki-doki like we use to do three years ago but it seems that you solved your problems.
sway8966 said:
Well you might have old bootloader (ADB/MDL) since you can install the TWRP as a custom recovery. Majority of AT&T S$ i-337 here has a newer bootloader and we could not install the custom recovery like TWRP since the bootloader is locked.
I was thinking of suggesting to use the motor-chopper or loki-doki like we use to do three years ago but it seems that you solved your problems.
Click to expand...
Click to collapse
I do vaguely remembering using the motor-chopper and odin when I did my S4 originally, but the above process worked for me, so perhaps if anything has a similar problem, they might be able to do what I did and it might help.
Hello,
I tried to install the new Nougat rom for jiayu S3, but it was unsuccessful. Phone got soft bricked, but I recovered it with a twrp backup.
My OS is android 4.4.4, and TRWP is 2.8. After installing the new rom , an installation error appeared and phone did not work.
I wonder it it's due to twrp 2.8, but I can't install twrp 3 (S3_h560_TWRP_3.0.2-0). There was an installation error with flashify...
The question is: can I install 7.0 from 4.4? Is it an Android problem, a TWRP issue, or just my clumsiness?
Thank you!
achilipu05 said:
Hello,
I tried to install the new Nougat rom for jiayu S3, but it was unsuccessful. Phone got soft bricked, but I recovered it with a twrp backup.
My OS is android 4.4.4, and TRWP is 2.8. After installing the new rom , an installation error appeared and phone did not work.
I wonder it it's due to twrp 2.8, but I can't install twrp 3 (S3_h560_TWRP_3.0.2-0). There was an installation error with flashify...
The question is: can I install 7.0 from 4.4? Is it an Android problem, a TWRP issue, or just my clumsiness?
Thank you!
Click to expand...
Click to collapse
in short:
To go from 4.4.4 to Nougat you need to go via LP RC5 via flashify using firmware upgrade.
This is because the partition layout is different from KK to LP onwards.
Then you can flash Nougat using TWRP (which will be version 3)
Thank you very much for your answer.
Please forgive me for my ignorance but, which LP ROM should I download? Can I install it via flashify, via TWRP 2.8, o flash?
Thank you again!
You can not use Flashify, you have to do it using Flashtools (with a PC) to go from KK to LP. Download LP 5.1.1 RC 5 from MAD.
fusant said:
You can not use Flashify, you have to do it using Flashtools (with a PC) to go from KK to LP. Download LP 5.1.1 RC 5 from MAD.
Click to expand...
Click to collapse
thanks to correct me, I thought Flashtools was meant
Well, I'm in trouble now... I installed successfully 5.1 in my S3, but when updated twrp 2.8 to 3.0, it did not work, so I can't install Nougat...
Now I have no twrp, and no root. How can I root to install twrp? I can't install superSU neither....
I'm sorry if it has been already answered but I can't find it.
Thanks a lot
I re-installed LP with Flash tools and everything worked right. (In twrp , it says 2.8 version, instead of 3.0, though).
Now I installed Nougat, and everything is ok.
Thank you for your excellent job!
Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?
Chattersking said:
Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?
Click to expand...
Click to collapse
You need the official recovery for update to work
Chattersking said:
Have a LeEco Pro 3 (US Version) running 5.8.19s official stock version, bootloader unlocked and official TWRP installed. But my system update fails everytime eventhough it shows there is new update 5.8.21s but phone boots to recovery in TWRP and asking for password. I have tried several times but its the same thing over and over again. Am I doing something wrong? Is there some different file that I must flash?
How can I stock update with rooted and TWRP?
Click to expand...
Click to collapse
You can update to 21s on the US version (727) from TWRP with a few modifications to the updater-script file (see the below post/thread):
https://forum.xda-developers.com/showpost.php?p=72815409&postcount=48
This will remove root but it keeps TWRP so you should be able to just reinstall root through TWRP.
Thank you. Will it keep my data and apps intact or will it erase them? I don't want to lose all my important data and setup.
Chattersking said:
Thank you. Will it keep my data and apps intact or will it erase them? I don't want to lose all my important data and setup.
Click to expand...
Click to collapse
I did a wipe before updating but it should work without wiping as the update zip file is the official OTA with only a modified updater-script. Do a backup from TWRP before you try it and if anything goes wrong you can revert to that backup.
Running into the same issue..did your script and that worked. Thanks for that.
Flash 19s using TWRP and needed a somewhat official way to get to 21s. Use the script of d/l the official 21s update and pushed the modified zip to sdcard to get flashed in TWRP. So hopefully this update, updated whatever it needs to update and maybe it will fix my other issue... why when I flash Lineage base ROMs they show my battery only at 50%
I followed the above instructions and replaced with the updated script however TWRP is giving me Error 7 and a quick google search is saying it is due to problem with updated script. How do you guys fix this?
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
bibile said:
Hi,
I've downgraded my phone ZE520KL couple months ago but I've forgotten that VOLTE is only available on 7.0...
I've recieved the OTA notification, downloaded the package on the phone, but when it reboots it is going on TWRP & then if I'm rebooting it doesn't continue the upgrade process.
What am I missing? (on my previous phones this wasn't so tricky...) Should I use the Install method directly from TWRP? If Yes on which zip? Is it possible to find the one that I've downloaded directly with my phone?
Click to expand...
Click to collapse
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
[email protected]@ said:
Same like me before. Have you rooted your phone yet? if yes then try this, it work for me though (Backup your phone is recommended)
1. Download busybox, supersu and no-verity file
2. Using flashfire app, choose flash zip or ota option
3. Add ota 'WW-ZE520Kl-.....'
4. Add firmware 'UL-ASUS-....'
5. Remove tickmark from 'Inject supersu'
And flash, it will reboot but do not boot to system. You must boot to twrp, flash no-verity file, busybox and supersu or your phone will not boot. Then reboot, done.
If this method is helpful, do reply to me
Btw, sorry for my poor english.
Click to expand...
Click to collapse
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
vEEGAZ said:
Thanks, works wonderfully! Flashfire flashed the new OTAs successfully but the phone didn't then boot (or it bootlooped). A quick Google search led me to your response and the dm-verity file fixed the boot!
I also didn't flash Busybox in case you needed to know and before flashing the OTAs I checked the "Automount" and "Mount systeam as R/W" in Flashfire otherwise the app would just get stuck in a blank screen.
EDIT: WiFI isn't working, tried already deleting the files in /data/misc/wifi, /persist and /data/misc/dhcp as suggested in various threads but still nothing. Anyone know how to fix it before I attempt to do a full backup and wipe?
Click to expand...
Click to collapse
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
[email protected]@ said:
Deleting files in /data/misc is not helped. Try this:
1. Check your selinux permissive or enforcing. If permissive, you should re-root your phone. Remember to flash busybox too or it will may some crash. Still not working follow step 2.
2. Re-flash the ROM using twrp. No data will be lost. Don't forget to re-root or it will not boot.
3. Try the lastest fw .68 or .75 though someone told that the .28 ota file had issue on wifi.
Click to expand...
Click to collapse
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
vEEGAZ said:
Reflashing through TWRP worked Although I did it after backing up all the apps and did a factory reset which didn't even fix the wi-fi problem. But then Flashfire is useless if TWRP is capable of flashing OTAs right?
Click to expand...
Click to collapse
Not really. Since OTA file can't flash through twrp. It really annoying for someone (like me ), so for the easiest way is just flash it using Flashfire, no need to use computer to flash stock recovery .
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP every time there's an update.
wang1chung said:
@vEEGAZ
yep, that's what I've been saying for months. I've never used anything but TWRP to flash my phone. I've downgraded, gone custom and back to stock many times.
@[email protected]@
I flash OTA's through TWRP everything there's an update.
Click to expand...
Click to collapse
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
edit your updater-script and it'll flash no problem.
[email protected]@ said:
When my phone still in 6.0.1, flashed OTA's throgh twrp it said 'not correct phone...' but after upgraded 7.0 it succeeded although i don't need it anymore.
Click to expand...
Click to collapse
Yeah that's what I encountered aswell back 2-3 years ago, I remember I couldn't flash any OTAs via TWRP but apparently now you can. That's why I also used Flashfire in the first place but after running out of all options for the wi-fi problem I decided to give TWRP a try et voilà, it worked
wang1chung said:
edit your updater-script and it'll flash no problem.
Click to expand...
Click to collapse
I've tried that and still not working.
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
wang1chung said:
@[email protected]@
I JUST did it....on 1711.75 now. There was no recovery partition update either so I didn't have to reflash TWRP after :good:
I did have a bootloop issue after but fixed that by flashing the no-verity file. I'm not sure if that's related to having magisk installed though.
Click to expand...
Click to collapse
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
[email protected]@ said:
1. After reflashing rom through twrp, i lost my twrp. Oh, but when i use Flasfire, it isn't lost.
2. Not sure but after flashing ROM your boot will change to normal so it may not related to magisk or supersu. Maybe it beacause of the twrp, i've tried reflash stock recovery once and i can updated it without flash no-verity file though i've installed magisk.
Click to expand...
Click to collapse
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
wang1chung said:
1. You will only lose TWRP if there is a recovery partition update in the stock firmware, yes, but that doesn't happen with every update. I think I read of a way to block it from updating the recovery partition but can't find the article right now. If flashfire works, use it, I just like TWRP for the other features like making and restoring nandroid backups.
2. I dirty flashed the update again through TWRP, verified the bootloop issue and then installed magisk (through TWRP) and it resolved the bootloop issue. No-verify file not required.
Click to expand...
Click to collapse
1.Ok, i got it.
2. The way using TWRP is keep the root ( root or not boot) and stock recovery is contrary ( can't root but will boot) or just flash custom kernel through twrp (not root required).
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
bibile said:
simple question :
- you are talking about OTA & Firmware...
I've downloaded again from asus website Version WW-V14.2020.1711.75 (I assume it is the latest firmware). Are you simply giving the example of an OTA that is released post the firmware version I have to install to have the 7.0 base?
Or is it anything that I'm missing...
From your explanations I should only :
- install flashfire
- flash the latest firmware
- boot into TWRP & flash no verity
- reboot the system
Right?
Click to expand...
Click to collapse
Yep, you can also flash the latest .zip via TWRP instead of using Flashfire, it's 100% working for me. Just REMEMBER to flash the no-verity file otherwise you'll end up in a bootloop.
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
ktl20 said:
I have newest oreo fw from asus website. Ive unlocked bootloader with official app. Now i want WTRP and root with magisk. I want to know how to flash updates to get all wroking?
1. Flash TWRP via fastboot?
2. Flash Magisk via TWRP?
3. When update will release i must flash whole fw from asus website with TWRP and then no-verity file to boot?
4. Or can i use flashfire app to flash fw from asus website and then no-verity zip?
What is the best solution to have updated system without use PC? Step by step guide will be great THX
Click to expand...
Click to collapse
iamROOTX said:
Im confuse.
Im using 1711.75 with magisk 15.3 and twrp 3.2.1.0
I have the full firmware of initial oreo
I just have to install flashfire
Flash the full firmware oreo that i have then rboot to twrp to flash no verify zip?
Click to expand...
Click to collapse
The safest and true way to flash any ota update without any issues by using stock recovery, don't use twrp or flashfire or any other apps.
follow the steps below:
1. When you are rooted and twrp installed, to getback to full stock boot and recovery without wiping data, flash the latest raw image available. For oreo the latest available one for ze520kl is WW_ZE520KL_15.0410.1712.31_M3.10.47.16_Phone-user.raw.zip.
2. Now flash the ota update available normally via stock recovery.
3. Flash oreo support twrp-3.2.1-0 and magisk zip.
4. Done.
I'm periodically upload the latest available ota update for ze520kl in the ze520kl ota update links thread.
Here is the latest one.