So a buddy has a Defy. He had CM on it. Was working fine. He than decided to try another rom. Well it wouldn't boot...just bootlooped. Dumba$$ didn't nandroid. So he just just wiped and went to flash an older version of CM he had on SD card.
Phone would boot but said corrupted memory error...he told him to reset. He tried, didn't work. So than he proceeded to RSD the JORDAN files. It now boot loops. Any suggestions? Really would appreciate your help.
aaronuser said:
So a buddy has a Defy. He had CM on it. Was working fine. He than decided to try another rom. Well it wouldn't boot...just bootlooped. Dumba$$ didn't nandroid. So he just just wiped and went to flash an older version of CM he had on SD card.
Phone would boot but said corrupted memory error...he told him to reset. He tried, didn't work. So than he proceeded to RSD the JORDAN files. It now boot loops. Any suggestions? Really would appreciate your help.
Click to expand...
Click to collapse
Try to flash SBF with RSD. here you can find some http://forum.xda-developers.com/showthread.php?t=966537
before flashing a stock rom go into stock recovery and do a factory reset. NOT from custom recovery!!
if u in bootmenu (if led is blue press volume down) is there a option in tools to formate data and Cache in ext4 and ext3? if yes, formate data in ext3. Had the same error with formate data in ext4 and flash an older ROM. u may need flash latest CM10 to get that bootmenu entries in tools.
Related
I had an earlier version of cyanogenmod installed, I went into rom manager and pressed update (or something like that). It did the whole installation thing but now it's just hanging at the cyanogenmod splash screen.
What do?
silverback88 said:
I had an earlier version of cyanogenmod installed, I went into rom manager and pressed update (or something like that). It did the whole installation thing but now it's just hanging at the cyanogenmod splash screen.
What do?
Click to expand...
Click to collapse
Have you tried to boot into recovery ? (turning it on by pressing the power button and the - volume button)
Did you backup? Always, always backup.
If not try downloading the ROM and flashing that, don't wipe just yet, if that fails you will probably need to wipe and flash again.
ok so i did a recovery of the backup i did just before trying to install cyanogen 7
FFUUUUU.... now everything is pretty much lost! even the old cyanogen is gone. What can I do?!
Was your old backup from a pre 2.3 ROM?
^^ how can i tell?
sorry for being a noob
What was the ROM you backed up before flashing CM7?
the backup i did just before trying to install cyanogen 7
Click to expand...
Click to collapse
it was cyanogenmod 6.1.3
Ok, your problem now is that the file system changed from 2.2 (Froyo) to 2.3 (Gingerbread) and you will need to flash a new version of ClockworkMod Recovery to restore that backup.
Do you have ENG S-OFF? You will be able to flash it via fastboot, if not you will have to start again from CM7 and downgrade ClockworkMod Recovery from there, then restore your backup.
I flashed the latest ClockworkMod Recovery (3.0.0.6) - I think before I tried to install CM7.
Restoring the backup means almost everything is gone, apps, settings, etc (but not everything). Did I **** it up? Will I have to redo everything?
If I have to do that anyway I might as well use CM7, but installing that means the splash screen hangs (I had the same problem with CM6, I dont remember how I fixed it)
Your right, to flash CM7 you needed CWM 3.x.x.x
Restoring that backup 6.1.3 will take you back to pre-CM7 so yes everything will be gone.
Have you tried just flashing CM7 again?
ok, trying to install cm7 again...
Don't wipe just yet, if it still hangs after flashing again you will then have to wipe.
****, it's hanging at the CM7 splash screen again
Ok, you will need to perform a wipe.
In CWM you have "mounts & storage"
Format boot & system, then flash CM7 again, (btw which CM7 ROM are you flashing?)
I did that (through the recovery or w/e) and then it was hanging at the HTC logo....
I had to restore the backup once again and am back where I was before
What can I do?
btw it's CM 7.0.0-RC2
Ok sounds like a full wipe is needed.
Again in CWM "mounts and storage" format everything except scdard, then back out and go into "advanced" and wipe dalvik cache.
Flash CM7 again, it should work now.
can i flash CM7 through the recovery console? because if i wipe everything then obviously i cant boot back into it?
Don't worry you can't wipe recovery from within recovery, so after a full wipe it will still be available.
before I do that, how exactly do i install CM 7 from recovery console? I think it was downloaded to my SD card but I dont see a straight forward option in the recovery console
my note is stucking at samsung logo. .again again it is running logo it is not opening home. . . .
hmm it shouldnt, but i had used to do like this going back from ics to gb:
flash 4.2v abbys kernel, reboot RECOVERY and then restore backup and never had any problem ^^
EdgaBimbam said:
hmm it shouldnt, but i had used to do like this going back from ics to gb:
flash 4.2v abbys kernel, reboot RECOVERY and then restore backup and never had any problem ^^
Click to expand...
Click to collapse
i had not made a backup :'(
turn off boot recovery and wipe data cache and dalvik cache. then try to boot
daraj said:
turn off boot recovery and wipe data cache and dalvik cache. then try to boot
Click to expand...
Click to collapse
again the same is happening. . .samsung logo is continuously playing :'(
Hopefully you have a GB kernel and GB ROM on your sdcard somewhere..
If not then you need to select usb mount in recovery and put those 2 things on your sdcard...now
unmount
then flash the GB kernel and then go into advanced and reboot recovery..
Now you can flash a rooted GB ROM and boot phone.
I will agree, coming back from anything based on the repacked ics is rather flakey. Even going from different versions of Stunner can be a PITA. A couple of times clearing the caches worked. Doing a full wipe worked best but I did have a couple of instances where I just had to Odin a stock firmware back on the device from a PC, reroot and then proceed to upgrade in the direction I wanted go.
If doing a full wipe from CWM does not work, I say give up and do the Odin flash from a PC with rootable OEM rom. I always go back back to a KA2 rom because that is what my phone came with.
On a side note, if you want to get rid of the yellow triangle count, the removal apk works on the repacked ics but not on the Stunner 3+. Just throwing that out there.
MrDSL said:
Hopefully you have a GB kernel and GB ROM on your sdcard somewhere..
If not then you need to select usb mount in recovery and put those 2 things on your sdcard...now
unmount
then flash the GB kernel and then go into advanced and reboot recovery..
Now you can flash a rooted GB ROM and boot phone.
Click to expand...
Click to collapse
I done a factory reset. .I just worked. .!!
Glad your heart is not paining because your note is stucking at the booting screen.. So you did your fixing by resetting?
Flash your gb with odin and choose pit and repartitions that will clear the partition have gone back and forward and no issues
And yes once flash to the gb get into recovery and clear cache and clear system
Sent from my GT-N7000 using Tapatalk 2
Hy there, will explain shortly
cm10 last quarx build, (everything works perfect)
I save data through cwm and format ext4 and then restore data
whole day goes perfect
I go to sleep and when I turn it on It gives fc in every app of the system,
1. I try to install again the cm10 build doesnt work same problem
2. try to install any custom rom that have always worked (skanky roms, maniac, whiterabbit edition... all with the correct kernel installed)
3. in all of the cases It gets freezed in boot
4. I have bricked my phone many times, and I always have done alright using rsd to flash over and start from the beginning
5. so this is what I did, flashed with RSD the same sbf as I always do but I also get bootloop
6. Im pretty sure its because the ext4 partition, and I thought flashing rsd would reset the phone format too.. what can I do now?
Please Help ty
EDIT: As its a problem of ext4 partition you must power+down and format data, then the new sbf will work ^^
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
llavsor said:
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
Click to expand...
Click to collapse
Try to wipe all from stock recovery ----> Power+Vol dwn
Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
llavsor said:
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
Click to expand...
Click to collapse
That's good sorry forget to say you need to hold VOL dwn& Vol Up at the same time then wipe all...
Good luck
Exactly the same problem here, cannot downgrade to CM7.
Any good news?
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
So the recovery won't work and will have to start with SBF. Will wait until I have the computer environment to do so.
Thanks!
Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
farsight73 said:
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Wipe all from stock recovery that's you needed to do btw before installing cm7.... Sbf is not needed.
Go to stock recovery and wipe all your ROM should boot...
Let's Go ^_^
llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
skeevy420 said:
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
Click to expand...
Click to collapse
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Since I have no luck restoring stock rom I now have the following plan.
Install ClockWorkMod recovery with ADB.
Using recovery to do a factory reset and clear cache.
Flash a CM10 ROM (or any rom that will successfully boot up my phone).
From that start over to downgrade to CM9 to find a stable ROM.
The question I have now is if I will be able to use ADB with the USB connection mode I get from the bootloader (volume up+pwr button)? Or does ADB actually require that I can boot my phone and go into some other USB mode such as UMS or MTP.
Second question. Playing with restoring stock ROM i run out of battery and now my defy wont charge (only see a big question mark when loading). Seems like I get no power when USB is connected so is there a way for me to charge the battery or do I need to find another happy camper in town with a working defy that can power up my battery?
llavsor said:
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Click to expand...
Click to collapse
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
farsight73 said:
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Thanks for very informative reply. I have a Defy 525 with red lens.
It's working.
I found a friend blessed with a defy and used that to charge the battery, tried to charge it over night with USB but it didn't work.
I then followed the steps from the last post and managed to flash a stock rom and then from there I rooted the phone with SuperOneClick, installed 2ndInit with ADB (guess you could use an apk installer from the phone as well ). I booted into recovery and flashed 7.2.0 Jordan from CM and now I am where I started a few weeks back.
Thank you all for your help.
That was the low battery problem.......
Since i had this i allways look for a full battery
If you think your defy is dead , a look for a empty battery won't be mad
Could anybody took a reminder info into beginners guide
MB525 red lense
Hi guys, need some help here. I'm sure this has been asked before but i just couldn't find any
Installed slimkat 20140406-0134 rom (cm11) last night and it's basically working. But I'm still not feeling comfortable using it as there's still bugs around. So thought of going back to cm7.2 for now. But for the life of me couldn't figure out how to get to the tool section so I can re-partition it back to ext3!!!
All I could get in to is twrp recovery and that's it. how do I even get into the bootmenu section where I can choose recovery, cpu settings, tools, etc? There's no red Moto logo with blue LED at boot up anymore
Is there any uninstall instruction somewhere, or perhaps someone should write one?
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
jh20 said:
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
Click to expand...
Click to collapse
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
aperture said:
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Click to expand...
Click to collapse
thanks. i'll remember that next time. don't know why i didn't think of that. panic striken maybe
hotdog125 said:
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
that's exactly what i did but didn't work. aromawiper seems to have worked properly but twrp 2.6.3.0 keep saying "no os installed" after i installed the gb rom and tried to reboot. tried maniac's cm7.2 and an older wiui gingerbread rom. i thought it might be a hickup and rebooted anyway and that was it.
don't know what went wrong there. has anyone actually tried this method before and got it to work?
edit: imho twrp is not worth it. it rebooted 8-10 times on me after installing cm11 and tried to get back into recovery to flash gapps. also other problems like blank backup files and my failures to install rom problem. they should have stuck to cwm until the problems are fixed.
edit 2: and i think removing bootmenu is not a good idea. more steps to take if you want to go back to cm7.2.