Related
Hi all!
Almost all ROMs out there are failing to work correctly or even boot on my Defy (red lens). Some do boot, some go to bootloop.
Here's the full story. Two days ago the latest CM10 nightly from Quarx went to bootloop, it was working just fine, but at some point the phone rebooted and didn't boot back up.
I've decided to try another ROM and installed WIUI v4 (JB) from CWM. I went to check device's internal memory and it appeared that I had 48 MB used and that that was all internal memory - the system hasn't even loaded total memory info.
I performed some search and found this thread with the similar issue: http://forum.xda-developers.com/showthread.php?t=1940503
It suggested flashing an SBF via RSD Lite. I did that using the SBF from that thread (2.2 CEE Froyo). I suppose that was my mistake since the thread referred to Defy with a green lens. However, I was finally able to boot the device. I decided to try another SBF. JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDN to be precise. Everything went just fine. I was able to root the device, install CWM using SndInitDefy 2.0, and install stable CM7 (the official one, update-cm-7.1.0-jordan-signed.zip) and Froyo kernel from WIUI.
Everything was working fine except for the camera. It was showing the following error:
"Camera error. Cannot connect to camera"
After that I though that maybe I've messed up with SBF versions. The phone is not sold in Ukraine officially and I didn't remember which SBF it used when it was shipped.
I then followed the guide from All-in-one beginners guide and installed that Chinese SBF with Version 5 CG (thus I presume I can't flash any full SBF now since this will cause a black screen and I will have to re-flash 97.21.51 SBF and do all that stuff all over). Again, I was able to root the phone and stuff. However, none of Quarx's nightlies are working, CM7.2 or 2nd-boot CM10 are simply bootlooping, WIUI v4 can't connect to any of Google's services (they constantly FC), and none of the ROMs can connect to the camera.
Currently I'm using the following:
official CM7.1.0
Android 2.3.7
kernel [email protected] #1
Build number Gingerbread GWK74
I'm okay with staying on CM7.1, but I require the camera to work. So, the question is, what should be done in order to make the camera work?
Maybe, I should change some lib files, if so, could you please provide with the link to the correct ones? I've already tried some camera fix SBF's but they didn't seem to work. If there is any additional information required, please let me know.
Any help will be really appreciated!
Thank you in advance.
Maybe you could get rid of the sbf problem(camera issue caused by wrong flashing) by flashing a defyplus sbf with group code 6. Then your camera should work.
Sent from my MB526 using xda premium
Thanks, thekguy! Will try this later today.
Nope, that didn't work, unfortunately. Flashed 4.5.1-134_DFP-125, but the camera is still failing, as well as the latest CM10. Any suggestions are welcome.
Hmm, latest cm10 2ndboot right? That's a very bad sign, since that rom indeed works with both the camera modules, and its really curious that it's not working.
Flash back to any defy bl6 sbf from this list(don't flash defy+ sbf since that approach isn't working):
http://forum.xda-developers.com/showthread.php?t=966537
Wipe data, and use the defy ultimate wiper script(it's there in themes and apps section, use ext4 version if you're on cm10 or ext3 for any other rom).
Now flash cm10 2ndboot build, and try using the camera.
Normally that should work, even if you have a green lens module, but if not so then it could be add a result of a hardware failure
Sent from my MB526 using xda premium
Yeah, I've also tried CM7 for Defy+, but that didn't work either. And I guess I pushed my device few steps closer to the brick yesterday. I flashed one of Chinese SBFs (JRDNEM_U3_3.4.3-36-1_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTINT_P011_A013_HWp3_Service1FF). It's BL7 SBF and it's known for its outstanding unbricking abilities. Didn't work for me. However, the bootloader is still accessible and I will keep playing with the phone today.
I'm getting tired of all this.
Didn't work? Camera or unable to boot?
Remember, you must wipe data from stock recovery before you can boot into the stock rom
Once you are running on the stock rom, check if the camera works. If not then follow my other post about getting to cm10 2ndboot. It may hang once on boot but it will boot after that. If still the camera is not working then I'm afraid it's beyond help
Sent from my MB526 using xda premium
thekguy said:
Didn't work? Camera or unable to boot?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Didn't boot at all, just a blank black screen. I can't enter stock recovery and the bootloader is not visible. However, if I boot up with power+vol+ and connect the phone to the desktop, RSD Lite detects the phone and I can flash an SBF. But my guess is that this would be useless since the last SBF I flashed was BL7.
Well, I'm at work right now, thus I can't try anything out right now. Theoretically, I should be able to flash any SBF with BL7, and root it using this guide http://forum.xda-developers.com/showthread.php?t=1542956
Then, flash both sbfs from that guide, and it should work.
You shouldn't get any blank screen, simply because you've got the highest possible group code, and you cannot have a wrong kernel just after flashing the sbf. It must work
Sent from my MB526 using xda premium
Thanks. Will definitely give it a try once I get home.
OK, I've managed to install 4.5.1-134 DFP-231 Retail.en.EU CEE, root it, and flashed CM10 2nd-boot nightly. However, I'm still unable to boot the phone. It shows CM10 logo spinning for 10-20 seconds and then reboots. I assume that this is the only ROM which can make the camera work. Am I right? If yes, what should I check or do in order to fix the boot looping? If I can use some other ROM, could you please let me know which one exactly and what can be done in order to fix the camera?
Thank you!
Just flashed CM10 and checked the log, there's the following message:
set_perm: chown of /system/xbin/tcpdump to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/tcpdump to 6755 failed: No such file or directory
Click to expand...
Click to collapse
Could this be a source of the problem?
Another update. I've installed WIUI v4 for GB kernel and looks like it requires less internal memory/RAM to run so I'm able to boot the phone completely. And it's showing that I have 0.00 MB of internal storage in total and 58 MB used. I guess internal memory issue is somehow related to the bootloop.
Before flashing cm10, use both the ultimate wiper scripts(ext4 and ext3 version)
After flashing cm10, go back to boot menu and select tools, file system tools and format to ext4. It should boot now
Sent from my MB526 using xda premium
Thanks for the clue, but I'm afraid that didn't work. Since I had some time and have no data to lose, I wiped the phone from stock recovery, flashed both standard 4.5.1-134 DFP-231 and rooted 4.5.1-134 DFP-231, wiped everything using both ext3 and ext4 Ultimate scripts, flashed Quarx's 2nd boot CM10, formatted data and cache to ext4 using File System tools. CM10 still bootloops, but at least now I have internal memory info displayed correctly in WIUI v4 (JB). But since it's not a 2nd boot ROM, the camera isn't working.
In fact, I've tried some other 2nd boot scripts (NEGAN-6DIC and Codenameandroid 3.6.6), but they are bootlooping as well.
Maybe there are some other 2nd boot ROMs I should check? Or maybe if I get a nandroid backup of a working system I could restore it on my phone?
Try converting to ext4 and flash after that. It is really curious why it bootloops. You must get cm10 to boot, so that the camera works. Look here for downloading a stock kernel that should hopefully fix the boot loops.
http://forum.xda-developers.com/showthread.php?t=1909242
Scroll down for the post which talks about having a compatible stock kernel which should allow 2ndboot to work(it's titled for bl7 users).
Flash this kernel after stock sbf flash, then try installing cm10.
Let's see how this goes
Sent from my MB526 using xda premium
Still no joy. Neither formatting, nor following this guide http://forum.xda-developers.com/showthread.php?t=1909242 worked. Is there a way to see boot log from a desktop? I have both Debian and Win7 on my desktop.
Thanks.
There is a way to debug using uart, but I have no experience with it. So, sbf flash+ compatible stock kernel failed? Please describe the boot loop. Does it reach the cyanogenmod logo? Or stuck at red Motorola logo? I am at my wits end at this one. All my semi bricks and other problems I could fix by the methods outlined in my previous posts, but they don't seem to work in your case. You flash full sbfs right? And are you able to boot the stock Rom?
Sent from my MB526 using xda premium
Here's how it loops:
- the phone starts
- shows red Moto logo
- blue led
- red led
- blank black screen
- HW buttons blink once
- CM10 spins for approx 5-10 seconds
- the phone restarts and all the steps repeat
Yes, I'm able to flash full SBF (BL7 ones). I'm able to boot into a stock ROM, I can flash modded SBF for BL7 (the rooted one). I've tried flashing CM10 SBF, but the phone booted into a bootloader and showed an error, with set of numbers. Looks like because of the kernel (my guess is that SBF contains non-2nd boot version of CM10).
If I install WIUI v4 right after I flash rooted SBF I have no issues with the internal storage.
If I install 2nd boot CM10 (Kayant's, Quarx's) I get a boot loop (Ultimate Wipe doesn't help)
If I install WIUI v4 after CM10 (without re-flashing SBF's), I get 0.00 internal storage, but wiping data/cache from stock recovery solves the issue.
Unfortunately, wiping data/cache from stock recovery doesn't do the trick for CM10 2nd boot builds.
One more thing, after I flash CM10 and try to wipe data/cache from stock recovery for the first time, it shows recover log errors. There are errors when entering stock recovery after that.
Might be a false trail, but what about wiping from custom recovery? Dalvik cache wipe?
This indicates that the kernel had loaded before some other problem caused the phone to enter into boot loop. What about the camera in the stock build? Same error as before?:banghead:
The cm10 sbf probably had a lower group code(bl6 perhaps) hence that approach won't work, and even discarding that it will yield the same results as before.
Also, in stock, check if the kernel version changes after you flash the compatible stock kernel from the thread I had mentioned earlier. This is important because otherwise there is no chance for cm10 to boot.
Sent from my MB526 using xda premium
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
Hello,
I currently have defy with the later lens with the latest Quarx CM10 nightly installed. While CM10 is generally awesome, it turns out to be not stable enough (radio crashing, sudden restarts) and a bit too slow. Now I would like to downgrade to CM7.2.
I tried just flashing CM7.2 after a wipe which yielded a non booting device and me flashing back CM10.
Does anyone have any experience with reverting the Defy to CM7.2?
Thanks for your help!
You should change ext4 format of data to ext3 before flashing cm7.
1. Boot to recovery
2. Wipe Delvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3. It don't show any progress. Wait for few time. It shows done.
5. Flash cm7
IMPORTANT don't attempt another wiping of data/cache after filesystem conversion.
Sent from my MB525 using Tapatalk 2
pradeeppk said:
You should change ext4 format of data to ext3 before flashing cm7.
1. Boot to recovery
2. Wipe Delvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3. It don't show any progress. Wait for few time. It shows done.
5. Flash cm7
IMPORTANT don't attempt another wiping of data/cache after filesystem conversion.
Sent from my MB525 using Tapatalk 2
Click to expand...
Click to collapse
I want to do the same with my green lenses. I have CM10-2nd boot, should I install CM7.2 for defy+ or just regular defy?
thanks in advance.
I don't know WHY all this redundant question? Is so hard to search a little? This problem was debated by enough time.
Sorry, I did search and found just this thread...
Just tried here, and cm7.2 for Defy+ worked just fine.
Hmmmm, last time I had to do this I reflashed a stock Froyo rom and did the whole process of rooting/installing 2ndinit/installing CWM again. Installing CM7 then wiping dalvik/cache/data did not work.
If a simple flash/wipe doesn't do the job, reflash Froyo again and follow the instructions to install CM7.
I haven't got the option in Tools to format in EXT3, there's only options to share SD, drivers, systems... Why?
I'm using a Quarx CM10-20120924-NIGHTLY-mb525.
Maybe I need to upgrade to CM10.1 to have that option? Which ROM could be good?
I'm using a Defy (mb525)
Miguemiguemigue said:
I haven't got the option in Tools to format in EXT3, there's only options to share SD, drivers, systems... Why?
I'm using a Quarx CM10-20120924-NIGHTLY-mb525.
Maybe I need to upgrade to CM10.1 to have that option? Which ROM could be good?
I'm using a Defy (mb525)
Click to expand...
Click to collapse
Just wipe from STOCK recovery .. it will format partitions to EXT3 and CM7 should boot =)
yzeroy said:
Just wipe from STOCK recovery .. it will format partitions to EXT3 and CM7 should boot =)
Click to expand...
Click to collapse
Wipe from STOCK recovery and then go to Custom recovery and flash directly the rom?
Miguemiguemigue said:
Wipe from STOCK recovery and then go to Custom recovery and flash directly the rom?
Click to expand...
Click to collapse
No just install CM7, GAPPS, and reboot to Stock recovery and there do Factory reset and reboot.
Now your CM7 should boot
Similar, but a little different
My requirement is to give CM 10.x one more try, this time with a clean install.
So, what should I do?
I posted here: http://forum.xda-developers.com/showthread.php?t=2192807
Do I need to use stock recovery, format, install SBF and then install the latest nightly?
Or something else as well?
s_u_n said:
My requirement is to give CM 10.x one more try, this time with a clean install.
So, what should I do?
I posted here: http://forum.xda-developers.com/showthread.php?t=2192807
Do I need to use stock recovery, format, install SBF and then install the latest nightly?
Or something else as well?
Click to expand...
Click to collapse
Any thoughts?
CM 10.1 to stock
I have gathered the following instructions so far:
1. Boot to recovery
2. Wipe Dalvic cache, data/cache
3. Go to tools menu in recovery.
4. Convert file system from ext4 to ext3.
5. Flash stock ROM (Where can I find this?)
Once I am with stock ROM, I would like to install CM 10.1 again, since I am not happy with the performance of the current CM 10.1 (perhaps 2 months old), so I would like to start from scratch.
Am I missing anything important?
Once you wipe data, system and cache in TWRP(of your current installation), your new installation is clean(as it would after stock rom/sbf flash)
You can cross check using the inbuilt file explorer in TWRP
Sent from my MB526 using Tapatalk 2
Title says it all: I get symlink: some symlinks failed, status 7 error, installation aborted when I try to install Quarx's CM10 (2nd boot). Haven't tried any other JB, since I can't find any that fits. Maybe something with 2nd boot? It seems not to work on my phone...
I tried google-ing the problem, found some information about removing lines from updater-script, but the line was not even there (something with asserts).
Defy red lens MB525
Try a system wipe. That error is because of some filesystem problem, not 2ndboot
Sent from my MB526 using Tapatalk 2
I tried wiping with AROMA wiper yesterday: ext4, wipe data, system, cache, dalvik, then NO reboot and install cm 10... it failed as hell.
ive had the same issue as you with cm10 2ndboot. i moved on after trying to get it installed for months. 10.2 is awesome! just make sure you start from a fresh sbf flash and reroot and all that jazz. also, start with twrp!
undyingvisage58 said:
ive had the same issue as you with cm10 2ndboot. i moved on after trying to get it installed for months. 10.2 is awesome! just make sure you start from a fresh sbf flash and reroot and all that jazz. also, start with twrp!
Click to expand...
Click to collapse
thanks for the advice but i can't seem to install twrp. goomanager is not available for stock éclair/froyo, and without installing any cwm i can't install twrp. also, i tried to install twrp from cm9's cwm, it wrote success but after reboot i still had cwm. WUT
Dummy question: did you try to download another ROM?s zip file ?
Alka-Seltzer PLUS said:
Dummy question: did you try to download another ROM?s zip file ?
Click to expand...
Click to collapse
I tried different nightlies of JB 4.1, 4.2, 4.3, MIUI JB. Also did clean install with 0 success. I'm getting close to the problem, and reached this far:
1.: My CWM (5.x.x.x) does not support the 2nd boot updater script. I don't know how could I upgrade to CWM v6 (seriously, I searched a lot but nothing.)
2.: I can't install TWRP. I mean... Éclair and froyo does not support GooManager to install from an app, and I can only install CWM from 2ndinit.apk. From CWM I install TWRP, it says: "Whoah you are great bro, reboot recovery!" I do that and boom CWM again.
Srsly.: HOW can this happen to me? Other ppl resolved this problem by flashing DFP sbf to their normal Defy (red lens). I won't do that. You know, there must be a way I can install CWM v6 or TWRP. But how? If anyone gives me a solution for my problem which is going on for half a year... I'll get a heart attack I'll be so happy
Uhm.... recently i had to start from SBF and had no problem installing last ( Quarx's ) build of 4.1.2 after having installed the first 2ndinit i downloaded from the web ... so... write exactly your steps ( i know, i know, .. but .... where'R talking through a monitor and misunderstandings are waitnig for us )
Alka-Seltzer PLUS said:
Uhm.... recently i had to start from SBF and had no problem installing last ( Quarx's ) build of 4.1.2 after having installed the first 2ndinit i downloaded from the web ... so... write exactly your steps ( i know, i know, .. but .... where'R talking through a monitor and misunderstandings are waitnig for us )
Click to expand...
Click to collapse
I start from sbf (Froyo). Install 2ndinit apk, install 2ndinit, reboot, wipe data cache dalvik, (try to) install cm10.x > status 0 or status 7
I start from cm9(epsylon build). Reboot into recovery, (try to) install cm10.x > status 0 or status 7
I start from cm9(epsylon build). Reboot into recovery, AROMA Wipe (system, data, cache) into Ext4, (try to) install cm10.x > status 0 or 7
After these, I can't revert to any rom even if i format to ext3 with AROMA Wiper. Cuz' my defy goes soft-bricked and i have to recover it RSD Lite.
Do not reboot after wiping/formatting system. Immediately flash some ROM. Ext3 --> CM7.
Sent from my MB526 using xda app-developers app
gyorgyszemok said:
I start from sbf (Froyo). Install 2ndinit apk, install 2ndinit, reboot, wipe data cache dalvik, (try to) install cm10.x > status 0 or status 7
I start from cm9(epsylon build). Reboot into recovery, (try to) install cm10.x > status 0 or status 7
I start from cm9(epsylon build). Reboot into recovery, AROMA Wipe (system, data, cache) into Ext4, (try to) install cm10.x > status 0 or 7
After these, I can't revert to any rom even if i format to ext3 with AROMA Wiper. Cuz' my defy goes soft-bricked and i have to recover it RSD Lite.
Click to expand...
Click to collapse
No rooting between sbf (Froyo) and installing 2ndinit apk ?
hotdog125 said:
Do not reboot after wiping/formatting system. Immediately flash some ROM. Ext3 --> CM7.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
Ehm, I didn't reboot after system format, I know that I shouldn't or I get softbricked.
Alka-Seltzer PLUS said:
No rooting between sbf (Froyo) and installing 2ndinit apk ?
Click to expand...
Click to collapse
Yea. It's rooted by default when i flash it....
gyorgyszemok said:
Yea. It's rooted by default when i flash it....
Click to expand...
Click to collapse
I would try to check the md5 at this point
gyorgyszemok said:
Ehm, I didn't reboot after system format, I know that I shouldn't or I get softbricked.
Click to expand...
Click to collapse
I started with sbf, Framaroot, 2ndinit. Then I directly flashed CM10 (9th July) and it flashed successfully. The latest dual recovery has CWMv6, but it's only for CM10 ROMs. Have you tried pre-TWRP builds (maybe the November builds)?
Or maybe, other ROMs like PA, PAC, etc.?
gyorgyszemok said:
Title says it all: I get symlink: some symlinks failed, status 7 error, installation aborted when I try to install Quarx's CM10 (2nd boot). Haven't tried any other JB, since I can't find any that fits. Maybe something with 2nd boot? It seems not to work on my phone...
I tried google-ing the problem, found some information about removing lines from updater-script, but the line was not even there (something with asserts).
Defy red lens MB525
Click to expand...
Click to collapse
Happened to me to before. Try change your kernel. Stock kernel cant flash cm10 and its variant. It'll give status 7 error. When i change to other kernel ex;BL v12 no problem at all.
aiis89 said:
Happened to me to before. Try change your kernel. Stock kernel cant flash cm10 and its variant. It'll give status 7 error. When i change to other kernel ex;BL v12 no problem at all.
Click to expand...
Click to collapse
I forgot to add that my problem got resolved like a month ago.
My main problem was that I couldn't install any JB rom because of status 0, status 7 or bootloop (always), so I went radical:
I flashed DFP231.sbf (for defy plus) on bayer lens defy (MB525!), used Framaroot to root, installed LATEST(!) cwm, and then I could install CM10.x with no problem!
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.