Hi All, my redmi 5a auto rotate doesn't work, I don't know why but I've experienced a tragedy that maybe connected with this problem.
I use AOSP Extended ROM for Rolex in my Redmi 5A Device, as long as I use it I don't have any problem, but yesterday I've tried to restore my kernel into this ROM Stock Kernel ( I Use Direwolf Unified Before, Many Times I Try Other Kernel Also But And Never Had Such A Tragedy) After I Restored the original kernel, then I wipe my dalvik and cache as usual, BUT, Suddenly The Boot animation Stucked before it show's the AEX Logo, So I Think It Was A Bootloop Simple Problem, Than I Reinstalled My AOSP Extended OS, Than Something Happened, Even Since The First Boot It's Stucked At The Same Point, Than I Tried To Re-flash it again, and after that it still like that, so I was thinking that my External Memory Data Was Corrupted, So I Tried To Copy The File Directly From My PC To My USB OTG (I copied same AOSP ROM) than I reflash it but it still like before, than i start thinking if this ROM file (in my PC and SD card) is corrupted, so I tried to install PE ROM, But The Result Is Still Same As Before, Stucked At Boot Animation Than Forced Shutdown.
Well after that I think my device is get a serious problem such as hard brick or soft brick, than I tried to do clean flash to MIUI 10 Fastboot ROM With My PC, BUT the time elapsed is more long than usually (About 20 minute) waiting for booting and finally my device is normal, so I immediately install TWRP Custom Recovery (3.2.3-1 by FenFern) And Installing AOSP ROM Again (I Swear I Love This ROM) Everything seems normal no problem, restoring app, rooting, personalization, and etc.
Well the problem with auto rotate is coming when I see some funny videos on YouTube, my devices ONLY CAN ROTATE TO THE LEFT, AND CAN'T ROTATE AUTOMATICALLY AND CAN'T ROTATE TO THE RIGHT SIDE, I tried many game's app and watching some anime's in video player, Even If I Switch to auto rotate mode.
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
SandipS said:
hi, you might have corrupted the persist partittion. check in other thread persist related issue. you can get a solution there. by the way does the other sensors working?
Click to expand...
Click to collapse
Well yeah it's working, except the auto rotate
Related
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
stevenx37 said:
I should mention that this phone is not mine and it was brought to me to fix. It could not get past the samsung bootup animation screen.
So I installed TWRP 2.8.6.0 and wiped everything. Then the first rom I flashed was [ROM][5.1.1][AOSPA] ParanoidAndroid 5.1 (5/21/2015) Then flashed gapps 5-22-15 from euroskank/banks. I wiped dalvik & cache (Is this necessary?) and rebooted.
The intro screen did not let me skip the wifi connecting part (I thought it was a bug in that version) and it told me to turn on wi-fi to connect.
So I tried the same thing with the version before that and it let me skip. After that I managed to turn it on once? But it the phone crashed and soft rebooted.
I tried other 5.1 roms and the wifi doesn't work still. It doesn't let me turn it on. Same with 4.4.4 with cm11. Also, the Wi-Fi MAC address says unavailable. Don't think that's supposed to happen?
Does anyone have a fix?
Edit: I took out the SIM card to see if that did anything. Then all of a sudden the grayed out On button turned blue and wifi networks appeared... But I couldn't do anything else since it made me restart. It stopped working after a reboot :/ Tried it several more times and couldn't get it to do the same thing..
Click to expand...
Click to collapse
Hope you had read the posts, it should had said the Rom is not "stable"
If your friend are going use their phone for daily driver, then I recommend you not have the 5.1 Roms for now because it's not really suitable for that right now.....
I'm not sure the CM11 you have flashed is unoffical or is offical. Offical onces are still work in progress and have most of the things broke (I think)
Here is a Kitkat Rom for SGH-T989
If your friend really wanted to have a Lollipop running on his/her phone, then I will recommend this one. Make sure you read the instruction CAREFULLY if you do wanted to install this one since it's a bit complicated with it's "virtual partition"
Or, if you wanted it to be just stock. Odin it back to normal, here is a instruction (with video too).
This is all the possible way to fix your friend's phone that I can think of, if you have encounter any error or have anymore question, feel free to reply :fingers-crossed::good::highfive:
P.S: yes, wiping dalvik & cache is a way to prevent any error caused by another old Rom if you decided to flash a new one. It's a good way to prevent error during Rom flash process
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
stevenx37 said:
Thanks! I'll try the 4.4.4 rom you sent me. I'll post an update when I get to it.
Uh and about the 5.1 you linked. For the virtual repartition part in his post, I couldn't open the phone's internal storage on the computer after formatting it to ext4. So I'm confused about that step.
Click to expand...
Click to collapse
For the virtual partition, it's best for you to have it on the External SD card. Since TWRP transporting file to Internal Storage after that seems bugged (not working)
Hi All,
Having some issues with my Galaxy Note 10.1 which I've had for quite a while now. It's rooted but with Android 5.0 stock rom and a custom kernel.
Just now (like 20mins ago) I tried to enable Adblock plus app, the app said it can't automatically change the settings - even though SuperSU was installed and had no issues with it previously. So like all things thought I'd give it a reboot that ought to clear it out. That didn't work, so tried clearing cache (Dalvik/ART/Cache), Still no joy.
I'm a s/w engineer, but not and android/bootloader expert, so I've tried to grab the dmesg and boot logs which I've attached, I've got some stuff on the internal SD (app data) which I'd like to keep, hence I'm not going for the full wipe.
Please take a look at the logs and see if you can determine how to fix this issue, my initial thoughts were there are some issues with the flash storage (bad sectors/partition table?), if I could grab the image and dd the image again I'd be OK - but I don't know much about about android boot loader/kernel etc so can't say.
Ok it has been fixed by wiping data - but I've lost my data and installed apps!
Is there anyway to find out which file/app is causing the boot loop so I can restore data, delete the offending file?
Well, I shall give a bump to this topic, with a little more info. Though probably not really useful.
First I had stock 5.1.1 deodex pre root etc ROM that, after I tried to insert a nano sim card (mine is a 601 3G model) that got stuck, it entered on a bootloop, I had to open it, take the sim card out, and it was still on a boot loop. Tried to install another image, still bootloop, tried to reinstall the original one I had, still bootloop, wiped data, worked fine.
Then almost 2 weeks later, everything worked fine, went to watch a video, the sound was mute, tried to turn it on but everything looked fine, decided to restart because it would probably fix the problem. Got a bootloop. Wiped the data, everything was fine again.
Now, a little more than 2 weeks later, seems like the wifi is not working, thought all my other devices are, guess it's the same problem, decided to restart it, and bootloop again. I'm currently trying to update my TWRP, and gonna try a different ROM, and wait to see if something like that happens, until then, I wonder what could be happening... I remembered an Asus Device that I had that had different firmware versions for 4.4 and 4.1, so if I tried to flash a 4.4 on a 4.1 firmware it wouldn't work, and for downgrade, the same problem happened, and wondered if Samsung has some difference between versions 4 and 5.
ssj4maiko Let me know if you find a more stable rom - I went back to pretty much stock, but with root as I wanted to use all the Samsung apps, but this constant random bootloops are annoying!
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
furiify said:
Hey,
some days ago i went from 7.1.2 to 8.1. I haven't had any issues whatsoever.
For some reason tho it seems like there's something wrong since my bug isn't listed as known.
The first ROM i tried was RR 6.0, and i tried it 2 times with this ROM. Same bug, just like with crDroid 4.1 which im running now. I even performed a COMPLETE wipe and made sure to flash the latest twrp recovery.
Whenever I setup a displaylock (PIN/Pattern/.. except swipe which is default) the device freezes immediatly afterwards, becomes totally unusable so im forced to pull out the battery. Rebooting then takes me to the lock that was just setup but entering the code just freezes the phone again. There's no workaround so far - everytime it happend i had to go back to factory settings.
Since i need to setup a displaylock to install a certificate I could really need your help. Im thanking in advice :good:
Regards,
furi
Click to expand...
Click to collapse
Same problem
i delete /data/system/locksettings.db with twrp file manager to get rid of this problem but i can not lock because all lock types freezes.
Hello, recently I got the poco f3 (256-8gB) and I have experienced a really weird behavior (I know about random reboots other peooke expperience, but please read what happened to me)
I rooted it with magisk (patching boot image using latest stable apk from official github).
I added smali oatchee module to it.
At some point miui auto-updated to 12.5.1.0 RKHEUXM, I had to get boot image from the update, extract from payload and reparch to get magisk back.
After this I noticed the phone rebooted randomly, it happened like once in 2-3 days, son nothing really anoying, I didn't pay much atention to it since the phone worked flawlessy for everything else. Then I tried to connect to a router wifi (router setup with openwrt) and I noticed EVERY TIME I tried to connect to that specific wifi the phone rebooted. I tried to reconfigure the wifi network but it still happened. No problem with other devices.
Then the next day, I openwd an app which had embedded adds (an app I have been using for a long time, the very same version). 1 second into the add the phone rebooted...and it became stuck in a bootloop in MIUI logo. I couldn't even power off the phone, I could enter recovery/fastboot though.
I used twrp to wipe it without erasing my data, but problem still persisted. Only reflashing boot image (I used stock version) revived my device. I tried to boot it without flashing, phone seemes to boot but with no display.
So I decided to make a full wipe, then reinstall magisk. Phone has been working fine since then, but the occasional random reboot still happens and I'm afraid eqch time my poco f3 will be stuck in bootloop again.
My conclusion is somehow boot image got coreupted, but I can't think of anything I could have done for that to happen, as I only had magisk set up, I didn't even use any app with root permisions yet. Any ideas why that my have happened?
I'm thinking of flashing twrp to recovery so I can reflash boot image from it in case this hapens again...
You mentioned your device rebooted when it connects to a specific WiFi network. Can you get logs for connecting to the network?
I do not use magisk, but I read this thread a lot lol, so as I see the simpler way to root ur phone is to boot to TWRP (fastboot boot xxxx.img) and install magisk from Advanced settings. As I know, there is even an option that allow u to keep ur root after an rom update. U can give it a try, maybe it will solve ur random reboot problem.
Robert314 said:
You mentioned your device rebooted when it connects to a specific WiFi network. Can you get logs for connecting to the network?
Click to expand...
Click to collapse
How may I get those logs?
Alin45 said:
I do not use magisk, but I read this thread a lot lol, so as I see the simpler way to root ur phone is to boot to TWRP (fastboot boot xxxx.img) and install magisk from Advanced settings. As I know, there is even an option that allow u to keep ur root after an rom update. U can give it a try, maybe it will solve ur random reboot problem.
Click to expand...
Click to collapse
My phone is already rooted via magisk patching the roms's boot.img, then flashing via fastboot. That's the recommended method for this device afaik.
Try clean flash. Backup all your stuff that you want to keep. Format data in TWRP before booting into system.
OTA auto-update from time to time causes issues.
I tried again and the revoot when connecting to that certain wifi network persists.
Is there anyway I can reflash my current firmware without having to wipe? Can I jast flash my current update with twrp with no data loss? (Basically what happens when a system update is out...)
Just posting to note that update 12.5.3.0.RKHEUXM solved all those random reboots for me.
They were also happenning when trying to share image/links/anything via bluetooth, telegram....only thing that worked without reboot was "copy link" in the share button.