COS 13.1 ZNH2KAS1KN - New Update for OPO - ONE General

Cyanogen recently pused out COS13.1 for our beloved OPO.
Here is the link to OTA :-
http://builds.cyngn.com/incremental/bacon/cm-bacon-64003595ee-to-ced5430fc0-signed.zip 378 MB
"Upgrade your device to Cyanogen OS 13.1. Based on Android™ 6.0.1, Marshmallow, this update provides critical security fixes, improved stability/performance, product upgrades, and new mods for Cortana, OneNote, Microsoft Hyperlapse, Skype, and Twitter."
Changelog :-
Complete changelog currently unknown.
1st June Android Security patch level
Some MOD Addons.
Skype integration in dialer.Removal of NextDialer. Looks like stock dialer.
Hyperlapse mod in camera.
Update Instruction :-
Stock Unrooted Devices
To flash OTA you need stock unrooted phone.
Flash via stock recovery.
Rooted devices
1st unroot the device or flash system image from previous update then flash the OTA from recovery.

Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.

gigatroned said:
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
Click to expand...
Click to collapse
try flashing from stock recovery !

gauravsaini964 said:
try flashing from stock recovery !
Click to expand...
Click to collapse
Same for me lol

gigatroned said:
Hi, i've a problem flashing the OTA update...
TWRP locks the update giving me the error7
I've completly unrooted with SuperSU settings.
Thanks a lot.
Click to expand...
Click to collapse
flash the stock system with the correct recovery over, then flash update

stock recovery here. in the middle of the update it gives me an error.
All the page with red fonts, after a few second the message disappear and I have not been fast enough to read.
after reboot everything it is normal, but still COS 13.0

dam76 said:
stock recovery here. in the middle of the update it gives me an error.
All the page with red fonts, after a few second the message disappear and I have not been fast enough to read.
after reboot everything it is normal, but still COS 13.0
Click to expand...
Click to collapse
Try to install the previous update, and then with recovery stock reinstall the last update.

alijoregon said:
Try to install the previous update, and then with recovery stock reinstall the last update.
Click to expand...
Click to collapse
thanks, I tried installing previous update (same file cm-bacon-64003595ee-to-ced5430fc0-signed.zip that gave me Marshmallow in the first place)
but it gave me the same error again!
This time I took a screenshot with an old phone:
http://i.imgur.com/sW5NTyb.jpg

dam76 said:
thanks, I tried installing previous update (same file cm-bacon-64003595ee-to-ced5430fc0-signed.zip that gave me Marshmallow in the first place)
but it gave me the same error again!
This time I took a screenshot with an old phone:
http://i.imgur.com/sW5NTyb.jpg
Click to expand...
Click to collapse
Is your previous update the full OTA? The incremental is not valid. If you did root any time your system is modified. You must reinstall the full zip.

alijoregon said:
Is your previous update the full OTA? The incremental is not valid. If you did root any time your system is modified. You must reinstall the full zip.
Click to expand...
Click to collapse
yes: my system was rooted, so I had to perform a full wipe and install what I think to be the full zip (cm-bacon-64003595ee-to-ced5430fc0-signed.zip 377MB)
where can I download the full zip just to make sure?
does the full zip update wipe apps and data?
thanks in advance for the help

dam76 said:
yes: my system was rooted, so I had to perform a full wipe and install what I think to be the full zip (cm-bacon-64003595ee-to-ced5430fc0-signed.zip 377MB)
where can I download the full zip just to make sure
thanks in advance for the help
Click to expand...
Click to collapse
This time you needn't do full wipe. Only installing the full OTA via TWRP and then you must come back to the original recovery and install the incremental update. By this way you will have the last update.
All the links are in a post on this web, I don't remember the name of the post, but is easy to find.

