Hi, I am hariharan. I need help guys. i restored my nexus 5 from cyanogenmod 13 to stock android 6.0.1 by wiping my device completely and format data option in TWRP. Everything went fine during formating the data except one error
"flash image /dev/block/platform/msm_sdcc.1/by-name/metadata /dev/zero process ended with error: 225"
And normally i restored my device with stock android 6.0.1. My device booted up normally.
After skipping the initial setup i made a call to my dad,it went dialing for 20 seconds with out any ringing sound and ended. When others tried to call me they heard that my phone was switched off.
I rebooted and once again tried no change. I changed the SIM to another mobile and checked the SIM was fine. I tried every stock rom released for nexus 5 but no luck. I also tried many roms but still no change. I also installed modems from the thread http://forum.xda-developers.com/goo...t/modem-nexus-5-flashable-modems-efs-t2514095 no luck in it.
But the data is working.
How could i solve this?
It could not be a hardware problem, as everything worked before the whole mess started up.
Related
Hello All,
I am freaking out. I am not sure what went wrong. I was flashing my phone with new rom from KiNgxKxNexus FroyoDesire2Nexus 1.4 and I got stuck while booting and then I restarted and went to bootloader and restored crayogen rom. Since then I am unable to use my phone without headset though I tried different roms, restored etc. Phone is always detecting headset though it is not connected. Please help me on how I can fix this issue. Your help is greatly appreciated.
Thanks
Just wanted to update that I got this fixed. After flashing couple more roms and restoring my rom from older versions and clearing and wiping the cache and data it finally worked.
So I installed clockwork and then installed an unlocked bootloader, after that I booted into recovery and installed cm 10 and gapps after I wiped data. Once that all finished I started the phone up I was already activated and stuff like that, but every time I would restart it would bring up a screen talking about activating my phone, and it never did anything just sat on that screen.
So I looked around and saw a post with someone having the same issue, and someone told them to wipe data and clear dalvik cache, so that's what I did. Once I started it back up, I had to go through the setup process again, this time it stopped and activated my phone, but it fails every time.
How could I fix this? I also tried installing cm10.1 and Liquid and neither of those would activate either.
If all else fails I will do http://forum.xda-developers.com/showthread.php?t=1867253 but I'm afraid that won't work correctly either..
Had the same problem after flashing the Carbon rom. Try going in settings>More>Mobile Networks>Preferred Network Mode. Select CDMA / EvDo auto. Reboot.
Ah that fixed it! I didn't have to activate either, it just started working.
Oddly though I tried dialing *22890 and it failed to activate.
I do have another question though, when I reboot it still seems to come up with the activation screen. Any idea how I can stop that from happening?
I tried to dial the # and I got this message unfortunately process com.android.phone has stopped
now every time I hit ok it comes back - after 3 times phone reboots and starts over the same message.
Phone is stock - just got updates OTA it is Global version
please advise if anyone had same issue and possible resolution. I checked some solutions from GAlaxy s2 and 3 but all of them require phone to actually work - I cant get to settings
thank you
Well i had the same problem after flashing many different roms. My mistake was forgetting to wipe to factory reset before flashing. Maybe this will solve your problem too.
Having this issue as well!
This started happening to me this morning. I am running CM12 Nightlies. I tried factory resetting...still happens. I tried everything. I even tried fastboot flashing the device to 100% stock...the first time I booted up after flashing stock and locking bootloader....the phone says "Unfortunately, the process com. android. phone has stopped". EVEN AFTER A FULL FLASH BACK TO STOCK UNROOTED 4.4.4!
HELP PLEASE!
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?
Pardon for a long story but someone gave this Samsung J7 Prime(SM-G610F) to me with an issue "An Error Has Occurred While Updating The Device Software". So I gave Samsung Smart Switch a try sadly they removed the Initialize option and old version don't seam to do what it suppose to do so I wen to a traditional Odin flashing. I then look for a stock rom for the phone that I think is the right one. Started with android 6 MM region pakistan and flashing went well. I was able to use it for a good hour or two until I notice it restarted by it self, then it keeps doing it 10-20 seconds after booting up. I though its the firmware I'm using so I went and look for Oreo version this time I region india (I don't know if region matters). So I flashed it again and tested the device again. I'm still able to use it for a good while till it restarted again. I then keep testing it to see what may be causing the problem. I notice that when the WIFI is on it just crash the phone to reboot so as soon as the phone reboots I turned the wifi off and it didn't crash anymore. I then factory reset the phone cleared everything, wipe cache then installed benchmark tools first. Thing I notice is it crashes when Google Play store is trying to install or download something. I tested it a couple of times to see when it crash and it does crash when downloading or installing something. I was still able to install 3Dmark and run it with wifi off. It completed the test without crashing so it couldn't the processor issue. I then look for another rom and tried flashing it. This time I had issue with it failing at system.img even if I use recent rom that worked. I then keep trying till flashing TWRP worked and flashing the rest of the rom is fine again.
What bothers me is why doesn't it crash during the first couple of hours. I've search similar issues and they say it may have been and app issue. I've already disabled bunch of app but nothing changed. Run the phone in safe mode but this time instead of crashing and rebooting right away it freezes for a few seconds. I suspect if google play or something being an issue since I've tried disabling it and it didn't crash for a couple of hours. Looked for allot of related thread but none of them seam to solve my problem.
I suspect either its the rom that I'm using and it can only be fixed by using the original rom, or its having a memory issue but don't know how to pin point it. Anyone can suggest on how I can debug this? I'm used to debugging things in real time and my knowledge with android is a quite slim but as a programming understanding the errors won't be a problem. I hope.
Edit: Hmm. Does copying kernel log with TWRP work or the kernel logs get overwritten every time the phone reboots? Because I see the kernet logs but don't see anything failing except for something saying SHUTDOWN but I don't think thats it. :S
Still no reply. :S I think its /system dismounting it self while doing a write operation. but it doesn't trigger until a certain amount of time after the phone is flashed or factory reset. I have to go to recovery and mount system back but that only happens on marshmallow. over version it remounts it self after the random reboot. After factory reset I'm able to install COD mobile and play a couple of match. after a long while it just decides to reboot.
I also tried z3x and after reading PIT from phone OK. the phone just reboots and flashing completes without it doing any flashing.