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
Related
so i just got my g2 and rooted using root file from the developsection
rooted, downloaded cm 7, wiped cache, then flash cm7
im stuck at cyanogen boot screen. anyidea?
didnt think it would make anyproblem, in samsung vibrant we had a file called odin where we can reflash,
right now i have no usbcable...am i f**ked?
edit: Fixed it but i get boot reboot when i try to turn on the wifi?
There's a problem with current Gingerbread 2.3.3 ROMs where the first Wi-Fi switch on after a wipe/first boot causes a bootloop - just pull the battery once you enable it, it's how I got around it.
eunkipark92 said:
so i just got my g2 and rooted using root file from the developsection
rooted, downloaded cm 7, wiped cache, then flash cm7
im stuck at cyanogen boot screen. anyidea?
didnt think it would make anyproblem, in samsung vibrant we had a file called odin where we can reflash,
right now i have no usbcable...am i f**ked?
edit: Fixed it but i get boot reboot when i try to turn on the wifi?
Click to expand...
Click to collapse
If you're coming from the stock ROM, you need to wipe everything (data/factory reset) or you're going to run into problems.
Sent from my HTC Vision using XDA App
i see everyone say pulling the battery... once it bootloops and turns back on you have enough time to hold the power button and do a manual reboot after that it will stop the bootloop
Thanks doing the factory reset and reflashing fixed it
Sent from my HTC Vision using Tapatalk
Hi, I have been running on Gingerbread CM7 for a few weeks now until today when I attempted to install 2nd-init. After the installation, I rebooted my Defy and has been stuck on the red logo. I tried flashing with an nandroid backup 2.34 sbf but it's still looping on the logo. I've also tried wiping data after flashing and still no luck.
I appreciate your time taken in helping me out of this mess. Thanks.
Wipe Data and cache from Stock Recovery than try to flash fixed SBF through RDS and if that don't work than Flash full SBF....
Sent from my Toilet using Motorola DEFY
ifu said:
Wipe Data and cache from Stock Recovery than try to flash fixed SBF through RDS and if that don't work than Flash full SBF....
Sent from my Toilet using Motorola DEFY
Click to expand...
Click to collapse
I'm sorry, I am quite new to this. But which full SBF should I look for?
nikki3010 said:
I'm sorry, I am quite new to this. But which full SBF should I look for?
Click to expand...
Click to collapse
You mus try 2.2.2 from this thread
http://forum.xda-developers.com/showthread.php?t=966537
Hey, I've managed to flashed back to the Nordic 2.2.2 SBF and everything's fine now. I panicked a little yesterday as I was away on vacation and had no phone to use. But I'm back home now and it's fixed. Thank you all!
Hi,
I am trying to flash MIUI on my Defy which is currently running the official 2.2.2 released here in India.
What i have done so far (and repeated the entire process several times):
-Rooted the phone using SuperOneClick
-Installed ROM Manager
-Installed Clockworkmod Recovery 2.5.1.8 for Defy
-Downloaded 'miuiandroid_Defy-2.3.4a' the then latest version of MIUI from their site and the corresponding language pack
-Installed and booted into custom recovery
-Took a nandroid backup of the current ROM
-Wiped data, cache and dalvik cache
-Selected the .zip ROM file from the sdcard and installed it
-After the installation was done, i rebooted the system
This is where the problem started. I had read that the phone might take forever for its first boot. But in my case, the phone would stay stuck on the M logo till i removed the battery. On restart, the same thing repeated.
I found the SBF for the retail version of 2.2 i found on the forums and used RSD Lite 4.9 to flash it to the phone and then restored the nandroid backup i had made previously to get back to where i started from. And i repeated the entire process 4 times using 3 different versions of MIUI.
Am i missing something here? What can i do to get the phone to move past that M logo? I have been trying to find a solution to this issue since over a week now. None of the forums seem to have a solution to a similar problem. Any help would be appreciated.
Answer to all Your problems
It's a common mistake. You must have forgotten about wipe all (cache and personal data) before installing zip package containing MIUI.
hex24 said:
It's a common mistake. You must have forgotten about wipe all (cache and personal data) before installing zip package containing MIUI.
Click to expand...
Click to collapse
I did that. Everytime i tried to install the ROM i did all the three.
Install 2nd inti not CMW and than install MIUI...
Sent from my MB526 using XDA App
ifu said:
Install 2nd inti not CMW and than install MIUI...
Sent from my MB526 using XDA App
Click to expand...
Click to collapse
It worked! It worked!
Thanks a lot!
Hello all,
I've followed the installation in the CM site
i've installed the latest stable via CWM
and now it keeps showing me the welcome to android "touch tge android to begin" and than it goes to the CM load animation
please help
flashed kernel ?
without right kernel phone wont boot up.
resolved
i used the one in the cm zipped file
but i've used the RC ver and it worked,
maybe i did something wrong the first time, i can't put my finger on it
thanks anyway
Wipe cache and others before flashing
abd_alazeez2002 said:
Wipe cache and others before flashing
Click to expand...
Click to collapse
Beat me to it. I had the same problem when I flashed FXP052 because I rushed and forgot to wipe the data and the delvic. Follow the wiki and you shouldn't have any problems
Sent from my LT15i using xda premium
Hi. All was working well when I was running Quarx's version of CM10 on my Green Lens Defy. I could update to each new update CM10 ROM by clearing the data and cache then flashing the ROM and GApps. After that, I wiped the dalvik cache and reboot. Note my Defy is using a Froyo kernel.
Then I decided to try out Codename Android JB Beta and I did what I normally did with the ROM and then GApps. I ended up stuck in a bootloop. No problem I thought. I'd just reflash Quarx's own version of CM10 after wiping data and cache. I got stuck in a bootloop again. Odd. I tried it with older versions of Quarx's CM10 and they result in me getting stuck in a bootloop as well. So I flashed the US T-Mobile SPF for the Defy using RSD Lite then I logged in to BLur and such as that is needed to access the homescreen where I then turned on USB debugging. I then plugged in my phone into my computer to use SuperOneClick Root to root my device. It said my device was already rooted though I don't think that should happen since I flashed a stock 2.1 SPF. Well I rebooted and installed the 2ndinit apk then installed 2ndinit using the app. I think it said that 2ndinit was already installed. But if my memory is wrong in this case, I then installed 2ndinit and rebooted my Defy but I never got a blue LED.
Then I did the same steps as I did previously over and over again with variations to try to get it to work.
Can someone help?
I caution anyone who may attempt to install Codename Android JB Beta from CM10.
On another matter, downloading an OTA update then rebooting when pressing "install now" brings me to the triangle with exclamation screen and gets stuck there.
Have you done a fullwhipe in the Motorola Recovery before flashing the SBF??(usually you would get a bootloop without fullwhiping but maybe the solution is that easy )
And why did you flash a 2.1 SBF you should maybe try some other SBFs like the Froyo SBFs for your Country
Steveletack said:
Have you done a fullwhipe in the Motorola Recovery before flashing the SBF??(usually you would get a bootloop without fullwhiping but maybe the solution is that easy )
And why did you flash a 2.1 SBF you should maybe try some other SBFs like the Froyo SBFs for your Country
Click to expand...
Click to collapse
Oh a full wipe in stokc recovery is needed? I'll try it.
Can you suggest a good SBF for a US Green Lens Defy if you know any?
Is it fine if I use the 3.4.2-179 CEE Deblur SBF as recommended by Quarz for a base then root, install 2ndinit. and flash CM10 from Clockwork Mod Recovery?
j814wong said:
Is it fine if I use the 3.4.2-179 CEE Deblur SBF as recommended by Quarz for a base then root, install 2ndinit. and flash CM10 from Clockwork Mod Recovery?
Click to expand...
Click to collapse
Yep fine for using that one but you should definitely check out the begginers guide for sbf rooting ect as you've been having trouble with this for the last few days now and I'd really like to see get this sorted once and for all
Sent from my MB525 using xda app-developers app
after you instaled 2ndinit
are you opend it and appli the recovery?
if you dont applied the recovery you will not find the led blue and the CWM