alijoregon said:
This time you needn't do full wipe. Only installing the full OTA via TWRP and then you must come back to the original recovery and install the incremental update. By this way you will have the last update.
All the links are in a post on this web, I don't remember the name of the post, but is easy to find.
Click to expand...
Click to collapse
thanks! here I found the CM13.0 Signed flashable zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip 691 MB
rebooting
applying full zip via stock recovery
rebooting - everything apparently the same
applying update via stock recovery
rebooting... optimizing apps...
success! COS 13.1 up and running! (phone very warm though)
thank you very much for the support. (why messing with android must be so complicated?)

Hi, i also have an ERROR while installing the OTA.
1. I had updated to CM13 via OTA.
2. Since I had an issue with stuck lockscreen , installed TWRP and wiped cache ( Stock CM recovery was not helping). Phone worked great since then.
3. TWRP was not longer there, instead CM Recovery.
4. New update has arrived, but i get an "ERROR" word in the middle of screen while installing.
What can I do?
Thank you in advance for your response.

Seems to be fine. Minimal fixes but at least something...
---------- Post added at 11:29 AM ---------- Previous post was at 11:28 AM ----------
leokook said:
Hi, i also have an ERROR while installing the OTA.
1. I had updated to CM13 via OTA.
2. Since I had an issue with stuck lockscreen , installed TWRP and wiped cache ( Stock CM recovery was not helping). Phone worked great since then.
3. TWRP was not longer there, instead CM Recovery.
4. New update has arrived, but i get an "ERROR" word in the middle of screen while installing.
What can I do?
Thank you in advance for your response.
Click to expand...
Click to collapse
thanks! here I found the CM13.0 Signed flashable zip
cm-13.0-ZNH0EAS2JK-bacon-signed.zip 691 MB
rebooting
applying full zip via stock recovery
rebooting - everything apparently the same
applying update via stock recovery
rebooting... optimizing apps...
success! COS 13.1 up and running! (phone very warm though)
thank you very much for the support. (why messing with android must be so complicated?)
USER ABOVE YOU POSTED HOW HE DID IT. FOLLOW HIS GUIDE AND THANK HIM

anyone have problem with titanium backup on latest ota s1kn ? i cannot freeze and restore app , any idea ? su version 2.65

Are there also any changes with the camera?

prototyp01 said:
Are there also any changes with the camera?
Click to expand...
Click to collapse
Hyperlapse got added !

Is overall camera quality better than before? Or is Hyperlaps the only change?

prototyp01 said:
Is overall camera quality better than before? Or is Hyperlaps the only change?
Click to expand...
Click to collapse
I am sure some one else will be able to answer this better
I haven't flashed this update yet neither I am camera enthusiast.

Updated on this one yesterday, and I regret it....my phone now charges very slow, it took 8 hours to fully charge, dont have this issue before, tried everybody else fixes, but did nothing...do anybody has the flashable ZIP on the previous version and can be flashed using stock recovery?
Thanks

Related

Original Shield tab 4.1 OTA update

