Develop Bugs

[Q] OTA 4.1.2 Failed! No new OTA notification!

Hello,
I kind of messed this myself.
I have GN 4.1.1 takju - maguro JR003C - rooted, unlocked bootloader through GN ToolKit.
Now today got OTA notification of 4.1.2.
Installed OTA Rootkeeper, opted for "Reboot and Install" in OTA screen.
Phone booted into CWM Recovery and then update failed due to signature verification.
Now I am not getting the update notification back in System Update screen.
So the big question - how to get the OTA back and even bigger question - what do I need to do to have 4.1.2 in my phone?

I have the same problem and would like to know the answer.

PeteT said:
I have the same problem and would like to know the answer.
Click to expand...
Click to collapse
i think you should manually download the rom from google when it will be available and use for easy of use gnexusToolKit to install it.
I did like this last time for the same problem and got the problem also now...
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
PeteT said:
I have the same problem and would like to know the answer.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images

MaxDNet said:
i think you should manually download the rom from google when it will be available and use for easy of use gnexusToolKit to install it.
I did like this last time for the same problem and got the problem also now...
Click to expand...
Click to collapse
I can see for takju-maguro, there is an image for 4.1.2 at https://developers.google.com/android/nexus/images#takjujzo54k
But need some one to confirm if thats the one we need to manually install.
Also any help on my original questions will be helpful!

royzlife said:
I can see for takju-maguro, there is an image for 4.1.2 at https://developers.google.com/android/nexus/images#takjujzo54k
But need some one to confirm if thats the one we need to manually install.
Also any help on my original questions will be helpful!
Click to expand...
Click to collapse
I'm going to use that as i did last time for the 4.1.1.
Let you know.

Thank you
I hope it works. I would like to use the upgrade though and not a clean install.

