While ago I changed my rom from Stock Miui to MiuiMix it was very smooth and then I wanted to try some aosp based rom after a while of using them I tried to go back to miui mix but everytime I install it the phone freezes and reboots itself automatically I can't even get pass the Set up wizard with all this freezing, I managed to get pass it but most of apps don't work or work but after restarting they don't work, I tried different miui based rom and all Stock roms with different version the only version that was working fine was 10.3.x but after updating it the freezes and rebooting and weird auto action started again, I did some digging i found out in An xda thread some guy has similar problem and they said it has something to do with persist so i flashed a new persist but nothing changed now i lost L1 DRM and gor stuck with L3 DRM, now I'm on PixelOS everything works fine but can't get back to MIUI.
Data formated in recovery?
Which firmware do you use?
Related
like the title says everytime that i install last oxigen and last cm7 .32, i try to turn on the wifi and the phone restarts and after i try to turn in on again and it gives to me the error.
is there a way to fix this, because if i use miui and the stock rom i can use wifi without any problems but with this two is impossible.
i have already install first a stock rom the b138 and after the cm7 or the oxigen but the final resoult is aleways the same,
help people since i can use the new rom, the .35 version, because of my touch atmel.
thank you
Check if you have imei=0...
Your only solution for that will be to use stock rom or FLB
yes, my imei is 0, but i have done the backup and i put it on the place and restat the phone and the problem continues
Ok this is a really strange Problem. I have two notes. On both I flashed the s5 port from Fahadali. Both had v6 on them and everything was awesome. He left development though so I continued the Project trying to make a "v7" Version, while doing that after I flashed the modified v6 many times but suddenly it softbricked. All I did Change though were some apks.
I've done this many times before with other roms without any Problems at all.
Then I reflashed stock NF4 through Odin and the newest twrp. Flashed v6 (the original non modded version) and it softbricked again...
I tried again, same result. I tried to Flash other recoveries, other bootloaders, other fw's through Odin and a lot more but: nothing.
Everytime I Flash v6 it breaks. I tried to Flash v5 and then suddenly: It worked! I tried to Flash other roms like Omega, and they work aswell. Only the v6 Version doesn't.
So if that's the case and the phone itself is clean (wiped 100 times Flashed stock even with a pit file) the Rom must be corrupted right? So I checked the md5 and well it was correct. I redownloaded and still: same md5. I checked the md5 on the note aswell. I tried using a sd Card instead and still: the same result.
In the meantime my other note worked perfectly, even with my modded Rom. So I continued to work on the v7 using that one. And then after like 14 flashes: the same Problem on that one aswell.
In detail:
I use twrp. And get into the Aroma installer of the Rom. It installs without any Errors whatsoever. Then I reboot.
And now the important part: the kernel has not been flashed cause it's not showing up in red (the rom's using a custom kernel).
This doesn't happen when I use the v5 Rom(still), and never happened before even with the v6. So I even tried flashing the kernel afterwards trough Odin and it gets successfully flashed. But the Rom still doesn't boot...
This means though that because of the kernel not being flashed (even though in Aroma it Shows that it does) even the rest might not get flashed. It only wiped the System Partition and that's it. But then the question remains why did it work before?? And why does it work for all the other People that have flashed it? And why did it work on mine until I flashed it more than 14 times?? And why does v5 and all the other roms still work fine?
I really don't get why this happens. Some v6 files have to still be on the device somehow, or idk. It's impossible cause I wiped but who knows. I've never seen anything like it, neither has the original dev of the Rom.
I Need to get v6 working, else I can't continue to build this Rom. Which is a big Problem for all who wants the s5 Rom.
I hope someone knows what to do. Thank you for your time.
Hello,
I have posted this on the cyanogenmod forum but everyone seems to be on holiday as I'm getting no replies. I'm hoping someone on here can help.
I recently had CM12.1 running on my S5 SM-G900F for about six months with no problems. I then switched over to CM13 and used that for about a month without any problems.
I decided to go back to CM12.1, I flashed the same CM12.1 Snapshot file that I had been using previously and it installed without error but when I rebooted the phone it would crash and reboot in a loop during start up. I wiped the phone and tried the install again about four or five times having the same problem until on the final attempt it managed to load the OS. Now that I have the OS running I cant connect to WIFI, the 'back' and 'recent apps' buttons on the phone don't respond (the home button does work), the camera app doesn't work (I get the error 'Can connect to Camera') and it keeps crashing and restarting on reboot. Everything else seems to work but the phone seems sluggish and there may be other errors that I haven't come across yet.
I thought that there may be a problem with the zip file I was flashing so I downloaded it again but it did the same thing. I've tried wiping and reinstalling several times but I get the exact same problems. The file I'm flashing is:
cm-12.1-20151007-SNAPSHOT-YOG4PAO333-klte.zip
If I go back to CM13 everything works fine so the problem is only with CM12.1.
I'm at a lost to explain why this keeps happening as I've had this running fine on my phone previously and wiping the phone and starting again doesn't do anything to solve the problem.
Any ideas please?
Come on people! Have a guess, I'm really stuck here!
I myself have not installed any custom roms on my s5 yet (bc of knox 0x0 lol) but try reverting back to the stock rom and then install cm12.1 again, maybe it could work.
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Can you tell what bothered you to go away from cm13 back to cm 12.1?
caned_monkey said:
Thanks, but I've tried that. Both stock rom and CM13 work without a problem. The issue only seems to be with CM12.1.
Click to expand...
Click to collapse
ezantera said:
Can you tell what bothered you to go away from cm13 back to cm 12.1?
Click to expand...
Click to collapse
CM13 sucks!!! snapchat and instagram keeps on crashing, now I'm using resurrection remix 5.7.3, that sucks too!!
After having had a 1 month experience with the rom pixel experience I wanted to return to the rom stock of miui by downloading it from the official pages, I installed them normal as I would with a custom rom (clean installation) but at the time of starting the system at load the first steps and the different configurations the fps drops appear on the screen and it is blocked for 5 to 10 seconds.
I would like to know if I am doing something wrong and I need your help to return to the rom stock and that it works smoothly as before.
Thanks :'(
Download Mi flashtool and fastboot rom.
Here a good how to
https://in.c.mi.com/thread-714161-1-0.html
alejandr769 said:
After having had a 1 month experience with the rom pixel experience I wanted to return to the rom stock of miui by downloading it from the official pages, I installed them normal as I would with a custom rom (clean installation) but at the time of starting the system at load the first steps and the different configurations the fps drops appear on the screen and it is blocked for 5 to 10 seconds.
I would like to know if I am doing something wrong and I need your help to return to the rom stock and that it works smoothly as before.
Thanks :'(
Click to expand...
Click to collapse
As said by the other member (joke19), the best solution is to use the mi tool so as to bring the phone back to its original condition, certainly one of the partitions (probably The vendor partition or persist) (it's just a guess) but ... did you install the latest firmware available in the version of the rom that you then installed?(you said you did a clean install, which means formatting sistem data cache vendor ... And then before installing the new rom reinstalled the Appropriate firmware ...) Personally only once did I return from custom to MIUI (not MIUI stock, however, and at the time I lost the IMEI despite all the correct steps) but it was a long time ago However, these are things that can happen even when you switch from one custom to another, even if one does all the steps. Correct "formatting" from twrp is never a formatting Really clean ... only from fastboot or using the xiaomi tool you usually have a Complete formatting And I would like to underline COMPLETE because in twrp only some partitions are cleaned and this can sometimes lead to small problems
After smashing my head against the limits of the MIUI again, i decided to say goodbye to my warranty and flash a custom rom. Via TWRP I flashed the latest (stable) version of Arrow OS based on android 10Q. Everything works perfectly aside from the popup camera, that appears to be firmly locked in place feeding live feed from inside the chassis. Thinking it was an error of that release, i tried other ROMs, both Android 9 and 10, ResurrectionRemix, Lineage. With RR the problem is the same, while with Lineage, the camera asks for a calibration: it actually pops out fully does two or three pops and then it says calibration failed. The servos are working, I've opened the chassis and found no dust at all, so I've looked for a fix online. The most common one is a flash of the stock 'persist.img' image, I've tried several times via TWRP, tried a few clean flashes (ROM+image) of different versions and nothing. Am I missing something? I don't want to get back to MIUI...
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
The problem persists.
Badis st said:
Did u backup your persist partition before ? if no u can flash any other one that comes in the fastboot stock rom but u will loose L1 (netflix in HD)
Click to expand...
Click to collapse
I did, but even when I tried flashing different versions of persist.img ranging from fastboot stock firmware 10 to 12, with and without backup, (clean wipe, fresh recovery) the problem was still present. I'm no expert but I'd guess the OS doesn't know how to: either tell the servos to pop the camera out (Arrow OS) or recognizing the camera working when calibrating (Lineage OS). I'm trying to dig my way to the cam app in the MIUI release and to install it in the custom ROM, but I don't think it works.