I got a new phone and decided to finally sell the Moto G. It was on some ROM, so I factory reset from options, which forced it into a bootloop. So I then tried to install a stock rom lollipop rom (http://forum.xda-developers.com/showthread.php?t=2542219). But it didn't work. I then realised, that I cannot update the recovery on the phone at all. Its stuck on a custom recovery, that works, but should not be there as I've tried to overwrite it with stock. Ever since then I've been trying to rectify this. I've tried flashing recovery both through the custom recovery itself and through fastboot.
Also, something else I've noticed. If I put some files on the phone and restart it, they seem to disappear. Another thing I've just noticed, I can't seem to wipe the phone. All of my original files are still on it ? That doesn't make sense..
eMMc corruption.
Symptoms:
(i) Cannot change Recovery.
(ii) Cannot wipe /system | /system is read-only
Many Moto G's end up this way. The corruption cannot be repaired, however you may be able to flash a custom ROM (Stock or AOSP) via TWRP.
I've tried flashing a stock rom through TWRP, but it seems to be stuck at boot :/
smilgy said:
I've tried flashing a stock rom through TWRP, but it seems to be stuck at boot :/
Click to expand...
Click to collapse
Try CM12/13.
lost101 said:
Try CM12/13.
Click to expand...
Click to collapse
It gives hangs at patching system image unconditionally.. Looks like its dead.
lost101 said:
Try CM12/13.
Click to expand...
Click to collapse
if is a emmc corruption theres any fix?
alex61194 said:
if is a emmc corruption theres any fix?
Click to expand...
Click to collapse
None that I am aware of.
Related
My Infinity won't boot any rom, not even stock. It will get stuck in a few second and reboot.
I was on the 10.6.1.14.4 bootloader and cm-20130430. I decided to try CROMI X 4.4 and downloaded the bootloader + twpr flasher (http://www.androidfilehost.com/?fid=22909751817928748) because it was the fastest way to get twpr. When the bootloader + twpr was flashed I rebooted back into recovery and wiped everything. Then I flashed CROMI X 4.4, but it was bootlooping.
I tried other roms but they also started bootlooping. I tried different bootloaders, like the one from dasunsrule32. I even went back to 4.1.1 bootloader + stock firmware from the Asus' site.
Does anyone have an idea how I can fix this?
You didn't write that you wiped /data when you moved from CM to CROMI, so try that.
_that said:
You didn't write that you wiped /data when you moved from CM to CROMI, so try that.
Click to expand...
Click to collapse
Hello!
i have the exactly the same problem! right now i just want to get my tablet running but it get stuck in the bootloop ( i see the ASUS logo and a circle that goes round and round).
I have tried several different ROM:s but i get the same problem.....but hey...it worked when i wipe all the data!7
Tank you thank you!!!
_that said:
You didn't write that you wiped /data when you moved from CM to CROMI, so try that.
Click to expand...
Click to collapse
Sorry, I forgot to say that I wiped /data before flashing CROMI. I have tried almost every rom/bootloader but it's still bootlooping . I'm afraid it has something to do with the bootloader, I hope someone has a solution.
Does it hang at the boot animation, or does it constantly reboot to the bootloader screen?
_that said:
Does it hang at the boot animation, or does it constantly reboot to the bootloader screen?
Click to expand...
Click to collapse
It hangs at the boot animation. I can get into fastboot/recovery but I can't find the problem
Abalos65 said:
It hangs at the boot animation. I can get into fastboot/recovery but I can't find the problem
Click to expand...
Click to collapse
Try getting a logcat via adb.
_that said:
Try getting a logcat via adb.
Click to expand...
Click to collapse
I have found a solution. Instead of a factory reset I wiped the entire internal storage and also found an option 'format data' in a older version of twpr. When I did both my tablet booted back into Android. Went through the process of flashing the new bootloader again and now I am on CROMI X 4.4 without any problems.
Thanks for helping
_that said:
You didn't write that you wiped /data when you moved from CM to CROMI, so try that.
Click to expand...
Click to collapse
This is timeless info for newbs. It may seem second nature to those of us with flashing experience, but thank you for noting this! Also, your OC V8 kernel is TEH OHSUM.:good:
So I was using Calkulin's stock 33R with AK kernel, which has been running fine. I deciced that I should try PA, so i did my regular thing of making a nandroid backup, wiping /data, /system and /cache. Flashed PA and the relevant Gapps, and got stuck on PA bootscreen. So I tried it again, and upon closer inspection, in, the flashing of Gapps failed because it was unable to find build.prop.
So I tried it all over again just with PA, no Gapps, no anything else. Same result, just the PA boot animation staring at me for over 20 minutes.
I then tried flashing Clakulin's stock again, and no luck, still stuck on OPO logo screen. I thought perhaps my partitions were messed up, so I wiped everything and flashed stock 33R from CM. Well, at least that booted and my EFS data was intact. I then tried reverting to Calkulin's stock by sideloading, and it never went past the boot screen.
Bottomline: I cannot use any ROM apart from stock 33R. Installing a kernel on top bootloops, installing root bootloops, installling a ROM bootloops, almost anything I flash bootloops. This is driving me nuts.
I am using the latest Philz recovery and my BL is unlocked. I am also a very seasoned flasher and I know what I am I am doing. Yet, this issue is boggling the crap outta me.. I know the solution is probably simple, yet I'm overseeing it.
PLS DON'T KILL ME FOR NOT PROVIDING A LOGCAT. I'll provide anything requested by those helping.
EDIT 1: When I say flash stock 33R, I am referring to the factory image provided by CM on their site. Also, remmeber the nandroid backup I made? That failed to restore. Yea, it failed hard on me.
EDIT 2: I remmeber reading in another device forum where his recovery was mounting the wrong partition when flashing, which makes sense since Philz's recovery produces an error where gapps can't find build.prob. I checked the recovery settings and the only mount I can change is SD from /media/0 to /media/
EDIT 3: I want to shoot the phone, and then myself.
Perhaps try using TWRP, just to rule it out?
EddyOS said:
Perhaps try using TWRP, just to rule it out?
Click to expand...
Click to collapse
Tried TWRP, no error on flashing the Gapps, but still stuck on boot animation.
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
EddyOS said:
If you flash the stock factory image does that work? I know you say you can 'use stock' but you don't say whether that was your backup or the factory image
Click to expand...
Click to collapse
I meant the stock factory image. My nan droid failed to restore.
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
EddyOS said:
I'm stumped cause if the factory image works so should everything else. Bizarre!
Hope you get it fixed soon, bud!
One last thought - I assume the md5s matched on the files you tried to flash, correct?
Click to expand...
Click to collapse
All md5s matched with the files. It IS really bizzare indeed. I searched about this problem for several hours, even on other devices. But no luck!
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
gavin-phelan said:
Try an older factory image and let it boot and do all the ota updates and try then that's what i did
Click to expand...
Click to collapse
Tried that too. Started off from 25, moved to 30 and still no luck.
Ok guys I'm stumped on this one. I got the OTA notification for 5.1 yesterday on my XT1034 and so I decided to preempt any issues I might have and just flash everything back to stock 5.0.2 in order to install the update.
I was able to flash everything fine then went to reboot, got the unlocked bootloader screen and...... nothing. It just stayed on the unlocked bootloader screen. I figured I did something wrong so I reset back to fastboot mode, tried again and sure enough I missed sparsechunk 3. So I tried again, restarted, and.... same thing.
OK then, reset again and reboot into recovery mode. It booted to the Motorola splash screen, ok this is different..... nope still not loading. Reset again and try flashing a custom recovery.
CWM, flashed ok, reset again, Moto splash
TWRP, flashed ok, reset, Moto splash
Philz, flashed, reset, splash
OK.. so I'm clearly doing something wrong. Did some research and tried:
- formatting the cache and userdata partitions
> cache formatted fine, userdata refused to format, not supported for filesystem type 'raw'
- tried flashing again without erasing the partitions
> flashed fine, no change in booting
- tried flashing back to 4.4.4
> flashed fine, no change in booting
- tried flashing all the custom recoveries with 4.4.4, no change
- I found a thread where someone else had a somewhat similar issue, and apparently resolved by unlocking their bootloader
> mines already unlocked, but sure it can't hurt, tried again, but nothing since it's already unlocked
I looked for anyone that had a stock 5.1 image other than the OTA, but couldn't find anything. I gave up on trying stock and looked at some custom roms, but all of them just start with, unlock your bootloader, load a custom recovery and flash the update zip file.
Soooo I'm stumped. I've tried just about everything I can think of. I made backups of everything so I'm not worried about the data I just want a working phone again. I refuse to accept that it's borked at this point since I can still get to fastboot.
OK so, no clue what changed, but I was finally able to boot into recovery, Philz
I wiped and reformatted everything and tried flashing 5.0.2 again
rebooted and it still hung on the bootloader unlocked screen
I'll try flashing Philz again and updating through there
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
tapman said:
Captains log, startdate much too late oh clock
I reflashed Philz and wiped everything again, then sidloaded CM 12.
I'm just thankful to have a working phone again so I'll go with this for now.
Click to expand...
Click to collapse
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Umer520 said:
Sorry for being off-topic but what are requirements of receiving OTA?
Stock ROM, stock recovery and a locked or unlocked bootloader?
Click to expand...
Click to collapse
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
moralesnery said:
Have you tried installing the stock firmware again?
I'm having exactly the same problem, any recovery says it succeeded flashing but when i try to boot it, it goes to stock motorola recovery.
Click to expand...
Click to collapse
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
tapman said:
I haven't tried reflashing the stock again over CM12, but I was able to find a link for stock 5.1 image, you can try going straight there skipping this whole pain.
Here's a link, you can also find it on the stock firmware sticky post that I can't seem to find anymore
https://www.androidfilehost.com/?fid=24052804347819474
Click to expand...
Click to collapse
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
tapman said:
My experience is that you need to be unrooted, unmodified system partition and stock recovery
It's usually much easier to reflash a stock image and update than trying to unroot, uninstall, xposed tweaks, restore original build.prop settings, restore original hosts file, etc
Click to expand...
Click to collapse
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Umer520 said:
Yeah, I'll reflash stock firmware.
Just wanna confirm about bootloader.
Click to expand...
Click to collapse
Yeah unlocking your bl doesn't affect ota's
moralesnery said:
Already tried to flash the full firmware again without luck, after rebooting the phone gets stuck at the Unlocked bootloader warning.
Thanks for the link.
Click to expand...
Click to collapse
I think at least in part what my issue was, was that the partition formatting got borked. If you can boot to a custom recovery you can wipe and reformat them. Then you should be able to reflash it normally.
I was just so tired of dealing with my phone at that point so I only tried once and gave up with stock, but I'm pretty sure that's what I need to do to fix it.
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
kennylrmsailo said:
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Click to expand...
Click to collapse
Anyone out there? Need help desperately.
Anyone?
samuelcr93 said:
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
Click to expand...
Click to collapse
Yeah that might work but I'm kinda looking for a solution where I don't have to flash the stock again because I lost all my moto g stuffs some months back.
And another thing is that when I flash MIUI its working fine again and I'm able to access all the file in my phone storage also. Any suggestions?
Mmmm if you are using TWRP you could connect the phone to the PC and make a backup while you are in recover mode. Then format again data partition to f2fs and make a factory reset including internal storage and finally flash your ROM and restore your files.
But if that is not working then the only option is flashing Stock ROM
If MIUI is still booting it means that your data partition is still ext4
The problem is kinda complicated. Previously, I flashed a custom ROM on my phone (a modified version of Oxygen OS). Just now, I updated my phone using the official ROM downloaded from Oneplus's official site (no idea what I was thinking), and I was only able to boot into the stock recovery. So, I tried reinstalling the TWRP recovery. I was able to boot the phone, but upon boot, it would say something like "Settings stopped working" and it would shut down immediately. I tried flashing a couple of different ROMs using the Install option in TWRP, but I still get the same error when booting my phone. Is there anyway to solve this problem? If not, would there be any way for me to recover my files at least?
Go back to factory stock using the MSM tool. If you can get to TWRP you can backup your stuff.
CosmicInsight said:
Go back to factory stock using the MSM tool. If you can get to TWRP you can backup your stuff.
Click to expand...
Click to collapse
I am able to get to TWRP right now. However, I did noticed that the Data partition in the TWRP Backup option is only 76MB. Does this mean that my data's gone already somehow?
leniumC said:
I am able to get to TWRP right now. However, I did noticed that the Data partition in the TWRP Backup option is only 76MB. Does this mean that my data's gone already somehow?
Click to expand...
Click to collapse
Yeah, probably.