TLDR: See this post for the solution; but do read through the thread, lots of good info!
I've got a MB525 for parts, seller got rid of it because it won't boot up anymore. I've tried it and it shows black screen but it can be seen over USB and I can flash .sbf files. Now, I'm curious whether it can be made to work after all.
First I've tried most of the smgver=4 stock .sbf files but no luck, still got black screen. From what I've read, black screen means the efuse has blown to a higher version. So I tried the JORDN_U3_97.21.51 (smgver=5). Still nothing.
The only thing left would be to flash a Defy+ .sbf, I've seen people recommend DFP-231 Taiwan retail or similar, hopefully a smgver=6 or 7 would work.
I've no idea what the seller did to the poor thing, nor what ROM it came with originally or from where.
Am I right that I should try a Defy+ .sbf? On the one hand, no risk really, I got it for pennies so no big loss. On the other, it just irks me that a potentially fully working Defy should just be abandoned for scrap.
You can try it. But if your defy is green lens the camera won't work on stock Rom only on custom Rom CM10.....CM11.
Sent from my MB526 using Tapatalk
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
wirespot said:
I intend to install a custom ROM anyway. The stock ROM is just to get me going, since right now flashing a .sbf is all I can do. Later on after I gain access to a working system I will install a CM version via recovery. Does that sound ok?
Click to expand...
Click to collapse
Try DFP-231. If it works, you can go ahead with custom ROMs.
I've successfuly flashed DFP-231. By "successfuly" I mean it now shows the Moto logo and I can enter bootloader (version 10.00, FWIW) and the stock recovery.
But it won't go past the Moto logo, shows it for about 10 seconds and then it reboots, forever. I pulled the battery after ~10 reboots in a row.
Yes, I did a factory reset from recovery (ie. cache and data wipe).
Any idea what might be causing this or what else I can try?
Try to reflash sbf.
And say "bye" to your battery charging via phone.
I've been trying all kinds of DFP-231 .sbf images. So far no luck, still got a few to go. Some of them have a longer delay, such as the first Moto logo staying on for more than 10 seconds – some for 20-30 seconds... but eventually they all bootloop.
I have another Defy+ so I can charge the battery through that one, but why do you say I can't charge through this one anymore?
PS: I've just realized that the stock recovery can flash stuff from the SD card. Would it be ok if I take a nandroid backup and slap it in there? Does it matter from what kind of system the backup is from eg. stock, a CM version etc? Or will anything work?
For battery you can check lasts posts of my problem here http://forum.xda-developers.com/showthread.php?t=2568049... I have never solve it .
Try ti omap blank flash option in rsdlite
Stock recovery cannot help unless you can brute force or steal Motorola's private key
You could try making a custom sbf, which would include custom recovery, from where it could work out.
@sterver1 the battery issue is an exception, it does not occur for most
Sent from my MB526 using Tapatalk 4
Oh, so ok. I'm only unlucky...
Good luck...
Still no go unfortunately.
I tried DFP-231, including with TI OMAP blank flash option. If TI blank flash didn't work, am I looking at a hardware problem?
To recap: it's a MB525 (unknown whether red or green) stuck in bootloop: will show Motorola logo for ~10 seconds then restart and repeat forever. I can enter bootloader and flash SBFs but so far none of them helped. I can enter stock recovery and wipe /data and /cache, still no help from there. It was already at BL7 when I got it (tried lower versions first and got blank screen, only BL7 will allow it to boot).
Cannot flash ZIPs from stock recovery because it will only accept ZIPs signed with Motorola's private key which I obviously don't have.
I've read that the wrong region SBF might be the bootloop cause so I will still try out the rest of the official BL7 SBFs, just in case.
The only thing left I can think of is to somehow put custom recovery in there so I can try flashing a custom ROM.
But how do I build a custom SBF with 2ndinit and CWM or TWRP? I have the unpacker and I know how to unpack and repack a SBF. I also know that CG39 is an ext3 image of the /system partition, but that's about it. Which CG files do I have to modify and how?
I'm also not clear on what a "fixed SBF" is. I've noticed that it usually contains only certain CG files, but not sure how it works together with other types of flash and what good are they.
You can flash one of the cm 10 sbfs in the dev forum. Basically you need the sbf to contain the boot menu and recovery to try flashing from custom recovery. A fixed sbf is used to prevent bl version from incrementing by removing the higher version files
Sent from my MB526 using Tapatalk 4
I did it! The SBFs that did the trick are the ones in the OP in the thread Motorola defy bl7 sbf all in one. First the Asian Retail BL7, then wipe from stock recovery, then the MIUI SBF (which also contains CWM custom recovery). Then it booted right up.
I'll be back with more info about this Defy just returned to the land of the living after I poke around a bit (the MIUI ROM is in Chinese, gotta figure out how/if I can switch to English...)
So! Once again it's been proven that it's nearly impossible to softbrick a Defy. Given enough obstinacy ^_^ you can find a SBF that will put it right again.
PS: I should probably also add to the wiki page various stuff I've learned while doing this. I've had a hard time looking up some info, maybe it will help others.
Aaaand I spoke too soon. It booted MIUI successfuly exactly once (1 time). Now after the Moto logo dissapears I get a blank screen (but lit, not off) and nothing happens. I also tried a CyanogenMod ROM (Quarkx), both 10.0 and 10.2 – the CM spinning logo appears, it goes on for a while, sometimes it attempts to boot (got to the Dalvik generation, for example) but then it reboots, other times it will keep spinning and nothing happens.
On the bright side, I now have access to the advanced bootloader and custom recovery with all the goodies (ADB shell etc.) which opens up possibilities. If anybody has any ideas what I could try to diagnose this, please speak up – like I said, I can now have access to the actual Linux system on the phone.
The only idea that pops to mind right now is the CPU settings. Maybe it got overclocked by the original owner and something got fried? Resetting them to defaults didn't seem to do anything.
Still no luck. The MIUI I linked above is the only one that boots up, but won't recognize the SIM card and claims there's no GSM connectivity.
I'm speculating that perhaps something is messed up with the radio hardware, and that MIUI is the only ROM that somehow works around that and boots up, but the other ROMs don't expect it and reboot halfway through the bootup sequence.
I'll see if there's any logs made during bootup.
The reboots are characteristic of bad eMMC(data not getting wiped properly). Does miui work fine apart from radio? Also 2ndboot builds require a specific stock kernel(from eu dfp 231) so try that as well. Try full wipes from cwm, and make sure the data partition is formatted correctly from boot menu(ext3 for ics and below, ext4 for jb+).
The miui sbf masked the data problem(atleast temporarily) allowing the phone to boot up. Unfortunately if you do have other /data issues(which are seemingly unrelated), they all point at bad eMMC, necessitating replacement of the motherboard as the only viable option.
Sent from my MB526 using Tapatalk 4
@thekguy: Yes, apart from the GSM MIUI seems to be working fine, including WiFi. But only one time, if I reboot it doesn't start up again. Sometimes I get a hanged boot logo, sometimes I get endless bootloops. Other ROMs never work, it's straight to hanged or bootloop.
Are you saying that the internal memory has gone bad, like an HDD getting bad blocks? If that's the case, I can probably use a recovery update script to repartition the memory and work around the bad zone(s). As long as I can figure out which exactly are the bad zones (other than trial and error).
Or are you saying it's simply not getting scrubbed properly and it's a problem with the filesystem? In which case I can reformat at least some of them (/system, /data/ and /cache).
But doesn't the flash tool overwrite the partitions by raw-dumping images on them? So how can a bad filesystem survive SBF flashing?
And what about update zips? Do they reformat/raw-dump partitions – or do they just take the filesystem for granted and copy to it?
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.
I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.
A log obtained via adb should be able to verify the same
Sent from my MB526 using Tapatalk
thekguy said:
The image files within the sbf govern raw dumping of partitions. Flashing zip files does not involve wiping partitions in normal scenarios; it can be done thru the update script. As you yourself state correctly, flashing an sbf rules out filesystem errors; provided a data wipe from the stock recovery is carried out for confirmation.
I suspect bad eMMC blocks to be the root cause of your problem; however our partition table is signature verified at boot, and cannot be tampered with. It is possible to emulate a partition table via our custom kernel, but this zone of development has not been entered so far.
A log obtained via adb should be able to verify the same
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
If the bad eMMC blocks are entirely within the ext3/4 partitions, we should be able to run badblocks on them (taking care not to overwrite the signature at the end of /dev/block/mmcblk1p21 but past the actual file system) and avoid them. As the badblock list is stored in the file system rather than the partition table, I believe that would work.
I've also been experimenting with using an SD card partition for /system and keeping only a few minimal files on the eMMC (I think we could get away with busybox and a modified logwrapper script)—no unexpected problems. It's quite likely those two files won't interfere with the bad blocks, and after they've booted the kernel we wouldn't be touching the eMMC at all (assuming /data and /cache are also SD partitions, but that should be doable). I have been using Quarx's CM11, and I don't think my trick works with stock ROMs (at least I've never had success booting a stock kernel with 2nd-boot), so it might not be a helpful suggestion.
2nd system/ multiboot is a good idea to get past the bad blocks (probably some performance hit though) but better than a non functional phone. 2nd system should work even with a stock ROM as secondary system, not sure why it isn't working for you. I have no idea about the badblock remapping logic
Sent from my MB526 using Tapatalk
Related
Hi All,
I am new here and this is my first post. But i have been reading this forum for quite sometime and know that u guys are now my final stone. I am a proud owner of a Motorola Defy. And I am having this strange behavior, which is effectively rendered the phone almost useless. The phone is acting like its got a restore point in itself, and every time i restart.. it gets back to that point in time.
This includes app installs, uninstalls, stuff placed in system through adb push, theme, everything in the OS. I tried installing a different ROm through clockworkmod, but its not taking effect. Its saying install success but as soon as it restarts, its going back to the old ROM. (takes time to load, so i guess it reinstall back/restored the old version)
Details of device : I am from India and the phone was manufactured in India in around April/May 2011. Its a red lens Defy and and came with Eclair. I updated it officially to the first Froyo release for SEA region. After that i rooted the phone with superone click, and installed WIUI rom. I have been updating the ROM with newer versions around each month. The last one was 1.11.18 though as i waiting for a good ICS version to flash.
The problem occurred after i started installing some gold apps from getJar. It restated in between and install... and that point is kind of acting like a restore point even now.
Things I did: Tried installing different rom by CWM method. Reinstalling second init and CM, both old and new version. Tried restoring nandroid backup of my official ROM. Tried fixed and full sbf flash through rsdlite 4.9.5.2 and now 5.6. First 3 things reset as soon as i restart. For RSDLite, it gives checksum error for each and every ROM i tried. I tried all SEA releases, JORDN_U3_97.21.51, Defy Plus Rom 2.3.6, 2.21 first eclair rom, everything gives the same error. From the RSDLite logs, i could see that there is something wrong as.. say the last successful CG was 33, and the error came for 34, the log says its expecting the checksum on the sbf to be equal to that of CG 33. Its taking the last successful checksum validation and expecting that for all the CGs henceforth. its not showing what the device actually has.
I atlast could somehow, but trial and error, removed all the CGs which were throwing error, and recompiled the sbf to make it pass the RSDLite flash. The CGs present in the ROM (JRDNEM_U3_3.4.3-36-1.7) were 32, 34, 42, 53, 61, 64, 65. And as soon as it booted, it restored back to the checkpoint. Even after i formatted by card and put it in, the app shortcuts remained on the home screen, but as the apps on the card were gone, they are just junk and doesnt open anything.
Thanks in advance. Please let me know what you need from me to help me resolve this issue.
Any help... Anyone?
Can someone please suggest something?
This is what i got from some people. I am not sure how far this is possible, but somehow the theme i installed just before this all happened, from MIUI market.. somehow managed to change something inside phone's kernel, past the locked bootloader? I am totally a noob in this and just a wild imagination?
Or may be some sort of cache wipe is happening everytime the phone boots up, So even when i install the ROM, when it boots up, it gets back the old ROM.. like what would probably happen if i do a factory reset soon after i instal a rom before the restart..?
I would really appreciate it if anyone could help me out with this...
Checksum errors were for me also.
I tried my office computer for flashing and instantly flash was done. The checksum error occurred 7 times on my good computer before that.
Reflashing froyo must take care of all errors happening
Thanks Kapil fr the response. Are you from india? Which sbf did u flash? And waht all did u install in the office pc? I have a pc of my friend where i can try to reflash if you tell me the exact steps that u took in the fresh pc.
Also, can anybody tell me how to use adb commands in CWM mode? Its recognizing my phone in normal mode but as soon as it boots in Moto recovery of CWM, its not recognizing anymore. Want to use adb format commands from recovery.
Hi I was able to use adb in CWM, but format commands were not working. How can i format the system partition? please help me with this.
Is there anyone here who know how to restore a nandroid backup manually using adb commands for MB525???!!!!!
Sounds weird and impossible. Try this. Wipe everything though cwm and flash new rom. Try ms2ginger.
Thanks darshanonline for the suggestion. I tried to wipe everything.. factory reset+cache+dalvik cache wipe. And then tried to install cyanogenmod 7.1 as well as 3 different wiui builds. Everytime it shows that the install was successful, ut as soon as i restart, it would go back to the old ROM.
Is there any checkpoint system in android, seeing the init.rc, i can see comments on something about saving a checkpoint. Is there any particular condition under which this checkpoint may be getting used on very restart?
Also.. is there any way for RSDLite to skip the chksum validations and get the install anyways?.. Some sort of a hack into it?
Ok.. Found something else thats happening. I dont need to shutdown for the system to revert back. Say i install a few things new after a reboot.. After some time.. 1 day at max, i am not able to open them, and neither am i able to open manage applications or market. Everything force closes. I have Ti Backup installed, and i opened it, and i didnt find the new apps to back up. I connected the device and checked through adb, and they were not present in the app folder. They just vanished... So basically after a certain point of tiime, the new stuff just gets deleted on its own.
Guys i know i may sound dumb and stupid with my questions, but i really couldnt find any solution on the net for this. Please tell me waht i should do, and i'll do it. But tell me something. Dont ignore please!
and you did wipe data from within stock recovery (vol down+power etc.), i presume..
Sent from my MB526 using Tapatalk
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Soumik84 said:
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Click to expand...
Click to collapse
DL WIUI 1.12.16 ICS > copy to SD card > Boot in CWM > select zip to install > Install WIUI 1.12.16
Hopefully your problem should be solved.
I found 1.12.16 ICS with lesser FC than the 2.21
labsin said:
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Click to expand...
Click to collapse
Thanks for the link. Now i know that i am not the only one having this issue. But even there its not resolved yet.
@ headers.chennai - Thanks. I will try that ROM, along with Pikachu ROM with Aroma installer, might be a different installer can try fix it?!
BTW.. does anyone have the TI OMAP board utility? Any chance that it can be available outsite here?
I tried the arora installer and it supposedly formatted the system partition and remade it.. but as soon as it finishes and i restart.. I get back the same ROM.
Is it some way that the files are not getting deleted, like some hardware lock or fault?
Soumik84 said:
I tried the arora installer and it supposedly formatted the system partition and remade it...
Click to expand...
Click to collapse
Hi, bro! What is "arora"? I should try it asap, and all other chance.
My trouble here, same as your.
Hey man.. looks like we are having same problem...
Sorry abt the typo... its Aroma Installer. Its with the Pikachu ROM in this link :
http://forum.xda-developers.com/showthread.php?t=1498843
Its a new installer that launches from cwm when u try and install this ROM. u got some options to select and on selecting the complete install option,, the log shows that it formats the system partition and then creates it. I saved the log file, but for some reason the file shows up blank now. Might be problem with the launcher.. or my phone.. dont know.
Soumik84 said:
Its a new installer that launches from cwm...
Click to expand...
Click to collapse
Not for me, my checkpoint without cwm
I recently switched to my wife's Atrix. It was never rooted or unlocked, and was upgraded to 141. As with all android devices I touch, I just had to root/ unlock it and flash something.
I used 'automatic unlock 4.2' and everything seemed to go fine. Phone booted normally and I ensured I had root. I then decided to flash ICS. ICS will not boot (stuck at 'M' logo). Tried to restore my backup and it gets stuck at the 'rethink possible' screen. Also tried the obvious fixes such as clearing cache and formatting data.
Any suggestions?
Did you flash pudding and unlock the bootloadrr?
Sent from my MB860 using XDA App
Well, it is unlocked. There is a 'pudding.sbf' in the script as well. I am just getting started with the atrix. I come from the samsung and htc world. Last moto phone I had was the cliq.
Is there a zip that I can pull system images from and just fastboot flash myself? Is that the proper procedure to recover from this kind of situation on this phone?
Oh, and it may be nothing.... when I try to flash ics in cwm, it seems to be done way too quick? No errors or anything... so it could just be I'm comparing apples to oranges (previous phones).
Flashing a new ROM only takes about 10 seconds through CWM. You shouldn't get any errors. After flashing any ICS based ROM you should see a random offset last.
Doesn't matter anymore.... looks like I bricked it.
Failed to boot 1.... and noe can't get into fast boot
Trying a second RSd lite flash but I'm not hopeful
I wasn't getting offset message btw for ics roms (can't believe I didn't notice that)
Sent from my SGH-T959 using XDA App
Finished 2nd rsd lite flash... no dice.... then pudding.... boots
Going to take a break and play with it later to see what I can see
Well, I loved this kernel! But I appear to have bricked when flashing another (also aparrently kernel fixed) rom.
I *could* get to CWM, but I can't touch system. The phone freezes if I try to do anything.
Odin will not flash.
I'm an experienced user, I've owned several Android phones in the past and understand how everything works, however, this time, it really appears I am dead.
I can take the phone back so no big deal, but I just wanted to let people know. If I am unable to get this working, it appears the new kernels still have some risk involved.
I was on UK Stock ICS (Not sure what the version was now), flashed Francos using DD, everything was fine but Wifi did not work, so I wanted to try Speedmod. This caused a bootloop. So I reverted, and the bootloop remained. At this point I downloaded a Lite rom that used Franco V4, (sorry, the name has escaped me) this flashed but also gave a bootloop. So I wiped, and re-applied.
When I reinstalled after wiping, the install bar glitched and flew past it's usual 100% right off the side of the screen. Then it froze.
After this I am unable to flash *anything* to the phone. CWM boots but I can't do anything within it. Odin attempts to flash but I see the phone send invalid responses back (non-alphabetical characters) and Odin then fails.
Anything else I could do? I think I've tried everything possible at this point. Gutted!
[edit]
UPDATE: This does currently appear to be a case of bad luck, and NOT The eMMC Bug. The eMMC Bug fix is now under critical testing by myself (as I have access to replacement phones within minutes), though I have flashed 18 times at present with no superbricks or broken eMMCs. So far so good!
I think u wiped from ICS kernel and this may have caused u a brick. At first when you flashed speedmod and had bootloop you could have flashed back to Abyss kernel wiped and reinstalled the whole rom instead of wiping from ICS kernel and installing rom. Its a known fact that while installing or restoring roms from ICS kernels people have faced lot of issues..
I'm aware of that issue. I used Franco's R5 kernel (which is ICS and superbug fixed. The fix was not a guaranteed fix, and sadly I appear to have proven this fix to be non-working at the moment.)
I guess I'll be popping back to the shop at lunchtime!
Cheers.
One last try just pull the battery for 30 seconds and try to get into download mode and try to flash stock GB with 16gb pit file and gb bootloaders
---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------
When i had Galaxy s same thing happened to me only download mode no cwm nothing and Odin was failing to flash stock roms even with a pit file and what i did was flash with bootloaders along with pit file and rom files and voila my phone was back to bussiness
You might be right about the PIT files. It would make sense, Odin almost completes when the phone throws out the invalid text- might be trying to put data out of the partition.
I'll give it a go, thanks. I do still have Download mode. I no longer can access recovery though.
so you cant flash on ODIN?? stuck on factoryimg??
Well, that didn't go to plan. Crashed again, and now I have no download mode, instead the phone appears to be insisting that the battery is not installed. How odd!
musashiro said:
so you cant flash on ODIN?? stuck on factoryimg??
Click to expand...
Click to collapse
This was the case, yes.
Oh, I just got Download mode back, Stupid thing. What odd behavior.
I can get the phone replaced within minutes if required (I'm 5 mins away from the shop) but I'd rather try to keep my internal storage intact
Here's the guide to fix it. I along with many others managed to fix our phones using this guide: http://www.android.gs/easily-fix-bricked-samsung-galaxy-note-n7000/
Thanks for that. I'd just found it before you posted and am reading through it now.
I am half tempted to try it, but I think if there are now "bad blocks" in internal memory, I will just get it swapped for a fresh device.
It's behaving weird, sporadically thinking the battery was removed etc. so I am not 100% sure this is a superbrick /mmc problem, and it could be some other issue that cropped up. Let's hope so (because I'd really like to think Superbrick is fixed as we had suspected!)
Thanks for your input. I'm off down the shops!
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
damiensturdy said:
Eyup! New phone in hand.
So I have 13 days in which to take advantage of this quick-swap. What I'm going to do now is begin heavy flashing with the R5 "fixed" kernel. If I succeed in breaking it, we know the fix isn't working. If I fail at breaking it, we're all good. Sound like a plan?
Click to expand...
Click to collapse
Yes seems like a good plan to me, looking forward to get results from you soon.
Thanks
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Glad to have someone willing to risk their devices in these dark times. Well appreciated!
Sent from my GT-N7000 using Xparent ICS Tapatalk 2
In order to run the test, you need to actually boot up the device, go through the settings, and install a few apps. Then go to recovery, and perform a wipe.
Simply hitting the Wipe key in succession (like 100 times) does not work. There must be something to format in the respective partitions.
Thank you for doing what you're doing. But if you could, and only if you have the time, could you try wiping from CWM (just wiping, not nandroid restore), for say 20 ~ 30 times? It's very tedious to do it due to the setting up and needing to wait for it to boot and install a few apps from the market.
I'm sure with 20 ~ 30 or more wipes on a single device, we can safely say that the fix is a likely permanent fix.
damiensturdy said:
Right, OK, I managed to duplicate the crash, but instead of using ODIN which failed the first time round and caused very, very weird behavior, I installed THOR'S CWM. This was able to unmount, format, etc the system partition. This means that despite the other errors, there was no EMMC damage
(I'm aware the damage is not always the same, but I was able to consistently cause the crash with no damage.)
After installing Thor, I was able to reinstall other roms
IMPORTANT!!!
When I tried to install Thor's CWM, It froze - I gave up hope here, but after forcing a reboot the phone had Thor's CWM anyway, so it'd written the important parts over before crashing
Hope this helps. If you find yourself with a recovery unable to flash roms, try flashing Thor's CWM, it may freeze, but give it a minute then pull the battery and re-enter recovery. Fingers crossed
Click to expand...
Click to collapse
So, in short, you had /system corrupted at the filesystem level, not the eMMC level. This seems to be a common problem on the Note, and some people falsely describe it as "partial root". CM9's initramfs has had changes made to make it easier to fix these problems by not automatically mounting /system on entry into recovery.
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Good input guys. Thanks.
Yes, indeed this didn't appear to be the eMMC Bug. I can't guarantee what it was on the old phone (which did appear bricked.), I just know I started off the same. It's more likely that I knackered it with failed Odin flashes than the eMMC bug at this time.
I'm still flashing, installing, wiping, etc. I'm basically trying everything that we're not supposed to do. So far the worst I've got is a corrupt system partition (indeed, that is not an eMMC bug) but the only CWM able to fix that was Thors.
Basically if I knacker the phone I can get it replaced within minutes, so I might as well take advantage so that we can all relax knowing it's fixed (or continue to look for a fix if it isn't)
Obviously I shouldn't take the piss. If somehow I brick it a couple more times I'll be forced to stop. But I like to help so let's go! :-D
What does "flashed Franco from DD" mean? After that process did you ever verify that you where actually on Franco?
Perhaps the kernel flash didn't take and your subsequent wipes/flashes where from stock ICS kernel.
Sent from my GT-N7000 using xda premium
Entropy512 said:
The problem was: If /system was corrupted due to plain-jane filesystem corruption, it would be mounted read-only if mounted at any time. Also, it seems that CWM would be unable to unmount it, preventing CWM from reformatting it.
Solution (which I haven't fully tested as I haven't had this issue in a few weeks, but I have encountered it before) is not to mount /system automatically on boot when entering recovery.
I pointed Franco to the fix for this but I'm not sure if he's included it yet.
Note that this is NOT the eMMC brick bug, it's completely different and is recoverable.
Alternate recovery method:
In CWM, connect via ADB, and in an ADB shell:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9 bs=1M count=1
Clobbers the first 1M of system so CWM will completely fail to mount it instead of treating it as corrupt. At this point it can be formatted in CWM's Mounts and Storage menu.
Click to expand...
Click to collapse
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
damiensturdy said:
VERY Useful information. Just got myself back into this situation and this did fix it without Thors CWM, although I recommend everyone have a copy of Thor's CWM on their card just in case!
Actually I notice that Thor does NOT Mount System by default, this seems to match your information.
Nice one, Thanks!
Click to expand...
Click to collapse
That's because he kangs from CM and then releases warez based on our work.
Linux kernel without source code published = warez.
- So I was updating to Quarx's 5th Nov build (2ndboot) and in the middle the flash my phone turned off and decided not to start up. (The battery WAS NOT drained)
- I started with this guide in order to get it back to life:
http://forum.xda-developers.com/showthread.php?t=1807899(I used the exact same files, even the sbf. I live in India and I couldn't find India's sbf in this list: http://sbf.droid-developers.org/umts_jordan/list.php)
- Everything went as excepted and I was back on 2.2.2, so I tried to flash Quarx's build again. (I installed gapps, and cleared everything twice, thrice). However, the phone stuck on a bootloop:
red Motorola logo -> blue led -> greend led -> blank screen -> repeat.I cleared the cache's, factory reset, etc etc. No use.
- So i followed the original method again to get back to 2.2.2 and then flashed ICS from Cyano's website. It worked! So I tried again to flash a CM10 release, but this time a PRE-2ndboot build - 24th Sep.
It didn't work either. So JellyBean is the evident problem, but it doesn't make any sense, right?
- I started agin and tried to flash a different sbf, I got to this thread:http://forum.xda-developers.com/showthread.php?t=1093352 and tried the sbf provided (they claim it to be the one for SEA, including India). However, even after doing a factory reset from the stock recovery and flashing this sbf, I got a brick. The phone won't start whatsoever. No bootloader, no recovery - zilch. Dead.
- I again went back to my original method and got back to ICS...Flashed JB -> Same bootloop as before.
- Somethings I have noticed:
1. On flashing, the internal memory shrinks to only 128MB. I tried a factory reset from within the phone, from custom recovery and from the stock recovery. The memory was still 128MB with about 40MB free.
2. When I return to stock, the phone is somehow pre-rooted. On running superOneClick it shows that it;s already rooted but I continue nonetheless.
3. I think MAYBE the low internal storage might be at fault since JB Gappa require a lot of space.. I have tried it with minimal gapps too.
4. I have flashed every sbf available for Asian countries...but the only one that works is the one from the first link provided.
5. The only thing I can do right now is get to 2.2.2 or ICS...So if someone can help me out, that's my current status.
PS - I have been at it for 3 straight days, so yea, I have tried just about everything and read every thread regarding this. I even had to jump start by battery once as it ran out in the middle of a sbf flash.
There s a chance you didn't installed JB the right way. Also you ca install it without Gaaps. Does 2nd boot got enabled in Bootmenu? Did you flashed the kernel accordingly?
if you have bl4 try one of my fixed sbf with 2ndboot
ex. 28.11JB.Quarx+jellyX.kernel
than make a data and cache format fom bootmenu
bootmenu/ CPU settings/ system tools/ format data and cache to ext3
reboot
hve the link in my signature
I think you need bl. 4 from an 2.3.4 sbf for defy
In my country there was as an official update to GB
Users posted prblems with bootloader 3 and 7 @ quarx cm10 2ndboot roms
MB525 red lense
Hi,
You can take one more try (if you wanna ) to flash 12.09 JB build - it shall work
If so then flash Nordic retail 2.2.2 or WE retail (U3_3.4.2-177 or 179 from here)and try again 2ndboot builds (for some sbfs the last pre 2ndboot, 24/09 was the first not working)
Flash then 5/12 and jb gapps, wipe dalvik cache and cache after flashing.
Concerning 128 MB free memory - I suppose you are talking about data partition, not a system. Of course it is too small - the same as prerooted phone - try another sbf
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
vinu.shukl said:
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
Click to expand...
Click to collapse
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Click to expand...
Click to collapse
These are the sbf's I found pertaining tp your specifications:
http://i.imgur.com/muQdT.jpg
EDIT: But they are all in the DEFY-PLUS repository...can I flash them?
So I can use anyone of them?
Also, I don't know much about BL versions...So should I just download one of the above sbf's and flash it using RSD? Do I need a nandroid backup to go with it too?
The procedure I would follow would be:
1. Factory reset, clear cache's
2. Go into bootloader menu
3. Flash above sbf using RSD
4. Reboot ??
Should that suffice?
First: if you are red lense it is ok to flash BL6
If you are green lense, to have your camera working, you will need 2ndboot builds (CM9, 10 or 7)
You will probably need red lens battery fix to show correct percentage, no matter you have green or red lense then.
You can flash it even later, after flashing CM10 and gapps and checking how it works
I would choose Nordic retail
Sometimes you can have problems with rooting with SuperOneClick (version 2.3) - force close Motorola Portal before rooting and it shall work ok then
And nandroid backup is not very useful when changing BL version, at least you will not be able to restore all
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
vinu.shukl said:
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
Click to expand...
Click to collapse
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
corrinti said:
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
Click to expand...
Click to collapse
Okay!
Gonna flash it tonight...Finger's crossed. =D
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
vinu.shukl said:
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
Click to expand...
Click to collapse
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
corrinti said:
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
Click to expand...
Click to collapse
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
vinu.shukl said:
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
Click to expand...
Click to collapse
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
corrinti said:
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
Click to expand...
Click to collapse
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
vinu.shukl said:
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
Click to expand...
Click to collapse
The ramdisk zip is to be installed in a standard way, like any other zip, probably doesn't require wiping caches, but probably
I usually use zRam (18%) - I didn't notice any bigger battery drain.
KSM off
WiFi - change to never when screen is off - you can have wifi on all the time without special battery drain
And choose proper baseband for you region
And CPU settings are ok as above
Defy on BL6
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
Click to expand...
Click to collapse
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
@Vycas
The problems might be several, unfortunately even hd problem, but try this:
- try different USB cable, different computer, different USB socket - the problem can arise when signal transmission is poor. Sometimes reinstalling of motorola drivers also helps
- if above does not help try Linux computer instead of Windows one
Regarding sbf - well, as you received error after each sbf flashing there could be a hope that you still may have BL4 (but also you may have BL6) - start your above mentioned trials with BL4 sbf, which will give you camera also with CM7
Hi all
So, I have a problem with my Defy (MB525 green lens). The best will be, if I'll write my full story. Here is it:
Story
I had Defy with CM 10. It had bloated battery. I wasn't using it for 6 months because I have another phone.
Some time ago, I decided, that I'll give Defy to my grandfather. On Tuesday this week I bought new original battery. I put it in the Defy, and charge it. I could boot up my old system as I wrote, CM 10. While it was charging, I detected that I haven't got SD Card. On the other hand, I found some 4GB Samsung SD, which had my father in his Desire. The SD Card had 3 partitions, which I tried to delete, and make only one, with GParted. After I did it, Linux and Windows can't see it. (This is almost other problem, which I'm trying to solve here http://crunchbang.org/forums/viewtopic.php?pid=350683)
But, when I put the CD Card to Defy, in TWRP recovery I could see some strange symbols. I thought, that I can repair something when I wipe SD Card. When the battery charged, I decided to do factory reset and wipe SD card. Here is my first failure. In TWRP I went to custom wipe, and here I marked everything including system and I wiped it. Then I remembered that system is recovery too. TWRP wrote, that everything except SD-Ext and SD was wiped. I known that this will be a problem. Yes, after reboot only Motorola logo without recovery.
I think, there was only one option - flash SBF, which I did. I went to stock bootloader and with sbf flash in Linux, I flashed this:
JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf
And than this:
CM7RC1.5_16_09_11_custom.sbf
After reboot, I got bootloop. I tried to replace battery, do factory reset but nothing helped. That time I haven't got working card, so I couldn't flash some zip via CWM recovery. Thus, I again flash another SBF, but I don't really remember which. Probably some official CEE Froyo however, I'm not sure.
After that and reboot, I got only black screen with white led lighting while USB was connected. When I wanted to go to stock bootloader, still black screen, but I can flash SBF, and while flashing, screen have brightness and text about flashing.
I knew that this is little hard brick. I again tried to flash other SBF which I have or I downloaded (yes, again I don't know which). One of SBFs which I flashed was some fixed Chinese SBF . That made my defy booting, screen working, but still bootlooping. I couldn't reach any recovery.
Again, I flashed other SBFs, CM's too but nothing worked and I got black screen again.
And this was end of my story.
Current situation
I have Defy (MB525 green lens), with unknown framework an it had only black screen and what only I can do, is break Defy with hammer or flash some SBF.
So, here is list of all SBF files, that I have downloaded and probably tried to flash: (No order)
JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf
CM7RC1.5_16_09_11_custom.sbf
JRDNEM_U3_2.51.1_BLUR_P3_SIGN_SIGNED_UCAJRDNEMARAB1B80AA030.0R_USAJORDANO2DE_P048_A015_HWp3_Service1FF.sbf
JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf
DFPRC_U_4.5.3-109_DPP-6-7_SIGNED_USADEFYPRCB1B50AA00A.0R_JRDNGIBRRTGC_P025_A019_HWp3a_Service1FF.sbf
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
JORDN_U3_97.21.51.sbf
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FF.sbf
4.5.1-134-DFP-132-gingerbread-BL6-fixed.sbf
4.5.2-109-DHT-22-gingerbread-BL5-fixed.sbf
3.4.2-177-003-nordic-froyo-fixed.sbf
3.4.2-179-002-tmobile-froyo-fixed.sbf
4.5.1-134-DFP-74-gingerbread-BL5-fixed.sbf
4.5.3-109-DPP-11-gingerbread-BL5-fixed.sbf
JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN.sbf
Probably that is all what I have.
I've read many topics with similar problem and guides, but nothing helped me, or SBFs were unavailable.
So, what have I to flash, or which guide to try, if I want working Defy?
Sorry for my not good English
Thanks
UPDATE
sterver1 said:
Wohooo!!
Story
After a long time (4 months)...
Accidentally today I found my favorite custom ROM - MoKee OS, for Defy. I said to myself: "Hm, I have some time... I'll try to flash this MoKee on my Defy and maybe it solve my problem with (not) charging/unknown battery for system."
I picked out box with Defy from drawer, wiped the dust, took the Defy and said: "Sh*t! I haven't got SD Card!" Fortunately I found one. I download MoKee OS zip on that SD Card, put it to Defy, booted to recovery and flash MoKee OS zip. (...with full wipe of course...) Then rebooted to system.
Uselessly. Still unknown battery. "Hmm, It doesn't matter. Maybe here are some new stuffs which can solve my problem." And I continued to finding something, that can solve my problem. After a while I found ROMs with new 3.0 Kernel by Quarx. HERE. I downloaded CM 11 EXPERIMENTAL with this kernel and update recovery and flashed them. I didn't read thread. After reboot system didn't boot up and TWRP was inaccessible. I found why when I read some posts from that thread. HERE. But I couldn't flash that zip via recovery because I couldn't open recovery. So I mount /system to USB from bootloader and added files from zip manually to /system partition. After reboot it jammed on booting up. But TWRP was accessible so I did full wipe and flashed CM 11 EXPERIMENTAL and than that fix zip by @lorcotti. After that it finally booted up and battery was working and charging!
And they all lived happily ever after. :laugh:
SO, If you have some problem as me (unknown battery after flashing GB SBF on MB525), try this:
1. Download recovery and some ROM from [Kernel][GPL] Development 3.0 Kernel and fix from this post.
2. Put all zips on your SD Card.
3. Boot up to recovery.
4. Flash update-recovery.zip.
5. Reboot to recovery.
6. Do full wipe.
7. Flash ROM with 3.0 Kernel.
8. Flash Fix.
9. Wipe cache and dalvik cache.
10. Reboot to system.
If you want, you can flash GAPPS via recovery too.
But this will not be for daily usage! 3.0 Kernel by Quarx have a lot of bugs!
Thanks all!
Click to expand...
Click to collapse
Yeah!
Today I again tried to flash chines SBF. This one: JDGC_U6_2.13.0 China Unicom Thread/Download !!!BL6 kernel !!!
JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF.sbf
...and now I have bootable phone . I read many topics again and I got to know how to aces stock recovery. So I made wipe on this chines ROM and I can boot without loop, but I can only do emergency call with SIM it is the same. So, now, I don't know, what have I to do/flash, how to root it and flash here custom rom. Can I use SuperOneClick if it probably haven't got turned on USD Debugging?
Back on black
So, I made sbf file with depacker...
CMG39 from JRDNEM_U3_3.4.2_155-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P011_A010_HWp3_Service1FF
and all others from JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF except CMG31.
Than the bootscreen changed from chines logo to grey motorola logo and I got Bootloader (9.00) Error A5,70,39,00,27. After that I flashed another sbf and I got Error A5,70,00,00,23. Than I flashed DEFYPLUS_U3_4.5.1-134_DFP-231_CEE_ROOTED_No_Signed.sbf and now I again have only black screen. F*ck!
I tried to flash my made sbf and chines one (JDGC_U6_2.13.0_SIGNED_USAJRDNPRCB1B50AA039.0R_JORDANAPCNCU_P017_A042_M006_HWp3_Service1FF) too but nothing...
Really here is nobody who can help please??? I want give Defy as Christmas gift. :crying:
OK, so repetition.
What mistakes I've made
1. I wipe wipe all including system partition in TWRP without any flashable zip on SD card.
2. I continued with flashing original SBF, while I have usable CWM.
3. I flashed many no downgradable GB SBFs.
4. I flashed Defy Plus SBF on Defy.
I hope that there is still hope.
Somehow to downgrade, flash only CWM where I can flash nandroid backup or I don't know what else...
a gingerbread sbf should also work on green lens defy as there is no diff. in hw... instead the cam
have you tried a factory reset in stock recovery after sbf flash ?
Sent from my MB526 using xda app-developers app
Now, after all (which I tried) SBFs I get only black screen. I tried many GB SBFs too, but still black screen...
I'm going to try some another Poland SBFs and than if that won't work, I'll try to flash all in Froyo CEE SBF particularly.
Thanks for your response.
Once you've flashed GB stock sbf you can't go back staight to froyo or else
Read the beginners guide and the SBF matrix sektion carefully.. if you haven't...
Sent from my MB526 using xda app-developers app
DFP 231 has been flashed by you, so no froyo sbf will work. Black screen on dfp 231 indicates some eMMC problem, because bl version is highest(no error possible). IMHO only service centre can disable bl check or replace the main board to fix the problem
The problem should have been solved at the boot loop issue by wiping from stock recovery, no network solved by baseband/radio fixes. Check the rsdlite log file to confirm checksum/access errors. I think that the custom sbf somehow messed up either eMMC or efuse(less likely, unheard of).
For sdcard error wipe everything using hdd llf. If any error persists it's a hardware issue
Sent from my MB526 using Tapatalk 4
@bone101
I know, I read it few times, and I know how it is (not) working. But, after all GB SBFs I got only black screen, so maybe were not correctly flashed... I'm using Linux and here is sbf_flash for flashing SBFs, and in it I can't view informations about phone as in RSD Lite... But maybe, it will work in wine..
Do you now, that if I flashed GB SBF, I have to flash another GB to solve my problem, because no Froyo will work?
@thekguy
I know how I can solve others problems. Only what I need help to solve is black screen.
Can't I flash something which support that high BL or it won't work?
check if you get into Bl. modus
press vol. up & then power button
tell what you see
Sent from my MB526 using xda app-developers app
That's what I'm saying, the black screen problem occurs due to bl version mostly, and you have highest bl, so in theory black screen is impossible. Unfortunately I have never seen in this forum any defy recovering from black screen after flashing dfp231. Check rsd log from windows if possible. Froyo sbf cannot work under any circumstance. You must flash only gb sbf
Sent from my MB526 using Tapatalk 4
@bone101
When I acess bootloader I have only black screen... While flashing I can see
"SW Update
In progress.."
Ok, I have Windows notebook available... Here are device properites from RSD Lite:
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 173002052f066b010000dcff0200
BP Die ID: 0000000000000000000000000000
AP Public ID: d0d8842b4879dd27b9eb94f970fbeec252fcb2f4
BP Public ID: 0000000000000000000000000000000000000000
Click to expand...
Click to collapse
I'm going to try some GB SBFs here...
WOHOOO I've got it! I flashed 231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf and now I have got bootable phone... I'm in the system. I'm going to root it and flash CWM and MIUI if it will work.
Really thanks for your help!
sterver1 said:
@bone101
When I acess bootloader I have only black screen... While flashing I can see
"SW Update
In progress.."
Ok, I have Windows notebook available... Here are device properites from RSD Lite:
I'm going to try some GB SBFs here...
WOHOOO I've got it! I flashed 231_GR_SIGN_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTCEE_P022_A022_Service1FF.sbf and now I have got bootable phone... I'm in the system. I'm going to root it and flash CWM and MIUI if it will work.
Really thanks for your help!
Click to expand...
Click to collapse
I'm stuck in same problem, downloading this sbf you mention before, hope it works. Fu^kin defy, it sucks
@Alejandrissimo
Good luck...
I have another problem. Now, I have GB kernel. In original 2.3.6 GB on MB525 green camera don't work, and battery too. So, I thought that, when I flash Froyo kernel (CM) and CM7 I got back Froyo kernel and working camera and battery. Yes, this was not possible. After I did it and rebooted it I got Bootloader error. I flashed DFP-231 again. Worked.
Than I tried restore Froyo from nandroid which I found something here on forum. Than I flashed CM7 and bootloader error again.
Now I have CM7 by Maniac for defy plus which worked well except camera and battery... I know that here are many topics about downgrading, camera fixing and others but all which I read are bad in something for me...
Here are some options what I found but I don't know if I can use one:
Method 2: (BIG thanks to Jebrew again for this one)
NOTE: You are going to need CM7 for this one. CM7 Stable version recommended.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=1216982
DOWNGRADE
If you come from Android 2.1 and never flashed Android 2.2 you can use the fixed sbf-files method. With this method you will have a option to downgrade to you personal stock Android 2.1 via direct sbf flash.
Click to expand...
Click to collapse
from http://forum.xda-developers.com/showthread.php?t=966537 but I'v ever flashed Android 2.2.
Or http://forum.xda-developers.com/showthread.php?t=1465436 ... This is better option but I have flashed full 2.3.6 SBF and here is:
It will only work if you never flashed a Android 2.3.6 full sbf.
Click to expand...
Click to collapse
So, how can I downgrade or repair battery and camera? I don't care whether I have got GB or Froyo kernel if I have working camera and battery.
have you tried cm11 ?
or ms2ginger by walter79
Sent from my MB526 using xda app-developers app
sterver1 said:
@Alejandrissimo
Good luck...
Click to expand...
Click to collapse
Working and rooted, thanks for your help
Alejandrissimo said:
Working and rooted, thanks for your help
Click to expand...
Click to collapse
please see your PN
sterver1 said:
@Alejandrissimo
Good luck...
I have another problem. Now, I have GB kernel. In original 2.3.6 GB on MB525 green camera don't work, and battery too. So, I thought that, when I flash Froyo kernel (CM) and CM7 I got back Froyo kernel and working camera and battery. Yes, this was not possible. After I did it and rebooted it I got Bootloader error. I flashed DFP-231 again. Worked.
Than I tried restore Froyo from nandroid which I found something here on forum. Than I flashed CM7 and bootloader error again.
Now I have CM7 by Maniac for defy plus which worked well except camera and battery... I know that here are many topics about downgrading, camera fixing and others but all which I read are bad in something for me...
Here are some options what I found but I don't know if I can use one:
from http://forum.xda-developers.com/showthread.php?t=1216982
from http://forum.xda-developers.com/showthread.php?t=966537 but I'v ever flashed Android 2.2.
Or http://forum.xda-developers.com/showthread.php?t=1465436 ... This is better option but I have flashed full 2.3.6 SBF and here is:
So, how can I downgrade or repair battery and camera? I don't care whether I have got GB or Froyo kernel if I have working camera and battery.
Click to expand...
Click to collapse
Congrats man! Seems that rsdlite on Windows is the most reliable solution. Now to fix everything just flash cm10 (jelly bean) or later rom. It includes fixes for camera and battery
Again, no downgrading bl(not even jtag will work)
Sent from my MB526 using Tapatalk 4
Oh, ok. I'll try it. Thanks.
Hmm, and than, can I flash CM7 by Maniac or JB/GB WIUI and fixes in CM10 will still working?
Ms2ginger is not good for me because it haven't got slovak language. I'll give defy to my grandfather.
//And now, in Quarx CM 10 my battery don't charge. I tried 2 chargers and charging via USB too.
In options, battery is still "60% - Unknown"
Alejandrissimo said:
Working and rooted, thanks for your help
Click to expand...
Click to collapse
Hehe, I'm glad...
sterver1 said:
Oh, ok. I'll try it. Thanks.
Hmm, and than, can I flash CM7 by Maniac or JB/GB WIUI and fixes in CM10 will still working?
Ms2ginger is not good for me because it haven't got slovak language. I'll give defy to my grandfather.
//And now, in Quarx CM 10 my battery don't charge. I tried 2 chargers and charging via USB too.
In options, battery is still "60% - Unknown"
Hehe, I'm glad...
Click to expand...
Click to collapse
There's a cm7 2ndboot build which should work for you. Try cm10.1 or above, problem should be solved.
JB wiui includes those fixes, as does cm7 2ndboot. I don't think that wiui GB has them. I would personally go for cm10.1 or above
Sent from my MB526 using Tapatalk 4