Database Info

[Completed] Can't boot into my Custom ROM

Hi! I just installed a new Custom ROM for my phone. After 5 minutes I wanted to create a backup. So I started ROM Manager. I entered the name, and hit OK. The phone booted into a crashed recovery mode. So I took the battery out and rebooted the phone. It didn't boot into my Custom ROM. It booted into recovery. So I am stuck inside the recovery mode and can't boot normally.
Phone: Samsung Galaxy Mini (GT-S5570)
Recovery: CWM Recovery
Custom ROM: CyanogenMod

Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:

It still puts me into recovery
HashyCode said:
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
Click to expand...
Click to collapse
I tried it. I wiped /system, /data, /cache and I did a factory reset. Flashed it back but it still puts me into recovery.

xdcsaba said:
I tried it. I wiped /system, /data, /cache and I did a factory reset. Flashed it back but it still puts me into recovery.
Click to expand...
Click to collapse
Flash the original firmware back. And try from the start
HashyCode

It still doesn't work
HashyCode said:
Flash the original firmware back. And try from the start
HashyCode
Click to expand...
Click to collapse
Tried it. Does not work.

xdcsaba said:
Tried it. Does not work.
Click to expand...
Click to collapse
Visit here and try one of them
HashyCode.

Hi, i would like help you with this problem as I myself have experienced it. The things that you should have done are:
1. Always make the backup early on before installing the Custom ROM.
2. When installing a Custom ROM, make sure you have not replaced core system apps
3. Make sure your there are complete symlinks in your ROM otherwise it be hard bricked. Ouch.
4. Before installing a Custom ROM, make sure they are from experts, like CyanogenMOD, and sure your device is supported for updates.
5.[Most Important] The only things to wipe when installing a ROM are : 1. Cache 2. Dalvik Cache 3. User Data, never ever ever ever WIPE your system folder with root access on it. This will always ensure that you will reboot into recovery, and it will be annoying to root your device w/o ADB USB Debugging on.
6. Make sure that there are no system apps missing on your Custom ROM, check for the legibility of the Custom apps installed. Are they pirated perhaps?
7.[Very Important]Always watch a video tutorial for it's errors, and search how to Unbrick your device first before proceeding with an installation.
So that if any problem arises, you will be sure to restore it to it's Stock experience.
8.[Absolutely Important]Make sure that your software counterparts on the PC are compatible and functioning well first before you proceed.
Now tell, me which of the following did you not do?
And if this really helped you a lot, please like. For the sake of those who did their research.

HashyCode said:
Hello,
If you can boot into the recovery, do a factory reset and flash back the custom rom. And then reboot the device, once you rebooted the device will boot into system. And then you're done!
Good luck!
HashyCode. :good:
Click to expand...
Click to collapse
ive already done factory reset like 5 times i still am not able to flash it to custom rom stock condition im going to try using a laptop with windows 7 to see if i can do that way because its not working on the latest windows 8
Kinnngzzzz

Try fastboot?
Hi,
No one seems to have suggested using a program called fastboot. It involves just installing some essential software on a PC, then running the program "Fastboot" along with the desired options.
I strongly suggest trying this: http://forum.xda-developers.com/showthread.php?t=2277112
I am always flashing ROMs and then trying to tweak them and end up messing up the bootloaders, or somehow breaking the system. And then i try using CWM or TWRP and still there remain issues. However, fastboot has always done the job for me.
Hope this helps.

Someone help me with my problem please ??

Use Fastboot!!!
kinnngzzzz said:
Someone help me with my problem please ??
Click to expand...
Click to collapse
kinnngzzzz, you too should use Fastboot! See my post right before yours...
So again, see this link: http://forum.xda-developers.com/showthread.php?t=2277112
I say if fastboot can't get it fixed, nothing will. :victory:

kinnngzzzz said:
Someone help me with my problem please ??
Click to expand...
Click to collapse
As you said that you're going to try with windows 7. Did you tried it? And please! Visit the link which youniqueg33k provided.
HashyCode.

Jeez, I can't flash ANYTHING! (well, sort of)

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.

[Q] - No Calls or SMS OxygenOS or CM12

OK I am having a problem, when i rooted and followed the direction to install both OxygenOS or CM12 nightly I am unable to receive any SMS or phone calls except after a reboot. Once i reboot any saved messages come through and then once the phone sleeps it stops. I have rolled back to CM11S for the time being. Any steps or tricks to follow to get this issue resolved.

"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?

abhibnl said:
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
Click to expand...
Click to collapse
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot

pkp190 said:
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
Click to expand...
Click to collapse
Well all i could suggest it, also please flash the CM12 firmware once. In theory oxygenOS and CM12 firmwares are compatible. So flash like this:
Install CM12 fimrware zip
Wipe System, Data, Cache, Dalvik etc without Internal memory
Flash Rom Zip
Flash Gapps
Flash SuperSu
and then let it boot and settle down. Before restorign apps or data, check for any issues again

seems to be sitting stable at the moment, will keep testing. but thanks for the input.

pkp190 said:
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
Click to expand...
Click to collapse
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.

abhibnl said:
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
Click to expand...
Click to collapse
spoke too soon, after letting the phone sit ideal for a few hours and testing incoming calls\sms nothing came through. restored a backup of CM11S, for the week to have a working device. will keep trying to get to a root cause later in the week. will also open a help ticket with OnePlus to see if there is something I am missing as well since this happens with OxygenOS as well.

Constant bootloop using multiple recovery methods

I have a 6045I
Originally I ran the Chinese ROM with no problems. Wanted to check out the CM beta so I did the standard procedure and followed in instructions on flashing. Found out I was constantly in a boot loop (phone would go through boot animation and load up the OS, then freeze, reboot, and repeat)
I tried going back to back to stock by using TWRP to restore my personal backup but it always went to bootloops. Same with the other backups on the forum.
As a last resort I tried using Mobile Upgrade Q 4.9.2 but the device wouldn't read my device (doesn't detect it).
Any suggestion on how to save this device? All that is working is TWRP so far.

seahavens said:
I have a 6045I
Originally I ran the Chinese ROM with no problems. Wanted to check out the CM beta so I did the standard procedure and followed in instructions on flashing. Found out I was constantly in a boot loop (phone would go through boot animation and load up the OS, then freeze, reboot, and repeat)
I tried going back to back to stock by using TWRP to restore my personal backup but it always went to bootloops. Same with the other backups on the forum.
As a last resort I tried using Mobile Upgrade Q 4.9.2 but the device wouldn't read my device (doesn't detect it).
Any suggestion on how to save this device? All that is working is TWRP so far.
Click to expand...
Click to collapse
The Chinese ROM screwed up your partitions, you have to flash the stock partitions (like I did) provided by @famewolf

fubugang said:
The Chinese ROM screwed up your partitions, you have to flash the stock partitions (like I did) provided by @famewolf
Click to expand...
Click to collapse
Yes, this fixed it!
Here's the post if anyone has the same issues http://forum.xda-developers.com/showpost.php?p=63272682&postcount=178

seahavens said:
Yes, this fixed it!
Here's the post if anyone has the same issues http://forum.xda-developers.com/showpost.php?p=63272682&postcount=178
Click to expand...
Click to collapse
Glad it worked for you. Now you can see just how fast your idol3 can fly under cm 12.1.

Can't flash new recovery, or anything.

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.