Related
So this is what happened...
I was helping my buddy install a Rom on his Droid X, and after wiping everything and installing the rom, i rebooted the phone and it got stuck on the "M" screen.
So i figured i would go into recovery and either restore a back-uped session or just wipe everything and reboot again.
But in recovery, he doesnt have an option to restore sessions or anything. and when i try to wipe data and clear cache partitions, he still gets stuck at the "M" screen when i reboot.
Also, in recovery, it gives me a message that says,
"E:cant open /cache/recovery/command"
and after googling this and looking for solutions, none have helped. It says try pulling battery for 5 minutes, or deleting the "update.zip" file (which i cant because i cant boot the phone up), and even pulling the SD card (which doesnt make sense, but nonetheless didnt work anyway).
Any help would be appreciated. I feel real bad for putting his phone on a soft brick haha so please help a brotha out.
Thanks in advance
ejeetguy said:
So this is what happened...
I was helping my buddy install a Rom on his Droid X, and after wiping everything and installing the rom, i rebooted the phone and it got stuck on the "M" screen.
So i figured i would go into recovery and either restore a back-uped session or just wipe everything and reboot again.
But in recovery, he doesnt have an option to restore sessions or anything. and when i try to wipe data and clear cache partitions, he still gets stuck at the "M" screen when i reboot.
Also, in recovery, it gives me a message that says,
"E:cant open /cache/recovery/command"
and after googling this and looking for solutions, none have helped. It says try pulling battery for 5 minutes, or deleting the "update.zip" file (which i cant because i cant boot the phone up), and even pulling the SD card (which doesnt make sense, but nonetheless didnt work anyway).
Any help would be appreciated. I feel real bad for putting his phone on a soft brick haha so please help a brotha out.
Thanks in advance
Click to expand...
Click to collapse
What ROM? What was the Android version before hand? At this point it's not going to matter, you're going to need to SBF (factory restore). Check google for guides, or look @ the site in my signature.
Yeah, seems from you described you got your hands on a bad file; maybe the file didn't get downloaded completely. In any case, your best bet is to sbf your phone (restoring to stock using software). There is a ton of info on that, do you shouldn't have a problem on how to do that. If you need help or direction, please let us know.
Sent from my DROIDX using XDA Premium App
you have encountered my one gripe about my X. You can't get to recovery if you get stuck in a boot loop.
Your only option is to sbf back to stock and go again. I just had this happen today while I was at work. I decided I want to run Apex 2.0 alpha 3 and messed up. I was stuck at work all day without my toy.
im having the exact same problem and i tried to sdf back to stock using rsd lite as explained in another section and it goes thru the whole process reboots itself, says 100% done and tells me to "power up this phone" only i cant because when it rebooted it got stuck on the M screen ands stays there and i cant power it up.....Any suggestions appreciated THANX
Get into stock recovery and wipe
Sent from my DROIDX using Tapatalk
Hi guys
Before I explain I'd like to say that yes, I have read other threads on similar topics, although none seem to have the same symptoms as me...
This week I bought a software-bricked Defy on eBay with the hopes of fixing it and giving it to a friend. I first tried flashing an old Eclair SBF to no avail (only switched on to bootloader) and thought that it could be failing due to it being on a newer firmware. So then I tried Froyo, and when that didn't work either (bootloops like when I received the phone) I thought my last resort was a CG 5 SBF, so I went for the JORDN_U3_97.21.51 build. This seems to get further into the booting process, with the MotoBLUR animation appearing but I get a BP Panic - 0x00080010 above the animation before the phone switches off. Thinking I had nothing to lose I tried a Gingerbread ROM, but that just bootlooped too so I went back to 97.21.51. I realise I've probably painted myself into a corner by flashing these
I'm all out of ideas with how to get the phone any further and have searched for the BP panic to no avail. I can get into stock recovery and bootloader, although the recovery seems to have issues with accessing the cache sometimes.
Thanks for reading
The same panic have y for the last 2 weeks, after flashing hangs in bootloader (red logo and no animation), after other flash hangs on a animated red logo and thats where you must give it time 3 or 4 min. wating, when its dont works you can try to pul out battery and do it in again while you hold the start and vol. down button, then in recovery menu wipe Dalvik cache and wipe cahe. Maby it works then, when not you can try like me to go again tho recovery and there restore stockrom, thats the way ym getting my defy work again. There are many ways to get it back to work again and it cost me 2 weeks after flashing maby 15 diverend roms to get it works and even than when it works, 2 days work whit rooting it and get 3G alive. So when you think its dead, maby RSDlite can bring it back to live, just like here.
Now my Defy MB525 working like a Defy 526 on Gingerbread.
So don't give up, when you can see whit RSDlite the phoon, it must be possible to get it work, only problem here was on a moment when the battery was empty, but here on XDA you can find the megayver method (charging on a ohter cell like a duo) or what y have don, get my old nokia loader (5V) and whit 2 wires hangs on the battery power it up to 4.1 V, succes.
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
ben_duder said:
Thanks, although I was just getting repeated boot loops rather than it hanging on the logo... And that wasn't animated either. How did you manage to restore the stock ROM through the recovery? Did you have a flashable zip? Please bear in mind that I did not get a custom recovery installed
I'll look out for the low battery problem. Thanks for your advice
Click to expand...
Click to collapse
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
nogoodusername said:
U should have wiped cache and data after flashing Froyo!!!!!!
It would have booted!!!!
Now u flashed GB!! Ur stuck there!!!
Flash gb again and Go to stock recovery and wipe data!!!! If know how to do it!!!
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
Thanks, although I'm pretty sure I did wipe cache and data... and I definitely did (several times ) after flashing Gingerbread. I feel like whatever is preventing Froyo and Gingerbread from booting is the same thing as what is giving me the BP panic on the CG 5 Eclair ROM.
I would suspect a hardware issue here.w
Sent from my MB525 using Tapatalk
I think it might be too It's a shame because I can enter recovery and bootloader okay, and the seller said it broke during a failed software update so I thought it would be a simple matter of reflashing an SBF.
what is bp panic?
what happens when it is booting?
Sent from my MB525 using xda premium
When I try to boot the CG 5 Eclair I get past the static Motorola logo (hence further than any other build) but the MotoBLUR animation is stuttery, with a BP panic at the top (see picture). This goes on for quite a while, then the phone switches off and this loops.
Ok if occurred during a software update, find out which he was installing and try that one. May also be worth trying motoupdate.
Sent from my MB525 using Tapatalk
I might try that, but won't it be useless now that I've flashed CG 5? I'll look into MotoUpdate
Is the general consensus that this is an unfixable hardware issue, then?
Apolgoies if you've already tried this, but I had a Defy which would do the same, either stuck on M logo or error in bootloader.
Each time I just plugged it into PC / USB at bootloader screen, and used RSD Lite to try another ROM. Eventually I found one which worked. I think I tried 5 before finding one which didn't cause any problems.
My defy was a ME525+ and the ROM which finally worked was "DEFYPLUS_U3_4.5.1-134_DFP-132_BLUR"
So, if you haven't already, I'd just suggest try a few more ROMS, flashed from Bootloader / RSD Lite.
Hope it helps somehow
Hey Guys,
i've got a strange bootloop problem with my defy plus ...
the phone was on 2.3.4 and i've rooted, installed 2ndinit, cm7, etc ...
yesterday i found the "Linux Installer" in the market and installed a debian on the defy just for fun (it's fun to see aptitude install packages on the defy, huh?! )
the loop-method didn't work for unknown reason, so i installed debian into chroot-folder ...
long story short - at a moment of no thinking i deleted /data/local/mnt/Linux ... the hole folder ... all apps crashed and the defy hung up ...
ok, i thought ... do a wipe ... wiped the defy and BOOTLOOPING ...
ok, flash 2.3.4 full-sbf ... done ... BOOTLOOPING ... WTF?!
then i tried maaaaany wipes, full sbf, fixed sbf, etc ... no success ...
after 5 hours of wiping, flashing, wiping, flashing, ... i resigned and flashed 2.3.6 full sbf (4.5.1-134_DFP-188) via RSD ... i was looking forward for a running system now ... but ... BOOTLOOPING ....
WHAT THE HELL IS GOING ON ??? Flashed full-sbf 's , wiped a lot, tried many fixed sbf ... i've just done everything that comes in mind in such a situation ...
now i don't have any more ideas ... is there somebody with a new look at this problem out there?
thanks in advice ...
So many wiping... .. but after flashed the 2.3.6 full sbf (4.5.1-134_DFP-188)... you'll see PASS and either it auto reboot or asking you to manually reboot.
Do this: first booting you goto stock recovery and do again factory reset and wipe..
If rsd lite showed no error during the flash and your phone bootloop after flash (with no fail to boot error code etc)....You should charge your phone full, and do a full sbf again. (As you flashed so much things after the first flash lol)
Edit: please make sure you flash the right sbf..... (downgrading through rsd lite can cause hardbrick......)
Edit2: Just aware you have posted in the wrong forum....
Go to stock Motorola recovery and wipe ...
ignore it if you already dis it
Sent from my DEFY
first of all, thx for your tips ...
as you can see in my post, i tried a lot of wiping after flashing ... but NOTHING helps ... even after full-sbf and wiping (data/factory AND cache again) it's just bootlooping ... after the flash of DFP-188 (2.3.6) i'm now unable to downgrade, so the flash process is working ... but every time i try to boot, it's just looping over and over again ... it doesn't matter which sbf or which android version ...
ps: the stock recovery comes up with NO errors (no /cache/... error or something) ... the wipe works with NO errors (both wipes done)
but i'm unable to boot anything .. treid to flash bootmenu and cwm over zip but (who wonders?) verification failed ... even tried cm7.2 / cm9 / etc ... (hope is dying last) ... no way to install / boot something ...
it's a strange prolem, i know ...
EDIT: cause of missing adb in stock recovery and failing boot sequence, i'm unable to do something on the system ... is there a way to get adb working or share root-folder ???
nobody with a good idea ???
do somebody have an similar problem or had an bootloop that won't go away after fullsbf and wipe?
is there anything on the system, that won't be deleted / wiped after sbf AND wipe ???
DJ_Synergy said:
nobody with a good idea ???
do somebody have an similar problem or had an bootloop that won't go away after fullsbf and wipe?
is there anything on the system, that won't be deleted / wiped after sbf AND wipe ???
Click to expand...
Click to collapse
i think there isn't.
check your rsd version and try to burn another sbf (231, for example).
RSD is the (i think) latest version 5.6 ...
is there any known problem with this rsd-version ??? is there a chance of a running system by flashing with an older rsd-lite (e.g. 5.0) ???
i really want to know what happens here with my defy ... i mean ... i really have no clue whats going on ... how could it be, that there is an bootloop even after flash AND wipe ... over and over again ...
i'm really despaired
ok, now i installed RSD 5.3.1 and downloaded DEFYPLUS_U3_4.5.1-134_DFP-2311
flash worked fine without errors, phone restarted and i hold power down to get into stock recovery ... i wiped data (factory reset) and wiped cache after that ...
then i rebooted the phone ... and it is just bootlooping ...
wtf ??? what is going on ???
ehhhhm ... hey guys ?!
is nobody out there with a clue whats going on here ???
PS: maybe i found a thing that is important for the bootloader unlock guys ... after that crazy bootloops, i was able to flash this crazy eclair from the downgrade thread ... it booted up with this b/w motoblur logo but is flickering and put a kernel panic message on the display ... after flashing a 2.3.6 again, this could not be redone ... eclair just won't boot (white led without display) ...
try to go to bootmenu and setup the boot into normal.. hope it works
nice try, but i can't even install 2ndinit without an bootable os, you know
i only got the stock recovery and the stock system for now ... but this won't boot ...
i'm getting crazy about that problem ...
hmm, i dont know, that look like a broken data partition, but the motorola recovery should be able the repair that (wipe data+cache which make a format, not the cache alone option, which only do it on cache...)
The only explanation possible if you get a reboot with a full sbf is another broken partition, like pds (the last one)
but CM7 (and recovery) doesnt touch anymore this partition... (never mounted)
thanks for your reply, epsy ...
it's giving me hope to have you here
i wiped a lot (yes, both wipes / factory reset and cache) (i also wiped each partition twice)
the idea with a broken patition was exectly what i have in mind when i look at the crazy things that are happening here ...
is there a way to flash such a partition ??? maybe with a customized sbf or with linux and flash-sbf ???
or is there a way to get adb up and running on stock recovery (don't think so, just hope )
hmm ... maybe this may help some guys that know the interna of our defys ...
this is part of the output of "sbf_flash -v -r"
Code:
CG_num: 38
CG_name: pds
signature_type: 0
start_addr: 0xb0300000
end_addr: 0xb06fffff
signature_start_addr: 0xffffffff
signature_end_addr: 0xffffffff
is this an output of an "normal" pds-partition?
if i try "sbf_flash -r -d --pds pds.img" i get
Code:
>> waiting for phone: Connected.
>> downloading pds: 0.0%
RX(7): [02]ERR[1e][8a][03]
>> downloading pds: failed at b0300000/b0700000
i've read about problems of sbf_flash and defy ... are there such problems, that we can't download dumbs from our devices ???
is there another way to backup and flash the partitions without root and custom recovery ???
Hey there Synergy, unfortunately I don't have an answer for you because...
I HAVE THE EXACT SAME PROBLEM!!! :S:S
How it originally started for me was I installed a cm9 defyplus on my defy (instead of a defy rom). It wouldn't charge my battery, and when phone died, that was it. Bought external battery charger, wiped the phone back to stock sbf, installed a nightly but wrong kernel, bootlooped. Went to reflash the stock sbf, constant bootloop, regardless of sbf now.
I manage to get all the way past the bootup up to the moto-blur setup but after about 3 seconds it reboots itself.
Nothings working, and whats even worse is that I can't access the stock recovery as its locked so my options are even more limited than yours........ Been flashing for about 6 hours now and I'm raging HARD to myself, nearly thrown my laptop across the room a few times.
Sbf_flash works fine on ubuntu. I hve done it lot of time. I get unexpected chip errors but it works!
@above
Boot into stock recovery by pressing and holding power and volume down button till the stock recovery appears. The bootlogo wil show but dont leave the buttons. Then pres volume up and down alternately till the menu is shown and wipe data and cache. I had same problem even after flashing sbf and it worked.
Sent from my MB526 using XDA
Thanks a ton! That worked for me.
I have the same problem
I also deleted the folder where linuxinstaller installed linux.
I have Defy with 2.2
So ... just to finish this thread:
there themes to be no way to restore this at the moment ... maybe it is the PDS-Partition that is broken ... Quarx CM10 Recovery can mount the PDS-Partition, so maybe they had a look at that ...
What i did: I flashed the newest stock rom again via rsd-lite and sent it to repair under warranty. Told them, i wanted to upgrade to newest firmware and after that got bootloop ... they changed the mainboard (have new IMEI now) after weeks of waiting ... so i think they also had no idea, what was the problem there ....
Hey guys. I'm trying to fix my friends Defy for him. I've rooted my old Evo 4g, my wifes samsung transform, and her motorola Photon Q so I'm pretty familiar with rooting. But I'm having a problem with his Defy. Here's the skinny:
So his phone froze up on him. And after pulling the battery, it now won't boot. So I booted into recovery, and tried a factory reset. The factory reset won't complete. The little loading bars that go across the screen just keep going forever (I let them go for 3 hours straight one day). And I still can't get the phone to boot. So I figure, no big deal, i'll just root and install custom recovery. So I looked into rooting methods for the Defy, and they all seem to involve booting the phone. Does anyone have any ideas? Or know of a way to reflash the original recovery? I'm assuming the problem is the recovery. Thanks in advance for any help. And my buddy thanks you too.
You can use RSD to flash it with stock rom of your region. Do not flash any gingerbread rom if the phone never had gingerbread(you will have downgrade issues).
I don't want a Tapatalk sig!
never heard of rsd. Just looking into it. It seems people are saying I would need to wipe cash and data first? Problem is when I attempt to wipe cache it just goes on forever never finishes.
Any Luck M8
dhughes214 said:
never heard of rsd. Just looking into it. It seems people are saying I would need to wipe cash and data first? Problem is when I attempt to wipe cache it just goes on forever never finishes.
Click to expand...
Click to collapse
was just reading your post and was wondering if you have had any luck with your buddy's Defy ???
Flashing a fresh .sbf using RSDlite should fix the recovery problems, as it will overwrite it with a fresh one. The /system partition will be rewritten, also. After flashing, the phone might boot to the system already, but if not, just enter recovery and do a factory reset, now it should finish fine and boot fine, as well. (it doesn't matter if you do a factory reset before or after the flash)
Latest RSD Lite I've found is v6.1.4. You will also possibly need drivers, google for - "Motorola_End_User_Driver_Installation_5.9.0"
Keep us posted! Good luck
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