Hello,
I want to know if it is possible to root the stock rom, and keep OTA.
Actually, my objective is to use screen mirroring (miracast), and I heard rooted devices can achieve that by changing build.prop. I didn't want to switch from stock rom, since I like it and like updating OTA.
Maybe if I adb boot twrp and install supersu, but keep regular revovery, I can still get OTA?
If there's another solution to screen mirroring, I'd be glad to know, too.
Thanks in advance!
I've tried to root stock rom and keep the system unmodified through Magisk. For whatever reason OTA always fails even though I have stock recovery, supposedly unmodified system, and rolling back to stock boot image prior to trying the OTA.
The only thing that works is to flash the stock firmware and then taking OTA. The only problem is that the stock firmware is tough to come by, but I read that someone got their hands on the latest 93-10 firmware image. So that's good.
I've since moved onto Pixel Experience 8.1 rom without any regrets. The camera works really well and battery is nearly up to par with stock Nougat.
No, unfortunately these things still modify the the system and boot partition and the upgrade script knows it and causes the update to fail. We don't know exactly everything the OTA update scripts check (it's not just a simple text file) but it is obviously something that it knows you are rooted even when nothing else does. :/
You must be completely stock to take an OTA update... the only exception is your bootloader lock state doesn't matter at this time, we do know that it is capable of detecting that as well.
I have done that and I got Bootloop! So don't Try!
else
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
Related
Hello,
I will try to keep this short. Was running 4.1.1 and rooted with moto2fail and installed safestrap recovery then I made a stock backup.
One day, my camera quit working (camera screen loads then a box pops up saying unfortunately, the camera has stopped) Anyways, I cleared data, rebooted same results. I didn't want to mess around with any files, so I decided to update to 4.1.2.
After the update, i get message that the update failed but everything seemed to be fine. AND the camera started working again.. Ending up losing root in the process, motochopper appears to install fine, but I get an error message when trying to update supersu. So, I reverted back to my 4.1.1 backup through the rp(?) tools in the stock recovery.
So now I'm back to 4.1.1 with full root, but no working camera. I can update to 4.1.2, but I think I'm gonna have problems with rooting again.
I did try reinstalling the stock MotCamera.apk from a stock razr m 4.1.1 rip. but it still fails. How can I fix the camera issues without having to mess around rsd lite?
Sorry about the confusion, just trying to lay out my issues and I will answer questions as I can.
i'm having the exact same issue, after failing to update to 4.1.2, i restored to 4.1.1 backup i had, but the camera just force closes. i'm on stock room.
bobross82 said:
Hello,
I will try to keep this short. Was running 4.1.1 and rooted with moto2fail and installed safestrap recovery then I made a stock backup.
One day, my camera quit working (camera screen loads then a box pops up saying unfortunately, the camera has stopped) Anyways, I cleared data, rebooted same results. I didn't want to mess around with any files, so I decided to update to 4.1.2.
After the update, i get message that the update failed but everything seemed to be fine. AND the camera started working again.. Ending up losing root in the process, motochopper appears to install fine, but I get an error message when trying to update supersu. So, I reverted back to my 4.1.1 backup through the rp(?) tools in the stock recovery.
So now I'm back to 4.1.1 with full root, but no working camera. I can update to 4.1.2, but I think I'm gonna have problems with rooting again.
I did try reinstalling the stock MotCamera.apk from a stock razr m 4.1.1 rip. but it still fails. How can I fix the camera issues without having to mess around rsd lite?
Sorry about the confusion, just trying to lay out my issues and I will answer questions as I can.
Click to expand...
Click to collapse
It could be that the Update has updated the firmware of the Camera itself, causing it to now be incompatible with the older 4.1.1 drivers baked in.
Typically when I get into these types of scenarios, I always feel best doing something along the lines of an RSDlite wipe and start fresh. Do the update straight, then customize afterwards.
I would unlock your bootloader prior to guarantee you have a back door into the phone afterwards.
I can't rsd back to 4.1.1, i get a preflash verification error, the only thing that works is matt's new utility that flashes to 4.1.2, the camera works after that, but i want the camera to work on the backup I did when i was on 4.1.1 before the update.
cybrnook said:
It could be that the Update has updated the firmware of the Camera itself, causing it to now be incompatible with the older 4.1.1 drivers baked in.
Typically when I get into these types of scenarios, I always feel best doing something along the lines of an RSDlite wipe and start fresh. Do the update straight, then customize afterwards.
I would unlock your bootloader prior to guarantee you have a back door into the phone afterwards.
Click to expand...
Click to collapse
I ended up booting in stock recovery by trying to get into fast boot, then selecting ap or rp tools(can't remember which). Truthfully, didn't even realize what it was. It loaded up what to me looked like the recovery menu with safestrap. Which I thought I uninstalled. From there, i restored the 4.1.1 backup I had. Then updated superuser and supersu from the play store. read in another thread to check and uncheck temp unroot in voodoo ota. twice.
Then I took the 4.1.2 update, was then able to install the supersu binary once it was finished and checked, and it kept root through the update. Camera works also. I still received a update fail message afterwards. But all appears to be okay, camera works, root checker says I have root, so all appears to be good.
I did make a backup of this in safestrap, and updated my backups in titanium, and froze a bunch of apps. Everything seems to be working just fine. I haven't unlocked the bootloader because I don't really feel like flashing any roms to this phone. Stock rom and rooted seems to be be good enough for me. For now.
If you still have a locked bootloader, you can't revert back without having issues. Once you've installed 4.1.2 and its boot.img, you shouldn't be able to restore a 4.1.1 ROM. If you are unlocked, then it's a different story.
For the OP, the best solution is to use Matt's Utility 1.20 and fastboot flash to 4.1.2. This utility does not require the use of RSD. After you flash, boot up the phone and just do basic setup, then use the Motochopper function in the utility to get root access. After you get root, then continue set up on the phone.
Just got the OTA update for nougat, every time I go to install it my phone crashes and switches off.
Anyone else having this problem?
Also, how to I flash stock recovery, I think it's to do with that STUPID twrp recovery that doesn't even work.
Megacamz said:
Just got the OTA update for nougat, every time I go to install it my phone crashes and switches off.
Anyone else having this problem?
Also, how to I flash stock recovery, I think it's to do with that STUPID twrp recovery that doesn't even work.
Click to expand...
Click to collapse
You need to flash back stock recovery. You can NOT update OTA updates when you have TWRP, it will crash, just what happened to you.
Use SPFT and flash back stock recovery for the current rom you are on. You can extract it from the scatter file. (If you don't know what that is, GOOGLE IT!!!!!!!!!!!!!!!!!!!!!!)
Btw I would avoid the update for now. It's buggy to say the least and you will loose fast charging.
Yea this OTA still needs improvement. Fast charging gone, fingerprint STILL not working, battery drain. Practically, latest Marshmallow is better then this OTA.I regret upgrading. If you gonna need downgrade use SPFT, their is a simple guide in umi community.
I did install iit and now I can not phone out or receive a call on Bluetooth phone Buzzzes loudly and the net work closes out, I use the bluetooth because of my hearing aids as the volume of the UMI super isn't very loud. I don't know how to fix this short of resetting back to origional except that way I loose all my info and have to start again. waiting for an answer.
Hello, i will try to be as elaborate as I can cause I know you guys here are really knowledgeable when it comes to smartphones. So, here are the issues I am currently experiencing with my G900F phone. Just a background, everything in my phone is stock (rom, recovery, kernel) no changes done yet. It currently runs MM with a security patch of February 2017. As of now, I can't boot into the phone.
1. . I was able to successfully root it with CF auto root.
2. I started experiencing random restarts. I tried obtaining the last kmsg however it does not exist.
3. I tried flashing a new ROM thinking maybe there is some rare bug in the stock rom i currently have. I flashed TWRP via Odin, to be able to flash a new ROM. Odin successfully flashed the recovery however when i proceed to install a new ROM through TWRP the phone gets stuck in a bootloop. I do not experience this in the stock recovery
4. I was able to restore the phone through Smart Switch device intialisation. However, with everything stock I still experience the random reboots.
Bottomline: Is there anyway I can fix this on the software side (e.g. flash/update this or that)? And if not, do you think this is a hardware problem? Worth mentioning it's got a yellow screen bug but if i press hard on the back of the phone it disappears. Also, I can boot into stock recovery and download mode without any problems.
Thanks and sorry for the long post really need your insights.
Sorry you are having issues. I apologize if I missed this, but have you tried downloading the official firmware for your device from sammobile or similar sites, then flash that through Odin?
Just flashed my XT1622 (UK Moto G4, NOT the plus version, but they are generally the same) using Nougat stock rom with September security patch(https://forum.xda-developers.com/mot...rch-1-t3608138). Thanks @tywinlannister7 who made the guide. It worked smoothly although it's in Moto G4 Plus forum.
Now, I got some questions regarding root. I did a forum search to find the post (https://forum.xda-developers.com/mot...droid-t3587918), which is quite good actually. However, I flashed my xt1622 for two reasons. The first is to upgrade to the latest system - Nougat (well, it not 'the latest' at the moment). The second is because I flashed TWRP on Marshmallow immediately after buying my Moto G4 to get root access, which stopped me to update the phone via OTA for a long time. I can still get the OTA notification, but it just won't let me update - failed after ~20 minutes. So what I did is just manually delay the update notification for 24 hours every day at 12.00pm. It bothered me a lot so I decided to go for a clean flash.
By flashing the new system, I lost some features I used quite a lot.
1. The root access for sure. I am not going to flash TWRP this time in case new patches would come over OTA again. If I flashed TWRP, I will face the same issue as I was on Marshmallow before this flashing. Is it possible to root without flashing TWRP that stops me to update over OTA?
2. I used to flash a specially made logo.bin to prevent the unlocked bootloader screen to appear. Now on Nougat, is there any similar logo.bin to do the same? A download link would be appreciated.
3. I used Llama with different profiles for some automated work such as change alarm volume at home or at workplace, make the phone ring loudly everywhere else, switch to flight mode at 12.00am at midnight and go back at 6.00am in the morning, automatically restart my phone at 1.00am while I am sleeping, and so on. This app won't work properly without root access. - well, looks like we go back to the first question of gaining root access.
Thanks for reading anyway.
1st you can't gain root without twrp installed and a custom kernel like ex kernel on stock rom. But on the opposite you can't update official OTA with a custom recovery like twrp.
2nd have a look at themes section
3rd see 1st
strongst said:
1st you can't gain root without twrp installed and a custom kernel like ex kernel on stock rom. But on the opposite you can't update official OTA with a custom recovery like twrp.
2nd have a look at themes section
3rd see 1st
Click to expand...
Click to collapse
thanks for your reply. I think I'd better stick to the official rom then. After so many times of flashing the phone, it seems that I cannot gain too much by rooting it.
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
travistyse said:
Same thing as the OP of this thread: https://forum.xda-developers.com/moto-g4-plus/help/bootloop-to-twrp-ota-update-t3667456
Late last night I saw that there was an update available and, given that I've only rooted my phone, security updates are important, and it's a mere ~15 minutes download + install time tops I went for it.
I absolutely cannot seem to get the update to install via the OTA channel - it downloads just fine but when I attempt to install it it boots into TWRP and once there the only way to leave is via Bootloader > Start (System just reboots into TWRP) and upon reaching Android I'm told that the update was unsuccessful.
I now have two problems:
1. I don't like having notifications that I can't do anything about. Assuming that this OTA is going to nag me for eternity that's definitely going to become an annoyance - but I'd prefer the update vs blocking the notification (again, IF it nags)
2. Every time I restart my phone (or it crashes) I now have to deal with TWRP. It's not a major annoyance. It's at most 8 extra seconds added to my boot time and I don't restart my phone more than 3 times a week. But it IS butt-ache inducing.
Edit: Forgot to add that I came across this and downloaded it https://forum.xda-developers.com/moto-e4/how-to/boost-mobile-ota-t3763851 My E4 is a 1766 and is also from Boost Mobile (Sprint) so I imagine they're the same update. Point is, can I install this with TWRP successfully or would that do nothing / make things worse?
Click to expand...
Click to collapse
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
madbat99 said:
You cannot install it with twrp on a rooted device. You would have to modify the updater script in it for that. And remove a bunch of assert props. And hope your system isn't modified too much.
So no, you can't. You have to flash back to stock, (the version you're on now) then install it. Or just sit tight, there is someone working on a partition updater, and a twrp flashable rom with the update included.
Once you root and install twrp, ota updates ain't gonna happen. How do you not know this
If you need a solution for the recovery Loop issue you're going to have to give me a minute to find the link it can be fixed.
It's a problem if TWRP when you format data not wiping something properly
this should help a recovery loop. Only if your issue is, every reboot it goes right to twrp. Then you have to reboot bootloader and select start. Easy fix.
Click to expand...
Click to collapse
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
travistyse said:
Thank you! And, frankly, because I never stick to stock. I always flash Cyanogenmod or LineageOS pretty much first thing when I get a phone. This time there wasn't a build available that seemed stable enough (Late November) but I still needed Root. I'm used to getting updates from both LOS and CM OTA so I figured the only thing preventing official OTA updates from working was that the build was entirely different. My assumption in this case was that I was still running the stock ROM that came with the device AND they were offering an OTA via notification so the phone must be eligible to receive it. >-> My bad.
Click to expand...
Click to collapse
The ota has a bunch of checks in it. If anything fails the checks, ota fails. When you root, there are system changes, boot.img changes, etc. All of which cause the ota to fail. Of course lineage and cm didn't have such strict checks in their update zips because they expect us to root and modify system. Manufacturers do not.