PeteT said:
Thank you
I hope it works. I would like to use the upgrade though and not a clean install.
Click to expand...
Click to collapse
Done, so quick and easy. Google released a bat files inside the rom that will do it all (yeah it'll erase all your data but i like a full format sometimes so its ok for me).
So if you wanna to follow this procedure :
1 - Verify you have adb drivers installed and working
2 - power off mobile
3 - launch "flash_all.bat" files inside google rom
4 - power on the mobile in bootloader mode (menu down + menu up together and power)
This will start all the procedure.
Wait..
Done

You can open the flash-all.bat in Notepad++ and remove the -w switch and it won't wipe the data when flashed

MaxDNet said:
i think you should manually download the rom from google when it will be available and use for easy of use gnexusToolKit to install it.
I did like this last time for the same problem and got the problem also now...
---------- Post added at 11:30 AM ---------- Previous post was at 11:27 AM ----------
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
MaxDNet said:
Done, so quick and easy. Google released a bat files inside the rom that will do it all (yeah it'll erase all your data but i like a full format sometimes so its ok for me).
So if you wanna to follow this procedure :
1 - Verify you have adb drivers installed and working
2 - power off mobile
3 - launch "flash_all.bat" files inside google rom
4 - power on the mobile in bootloader mode (menu down + menu up together and power)
This will start all the procedure.
Wait..
Done
Click to expand...
Click to collapse
Thanks but could you please help with a bit more detailed for noobs like me!
1. How will we come to step 3? is it through genx toolkit?
2. delete all user data - you mean everything under /sdcard/ ? Means will need a backup of "everything" of my nexus!
Thanks again!

It's in the factory image you download from Google

royzlife said:
Thanks but could you please help with a bit more detailed for noobs like me!
1. How will we come to step 3? is it through genx toolkit?
2. delete all user data - you mean everything under /sdcard/ ? Means will need a backup of "everything" of my nexus!
Thanks again!
Click to expand...
Click to collapse
Hi i dont used GNexus toolkit.
The step i did are the following :
1 - Download the GNexus image (i downloaded the one without Google Wallet) from here https://developers.google.com/android/nexus/images#takjujzo54k and extract the content wherever you want on your pc.
2 - verify that your ADB drivers are installed and your mobile is recognized succesfully (you can do this by installing the gNexus toolkit and follow the inline instructions).
3 - Download if you dont have the fastboot (attacched) and for easy of use extract the content inside the folder of the downloaded ROM (would be better to install in a global folder and set it into windows global variables)
4 - Once extraced go into the folder where you have the extracted ROM and open the file "flash_all.bat" with a notepad
5 - update this line "fastboot -w update image-takju-jzo54k.zip" with this "fastboot update image-takju-jzo54k.zip" if you dont want to wipe your data and save the file.
6 - Inside this folder SHIFT + RIGHT MOUSE CLICK and select "Open Command Prompt from here"
7 - write flash_all.bat and it'll say it's waiting for device to be connected
8 - Power OFF your Mobile if you didnt do yet
9 - POwer ON your mobile in bootloader mode using the combination of VOLUME UP + VOLUME DOWN + POWER (all together at the same time)
The procedure will starts and your mobile will be updated in less than 2 minutes.
Hope this is clear.

It works perfectly!! Thank you.

It couldn't have been put more lucidly! Thanks.
But after installing 4.1.2, Titanium Pro stopped working! I uninstalled and then tried to reinstall but got "no space" error though 9GB is left free!
Any help!
---------------------------------
Solved from this post - http://forum.xda-developers.com/showthread.php?t=1717897
-------------------------------------
Moderators, please mark this thread as SOLVED

[FIX] build.prop variety fix (aka contact manufacturer problem)

Hello everybody,
this is a fix for the rather common build.prop variety problem on nexus 9 (and maybe others). This is the error-message that users often see after boot:
Android System
There's an internal problem with your device. Contact your manufacturer for details.
The problem occurs because of a check that google implemented in Android 5.1 which compares /system/build.prop with the values found in /vendor/build.prop. If they differ you get that error message. All one has to do to get rid of the error is to change the 3 values in /vendor/build.prop according to the values in /system/build.prop.
Doing this manually after every flash is cumbersome so I created an update-zip that corrects the values in /vendor/build.prop in a generic way (it should work no matter what rom you use). It mounts /system and /vendor, extracts the relevant information from /system/build.prop and creates a new /vendor/build.prop. I successfully tested it on my nexus 9 so I decided to release it to all of you.
Just install it via your recovery and you are done! This has to be done every time you flash a new rom.
Tell me if it worked for you!
cheers, chris

Works for me. Thanks!
Sent from my Nexus 9 using Tapatalk

Works on http://forum.xda-developers.com/showthread.php?t=3129778

Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.

wfujay said:
Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.
Click to expand...
Click to collapse
Have you flashed the stock vendor.img with fastboot?

wfujay said:
Welp, I flashed this while flashing the AICP rom and GAPPS and now touch is completely broken on my device. No touch commands work, not even in recovery mode. So I flashed to stock + unrooted with the Nexus Toolkit and still no touch. I have no idea what to do next...lol.
Click to expand...
Click to collapse
Hey wfyjay,
sorry to hear about your nexus. Well, my fix only creates a property-file which stores version-information in /vendor and should have nothing to do with your touchscreen problem. However, as fleischbanane said, have you tried flashing the vendor image which is included in Google's factory image?

fleischbanane said:
Have you flashed the stock vendor.img with fastboot?
Click to expand...
Click to collapse
No but any idea where to find this?
Sent from my Nexus 6 using Tapatalk

wfujay said:
No but any idea where to find this?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Factory images are located here: https://developers.google.com/android/nexus/images

gladiac said:
Factory images are located here: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Yes this is what I did with the Nexus Toolkit when I stated I "flashed to stock + unrooted". I flashed the latest LMY47X build and still no touch commands work.
Sent from my Nexus 6 using Tapatalk

wfujay said:
Yes this is what I did with the Nexus Toolkit when I stated I "flashed to stock + unrooted". I flashed the latest LMY47X build and still no touch commands work.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Well, that's odd. If you flashed back to stock then the vendor-partition (as well as all the other important partitions) must be in their original state. I'm afraid your touchscreen problem is unrelated to my fix. You could post a logcat (adb logcat) on the forum and someone might be able to figure something out or relock the bootloader and send your nexus in for warranty. I'm not sure if I can help you any further.

What is the command I enter to flash this file?
fastboot flash <????> vendor-build-prop-fix.signed.zip

mgiusto said:
What is the command I enter to flash this file?
fastboot flash <????> vendor-build-prop-fix.signed.zip
Click to expand...
Click to collapse
Hi, this file is supposed to be flashed via the recovery (TWRP, CWM, ...) just as you would do with a normal rom.

Worked for me, running Broken 2.4

Could just avoid all of this and update bootloader and vendor to 5.1.1
Sent from my LG-D852 using Tapatalk

Cuzz1369 said:
Could just avoid all of this and update bootloader and vendor to 5.1.1
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Hey there,
well, the error occures as soon as the values in /vendor/build.prop do not match those in /system/build.prop. Most roms only flash /system - leaving /vendor completely untouched. And since most roms change /system/build.prop in every release which in the end causes the error message to appear. At the end of the day, there is no mechanism that ensures that the values of those two files actually match. In an ideal world, roms should provide /vendor as well. In a less ideal world, roms should patch /vendor/build.prop themselves. In _this_ world, roms just don't care so I created this update-zip.
Hope that clears things up,
cheers gladiac

gladiac said:
Hello everybody,
this is a fix for the rather common build.prop variety problem on nexus 9 (and maybe others). This is the error-message that users often see after boot:
Android System
There's an internal problem with your device. Contact your manufacturer for details.
The problem occurs because of a check that google implemented in Android 5.1 which compares /system/build.prop with the values found in /vendor/build.prop. If they differ you get that error message. All one has to do to get rid of the error is to change the 3 values in /vendor/build.prop according to the values in /system/build.prop.
Doing this manually after every flash is cumbersome so I created an update-zip that corrects the values in /vendor/build.prop in a generic way (it should work no matter what rom you use). It mounts /system and /vendor, extracts the relevant information from /system/build.prop and creates a new /vendor/build.prop. I successfully tested it on my nexus 9 so I decided to release it to all of you.
Just install it via your recovery and you are done! This has to be done every time you flash a new rom.
Tell me if it worked for you!
cheers, chris
Click to expand...
Click to collapse
I have been flashing and trying different ROMs lately and when I saw this internal problem message I got the fright of life, google search brought me to Ur life affirming thread, is it safe to use Ur fix on Samsung Note 4?
Thank U.

Anubis22666 said:
I have been flashing and trying different ROMs lately and when I saw this internal problem message I got the fright of life, google search brought me to Ur life affirming thread, is it safe to use Ur fix on Samsung Note 4?
Thank U.
Click to expand...
Click to collapse
Hey there,
to be honest - I don't know for sure. The note 4 does not seem to have a vendor-partition. Can you check with a file-manager if there is indeed no /vendor on the note 4?
cheers

gladiac said:
Hey there,
to be honest - I don't know for sure. The note 4 does not seem to have a vendor-partition. Can you check with a file-manager if there is indeed no /vendor on the note 4?
cheers
Click to expand...
Click to collapse
Therein lies the crux of the matter, I really am a novice since I shifted to Android a few months ago, so must apologise for my lack of knowledge and perhaps limited answers .. I do have a /vendor folder which clicked shows 3 folders (etc, firmware, lib) Another thing, I Dual boot two ROMs, have tried all kinds of ROMs, the trouble started when I flashed the latest EchoeRom Hybrid version with CMRemix latest version (12.6) I don't know which of the two created this issue.
Could U perhaps help me change these lines manually plz? Or direct me to a guide

Anubis22666 said:
Therein lies the crux of the matter, I really am a novice since I shifted to Android a few months ago, so must apologise for my lack of knowledge and perhaps limited answers .. I do have a /vendor file/folder which clicked shows 3 folders (etc, firmware, lib) Another thing, I Dual boot two ROMs, have tried all kinds of ROMs, the trouble started when I flashed the latest EchoeRom Hybrid version with CMRemix latest version (12.6) I don't know which of the two created this issue.
Could U perhaps help me change these lines manually perhaps? Or direct me to a guide
Click to expand...
Click to collapse
Alright, no problem. So you do have a /vendor folder. That's good! Is there also a file called build.prop in it? And if there is, does it happen to have the following 3 lines in it?:
ro.vendor.build.date=something
ro.vendor.build.date.utc=something
ro.vendor.build.fingerprint=something
If it has those 3 lines - go ahead and try my apk. If it has more lines you can pm me the /vendor/build.prop as well as the /system/build.prop and I will have a closer look.

gladiac said:
Alright, no problem. So you do have a /vendor folder. That's good! Is there also a file called build.prop in it? And if there is, does it happen to have the following 3 lines in it?:
ro.vendor.build.date=something
ro.vendor.build.date.utc=something
ro.vendor.build.fingerprint=something
If it has those 3 lines - go ahead and try my apk. If it has more lines you can pm me the /vendor/build.prop as well as the /system/build.prop and I will have a closer look.
Click to expand...
Click to collapse
Thank U so much for Ur kind help.
I checked, this /vendor folder doesn't have the 'build.prop' file in it,it has just three folders. Although /system folder does have the 'build.prop' file. See attachments, please

Updated Magisk Manager - NOW BRICKED?!

Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:

dustylambo said:
Hello all!
This morning I updated Magisk Manager.
Once updated (or perhaps only downloaded update) the app prompted a reboot.
I rebooted and ended up in TWRP.
But I did not know what to do in TWRP so I rebooted system...
However, now the phone cannot boot and after one try it reboots into TWRP again.
PLEASE HELP ME!
I need my phone for work! Like now-now! :silly: :crying:
Click to expand...
Click to collapse
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504

timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
Well, that rabbit went into quite the hole... hehe
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
The other suggestion was wiping my MISC-partition using commands through ADB - something I have no clue how to setup and/or execute.
Still, thank you so much for your effort!
Reading all of this made me remember that one time I spaced out and tried to install an official firmware update upon release and prompt, which lead to the same issue. I could then just reinstall an older raw firmware version, which left all my files and data intact. Hopefully this will work here too.
BUT... It still feels very risky. If anyone out there has any sure-fire solution to this update Magisk Manager through the built-in updater no-boot issue, then please feel free to let me know - I would be forever in your debt

The best surefire solution is just don't. And BTW always backup before you flash anything in twrp.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:49 AM ---------- Previous post was at 08:47 AM ----------
timbernot said:
How soon is now ? follow the white rabbit:good:
https://forum.xda-developers.com/zenfone2/help/help-bootloop-to-recovery-t3577504
Click to expand...
Click to collapse
I love what you did there! Lol
Sent from my ASUS_Z00A using Tapatalk

kenbo111 said:
The best surefire solution is just don't. And BTW always backup before you flash anything in twrp
Click to expand...
Click to collapse
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.

dustylambo said:
I didn't flash anything in twrp. If you're gonna reply at least read the post. Also, none of what you wrote is a solution, unless you're in possession of a time machine. I'll keep it in mind for the next time though (of which there won't be one). Thanks, captain hindsight.
Click to expand...
Click to collapse
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk

dustylambo said:
However, at the other end was a person who restored an old backup to revert this problem... And I -MAYBE- have an old backup on my external hdd, but won't that wipe all data that has been written to my phone since that "MAYBE" backup?
Click to expand...
Click to collapse
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.

kenbo111 said:
That's what the update does. Reboots to twrp and installs the download. Maybe you should know what you're doing before you snap at us.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Look... I am sorry if I "snapped" as you put it... But let's make one thing clear - I snapped at YOU; there is no "us" in this case, as you tried to skew it. Don't lump yourself together with these other helpful people, because so far you have nothing in common to me. If I were looking for someone to go "Hey, I got a solution - you know that thing you did? - Don't do it again!" I'd just go stand on the street corner with a sign asking for someone to slap my face.
As for your principal of don't do things if your not sure of how they work, I am totally behind that. But it has NOTHING to offer here as we are past that point. A broad comparison would be like "a solution to world hunger = eat food" ("but we don't have any food!" "you should have thought of that before you started starving now shouldn't you...?!").
In your defense, I guess you really believe you are trying to help. But compare your comment to the other ones posted and it is quickly clear that you are not. However, YOU ARE RIGHT, I should've known better and shouldn't do it again. And obviously I am enerved at this situation, but equally obvious (now) is that what you wrote is NOT "the best sure-fire solution" as what was posted afterward seems at least 100% (would have been more if possible) more applicable to my issue.
Anyway, I'll do the right thing here in the end, after having said so many things, and admit, once again, that I was wrong, you were right, I snapped for no good reason and you were just trying to help.
And I sincerely apologize for my rude behaviour. Hopefully now you can at least understand my reaction.
Also, fair is fair - Maybe TWRP flashes the update before it even enters into it. It would be the first I've EVER heard of something like that. But I am out of my element a bit here, so I will withdraw that comment and once again apologize for snapping at you because of it.

Magister54 said:
No, just restore the boot partition (16MB).
I learnt the hard way about backup, when years ago I didn't make one for my Galaxy S2 and lost everything (pictures, etc). Now after installing TWRP I always do a backup...
You should be able to reflash your boot partition with a fastboot command like "fastboot flash boot boot.img" (people with more knowledge than me can help you)
EDIT: the problem is that our Zenfone2 needs a signature for the boot partition, this is why we have a special Magisk installer that just add the signature to the image. The automatic update installer of Magisk has no clue about this, me and a few others here made the same mistake as you when Magisk popup "I have an update!" and we clicked "Install"...
All your data and app are still there, do not worry, no need to wipe anything, just reflash a signed boot.
Click to expand...
Click to collapse
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:

dustylambo said:
NOW THIS IS HELPING!
THANK YOU SO MUCH!
Basically, you are saying that I would, in theory, just have to use fastboot and flash boot.img (extracted from any firmware?) again, which I am very familiar with how to do, and presto - boot partition restored and working (once again, in theory)?
Sounds amazing!:good:
Click to expand...
Click to collapse
Yes, if you have a Z00A for instance with MM version 223, take the Z00A.zip file from https://forum.xda-developers.com/zenfone2/general/bl-unlock-ze551ml-toolkit-t3546293 and use the file stock\z00a\223\boot.img

This is stock unsigned boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img

timbernot said:
boot.img file for M .223
http://www.mediafire.com/file/rw73099svgbv0kv/boot.img
Click to expand...
Click to collapse
Is there any way to check from TWRP or using fastboot, or otherwise find out what version of the rom I have (had)?
I am definitely still on LolliPo... I think I am one or two official updates from the switch to MarshMallow... But how can I be sure?

WW_ZE551ML_2.20.40.139_sal358-amtech.vn
Last year sometime I ran into a similar problem, where I had to flash raw firmware in order to unbrick the phone... This is the firmware that I downloaded and flashed then.
However, within this .raw-file there is no boot.img ...? There are a couple of .img-files, but none named boot.
On a side-note: When I bricked it last year and had to flash this raw firmware, which I did with Asus Flash Tool, if I am not mistaken... However, whichever way I did it, I managed to flash and then boot as usual. The phone then updated all apps, and I was just blessed with this wonderful sight of "my phone" with all the apps, files and data still intact.
And this problem, which resulted in the same boot issue, came from trying to apply an official OTA update, just after rooting and unlocking the bootloader (forgot myself for just a moment there), which to me seems like a way more serious screw-up than what I just managed to do today...?

@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy

timbernot said:
@dustylambo
You still boot to TWRP ?
Simple questions
check date of back ups , course you won't be able to restore but title will have builds.
What twrp build ?
Then....
Select reboot in twrp then power off in twrp .
Wait 15 seconds...
Power plus vol+ , you can now boot to bootloader.
What IFWI version ?
0094.0177 or .0173 is LP
0094.0183 is M
Flash relevant raw , without ticking wipe data in AFT.
Check my unbrick thread in my signature for AFT and links to raws
Enjoy
Click to expand...
Click to collapse
Yes, I still boot into TWRP.
I can't find my old backup for some reason, but after flashing the previously mentioned raw firmware I never up- or downgraded the ROM, so it MUST be that version. It's the only one I've ever downloaded and flashed.
IFWI version is 0094.0183
But so you are saying I could basically just flash [correct version FW].raw via AFT, without wiping data, and all should be good?
I am on your unbrick thread aws.
I will def bookmark it.
But I already have AFT and the same FW... so I could just go-go-go, right? Or is the IFWI version being M an issue?
Also, I downloaded the official Asus FW from their ZF2 website. In that .zip is in fact a "boot.img" - can I flash this via fastboot you think?
Thanks again for all your help!
You are unbelievable!

@dustylambo
0094.0183 is M
So flash a M raw.
You must've upgraded bootloader since flashing the last raw .139 which is LP to get to M bootloader .0183
In bootloader .0183
You flash raw for M, these have just been added by realyoti
drop him a thanks .
Flash without ticking wipe data in AFT

Damnit! I don't like where this is going... But it's late and I'm dumb
I never upgraded to M because I read that there were several apps that would lose support, MUSIC in particular, but there were others as well.
Will an M raw-file flash and still boot with all my old apps?

@dustylambo
It's simple really , what is the twrp build number ?
You never said
0094.0177
Is locked 5 LP bootloader.
.0173 is 5 unlocked bootloader
.0183 is M
What twrp build is yours ?
Ps , I don't think it matters which version raw you flash , only that it may fail and might have to wipe data to succeed which is better than what you have and are struggling with right now
gnite , enjoy
---------- Post added at 11:45 PM ---------- Previous post was at 11:30 PM ----------
Pls , remember the reason you installed twrp initially ?
For backing up

Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.

adobrakic said:
Sounds like you didn't only update Magisk Manager, you update Magisk itself. A non-signed Magisk update will always result in bootloop.
Click to expand...
Click to collapse
To be corrected: Not the Magisk, but the repacked boot.img. ?
Sent from my Redmi 3 using XDA Labs

How to: flash stock without loosing data (without reformatting)

Hi all,
I had to reflash the stock, using the Lenovo Moto Smart Assistant. (Because the OREO OTA refused to install).
I connected the phone, followed the instructions (and backed up the data) but BEFORE starting the "rescue" process (and after completing the download) I modified a file!
Go in the "c:\ProgramData\LMSA\Download\RomFiles" folder, you will find the unzipped ROM folder, mine was "POTTER_NPNS25.137_93_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
Inside you have near 3GB of files.
Open with a text editor (notepad) "flashfile.xml" and delete this line (near the end):
Code:
<step operation="erase" partition="userdata"/>
Save the modified file and let the Smart(!) Assistant do the rescue.
After some minutes (be patient... nothing moves for a lot of time) the phone will reboot.
And your data is all at his place!
WARNING: in some cases the data format has a reason! Eg. if you flash a different ROM the system apps will find the old version settings and behave badly...
In my case I flashed the SAME ROM version so there really no reason to format.
Nicola

LMSA does not recognize my rooted phone. I think your process is good for stock un-rooted devices. Correct?

goodjuju said:
LMSA does not recognize my rooted phone. I think your process is good for stock un-rooted devices. Correct?
Click to expand...
Click to collapse
No. My phone was (and is) rooted.
The ROM was stock, with minor (unwanted) modification.
It's ADB working? Test it separately.

goodjuju said:
LMSA does not recognize my rooted phone. I think your process is good for stock un-rooted devices. Correct?
Click to expand...
Click to collapse
My device is rooted with magisk and recognized by Smart Assistant. I used it to download full fastboot firmwares
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
My device is rooted with magisk and recognized by Smart Assistant. I used it to download full fastboot firmwares
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Hmm... mine is too - but LMSA does not recognize - strange. It recognizes only when unrooted. Is your phone XT 1687?
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
nicolap8 said:
No. My phone was (and is) rooted.
The ROM was stock, with minor (unwanted) modification.
It's ADB working? Test it separately.
Click to expand...
Click to collapse
It was last time - when I upgraded to 8.1 using Minimal ADB and Fastboot. Will double check.

goodjuju said:
Hmm... mine is too - but LMSA does not recognize - strange. It recognizes only when unrooted. Is your phone XT 1687?
Click to expand...
Click to collapse
XT 1685
Sent from my Moto G5 Plus using XDA Labs

goodjuju said:
Hmm... mine is too - but LMSA does not recognize - strange. It recognizes only when unrooted. Is your phone XT 1687?
---------- Post added at 03:31 PM ---------- Previous post was at 03:27 PM ----------
It was last time - when I upgraded to 8.1 using Minimal ADB and Fastboot. Will double check.
Click to expand...
Click to collapse
ADB is working from minimal ADB and Fastboot app. Just upgraded to Oreo using the app first to reflash 28..85-17-1 then taking the OTA.

I tell you the problem is that the computer does not detect the phone is as if the data port on the phone does not work, if I open a CMD console and put the command: fastboot devices tells me that it is waiting for the device, but if I prendo the phone nothing and check the charging connector and it's fine, someone who has happened this and guide me. , I installed the drivers, tried other USB cable, and different PC ports

nicolap8 said:
Hi all,
I had to reflash the stock, using the Lenovo Moto Smart Assistant. (Because the OREO OTA refused to install).
I connected the phone, followed the instructions (and backed up the data) but BEFORE starting the "rescue" process (and after completing the download) I modified a file!
Go in the "c:\ProgramData\LMSA\Download\RomFiles" folder, you will find the unzipped ROM folder, mine was "POTTER_NPNS25.137_93_14_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml"
Inside you have near 3GB of files.
Open with a text editor (notepad) "flashfile.xml" and delete this line (near the end):
Code:
<step operation="erase" partition="userdata"/>
Save the modified file and let the Smart(!) Assistant do the rescue.
After some minutes (be patient... nothing moves for a lot of time) the phone will reboot.
And your data is all at his place!
WARNING: in some cases the data format has a reason! Eg. if you flash a different ROM the system apps will find the old version settings and behave badly...
In my case I flashed the SAME ROM version so there really no reason to format.
Nicola
Click to expand...
Click to collapse
Hi,
Will this method work on Locked BLs, and if USB Debug is off?
My Phone - Moto One Power

@nicolap8
Thanks, I added similarly instructions to my
LMSA: Lenovo's Motorola Smart Assistant thread
with a link back to this thread as credit.

Jack_731 said:
Hi,
Will this method work on Locked BLs, and if USB Debug is off?
Click to expand...
Click to collapse
The update part yes but I never tryed to skip the reformat with locked BL.
I think that CAN work but I can't assure this.
N
@sd_shadow: thanks

Has anyone had success or failure with this method lately? I want to give this a shot but I am worried about losing my data that I really need so I thought to hear from other experiences before I take my chance on this.

Shuton said:
Has anyone had success or failure with this method lately? I want to give this a shot but I am worried about losing my data that I really need so I thought to hear from other experiences before I take my chance on this.
Click to expand...
Click to collapse
Probably only a 50% chance that it will work for your device.
Is the bootloader unlocked?
What are you trying to do?

sd_shadow said:
Probably only a 50% chance that it will work for your device.
Is the bootloader unlocked?
What are you trying to do?
Click to expand...
Click to collapse
The bootloader is locked. My phone is stock and has never been rooted, which it somehow failed to boot one day with a "No bootable A/B slot" error. So I am trying to use the Rescue and Smart Assistant tool to fix it. I see that it would wipe the user data, so I am looking into options on how I can fix it without losing my data.

17.0240. 2004.9 Out

Was checking system updates and found an update.

HermesHidayat said:
Was checking system updates and found an update.
Click to expand...
Click to collapse
Yup, was posted today on telegram group...
(WW)
FOTA (incremental update from 2004.60) ;
Rename to UL-ASUS_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
https://fota2.asus.com/delta_packag...2004.60-17.0240.2004.9-06061254-fota-user.zip
Full rom zip ;
https://dlcdnets.asus.com/pub/ASUS/...S_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
Raw rom ;
https://drive.google.com/file/d/1T0P8CDJLjPypRAS2HDpdUn8Z-M5tfzKc/view?usp=drivesdk
Stock boot img ;
stock2004.9
Root boot img ;
root2004.9
Place rom in root of storage and reboot. Once detected click to update. Reboot again to finish.
For those with root already and wishing to keep root, simply put the rom in root of storage, reboot and click to update when prompted. BUT, DON'T reboot yet when it finishes updating. Click 'later', go to magisk manager and choose 'install magisk'. When given the options for installing, select 'after OTA' (or words like that). Once magisk is installed again, select reboot. Root will be maintained. Saving the hassle of flashing the root img via fastboot.
-----------------------------------------
For those of you who are not yet rooted but would like to be using the boot img above, see below for guidance. NOTE: if something goes wrong, I am not responsible in any way!! Also, by unlocking bootloader (which is required for root), you will void your warranty.
Also note: you must update to latest 2004.9 rom from above links before starting this process. Should you wish to do this process another time with another update, you MUST ALWAYS match the root boot img for the same rom version you are using.
1. First you need to unlock the bootloader. Download and install the apk from link, then follow instructions. NOTE: doing this wipe the device. Do not power off the device or stop the process once started. I think the device will reboot a couple of times during the process, but ican't remember sorry... Just leave it to do its thing and once finished, proceed to step 2.
Get the bootloader unlock tool, which says in the description that it's compatible with android 10, from here. You'll find it under tools/utilities.
2. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC/laptop to C drive
3. Download the root2004.9 boot img from above and move/save it to (C:\Program Files (x86)\Minimal ADB and Fastboot folder)
4. Switch the phone into fastboot mode (from device being in off/powered down, hold volume up then press and hold power button). Fastboot is the first screen you see with a scrollable menu giving some other options, don't select any options... just stay in that mode. Connect the phone to pc/laptop using the SIDE port of the phone. Navigate to C:\Program Files (x86)\Minimal ADB and Fastboot folder and double click the cmd-here.exe, this will open a cmd window.
5. (optional, but recommended) Once your phone is connected in fastboot mode and you have your cmd window open, type 'fastboot devices' in the cmd window. If your device is recognised then a key/serial will be displayed. Providing this is shown, proceed to step 6.
6. Next you are going to flash the root boot img (which, if you followed the instructions, should be in the Minimal ADB folder). In the cmd window type 'fastboot flash boot magisk_patched2004.9.img'. Once completed without errors, your device will now have a rooted boot img flashed. Yey!!
7. Now you can go ahead and unplug your device and boot it up. I did this months ago when I first got the phone, so you'll have to forgive me.... I can't remember if magisk manager is installed during the above process or if you have to install it manually after. If, when you have booted to system, there is no 'magisk manager' in your app drawer, you'll need to install yourself from here scroll about half way down the page and you'll see the downloads section. Go for the latest stable (currently 7.5.1).
8. Download a root checker app from playstore to verify you have root and you're done. If you need to resort back to original boot img, download it from above and follow the same process, but instead type 'fastboot flash boot boot2004.9.img'.

reg66 said:
Yup, was posted today on telegram group...
(WW)
FOTA (incremental update from 2004.60) ;
Rename to UL-ASUS_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
https://fota2.asus.com/delta_packag...2004.60-17.0240.2004.9-06061254-fota-user.zip
Full rom zip ;
https://dlcdnets.asus.com/pub/ASUS/...S_I001_1-ASUS-17.0240.2004.9-1.1.185-user.zip
Stock boot img ;
stock2004.9
Root boot img ;
root2004.9
Place rom in root of storage and reboot. Once detected click to update. Reboot again to finish.
For those with root already and wishing to keep root, simply put the rom in root of storage, reboot and click to update when prompted. BUT, DON'T reboot yet when it finishes updating. Click 'later', go to magisk manager and choose 'install magisk'. When given the options for installing, select 'after OTA' (or words like that). Once magisk is installed again, select reboot. Root will be maintained. Saving the hassle of flashing the root img via fastboot.
Click to expand...
Click to collapse
bro,im not saying youre disturbing or whatsoever,you should make a detailed thread.unlike me im kinda dumb,i dont understand this Root boot img and so on. and making your own thread will allow more people will see your thread as i doubt many people will come to this thread to read...

Can anyone check to confirm whether heating is still on an issue on the new version?

HermesHidayat said:
bro,im not saying youre disturbing or whatsoever,you should make a detailed thread.unlike me im kinda dumb,i dont understand this Root boot img and so on. and making your own thread will allow more people will see your thread as i doubt many people will come to this thread to read...
Click to expand...
Click to collapse
Nah, should be fine here. People will still see the update in your title and click to view content. And for those that want root who are not already rooted I'll add some instructions in a while or tomorrow about how to use the boot img's (on my phone right now, it's easier if I do it on pc). Links and details are only the second post on the page so people will still see the info they need. So yeah, if it's OK with you I'll just leave the content here rather than starting another thread with the same title
---------- Post added at 03:36 AM ---------- Previous post was at 03:35 AM ----------
TikiThePug said:
Can anyone check to confirm whether heating is still on an issue on the new version?
Click to expand...
Click to collapse
I'd like to shed some light on this for you but I'm not a heavy gamer (I assume that's when the device gets hot mainly) and have never had any heating issues with any of the builds

TikiThePug said:
Can anyone check to confirm whether heating is still on an issue on the new version?
Click to expand...
Click to collapse
i dont play games anymore on my phone but the only time it hit 74 degrees was when i left my phone in my car under the sun...
reg66 said:
Nah, should be fine here. People will still see the update in your title and click to view content. And for those that want root who are not already rooted I'll add some instructions in a while or tomorrow about how to use the boot img's (on my phone right now, it's easier if I do it on pc). Links and details are only the second post on the page so people will still see the info they need. So yeah, if it's OK with you I'll just leave the content here rather than starting another thread with the same title
Click to expand...
Click to collapse
of course its fine.i was worried people wouldnt be able to see it.

Issue with Android 10 update on tencent with WW fingerprint
@reg66 tried moving post 2 ROM into root of storage .bit the update is still failing . New update is detected and after reboot, while it initialising install it's failing at the very start
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !

VeeJay1 said:
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !
Click to expand...
Click to collapse
Hmm, you should be able to update from latest A9 (1910.64) to A10. I'm guessing that the updater app only downloads the small incremental updates. These will fail unless you update 1 by 1, going up one version each time.
If you wanna jump straight to latest update (currently this one) download the FULL rom zip from post 2 of this thread. Put that in root of storage and reboot. Should hopefully not fail now and you'll be on latest.

Issue with Android 10 update on tencent with WW fingerprint
@reg66 tried moving post 2 ROM into root of storage, but the update is still failing . New update is detected and after reboot, while it's initialising install it's failing at the very start
Hi I have a CN Rog2 on ww1910.64-0 and fingerprint on ww. Using Asus updater I am getting 2001.60 .but post reboot while installing it errors out in the very beginning. Any guidance would be much appreciated !

Yes, moved to 2004.9
Did the incremental update and now my tencent rog2 on ww2004.9. thanks for the pointers.They really helped.

reg66 said:
I'd like to shed some light on this for you but I'm not a heavy gamer (I assume that's when the device gets hot mainly) and have never had any heating issues with any of the builds
Click to expand...
Click to collapse
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.

well, video recording while connected to usb mic still doesn't work with the asus camera app

VeeJay1 said:
Did the incremental update and now my tencent rog2 on ww2004.9. thanks for the pointers.They really helped.
Click to expand...
Click to collapse
So the incremental worked direct from 1910.64 to latest? Or you had to go through each incremental?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
TikiThePug said:
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
Click to expand...
Click to collapse
Man that sucks. I've had zero heating issues even with leaving X mode on permanently @120Hz

Had to do this with each incremental update!
reg66 said:
So the incremental worked direct from 1910.64 to latest? Or you had to go through each incremental?
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
Man that sucks. I've had zero heating issues even with leaving X mode on permanently @120Hz
Click to expand...
Click to collapse

TikiThePug said:
Thanks man. Basically I had issues on A10 heating up even while just browsing the web. I would open up Armory Crate > Console and the CPU temp would be around 40+ Celsius. So now I'm back on A9, which shows temps of 30 Celsius with normal use.
Click to expand...
Click to collapse
I've also suffered from battery and performance issues in A10. A9 was just fabulous, A10 was a step back.
I'm also a heavy gamer and just updated so I'll be sure to let you know what's going on.
P.S I did manage to improve performance and some battery life by installing the only real custom kernel we have, but which is a great one - kirisakura + Naptime with doze on Google play services.

VeeJay1 said:
Had to do this with each incremental update!
Click to expand...
Click to collapse
Ahh ok, bummer!! At least it's sorted now

Hi all, I have problem with the last update, always that's stop at 9% with message error update

dracoolia said:
Hi all, I have problem with the last update, always that's stop at 9% with message error update
Click to expand...
Click to collapse
I had the same problem with the incremental update. Just use the full ROM linked in the op.

Thanks for the Rooted Image.

Hi just chasing the raw rom if anyone has it please!