Doesn't seem like there will be a US LTE version again... hoping there will be a RoW version that someone will eventually create a flashable zip...
Hey Guys -
Yeah, just saw this was available for my Original Shield Tablet (rooted) few minutes ago. Aside from wiping and installing OS all over again, what's the best method to upgrade and ensuring I still have root afterwards + retain installed apps & settings?
I use an SD card in Internal mode if that makes a difference. Thanks!
Just got the Notication for the wx-un-do upgrade.
Now looking for the full ota update.
Send from my .I. .I.
Don't worry, it doesn't seem to work. OTA downloads, boots and back into system again. Asks to download ota again, version number unchanged. I've tried it 3 times already.
Whatever Nividia can do wrong, they will do wrong. It's so frequent it's no longer funny.
When you are rooted and have a custom recovery installed you need the full Ota zip file.
The incremental ota update won't work.
Snah001 said:
When you are rooted you need the full Ota zip file.
The incremental ota update won't work.
Click to expand...
Click to collapse
If you're telling me, then my device is unrooted, stock everything. Not just me, got another guy on the Shield forums saying the same thing hehe.....
on a side note, mine is a ROW LTE. Maybe those with wifi sets have better luck. But the other guy I mentioned has a wifi set, and it didn't work for him.
You have a custom recovery installed?
I search the full WiFi EU ROM. Can anybody help me
Snah001 said:
You have a custom recovery installed?
Click to expand...
Click to collapse
Stock EVERYTHING.
Have no intention to root this one because the battery replaced old version is already rooted.
---------- Post added at 03:17 AM ---------- Previous post was at 03:16 AM ----------
clawwulf said:
I search the full WiFi EU ROM. Can anybody help me
Click to expand...
Click to collapse
Be patient. It will come. many still asleep now.
When we have the full OTA zip then the link will be posted here immediately 4sure.
Yea, I saw mine had the 4.1 update and decided to wait to sideload it and not do the OTA update. Waiting for a TWRP version.
C'mon, RoW LTE version... can't wait
JohnK71 said:
Yea, I saw mine had the 4.1 update and decided to wait to sideload it and not do the OTA update. Waiting for a TWRP version.
Click to expand...
Click to collapse
You should be able to do a FULL OTA download, offload it - then TWRP it.
Once they post it on their site, we'll be able to flash it one way or another, just a matter of time. I'm disappointed it's only through the Mar update though...
Release notes here:
https://shield.nvidia.com/support/shield-tablet/release-notes/1
Incremental OTA works just fine on rooted tab + TWRP. Just keep in mind that it will replace your recovery for the stock one and you will loose root.
Worked fine for me. Completely stock.
Didn't work for me on stock row lte rom with multirom. Does go into mr twrp but fails install with an error 7.
Snah001's posting #24 of 2016.05.13.Fr.09:35 PM solved it all.
Before that, I ran into Failure as follows with "Upgrade" on my rooted RoW LTE.
< 1. > Hitting [[ Restart to install ]] made it into Team Win Recovery Project v3.0.0-0, where it logged the following :::
Running OpenRecoveryScript – Installing ZIP :::
Updating partition details » Done.
Full SE Linux support is present.
Running Recovery Commands
Installing zip file '@/cache/recovery/block.map'
Installing zip file '@/cache/recovery/block.map'
Checking for MD5 file.
Skipping MD5 check : no MD5 file found.
:::
After that, I could reboot from TWRP, get another identical upgrade notification, and loop through as_many times as I'd like.
< 2. > Installing the upgrade manually from TWRP resulted in :::
Source : nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_664.1902:user/release-keys
Target : nvidia/wx_un_do/shieldtablet:6.0.1/MRA58K/40827_700.6895:user/release-keys
Verifying current system...
Package expects build fingerprint of :::
nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_664.1902:user/release-keys
or nvidia/wx_un_do/shieldtablet:6.0.1/MRA58K/40827_700.6895:user/release-keys;
this device has ::
nvidia/wx_un_do/shieldtablet:6.0/MRA58K/41524_658.5732:user/release-keys
:::
Updater process ended with ERROR : 7
Error installing zip file '/data/data/com.nvidia.ota/app_download/PUBLIC92c9 4d59.zip'
Updating partition details » Done.
» Failed.
< 3. > Skipping all checks in OTA 4.1 LTE's "PUBLIC92c9fefb721b31eb2dc26fb6ac2b4d59.zip\META-INF\com\google\android\updater-script" seems no_good idea either, as I ended up without Notification Drawer and without Android Settings app. }} I had to restore a backup in TWRP to regain normal functionality.
Didn't manage to the OTA URL (somehow it's not showing in my logcat). But, I managed to grab it out and install manually with TWRP. Here it is:
Code:
https://mega.nz/#!XggijAhZ!Depd8u5nwMNt_wNcjbWmbT_6EGJB4OejmTv8eMSte9Y
EDIT: forgot to mention that this is the LTE ROW version.

New July images posted

