Hello,
I was running CM7.2 but had an issue so I flashed back to the stock rom. Now I'm trying to flash a new custom rom but for some reason 2ndinit is not working.
I rooted and installed the recovery menu from 2ndinit, but I am not seeing a blue light on bootup.
The phone boots into the stock rom just fine, but I cannot get into the recovery menu.
Any help?
Problem
Cannot access ClockworkMod Recovery menu after installing 2ndInit
What I've tried
Wiped SD
Wiped Data
Reflashed JORDN_U3_6.36.0
Rooted
Installed 2ndinit 2.3
Still no luck, upon boot there is no LED. If I hold the down volume for the entire boot I am met with an android exclamation mark.
Update...
I was able to access an old version of CWM v2.5 using 2ndinit 2.0.
But that brings with it a new set of problems. When trying to access the SD card from CWM, it cannot mount it.
Using ADB and the commands in this forum (forum.cyanogenmod.com/topic/33179-problems-installing-71-recovery-cant-mount-sdcard/) I was able to mount the SD and install CM7.2.
Now I am having GPS and 3g connectivity issues with CM7.2 that I've never had before. It makes me wonder if that hack way of mounting the SD messed up the installation?
I am using the US T-Mobile 3.4.2-107-9 baseband.
Takkun88 said:
Hello,
I was running CM7.2 but had an issue so I flashed back to the stock rom. Now I'm trying to flash a new custom rom but for some reason 2ndinit is not working.
I rooted and installed the recovery menu from 2ndinit, but I am not seeing a blue light on bootup.
The phone boots into the stock rom just fine, but I cannot get into the recovery menu.
Any help?
Problem
Cannot access ClockworkMod Recovery menu after installing 2ndInit
What I've tried
Wiped SD
Wiped Data
Reflashed JORDN_U3_6.36.0
Rooted
Installed 2ndinit 2.3
Still no luck, upon boot there is no LED. If I hold the down volume for the entire boot I am met with an android exclamation mark.
Click to expand...
Click to collapse
Hi there. Any luck getting this to work, as i have the same issue.
I rooted the phone, then installed 2ndInit and when i reboot it has no blue light. When i run the Defy 2mdInit in android it lights up red, then goes green, so appears to be doing all right stuff.
A silly question but one i cant find a answer too, is how to reboot! Im holding down the power button, then selecting power off. Once off i power on again, now technically thats a cold restart. Is there a different method to rebooting/restarting once the green light is on?
Many thanks.
Twister42ZA said:
Hi there. Any luck getting this to work, as i have the same issue.
I rooted the phone, then installed 2ndInit and when i reboot it has no blue light. When i run the Defy 2mdInit in android it lights up red, then goes green, so appears to be doing all right stuff.
A silly question but one i cant find a answer too, is how to reboot! Im holding down the power button, then selecting power off. Once off i power on again, now technically thats a cold restart. Is there a different method to rebooting/restarting once the green light is on?
Many thanks.
Click to expand...
Click to collapse
If you just want to install a custom rom, like cm7 then you don't need to go through that process. You could try this method instead http://forum.xda-developers.com/showthread.php?t=1787541
Please note: This method does not work for BL7 bootloader.
pravarth said:
If you just want to install a custom rom, like cm7 then you don't need to go through that process. You could try this method instead http://forum.xda-developers.com/showthread.php?t=1787541
Please note: This method does not work for BL7 bootloader.
Click to expand...
Click to collapse
Hi There Pravarth.
Im completely new to all this, and this will be the first phone i mod. All i would like to do is install CM 10.2 (Android 4.3) and overclock to 1.0Ghz.
I know the Kernel needs to be changed to overclocking from what i read, so if i do the ROM update via this method, is there a option to overclock then too?
Is there a known issie with 2ndInit not doing the blue light on a reboot?
Many thanks.
Twister42ZA said:
Hi There Pravarth.
Im completely new to all this, and this will be the first phone i mod. All i would like to do is install CM 10.2 (Android 4.3) and overclock to 1.0Ghz.
I know the Kernel needs to be changed to overclocking from what i read, so if i do the ROM update via this method, is there a option to overclock then too?
Is there a known issie with 2ndInit not doing the blue light on a reboot?
Many thanks.
Click to expand...
Click to collapse
First of all, do you have a defy or defy+? Because some methods dont work for defy+
Then you should probably read this if you new to flashing: http://forum.xda-developers.com/showthread.php?t=1216982
I also suggest going from stock to cm7 and then cm10.2
Cm10.2 is overclocked to 1ghz by default. You dont have to do anything
pravarth said:
First of all, do you have a defy or defy+? Because some methods dont work for defy+
Then you should probably read this if you new to flashing: http://forum.xda-developers.com/showthread.php?t=1216982
I also suggest going from stock to cm7 and then cm10.2
Cm10.2 is overclocked to 1ghz by default. You dont have to do anything
Click to expand...
Click to collapse
Hi again.
I have a Defy with no moto blur and a red lens.
I have read a lot about flashing, and downloaded all the files i needed, rooted the phone then first problem came getting 2ndInit. I was having issues with the phone resetting when connected via usb so got the SndInitDefy_2.3.apk which runs fine, goes through all the steps, red light becomes a green light and says success. But then when i reboot it never shows the blue light.
Also a lot of these guides are Windows based and i dont use Windows i use Linux.
What are the benifits of going to CM10.2 via CM7, is there a reason for this?
Am i rebooting the correct way by doing a shut down then starting the phone again? Is there no way to do a hot reboot rather than a cold reboot?
Thanks again for your replies.
I don't know what went wrong, you should have been able to see the blue led. But, it's much easier to recover by flashing the easy recovery sbf. Then reboot to recovery and flash cm7. I say flash cm7 because the new cm10.2 has a newer version of update-binary so it wont flash successfully.
You need cm7 just for the CWM and bootmenu, from there you can flash cm10.2
You can use this method to flash sbf using linux http://forum.xda-developers.com/showthread.php?t=1076138
pravarth said:
First of all, do you have a defy or defy+? Because some methods dont work for defy+
Then you should probably read this if you new to flashing: http://forum.xda-developers.com/showthread.php?t=1216982
I also suggest going from stock to cm7 and then cm10.2
Cm10.2 is overclocked to 1ghz by default. You dont have to do anything
Click to expand...
Click to collapse
Hi.
I seem to be having more success now, i got SndInit1.4.apk and now it gives the blue light and im in the BootMenu!
So maybe the new version has some issues!
---------- Post added at 05:55 PM ---------- Previous post was at 05:01 PM ----------
Well im now ablle to at least get the bootmenu, however everything is there but it wont mount my sd card. Its shows the following..
ClockworkMod Recovery v2.5.1.8
E:Can't mount /dev/blocl/mmcblk0p1 (or /dev/blocl/mmnblk0)
(No such file or directory)
E:Can't mount /sdcard
Any ideas what is causing this problem?
I did try with another SD card, tried a smaller one thinking its a size issue, then formatted it too and same error message comes up.
Hope im giving enough info, but thats all i can see. Thanks again.
Twister42ZA said:
Hi.
ClockworkMod Recovery v2.5.1.8
E:Can't mount /dev/blocl/mmcblk0p1 (or /dev/blocl/mmnblk0)
(No such file or directory)
E:Can't mount /sdcard
Any ideas what is causing this problem?
I did try with another SD card, tried a smaller one thinking its a size issue, then formatted it too and same error message comes up.
Hope im giving enough info, but thats all i can see. Thanks again.
Click to expand...
Click to collapse
So, I'm guessing you flashed froyo, root and then sndinit? Did you try the easy recovery method?
While I've had similar issue before, I would just assume it was some bad flash and start over. Never wondered why it would happen. It is quite a pain. But most importantly, make sure the battery doesn't go low otherwise it wont allow you to flash.
Usually all such problems go away if you return to stock and try again
Here's what I usually do: Flash froyo stock + super one click to root + 2ndinitdefy2.0apk (It has the new version of CWM). Then flash cm7
OR
Flash froyo stock + easy recovery sbf. Then flash cm7 from stock recovery
Hope this works
Your link to everything about the Defy was very helpful and informative.
Im still on Eclair which seems like that might be the problem, so i guess i need to get Windows...i do have a old Windows XP so will find that old hard drive and boot into that then try the SDlite app and try install a stock 2.2 rom.
At the moment it has a French rom, in English though, so will try find a 2.2 French rom sbf. I think the issue might be 2.1 not being able to use the SD card like 2.2 and up does. Also 2ndInit v2.3 does not work, any other lower version does work, but gives a sd card error.
So my bext question, where do i get a standard 2.2 french rom? There is a link on here, but its the Orange version, not sure if that will be ok.
All i did was root, then 2ndInit. Rooting was a knightmare, eventually used the Motorola1Click Root and that worked, nothing else worked.
Thanks for all your help, knowing all the technical stuff is one thing, knowing all the orders, files and so on is another.
Related
Good day everyone! I would like to ask for some help if it wouldn't bother.
I previously have WajkIUI 1.10.21 installed on my 2nd init. I have installed the Multiboot plugin (http://forum.xda-developers.com/showthread.php?t=1364659) and installed the CM9 12-2-2012 build on 2nd boot.
However when I updated the 2nd boot to CM9 12-11-2012 build, the 2nd boot stays stuck on the red M logo. Because of that, I installed the "kernel" on 2nd boot which was supposed to boot the build. Unfortunately, it only resulted to a boot loop for my CM9.
When I tried to boot from 2nd init (which still has my WajkIUI), it suddenly stopped booting as well. I tried to recover using my recovery file but to no avail, 2nd init still won't boot.
So my phone's condition now is: it is able to run CWM recovery on both 2nd boot and 2nd init. Will I still be able to boot my 2nd init? Will I still be able to restore to my latest recovery file? If yes, can anyone guide me on how to fix my 2nd init boot?
Thank you very much everyone!
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
esok44 said:
I think its mentioned in the defy cm9 thread.
Its not possible to flash any newer version including 111207 in second Boot.
i think i made the same mistake too...
but i dont know wether i had to reinstal primary boot...
you could try to flash miui on primary boot so that you can do atleast anything...
if you want cm9:
wipe everything
instal cm9 111207.zip
instal cm9 111213.zip
im using cm9 and everything is great, except camera, wich in fact isnt working at all
hope it helped, greetz esok
Click to expand...
Click to collapse
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
arvs0z said:
Thanks! Now I'm running the Dec13 build
I guess it's about the kernel which messed up. Motorola is so *** for locking the bootloader.
Anyway, thanks again! I'll try to install multi boot again and install Wajkiui on 2ndboot )
Click to expand...
Click to collapse
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
esok44 said:
Think this doesn't work either, because of the Kernelchange
but maybe you could post the result of this test.
Would like to install cm7 as second boot, cause of the camera and all my old data
Click to expand...
Click to collapse
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
arvs0z said:
Yes, apparently installing a 2.2 based rom on the virtual system doesn't work (won't get past the M logo again) even when I apply the 2.2 kernel on the virtual system.
So I guess we're stuck on manually choosing our main rom. I also have my data on my older rom (not to mention, app highscores, etc) and I miss my defy's camera, but the ICS rom is so hard to resist.
Click to expand...
Click to collapse
Yeah it is....
AHHHHH damn it.
hmmmm well nevermind, think i will stay with ICS...
titanium backup works, so maybe as a tip for you:
install old rom,
make backup,
install ics,
restore backup,
some data may be back
Yes, I tried that before but for some reason, during restore, Ti force closes on my ICS.
Anyway, I'm fine without my old data for now Thanks Esok
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
die2mrw007 said:
same issue here
did wipe data and cache
install from sd
selected CM7.zip
finding update package
opening update package
opening update package
installing update
done
cynogen mod splashscreen appeared
waited for 20 minutes..and still at splashscreen
what to do ?
---------- Post added at 08:21 PM ---------- Previous post was at 08:06 PM ----------
any help ?
Click to expand...
Click to collapse
try removing the battery. then put it back in and power up. see if it boots up. depending on which cm7 rom you were using, there's a known "stuck in boot" problem and removing battery method will overcome it.
^ Yes, try removing the battery and restarting the phone. One other solution could be applying the 2.2 Kernel after the installation of CM7 (only if you are using Defy and the base ROM of CM7 is 2.2) because I tried installing a CM7 nightly and had to apply the kernel
Kernal
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
phatboyjr said:
I have a Defy I tried flashing to a few different versions of CM7, but it keeps stopping on the boot logo. I tried flashing from stock, so do I have to change my kernal? If so, how?
Click to expand...
Click to collapse
are you saying you were still on stock rom and you tried to install cm7? what was your stock rom and have you flashed any full sbf? what were the steps you did to install cm7?
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
to install CM7 follow the steps in this faq :
http://forum.xda-developers.com/showthread.php?t=1065798
phatboyjr said:
Yeah, I was running the stock 2.2 and tried installing CM7.
I rooted my phone, then installed 2ndinit boot loader. Wiped caches/factory reset and used CWM to install from a .zip file on the SD card.
No idea how to set up RSDLite..
Click to expand...
Click to collapse
so far so good. could be the rom you were flashing. were you trying to flash the nightlies by any chance? all the latest nightlies do not come with the kernel. you either have to flash the stable release first, or the cm7-kernel-signed.zip, inorder to have the correct kernel before you can flash the nightlies.
do not flash any full gb sbf or you can get yourself in trouble.
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Do you still see the blue led for custom recovery?
Hmetool said:
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Click to expand...
Click to collapse
You will need to flash a new SBF with RSD lite
follow instructions in this thread
How to flash new SBF
Hmetool said:
I've just tried upgrading to ICS and failed. Apparently I flashed the wrong kernel - should have flashed the CM7 one, but flashed the CM9.
Now my Defy is stuck on the Google logo and I don't know how to reach recovery mode. Pressing Power+voldown does nothing. Power+volup gives me the bootloader, which asks me to connect a usb cable, but I have no idea what to do after that.
I have two Nandroid backups: one stock (2.2) and another with CM7 (2.3.7). My Defy has a green lens.
Is there any way to restore my phone to one of those backups?
Thanks in advance
Click to expand...
Click to collapse
Do not flash any sbf's. Reboot the phone, at the blue led press Vol- and when you get into boot menu, flash the correct kernel. If you flashed Defy build, flash CM7 (Froyo) kernel. If you flashed the Defy+ build, flash CM9 (Bingerbread) kernel.
fiskenigaten said:
Do you still see the blue led for custom recovery?
Click to expand...
Click to collapse
I see the blue led, but it goes on to green regardless of what I do (power+voldown does nothing). I've tried to access recovery mode several times, but the phone doesn't respond. Maybe I'm doing something wrong.
rperdue5 said:
You will need to flash a new SBF with RSD lite
follow instructions in this thread
How to flash new SBF
Click to expand...
Click to collapse
I've read the guide, but my original SBF is missing ever since MegaUpload's demise. Is it possible to use the Nandroid backup instead?
Auris 1.6 vvt-i said:
Do not flash any sbf's. Reboot the phone, at the blue led press Vol- and when you get into boot menu, flash the correct kernel. If you flashed Defy build, flash CM7 (Froyo) kernel. If you flashed the Defy+ build, flash CM9 (Bingerbread) kernel.
Click to expand...
Click to collapse
Ok, apparently I wasn't pressing the button at the right time. Recovery mode is now working. However, I don't have the correct kernel in my SD card - only the wrong one.
My Nandroid backup seems not to be working too, apparently. I went into recovery and restored it, but boot still doesn't work. I wiped data/cache/dalvik cache and tried again, but it still didn't work. I'm at a loss here.
Should I try to flash some other sbf, since I can't find my phone's stock one?
Hmetool said:
Ok, apparently I wasn't pressing the button at the right time. Recovery mode is now working. However, I don't have the correct kernel in my SD card - only the wrong one.
My Nandroid backup seems not to be working too, apparently. I went into recovery and restored it, but boot still doesn't work. I wiped data/cache/dalvik cache and tried again, but it still didn't work. I'm at a loss here.
Should I try to flash some other sbf, since I can't find my phone's stock one?
Click to expand...
Click to collapse
go to ICS thread and on the first post there is a link to signed CM7 kernel zip..copy it to ur sd card and flash it..
arpith.fbi said:
go to ICS thread and on the first post there is a link to signed CM7 kernel zip..copy it to ur sd card and flash it..
Click to expand...
Click to collapse
I just tried installing the zip from the sdcard, but I got an error message: "Can't make /tmp/update_binary. Installation aborted". It seems that I can't install any zip now.
Is there any way out of that? I'd be more than happy if I could just flash my nandroid backup, even if that means being stuck without ICS for a bit more time.
I'm on ClockworkMod Recovery v2.5.1.8, if that helps.
Hmetool said:
I just tried installing the zip from the sdcard, but I got an error message: "Can't make /tmp/update_binary. Installation aborted". It seems that I can't install any zip now.
Is there any way out of that? I'd be more than happy if I could just flash my nandroid backup, even if that means being stuck without ICS for a bit more time.
I'm on ClockworkMod Recovery v2.5.1.8, if that helps.
Click to expand...
Click to collapse
Hi,
I faced a similar issue but it was since I flashed CM9 for Defy in my Defy+ with 2.3.6(stock) ! Nothing was working and I would get some boot errors! I rectified it by flashing full SBF and then rooting. Well if you want I can provide you with the SBF I have but it is for 2.3.6 and so you will loose downgradability. I have 4.5.1-134-DFP-1321 - retail-asia full Blur multilanguage with me. However, you can also give Walter's fixed SBF and Nandroid backup a try
Thanks, it turns out that flashing a sbf was a nice way out of this mess. I flashed a 2.2.2 which is almost identical to my stock rom (couldn't find that one).
If I root my phone now, can I still try to restore my nandroid backup? Or should I just skip that and try flashing ICS again?
My SD card has the 03-19 CM9 Nightly, gapps and both CM9 and CM7 signed kernels. Should that suffice? CM7 kernel is the right one for green lens defy, right?
Hmetool said:
Thanks, it turns out that flashing a sbf was a nice way out of this mess. I flashed a 2.2.2 which is almost identical to my stock rom (couldn't find that one).
If I root my phone now, can I still try to restore my nandroid backup? Or should I just skip that and try flashing ICS again?
My SD card has the 03-19 CM9 Nightly, gapps and both CM9 and CM7 signed kernels. Should that suffice? CM7 kernel is the right one for green lens defy, right?
Click to expand...
Click to collapse
If you are on a green lensed Defy, then yes - flash CM7 signed kernel and one of the Froyo bulds of Quarx or Epsylon3 - try them all if you wish and see which one you like the most.
Procedure is easy:
1. Full wipe
2. Flash CM7 kernel
3. Flash ROM
4. Flash gapps
5. Full Wipe
6. Reboot
When you decide to try a new ROM, there is no need to flash the kernel again, just wipe, flash the new ROM and gapps and then wipe again.
Auris 1.6 vvt-i said:
If you are on a green lensed Defy, then yes - flash CM7 signed kernel and one of the Froyo bulds of Quarx or Epsylon3 - try them all if you wish and see which one you like the most.
Procedure is easy:
1. Full wipe
2. Flash CM7 kernel
3. Flash ROM
4. Flash gapps
5. Full Wipe
6. Reboot
When you decide to try a new ROM, there is no need to flash the kernel again, just wipe, flash the new ROM and gapps and then wipe again.
Click to expand...
Click to collapse
Thanks, that's great. Are all regular Defy roms Froyo builds unless stated otherwise? I couldn't find that info on the files I have.
One question: by full wipe you mean data/cache/dalvik cache or is there anything else that I'm missing?
Hmetool said:
Thanks, that's great. Are all regular Defy roms Froyo builds unless stated otherwise? I couldn't find that info on the files I have.
Click to expand...
Click to collapse
Yes, "Defy build" means Froyo kernel based, "Defy+ build" means GB kernel based.
Hmetool said:
One question: by full wipe you mean data/cache/dalvik cache
Click to expand...
Click to collapse
Exactly.
Auris 1.6 vvt-i said:
Yes, "Defy build" means Froyo kernel based, "Defy+ build" means GB kernel based.
Exactly.
Click to expand...
Click to collapse
Yep, that's exactly what it is..
I've just rooted my phone again, followed the steps and installed CM9. It worked like a charm. I was pleasantly surprised at how smoothly it runs, didn't expect that sort of quality from a Nightly. Awesome.
Thanks a lot for saving my phone, guys.
Hmetool said:
I've just rooted my phone again, followed the steps and installed CM9. It worked like a charm. I was pleasantly surprised at how smoothly it runs, didn't expect that sort of quality from a Nightly. Awesome.
Thanks a lot for saving my phone, guys.
Click to expand...
Click to collapse
Sounds great Well since CM9 nightly is still a long way to go, you may want to dual boot CM7 and CM9. Install CM7 as primary and dual boot to CM9.
Guide: http://forum.xda-developers.com/showthread.php?t=1375156
i did the same thing on my defy im a noob and need alor of help.
Ok so i had a motorola defy and i wanted to update it to cyanogenmod 7 but it must have been the wrong one and now its stuck on google boot i can't get to my custom recovery screen by pressing volume - and power buttons and if i press volume + i get this black screen asking to plug in the usb to the laptop which i did but i don't know what to do now. i need complete instructions! , iv checked ALOT of forums and tried following this ones instructions, but RSD lite wont download and install like it said it would . and i have no idea how to get tmobile android 2.2 OS for motorola defy. if i could just get that back i would be more then forever greatfull . please someone HELP ! please all be forever in debt to whoever can help me.
blackhack516 said:
Ok so i had a motorola defy and i wanted to update it to cyanogenmod 7 but it must have been the wrong one and now its stuck on google boot i can't get to my custom recovery screen by pressing volume - and power buttons and if i press volume + i get this black screen asking to plug in the usb to the laptop which i did but i don't know what to do now. i need complete instructions! , iv checked ALOT of forums and tried following this ones instructions, but RSD lite wont download and install like it said it would . and i have no idea how to get tmobile android 2.2 OS for motorola defy. if i could just get that back i would be more then forever greatfull . please someone HELP ! please all be forever in debt to whoever can help me.
Click to expand...
Click to collapse
Try running three setup as administrator. Read all in defy guide. Check the wiki for more guides.
Sent from my MB525 using XDA
do u have a link?
labsin said:
Try running three setup as administrator. Read all in defy guide. Check the wiki for more guides.
Sent from my MB525 using XDA
Click to expand...
Click to collapse
do u have a link
I installed BandroidX on my Bravo (running Cyanogenmod 7.2), hit the bootstrap button, and then hit reboot recovery. The phone shows the red M and then the following error: "Err:a5,70,39,00,21." Can anyone help?
Parcae said:
I installed BandroidX on my Bravo (running Cyanogenmod 7.2), hit the bootstrap button, and then hit reboot recovery. The phone shows the red M and then the following error: "Err:a5,70,39,00,21." Can anyone help?
Click to expand...
Click to collapse
BandroidX Recovery is INCOMPATIBLE with CYANOGENMOD.
You're gonna have to flash the sbf, root, enable non market apps, and install DEFY 2ND-INIT RECOVERY.
As far as I know, BandroidX is only compatible with Stock and BravoX Roms.
brandoix procedure should eliminate as many people make mistakes and also is obsolete
help with bravo
having problems with my bravo on the screen it has have CyanogenMod 7.2.0 using BandroidX recovery
bootloader
09.12
battery ok
ok to program
transfer mode:
usb
harv65 said:
having problems with my bravo on the screen it has have CyanogenMod 7.2.0 using BandroidX recovery
bootloader
09.12
battery ok
ok to program
transfer mode:
usb
Click to expand...
Click to collapse
Do not use BandroidX recovery for any rom except for BravoX (BravoX is a lightweight, deodexed stock rom). Use Defy 2nd-init -- Defy 2nd-init -- Defy 2nd-init.
Anyways, that's the screen to flash an sbf -- if its going there directly when you power up your phone and you're not pressing anything then your Bravo is in a semibrick state -- meaning the only fix is to flash the sbf and start over.
You just need to flash the sbf and install a proper recovery solution.
You only need to install Defy 2nd-init once (per sbf flash). Also, all custom roms on the Bravo come with Defy 2nd-init already installed so DO NOT INSTALL A CUSTOM RECOVERY ONCE YOU'RE RUNNING A CUSTOM ROM. Its pointless*.
*Unless you're testing some version of Touch recovery -- only recommended for advanced users.
Follow the directions in these two links and you'll be back in action in no time
Link to sbf thread
Link to Defy 2nd-init thread
Once you get the hang of it you'll be able to go from sbf to custom rom in under 10 minutes and lol at yourself for being stuck with a simple problem. On my first week of having a Bravo I was stuck on boot at the red M. Couldn't figure out what was wrong. Tried everything I knew and ended up low battery bricking myself. Managed to get a charge and accessed the screen with an ! in the triangle and an andriod -- didn't know what to do on that screen -- got lucky and happened to hit both volume buttons and access stock recovery (took me 3 days to figure out how to access stock recovery btw), did a factory reset there and my Bravo was fully working again. Problem was I didn't factory reset before flashing CM7 when coming from stock...Also, Bravo's 3g was my only internet at the time.
Wow, after looking back I just realized how much I've learned in my 1.5 years with a Bravo. Gotta love XDA for all the knowledge you can obtain here.
/the Bolded crap isn't necessarily directed at you, just bolding it so it sticks out and hopefully helps someone else out -- I've answered questions similar to this and the solution is always "Don't use BandroidX Recovery"
//Defy 2nd-init
skeevy420 said:
Do not use BandroidX recovery for any rom except for BravoX (BravoX is a lightweight, deodexed stock rom). Use Defy 2nd-init -- Defy 2nd-init -- Defy 2nd-init.
Anyways, that's the screen to flash an sbf -- if its going there directly when you power up your phone and you're not pressing anything then your Bravo is in a semibrick state -- meaning the only fix is to flash the sbf and start over.
You just need to flash the sbf and install a proper recovery solution.
You only need to install Defy 2nd-init once (per sbf flash). Also, all custom roms on the Bravo come with Defy 2nd-init already installed so DO NOT INSTALL A CUSTOM RECOVERY ONCE YOU'RE RUNNING A CUSTOM ROM. Its pointless*.
*Unless you're testing some version of Touch recovery -- only recommended for advanced users.
Follow the directions in these two links and you'll be back in action in no time
Link to sbf thread
Link to Defy 2nd-init thread
Once you get the hang of it you'll be able to go from sbf to custom rom in under 10 minutes and lol at yourself for being stuck with a simple problem. On my first week of having a Bravo I was stuck on boot at the red M. Couldn't figure out what was wrong. Tried everything I knew and ended up low battery bricking myself. Managed to get a charge and accessed the screen with an ! in the triangle and an andriod -- didn't know what to do on that screen -- got lucky and happened to hit both volume buttons and access stock recovery (took me 3 days to figure out how to access stock recovery btw), did a factory reset there and my Bravo was fully working again. Problem was I didn't factory reset before flashing CM7 when coming from stock...Also, Bravo's 3g was my only internet at the time.
Wow, after looking back I just realized how much I've learned in my 1.5 years with a Bravo. Gotta love XDA for all the knowledge you can obtain here.
/the Bolded crap isn't necessarily directed at you, just bolding it so it sticks out and hopefully helps someone else out -- I've answered questions similar to this and the solution is always "Don't use BandroidX Recovery"
//Defy 2nd-init
Click to expand...
Click to collapse
thanks for the help
brandoix works
harv65 said:
thanks for the help
Click to expand...
Click to collapse
I used 2initD firts ti me with stock ATT and then install brandoix Bravo recovery . Worcks great installing MIUI V4 (android update 4.0.3 and its fast!!!
(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.
tmcookies said:
(this thread might also be called "A series of unfortunate flashes")
So, i was trying to upgrade my (obviously rooted) defy from a CM10.1 to CM11. Since this upgrade gave me the error message "set_metadata_recursive: some changes failed", i tried installing CM10.2 to see if it makes a difference and that worked. But i still wasn't able to install CM11. After another unsuccessful flash of CM11, i didn't remember to flash a working rom back on it again and instead rebooted the device. By doing, i was not able to get into recovery mode anymore. In fact, my phone just showd the red Motorola sign and seemingly did nothing. I was though able to boot into flash mode (by holding down the VOL-UP button) as well as into the motorola recovery (by holding down the VOL-DOWN button). The latter did not allow to flash anything, but i was able to delete the cache and so on.
So i decided to try and flash an sbf file. I downloaded sbf_flash.sh (running linux) and i downloaded the "Retail DE, AT, CH" sbf-file from hxxp://sbf.droid-developers.org. I got the device into flash mode and ran sbf_flash.sh which ran smoothly and rebooted the phone.
Now the phone won't power up at all. When i connect it to usb, the white led is on, but otherwise it's not giving me any sign of life.
Is there hope or should resign by smacking myself on the head?
regards.
Click to expand...
Click to collapse
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Your battery is dead. Charge it using McGyver method or with an external battery charger.
Click to expand...
Click to collapse
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...
tmcookies said:
It's a good idea, but i have another defy here and i've checked: the other battery is 80% charged but the phone still isn't going on...
Click to expand...
Click to collapse
Is RSD recognizing it?
Sent from my Nexus 7 using Tapatalk
hotdog125 said:
Is RSD recognizing it?
Click to expand...
Click to collapse
Who would have thunk? RSD Lite did recognize the phone and when it started flashing, the phone showed
"SW Update
In Progress.."
So, now what? Which sfb file should i flash?
Anyway, thank you so very much!
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse
Yes, root again if needed.
I saw your other post in the cm11 thread about how your phone died.
I remember reading somewhere in the forums that you should go to cm10.2 before installing the updated recovery, and then install cm11.
I'm not sure if that's 100% accurate, and I couldn't find the link (sorry).
Couldn't hurt, though, seeing as you'd just have to do a few extra ROM flashes.
Good luck!
tmcookies said:
Ok, i installed this sbf and it is working!
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTDACH_P014_A009_HWp3_Service1FF
Now i'm thinking i need to root the system again?
Click to expand...
Click to collapse
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:
after some effort - great on CM11!
leandrolutz said:
Root, install 2ndinit, install CM10, install CM10.2, install update-recovery.zip, REBOOT (without any wipe), install CM11 and GApps. Hope it helps :angel:
Click to expand...
Click to collapse
I had a simiilar problem - somehow after a similar failed CM11 install, I pressed that "reboot" button and my mb525 was dead. I did as suggested here, Except I happened to have CM10.1 not CM10 on the SD.
However I had a lot of trouble getting a successful boot after installing update-recovery.zip, and then also after installing CM11 with the updated recovery.
Now I have a great well-running defy on CM11. I don't exactly why it succeeded when it did - just repeatedly wipe and install and wipe until it worked.
The defy really runs well on CM11 - very responsive - it is robust both in HW and SW! - maybe I'll myke it my main phone again! (before the S3 or the xperia V) - Samy just ain't interested in my S3 - the community provides the same Android version for my defy as I have on my nexus 7 2013!!!
Many thanks to all who have contributed, especially quarx -
try this http://forum.xda-developers.com/showthread.php?p=48501247
Hi all
So, I have a problem with my Defy (MB525 green lens). The best will be, if I'll write my full story. Here is it:
Story
I had Defy with CM 10. It had bloated battery. I wasn't using it for 6 months because I have another phone.
Some time ago, I decided, that I'll give Defy to my grandfather. On Tuesday this week I bought new original battery. I put it in the Defy, and charge it. I could boot up my old system as I wrote, CM 10. While it was charging, I detected that I haven't got SD Card. On the other hand, I found some 4GB Samsung SD, which had my father in his Desire. The SD Card had 3 partitions, which I tried to delete, and make only one, with GParted. After I did it, Linux and Windows can't see it. (This is almost other problem, which I'm trying to solve here http://crunchbang.org/forums/viewtopic.php?pid=350683)
But, when I put the CD Card to Defy, in TWRP recovery I could see some strange symbols. I thought, that I can repair something when I wipe SD Card. When the battery charged, I decided to do factory reset and wipe SD card. Here is my first failure. In TWRP I went to custom wipe, and here I marked everything including system and I wiped it. Then I remembered that system is recovery too. TWRP wrote, that everything except SD-Ext and SD was wiped. I known that this will be a problem. Yes, after reboot only Motorola logo without recovery.
I think, there was only one option - flash SBF, which I did. I went to stock bootloader and with sbf flash in Linux, I flashed this:
JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf
And than this:
CM7RC1.5_16_09_11_custom.sbf
After reboot, I got bootloop. I tried to replace battery, do factory reset but nothing helped. That time I haven't got working card, so I couldn't flash some zip via CWM recovery. Thus, I again flash another SBF, but I don't really remember which. Probably some official CEE Froyo however, I'm not sure.
After that and reboot, I got only black screen with white led lighting while USB was connected. When I wanted to go to stock bootloader, still black screen, but I can flash SBF, and while flashing, screen have brightness and text about flashing.
I knew that this is little hard brick. I again tried to flash other SBF which I have or I downloaded (yes, again I don't know which). One of SBFs which I flashed was some fixed Chinese SBF . That made my defy booting, screen working, but still bootlooping. I couldn't reach any recovery.
Again, I flashed other SBFs, CM's too but nothing worked and I got black screen again.
And this was end of my story.
Current situation
I have Defy (MB525 green lens), with unknown framework an it had only black screen and what only I can do, is break Defy with hammer or flash some SBF.
So, here is list of all SBF files, that I have downloaded and probably tried to flash: (No order)
JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf
CM7RC1.5_16_09_11_custom.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANO2DE_P048_A015_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
DFPRC_U_4.5.3-109_DPP-6-7_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTGC_P025_A019_HWp3a_Service1FF.sbf
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
JORDN_U3_97.21.51.sbf
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FF.sbf
4.5.1-134-DFP-132-gingerbread-BL6-fixed.sbf
4.5.2-109-DHT-22-gingerbread-BL5-fixed.sbf
3.4.2-177-003-nordic-froyo-fixed.sbf
3.4.2-179-002-tmobile-froyo-fixed.sbf
4.5.1-134-DFP-74-gingerbread-BL5-fixed.sbf
4.5.3-109-DPP-11-gingerbread-BL5-fixed.sbf
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN.sbf
Probably that is all what I have.
I've read many topics with similar problem and guides, but nothing helped me, or SBFs were unavailable.
So, what have I to flash, or which guide to try, if I want working Defy?
Sorry for my not good English
Thanks
UPDATE
sterver1 said:
Wohooo!!
Story
After a long time (4 months)...
Accidentally today I found my favorite custom ROM - MoKee OS, for Defy. I said to myself: "Hm, I have some time... I'll try to flash this MoKee on my Defy and maybe it solve my problem with (not) charging/unknown battery for system."
I picked out box with Defy from drawer, wiped the dust, took the Defy and said: "Sh*t! I haven't got SD Card!" Fortunately I found one. I download MoKee OS zip on that SD Card, put it to Defy, booted to recovery and flash MoKee OS zip. (...with full wipe of course...) Then rebooted to system.
Uselessly. Still unknown battery. "Hmm, It doesn't matter. Maybe here are some new stuffs which can solve my problem." And I continued to finding something, that can solve my problem. After a while I found ROMs with new 3.0 Kernel by Quarx. HERE. I downloaded CM 11 EXPERIMENTAL with this kernel and update recovery and flashed them. I didn't read thread. After reboot system didn't boot up and TWRP was inaccessible. I found why when I read some posts from that thread. HERE. But I couldn't flash that zip via recovery because I couldn't open recovery. So I mount /system to USB from bootloader and added files from zip manually to /system partition. After reboot it jammed on booting up. But TWRP was accessible so I did full wipe and flashed CM 11 EXPERIMENTAL and than that fix zip by @lorcotti. After that it finally booted up and battery was working and charging!
And they all lived happily ever after. :laugh:
SO, If you have some problem as me (unknown battery after flashing GB SBF on MB525), try this:
1. Download recovery and some ROM from [Kernel][GPL] Development 3.0 Kernel and fix from this post.
2. Put all zips on your SD Card.
3. Boot up to recovery.
4. Flash update-recovery.zip.
5. Reboot to recovery.
6. Do full wipe.
7. Flash ROM with 3.0 Kernel.
8. Flash Fix.
9. Wipe cache and dalvik cache.
10. Reboot to system.
If you want, you can flash GAPPS via recovery too.
But this will not be for daily usage! 3.0 Kernel by Quarx have a lot of bugs!
Thanks all!
Click to expand...
Click to collapse
Yeah!
Today I again tried to flash chines SBF. This one: JDGC_U6_2.13.0 China Unicom Thread/Download !!!BL6 kernel !!!
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
...and now I have bootable phone . I read many topics again and I got to know how to aces stock recovery. So I made wipe on this chines ROM and I can boot without loop, but I can only do emergency call with SIM it is the same. So, now, I don't know, what have I to do/flash, how to root it and flash here custom rom. Can I use SuperOneClick if it probably haven't got turned on USD Debugging?
Back on black
So, I made sbf file with depacker...
CMG39 from JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FF
and all others from JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF except CMG31.
Than the bootscreen changed from chines logo to grey motorola logo and I got Bootloader (9.00) Error A5,70,39,00,27. After that I flashed another sbf and I got Error A5,70,00,00,23. Than I flashed DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf and now I again have only black screen. F*ck!
I tried to flash my made sbf and chines one (JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF) too but nothing...
Really here is nobody who can help please??? I want give Defy as Christmas gift. :crying:
OK, so repetition.
What mistakes I've made
1. I wipe wipe all including system partition in TWRP without any flashable zip on SD card.
2. I continued with flashing original SBF, while I have usable CWM.
3. I flashed many no downgradable GB SBFs.
4. I flashed Defy Plus SBF on Defy.
I hope that there is still hope.
Somehow to downgrade, flash only CWM where I can flash nandroid backup or I don't know what else...
a gingerbread sbf should also work on green lens defy as there is no diff. in hw... instead the cam
have you tried a factory reset in stock recovery after sbf flash ?
Sent from my MB526 using xda app-developers app
Now, after all (which I tried) SBFs I get only black screen. I tried many GB SBFs too, but still black screen...
I'm going to try some another Poland SBFs and than if that won't work, I'll try to flash all in Froyo CEE SBF particularly.
Thanks for your response.
Once you've flashed GB stock sbf you can't go back staight to froyo or else
Read the beginners guide and the SBF matrix sektion carefully.. if you haven't...
Sent from my MB526 using xda app-developers app
DFP 231 has been flashed by you, so no froyo sbf will work. Black screen on dfp 231 indicates some eMMC problem, because bl version is highest(no error possible). IMHO only service centre can disable bl check or replace the main board to fix the problem
The problem should have been solved at the boot loop issue by wiping from stock recovery, no network solved by baseband/radio fixes. Check the rsdlite log file to confirm checksum/access errors. I think that the custom sbf somehow messed up either eMMC or efuse(less likely, unheard of).
For sdcard error wipe everything using hdd llf. If any error persists it's a hardware issue
Sent from my MB526 using Tapatalk 4
@bone101
I know, I read it few times, and I know how it is (not) working. But, after all GB SBFs I got only black screen, so maybe were not correctly flashed... I'm using Linux and here is sbf_flash for flashing SBFs, and in it I can't view informations about phone as in RSD Lite... But maybe, it will work in wine..
Do you now, that if I flashed GB SBF, I have to flash another GB to solve my problem, because no Froyo will work?
@thekguy
I know how I can solve others problems. Only what I need help to solve is black screen.
Can't I flash something which support that high BL or it won't work?
check if you get into Bl. modus
press vol. up & then power button
tell what you see
Sent from my MB526 using xda app-developers app
That's what I'm saying, the black screen problem occurs due to bl version mostly, and you have highest bl, so in theory black screen is impossible. Unfortunately I have never seen in this forum any defy recovering from black screen after flashing dfp231. Check rsd log from windows if possible. Froyo sbf cannot work under any circumstance. You must flash only gb sbf
Sent from my MB526 using Tapatalk 4
@bone101
When I acess bootloader I have only black screen... While flashing I can see
"SW Update
In progress.."
Ok, I have Windows notebook available... Here are device properites from RSD Lite:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 173002052f066b010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: d0d8842b4879dd27b9eb94f970fbeec252fcb2f4
BP Public ID: 0000000000000000000000000000000000000000
Click to expand...
Click to collapse
I'm going to try some GB SBFs here...
WOHOOO I've got it! I flashed 231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf and now I have got bootable phone... I'm in the system. I'm going to root it and flash CWM and MIUI if it will work.
Really thanks for your help!
sterver1 said:
@bone101
When I acess bootloader I have only black screen... While flashing I can see
"SW Update
In progress.."
Ok, I have Windows notebook available... Here are device properites from RSD Lite:
I'm going to try some GB SBFs here...
WOHOOO I've got it! I flashed 231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf and now I have got bootable phone... I'm in the system. I'm going to root it and flash CWM and MIUI if it will work.
Really thanks for your help!
Click to expand...
Click to collapse
I'm stuck in same problem, downloading this sbf you mention before, hope it works. Fu^kin defy, it sucks
@Alejandrissimo
Good luck...
I have another problem. Now, I have GB kernel. In original 2.3.6 GB on MB525 green camera don't work, and battery too. So, I thought that, when I flash Froyo kernel (CM) and CM7 I got back Froyo kernel and working camera and battery. Yes, this was not possible. After I did it and rebooted it I got Bootloader error. I flashed DFP-231 again. Worked.
Than I tried restore Froyo from nandroid which I found something here on forum. Than I flashed CM7 and bootloader error again.
Now I have CM7 by Maniac for defy plus which worked well except camera and battery... I know that here are many topics about downgrading, camera fixing and others but all which I read are bad in something for me...
Here are some options what I found but I don't know if I can use one:
Method 2: (BIG thanks to Jebrew again for this one)
NOTE: You are going to need CM7 for this one. CM7 Stable version recommended.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=1216982
DOWNGRADE
If you come from Android 2.1 and never flashed Android 2.2 you can use the fixed sbf-files method. With this method you will have a option to downgrade to you personal stock Android 2.1 via direct sbf flash.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=966537 but I'v ever flashed Android 2.2.
Or http://forum.xda-developers.com/showthread.php?t=1465436 ... This is better option but I have flashed full 2.3.6 SBF and here is:
It will only work if you never flashed a Android 2.3.6 full sbf.
Click to expand...
Click to collapse
So, how can I downgrade or repair battery and camera? I don't care whether I have got GB or Froyo kernel if I have working camera and battery.
have you tried cm11 ?
or ms2ginger by walter79
Sent from my MB526 using xda app-developers app
sterver1 said:
@Alejandrissimo
Good luck...
Click to expand...
Click to collapse
Working and rooted, thanks for your help
Alejandrissimo said:
Working and rooted, thanks for your help
Click to expand...
Click to collapse
please see your PN
sterver1 said:
@Alejandrissimo
Good luck...
I have another problem. Now, I have GB kernel. In original 2.3.6 GB on MB525 green camera don't work, and battery too. So, I thought that, when I flash Froyo kernel (CM) and CM7 I got back Froyo kernel and working camera and battery. Yes, this was not possible. After I did it and rebooted it I got Bootloader error. I flashed DFP-231 again. Worked.
Than I tried restore Froyo from nandroid which I found something here on forum. Than I flashed CM7 and bootloader error again.
Now I have CM7 by Maniac for defy plus which worked well except camera and battery... I know that here are many topics about downgrading, camera fixing and others but all which I read are bad in something for me...
Here are some options what I found but I don't know if I can use one:
from http://forum.xda-developers.com/showthread.php?t=1216982
from http://forum.xda-developers.com/showthread.php?t=966537 but I'v ever flashed Android 2.2.
Or http://forum.xda-developers.com/showthread.php?t=1465436 ... This is better option but I have flashed full 2.3.6 SBF and here is:
So, how can I downgrade or repair battery and camera? I don't care whether I have got GB or Froyo kernel if I have working camera and battery.
Click to expand...
Click to collapse
Congrats man! Seems that rsdlite on Windows is the most reliable solution. Now to fix everything just flash cm10 (jelly bean) or later rom. It includes fixes for camera and battery
Again, no downgrading bl(not even jtag will work)
Sent from my MB526 using Tapatalk 4
Oh, ok. I'll try it. Thanks.
Hmm, and than, can I flash CM7 by Maniac or JB/GB WIUI and fixes in CM10 will still working?
Ms2ginger is not good for me because it haven't got slovak language. I'll give defy to my grandfather.
//And now, in Quarx CM 10 my battery don't charge. I tried 2 chargers and charging via USB too.
In options, battery is still "60% - Unknown"
Alejandrissimo said:
Working and rooted, thanks for your help
Click to expand...
Click to collapse
Hehe, I'm glad...
sterver1 said:
Oh, ok. I'll try it. Thanks.
Hmm, and than, can I flash CM7 by Maniac or JB/GB WIUI and fixes in CM10 will still working?
Ms2ginger is not good for me because it haven't got slovak language. I'll give defy to my grandfather.
//And now, in Quarx CM 10 my battery don't charge. I tried 2 chargers and charging via USB too.
In options, battery is still "60% - Unknown"
Hehe, I'm glad...
Click to expand...
Click to collapse
There's a cm7 2ndboot build which should work for you. Try cm10.1 or above, problem should be solved.
JB wiui includes those fixes, as does cm7 2ndboot. I don't think that wiui GB has them. I would personally go for cm10.1 or above
Sent from my MB526 using Tapatalk 4