[Q] please help me! the custom rom wont boot - Defy Q&A, Help & Troubleshooting

i flashed the custom rom and my phone wont boot
i could go to 2nd-init recovery menu, so i saved recovery.log
this is the part of recovery log, i think this is the problem
-- recovery.log --
system is not a block special device.
Proceed anyway? (y,n) failure while running mke2fs
format: format_ext3_device failed (-1) on systemmount: failed to mount system at /system: Block device required
-- End recovery.log --
please explain me why it happens (i want to know the reason.......)
and sorry for my bad english.
Sent from the Earth using a loaf of bread

Enter in bootmenu/stable recovery. Wipe the data and the Dalwik. Reboot. If nothing happen (have 2-3 minute of patience) then do it from beginning: flash a stock ROM according to your device (read the tutorial), root, install 2ndinit, reboot, wipe data and Dalwik, flash ROM, (optional custom kernel) flash gapps, wipe cache and Dalwik. Reboot. Enjoy.

thanks
but i wonder why it happens too.....
Sent from a piece of pizza using xda app

It looks like you try to downgrade your ROM without first format system to ext3.

thanks for the replys! :thumbup:
Sent from my MB525 using xda app-developers app

pgreed said:
It looks like you try to downgrade your ROM without first format system to ext3.
Click to expand...
Click to collapse
How do you downgrade to ext3?
Sent from my iPad using Tapatalk HD

My Defy won't still boot after installing the rom
I wiped dalvik cache and /data, /cache.
And I checked this custom rom's updater-script for errors..
but my phone gets problem(appears bootlogo -> black screen -> bootlogo -> black screen looping)
what should I do? please help me once more :crying:
the first and second line of the content of updater-script
format("ext3", "EMMC", "/dev/block/mmcblk1p21", "/system");
mount("ext3", "EMMC", "/dev/block/mmcblk1p21", "/system");

IXM_DEVS said:
My Defy won't still boot after installing the rom
I wiped dalvik cache and /data, /cache.
And I checked this custom rom's updater-script for errors..
but my phone gets problem(appears bootlogo -> black screen -> bootlogo -> black screen looping)
what should I do? please help me once more :crying:
the first and second line of the content of updater-script
format("ext3", "EMMC", "/dev/block/mmcblk1p21", "/system");
mount("ext3", "EMMC", "/dev/block/mmcblk1p21", "/system");
Click to expand...
Click to collapse
Boot loop appear after flashing stock ROM or after installing custom ROM?

No, just custom roms
Sent from my MB525 using xda app-developers app

IXM_DEVS said:
No, just custom roms
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
If boot loops appear after flashing custom ROM enter in custom recovery and wipe (that means format) data/cache and dalvik (that for restore ext4 partition). But that is true for flashing CM10. When flashing CM7 you must do wipe from stable recovery !!

i already did them...
actually i modified updater-script in cm7 please give me the solutions
Sent from my MB525 using xda app-developers app

IXM_DEVS said:
i already did them...
actually i modified updater-script in cm7 please give me the solutions
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
If I understand correctly you have boot loop in CM7.2 after you format on ext3 (with stable recovery) cache and dalvik?

yes thats correct
before, i didnt have any problem.
i flashed nordic froyo sbf using rsd, maybe that is the reason?
Sent from my MB525 using xda app-developers app

Related

Stuck in a bootloop!

