Related
So I've tried to root my xiaomi mi 3 running the latest official miui 6, using the update package v23 provided on this thread. http://forum.xda-developers.com/xiaomi-mi-3/general/root-recovery-rom-qa-xiaomi-mi3-wcdma-t2830538
After doing so, the phone did not get root access and furthermore whenever I open updater I get a message "Unfortunately, Updater has stopped". I then tried factory reset in hope that the updater app would return to the previous state. Nothing happened unfortunately and the situation remains the same. I have then decided to download the official build from the website. I renamed it as 'update.zip' placed it on the root of the device and went into the provided xiaomi recovery, clicked update but I got an error. Is there any way to return to the previous state? To make updater work again?
kyczawon said:
So I've tried to root my xiaomi mi 3 running the latest official miui 6, using the update package v23 provided on this thread. http://forum.xda-developers.com/xiaomi-mi-3/general/root-recovery-rom-qa-xiaomi-mi3-wcdma-t2830538
After doing so, the phone did not get root access and furthermore whenever I open updater I get a message "Unfortunately, Updater has stopped". I then tried factory reset in hope that the updater app would return to the previous state. Nothing happened unfortunately and the situation remains the same. I have then decided to download the official build from the website. I renamed it as 'update.zip' placed it on the root of the device and went into the provided xiaomi recovery, clicked update but I got an error. Is there any way to return to the previous state? To make updater work again?
Click to expand...
Click to collapse
Why did you used a file of MIUI5 V23 for MIUI6?
What error are you getting in recovery?
You can try to flash fastboot ROM that will reinstall the ROM and repair config files. Use the one according to your device.
http://en.miui.com/thread-14641-1-1.html
mchauhan said:
Why did you used a file of MIUI5 V23 for MIUI6?
What error are you getting in recovery?
You can try to flash fastboot ROM that will reinstall the ROM and repair config files. Use the one according to your device.
http://en.miui.com/thread-14641-1-1.html
Click to expand...
Click to collapse
I flashed it because I asked in an another thread if it will work, and someone said it will... In the recovery I get a message like this
'Install Update.zip Failed
Error applying update'
Do you think I should use this tutorial for fastboot flashing? http://en.miui.com/thread-11047-1-1.html
Do I lose my warranty by peforming flashing through fastboot? How should I root the device afterwards? Should I flash the developers version?
Sent from my MI 3W using Tapatalk
kyczawon said:
I flashed it because I asked in an another thread if it will work, and someone said it will... In the recovery I get a message like this
'Install Update.zip Failed
Error applying update'
Do you think I should use this tutorial for fastboot flashing? http://en.miui.com/thread-11047-1-1.html
Do I lose my warranty by peforming flashing through fastboot? How should I root the device afterwards? Should I flash the developers version?
Sent from my MI 3W using Tapatalk
Click to expand...
Click to collapse
You will not loose warranty for applying MIUI ROM in fastboot. However before that you should check if you have downloaded correct full ROM zip file and the zip is not corrupted. You can try extracting it and if throws any error than it is corrupted. If the zip is ok and updating through recovery does not work than fastboot seems to be only option.
There are fastboot ROMs available for stable build of MIUI6 as well.
For Root you can try this.
http://en.miui.com/forum.php?mod=viewthread&tid=52192&extra=&highlight=root+for+miui+6&page=1
If that does not work, provide me with the build.prop file from the ROM zip you have downloaded I will try to make a root file for you.
Which current version of android do u guys have?
I have moto g (2014) 2nd gen [XT-1068 model] and Android 5.0.2 on it. When I go to system updates it shows:
"New system software avaliable!"
New version: 22.56.3.en.DE
When I try to update it stops on halfway it after boot I get the message something like: Software update unsuccessful no changes were made."
Yes, my device is rooted via KingRoot and interesting is that when I try to find updates via USB cable and Motorola device manager. Device Manager says that there are no updates found. *WHAT?*
I managed to remove root permission (unroot) but the update always fail.
hrc3000 said:
Which current version of android do u guys have?
I have moto g (2014) 2nd gen [XT-1068 model] and Android 5.0.2 on it. When I go to system updates it shows:
"New system software avaliable!"
New version: 22.56.3.en.DE
When I try to update it stops on halfway it after boot I get the message something like: Software update unsuccessful no changes were made."
Yes, my device is rooted via KingRoot and interesting is that when I try to find updates via USB cable and Motorola device manager. Device Manager says that there are no updates found. *WHAT?*
I managed to remove root permission (unroot) but the update always fail.
Click to expand...
Click to collapse
Don't use kingroot. It's a risky method and nobody really knows what it does (except searching for exploits). It may change things in your system that are not reversible.
To root the Moto G 2014 unlock bl, flash twrp and then flash latest superSU or use chainfires autoroot. These are the only solid methods.
Sent with somewhat
Wolfcity said:
Don't use kingroot. It's a risky method and nobody really knows what it does (except searching for exploits). It may change things in your system that are not reversible.
To root the Moto G 2014 unlock bl, flash twrp and then flash latest superSU or use chainfires autoroot. These are the only solid methods.
Sent with somewhat
Click to expand...
Click to collapse
But, umm how can I update to latest android or should I say, am I able to uptade it on higher version than 5.0.2?
you can try it with this tool
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I have the same issue. I have downloaded update and and let it install. when it reboot to install the update it reboot in to twrp and gives an error in the log; after I normally reboot through twrp the phone turn up and after a while it reboot in to twrp show to fix this?
if you use ota update(stock-rom) you need STOCK RECOVERY.
twrp doesn't work because its a custom recovery
Gesendet von meinem Moto G 2014
Same problem here. Moto G 2014 XT1068, rooted and no twrp. The update in recovery makes it till halfway, then it shows an error and Andy with a red exclamation mark and the phone reboots. After that, MOTOROLA OTA shows a message that something went wrong and no change has been made.
Got the update message, let it install without knowing it would brick with TWRP.
Now I got a automatic boot into TRWP, I choose reboot to system, it goes pass the lock screen and then.... automatically reboots into TRWP again. I'm in a loop, what do to? Would like some help please. Would a wipe as a last resort solve this problem?
update: I decided to restore a rom backup using TWRP, no more official updates for me unless there's another way of doing it correctly.
What a joke... 3 months to release a security update... Android 6 only next year... Update fails apparently because the phone is rooted... Thank god nexus 5x has come out, bye bye motorola
unroot your phone and make sure that you are using stock recovery.
I did exactly the same mistake today.
My solution was to flash SuperSU in recovery, delete cache and dalvik and reboot the phone. The phone reverted the update and everything looks fine for now. Now it prompts me again for the ota update.
RobaL4 said:
I did exactly the same mistake today.
My solution was to flash SuperSU in recovery, delete cache and dalvik and reboot the phone. The phone reverted the update and everything looks fine for now. Now it prompts me again for the ota update.
Click to expand...
Click to collapse
You could use the SuperSU app and do a full unroot using the app, do the update and reflash SuperSU.
Sent from my SM-T530NU using Tapatalk
daywalk3r666 said:
if you use ota update(stock-rom) you need STOCK RECOVERY.
twrp doesn't work because its a custom recovery
Gesendet von meinem Moto G 2014
Click to expand...
Click to collapse
Will it be different if I try to install it via motorola update manager in PC?
How do I go back to stock recovery?
no its the same.
you must flash the stock firmware for your device
Tel864 said:
You could use the SuperSU app and do a full unroot using the app, do the update and reflash SuperSU.
Sent from my SM-T530NU using Tapatalk
Click to expand...
Click to collapse
And this way you don't need to flash a stock recovery?!
svendsvin said:
And this way you don't need to flash a stock recovery?!
Click to expand...
Click to collapse
No, that's only if you have rooted stock. If you're on a custom recovery you'll need to flash stock.
But I do have custom recovery I have only rooted it with KingRoot.
So if I want OTA update I have to do this:
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
EDIT: Bruh it's works as a charm. I've flashed stock rom and OTA update passed.
Thnx guys.
I received the notification OTA update for stagefright patch few days ago, I downloaded, but when the device reboots the installation fails. The system version is: 22.21.28.titan_retaildsds.retaildsdsall.en.03 reteu. The build number is LXB 22.46.28. I had a chat with a Motorola techcinian two days ago and he informed me that my phone is rooted and that’s is the reason that I cannot get the update.!!! This is really strange, because I NEVER try to unlock the bootloader. My phone is not rooted . The indication in fastboot mode shows 0.
kompostas said:
I received the notification OTA update for stagefright patch few days ago, I downloaded, but when the device reboots the installation fails. The system version is: 22.21.28.titan_retaildsds.retaildsdsall.en.03 reteu. The build number is LXB 22.46.28. I had a chat with a Motorola techcinian two days ago and he informed me that my phone is rooted and that’s is the reason that I cannot get the update.!!! This is really strange, because I NEVER try to unlock the bootloader. My phone is not rooted . The indication in fastboot mode shows 0.
Click to expand...
Click to collapse
Just do what i did. From previous post.
Question: OP, did you UNROOT the device and then flash the update via fastboot, or not?
And, one more thing: Did it wipe everything on your phone? I read the readme file and it says that it does not, but I find it strange to flash the rom from scrath and keep your files, apps etc untouched.
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
What version of SuperSU are you using? Older versions will cause you to get stuck on the boot animation.
Try v2.79. It should reboot once or twice during first boot after flashing.
Alternatively, you can also root by flashing Magisk v11.1.
sguy156 said:
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
Click to expand...
Click to collapse
First, reflash OS to get a stable starting point. Then use the unofficial beta release of twrp to flash. I have heard of success with a fork ( blu something) but basically he merged the same patches.
Check the dm-verity thread for more details
Sent from my ONEPLUS A3000 using Tapatalk
sguy156 said:
Tried to root OP3T with 7.0 . Not sure what happened but the phone is stuck in bootloop.
What do I need to do to get rid of boot loop ? Do I need different version of SU which works with 7.0 ?
Click to expand...
Click to collapse
Follow this guide:
https://www.youtube.com/watch?v=wwd31NU7VC0&t=4s
I used SU version 2.79 and how do I get rid of this boot screen now. Video is using same version of SU I used which caused bootloop.
Is there another version of SU which doesn't cause bootloop ?
sguy156 said:
I used SU version 2.79 and how do I get rid of this boot screen now. Video is using same version of SU I used which caused bootloop.
Is there another version of SU which doesn't cause bootloop ?
Click to expand...
Click to collapse
U can't get rid of this msg.
Navi44 said:
U can't get rid of this msg.
Click to expand...
Click to collapse
He can, by doing as it says. To keep root, Use a SYSTEM version of SuperSU then relock the bootloader. This wipes data but SuperSU is then part of the OS so will survive the lock. Obviously, all user data gets wiped In the process.
damiensturdy said:
He can, by doing as it says. To keep root, Use a SYSTEM version of SuperSU then relock the bootloader. This wipes data but SuperSU is then part of the OS so will survive the lock. Obviously, all user data gets wiped In the process.
Click to expand...
Click to collapse
Have you tried that personally?
Which version of SU is the system version 2.79 ? First thing is to get the phone to boot first
Navi44 said:
Have you tried that personally?
Click to expand...
Click to collapse
I did this with OxygenOS 3.5.(4?) in order to pass safetynet before the bootloader patched kernels were created.
damiensturdy said:
I did this with OxygenOS 3.5.(4?) in order to pass safetynet before the bootloader patched kernels were created.
Click to expand...
Click to collapse
Thank you for telling this.
This was a normal thing in rn3 thread.
Where even we flashed roms with locked bootloader. And whatever we can do through recovery we did with locked bootloader.
Didn't try it here though.
So after rooting 7.0 I can then lock the phone and rooting will still work. Not sure how will that happen as phone will be wiped
sguy156 said:
So after rooting 7.0 I can then lock the phone and rooting will still work. Not sure how will that happen as phone will be wiped
Click to expand...
Click to collapse
Someone said to use system root.
And then lock the bootloader. Since the su is in system, it won't be wiped.
Haven't tried it but should work THEORETICALLY
What exactly is system root is that a flashable zip or regular SU in rom when rom gets rooted .
sguy156 said:
What exactly is system root is that a flashable zip or regular SU in rom when rom gets rooted .
Click to expand...
Click to collapse
Regular su.
Earlier su used to be system root.
The systemless root started quite recently.
So do I need to use seamless root or SU for 7.0
On using systemless root it will be deleted when you lock bootloader.
You need to use system root for naught
Keep in mind that if you update OOS after locking the bootloader,you'll lose root. Afterwards, you'll have to unlocked the bootloader again - and wiping your device in the process - to reroot.
Hi everyone,
Just taking my chances if anyone in here encountered the same issue. I'm currently on EVA-L19C636B381 and the System Updater is asking me to update to B390. However, I've tried downloading the update several times but keep on getting the "Software Install Failed" error message. Any ideas on how I can update the firmware and ensure that updates will be installed seamlessly moving forward?
Note that the bootloader was unlocked before and it used to have TWRP. Now I've relocked the bootloader and installed the stock recovery.
Thanks!
Clarification:
Version: EVA-L19C636B381 (everything's stock: BOOT, RECOVERY, RECOVERY2, SYSTEM)
Would like to update to: B390
Issue: Getting "Software install failed" error message after downloading through System Update
** Used to have TWRP and root. Flashed stock IMGs
Update:
Issue solved! Please see last post for the update/solution.
thedarkinvader said:
Hi everyone,
Just taking my chances if anyone in here encountered the same issue. I'm currently on EVA-L19C636B381 and the System Updater is asking me to update to B390. However, I've tried downloading the update several times but keep on getting the "Software Install Failed" error message. Any ideas on how I can update the firmware and ensure that updates will be installed seamlessly moving forward?
Note that the bootloader was unlocked before and it used to have TWRP. Now I've relocked the bootloader and installed the stock recovery.
Thanks!
Click to expand...
Click to collapse
If you had TWRP, maybe you also rooted - root will also block OTA (you had to unroot in that case).
Btw, unlocked bootloader does not prevent/affect OTA
zgfg said:
If you had TWRP, maybe you also rooted - root will also block OTA (you had to unroot in that case).
Btw, unlocked bootloader does not prevent/affect OTA
Click to expand...
Click to collapse
Hi zgfg!
Thanks for the response. Yeah, if I'm not mistaken, it used to be rooted. However, I've installed stock B381 and stock recovery already, and still getting the error message. Checked with Root Checker and it says that there's no root access.
thedarkinvader said:
Hi zgfg!
Thanks for the response. Yeah, if I'm not mistaken, it used to be rooted. However, I've installed stock B381 and stock recovery already, and still getting the error message. Checked with Root Checker and it says that there's no root access.
Click to expand...
Click to collapse
Rooting affects Boot partition, it must be flashed back to stock. And it's recommended to Hard reset then, before OTA. For OTA, go to Settings, and choose Full upgrade
zgfg said:
Rooting affects Boot partition, it must be flashed back to stock. And it's recommended to Hard reset then, before OTA. For OTA, go to Settings, and choose Full upgrade
Click to expand...
Click to collapse
Yeah, that's what I did. Basically, everything's stock already. That's why I don't understand why I'm still getting the error message.
You can try downloading the full stock rom package and manually update with the dload method.
noalt said:
You can try downloading the full stock rom package and manually update with the dload method.
Click to expand...
Click to collapse
Hi noalt! Thanks for the response.
Yeah, kinda wondering if that'll work. For the dload method, does it really require an SD card? Also, for the dload method, it is okay to get the latest full package instead? (Upon checking using Firmware Finder, the latest one is B395 or B396)
Any steps that I can follow to do a sort of "clean install"? As in free of any modifications? In short, some kind of steps as alternative for using System Update (which I can't use due to the error message I'm getting)?
You can use any stock rom you like. If it is the same or higher build, you may not need to do a rollback. The dload method only works from sd-card. It will be a clean install.
I think the dload method is the safest. Alternatives are flashing images indiviually through fastboot but I have no experience with that, except for the recovery.img
noalt said:
You can use any stock rom you like. If it is the same or higher build, you may not need to do a rollback. The dload method only works from sd-card. It will be a clean install.
I think the dload method is the safest. Alternatives are flashing images indiviually through fastboot but I have no experience with that, except for the recovery.img
Click to expand...
Click to collapse
I see. Regarding the dload method, if by sd-card you're referring to the internal memory, I'm afraid I've tried that (creating a dload folder and putting nothing else but the UPDATE.APP file inside) and I'm getting a Software Install Failed error message as well. :crying:
No, I mean a micro sd card. You can put one in the tray next to your sim card. And then you have to shut down you phone and boot it holding vol+ vol- and power until you get into the updater.
noalt said:
No, I mean a micro sd card. You can put one in the tray next to your sim card. And then you have to shut down you phone and boot it holding vol+ vol- and power until you get into the updater.
Click to expand...
Click to collapse
Ah yes, that's the one that I have yet to try (as I don't have an SD card, the other spare phone that I have is a 5s).
UPDATE:
I eventually was able to install EVA-L19C363B395!
Initially, I was having issues with the partitions (as I tinkered around a bit with TWRP) and was stuck with the Huawei logo and not proceeding with the booting. So what I did was I flashed BOOT.img, SYSTEM.img, RECOVERY.img, and RECOVERY2.img from the stock B381 (use the Huawei Update Extractor to get it from the UPDATE.APP file from the update.zip (the large file), do some Googling to find it here in XDA . Then I was still experiencing the said issue so I used the stock recovery's features: "Wipe data/factory reset" and "Wipe cache partition" to sort of repair the issues with the partitions (didn't know how to properly do it in TWRP.
Then B381 booted and was able to access USB debugging (initially had issues with this as well, after flashing images, Settings app kept on crashing when trying to access Security and Developer options).
And then finally followed the HWOTA procedure made by @Atarii. Make sure that you're going to use the proper recovery file for your version (L09, L19, etc). According to the steps, being rooted is also required so I used @zgfg's SuperSU 2.82 permissive (https://mega.nz/#F!w41RmZKB!IG53JadhjUKgFK8anbctIw). Make sure to flash it before flashing the nocheck recovery file.
And voila! That should do it. Based on what I'm seeing, root has been removed after doing the HWOTA procedure, same goes for TWRP, and bootloader's locked again.
Thanks to all of those who responded and credit goes to @Atarii and @zgfg for the procedure and file/link.
Why does it always say 'only official binaries are allowed to be flashed' after rebooting my rooted note 8(n950f/ds)
After installing twrp recovery and flashing magisk, rebooting the phone would always result in a bootloop with the error message (only official binaries are allowed to be flashed)
any solutions for this?
creastwell95 said:
Why does it always say 'only official binaries are allowed to be flashed' after rebooting my rooted note 8(n950f/ds)
After installing twrp recovery and flashing magisk, rebooting the phone would always result in a bootloop with the error message (only official binaries are allowed to be flashed)
any solutions for this?
Click to expand...
Click to collapse
You HAVE to delete "securitylogagent" in system/app on the first boot after flashing TWRP.
stonedpsycho said:
You HAVE to delete "securitylogagent" in system/app on the first boot after flashing TWRP.
Click to expand...
Click to collapse
I had the same problem, even after flashing the rmm fix. after wanting to install a module finish on reboot and flashing stock ROM. I believe that the rmm fix should always be used after installing something.
I do not think that deleting the security log agent makes a difference, that's why the Samsung root removal fix is anyway
cogelindo said:
I had the same problem, even after flashing the rmm fix. after wanting to install a module finish on reboot and flashing stock ROM. I believe that the rmm fix should always be used after installing something.
I do not think that deleting the security log agent makes a difference, that's why the Samsung root removal fix is anyway
Click to expand...
Click to collapse
Use this zip instead. You can get it link on dr.ketan' rooting guides
anwar amu said:
Use this zip instead. You can get it link on dr.ketan' rooting guides
Click to expand...
Click to collapse
Yes thank you, I have had it for a while and I already used it, but I still distrust having to restart for some reason. If I have to do it I turn it off and go to the recovery to flash that zip before restarting. The problem of official binaries has already happened to me before, and it is very uncomfortable ...