Two again - MMB30K & MOB30O. I have no idea what the difference is, but I've used MOB30O successfully.
Link to the Nexus 6 OTA page with instructions for sideloading (no data loss, need to reinstall TWRP & reroot):
https://developers.google.com/android/nexus/ota
For those people who prefer to install separate components:
MMB30K
MOB30O
dahawthorne said:
Two again - MMB30K & MOB30O.
Click to expand...
Click to collapse
Did anyone ever figure out what the difference was? Google did this last time, and the result seemed the same between the two.
I went with MOB30M last time and it worked fine, so I'm going with MOB30O.
@dahawthorne added the links on the first post for you..
Thanks. I should have included the links, but I reckoned that anyone who's interested knows where to find them, and anyone who doesn't know probably shouldn't be tinkering...
But yes, the pointer is appreciated.
Edit: I used the OTA at this link - simpler, and doesn't lose your data:
https://developers.google.com/android/nexus/ota#shamu
Instructions are on the page. A simple sideload, flash recovery, install SuperSU.
Sir , is there any difference between MMB30K and MOB30O versions?
marcus droid said:
Sir , is there any difference between MMB30K and MOB30O versions?
Click to expand...
Click to collapse
we have to wait for the AOSP change logs on that
Encrytable boot/kernel IMGs:
MOB30O:
https://www.androidfilehost.com/?fid=24572369242688110
MMB30K:
https://www.androidfilehost.com/?fid=24572369242688111
What was the difference between the last 2 images? That was released without explanation as well!
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Strange. I sideloaded the MOB30O OTA, flashed TWRP (twice - it didn't stick first time) then installed SuperSU 2.76 from TWRP. No problems at all so far.
ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
The difference between these two images has been posted many times - not sure why people are confused about it!
MOB is the version you want.
MMB is the version for the Carriers who haven't approved the newer radio in MOB.
MOB also includes some kernel enhancements to increase performance. These changes related to the Kernel "Tick Rate". I think the changes have improved performance a little, but you're not going to think you've purchased a new phone or anything.
Summary:
MOB: Newer kernel with performance improvements, updated Radio image.
MMB: Older kernel sans performance improvements, old radio.
Summary: MOB is the train you want to be on.
ayang02 said:
I flashed the MOB30O version, anyone having trouble flashing SuperSU like me?
SuperSU flashed alright in TWRP(though the log seems a bit shorter than usual). When I rebooted the system, it says that SuperSU binary is not installed. I've tried to reflash TWRP (since stock recovery takes over) & different versions of SuperSU: 2.74 / 2.76 and can't seem to get root.
Click to expand...
Click to collapse
I dl'd the O image, extracted and flashed the system image only through twrp while at work. Rooted using a PC when I got home and I have no issues so fah. I use chainfires method and his method requires running his image with fast boot. Fastboot boot cf... What ever you have the file named. It'll do it's thing on the phone then reboot 1-3x before it boots up fully. This root it rebooted once. On previous updates, up to 3 times before it finally finished.
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
For me it's because I've lost my data a couple of times in the past doing an OTA update. I guess old habits die hard and I like the control I have flashing each image file manually. At least that way I can be reasonably sure that my data isn't messed with by not flashing the userdata image, plus, I can skip flashing recovery so I don't have to reinstall that. It only took me 9 minutes to complete the process tonight, including re-rooting, doing it the "old" way.
dahawthorne said:
Why are people insisting on flashing the "old" modular way (extracting components for individual flashing) when Google have provided a total no-data-loss OTA? 15 minutes, risk-free. Why choose the difficult way when there's a seamless simple upgrade? Incomprehensible.
Click to expand...
Click to collapse
Two very simple reasons. 1) if you are rooted. 2) if you are unencrypted.
FWIW: it takes about 60 seconds to extract the images from the .zip file. And about 3 minutes to flash the boot and system image files in fastboot.
before i download the entire package can anyone tell me if there is a new modem in july update?
H4X0R46 said:
I flashed SuperSU 2.76 just fine after flashing the MOB30O image. Also, I've never had stock recovery get replaced on my Nexus 6 ever. That's really strange.
Click to expand...
Click to collapse
Then that means you were able to get root successfully. My TWRP recovery got overwritten because I didn't get root. Anyways, I am gonna try flashing stuff from scratch in a few days. I've also never had issues flashing monthly updates and SuperSU until now.
Sent from my Nexus 6 using XDA Free mobile app
adm1jtg said:
before i download the entire package can anyone tell me if there is a new modem in july update?
Click to expand...
Click to collapse
There is no new modem, nor bootloader. Just security updates to boot and system images.

