well I have defy green lense... I just flash miui pikachu edition, It was working fine then last night I'd just flash another JB ROM that was working fine... but when I again try to flash pikachu ROM it was stuck on motorola M logo no blue LED turn on ....after that I flash a fixed sbf "4.5.3-109-fixed.sbf" this one....
the problem is same no blue LED turn on ... Please let me know how I can get CMW again .. step by step procedure needed. Thanks!
Note: I was using GB kernel 3.4.7
Your 2ndinit got wiped, hence no blue LED. If you can boot into the stock ROM, you need to root it and install 2ndinit apk(just search for 2ndinit defy on Google) and install your custom recovery again. After this you will get the blue LED again
Sent from my MB526 using xda premium
thekguy said:
Your 2ndinit got wiped, hence no blue LED. If you can boot into the stock ROM, you need to root it and install 2ndinit apk(just search for 2ndinit defy on Google) and install your custom recovery again. After this you will get the blue LED again
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I cant boot into stock ROM, phone stuck on motorola M logo..... Can I flash full sbf again, coz I was on fixed GB sbf?
slhysf said:
I cant boot into stock ROM, phone stuck on motorola M logo..... Can I flash full sbf again, coz I was on fixed GB sbf?
Click to expand...
Click to collapse
Get into stock recovery by keeping volume down pressed when powering the phone.
When you see a triangle with excl. mark press volume down and up at the same time
Wipe data and cache
If above doesn't work flash proper full sbf and repeat the procedure
You're stuck on red logo as you have not wiped data from stock recovery, and instructions are /\
Sent from my MB526 using xda premium
Hi all!
Almost all ROMs out there are failing to work correctly or even boot on my Defy (red lens). Some do boot, some go to bootloop.
Here's the full story. Two days ago the latest CM10 nightly from Quarx went to bootloop, it was working just fine, but at some point the phone rebooted and didn't boot back up.
I've decided to try another ROM and installed WIUI v4 (JB) from CWM. I went to check device's internal memory and it appeared that I had 48 MB used and that that was all internal memory - the system hasn't even loaded total memory info.
I performed some search and found this thread with the similar issue: http://forum.xda-developers.com/showthread.php?t=1940503
It suggested flashing an SBF via RSD Lite. I did that using the SBF from that thread (2.2 CEE Froyo). I suppose that was my mistake since the thread referred to Defy with a green lens. However, I was finally able to boot the device. I decided to try another SBF. JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDN to be precise. Everything went just fine. I was able to root the device, install CWM using SndInitDefy 2.0, and install stable CM7 (the official one, update-cm-7.1.0-jordan-signed.zip) and Froyo kernel from WIUI.
Everything was working fine except for the camera. It was showing the following error:
"Camera error. Cannot connect to camera"
After that I though that maybe I've messed up with SBF versions. The phone is not sold in Ukraine officially and I didn't remember which SBF it used when it was shipped.
I then followed the guide from All-in-one beginners guide and installed that Chinese SBF with Version 5 CG (thus I presume I can't flash any full SBF now since this will cause a black screen and I will have to re-flash 97.21.51 SBF and do all that stuff all over). Again, I was able to root the phone and stuff. However, none of Quarx's nightlies are working, CM7.2 or 2nd-boot CM10 are simply bootlooping, WIUI v4 can't connect to any of Google's services (they constantly FC), and none of the ROMs can connect to the camera.
Currently I'm using the following:
official CM7.1.0
Android 2.3.7
kernel [email protected] #1
Build number Gingerbread GWK74
I'm okay with staying on CM7.1, but I require the camera to work. So, the question is, what should be done in order to make the camera work?
Maybe, I should change some lib files, if so, could you please provide with the link to the correct ones? I've already tried some camera fix SBF's but they didn't seem to work. If there is any additional information required, please let me know.
Any help will be really appreciated!
Thank you in advance.
Maybe you could get rid of the sbf problem(camera issue caused by wrong flashing) by flashing a defyplus sbf with group code 6. Then your camera should work.
Sent from my MB526 using xda premium
Thanks, thekguy! Will try this later today.
Nope, that didn't work, unfortunately. Flashed 4.5.1-134_DFP-125, but the camera is still failing, as well as the latest CM10. Any suggestions are welcome.
Hmm, latest cm10 2ndboot right? That's a very bad sign, since that rom indeed works with both the camera modules, and its really curious that it's not working.
Flash back to any defy bl6 sbf from this list(don't flash defy+ sbf since that approach isn't working):
http://forum.xda-developers.com/showthread.php?t=966537
Wipe data, and use the defy ultimate wiper script(it's there in themes and apps section, use ext4 version if you're on cm10 or ext3 for any other rom).
Now flash cm10 2ndboot build, and try using the camera.
Normally that should work, even if you have a green lens module, but if not so then it could be add a result of a hardware failure
Sent from my MB526 using xda premium
Yeah, I've also tried CM7 for Defy+, but that didn't work either. And I guess I pushed my device few steps closer to the brick yesterday. I flashed one of Chinese SBFs (JRDNEM_U3_3.4.3-36-1_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTINT_P011_A013_HWp3_Service1FF). It's BL7 SBF and it's known for its outstanding unbricking abilities. Didn't work for me. However, the bootloader is still accessible and I will keep playing with the phone today.
I'm getting tired of all this.
Didn't work? Camera or unable to boot?
Remember, you must wipe data from stock recovery before you can boot into the stock rom
Once you are running on the stock rom, check if the camera works. If not then follow my other post about getting to cm10 2ndboot. It may hang once on boot but it will boot after that. If still the camera is not working then I'm afraid it's beyond help
Sent from my MB526 using xda premium
thekguy said:
Didn't work? Camera or unable to boot?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Didn't boot at all, just a blank black screen. I can't enter stock recovery and the bootloader is not visible. However, if I boot up with power+vol+ and connect the phone to the desktop, RSD Lite detects the phone and I can flash an SBF. But my guess is that this would be useless since the last SBF I flashed was BL7.
Well, I'm at work right now, thus I can't try anything out right now. Theoretically, I should be able to flash any SBF with BL7, and root it using this guide http://forum.xda-developers.com/showthread.php?t=1542956
Then, flash both sbfs from that guide, and it should work.
You shouldn't get any blank screen, simply because you've got the highest possible group code, and you cannot have a wrong kernel just after flashing the sbf. It must work
Sent from my MB526 using xda premium
Thanks. Will definitely give it a try once I get home.
OK, I've managed to install 4.5.1-134 DFP-231 Retail.en.EU CEE, root it, and flashed CM10 2nd-boot nightly. However, I'm still unable to boot the phone. It shows CM10 logo spinning for 10-20 seconds and then reboots. I assume that this is the only ROM which can make the camera work. Am I right? If yes, what should I check or do in order to fix the boot looping? If I can use some other ROM, could you please let me know which one exactly and what can be done in order to fix the camera?
Thank you!
Just flashed CM10 and checked the log, there's the following message:
set_perm: chown of /system/xbin/tcpdump to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/tcpdump to 6755 failed: No such file or directory
Click to expand...
Click to collapse
Could this be a source of the problem?
Another update. I've installed WIUI v4 for GB kernel and looks like it requires less internal memory/RAM to run so I'm able to boot the phone completely. And it's showing that I have 0.00 MB of internal storage in total and 58 MB used. I guess internal memory issue is somehow related to the bootloop.
Before flashing cm10, use both the ultimate wiper scripts(ext4 and ext3 version)
After flashing cm10, go back to boot menu and select tools, file system tools and format to ext4. It should boot now
Sent from my MB526 using xda premium
Thanks for the clue, but I'm afraid that didn't work. Since I had some time and have no data to lose, I wiped the phone from stock recovery, flashed both standard 4.5.1-134 DFP-231 and rooted 4.5.1-134 DFP-231, wiped everything using both ext3 and ext4 Ultimate scripts, flashed Quarx's 2nd boot CM10, formatted data and cache to ext4 using File System tools. CM10 still bootloops, but at least now I have internal memory info displayed correctly in WIUI v4 (JB). But since it's not a 2nd boot ROM, the camera isn't working.
In fact, I've tried some other 2nd boot scripts (NEGAN-6DIC and Codenameandroid 3.6.6), but they are bootlooping as well.
Maybe there are some other 2nd boot ROMs I should check? Or maybe if I get a nandroid backup of a working system I could restore it on my phone?
Try converting to ext4 and flash after that. It is really curious why it bootloops. You must get cm10 to boot, so that the camera works. Look here for downloading a stock kernel that should hopefully fix the boot loops.
http://forum.xda-developers.com/showthread.php?t=1909242
Scroll down for the post which talks about having a compatible stock kernel which should allow 2ndboot to work(it's titled for bl7 users).
Flash this kernel after stock sbf flash, then try installing cm10.
Let's see how this goes
Sent from my MB526 using xda premium
Still no joy. Neither formatting, nor following this guide http://forum.xda-developers.com/showthread.php?t=1909242 worked. Is there a way to see boot log from a desktop? I have both Debian and Win7 on my desktop.
Thanks.
There is a way to debug using uart, but I have no experience with it. So, sbf flash+ compatible stock kernel failed? Please describe the boot loop. Does it reach the cyanogenmod logo? Or stuck at red Motorola logo? I am at my wits end at this one. All my semi bricks and other problems I could fix by the methods outlined in my previous posts, but they don't seem to work in your case. You flash full sbfs right? And are you able to boot the stock Rom?
Sent from my MB526 using xda premium
Here's how it loops:
- the phone starts
- shows red Moto logo
- blue led
- red led
- blank black screen
- HW buttons blink once
- CM10 spins for approx 5-10 seconds
- the phone restarts and all the steps repeat
Yes, I'm able to flash full SBF (BL7 ones). I'm able to boot into a stock ROM, I can flash modded SBF for BL7 (the rooted one). I've tried flashing CM10 SBF, but the phone booted into a bootloader and showed an error, with set of numbers. Looks like because of the kernel (my guess is that SBF contains non-2nd boot version of CM10).
If I install WIUI v4 right after I flash rooted SBF I have no issues with the internal storage.
If I install 2nd boot CM10 (Kayant's, Quarx's) I get a boot loop (Ultimate Wipe doesn't help)
If I install WIUI v4 after CM10 (without re-flashing SBF's), I get 0.00 internal storage, but wiping data/cache from stock recovery solves the issue.
Unfortunately, wiping data/cache from stock recovery doesn't do the trick for CM10 2nd boot builds.
One more thing, after I flash CM10 and try to wipe data/cache from stock recovery for the first time, it shows recover log errors. There are errors when entering stock recovery after that.
Might be a false trail, but what about wiping from custom recovery? Dalvik cache wipe?
This indicates that the kernel had loaded before some other problem caused the phone to enter into boot loop. What about the camera in the stock build? Same error as before?:banghead:
The cm10 sbf probably had a lower group code(bl6 perhaps) hence that approach won't work, and even discarding that it will yield the same results as before.
Also, in stock, check if the kernel version changes after you flash the compatible stock kernel from the thread I had mentioned earlier. This is important because otherwise there is no chance for cm10 to boot.
Sent from my MB526 using xda premium
(i read many threads relating my issue but they were not same, they was little difference in the problem. and i also tried there solutions but no improvement. so i decided to ask in a thread)
i was using defy+ with CM7 rom.
I installed this rom on my defy+
http://forum.xda-developers.com/showthread.php?t=2044797
first it booted and was working but after rebooting it resulted in boot loop .
( it shows Motorola sign then shows rom animation within few seconds is resumes rom animation and it keeps repeating animation.)
i waited for it an hour but is didn't go well.
then i tried restoring my old rom using CWM but i was unable to restore it is also resulted in same...
then i tried installing sdf using rsd but i have no improvement....
Now i can only go to bootloader version 09.1 and i says battery is low , can't program . i put the charger for whole night but i still says battery low can't program
can you please help me solving this problem
After installing that Rom you needed to enter boot menu and format data to ext4. Now, if you're unable to flash any sbf due to low battery then refer here: http://forum.xda-developers.com/showthread.php?t=892026
Or if you have access to another defy then use its battery and flash the sbf. Wipe data from stock recovery if you run into any issues after sbf flash
As stated below dalvik cache should be wiped, and data is automatically wiped when you format it to ext4 as stated above
Sent from my MB526 using xda premium
thekguy said:
After installing that Rom you needed to enter boot menu and format data to ext4. Now, if you're unable to flash any sbf due to low battery then refer here: http://forum.xda-developers.com/showthread.php?t=892026
Or if you have access to another defy then use its battery and flash the sbf. Wipe data from stock recovery of you run into any issues after sbf flash
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Or in other words you need to wipe data/cache and dalvik BEFORE and AFTER flashing the custom ROM (neagan or other). For now charge the battery and do the sbf flash. Pay attention at the "optional" indications. It better to do it.
CWM is missing
using your link i can solve the problem
but i dont have CWM so i cant wipe delvik data/cach
i only have bootloader
i only can go to bootloader and can't do any thing else. because CWM is removed.
tell me if you have any information about to do something using bootloader..
Do it from stock recovery, data wipe and cache wipe
Sent from my MB526 using xda premium
From stock recovery (bootloader) you will format as ext3 but is better to format in ext4 and that can be done from custom recovery. For that you have to install 2init and run it.
He's unable to boot...boot loop was before battery issue
Sent from my MB526 using xda premium
thekguy said:
He's unable to boot...
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Yes because of low battery. Software solution is ... after charging.
where is stock recovery??
how to boot in stock recovery??? sorry I dont know if there any stock recovery is existed...... ( i tried different buttons while Motorola sign but i got nothing except bootloader and download mod)
tell me i think i can do it using stock recovery
because there is no problem in bootloader. even i am able to flash new SDF.
it makes trouble in loading ROM....
what do you think?
battery is working now
thekguy said:
He's unable to boot...boot loop was before battery issue
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
i solved this problem using universal charger. i pulled off the battery and put in universal charger and charged it for two hours.
stock recovery?
now i just need to know how to boot in stock recovery???
AW: [Q] Defy+ not loading any rom.
There is a beginner guide anywhere in xda/defy sektion
You should read it
MB525 red lense
stock recovery?
i just need to now how to go into stock recovery?
How do I enter Recovery Mode?!: With the Phone off press VOLUME DOWN then, while still pressed, power up the phone and leave VOL key pressed until you see a Yellow triangle, once you see this you are in Recovery now press Vol Up and Vol Down at the same time (if you are in Froyo) and the menu will appear, if you are on Éclair the menu should appear without having to press anything.
copy/paste from this thread.
thanks
Thanks bros
I recovered my phone and i is running with CM7 and i am not gonna try CM10 again until it comes with all bug fixes..
thanks again for your help..
hey guys, i finally need some help with my phone before i'll totally destroy it.
i was on cm-10-20130709-NIGHTLY-mb526 and installed the newest blechdose kernel, 30.08 i think.
it worked pretty well until i had some very random freeze while using the browser.
rebooting turned into a bootloop, i tried to wipe cache and dalvik then, after another reboot it took me to this "optimizing apps" thing, where it stuck again on "starting apps".
i managed how to get into custom recovery and did a system wipe, i thought thats the same as factory reset, but it turned out that it wasnt..
so the situation now is, that the phone is stuck on the standard boot logo after turning on, i cannot get into custom recovery anymore, just stock recovery works.
whats the best workaround for this ?
thanks for helping!
Sbf flash is the only thing which will revive your phone
Sent from my MB526 using Tapatalk 2
thekguy said:
Sbf flash is the only thing which will revive your phone
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
how can i do that? via stock recovery or rsdlite?
i'm trying to get rsd lite to work right now
.jano said:
how can i do that? via stock recovery or rsdlite?
i'm trying to get rsd lite to work right now
Click to expand...
Click to collapse
You need to wipe data and cache through stock recovery and then flash sbf using rsdlite.
thanks for your help its working again