Just installed Hyperion via Clockwork Mode and I am stuck in a bootloop, could I get some help with this?
Install another rom or the same rom
By reading the installation instruction properly
Sent from my GT-S5360 using xda premium
flash stock Rom using Odin then flash Hyperion again properly or another Rom
This is how to flash stock Rom via Odin
http://forum.xda-developers.com/showthread.php?t=1465800
So 2 android phones walk into a bar
At first i also have bootloops, hmmm try to flash again the same ROM
But this time wipe data/cache in CWM and then boot into recovery then wipe data/cache again then flash
Boncey said:
Just installed Hyperion via Clockwork Mode and I am stuck in a bootloop, could I get some help with this?
Click to expand...
Click to collapse
*flash a stock rom
*wipe ur ext partition if u have it (using link2sd)
*then flash Hiperion
oh, it's you again u made it.
*flash with stock rom using Odin
*flash with CWM that Hyperion (read the instruction carefully on the Hyperion Thread)
goodluck
Did all of that before you guys said, still gives me a bootloop, do I need to root my phone? But, when I root it I can't mount /system or /data or the other one
Boncey said:
Did all of that before you guys said, still gives me a bootloop, do I need to root my phone? But, when I root it I can't mount /system or /data or the other one
Click to expand...
Click to collapse
use another cwm or try cwm_bla_bla.zip
Link meh?
Boncey said:
Link meh?
Click to expand...
Click to collapse
i dont have a link but use the xda search botton it will help u a lot.good luck.
Still nothing :l
STEPS TO FLASH HYPERION (worked for me 100%)
- Flash stock rom via odin
- Reboot and go to CWM
- Clear Data/Reset and Cache
- Mount System/Sdcard/Data/Cache, (Sometimes Data/Cache can't be mounted it is OKAY)
- Flash Hyperion
- DO NOT REBOOT YET
- Go to Advanced
- Boot to Recovery
- Clear Data
- Clear Cache
- Reboot
Try it
Sent from my GT-S5360 using xda app-developers app
Make sure you're in a stock kernel first.
@boncey
Try the instruction provided by jeannuel's
Its working....good
Sent from my GT-S5360 using xda premium

[Q] Revert Defy from Quarx CM10 to CM7.2?

Hello,
I currently have defy with the later lens with the latest Quarx CM10 nightly installed. While CM10 is generally awesome, it turns out to be not stable enough (radio crashing, sudden restarts) and a bit too slow. Now I would like to downgrade to CM7.2.
I tried just flashing CM7.2 after a wipe which yielded a non booting device and me flashing back CM10.
Does anyone have any experience with reverting the Defy to CM7.2?
Thanks for your help!
You should change ext4 format of data to ext3 before flashing cm7.
1. Boot to recovery
2. Wipe Delvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3. It don't show any progress. Wait for few time. It shows done.
5. Flash cm7
IMPORTANT don't attempt another wiping of data/cache after filesystem conversion.
Sent from my MB525 using Tapatalk 2
pradeeppk said:
You should change ext4 format of data to ext3 before flashing cm7.
1. Boot to recovery
2. Wipe Delvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3. It don't show any progress. Wait for few time. It shows done.
5. Flash cm7
IMPORTANT don't attempt another wiping of data/cache after filesystem conversion.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I want to do the same with my green lenses. I have CM10-2nd boot, should I install CM7.2 for defy+ or just regular defy?
thanks in advance.
I don't know WHY all this redundant question? Is so hard to search a little? This problem was debated by enough time.
Sorry, I did search and found just this thread...
Just tried here, and cm7.2 for Defy+ worked just fine.
Hmmmm, last time I had to do this I reflashed a stock Froyo rom and did the whole process of rooting/installing 2ndinit/installing CWM again. Installing CM7 then wiping dalvik/cache/data did not work.
If a simple flash/wipe doesn't do the job, reflash Froyo again and follow the instructions to install CM7.
I haven't got the option in Tools to format in EXT3, there's only options to share SD, drivers, systems... Why?
I'm using a Quarx CM10-20120924-NIGHTLY-mb525.
Maybe I need to upgrade to CM10.1 to have that option? Which ROM could be good?
I'm using a Defy (mb525)
Miguemiguemigue said:
I haven't got the option in Tools to format in EXT3, there's only options to share SD, drivers, systems... Why?
I'm using a Quarx CM10-20120924-NIGHTLY-mb525.
Maybe I need to upgrade to CM10.1 to have that option? Which ROM could be good?
I'm using a Defy (mb525)
Click to expand...
Click to collapse
Just wipe from STOCK recovery .. it will format partitions to EXT3 and CM7 should boot =)
yzeroy said:
Just wipe from STOCK recovery .. it will format partitions to EXT3 and CM7 should boot =)
Click to expand...
Click to collapse
Wipe from STOCK recovery and then go to Custom recovery and flash directly the rom?
Miguemiguemigue said:
Wipe from STOCK recovery and then go to Custom recovery and flash directly the rom?
Click to expand...
Click to collapse
No just install CM7, GAPPS, and reboot to Stock recovery and there do Factory reset and reboot.
Now your CM7 should boot
Similar, but a little different
My requirement is to give CM 10.x one more try, this time with a clean install.
So, what should I do?
I posted here: http://forum.xda-developers.com/showthread.php?t=2192807
Do I need to use stock recovery, format, install SBF and then install the latest nightly?
Or something else as well?
s_u_n said:
My requirement is to give CM 10.x one more try, this time with a clean install.
So, what should I do?
I posted here: http://forum.xda-developers.com/showthread.php?t=2192807
Do I need to use stock recovery, format, install SBF and then install the latest nightly?
Or something else as well?
Click to expand...
Click to collapse
Any thoughts?
CM 10.1 to stock
I have gathered the following instructions so far:
1. Boot to recovery
2. Wipe Dalvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3.
5. Flash stock ROM (Where can I find this?)
Once I am with stock ROM, I would like to install CM 10.1 again, since I am not happy with the performance of the current CM 10.1 (perhaps 2 months old), so I would like to start from scratch.
Am I missing anything important?
Once you wipe data, system and cache in TWRP(of your current installation), your new installation is clean(as it would after stock rom/sbf flash)
You can cross check using the inbuilt file explorer in TWRP
Sent from my MB526 using Tapatalk 2