N910TUVS2EPG2 - Caution & Info

Be cautious with the latest N910TUVS2EPG2.
You might not be able to downgrade the bootloader once its updated.
If you look back at the history of builds for the N910T you will see the following:
N910TUV U2 EPE3 = 6.0.1
N910TUV U2 DOK2 = 5.1.1
N910TUV U1 COG2 = 5.0.2
Pay attention to the U1 & U2 numbers.
Notice that you can upgrade and downgrade between 6.0.1 and 5.1.1 but cannot downgrade to 5.0.1
Both 6.0.1 and 5.1.1 have U2 in their build. In the past (at least on some devices) once these numbers change is when you cannot downgrade to a different number.
So whats my point? Look at the latest build. N910TUV S2 EPG2.
"S2" This very well could mean you can not downgrade to 5.1.1 and or PE3 6.0.1.
It also could mean that there have been some other bootloader changes.
There have been some reports that some on the latest N910TUVS2EPG2 have had trouble flashing TWRP.
Disclaimer: This info is not to be taken as golden fact. I'm just providing it so people can look out and be aware this has been the case in the past.
Since a lot of this information has not been confirmed and will not be confirmed by Samsung we can only go by past situations.
This has been indeed the case on both the Note 4 and the Galaxy Tab S2
To everyone that has indeed updated to this new Firmware version (N910TUVS2EPG2) please post any experiences from it.
Any problems? Any confirmed known changes. Anything.
Thanks!
I updated, and I was able to install twrp, root, and xposed. However, I have heard reports that twrp doesn't work for some people.
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
ayeitschris said:
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Chocu1a said:
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
Click to expand...
Click to collapse
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
DeeXii said:
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
Click to expand...
Click to collapse
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
wilsonmd said:
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
Click to expand...
Click to collapse
Any update to this?
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
Odined stock EPG2 tar, SuperSu systemmode, Xposed alt 86 wanam, TWRP 3.0.2-0, no issues. Great battery, runs smoother, no hiccups. :good:
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
via Odin and i could not let me try flashing the LP bootloader and flash any room ......
How Downgrade your T-Mobile Note 4 (N910t) from MM (any version) to DOK2 Lollipop!
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
IM NOT RESPONSABLE IF A HEART ATTACK OCCUR OR YOUR PHONE BLOW UP WITH ALL THE ROOF :silly:
IF YOU HAVE YOUR PHONE IN MM PG2 STOCK rooted with super SU systemless and last TWRP instaled (like me) YOU CAN DOWNGRADE TO D0K2 LOLLIPOP :
******REMEMBER Disable Reactivation lock (see picture below) and activate USB debuggin, Before DO this procedure!!*******
1-Download the DOK2 BOOTLOADER HERE https://www.androidfilehost.com/?fid=24269982087008410 and the D0K2 modem here: https://www.androidfilehost.com/?fid=24269982087008409 ( i did use 3.0.9 Odin) >>>>>>>>>thanks to @xoxo_xdagirl91 for post the links!
2- Download The 5.1.1 rom here: http://forum.xda-developers.com/note-4-tmobile/development/rom-maximum-ovrdrive-v15-1-1-t3196653 its an awsome rom by @OvrDriVE and so Thanks for that!
3-Put the ovrDrive 5.1.1 rom into the external sd card together with the upgrade. (because need erase all in the internal memory, remember, make a back up of your data in the phone or in the internal memory if you want).
4-now GO to your TWRP and wipe cache-dalvik-system-data-INTERNALmemory x3 ..........DONT TOUCH YOUR EXTERNAL SD, REMEMBER THE OVRDRIVE 5.1.1 ROM IS THERE!
******REMEMBER WHEN YOU ERASE YOUR INTERNAL MEMORY JUST REBOOT AGAIN IN RECOVERY, each time you erase yor internal memory, when reboot in TWRP you see the warning and said that you need to click in "never show this screen during boot again" just click there and swipe to allow Modifications or the stock recovery will rewrite again. TURN OF YOUR PHONE!
5-GO TO DOWNLOAD MODE TO USE Odin and flash the 5.1.1 bootloader FIRST, WHEN FINISH, Flash the modem ..... REMEMBER: put the bootloader in the BL section FIRST AND FLASH & FOLLOWING THE modem in the CP section of odin
6- When finish the step 5, go to your recovery TWRP>install>go to ext sd>flash the ROM first, when finish, wipe dalvik, cache and reboot again in TWRP
7- Just flash the othe part of the rom........the upgrade zip file, when finish just reboot the system aaaaaaaand
WALAAAAAHHHHHH!!!!!!
I DID IT EXACTLY AS DIRECTED AND I HAVE A CLEAN OVRdrive
rooted rom in 5.1.1. Now you can flash via ODIN the original firmware on 5.1.1:good::good:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
mykos said:
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
Click to expand...
Click to collapse
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
kiikez said:
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
Click to expand...
Click to collapse
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Conflicting reports on here. I haven't tried this myself yet but THIS post states a successful downgrade. YMMV.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
how did you flashed the super su systemless?
Cannot root or odin twrp after latest (pg2) update. Odin to pe2 and everything is back to normal.
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
krishelnino said:
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
Click to expand...
Click to collapse
Sure bud.
1) Download the M6 ROM from Dev-Host or from MediaFire.
Put this file in your external SD card.
2) Download the BeastMode kernel.
Put this file in your external SD card.
3) Download the Data Fix - MM_DataFixs7rebootmenu.zip.
Put this file in your external SD card.
4) Boot into recovery. Make a backup of your current ROM just in case. :fingers-crossed:
5) Go into Advanced Wipe (if you're using TWRP) and wipe dalvik, system, data, cache, internal storage (or whichever options are available in the recovery you are using).
6) Flash M6 Rom from Step 1. Do not restart.
7) Flash kernel from Step 2. Do not restart.
8) Flash data fix from Step 3.
9) Now wipe cache and dalvik cahe. Restart.
Once you restart, it will look like your phone crashed or is stuck in a bootloop, it's not. Let it sit there for about 10-15 minutes and it will boot into the setup screen. Good luck. :good:

