Related
I accidentaly installed the CM9 kernel when i should have installed the CM7 one with ICS. Then i made a nandroid restore of my previous CM7. Than... phone dead. Starting but no CWM no ROM booting.
As i have had CM7 with GB kernel( i think) i flashed ( not knowing) an old SBF than didn't booted. I tried the JORDN_U3_97.21.51 T-Mobile It boots, i can root it, install CWM.
But than when i try to install a CM7 nightly ( installed ok) it dies again. Starts but No CWM no Rom booting.
What to do? I don't know what SBF to flash or what method to install?
Problem update I red that the above SBF has a CG Version 3: SBF 2.51 (Éclair) (Defy) so i installed several CG Version 4: SBF 3.4.2 (Froyo) (Defy).
They don't work. RSD says PASS but phone is dead .No stock recovery no boot. Only way to get it back to life is if i flash the eclair again.
I red that if i get a back screen when booting i have installed a lower CG version. As i tested with version 4, version 5 GB is the only option. I didn't try it out because there are some issues. Froyo would have been much more easier.
i think many readers of your post are getting problems with understanding your problem ...
you got a stock defy, rooted it, installed 2ndinit via apk, booted into recovery (vol- at blue led) and installed CM7 zip ??? correct ???
after succesfull install of CM7 your phone doesn't turn on? Black screen?
black screen after zip is (i think) impossible ... but i can fail ...
i would like to help you, but first you have to give the detailed steps you did and what you wanted to do ...
To make it simplier
I installed the JORDN_U3_97.21.51 T-Mobile (which is 2.1 update1) It boots, i can root it, install 2nd-init > CWM. Set Normal boot.
Than in CWM nothing works.
Installing a CM7 nightly, or restoring a CWM backup.
I install a CM7 nightly like this> In CWM> Custom Recovery> Wipe data, wipe cache> install Cm7 zip, install Gaaps zip. After this, phone restarts, screen is on, logo appears and i wait and wait. Nothing happens.
Do i have to install a special CM7 build?
The CWM backup does not restore. It says that files are missing ( like android.secure..) I am not interested in keeping downgrade ability. i would like to try another SBF. I am not 100% sure what SBF to use from the wiki page.
I red that the SBF i installed has some special "problems" here> http://forum.xda-developers.com/showthread.php?t=905371. They are talking of a CWM revoery app by tenfair here> http://forum.xda-developers.com/showthread.php?t=875233
Maybe that works^. Will try it after the phone is fully charged.
so, ok ... thats detailed as i wish
ok, the problem is clear i think ... first of all eclair is not a nice system for a defy ... upgrade to froyo or even gingerbread ... (keep in mind, that GB has problems with green lens camera) ...
than you can root it with SuperOneClick e.g. ... if this is running correctly, you can install 2ndinit via apk ... then boot, vol- while blue led (i know, you know how ) ... in that clockworkmod recovery you can wipe the devices data and cache partition (even wipe dalvik cache in advanced menu) ... then install CM7.2-nightly-.... .zip ... you may have to flash an fixed sbf with the nessesary kernel for CM7 at this point to boot ...
if this is working fine, you can install the gapps.zip via recovery ...
also try to set boot to 2ndinit in boot-menu ... i don't think it's "normal" boot for CM7 ... but i can't try at the moment cause of my bricked defy ...
Thanks for the reply.
The problem is that i can't install other Froyo SBF's. Will try Gingerbread SBF. The last froyo didn't boot, will try a new one. Weird, i know. Maybe someone can tell me which CM7 to flash? An older one with Kernel ? I didn't think the install would be so tricky.
Froyo Full-SBF doesn't boot on your defy?
be aware of flashing Gingerbread then ... if GB doesn't boot, you will have a problem downgrading to froyo / eclair ...
it sonds crazy, that froyo isn't booting on your device ... have you done a full wipe after froyo sbf? it's important ...
I'm on the Eclair SBF right now. What should i do? Go into recovery and do a wipe or install a new Froyo SBF? It's about the CG value maybe. I understand the mechanism but don't know how to check the CG value. If i search for my current eclair SBF i get all sorts of weird stuff. Nevertheless i will try and try until i succeed. It took me a while to figure out the Rooting method. Superoneclick does not work. It's a special method for the 2.51.
The thing is that i wanted to go the my Nordic SBF( the one Quarx used during the first days of CM7) and it didn't booted. That's why i tried this one. Funny ho flashing the wrong kernel(CM9 instead of CM7) can brake things like this. What i don't understand is how my CWM backup didn't restore. It restored well, finished, then phone dead. No CWM.
edit: i just red: 2.51 is Not downgradable. But no downgrade to what??? Will try to some Froyo SBF's, see if works. But that does not solve my CM7 issues.
Tried a few Froyo SBF's. Wiped data/cache in Stock Recovery. RSD says PASS than phone does not boot. Only the 21.51 eclair works all the time.....Where next?
Update 2 got it to work with this>
http://forum.xda-developers.com/showthread.php?t=1486731&highlight=cg
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Glad it worked.
DJ_Synergy said:
OMG i dn't understand what was going on with your defy, but i'm happy to know your on the road again
the only sbf that are running are the stock eclair you have (21.51) and the modded BL6 with Froyo Kernel ???
Click to expand...
Click to collapse
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
HI Deonix, I have the similar problem. However I am unable to use RSDlite as it gives a failure messg when u click start. I tried JRDNEM_U3_3.4.3-36-1.7.sbf and JRDNEM_U3_2.59.0_CHN_P3_SIGN_SIGNED_UCAJRDNEMARAB1B50AA028.0R_USAJORDANRTINT15_P003_A020_HWp3_Service1FF.sbf.
Both failed, I will try using the rsdlite after the cache and factory rest this time based on your suggestions. Can you tell, if your adb command was listing your device, as mine is not.
my CWM is also gone I get some old android recovery system 3e instead which fails after signature check.
Hi,
I think I know what is your problem.
I also installed the firmware JORDN_U3_97.21.51 and now I can only install any Custom ROM after installing the firmware fix for JORDN_U3_97.21.51.
I did upload it for you: http://www.4shared.com/rar/o02VEk_v/firmware.html?refurl=d1url
It is the following:
Install JORDN_U3_97.21.51;
Rootear;
Install the Recovery;
Install the fix;
enter the recovery and install any rom you want, remembering to delete the caches (data and Dalvik cache)
ps: have 100% of the battery before installing the SBF.
any problems let me know.
Sometimes you could get stuck in a bootloop and all you need to do is pull battery and reboot
Sent from my MB525 using xda premium
Same Problem, Please help!
Deonix said:
Yes but now i am running CM9 flawlessly. So happy. The only thing that bothers me is the Chinese Boot screen )). But that can be changed. It's great that one SBF works, moded or not. I tried like 6,7 other Stock sbf's before. So a message to whom tries to install SBF's: Stay away from JORDN_U3_97.21.51 SBF. Even the Rooting method is awful (until you find it) .
Click to expand...
Click to collapse
Hey bro.
Even i have got the Defy working, but its not detecting the device when connected to the computer, i have done all the basic troubleshooting, is it working for you??
is it bcoz this room is for ME525??
-Solved btw-
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
How To Flash ICS(Defy Builds)
1:Head Over To Stable recovery
2:Wipe Data
3:Install ZIp from SD Card
4:Select ICS(Defy) .zip
5:Flash
6:Flash Gapps and CM7 Kernel
7:Clear Cache and Dalvik Cache
Click to expand...
Click to collapse
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
FAQ:
Q: I installed 08/12 build(or newer), but it gets stuck at the CM boot logo. What do I do?
07/12 contains the required 2.3 kernel. 08/12 and newer do not. If you have installed 08/12 or newer, enter recovery and flash the 2.3 kernel, then reboot. This applies only to Defy owners; Defy+ owners already have 2.3 stock ROM and kernel, so they do not need to apply the kernel.
In fact, the kernel zip for Defy owners is the kernel from Defy+.
Click to expand...
Click to collapse
I've tried everything I can think of. Can anyone help?
Thanks.
pk92 said:
Hey all. I've just tried installing CM9 using the instructions HERE.
I used the second options..
I used the most recent CM9 rom from here.
(CM9-NIGHTLY-120319-Defy.zip 19-Mar-2012 23:15 104M )
I got my kernels from this thread. I've tried both CM7 (2.2 kernel) and CM9 (2.3 kernel). With the CM7 2.2 Kernel, I get stuck on the "Motorola" logo, and with CM9 2.3 kernel I get stuck on the CM9 boot logo (1 hour + now)
From the FAQ thread I found this (below), but as I said I've tried both kernels.
I've tried everything I can think of. Can anyone help?
Thanks.
Click to expand...
Click to collapse
Hi,
Can you also provide the following info:
Which ROM did you have as stock?(Was it a froyo kernel or GB kernel as stock)
If you already had GB ROM in your phone you don't need the kernels to be installed!
It was a Froyo kernel
He's right. U don't have to flash a kernel if u were on froyo (2.6.32.9-gb08c3c8). Just make a wipe after installing the cm9 rom.
U only have to pick the right version. There are froyo-cm9 builds and GB-cm9 builds (so if u are on GB-kernel right now, take a GB-Build).
Or try the "codename android 1.5.5"... (froyo-kernel!) it's ported from the nexus
I'm testing this rom right now and for me it's working much better than cm9 builds.
Greetz
I recieved a pm suggesting installing cm7 then cm9 over, but more bootloop..
Sent from my Huawei_8100-9 using XDA
Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA
pk92 said:
Oh, its a cm7 bootloop now by the way, forgot to mention that
Sent from my Huawei_8100-9 using XDA
Click to expand...
Click to collapse
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.
I have no idea if it's Quark or Epsy :S
hboy1337 said:
Well, I think there is no need to flash cm7 before? (I didn't and it worked, correct me if I talk bull****)
Try to install the zip, and AFTER that make a wipe (do not boot in system after installing, first the wipe than boot!)
Is it a quark or epsy? When I flashed the epsy over quark I had big problems so I had to start again.
Click to expand...
Click to collapse
pk92 said:
I have no idea if it's Quark or Epsy :S
Click to expand...
Click to collapse
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....
pranks1989 said:
Hi,
Well you are correct you do not need to flash CM9 above CM7! it's Quark or Epsy do not matter. What matters is the kernel! If you have a Defy+ or stock GB use the CMs for Defy+(preferably Quarx's because they are more updated and he is the only dev with a Defy+) and don't flash any extra kernels. If you have Defy or Froyo kernel then use CMs for Defy. Always remember two golden rules after flashing ROMs:
1.) Wipe data.
2.) Wipe Dalvik.
In fact even after or before a full SBF you may not be able to boot until you do a data wipe from stock recovery! (Seen that in some cases and in mine case too!) ....
Click to expand...
Click to collapse
What I usually do when installing roms is this:
-Enter Stable Recovery
-Factory reset & clear data
-Install Zip from SD Card (Defy CM9.zip)
-Wipe cache
-Wipe dalvik cache.
So I need to do a Factory reset & data wipe in stock before flashing CM9?
I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)
pk92 said:
I've managed to get the CM9-NIGHTLY-120112-Defy+.zip rom working from here.
I installed the CM7 kernel, then the CM9 kernel ontop of that, then installed gapps, and wiped cache/dalvik. (though I'm not sure wiping dalvik worked, as when I clicked it it just refreshed, didn't give me the option to confirm that I want to wipe dalvik)
However, this doesn't have any mobile network, and a lot of settings options are missing..
I'm still trying to get the CM9-NIGHTLY-120319-Defy.zip rom working from here working, but it's stuck on the bootloop.
If I try the baseband switcher in-rom then it asks me to restart, and then once it has restarted it goes back to factory settings (the welcome screen to set up the "new" phone)
Click to expand...
Click to collapse
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!
pranks1989 said:
For CM9 you can do a data wipe from CWm itself, don't do from stock. Only if you do a full SBF flash do a data wipe from stock. And the CM9 you are using is toooo old!!! Quarx's CM9 for Defy+ are much newer! So try that here . 17th March is the latest one. That should run fine.. Worked great for me..
Hey I see once you were using CM for Defy(Dint work for you as you got bootloop) and next moment you were trying CM9 for Defy+(which worked) !!! :O First be sure which kernel you have in your original ROM(flashed SBF)!!
Click to expand...
Click to collapse
I eventually decided to flash a froyo SBF (2.2.2), and flashed CM9 Defy from here. Suggested to me by Pottkopp.
I didn't flash any kernel and it worked fine.
Also installed Pottkopp's AIO.
So, all solved
Can someone help me?
Ok!
So i have green lensed defy. I already had CM9 installed( installed it using normal procedure). So i decided i will return to stock, by recovering backup. So i did. After a while on stock, i decided to go back to CM9. I forgot to do factory reset, and after install wipe chache and dalvik.I booted phone, and entered requesting data. I after that got back to recovery and did factory reset via custom recovery, and installed it again using correct method. My phone seems a bit slower than before, and did i damaged my phone?
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
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!
I tried to install TWRP from CWM. The process goes down, it tells me to reboot recovery. I rebooted, and still, i have CWM. What should i do?
defy red lens cm9 epsylon
if youre not opposed to starting over with a fresh sbf, then do just that. this time stick to twrp. seems to be doing much better than CWM
undyingvisage58 said:
if youre not opposed to starting over with a fresh sbf, then do just that. this time stick to twrp. seems to be doing much better than CWM
Click to expand...
Click to collapse
but i can't install twrp. i just does not replace cwm, and from froyo or éclair i cant install it with goomanager. from cm9 goomanager tells my device is not supported
gyorgyszemok said:
but i can't install twrp. i just does not replace cwm, and from froyo or éclair i cant install it with goomanager. from cm9 goomanager tells my device is not supported
Click to expand...
Click to collapse
my next advice is to learn how to manage your own roms without goomanager. for the most part you can read the tutorials on the defy wiki page to install "2ndInit Recovery". then use the 2ndinit recovery to install twrp. from there you install 10.2/4.3 and enjoy. just make sure you know well how to do sbf flashes just in case you goof and softbrick your phone in the process.
plus you should be able to install goo manager once youve settled in with twrp.
undyingvisage58 said:
my next advice is to learn how to manage your own roms without goomanager. for the most part you can read the tutorials on the defy wiki page to install "2ndInit Recovery". then use the 2ndinit recovery to install twrp. from there you install 10.2/4.3 and enjoy. just make sure you know well how to do sbf flashes just in case you goof and softbrick your phone in the process.
plus you should be able to install goo manager once youve settled in with twrp.
Click to expand...
Click to collapse
You misunderstood me maybe. I never used Goomanager. The first time I did was like 2 days ago when I found out I can't install CM10.x with CWM v5, but v6 or TWRP, and tried to install TWRP from it. It didn't work. Also, the TWRP flashable zip won't install from CWM. I mean... It says it's ok and reboot recovery but nothing. Gwah I know all about sbf flashes in case of softbrick and all...
edit: im very, VERY familiar with cwm... never used any apk to manage my roms just 2ndinit to install.
gyorgyszemok said:
You misunderstood me maybe. I never used Goomanager. The first time I did was like 2 days ago when I found out I can't install CM10.x with CWM v5, but v6 or TWRP, and tried to install TWRP from it. It didn't work. Also, the TWRP flashable zip won't install from CWM. I mean... It says it's ok and reboot recovery but nothing. Gwah I know all about sbf flashes in case of softbrick and all...
edit: im very, VERY familiar with cwm... never used any apk to manage my roms just 2ndinit to install.
Click to expand...
Click to collapse
theres nothing else i can help you with then. all i can say is start from sbf flash and stay away from cm 10 2ndboot
Maybe not enough memory?
Sent from my MB526 using xda app-developers app
undyingvisage58 said:
theres nothing else i can help you with then. all i can say is start from sbf flash and stay away from cm 10 2ndboot
Click to expand...
Click to collapse
yeah... but i'd like to try it at least...
hotdog125 said:
Maybe not enough memory?
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
I don't think so. Something is very fishy about my phone. very-VERY strange... I can't install cm10.x cuz' of no update-binary support in cwm v5, and i can't find a way to make TWRP work, nor can I find any CWM v6 install methods... srsly WUT EVERY OTHER stuff works as intended. everything. all roms before jelly bean. i need to make twrp work or a cwm v6 installation.
gyorgyszemok said:
yeah... but i'd like to try it at least...
I don't think so. Something is very fishy about my phone. very-VERY strange... I can't install cm10.x cuz' of no update-binary support in cwm v5, and i can't find a way to make TWRP work, nor can I find any CWM v6 install methods... srsly WUT EVERY OTHER stuff works as intended. everything. all roms before jelly bean. i need to make twrp work or a cwm v6 installation.
Click to expand...
Click to collapse
Only CM10.2 needs the new CWMv6. CM10 and CM10.1 should work.
Your phone seems to trolling you:laugh:. But seriously, as a last resort I would flash DFP sbf. Gingerbread isn't half bad (especially with MS2Ginger, which is really stable and is compatible with Green Lens too).
hotdog125 said:
Only CM10.2 needs the new CWMv6. CM10 and CM10.1 should work.
Your phone seems to trolling you:laugh:. But seriously, as a last resort I would flash DFP sbf. Gingerbread isn't half bad (especially with MS2Ginger, which is really stable and is compatible with Green Lens too).
Click to expand...
Click to collapse
Well then it's trolling me 'cuz CM10 gives the same status 7 error. It IS trolling me. But i'm scared of flashing a DFP sbf. What if things go wrong? I won't be able to rollback then.
You can try to use twrp on gb roms by replacing the boot menu folder in system by that of cm10 or later. Try once with a clean folder, and once by copying over the existing files.
As for defy plus sbf, if you have a green lens, camera won't work on any gb except ms2ginger. In addition a battery patch must be flashed after every rom for full charging. For red lens only battery patch has to be flashed.
None of the above applies to cm10 and later.
Sent from my MB526 using Tapatalk 2
gyorgyszemok said:
Well then it's trolling me 'cuz CM10 gives the same status 7 error. It IS trolling me. But i'm scared of flashing a DFP sbf. What if things go wrong? I won't be able to rollback then.
Click to expand...
Click to collapse
If things go wrong, try a different SBF.
thekguy said:
You can try to use twrp on gb roms by replacing the boot menu folder in system by that of cm10 or later. Try once with a clean folder, and once by copying over the existing files.
As for defy plus sbf, if you have a green lens, camera won't work on any gb except ms2ginger. In addition a battery patch must be flashed after every rom for full charging. For red lens only battery patch has to be flashed.
None of the above applies to cm10 and later.
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
I tried replacing the bootmenu folder with different apps, but all got some "Operation failed!" or "Error with files" in itself, so I also tried to replace some of the files 1 by 1, they still failed. So that could be the reason why the zip won't flash properly... Maybe some safety option somewhere in CM9??? My phone can't seem to handle the recovery zips, only the 2ndinit apk. Very strange!
That must be done from recovery. I recall helping someone replace the recovery using a flashable zip because only a legacy recovery worked for him. I think it was zer0-gravity. Check my posts on that.
Replacing the recovery files with twrp ones in the zip I had made on that thread should with hopefully.
Also, your problems indicate file system errors, and I'll advise you to flash a different(higher) sbf, since that has in the past worked out well, for me and others. Beyond this point I'm out of ideas.
Sent from my MB526 using Tapatalk 2
thekguy said:
That must be done from recovery. I recall helping someone replace the recovery using a flashable zip because only a legacy recovery worked for him. I think it was zer0-gravity. Check my posts on that
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
another fast question. i recover my phone using the JORDN_U3_97.21.51 method, after that i have to do a root, nandroid, then instantly flash a fixed sbf (firmware.sbf...). its cuz i got the phone 2nd hand, and he f-ed up smth upgrading to gingerbread or so... can it be the root of my problem?
http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
Why do you need a fixed sbf? After rooting try directly 2ndinit. Don't restore nandroid. Also, root using framaroot since its much easier and faster. You can jump from 2.1 to
2ndboot directly.
Sent from my MB526 using Tapatalk 2
thekguy said:
Why do you need a fixed sbf? After rooting try directly 2ndinit
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
Cuz' my mb525 got flashed a GB sbf accidentally, from which you can't downgrade (by its user before me), and you can only recover it from éclair via the method i linked. other sbf's wont work
Ok, so when you flash the first sbf, and root, what stops you from directly using 2ndboot at that point
Sent from my MB526 using Tapatalk 2
thekguy said:
Ok, so when you flash the first sbf, and root, what stops you from directly using 2ndboot at that point
Sent from my MB526 using Tapatalk 2
Click to expand...
Click to collapse
It just won't install, with status 0 or 7.
But right now I grew tired of this problem and i will flash a DFP 231.sbf from here:
http://forum.xda-developers.com/showthread.php?t=1542956
I will follow these steps. Can i do that? (MB525 Red Lens)
edit: 4.5.1-134 DFP-231 Retail.en.EU CEE
Yes. Flash that and root with framaroot.
Don't follow the guide for rooting, just flash dfp 231 , if it hangs on moto wipe data and cache from stock, and use framaroot.
Depending on eu or cee you've flashed, you may require a kernel to boot successfully with 2ndboot roms(otherwise you will just hang even after waiting a lot). It can be found in the defy custom kernel thread in General
Best of luck
Sent from my MB526 using Tapatalk 2