Related
This does work to upgrade from 4.4.2 to 4.4.4 and there was no data/setting loss. I am running Verizon, developer phone, rooted, with xposed. Here are the directions I used:
1. disable Xposed - I just went to the app and uninstalled it
2. boot into bootloader/fastboot - connect your computer to the phone via USB. Then push the down volume and power at the same time. This will take you to the bootloader/fastboot
3. flash stock recovery (fastboot flash recovery yourfilename.img) - to do this (and to flash stock system) you need the motorola fastboot files and you will need to use the command prompt on the PC. for directions and download for the fastboot files check out this link - http://www.addictivetips.com/android/root-moto-x-install-cwm-recovery-complete-guide/ To actually download the stock recovery and stock system files you can download them here (look for 4.4.2 verizon - http://sbf.droid-developers.org/phone.php?device=0. I actually pasted the recovery.img/stock.img files into the windows fastboot folder and accessed CMD prompt from there to flash them. I flashed recovery then moved onto stock. I did not reboot until both were done.
4. flash stock system (fastboot flash system yourfilename.img)
5. reboot (stay in the CMD prompt and type - fastboot reboot)
6. update via OTA
7. reboot
You are now stock unrooted 4.4.4, so just re-apply root the same way you did the first time:
1. boot into bootloader/fastboot - you should be able to follow the directions from above to do this now
2. flash custom recovery - you should be able to follow the directions from above to do this now. Note that I tried CWM and it didnt work until I used TWRP. - download the latest version here and stick in the same fastboot folder you were using above - http://teamw.in/project/twrp2
3. boot to recovery - make sure you do this from the bootloader/fastboot screen. To do it, press down until you get to recovery then up to actually select it. I kept pressing power to select which doesnt actually select it.
4. flash SuperSU - this should be on your phone from the first time you rooted. If doing a new root you will need to get it first.
5. reboot
6. re-enable Xposed - i just reinstalled it and all of my settings were back
7. reboot
- BAM you are done!
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
Multiple reports all over the forum say YES. (must flash stock recovery back, FIRST -- OR just use the FXZ and don't worry about having to flash stock recovery...)
Also, to the OP: questions belong in Q&A, not General. See the 2nd Sticky post at the top of the General forum....please post in the correct forums in the future...
I have a vzw DE
I took the 4.4.4 FXZ file from the other thread and just flashed it, no prep, didn't disable xposed.I was flashing in fastboot, not recovery, so its not checking for intact files. Then had to twrp/root and re-enable xposed.
But if you want to take the OTA then your procedure would be good.
Ryphez said:
I'm curious to see if this works the same for unlocked non developer edition Moto X's on VZW too
Click to expand...
Click to collapse
There is no difference whatsoever between an unlocked dev edition and any other unlocked X. The ONLY difference is the dev edition keeps its warranty when you unlock.
Whats the best twrp for root on 4.4.4
Mickoou said:
Whats the best twrp for root on 4.4.4
Click to expand...
Click to collapse
How about the latest version from the official source? Here: http://techerrata.com/browse/twrp2/ghost
It will root for you. Just flash w/fastboot, then "fastboot reboot-bootloader", then VOL DOWN to RECOVERY, and VOL UP to select it. When you go to exit, it will offer to install SuperSU Installer. Once booted, launch SuperSU Installer, and select Play Store method.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
No, you should be the guinea pig for all of us.
I can confirm that this works. I did it. I did not lose any data. It took about 20 minutes total. I already had everything installed otherwise you are looking at about 45 minutes.
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
KidJoe said:
The only reason to flash stock system.img before taking an OTA is if you made so many changes to system files you can't remember them to undo them. i.e. you modified your system so much that flashing system.img is the fastest way back to stock so it passes the validation checks of the OTA.
I thought there is an Xposed disabler (in the xposed thread) that you can run rather than uninstalling?
That being said.. this information has been the same for EVERY OTA Update. You have to flash stock recovery for the OTA to install, and your system can't be modified too much or it will fail the validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
IF you are close enough to stock... you can also use the following... WITHOUT a PC... i.e. you haven't modified system too much, etc.
Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Install Rashr.
Use Rashr to to flash stock recovery (select other from storage, and select your stock recovery). When it completes, pick the option to reboot to stock recovery.
From stock recovery, install the update zip and reboot the phone.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
Click to expand...
Click to collapse
Thanks for the tip. I believe I did it the way I mentioned because last time gravity box didnt have a wifi tether available so I had to modify the system files. this time I didnt touch them.
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
+1 :good:
Schaweet said:
Flashing system.img is imo the smartest move to ensure the OTA takes. It's worth it as it only takes a minute and you don't have to even think about what you changed. Plus, it doesn't delete your data.
You are in there flashing stock recovery anyway, might as well.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
zoid_99 said:
I'm getting an error while attempting to flash the system.img. I don't remember the exact wording but it was something like "data exceeds download buffer". I flashed the recovery.img without issue. I tried to take the OTA and it gets halfway through and craps out with the red exclamation triangle... Any ideas?
Click to expand...
Click to collapse
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Schaweet said:
Are you using mfastboot to flash system.img? You can't use regular fastboot. Just search for mfastboot.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Thank you Thank you.... That was it.
dhoppy said:
has anyone tried this to upgrade to 4.4.4? (unlocked BL, rooted 4.4.2 on Verizon)
Click to expand...
Click to collapse
1.6 SU was the only issue I had, I got the latest and had no issue
http://download.chainfire.eu/supersu
KidJoe said:
[*]Place stock recovery.img, the latest TWRP img, the latest SuperSU.zip and the OTA.zip on your phone's DOWNLOAD folder.
Click to expand...
Click to collapse
Where do I get the stock recovery.img file?
Thank you!
fede_arg said:
Where do I get the stock recovery.img file?
Thank you!
Click to expand...
Click to collapse
The OP tells you in the very first post...
Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.
do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you
Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/
OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance
Sir
can you capture ota for myphone uno
gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Working internal detect for pc and file ?
marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM
marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.
success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man
Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!
OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.
Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!
1. Read the build information in the OP of the thread, it mentions all the differences.
2. It's the full stock FW but recovery flashable instead of fastboot and also rooted.
3. You would need to fastboot stock FW and manually root or flash the recovery flashable stock FW the was mentioned in question no. 2.
1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!
duba500 said:
1) "100% untouched stock framework" Would actually be and act the same as a real stock from from(Factory Image) developers.google.com?
2) Meaning that when an update will be released I would able to flash it auto' from the recovery?
3) Can you please explain me?
- "fastboot stock FW" ?? Means download the Factory Image from developers.google.com , connect to usd and hit the " flash-all.bat"?
- "recovery flashable stock FW" ?? I know only about the Factory Image that flashed through fasboot...Where can i get the recovery version? (not from Google,right?)
Or I could just use this tutorial?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481 Read this to get a better idea what to do.
duba500 said:
Hi There
Using this rom by Danvdh (6.0.1 MMB29K):
http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493
1) Is there a difference between the original one from Google to that rom?
2) OP mentioned that there is an updated recovery flashable releases of stock rooted Android.
It mean that it actually like an OTA updates?
3) What is the process if I want to move from rom such as the one mentioned here to a stock by Google and stay rooted?
Thanks!
Click to expand...
Click to collapse
1)Differences would be that SuperSu is installed, busybox is installed, encryption is disabled in the kernel, important gapps such as google play services and the play store are updated to their newest current version so when you install the rom google services immediately work without needing to wait for a background update, gapps that can be fully functional by just downloading them from google play store (google+, youtube, google drive, etc) were removed from /system likely to save space to make it easier to install mods such as guitardedhero's viper/dolby sound mod, vanilla android's gallery photos app was added in place of google photos app, the little android debugging notification is hidden, and the tethering check was disabled to allow for tethering without a tethering plan.
2) The updated recovery flashable line is referring to the fact that the dev updated the google apps in the rom.
3) If you wanted to go totally stock then you'd need to just flash the boot.img and system.img out of a factory image from google since the rom is very very close to stock a userdata wipe shouldn't be needed and a cache/dalvik wipe may or may not be but as always have a backup in TWRP. Then go into TWRP before booting and install the latest SuperSu (2.65 iirc right now) installing the newest SuperSu's can cause a bootloop or 2 (in the middle of booting the phone will go back to the Google logo and booting again, it will usually do this 1 or 2 times before properly booting). (if you boot to android before going to TWRP it will be replaced since you have an untouched /system after flashing the system.img). And if you allow TWRP to keep /system as read only (it'll popup when you first boot into TWRP asking if you want to do that) then the stock /system will replace TWRP with stock recovery and OTA's will work if you do a total unroot from within the SuperSU app.
Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download the factory image and just extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersyood it right?
Thanks for your advice-tip of the SuperSu version!
P.S:
LG doesnt have a dev site such as Google's have with all the Factory Firmwares?
Can I trust site such as: lgg3root. com/lg-g3-stock-factory-firmware
???
duba500 said:
Hi,
Regarding (1): Yes I know that.
I meant to the rom itself(not gaspps, supersu, busybox..).
(2) Really? that's all? I thought it kinda of ota to the rom.
(3) Really? that's all(2...)?
If i boot in into twrp => flash the boot.img and system.img from the factory image , I will have a totally stock rom?!
So 4sure just download G3 LS990 32GB and extract the boot.img and system.img?
Would you mimd to aprove if i got this right?
-> Take the boot.img and system.img from the factory image
=> Boot into TWRP and FLASH the 2 img's *without rebooting at the end*
=> Wipe cache/dalvik.
=> Flash SuperSu 2.65 ***By flashing 2.65 I wont face the 1-2 bootloop's?***
=> Wipe cache/dalvik.
=> Boot into system.
Did I undersood it right?
Click to expand...
Click to collapse
You have got a fantastic tip in looking here: http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Search for fastboot.
Am I the only one on XT1900-7 stuck on the August update? I mean considering it's NOVEMBER now... it's pretty infuriating. My phone is locked (I suppose... if it ever was) btw.
TeamRainless said:
Am I the only one on XT1900-7 stuck on the August update? I mean considering it's NOVEMBER now... it's pretty infuriating. My phone is locked (I suppose... if it ever was) btw.
Click to expand...
Click to collapse
Same here waiting for it as I hope it fixes the Android Auto connectivity issue .... wonder why it takes so long
Italy, XT1900-7 RETEU stuck on 8.0 August patch here, too.
I hope they're working hard on Pie!
Just got the October update Today. Apparently it was released Oct 4th... we just didn't GET it.
Same here
TeamRainless said:
Just got the October update Today. Apparently it was released Oct 4th... we just didn't GET it.
Click to expand...
Click to collapse
Same here ... just started the installation, but I doubt it will be an 8.1 update based on numbers it's "just" a security update ... will see what it fixes and what will be broken I would love to have Android Auto working without errors
the same **** here
Can I install thiw wia TWPR because i am rooted and I can not update?
vidra said:
Can I install thiw wia TWPR because i am rooted and I can not update?
Click to expand...
Click to collapse
No, only with stock recovery and all stock partitions.
Comby_sk said:
No, only with stock recovery and all stock partitions.
Click to expand...
Click to collapse
So if I restore /boot I should be able to do it?
vidra said:
So if I restore /boot I should be able to do it?
Click to expand...
Click to collapse
And /system too. I do flash fastboot rom without erase userdata and than flash OTA from adb sideload. Check my guide in moto x4 thread.
Comby_sk said:
And /system too. I do flash fastboot rom without erase userdata and than flash OTA from adb sideload. Check my guide in moto x4 thread.
Click to expand...
Click to collapse
I cannot seem to find it, can you please link it?
vidra said:
I cannot seem to find it, can you please link it?
Click to expand...
Click to collapse
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Comby_sk said:
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Click to expand...
Click to collapse
I don't have the permission to download the OTA.
Comby_sk said:
1. fastboot flash 8.0 OPWS27.57-40-22 (remove command "fastboot erase userdata" from script) - use this guide - after flash do not reboot to system
2. reboot to stock recovery (how to enter recovery) - install OTA from adb sideload - october 2018 OTA Blur_Version.27.301.32.payton.retail.en.US (save as zip)
3. reboot to system
if you want root gain
4. reboot to bootloader and use fastboot boot twrp.img
5. in twrp flash magisk and reboot to system
Click to expand...
Click to collapse
I keep getting E: failed to mount / if i use sideload and failed yo unmount / if I try to install from sdcard in official recovery.
How do I solve that?
Reboot to bootloader and check software status is official.
Comby_sk said:
Reboot to bootloader and check software status is official.
Click to expand...
Click to collapse
I have falsed everything back but it says modified. Did I miss something?
If software status is modified, you cannot install OTA from SD card or from adb sidelod. You will try fastboot flash with "fastboot erase userdata", but you will lost all pictures, settings etc. I dont know if this helps.
Comby_sk said:
If software status is modified, you cannot install OTA from SD card or from adb sidelod. You will try fastboot flash with "fastboot erase userdata", but you will lost all pictures, settings etc. I dont know if this helps.
Click to expand...
Click to collapse
Yes, but shouldn't the flag get reset back to official when I restored factory firmware.
vidra said:
Yes, but shouldn't the flag get reset back to official when I restored factory firmware.
Click to expand...
Click to collapse
It does not.. it will remain modified.. even if you root.. the flag is triggered that helps the folks at Moto recognise the Device is tampered or something.. and I dont think there is a way to get it to official
Abhishek Survase said:
It does not.. it will remain modified.. even if you root.. the flag is triggered that helps the folks at Moto recognise the Device is tampered or something.. and I dont think there is a way to get it to official
Click to expand...
Click to collapse
So how con I install the OTA?
Root can be done on Emui 9.1?
root for emui 9.1
Please
nothing yet?
nesoler said:
nothing yet?
Click to expand...
Click to collapse
Maybe this works with a magisk patched recovery_ramdis from EMUI 9.1 firmware?
I found the firmware here.
it gives me the error, error: cannot load 'recovery_ramdiskMagiskAL00-b7f69238.img': No such file or directory
htcdesire-hd said:
Maybe this works with a magisk patched recovery_ramdis from EMUI 9.1 firmware?
I found the firmware here.
Click to expand...
Click to collapse
it gives me the error, error: cannot load 'recovery_ramdiskMagiskAL00-b7f69238.img': No such file or directory
nesoler said:
it gives me the error, error: cannot load 'recovery_ramdiskMagiskAL00-b7f69238.img': No such file or directory
Click to expand...
Click to collapse
You first have to be on EMUI 9.1 and then patch your recovery_ramdis via Magisk (like with EMUI 9.0).
And you have to flash it via fastboot and the patched recovery have to be in the same folder. (fastboot flash recovery_ramdisk <your patched recovery>.img)
htcdesire-hd said:
You first have to be on EMUI 9.1 and then patch your recovery_ramdis via Magisk (like with EMUI 9.0).
And you have to flash it via fastboot and the patched recovery have to be in the same folder. (fastboot flash recovery_ramdisk <your patched recovery>.img)
Click to expand...
Click to collapse
I did everything and it didn't work
nesoler said:
I did everything and it didn't work
Click to expand...
Click to collapse
So you also did a full wipe after flashing the patched recovery?
What symthoms do you have if you say it did not work?
htcdesire-hd said:
So you also did a full wipe after flashing the patched recovery?
What symthoms do you have if you say it did not work?
Click to expand...
Click to collapse
I have not done factory reset. Is it mandatory to do so?
nesoler said:
I have not done factory reset. Is it mandatory to do so?
Click to expand...
Click to collapse
Yes unfortunatelly it is mandatory.
I would do the following:
backup all data
do a factory reset via settings
boot to fastboot after setup
flash your magisk-modified recovery via fastboot
reboot to recovery directly afterwards (unplug and press power and volume up until device is booting to recovery)
there should be the stock recovery surface where you do the factory reset again
phone should boot up rooted (Magisk Manager has to be installed afterwards)
(did not test it myself)
P.S.: due to a new filesystem it is probably not possible to modify the system folder I found out...
htcdesire-hd said:
Yes unfortunatelly it is mandatory.
I would do the following:
backup all data
do a factory reset via settings
boot to fastboot after setup
flash your magisk-modified recovery via fastboot
reboot to recovery directly afterwards (unplug and press power and volume up until device is booting to recovery)
there should be the stock recovery surface where you do the factory reset again
phone should boot up rooted (Magisk Manager has to be installed afterwards)
(did not test it myself)
P.S.: due to a new filesystem it is probably not possible to modify the system folder I found out...
Click to expand...
Click to collapse
I will hope that there is a safer method, thanks
nesoler said:
I will hope that there is a safer method, thanks
Click to expand...
Click to collapse
Not now due to the new filesystem-type... Maybe it will be fixed in the future by Magisk dev team...