LE S3 20 & 21s[official]with OTA updatable[Lock bootloader]

This is totally CLEAN and Typically ENGLISH (OFFICIAL) version that means no chinees APPS no issue.
Donot forget to make a backup before starting.
Steps to Follow: (FOR TWRP installed user)
1. Download 20s OTA file from here.
2. Download 21s OTA file from here. (Donot Download this ZIP file as i got an OTA update of 21S after installing 20s)
3. Goto TWRP recovery.
4. Formate everything. (Cashe, Delvik, Sysytem,Data)
5. Flash the 20s Rom (Provided in STEP 1)
6. After Installing and setting up phone, You are ready to GO BACK to official stock recovery.
Steps to Follow: (FOR already on stock recovery users)
7. Download the 21s recovery (provided in step # 2)
8. change the name to update.zip
9. put it into the root folder.
10. Goto stock updater and slect MANUAL UPDATE from 3dots on top.
11. This is will install the recovery 21s.
12. DONE
Note: you can not install 21s directly on custom recovery as it will give error 7
Can you 1. correct typos 2. move this to https://forum.xda-developers.com/le-2/how-to
Thank you
Thread cleaned up.
If you find some rule violation, please report it.
Also this is not a thread to bring up your personal vendettas. Add the annoying member to your ignore list and move on. No need to use foul language.
Consider this as the first and final warning. If this is repeated any further, there will be action taken against your accounts.
Hope I made myself very clear.
Regards
Vatsal,
Forum Moderator.
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
26s removed
as the provider stopped me to share it. correction in heading done.
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
zogu said:
Found link on Google's cache of https://forum.xda-developers.com/le-2/how-to/le-s3-20s-21sofficial-ota-lock-t3634079.
But this file update.zip was for s2_india, not for s2_na
Is newer version for usa market available?
Click to expand...
Click to collapse
As I already mentioned that I have tested these file on my x522(S3) before upload.
Nd x52x series means x520/522/526
Download 20s flash it you will receive 21s automatically
zogu said:
I didn't understand, is 26s version available for x522 because it is mentioned in the name of this thread?
Click to expand...
Click to collapse
Original 26s is available in Chinese only. You can flash it via twrp than root nd remove all Chinese app.
Chinese twrp ?
edan lkr said:
Chinese twrp ?
Click to expand...
Click to collapse
Yes.
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Christhepenguin said:
Sooooo I have a slight problem.
I have TWRP and stock ROM. Sort of. Xtreme Addiction ROM, only one that would work and not give the error"This is an s2 not s2_na_Xxxx" so I Flashed that, and uninstalled root, now in TWRP it doesn't show my internal storage so I can't flash this ROM, and ask for a password. So I tried using the 3dot option from settings and it won't work either, it'll just boot to TWRP and nothing happens. I'm really not looking forward to deleting everything... AGAIN but I will if I have to.
Click to expand...
Click to collapse
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
gtd2000 said:
I think we might be having the same problem...
My X527 came with 16s as the stock ROM.
Upgraded to 19s with TWRP which gives me the system update option as well as OTA (which says I'm running the latest version).
I want to update to 21s and use the system update method..
Phone starts to load the new update (renamed to "update.zip") progress bar at the bottom of the screen while all of this takes place.
Phone reboots into password screen for TWRP, swipe to continue, then select system reboot and once it's back up and running it is still on 19s...?
Did you get your update resolved?
Click to expand...
Click to collapse
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Christhepenguin said:
I did, I used this website. https://www.google.com/amp/s/forum....factory-image-5-8-020s-directly-t3527790/amp/
Downloaded Chinese TWRP from there. As well as that ROM, if you have the 21s update file, I'm sure you can get it working with that TWRP. Hopefully it works for you.
Click to expand...
Click to collapse
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
gtd2000 said:
What worked for me was replacing TWRP with the factory recovery and I'm good to go.
There was talk of an official update (beyond 21s) in December but so for, no sign of that...
Click to expand...
Click to collapse
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Christhepenguin said:
Interesting, replacing stock Recovery didn't work for me when I did it, and yeah. It's most likely not coming soon due to financial issues LeEco has.
Click to expand...
Click to collapse
I note that this says it's the ROM for the S3.
I'm using the X527 which is the S2 with the Snapdragon chip (now listed as X526 after installing 21s), did you perhaps flash the incorrect ROM?
I had continual problems upgrading from 19s with TWRP - it would go through the whole process and then reboot to 19s..
Even after the replacement of the stock recovery, the first ROM I downloaded (21s) was not accepted. Had to download another one for it to finally work.
Could be a bad download?
Contact
How did you contact leeco and get this. I need all future updates. My phone is rooted and I am unable to completely unroot it and get OTAs.
---------- Post added at 02:59 AM ---------- Previous post was at 02:52 AM ----------
rodogg88 said:
Is there an update for the Le s3 x522 that can be installed though the phone update app? I am still running stock recovery and don't want to change it but it seems the OTA updates not working
Click to expand...
Click to collapse
If you don't have TWRP or anything installed, it should work fine if you put the 20s update in the root folder (the folder with the android and download folders). Then just go to system update, press menu, press local update, go through prompts and it should update automatically. Then just repeat the process for the 21s update. If you have twrp installed, I'm pretty sure the chinese ydss version doesn't allow OTA installs. This update requires stock recovery installed because it updates through the recovery. You can find stock recovery images on google (search le s3 stock recovery and click skyneel) or, someone might have posted a recovery image on the le 2 forum. Plz reply if it doesn't work, it worked for me tho.
Is there any bugs? If yes please list. Thank you
does it work for le s3 X626 mtk?
if not, please guide me as I see that this forum support Le S3.
thanks.

Help with soft brick

Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.
+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.

Categories

Resources