Let me start by saying I am not rooted no twrp just plain stock , with locked bootloader. Also EU version.(V12.0.8.0.QJGEUXM)
A few months ago I downloaded the Android 11 Rom V12.0.6.0.RJGEUXM through the phone even though I am not on any trial program.
It installed easily on my phone , some people have had to use other methods...so I read.
Anyhow , I thought it was way too buggy and needed to downgrade.( Even after the the 2 other upgrades to V12.0.7.0.RJGEUXM. This is what I did to rollback if someone else is in the same boat.
I had to wait 3 days to unlock my bootloader,
Then I used the MiTool to select the ROM I wanted.
The problem then is the bootloader is still unlocked after you flash the new ROM, you need to use ADB command " OEM lock" to relock then phone , it should erase everything then go back stock. I am still learning with this Xiaomi device so I had to learn this from different sources and hope it helps somebody else out.
Soz if this is common knowledge or wrong part of forum!
thanks for the info but why did you downgrade did android 11 lags the phone or what
aymen peter said:
thanks for the info but why did you downgrade did android 11 lags the phone or what
Click to expand...
Click to collapse
1) WiFi issues and random reboots, when the phone booted (on its own accord) on reboot the wi fi took quite a few minutes ( over 5 minutes sometimes longer) to get back online.
2) The speaker volume seemed too quiet for video and calls.(on at full volume most of the time).
3) Not so polished, sometimes would be a bit laggy other times not.
At the minute Android 11 for the Poco is still Beta, I am sure these problems will get resolved. The moral of story ... Wait for OTA instead of forcing updates.
i used xiaomi flash tool to flash fastboot rom and selected this to keep unlocked bootloader
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
Hey,
I recently got a cheap, slightly used chinese version Nokia N1. But because without the Google Services its pretty much useless to me, I want to root it and install a custom ROM.
I followed 2 tutorials:
https://forum.xda-developers.com/nokia-n1/help/nokia-n1-root-t3125771
and
https://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
But I always get stuck on the part with the Recovery Launcher.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
To give some background, here are the steps I did:
Because fastboot and the launcher won't see my device if its in MTP or PTP, I disabled both. That seems to work fine.
I "unlocked" oem in the developer settings and also allowed USB debugging.
I started the Recovery Launcher with admin privileges and used option T4.
It boots into recovery mode, but I just get errors all over the place bacause the device is still locked. So i just typed "fastboot oem unlock". Then T4 again.
Thats where this error occurs. From what I read, this should put me into a CWM recovery session. But it doesn't. It just stays in the fastboot mode window.
I'm pretty new to this android modding thing, so don't expect to much knowledge from me.
with much thanks
~David
Bump
I really hope bumps are allowed here
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
nuzzydev said:
its seems from ur bootloader, try to re unlock with fastboot unlock oem. if you done try different recovery developed for ur devices.
Click to expand...
Click to collapse
The thing is, there are no other solutions out there I really know about. I searched google up and down and got no real result.
I think my problem is that my android version isn't 5.0.x, like almost every english tutorial suggests. It is 5.1.1.
oh God... my fault sorry
Hello,
I've got a weird problem with my M4
I've got the phone for over 2 years, it's the E2303 version. It worked perfectly normal until at some point it started randomly crashing (Note: the phone wasn't rooted at this point and it had Android 5.0 26.1.A.3.111 (carrier version)). The crash looks like this: the phone freezes for like 2-3 seconds not responding to any input, then the screen goes black, then it boots up normally. However it isn't rare for it to crash like that, then while booting up crash again in the same way, repeat a couple of times. In System incidents it's counted as just 1 incident. I also noticed that sometimes after successfully booting up after crash wi-fi, mobile transfer or airplane mode are switched on/off, not as before the crash.
I thought the problem would go away so I waited a bit, but it kept on crashing. Sometimes it can go for a few days without crashing, sometimes it crashes a few minutes after last crash.
I've tried fixing the phone using PC Companion (it also updated it to 6.0) - didn't help. I've tried flashing a stock 5.0 ROM using Flashtool (same as before: 26.1.A.3.111, but a non-carrier version) - also didn't help. Also I've got the phone rooted by now. I don't know about bootloader, the service menu tells me Bootloader unlock allowed: No, even though I've got the OEM unlocking switched on in the Developer options (I'm not that tech savvy in case of phones and I'm getting lost a little bit).
I've got some screenshots here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I hope there is a way to fix this phone, this crashing is starting to get a little annoying...
Any help would be really appreciated
Install twrp. Download latest stock rom. Format phone by wiping cache, system and data in twrp wipe option. Install flashtool and use it to install latest stock rom. Watch a tutorial on youtube How to install latest stock rom through twrp
I read a lot in these forums here about OEM unlock S9+ but until now it did not work for me. Additionally there are lot of confusing information around here...
Can anyone (from OWN experience !) please write how unlock, waiting-time and RMM-states are related?
I bought a new phone from U.K., a variant which actually is only available in the Asian market as far as I know.
Color blue with 256 GByte and dual-SIM.
It has EXYNOS CPU !!! As you can see from my attachments, I have already been waiting 7 days for OEM-unlock with no success. I did not boot into download-mode yet.
I assume Samsung has produced phonse, even with EXYNOS, where the OEM-unlock is impossible...
View attachment SoftwareInfoS9.pdf
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as I know, so far, only the snapdragon variants can not be unlocked using the OEM Unlock feature.
I had a custom ROM for about 5 days, and to be honest I sort of wish I hadn't done anything at all. Unlocking the bootloader breaks things like Google Pay and Device Certification on Google Play. This stops things like Netflix and other services (seemingly only ones that rely on Googles Windvine DRM - although the APKs can be installed manually). The second you load TWRP, Knox is gone forever. It is unrecoverable. This I care less about, although Secure Folder had its uses for duplicating apps.
Yes, its possible for Root to fix most of those, but its an endless cat and mouse chase and often breaks when Google update things (I could not get Google Pay to work at all despite Magisk Hide)
During those 5 days, the OEM Unlock option was unavailable to me. When I decided to go back to full stock condition (minus Knox) I loaded all the correct things in via Odin, and the OEM Unlock option was available, with the slider in the off position.
What I want to know at this point, is does turning it on re-lock the bootloader? Because if it does that would likely solve my issues with Google Pay (its incredibly handy).
To answer your question though, the standard waiting time is usually 7 days, after which it will re-appear.
I now rebooted to download mode to see the RMM state. It is Prenormal...
Well, it's a bit of a long story, so I'll try to be as short as possible.
Last year, and after hours of searching on the internet, I found the solution for "Custom binary blocked by frp lock" on this forum (here and here). Both methods promised to fix the lock without erasing my data, but I decided to try the second one (it consists of reinstalling only the boot image with Odin).
Fortunately it worked for me on the first try, and since this method was not well known on the internet, I decided to make a video tutorial to help those who had the same problem and wanted to keep their data.
The fact is that, unfortunately, this method didn't work for everyone, and in many cases it generated bootloops or black screens of death.
And my question is: does anyone know what could be the cause of this?
I tested it on SM-J710MN and SM-G532M, both running Android Marshmallow, and the bootloops/black screens occurred on devices running Android 6, 7, 8 and (I guess) 9 and 10.
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
jwoegerbauer said:
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
Click to expand...
Click to collapse
Thanks for answering.
Maybe I did not express myself in the correct way, but actually I was referring to the block that does not even allow to boot the device and only shows words in red, as seen in this image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But beyond that my question is about why does the bootloop or black screen happen after flashing the boot.img file? Does it have to do with a different/incompatible version of Android/binary/csc or something like that?
So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.