Unable to flash cm7 kernel

i tried flashing many times cm7 kernel (boot2.tar) via odin but my phone doesn't boot when i enter into recovery it shows unable to mount system unable to mount cache, unable to mount data please tell me what should i do to flash this kernel
EDIT: my problem is solved thanks for help.
Sent from my GT-S5360 using Tapatalk 2
Bro u if u rooted surely u have CWM
Go to recovery mode» CWM»where u find mount/system
Sent from my GT-S5302 using xda premium
djraje said:
Bro u if u rooted surely u have CWM
Go to recovery mode» CWM»where u find mount/system
Sent from my GT-S5302 using xda premium
Click to expand...
Click to collapse
i know that i have cwm whenever i try to mount it shows error unable to mount
Sent from my GT-S5360 using Tapatalk 2
1.flash the kernel via Odin
2.after that remove the battery and boot into recovery mode (after flashing the kernel the phone will not get powered on so don't worry)
3.when you're in recovery mode,go to mounts and storage and format system,data and cache
4.go back and wipe data and cache
5.again go to mounts and storage and mount all the partitions (all 4 should show unmount)
6.go back and flash cm7 rom
7.after flashing wipe data and cache
8.reboot and enjoy cm7!
aniket.lamba said:
1.flash the kernel via Odin
2.after that remove the battery and boot into recovery mode (after flashing the kernel the phone will not get powered on so don't worry)
3.when you're in recovery mode,go to mounts and storage and format system,data and cache
4.go back and wipe data and cache
5.again go to mounts and storage and mount all the partitions (all 4 should show unmount)
6.go back and flash cm7 rom
7.after flashing wipe data and cache
8.reboot and enjoy cm7!
Click to expand...
Click to collapse
after flash via odin i removed battery and reinserted it then i entered into tge recovery i faced the same problem i tried mounting system,data,cache but it shows error unable to mount.
Sent from my GT-S5360 using Tapatalk 2
sanchit0403 said:
after flash via odin i removed battery and reinserted it then i entered into tge recovery i faced the same problem i tried mounting system,data,cache but it shows error unable to mount.
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
-_-
When you enter the recovery mode go to mounts and storage and format system,data and cache and then mount all the partitions..
aniket.lamba said:
-_-
When you enter the recovery mode go to mounts and storage and format system,data and cache and then mount all the partitions..
Click to expand...
Click to collapse
i formated system too but 1 i am still facing this. when i enter into the recovery at the bottom it starts showing unable to mount system,data etc.
Sent from my GT-S5360 using Tapatalk 2
First flash stock kernel and stock rom, and after kernel cm7 and cm7, all with odin
Sent from my GT-S5360 using xda app-developers app
brianmorales said:
First flash stock kernel and stock rom, and after kernel cm7 and cm7, all with odin
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
firstly i flashed stock then i flashed cm7 kernel after flashing kernel i have to flash cm 7 via cwm but i am unable to mount system thats why i am unable to flash cm. Please help me i want to use cm 7 in my phone
Sent from my GT-S5360 using Tapatalk 2
installed some kernel with that of merruk?
Keep trying it in odin, fully installed all stock, and proves that everything works on and, if so, install the cm7 kernel if possible from odin. Then try again to install cm7
Man, try install stock rom in odin. If the phone doesn't boot, remove the battery and enter in CWM stock. Make a wipe in data and restart the phone. The phone will take 5 minutes or more to turn on. Post ur results.
sanchit0403 said:
firstly i flashed stock then i flashed cm7 kernel after flashing kernel i have to flash cm 7 via cwm but i am unable to mount system thats why i am unable to flash cm. Please help me i want to use cm 7 in my phone
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
After flashing cm7 kernel go to recovery mode and format system first then you will be able to mount system. Then format data and cache and mount them all and flash cm7
Sent from my GT-S5360 using Tapatalk 2
you all guys dont get it.. how can you format if he got bootloop.. you can enter in recovery mode but there is an error in mounting.. you cant mount data, cache and system.
Sent from my GT-S5360 using xda premium
---------- Post added at 02:49 PM ---------- Previous post was at 02:45 PM ----------
i dont know if this will work. flash hyperion 8 with savie1 kernel not the hyperioN b2.5 stock based. then flash the cm kernel you want.. via odin or cwm.
someone just told me this but i dont know if this will works. just try
Sent from my GT-S5360 using xda premium
"theviper" said:
After flashing cm7 kernel go to recovery mode and format system first then you will be able to mount system. Then format data and cache and mount them all and flash cm7
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
after formating system i am able to mount system then i installed cm7 but it starts bootloops
Sent from my GT-S5360 using Tapatalk 2
sanchit0403 said:
after formating system i am able to mount system then i installed cm7 but it starts bootloops
Sent from my GT-S5360 using Tapatalk 2
Click to expand...
Click to collapse
Did you format data,cache and mounted them too?
Also which one are you trying 3rd nightly?
Sent from my GT-S5360 using Tapatalk 2

Help. Bricked found the cause

I feel my install storage is corrupted so rsd Is not able to flash things into internal memory. Whatever I flash, even a cmx sbf, I get the same stock android symbol and the checksum verification fails for all except cg31 and cg32. I need to reformat my internal memory before I flash .for the I need custom recovery. With a locked bl, internal memory is not formattable. Exactly my /system partition is corrupted. If there any update.zip which can format /system partition?
Sent from my C6602 using Tapatalk 4
Okay I ve found the options.
1. I need an update.zip which I need to use from stock recovery to format /system
Or
2. I need to format /system through rsd lite..or some other software similar to this? Is there Ny?
Sent from my C6602 using Tapatalk 4
pjgowtham said:
Okay I ve found the options.
1. I need an update.zip which I need to use from stock recovery to format /system
Or
2. I need to format /system through rsd lite..or some other software similar to this? Is there Ny?
Sent from my C6602 using Tapatalk 4
Click to expand...
Click to collapse
Flashing any SBF with RSD will fix your partitions; I know this because I've had damaged partitions before. I don't think a corrupt /system partition is your problem, I think your internal memory might be physically failing.
Why do I get the classic android boot animation whatever sbf I flash? A and I've seen many ppl complaining if boot looping after flashing a sbf if it formats partitions
Sent from my C6602 using Tapatalk 4
pjgowtham said:
Why do I get the classic android boot animation whatever sbf I flash? A and I've seen many ppl complaining if boot looping after flashing a sbf if it formats partitions
Sent from my C6602 using Tapatalk 4
Click to expand...
Click to collapse
I thought you said you weren't getting a boot animation and it was taking you straight to stock recovery? You're going to have explain yourself better. If you're getting a boot loop in the boot animation, and you can still access stock recovery, then through there wipe /data and /cache and it'll boot up. You almost always need to wipe /data after flashing an SBF.
I don't know if it formats partitions or not, I just know that it fixes them.
I ve tried sbf ing with both rsd and sbf flash in linux. Nothing worked.
Wherever sbf I flash, I get one same boot animation bootlooping.
The device fails on checksum verifications during flash. This tells the rsd has problems with internal memory.
If the internal memory has failed permanently, why would it read the bootanimation?.weird
Most probably its corrupted
Sent from my C6602 using Tapatalk 4
Antiga Prime said:
you can still access stock recovery, then through there wipe /data and /cache and it'll boot up. You almost always need to wipe /data after flashing an SBF.
.
Click to expand...
Click to collapse
Ive tried /data /cache wipe through stock recovery.
And defy doesnt flash properly. Every flash fails with checksum errors.
I thought I could access custom recovery if I flash fixed sbf with custom rom but defy acts like sbf is never flashed. Because if I access bootmenu, I can format system partition
Sent from my C6602 using Tapatalk 4
Dfp231 is worth a try
Sent from my MB526 using Tapatalk 2
thekguy said:
Dfp231 is worth a try
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Sure I'll try and let you know
Sent from my C6602 using Tapatalk 4

[Q] Stuck on Boot Animation and can't mount /data

Hey guys,
I was attempting to root my phone so I unlocked the bootloader (using fastboot oem unlock) and flashed CWM recovery (using fastboot flash recovery <filename>.img using version 6.0.4.3). Now, that all worked but when I tried to boot into Android, it got stuck on the boot animation and when I try to mount /data in CWM. I can't do backups because of that problem (namely, it gives me "can't mount backup path") and I don't want to lose all my data. Is there any way of saving this/if I flash a custom ROM, will it erase that data?
Thanks,
Ninja!
Yes wipe /data /cache is required to flash custom roms.
Try to fastboot boot recovery.img and see if it loads /data, and remember to check your bootloader version (not z20i)
Sent from my Nexus 4 using xda app-developers app
zarica said:
Yes wipe /data /cache is required to flash custom roms.
Try to fastboot boot recovery.img and see if it loads /data, and remember to check your bootloader version (not z20i)
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ok, I tried that using the CWM touch recovery image that I had but it still didn't work. My bootloader version is Z30d.
Fixed it by flashing stock ROM.

Categories

Resources