I tried dirty upgrading alberto's cm 13 to latest 20-jan version. After rebooting,i found that just after reboot,as soon as i cleared my lockscreen,the phone rebooted.At first i suspected the rom and tried a clean flash,but the problem stuck on.This is not a boot loop.
I tried other roms,backups etc but no avail.I tried restoring boot.img from old backups but no good.Then i closely observed that the phone shows lockscreen,and just when the carrier name appears at top ,after about 5 seconds the phone reboots.Further, the phone reboots only when 2nd sim is placed. But even if the phone does not reboot,turning airplane mode with only slot 1 containing sim results in reboot. Also,if any sim is placed,the phone does not reboot to recovery or bootloader mode and reboots normally.When i try to power off,it reboots.
All the above problems disappear if the two sim slots are empty.Please help me
Edit:-Fixed this issue by using lost101's guide to flash stock files.Great thanks to him.
Broadcasted from Zeta Reticuli
Related
Some weeks after rooting my infinix x403, i started having this error message( process.com.andriod.phone) has stopped, which led to disabling of my SIM Management after phone reboot during call.
since then, the phone can't recognize SIM card.
I've cleared the cache memory, phone clean up and even hard reset the phone to factory setting, but the error remains.
.........................................................................................................................................................................................................................................................................................................................................................................................
To my thought, i believe booting the phone with a working boot.img will work......please help. thanks
olusheye9 said:
Some weeks after rooting my infinix x403, i started having this error message( process.com.andriod.phone) has stopped, which led to disabling of my SIM Management after phone reboot during call.
since then, the phone can't recognize SIM card.
I've cleared the cache memory, phone clean up and even hard reset the phone to factory setting, but the error remains.
.........................................................................................................................................................................................................................................................................................................................................................................................
To my thought, i believe booting the phone with a working boot.img will work......please help. thanks
Click to expand...
Click to collapse
Stock ROM link: https://docs.google.com/uc?id=0By4TkgQ4BdhWQ0Vqd0Z2b3hvREE&export=download
Before you do this, try resetting your phone to factory settings from recovery and see if the problem is solved.
Infinix X403 now stock @ infinix logo after flasing
i really want to appreciate this great working team..thanks.
After flashing with Sp flash tool, in which the flashing was successful with a green notification icon, the phone refuse to boot pass infinix logo also can not enter recovery mode using Volume down button+power button. the phone is no more charging, just displaying the red charging indicator
please kindly help.
This are some of the areas flashed in the scatter file...
EBR1, UBOOT , BOOTIMG, RECOVERY, SEC_RO, LOGO and ANDROID
note: PRELOADER, MBR and CACHE not flash.
Hi! Long story short: My oneplus one has started to behave weird since last month.
I was on cm13 latest nightly and boeffla kernel.
Device worked great UNTIL you perform a reboot. (I had liveboot app installed and the log started to show an abnormal error code causing a bootloop. "unable to open mixer card 0, then 1, then 2 and so on. )
Every time i reboot and this error starts, it bootloops, or starts. But when boeffla kernel default settings apply, device freezes and shutted off. (I checked this by changing the time that boeffla app waits until it applies default config).
At first i thought a clean flash was needed, i usually dirty flash nightlies and some times i start over with a clean flash.
I identified that this error " mutes" the device and causes audiofx app to FC until the phone dies.
I related this to the thread "brickloop EFS corrupt" but i didnt have any time to try anything.
Last week device shutted of because of low battery and hard bricked itself. (Well, qdloader 9008. Not a hard brick, properly speaking but there is a fix with the chinese colorOS zip)
Now this is the first weird thing... Devices dont just hardbrick itselves.
But battery was dead, really dead, and caused the mbn image flashing in the chinese tool to loop and device connect and reconnect on every attempt to flash this first file. (For those experiencing this issue i can confirm is the battery dead, and sahara error code is a corrupted file on the folder).
I have another oneplus one, so switched batteries and was able to flash the damn thing.
Now, back from dead i had none imei, baseband, bluetooth or wifi and audioFx FC.
I tried reflashing the persist, reserve4, modem1 and 2.
I tried formatting mmckbl0p15 with terminal command.
I installed colorOS, then switched to cm12 and got back my baseband, but still none of the other things.
I downloaded the "nightmare fix" full folder from the brickloop thread and followed the steps. No result on any flashing attempt.
On a random cm12.1 flashing attempt i got back wifi and bluetooth and imei showed now "0"
Using the "el hechizero" method i had rewritten the imei number with QPST and got the signal back and sim card detection. But it looped from "no sim" to "no service" all the time.
From there, i fastboot flashed cm11 44s and got everything running. Wifi, sim card, bluetooth, imei. All except audio. Device is mute, audiofx FC. And i have to reboot it several times until i get it working.
Now i am where i started. Stuck on cm11 44s. Any other rom flashing causes a hardbrick if i go with fastboot. And if it boots, something will not work, wifi, or sim detection. And audioFx FC on ANY rom (after 10 or 15 reboots it works until i reboot again) and random shut downs. (Not reboots, device just freezes and shuts off)
Of course i dont have a EFS backup, just another oneplus one that works like a charm running cm13 and boeffla.
I tried MANY things. It only leads to qdloader or faulty roms. Cm11 44s works stable enough as long as i get it to boot with audio and keep the phone charged.
Anu suggestions? Maybe i should start to think about a faulty motherboard?
Hi,
since my old M7 is having more and more annoying issues, I tried to move to a One A9.
The problem:
The phone gets stcuk on LOS boot screen. Looks like it's loading but it never finishes and I can't even turn it off by holding power button pressed for 10s, 1m or even 10m!
BUT this happens only sometimes! Last night I just left it in this state to get the battery empty and this morning it was turned off. "On the way" to recovery (TWRP 3.1.1) I pressed the wrong button and it rebooted. Without any issues! Used it all day until I wanted to reboot it to insert a microSD-card. Since then: stuck on bootscreen! Can't get out...
Any ideas?
What I did:
Unlocked the phone
Factory reset
Installed TWRP
Flashed LOS 14.1
Flashed Magisk 14.0
Help appreciated
Somehow I'd consider this thread as solved:
I went back into TWRP and:
- formatted DATA
- made a full wipe
- made another full wipe
Now suddenly I don't get neither bootloops nor "Can't mount" errors in recovery (which I forgot to mention in the opening post :silly
I write "somehow" since I have formatted DATA before, as well as made a full wipe, because I couldn't even install LOS before that
UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!
EDIT: Disregard the rest of the post. Restoring the stock ROM and then installing the OTA apparently fixed the issue for me.
G7 Power user here, with Magisk.
Recently I tried to install the new OTA update, so I followed the Magisk tutorial with the Uninstall -> Restore Images, then Install -> Install to Inactive Slot and all that. Magisk had some issues unpacking the zip at first, but it eventually worked, so I rebooted as per instructions.
Then I got bootlooped. I was warned that might happen once or twice after updating, but no, this was a genuine bootloop, lasted forever. Disheartened, I figured my only option was to reflash the stock ROM completely (as flashing just the unpatched boot.img didn't help) and work my way up from there again.
But when I did that, suddenly my phone stopped detecting my SIM card. No matter which slot I put it in, no matter how many times I turned the phone on and off, the airplane mode on and off, it remained unresponsive. My IMEI is blank, even when I use the *#06#. Dialing the *#*#64663#*#* code, which I've seen as a suggestion to solve the issue, doesn't work either, it just returns me to the dial-up screen.
I've tried every solution I could find online. Some of them led me to more bootlopping, some of them simply added a "system integrity compromised" message that prevented updates and most had no effect. I'm not sure where the problem lies in the first place... Any ideas on what I could do? Any help would be much appreciated.