Hey,
So I have a note 9 for work. I needed to install VMware Airwatch so I can access work stuff. It works great. However, Samsung did an update since I installed the work software, and all my (newer) coworkers have Personal and Work profiles. I hate it. I prefer it all in one but our IT says that's a no go due to newer Samsung updates. The reason why mine is set up like it is, is because the software was in my phone before the update.
I have an opportunity to upgrade to an A52. However, if I do it with the android 11 software that came with it - It will separate my phone.
Can I put oreo on this A52 - install the software from work, then upgrade using the "Check for Updates" option in my phone to get back to the latest and greatest?
I am not a specifical phone savvy guy, but I know my way around computers etc. so I just want to make sure it can be done- where to get the ROM for it (are they specific to device?)
Khial said:
Hey,
So I have a note 9 for work. I needed to install VMware Airwatch so I can access work stuff. It works great. However, Samsung did an update since I installed the work software, and all my (newer) coworkers have Personal and Work profiles. I hate it. I prefer it all in one but our IT says that's a no go due to newer Samsung updates. The reason why mine is set up like it is, is because the software was in my phone before the update.
I have an opportunity to upgrade to an A52. However, if I do it with the android 11 software that came with it - It will separate my phone.
Can I put oreo on this A52 - install the software from work, then upgrade using the "Check for Updates" option in my phone to get back to the latest and greatest?
I am not a specifical phone savvy guy, but I know my way around computers etc. so I just want to make sure it can be done- where to get the ROM for it (are they specific to device?)
Click to expand...
Click to collapse
Unfortunately you won't be able to do this.
The ROMs are specific to each model and the A52 came with 11, there's nothing older available.
The version of Android the phone ships with is the oldest software the phone will support. In the case of the A52, it is Android 11.
In short word, You can’t go back officially and you can’t blow up your motherboards like Xiaomi in the process of trying to go back!
{Mod edit: Quoted post has been deleted}
This isn't really the place to be asking this question, please go to the Nokia 6.1 thread on XDA for further help.
That said, from the quick look I've had, it appears to be a complicated process to downgrade to Android 8.
Related
I am trying to relock bootloader in attempt to get Android Pay working. Does anybody know how to do that? I have tried the fastboot oem lock without success. Also have reinstalled stock ROM mutliple times without success either.
Try downgrading the firmware first, then upgrade again using the official process posted on ASUS. This should work with any Lollipop firmware you have installed. By doing that this may downgrade the bootloader, and by updating it to 5.0 again that should re-lock the bootloader.
Even this might be the case, I think even after you do this it could be a waste, because the padfone s firmware doesnt even support taptopay. The only way android pay might work is by having padfone x firmware run. (even that might not work because its old).
I want this to work too, but I think (in my opinion) we should wait a little bit more to see if android AOSP could support that feature or if some person finds away to make it work by going past that safteynet api.
It is also not too long that a representative of google commented on this issue as well, hinting that they acknowledged the problem with this process.
I might as well wait, and plus not even all the stores in my area support this type of payment.
Justatechie said:
Try downgrading the firmware first, then upgrade again using the official process posted on ASUS. This should work with any Lollipop firmware you have installed. By doing that this may downgrade the bootloader, and by updating it to 5.0 again that should re-lock the bootloader.
Even this might be the case, I think even after you do this it could be a waste, because the padfone s firmware doesnt even support taptopay. The only way android pay might work is by having padfone x firmware run. (even that might not work because its old).
I want this to work too, but I think (in my opinion) we should wait a little bit more to see if android AOSP could support that feature or if some person finds away to make it work by going past that safteynet api.
It is also not too long that a representative of google commented on this issue as well, hinting that they acknowledged the problem with this process.
I might as well wait, and plus not even all the stores in my area support this type of payment.
Click to expand...
Click to collapse
Yeah, I reverted back to the X firmware to see if I could get it to work. It got to the option to add a card and just after agreeing to the bank terms, it gave me the error about android not being able to verify if device/software is compatible. I have disabled root and tried using root cloak.
After some reading I found that people were able to get it to work with relocking bootloader. Others said that future patches may fix the issue considering google wallet had the same issues when first released.
daggorlad said:
Yeah, I reverted back to the X firmware to see if I could get it to work. It got to the option to add a card and just after agreeing to the bank terms, it gave me the error about android not being able to verify if device/software is compatible. I have disabled root and tried using root cloak.
After some reading I found that people were able to get it to work with relocking bootloader. Others said that future patches may fix the issue considering google wallet had the same issues when first released.
Click to expand...
Click to collapse
Yes, Im hoping for AOSP support as its one step closer to putting on cyanogenmod, since it stems from that. Then it wouldn't be long for a compromise. Might as well wait.
I took a gamble buying a Chinese phone redmi-note 2 but sadly! it hasn't worked out for me.
All I wanted from it, was for it to do what it is supposed to do.
Bluetooth
Bluetooth doesn't connect to any of my devices, car, Hi-fi and not even my nexus 7!
Miui updater
Totally useless on my phone. This app crashes every time I select "choose update package"
I have looked for help on YouTube but the majority of videos seem to be Indian, using Indian versions of software where the updater app seems to work perfectly.
I managed to root my nexus 7 with ease but the redmi-note 2 is a nightmare.
I could really do with some of you android guru's to point me in the right direction! in finding a good beginners guide to finding all the apps and suitable rom for my phone, Or better still.! A way to get Bluetooth to work.
First of all check if your device has official rom or custom (if you bought it from China it probably has custom rom so flash official one).
Mine is working very good...
I second what ibeqa said - you're probably running a crapware-loaded ROM. Crashing updater is a good hint. You could also look into "about phone" section for the MIUI version, if it's something like 9.99.99 then it's crapware. "Legit" ROMs have version 7.xx.yy or 6.xx.yy. The crapware ROMs are IMHO the main reason why Xiaomi decided to lock the bootloader on RN3 and other newer phones. Because obviously, those ROMs give them bad reputation even though it's not their fault.
Bluetooth works fine for me, but sometimes it hangs up forcing me to restart it - not optimal but doesn't happen too often.
As for rooting, rooting the Nexus 7 (2012) was the same as RN2 for me - connect to PC in fastboot mode, flash recovery.img, reboot to recovery and flash a custom ROM. There are enough guides out there. For the RN2, fastboot can be accessed by starting the phone with the volume down key pressed.
Agree with the above. Please re-flash using official ROM via fastboot method and then try again. See http://en.miui.com/a-234.html
Android version 5.02 LRX22G
MIUI Version 66.77.33.00(LHMCNCH) Stable
Cpu octo core 2.2Ghz
Ram 2GB
I Have downloaded Update supersu 2.4 and miui HMNote2Global v7.2.2.0LHMMIDA_DA_d71ff21b81_5.0.zip are these correct please?
I installed CWM but have read that TWRP is the one I should be using! is that correct?
The trouble with the redmi 2 ,is there is too much conflicting information out there, making it very difficult for a newbie.
Is there any other things that I need to download?
This whole thing has really put me off the Xiaomi brand. I just expected bluetooth to work ! it is supposed to be standardised worldwide.
To you Guys it is probably fun to mess about with different roms, all I wanted was a working phone.
"MIUI Version 66.77.33.00" <- that's your problem right there. You reseller installed a crapware loaded ROM and has modified the version so that you never get an update (= he can spy on you forever), had you bought from another one, you would have gotten a working phone. I know mine did.
Putting blame on Xiaomi for this is misplaced, unless you want to blame them for being dev-friendly and leaving the bootloader unlocked. They reconsidered by now, though, their newer phones are locked.
In any case, yes TWRP is the way to go personally. CWM has cut important features like backup/restore (at least the version shipped with cyanogen roms I tried), so it's basically useless.
For the ROM, if you have downloaded it from the xiaomi page, then yes. You could also get the rom from xiaomi.eu if you want to use an European language.
If you just want official MIUI then you don't need to install custom recovery (use fastboot method instead as per official instructions). In fact the custom recovery will get removed next time you receive an OTA update.
Personally I use TWRP from this link http://en.miui.com/thread-224679-1-1.html because I wanted to install root. But only do this AFTER you install a clean ROM at the first place.
Crim Soukyuu said:
"MIUI Version 66.77.33.00" <- that's your problem right there. You reseller installed a crapware loaded ROM and has modified the version so that you never get an update (= he can spy on you forever), had you bought from another one, you would have gotten a working phone. I know mine did.
Putting blame on Xiaomi for this is misplaced, unless you want to blame them for being dev-friendly and leaving the bootloader unlocked. They reconsidered by now, though, their newer phones are locked.
In any case, yes TWRP is the way to go personally. CWM has cut important features like backup/restore (at least the version shipped with cyanogen roms I tried), so it's basically useless.
For the ROM, if you have downloaded it from the xiaomi page, then yes. You could also get the rom from xiaomi.eu if you want to use an European language.
Click to expand...
Click to collapse
I bought the phone from Gearbest.EU and expected it to be direct from Xiaomi, as I have never had a problem with this company before.
I have had another go at installing a new rom with the Mi suite and also with the miui flash tool and am not getting anywhere with it. I can't even root the damned thing as it boots into Mi when pressing vol up and start. This happened with CWM and TWRP.
I have said before,that I have little experience with android and perhaps I am going wrong somewhere! or the tutorial posters are using phones that have totally different roms to mine. ,It is very difficult when you have Indian,Chinese and global versions with many variations of each, the same seems to apply to CWM and TWRP.
Is there a way to install this via windows, ie formatting the phone and running an installer direct from pc?
I had a dabble with Linux mint and Artist in the past and found them quite user friendly, I can't believe that android is Linux based! I could have done a fresh install of windows, several times by now,the amount of time I have spent on this. Of course windows truly is global with only a couple of variations . Format disk, run and your away. Then hours installing software.
I am fast getting to the stage where I shall give it a bounce test, from a great height. :crying:
I'd like to root my Nougat OS Galaxy S7 Edge G935A, firmware G935AUCU4BQA6.
All I'm looking to do is to disable OS updates and remove bloatware, if I can go back to Marshmallow to do that, that is fine also.
Has anyone rooted the s7 Nougat yet? Or went backwards to a Marshmallow version? What are my options?
Hey, look at that!!!! :cyclops: The people running xda are so great, they put a search bar up for us in the right hand corner of the page!!
Now if you enter your device name there then you'll find...
this thread amongst other things
I didn't see anything for this new OS and don't want to brick my phone. If I can go backwards with those linked instructions I will try. Are you saying that I can go backwards?
I didn't see anything for this new OS and don't want to brick my phone. If I can go backwards with those linked instructions I will try. Are you saying that I can go backwards?
Click to expand...
Click to collapse
I just had another look and noticed that the thread I sent to you yesterday was 8 months old and very experimental. Newer and more stable approaches are available now. Such as this one. Look through the Galaxy S7 Section (edit: corrected link) to find more info on routing your device.
As for your question: I can not give you a specific answer for the Galaxy S7 because I haven't worked with it myself, but generally speaking, if you have an unlocked bootloader, then you can boot a recovery image such as TWRP and with that you can install any OS image that has been made for your device. So if you have an unlocked bootloader, you don't need root to flash a different OS. Plus I've already come accross guides on downgrading from Nougat to Marshmallow on the S7, so it must be possible.
As for not wanting to brick your device: that's understandable - I wouldn't either And if you know what you're doing, don't skip steps, use software that is compatible with your device and has already been tested and verified (i.e. don't be the first to follow a new guide if you haven't done this before and know how to help yourself if things don't work - see that it's worked for several others to make sure ), then it usually won't happen. But you can never be 100% sure, so if possible, you should make a backup of your running system (not just your data) before making any changes to the system or flashing. That's another reason why a recovery image is useful...
May I ask why you want to downgrade?
The only thing I want to do is to disable the OTA OS upgrades and any other upgrades, so that I can selectively choose what I want ... and to get rid of the bloatware.
I'd be happy to do so on Marshmallow or Nougat, it doesn't matter to me which OS.
Ok, to uninstall system apps and make certain system changes, you will need root. Look at the rooting approach provided in my last post, that looks quite reliable.
Hi guys,
I bough a used LG G5 back a couple of days because i have a lot of love for the LG G series. I got the phone after i had a quick look over the phone when i was with the seller and i was very happy about the external look of the phone so i bought it.
I had read that there is an official update for the LG G5 to Oreo so it was a big surprise when i realized that the one i got was still on 6.0.1. What i did was come back to the house, connect to the wifi and try to do a FOTA upgrade. No luck. It said that the phone was already at its latest update available. What i did then was to do a manual upgrade with LG Bridge. All went good and the phone was updated to 7.0. After the first reboot, i got the message "Current version is not available for user....". I didn't bother at the time because i thought that after a factory reset all would be ok. Well that didn't happen . I did notice something strange. The software version i had was referring to "EU" but now it says V20r-OPT2-SI. Perhaps the previous owner had the phone rooted and perhaps that version that it had was not the official EU.
Now the OS is full off bloatware and there isn't an update to Oreo available.
I want to:
- Find the appropriate OS version that my phone should have
- Get rid of the message that appears during the boot
- Get rid (if possible) from the bloatware when the correct OS is loaded
I want to use an official ROM with no root because of company regulations where i work so, rooting might be an issue. If i do have to root, i then have to unroot it again before use.
Because i have been away from the scene for a long time, please excuse my lack of information.
Regards,
If you don't mind loosing VoLTE support for the operators your rom was made for, just delete the /cust/ folder and you'll get rid of both error message and most of the bloatware.
tremalnaik said:
If you don't mind loosing VoLTE support for the operators your rom was made for, just delete the /cust/ folder and you'll get rid of both error message and most of the bloatware.
Click to expand...
Click to collapse
i am a noob, i didnt know this, thanks for the tip
tremalnaik said:
If you don't mind loosing VoLTE support for the operators your rom was made for, just delete the /cust/ folder and you'll get rid of both error message and most of the bloatware.
Click to expand...
Click to collapse
That is indeed a nice tip that i was not aware of but would it be possible to know if i am able to flash a rom carrier independent in order to be able to upgrade afterward to the Oreo? If so, how can i find out the version that i can flash without damaging the phone?
Thanx for the help so far.
You can flash whatever rom you want (of course an H850 one, never try to flash a H830 or H860 ROM on the H850!!!). If you want to upgrade to Oreo having an Open EU stock rom, follow these instructions: https://forum.xda-developers.com/lg-g5/development/stock-h850-30a-eu-rom-flashable-zips-t3850072
If you follow colsely the instructions and charge the phone before proceeding, there's virtually no risk of damage (avoid flashing form a desktop pc in a stormy night, of course).
According to the people on reddit it is because I have debloated my phone. I also tried to install the Pixel Experience Plus custom rom at one point but it didn't work, I did reinstall the stock recovery an relocked the bootloader after that.
I did factory reset it and even flashed it with an ozip file still no update.
also found an ofp file for the Android 11 update but relme flash tool wouldn't work with it.
Is there any other way to manually update it or force it to update?
Thanks in advance.
Do you really want it?
I think it's a bloatware dud.
The "security" is not needed and comes at a stiff price as you will see if you load it.
Scoped storage sucks.
Rule #1, if your OS is running fast, stable and fulfilling its mission... let it be.
You do make a good point.
But if it is possible and I don't like it I can always reverse to Android 10.
At this point I just want to try it out and try the Pixel Experience rom.
If it isn't, well both my phone and I will survive.
thephone.geek said:
You do make a good point.
But if it is possible and I don't like it I can always reverse to Android 10.
At this point I just want to try it out and try the Pixel Experience rom.
If it isn't, well both my phone and I will survive.
Click to expand...
Click to collapse
You can go back... as long as it doesn't update the boot loader version too.
As a Samsung user I'm all too aware of that trick.
I would investigate what advantages R has over Q that would benefit you. Scoped storage isn't fully implemented on Q apparently and seems to run as well maybe better than Pie. In Q it's scoped storage in all it's blazing cpu cycle sucking glory.
Is there anyway to do it using adb?
I got Realme 7 Pro from Amazon Warehouse with somehow broken security - figerprint scanner didn't work and the phone didn't want update itself thru OTA, even with relocked bootloader and when connected via VPN to Germany, Italy etc. It actually updated to Android 11 C23 using OTA when I changed phone's region to Singapore using the service code. Then I was still able to go back to Android 10 using OZIP file (like described in this guide), or it was also possible to flash individual img files from fastboot using adb as described here. But OTA updates and fingerprint scanner were still broken until I sent the phone to Realme service and they reflashed it completely within warranty - after that fingerprint sensor works properly and I got OTA update to Android 11 C26 right after connecting to Germany over VPN.