[Q] Defy+ stuck... on stock firmware! - Defy General

My Defy+ had originally an Android 2.3.4
I successfully flashed many ROMs and happy with CM7 WhiteRabbit.
I decided to restore a nandroid backup of the original firmware 4.5.1-134_DFP-89 just to test if I could go back "just in case".
With great wonder the phone is stuck un Motorola logo even if checksum seems right.
If I re-flash WhiteRabbit the phone boots correctly.
I never flashed a kernel different from the original.
I know I could flash a more recent SBF but could you help me in explaining how is this possbile?
PS: I wiped cache/data/dalvik with no result.

UncleDan said:
My Defy+ had originally an Android 2.3.4
I successfully flashed many ROMs and happy with CM7 WhiteRabbit.
I decided to restore a nandroid backup of the original firmware 4.5.1-134_DFP-89 just to test if I could go back "just in case".
With great wonder the phone is stuck un Motorola logo even if checksum seems right.
If I re-flash WhiteRabbit the phone boots correctly.
I never flashed a kernel different from the original.
I know I could flash a more recent SBF but could you help me in explaining how is this possbile?
PS: I wiped cache/data/dalvik with no result.
Click to expand...
Click to collapse
Some roms like cm7.1 stable contain kernels, ie boot images chances are you've flashed a boot.img(kernel) without knowing
teamwork makes the dream work

You are right! Now the next (and last) questions.
Can I go back to old firmware without sbf?
How can I discover which ROM flashed the kernel?
Sent from my MB526 using XDA

UncleDan said:
You are right! Now the next (and last) questions.
Can I go back to old firmware without sbf?
How can I discover which ROM flashed the kernel?
Sent from my MB526 using XDA
Click to expand...
Click to collapse
Without knowing the rom you've flashed I can't tell you which have caused it, but if you still have the zips then just open them up the one with the boot.img done it,
Only way back is reflash the sbf unless you made a back up of the boot image when you made your nandroid
teamwork makes the dream work

The nandroid backup I am trying to restore has a boot.img. When I find which ROM flashed the kernel I will compare and see if it is the right one. Thanks.
EDIT: I found out that I flashed a kernel with maniac's CM7.2 RC1 (I thought it was no kernel like nightlies), but it is different from the one I have in stock image backup. So the question why I am stuck if I restore the nandroid including the kernel remains. I will go on in the study.
Sent from my MB526 using XDA

Related

[Q]

I have never flashed a rom to my current evo which is rooted and I love it. My question is how do I go back to my current stock state if I don't like rom. I have nandroid backups and will make another before I flash a rom, I know how to clear everything out before flashing the new rom. Can I just restore the nandroid back to return to the stock rom or do I have to do something else. Also what kernel should I use if I want to check out CM7. I have read that a lot of people use either Tiamat or Savaged-Zen. Thanks in advance.
Smurph82 said:
I have never flashed a rom to my current evo which is rooted and I love it. My question is how do I go back to my current stock state if I don't like rom. I have nandroid backups and will make another before I flash a rom, I know how to clear everything out before flashing the new rom. Can I just restore the nandroid back to return to the stock rom or do I have to do something else. Also what kernel should I use if I want to check out CM7. I have read that a lot of people use either Tiamat or Savaged-Zen. Thanks in advance.
Click to expand...
Click to collapse
That is correct, all you would need to do is restore a nandroiid backup, to return the exact point you were at when you created that backup. Simple as that. As far as kernels, either of the two you tried should work great. Every phone is different, so try them out and see how they run. I'd also give the stock CM kernel that comes with CM7 a chance, it ran beautifully on my device, fwiw.
I agree with buckley in regards to just using the stock CM7 kernel. I'm pretty sure Cyanongen and Co. know what they're doing...
Great then I think that I will try to install CM7. Also do I need to do the gps fix now while I'm on the stock rom or do I needed to just wait to see if I have gps problems first. Also will CM7 replace my Amon-Ra v 2.3 with Clockwork recovery.
Sent from my PC36100 using XDA Premium App
Flashing CM won't effect your recovery. Also, I think you can do the GPS fix now before you flash. Either way, couldn't hurt.

[Q] Downgrade ability?

