Related
I have a Nexus 6, Marshmallow (Build MMB29K). I rooted it using the NRT which installed SuperSU version v2.46. Apparently from the NRT dialogs, the last step of rooting is configuring SuperSU properly.
I get a message that I must update to the latest binaries; but every attempt fails.
I am new at this. Can someone please help?
m_albert69 said:
I have a Nexus 6, Marshmallow (Build MMB29K). I rooted it using the NRT which installed SuperSU version v2.46. Apparently from the NRT dialogs, the last step of rooting is configuring SuperSU properly.
I get a message that I must update to the latest binaries; but every attempt fails.
I am new at this. Can someone please help?
Click to expand...
Click to collapse
stop using toolkits, do it the freaking right way. its MUCH easier the right way. use google, search for the latest supersu, download it, flash it in twrp recovery, then reboot. btw, the toolkits version is VERY old. and you trust the toolkit?
---------- Post added at 09:38 PM ---------- Previous post was at 09:04 PM ----------
latest btw http://download.chainfire.eu/752/SuperSU/BETA-SuperSU-v2.65-20151226141550.zip
simms22 said:
stop using toolkits, do it the freaking right way. its MUCH easier the right way. use google, search for the latest supersu, download it, flash it in twrp recovery, then reboot. btw, the toolkits version is VERY old. and you trust the toolkit?
---------- Post added at 09:38 PM ---------- Previous post was at 09:04 PM ----------
latest btw ...
Click to expand...
Click to collapse
Thank you for the info. Your link fixed it. But please, go a bit easier on me. I'm new to all this.
simms22 said:
.....btw, the toolkits version is VERY old. and you trust the toolkit?
Click to expand...
Click to collapse
lies, all lies.
wug just updated it last week to work on froyo
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
yea simms, take it ez on the noobs geez, not everyone knows it all like you
bweN diorD said:
lies, all lies.
wug just updated it last week to work on froyo
Click to expand...
Click to collapse
I THINK the problem was that TWRP asked if I wanted to install ITS version of SuperSU. I wasn't supposed to allow that; but I did.
EDIT: When I'm nervous, I tend not to read everything carefully.
m_albert69 said:
I THINK the problem was that TWRP asked if I wanted to install ITS version of SuperSU. I wasn't supposed to allow that; but I did.
Click to expand...
Click to collapse
yea, you dont want to do that ever.
bweN diorD said:
yea, you dont want to do that ever.
Click to expand...
Click to collapse
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.
m_albert69 said:
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.
Click to expand...
Click to collapse
another thing, im thinking you should have been using su zip 2.52 also, not 2.4whatever. i could be mistaken, but i always use 2.5*.
---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------
m_albert69 said:
I'm sure that's what happened. I thought it was weird that I had to "swipe to install" twice.
Click to expand...
Click to collapse
i just noticed simms linked you to 2.65, i wouldnt recommend you use that unless you need it, its systemless and still working out the kinks.
Looking back on my NRT logs, it DID install 2.64. But as I said, during the TWRP recovery I nervously allowed it to do everything it asked of me. That included installing its own version of SuperSU, which must have immediately overwritten NRT's version.
m_albert69 said:
Looking back on my NRT logs, it DID install 2.64. But as I said, during the TWRP recovery I nervously allowed it to do everything it asked of me. That included installing its own version of SuperSU, which must have immediately overwritten NRT's version.
Click to expand...
Click to collapse
actually it more likely made some sort of conflict. 2.64 installs in the kernel, twrp put it in the system, but in all the years i have had a smart phone, i have never used twrps root once.
m_albert69 said:
Thank you for the info. Your link fixed it. But please, go a bit easier on me. I'm new to all this.
Click to expand...
Click to collapse
im sorry for sounding/being so rough on you.. really i am. but stuff like flashing supersu is part of the most very basic knowledge needed. and i mean very basic. i was just trying to get that point across. im normally an extremely nice person :angel:
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
bweN diorD said:
actually it more likely made some sort of conflict. 2.64 installs in the kernel, twrp put it in the system, but in all the years i have had a smart phone, i have never used twrps root once.
Click to expand...
Click to collapse
twrps root, never. its always a very old version, so stay away :good:
Hi
i recently had this problem and overcome it by doing the following
open up settings > click on applications > Application Manager > scroll across to all > scroll down to Supersu and click it (should come up with application info) > click remove installed updates
once that is completed i rebooted (may not be need but better to be safe) the opened up supersu again, and installed the binary with the normal procedure and all updated ok
this was done on my Samsung Galaxy S6 Edge running 3.10.61-S6_UniBase_BOG8_v2, Android Version 5.1.1
i hope this helps someone
regards
Dennis
got the ota today on my phone. is it Marshmellow?
Got it earlier this week.
No, it is not Marshmallow. Marshmallow should be version 6.
Was this question rhetorical? The details are listed in the release notes.
There's some radio related firmware in there for anyone interested. Sometimes that's helpful for people with radio issues.
---------- Post added at 12:07 PM ---------- Previous post was at 12:04 PM ----------
It'd be nice if there was a method to upgrade modem firmware without needing the entire update.zip. That was certainly always a pro with Samsung devices. Odin was nice but Chainfire's Mobile Odin was noice.
Hello, looking for help.
My daughters Ze551kl had an ota update error resulting in a true cyclic bootloop from asus bootup screen to op system which reboots in about 1 second after flashing the op system background.
I cant unlock the bootlock. No operating system access.
I tried to restore with adb sideload and i get response on a pc and the phone that it installs ok, but the bootloop remains. I put 1531 on via adb and i did get the correct files from asus. I have done this several times. No change.
I can't flash because the bootloader is locked and i cant find an adb bootloader level unlock. Does this exist?
What do you folks recommend?
I cannot install twrp or do flashing of recovery. I can get to fastboot and the recovery options. I have cleared the cashes.
Thanks for any advice.
---------- Post added at 11:32 AM ---------- Previous post was at 11:16 AM ----------
Hello, almost forgot, do i need to unlock the bootloader?
If the abd transfer has worked and installed the new version, but the bootloop remains, what else can be done? Is this a partition or hardware problem that showed itself during the update process?
You may have bricked it. Personally, I'd send it to Asus, if it's still in warranty, and let them fixit.
Currently on version 8.1.0 at patch level Nov 5 2018.
Any idea how to resolve ?
Is it possible they removed the update from the server?
kalda01 said:
Currently on version 8.1.0 at patch level Nov 5 2018.
Any idea how to resolve ?
Is it possible they removed the update from the server?
Click to expand...
Click to collapse
Hi!, I have the same problem here. I got yesterday my mi a2 and can't update to android pie, I'm in the same patch that you are.
hi the same thing has happened with me. received my red mia2 4/64 today but with 8.1 and nov 5 2018 security patch. i am on a strong wifi network but still no updates visible. tried flashing recent rom from mi website but i get the error flash error mismatching image and device.
i am out of ideas now.
Intersting to point out, that about a month ago we bought another MI A2 from same dealer (different color) and it was already running version 9 and not 8.1.
kalda01 said:
Intersting to point out, that about a month ago we bought another MI A2 from same dealer (different color) and it was already running version 9 and not 8.1.
Click to expand...
Click to collapse
Sounds like your dealer is Dodgy
solved
simply download the files from given link. they are edited bat and sh files to fix mismatch error which you might receive as i did while flashing the stock image.
i faced a similar situation today. mi mia2 red didn't receive any update since 8.1 nov 5 2018. so had to flash stock rom.
extract copy paste and overwrite.
so icant post links as i am less than 10 postshere . so looking for workaround
---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------
heartbreak1o1 said:
hi the same thing has happened with me. received my red mia2 4/64 today but with 8.1 and nov 5 2018 security patch. i am on a strong wifi network but still no updates visible. tried flashing recent rom from mi website but i get the error flash error mismatching image and device.
i am out of ideas now.
Click to expand...
Click to collapse
this was me. from guest account so i will dm you the link for the edited batch and sh files. also my device has now received september 2019 security update. so everything good.
ass wipe said:
simply download the files from given link. they are edited bat and sh files to fix mismatch error which you might receive as i did while flashing the stock image.
i faced a similar situation today. mi mia2 red didn't receive any update since 8.1 nov 5 2018. so had to flash stock rom.
extract copy paste and overwrite.
so icant post links as i am less than 10 postshere . so looking for workaround
---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------
this was me. from guest account so i will dm you the link for the edited batch and sh files. also my device has now received september 2019 security update. so everything good.
Click to expand...
Click to collapse
What given link are you referring to ?
ass wipe said:
simply download the files from given link. they are edited bat and sh files to fix mismatch error which you might receive as i did while flashing the stock image.
i faced a similar situation today. mi mia2 red didn't receive any update since 8.1 nov 5 2018. so had to flash stock rom.
extract copy paste and overwrite.
so icant post links as i am less than 10 postshere . so looking for workaround
---------- Post added at 05:21 PM ---------- Previous post was at 05:19 PM ----------
this was me. from guest account so i will dm you the link for the edited batch and sh files. also my device has now received september 2019 security update. so everything good.
Click to expand...
Click to collapse
Did you updated to android 9 with a full rom downloaded from the xiaomi site?
aeonoak said:
Did you updated to android 9 with a full rom downloaded from the xiaomi site?
Click to expand...
Click to collapse
yes. and everything works normally now
ass wipe said:
yes. and everything works normally now
Click to expand...
Click to collapse
can you explain and send a PM with the link used?
experience this yesterday, probably this corresponds in Xiaomi server. Maybe they take down the patch after November 2018. You can download the official stock Pie version at MIUI website.
Updaing to PIE was successfull.
Used this guide to unlock bootloader: https://www.androidexplained.com/mi-...ck-bootloader/
Then used the MI FLASH tool to apply the stock rom. First atemp failed with "write error" after 55 seconds, but I tried a second time and this time the process completed.
kalda01 said:
Updaing to PIE was successfull.
Used this guide to unlock bootloader: https://www.androidexplained.com/mi-...ck-bootloader/
Then used the MI FLASH tool to apply the stock rom. First atemp failed with "write error" after 55 seconds, but I tried a second time and this time the process completed.
Click to expand...
Click to collapse
Your link is broken
aeonoak said:
Your link is broken
Click to expand...
Click to collapse
https://www.androidexplained.com/mi-a2-unlock-bootloader/
kalda01 said:
Updaing to PIE was successfull.
Used this guide to unlock bootloader: https://www.androidexplained.com/mi-...ck-bootloader/
Then used the MI FLASH tool to apply the stock rom. First atemp failed with "write error" after 55 seconds, but I tried a second time and this time the process completed.
Click to expand...
Click to collapse
One more info, can you share the link of the ROM used to flash with the MI FLASH?
I have the same issue with OTA updates. I went back to stock (V10.0.8.0.PDIMIXM) from that thread:
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
And I wanted to check if OTA is working, but it says there are no updates available.
I did it before and everything was working fine.
Yaroray said:
I have the same issue with OTA updates. I went back to stock (V10.0.8.0.PDIMIXM) from that thread:
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
And I wanted to check if OTA is working, but it says there are no updates available.
I did it before and everything was working fine.
Click to expand...
Click to collapse
Tried to update using mi flash tool to the V10.0.13.0.PDIMIXM?
aeonoak said:
Tried to update using mi flash tool to the V10.0.13.0.PDIMIXM?
Click to expand...
Click to collapse
I will do it if there will be no other option. Didn't try yet, because my intention was to check of OTA updates will be working for the further updates.
If I will update in this way I will not get any info about next updates if OTA will not be working.
Yaroray said:
I will do it if there will be no other option. Didn't try yet, because my intention was to check of OTA updates will be working for the further updates.
If I will update in this way I will not get any info about next updates if OTA will not be working.
Click to expand...
Click to collapse
I'm in the same boat.
---------- Post added at 10:09 AM ---------- Previous post was at 10:07 AM ----------
Yaroray said:
I will do it if there will be no other option. Didn't try yet, because my intention was to check of OTA updates will be working for the further updates.
If I will update in this way I will not get any info about next updates if OTA will not be working.
Click to expand...
Click to collapse
Yesterday I tried to write a stock PIE rom on my phone but I got some erros. I'm afraid of brick a new phone trying this.
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
@Yaroray do you know how to check this?
Check that the partition structure is A/B dual type, use fastboot commands.
Click to expand...
Click to collapse
Ok, I updated using this file: https://bigota.d.miui.com/V10.0.13....0.PDIMIXM_20190807.0000.00_9.0_9083804c9e.tgz
And this tool: download.appmifile.com/images/2019/07/01/09cdc3a7-5a11-42aa-81f4-be27fe12ce80.msi
Unlocked the bootloader with "fastboot flashing unlock_critical"
After the update (I have no error using the process) I received an OTA security update from setember 5, 2019 that installed without problem too.
Hey guys, finally motorola pushed new system upgrade i.e Android 10 to moto one power users. Go and upgrade your phone.
Yes it is available. Huraaay
imjhachandan said:
Hey guys, finally motorola pushed new system upgrade i.e Android 10 to moto one power users. Go and upgrade your phone.
Click to expand...
Click to collapse
Yes you are right. Stable version of Android 10(with December security patch) for MOP has been released.
https://piunikaweb.com/2019/12/11/motorola-one-power-android-10/
Everyone will get Android 10 by January 10(i.e. with in a month.)
Bro on paper yes it's stable but technically/practically it's not as it still contain many bugs which needs yo be fixed ASAP soo please guys use feedback to report......
Anyone who wants the ota file for manual installation can pm me. Currently uploading..
Edit: File uploaded
reddevil08 said:
Anyone who wants the ota file for manual installation can pm me. Currently uploading..
Edit: File uploaded
Click to expand...
Click to collapse
could you please share the link of the OTA
[email protected] said:
could you please share the link of the OTA
Click to expand...
Click to collapse
PM
Here's the link for the OTA file. It's a patch file and not the full ROM, so please be sure that you are already on November security patch without any modifications (I have a bootloader locked device as Motorola voids warranty after bootloader unlock. So people with unlocked/rooted devices should wait for the full ROM or they can try their luck at their own risk)
https://mega.nz/#!k58AGSbD!ePccyYgFiyhWVKFBUw2SUIFVcpYrAK8qvn9M2rv0zXc
Prerequisites: 100% Stock ROM with no system modifications of any kind. This file is only for the Indian variant of the Motorola One Power. You should already have installed the Android Pie November security patch update from Motorola before installing this update.
1. Download from link and move it to root of your internal storage(not in any folder like Downloads etc). Put it outside all folders.
2. Go to Settings>Apps¬ifications>Show all apps>3dot menu(top right of the screen)>show system apps
3. Find Motorola Update Services and give it storage permission.
4. Go to Updates screen and check for update. It will show up. Install as any normal OTA.
I've used the same file to upgrade my own device and a few others who got the file over PM. No one reported any issues with the update.
Disclaimer: I'm not responsible for anything you install on your device. Use at your own risk.
Thank you for the link!
---------- Post added at 12:08 PM ---------- Previous post was at 12:04 PM ----------
ashishmishra said:
Bro on paper yes it's stable but technically/practically it's not as it still contain many bugs which needs yo be fixed ASAP soo please guys use feedback to report......
Click to expand...
Click to collapse
Do you see any known issues/bugs?
Sundar247 said:
Thank you for the link!
---------- Post added at 12:08 PM ---------- Previous post was at 12:04 PM ----------
Do you see any known issues/bugs?
Click to expand...
Click to collapse
Yes found many also reported almost all let's see if they fix this
reddevil08 said:
Here's the link for the OTA file. It's a patch file and not the full ROM, so please be sure that you are already on November security patch without any modifications (I have a bootloader locked device as Motorola voids warranty after bootloader unlock. So people with unlocked/rooted devices should wait for the full ROM or they can try their luck at their own risk)
https://mega.nz/#!k58AGSbD!ePccyYgFiyhWVKFBUw2SUIFVcpYrAK8qvn9M2rv0zXc
Prerequisites: 100% Stock ROM with no system modifications of any kind. This file is only for the Indian variant of the Motorola One Power. You should already have installed the Android Pie November security patch update from Motorola before installing this update.
1. Download from link and move it to root of your internal storage(not in any folder like Downloads etc). Put it outside all folders.
2. Go to Settings>Apps¬ifications>Show all apps>3dot menu(top right of the screen)>show system apps
3. Find Motorola Update Services and give it storage permission.
4. Go to Updates screen and check for update. It will show up. Install as any normal OTA.
I've used the same file to upgrade my own device and a few others who got the file over PM. No one reported any issues with the update.
Disclaimer: I'm not responsible for anything you install on your device. Use at your own risk.
Click to expand...
Click to collapse
Thanks for the link, wondering if this will work on an unlocked Moto P30 Note? On P30 note I flash everything from latest full ROM except those files: bootloader.img, BTFM.bin, fsg.mbn, gpt.bin, NON-HLOS.bin.
lanyao1920 said:
Thanks for the link, wondering if this will work on an unlocked Moto P30 Note? On P30 note I flash everything from latest full ROM except those files: bootloader.img, BTFM.bin, fsg.mbn, gpt.bin, NON-HLOS.bin.
Click to expand...
Click to collapse
I wouldn't recommend using this file in that case. I have used it in a bootloader locked Indian moto one power without any problems.
You should wait for the full ROM as this is just the patch file. Shouldn't be too long.
Yes !! There are some bugs and issue, but nice one i got some new features atleast
Thanks reddevil for sharing the link of that ota file
i rooted my device using magisk. now everytime i uninstall magisk my phone ends up rebooting to recovery. and the updater wouldnt update to the new build.
i have tried wipe from twrp after restoring my boot image. doesnt seem to work. any help would be appreciated.
Good Morning/Afternoon/Evening/Night. I have compiled an experimental Sky Hawk Recovery Project for the Tab S7+ 5G by literally taking @ianmacd 's TWRP tree and modding it. I did this because TWRP looks a bit boring to me and I personally like SHRP. Also fun fact, I do not own this device but I just want to give back to the community I take and use everything from. Here you will find the download links and instructions:
But before that, here's a warning: I AM A NEWBIE and there is no denying that. So take and use whatever I say with a kilogram of salt. And please please correct me wherever I made a mistake because, you know, I've only started android development literally 2 months ago.
So here is the link: Mega
[Might not boot, might soft-brick your device, I honestly do not know what will happen. So have ODIN and ian's recovery image in tar form handy. Also this is for testing purposes, not "un"official release. And be sure to leave feedback if you tested this.]
Bugs will be the same as ianmacd's one (if it even works)
Installation is as easy as flashing the zip in your TWRP recovery [you should have encryption and all the scary things disabled by following ian's guide HERE
Advantages: I personally think it looks better than TWRP. Also I will add the flashlight feature after I see that the build boots up fine.
[The reason that I am trying to build for tablets first is because I have a problem with tablets. I've built SO MANY Tab S3 recoveries but none of them boot AT ALL. But the 2016 phone I had lying around booted up first try with my self-made device tree].
Mega thanks to,
@ianmacd (because I didn't have to waste a day making a device tree from scratch) [and because I am scared of encrypted devices]
and Ian's device tree: https://github.com/ianmacd/twrp_gts7xl
Stay safe and happy flashing!
Thanks might give it a try at the weekend.
Huntyz said:
Thanks might give it a try at the weekend.
Click to expand...
Click to collapse
Thanks a lot man! Also remember to follow ian's guide fully cuz your tab'll suffer if you don't.
has anybody tried this?
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
just flash. doesnt boot. goes straight to download mode and says,
partition vbmeta
Reason vbmeta: error verifiying vbmeta image: and a code here
CVLover said:
has anybody tried this?
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
just flash. doesnt boot. goes straight to download mode and says,
partition vbmeta
Reason vbmeta: error verifiying vbmeta image: and a code here
Click to expand...
Click to collapse
cuz u havent properly disabled vbmeta.. as post right above urs says, follow twrp guide to the T or ull have problems
Does it work? Let us know. Thank you
I also tried and no success.Just to mention that I had properly disabled vbmeta and it seems problem is somewhere else.