Hey there. I'm kinda clueless when it comes to this stuff, but the performance drop when gaming with Android 11 was so bad that I'm willing to try my hand at downgrading if it's possible. So I wanna ask, is this possible? And if it is, how hard would it be for someone who has no experience doing it? Could I get some pointers?
I've found some guides for downgrading G9 Play and they seem simple enough but they're all for downgrading from 10 to 9, would it work if I followed them but downloaded the files for Android 10 instead of 9? And would I lose anything besides my files and apps by downgrading (ex: some base function stops working or something)?
I go to Pie. It's a better OS with less restrictions on trusted apps. No scope storage.
Related
Does anyone know if this software is worth installing onto my Dream using Cyanogenmod ROM? Main question is, is it safe? Is there any point in having it?
https://beta.flexilis.com/
Is scanned every app that I installed , which was great , but also caused some major lagging , lockups and even some fc's .
We havent tested against cyanogen modded devices, there shouldnt be an issue, just depends on how the device is setup and how much is on it in memory, etc. We work on regular stock android devices, though custom mods dont usually go through the same stringent QA procedures that stock firmware's do in the factory, so there's more variables there for us to work around.
But, long story short, it should work fine.
Right. I have been doing a fair amount of research on how to install the Xposed Framwork. I am running Lolipop 5.1 and I am pretty sure all Doogee X5 Pro's run it. I haven't changed anything to do with the rom and my android is rooted using KingRoot. I only did that because it was easy to do and I didn't want to go through the bother of flashing a nand or anything. I got the installer thinking that would work[This was before I did any research about Xposed] I heard that it allowed you to use a lot of modules and improve the device so I thought.. Why not. this isn't my first time screwing around with nands and stuff with devices.
Anyhow. On to the problem at hand, To start with I think I am on a stock ROM and a lot of people are saying that I am going to need to get a custom ROM. I am not entirely sure what to do there and I am aware that most android devices are different so looking at a tutorial from someone not using the same device as me causes some issues.
I don't know which SDK to get for the framework but after doing a fair amount of looking and finding that I need armv8-a helped out a little but then I got slightly confused with the table that they made on the Xposed Framework Thread. It stated that if I was not on a TW ROM then I would need to check if the /system/lib64/ folder exists and then that would tell me what ROM to get.. I found that all a bit confusing and not very well explained so I didn't proceed because I didn't want to end up bricking my phone [So much as you can fix a soft brick. I thought I would come here first and save my self some hassle]
Model Number : x5pro
Android Version : 5.1
http :// prntscr.com / bzu2he
EDIT: I just booted into recovery mode and then I got the "No Command" problem so I had to take the battery out to get it to reboot into normal mode..
EDIT: Well that was silly. Found a way around it. Now I can get into Recovery Mode.
Link to the spec's of Doogee X5 Pro
Kindest Regards XeNitro
Is it possible to unlock?
At this moment, no.
You will know as it'll be reported here very early. There are some third party companies that do it. Some are cheaper than others.
For the moment, there is nothing..
Sucks I know
I asked this before on another similar thread and didn't get a response. Is it possible to dump the bootloader from either an unlocked or locked phone to analyse it for potential vulnerabilities either in how it handles the unlock code, or more generally that would allow a user to soft-mod unlock the phone? I know for the 5th, 7th, and 9th gen Fire 7 tablets exploits were found in the LK part of the bootloader which eventually allowed for a customised version of TWRP to be flashed onto the devices, and later LineageOS. If we could dump the current Huawei bootloader surely we could try to find if there are any similar exploits?
I am found metod but it needs mrt dongle((
Tbh custom roms aren't really important anymore. Google is already ruining android everytime a new update comes around, like the overlay feature that was introduced in oreo but then removed for no reason.
Besides EMUI is already optimised for the chip so, again, no reason for custom roms and/or rooting (unless you want to remove bloatware but that can be solved via ADB)
The Restless Soul said:
Tbh custom roms aren't really important anymore. Google is already ruining android everytime a new update comes around, like the overlay feature that was introduced in oreo but then removed for no reason.
Besides EMUI is already optimised for the chip so, again, no reason for custom roms and/or rooting (unless you want to remove bloatware but that can be solved via ADB)
Click to expand...
Click to collapse
I am need it for root and lineage os
Hey so since EMUI 10 hasn't been released yet to Honor Play devices (and won't be released any time soon) I've been looking for every possible way to manually flash a custom rom so I could upgrade myself to Android 10 or anything similiar, but as far as I know it is practically impossible. It always comes back to unlocking the bootloader which is by itself impossible too.
Every information regarding this more than a year old and I can't find new releavnt information.
I'm posting this thread to see if anyone knows of a workaround to this problem because I'm completely in the dark about this.
Is there anyway at all to install a newer EMUI/Android versions on Honor Play, either officiallyor unofficially?
It looks like there isn't and there probably won't be in the future either. There was some kind of manual bootloader unlock by opening the phone, but if I remember correctly you still needed a code. Unfortunately it's like this for any latest huawei phone. Unless huawei changes its mind about modding (narrator: it won't), we don't have many chances at it.
Is it possible to downgrade from 13 to 12? I think the upgrade messed up my camera. Or maybe a way to reflash the camera firmware?
If the bootloader wasn't updated you can roll it back.
How can I find out if it was updated? I have a US unlocked phone. Its updated from 11 to 12 and now to 13.
See this thread, different models but the same information applies.
blackhawk said:
See this thread, different models but the same information applies.
Click to expand...
Click to collapse
This is the build I'm on now:
RedCrane3 said:
This is the build I'm on now:
Click to expand...
Click to collapse
Hello good morning
Of course, it can be downgraded, as long as the binary number is the same... example in the image.
The bootloader version is 9 so for you to roll back that build number's 5th digit from the end needs to be the same or higher.
With stock Snapdragon's locked bootloader it's easy to get locked into an OTA upgrade you don't want if it updates the bootloader too. I have two N10+'s, one running on 9, the other 10 (can't be rolled back to 9). That's what they were loaded when bought new. They will likely remain on those versions for their service lives as they are running well. I prefer Pie though.
I could be running Android 11 or 12 but I blew them off mostly because of the scoped storage bs.
The first thing I disable is OTA updates, once bitten twice shy. Had a S4+ that got screwed up by a OTA update that couldn't be rolled back... it sucks.
Thank you guys for helping me with all of this information. I guess I have a decision to make.
I can try to rollback to Android 12 in the hopes that will fix my camera issue, or I can sit tight and hope that a future update will resolve it.
Either way, I'm beginning to regret allowing OTA updates.
I really love the hardware of this phone, especially the screen, but its not important to me to have the latest Android (security updates are important though).
I originnaly submitted the problem to Samsung through their members app and the tech who looked at it said he *thought* it was a hardware issue, but come on, what are the chances that the one camera stops working right after the update to 13 and OneUI 5? I take very good care of my phone and never drop it (certainly didn't recently, after the update), there's not a scratch on it.
I suppose its possible, but it would be an incredible coincidence...
The tech suggested I visit a service center (which for me would be a Best Buy, yikes) or call their support 800 number, but what are they going to be able to do that the tech couldn't?
I just don't know if I can trust their initial assessment - no one knows everything, and plenty of people give up on a problem and pass it off the first trouble they run into. Maybe the tech just wasn't interested in digging deeper? A quote from their answer:
"Chi request is getting timed out. Read wide camera sensor seems to be not responding to requests [...]"
I guess my question is: can a downgrade to 12 even fix the issue?
Should I wait for another update?
Or should i just heave Samsung over the side and try to install a custom ROM?
Thanks again for all your help.
You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.
blackhawk said:
You're welcome.
If the bootloader is locked you can't install a custom rom. This is the case with most newer Snapdragon's including the N10+.
The Samsung Experience center at the best buys can run advanced diagnostics so they might be able to find the issue. They can also roll it back or try a reflash of 13.
Click to expand...
Click to collapse
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.
RedCrane3 said:
Ah, ok, but do you mean that the version I have (unlocked US snapdragon) is not able to unlock the bootloader, or just that I'd need to do that first? I do have experience with custom ROMS; my old moto X4 has seen many different ROMS in it's lifetime, so I do feel comfortable unlocking the bootloader and flashing other ROMS.
Click to expand...
Click to collapse
That refers to the carrier not bootloader I think. Not sure about your specific model's bootloader.