Hi guys,
New to xda.. I own a defy with 2.2.2 official SEA. I want to update to CM7 RC0, without losing the downgrade ability. After reading a lot in xda, I've got a fair amount of knowledge to flash my phone. Just have a couple of queries..
6) Can I restore my phone to send it to warranty after flashing CM7?
- You can in these two situations
1 - You have a full SBF of your original ROM (for carriers that already released 2.2 is very easy to find one)
2 - You have a nandroid backup AND a fixed SBF of the version you need.
Click to expand...
Click to collapse
Quick question:
Considering option 1, I have the official ROM (full sbf, 2.2.2 for India) downloaded here. If I flash to CM7, can I re-flash it with the official full sbf to claim warranty? Considering the scenario that I only have contacts and sms to restore and I don't want to restore settings, apps and all. I like to do them anew (even if it takes time).
Technically, that would be like formatting the drive which has the operating system, instead of restoring an image.. Is that possible? Is Nandroid Backup + fixed sbf is the only way to go back to the stock OS to claim warranty?
P.S. - I still don't get what fixed sbf is. Can anyone help?
Just create a backup of your current OS if anything happens restore it.
Sent from my MB525 using XDA Premium App
ATXiceman512 said:
Just create a backup of your current OS if anything happens restore it.
Click to expand...
Click to collapse
You mean Nandroid backup? Can i restore just that file (and not the sbf) in case anything goes wrong?
If your device is rooted download the 1.4.2 version of 2ndinit go into custom recovery and create a backup, then boot back up normally and connect device to the computer and copy the backup to a safe place on your computer, so if you ever need to back it up, you will have the file.
Sent from my MB525 using XDA Premium App
I mean do I always need an sbf file to restore an image?
No you only need sbf. file to flash a image, to restore and image all you need is a copy of a backup.
Hmm.. okay... Consider this scenario:
1. I'm having official 2.2.2 SEA ROM
2. I just want to root, install a custom recovery (take a backup in Nandroid), make changes to the current ROM and I'm NOT flashing a new ROM ie like CM7.
3. Can I just restore the backup from recovery if something goes wrong (without any sbf of course)?
4. Do I still have to install 2nd init in that case?
P.S. - Thanks to your patient replies bro.. Much appreciated
Yes you can downgrade back to sea version using sbf file
Just make a nandroid backup if anything goes wrong restore the nandroid you made plus flash it with the fixed or full sbf file of sea and it will bring everything back the way it was that's what i did anyway and it worked
Let me know how cm7 is on the SEA version if it works stable ill install it
Cheers
WolVish said:
Hmm.. okay... Consider this scenario:
1. I'm having official 2.2.2 SEA ROM
2. I just want to root, install a custom recovery (take a backup in Nandroid), make changes to the current ROM and I'm NOT flashing a new ROM ie like CM7.
3. Can I just restore the backup from recovery if something goes wrong (without any sbf of course)?
4. Do I still have to install 2nd init in that case?
P.S. - Thanks to your patient replies bro.. Much appreciated
Click to expand...
Click to collapse
Yes 2ndinit is a custom recovery program as long as you have that you wont need sbf. Files. Sbf. Files are used with RSD lite in order to install custom roms. You can use any recovery program you want, best I have found to use on the defy is 1.4.2 version of 2ndinit.
Sent from my MB525 using XDA Premium App
Mem check your message please
Sent from my MB525 using XDA Premium App
memz180 said:
Yes you can downgrade back to sea version using sbf file
Just make a nandroid backup if anything goes wrong restore the nandroid you made plus flash it with the fixed or full sbf file of sea and it will bring everything back the way it was that's what i did anyway and it worked
Click to expand...
Click to collapse
Why should i use Nandroid, If I want to flash with full sbf of my SEA official ROM?It'll be factory fresh right?
Let me know how cm7 is on the SEA version if it works stable ill install it
Cheers
Click to expand...
Click to collapse
Sure.. But in Quarx's thread, It was advised to flash Nordic ROM first before installing CM7.
WolVish said:
Why should i use Nandroid, If I want to flash with full sbf of my SEA official ROM?It'll be factory fresh right?
I just restored my old nandroid and flashed with the fixed sbf but i believe if you do a full sbf it will result in the same thing both ways should work
Sure.. But in Quarx's thread, It was advised to flash Nordic ROM first before installing CM7.
Click to expand...
Click to collapse
Yes thats correct some people have installed over the SEA version and its full working im yet to test this i have however tested the NORDIC II version and flashed cm7 beta 6 and that did work nicely but i went back to SEA15 until cm7 releases a more bug free version.
memz180 said:
Yes thats correct some people have installed over the SEA version and its full working im yet to test this i have however tested the NORDIC II version and flashed cm7 beta 6 and that did work nicely but i went back to SEA15 until cm7 releases a more bug free version.
Click to expand...
Click to collapse
What i found in the Official SEA 2.2.2 ROM's thread
ok make sure you do not install CM7 directly on this rom, else boot looping.
Please follow the cyanogenmod7 FAQ point 7. http://forum.xda-developers.com/show....php?t=1065798
i tried and was stuck on boot loop.
Again FLASHED this sea15 sbf via rsd lite back to square1 now need to start the process all again.
Click to expand...
Click to collapse
Nordic is the way to go it seems..
Nice find because i just got my sea15 back i listened to someone from here like a idiot they said they were running SEA15 with cm7 which is a lie because it when i installed cm7 i got a never ending boot loop so id like to say it does not work with sea15 it took me an 1hr to restore all my stuff back to the way it was so yes NORDIC I or II is the way to go thanks for the info
You're welcome mate.. Heard review that RC0 is way better than Beta6..
Finnaly the thread i've been looking for.
I'm currently on official German 2.2.2. I really want to try out CM7 but the tutorials keep telling me I need a sbf (wich is not available at this moment) of my version if I want to downgrade again.
So just to be sure:
Having a sbf is not an absolute must?
And in the case anything goes awry (eg. boot loop) I just have to restore it via my nandroid backup, unroot, deinstall 2ndInit, wipe and I'm practically back were I started, right?
ShiroHouseki said:
I'm currently on official German 2.2.2. I really want to try out CM7 but the tutorials keep telling me I need a sbf (which is not available at this moment) of my version if I want to downgrade again.
Click to expand...
Click to collapse
That's correct. Even if you can't find a full sbf (carrier released version of your OS, usually a large file, 200-300 MB), make sure you have one nandroid backup of your data/settings and a fixed sbf (usually stripped down version, less size <50 MB) of your current OS. This would enable you to re-flash in case you have to claim warranty.
So just to be sure:
Having a sbf is not an absolute must?
Click to expand...
Click to collapse
I don't think so. You MUST have one if you want to claim warranty. Even if you don't need warranty, still you need either Nordic ROM or UK ROM (sbf files, mind you )to be flashed first to install CM7.. Other ROMs are not recommended.
And in the case anything goes awry (eg. boot loop) I just have to restore it via my nandroid backup, unroot, deinstall 2ndInit, wipe and I'm practically back were I started, right?
Click to expand...
Click to collapse
This only works If you flashed with nandroid + fixed sbf of the Nordic/UK ROM.
OR
You have the full sbf of your current ROM, which you can flash from RSD lite.
Hope this helps...
P.S. - Can anyone confirm these answers?
Aww, well i guess i'll be waiting for the sbf files then
Well, thank you anyway for the info.
Who releases this sbf files anyway? Are they somehow extracted out of offical update packages or are they leaked from service contractors?
I am also confused. I thought a nandroid was a complete image of the phone and didn't require an SBF?
Putting it in PC terms I considered a nandroid the equivilent to a ghost image of a HDD? So if I had a PC with XP on it and took a ghost image of that it would be a complete copy of the drive. I could then install Vista on that drive and when / if I wanted to restore the ghost image and it would restore XP onto that system?
I understood an SBF to be a system image as such, but not including the very base level stuff that a nandroid backup would have and hence why you can flash a 2.2.2 rom but need a 2.2 SBF flashed on the phone?
Or am i getting confused?
ShiroHouseki said:
Aww, well i guess i'll be waiting for the sbf files then
Well, thank you anyway for the info.
Who releases this sbf files anyway? Are they somehow extracted out of offical update packages or are they leaked from service contractors?
Click to expand...
Click to collapse
I think your German 2.2.2 ROM has been added only yesterday. Go to www.motorola.com/update, select your region - Select MOTODEFY - Follow instructions.. (Don't forget to do a hard reset after updating )
Full sbf s are released by the Manufacturers/Carriers. It's like untouched windows XP cd. You can directly update via MSU or use RSDlite to flash it..
Fixed sbf s can be made by anyone, maybe you or me, by making some tweaks, just like we do to Windows XP using nlite (which i'm still not that familiar with )

[Q] SBF Mix up

Hi there,
My Defy was on Quarx's 0308 CM9 (With CM7 Kernel), when I tried to install Walters Kernel using 4.5.2-109_DHT-22-kernel.zip. After doing this it did not go past the "M" logo upon reboot.
I then read that others had flashed the fixed DHT-22 kernel to fix this issue. I accidentally selected the wrong SBF (JRDNEM_U3_3.4.3-11_BLUR_SIGNED) and I am now stuck in a boot loop. Could anyone please help me figure this out?
Thanks in advance
Can you get into recovery ? , have you tried full wipe , data,catch+dalvik
Sent from my MB526 using xda premium
No can't get into recovery, only into bootloader to flash sbf's.
IgWaBaBa said:
No can't get into recovery, only into bootloader to flash sbf's.
Click to expand...
Click to collapse
I was in your situation last week (stuck at m logo), so i flashed a 2.2 sbf, then rooted, installed recovery and installed ics again with correct kernel,
That is the way i done it, its a long way around but I'm not sure if there is a faster way sorry,
Djc
Sent from my MB526 using xda premium
i have today this problem.
i found china sbf 2.2.2 work on my defy flash root boot cm7 and cm9
Thanks for the response, I'm busy downloading another SBF to try that, will give feedback and thanks, if I prevail!
Ok, I'm back in action. The issue was that I needed to wipe user data and cache using the standard restore (I think that's what it's called). Anyway instead of looking for a SBF that makes it work, I accessed the standard restore by holding volume - while powering up, then wiped user data and cache, which stopped the boot loop after the reboot.
Now I'm back onto CM9
Glad That Worked me too faced alot probs with CM7 and 9

Custom Rom help

Hey All
I'm in need of some help. For some reason this whole SBF thing is completely confused me
My Defy
System Version: Moto_Version.34.30.3601.MB525.Vodacome.en.GB
Firmware Version: 2.2.2
Baseband Version: EPU93_U_00.59.02
Build number: JEM_3.4.3-36-1
(Unsure if these will help)
Anyway, I'm wanting to put CM7 or another custom rom onto my phone, but they all seem to be version 2.3 or so, but I want to be able to drop down to my original rom in case I need to return the phone for something
I did the official update to 2.2.2 from 2.1, which was lucky as with my 2.1 stock rom Clockworkmod couldn't read my memory card, seemed to be a common glitch with the SBF version it had, but it seems fine now
I read somewhere to use a Nordic nandroid backup for some reason, cant remember, just found it in my download folder from attempting to get clockworkmod to work on 2.1, restored the image onto my phone, which worked fine, but that seemed to be a no risk flash
So now I'm confused on how to proceed to putting on a custom rom, I fear that I'm going to **** up something, or going to run into issues if I try change to different custom roms
I'm possibly just over thinking what is meant to be done, and it is way simpler than it seems at the moment
anyone have some advice?
Using nordic as a base is old, custom runs like cm7 work on any base.
As long as you don't flash full sbf of gingerbread builds via rsdlite you can always go back to your original 2.2 by flashing full sbf through rsdlite.
Okay coming to installation of custom roms, first thing is to root it. You can use super one click for that. Then install defy 2ndinit after that boot menu and recovery.then you are all set to install custom roms.
For cm7, down load the zip and install through cwm.
Restart phone and as soon you see blue led press volume down, this would put you into boot menu.then select custom/stable recovery. Select wipe user data/factory reset.then go to advanced and select wipe dalvik cache. Come back and select install from zip and give cm7 zip, after finished reboot. It will now boot with cm7, first boot will take few minutes 2-3. It is generally cm7 first boot is in loop, if you are stuck just remove battery and put back and restart.
You can go through cm7 installation thread for better clarity.
Enjoy flashing!
Sent from my MB526 using XDA App
Thanks for the reply
So basicly I just flash the rom straight in clock work mod, no need for fixed SBF's or anything?
Do I need to back up/make full SBF of my stock SBF or something?
Is CM7 7.1 based on Froyo, and you'd just flash it straight from the memory card in Clockwork mod?
Or have I missed the point and meant to flash a fixed SBF to allow for gingerbread or any roms and then reflash 2.2 back on when I want to retore stock again?
Well I went ahead and installed Motogamer, which I downloaded last night and its working fine, but it seems to be based on the froyo kernal
I'm still a little confused as CM7.1 looks like its gingerbread, unsure of the downgradeability to my froyo stock rom, but this rom had no issue when I used my nandroid backup to restore to my stock rom
Thanks for the help
CM7.1 stable is android 2.3.7 with froyo kernel. And there is CM7.2 nightlies with both froyo and gingerbread kernels. I use the defy+ CM7.2 with gingerbread kernel from Quarx (this gives me better battery life) http://quarx2k.ru/, since i have redlens defy.
You dont have worry about the downgradability as long as you dont flash full sbf of gingerbread using rsdlite. All the dev custom roms have no problem in downgrading back to your original stock froyo. Look at if there is any WARNING IN RED regarding downgradability when you download any rom.
There are good number of ROMs to try, whenever you change ROM remember to do full wipe (factory reset and wipe dalvik cache), back up your apps and other information before you do this. If you are upgrading to night revision of same ROM, for example next nightly of CM7.2 we dont have do to full wipe, just cache and dalvik cache wipe would be fine.
If you like Stock ROM, try MS2ginger3.0 which gives awesome battery life and with full blur functionality if you like.
Awesome, thanks
I'm really keen to try more custom roms out, really happy so far with this new one at the moment, but will probably try CM7 soon
Thanks for the advice, not sure I'll go back to stock rom for a long time, just feared that I'd **** something up and not be able to return to stock if needed to
Really keen to start seeing what android really has to offer now

Cant flash ROM anymore

I have tried to flash a new ROM, but cmw were never able to flash it always being aborted. Yesterday tried to flash Darkside evo 3. Flash super wipe success, flash new baseband good, comes the rom itself aborted package not good. I thought it was just bad messages from cmw.Reboot the phone wouldnt reboot just hung,i tried cache wiped still not reboot, hung again. Any idea why? I just flashed the cmw again so i will try again. In the mean time any idea will be appreaciated
JugMod V 5.0,
2.3.6, 2.3.14
Possible bad download of the rom. Definitely won't boot after a superwipe. Did you make a nandroid?
Sent from my SGH-T989 using xda app-developers app
Yes, i did make a backup. Funny thing is, i am only able to install a new baseband, anything else is fail.
JugMod V 5.0,
2.3.6, 2.3.14
FwaZ said:
Yes, i did make a backup. Funny thing is, i am only able to install a new baseband, anything else is fail.
JugMod V 5.0,
2.3.6, 2.3.14
Click to expand...
Click to collapse
*my opinion*
your running gb, some of the newer roms are ics created, will cause conflict between the 2 hence why the non flash capable. i would recommend to update to ics and try again, make sure u nandro first in the event you wanna revert back to prior os and maybe that will solve your probs. hope this helps
sgs2:chimera bitten/ herculoid stout
3.0. perfection
I had this problem too both on My Vibrant and Galaxy Tab 10.1. I say odin to stock and do a clean install of the rom. that always seemed to fix it for me
Check the md5sum and see if it matches before flashing any rom thats very important.... Or what cwm version u using??? Cause the touch cwm has some issues so i changed to the non touch cwm its more secure
Sent from my SGH-T989 using xda premium
if you want, do what i did, i restored stock ics and cleaned up my phone fully as from factory. started from root to flashing all the stuff all over, now im on a clean sd card( backedup all the external sd on my pc) so i have tons of room to play with. hope this helps

Categories

Resources