Related
So I was trying to go from comrom to OMFGB nightlies, and didn't know you have to go to OMBG first. When I tried to do that. I odined the ED05 modem, then flashed OMFGB, then the GAPPS. It wouldn't work, and then I read I had to flash a new kernel, so I flashed the Glitch high leakage. Then it started to work, but after it went to the boot screen, it went to a new CMW, blue, and tried to install GAPPS? I think that's what it was doing, but it went really quickly, and said something like it couldn't mount the sd card, which is weird. So I took out the sd card, and it said waiting for mount, or something similar. I put it back in, but it wouldn't work. So then, I flashed back to UKB with the pb&j kernel, to see if I could get things going from there. It booted fine, but when I tried to just flash OMFGB, it would go to the boot screen, and then go back to CWM. So I tried to go back to UKB, and then it did the same thing, didn't change the boot screen at all (so now it's stuck with Galaxy S Cyanogen mod boot screen). I tried to flash OMBG then, but it was still going back to CWM. I'm thinking about odining the eclair package, and then trying from there. What do you think. Oh and usually I go to android central, but they don't have OMFGB nightlies there, so here I am.
TL;DR: I flashed a bunch of GB stuff in what I assume to be in the wrong order, now I'm stuff. Help me?
EDIT:After flashing a bunch of stuff, I don't remeber what or what order, just that the Glitch was last, I managed to get it to boot, first with a glitch boot screen, then the android boot screen. I'm not sure what I'm on, I think it is OMGB, at least that is what the widget says when I booted it up. I'm really confused. Anyways, I think I got it.
EDIT2:Nope, stuck at the boot to CWM loop. I'm going to try to go back to UKB (froyo) through that sticky in dev
EDIT3:Well I'm waiting for it to download, so what I did that worked was flash OFGB in red CWM, weird, but it worked. I'm leaving it at that for now, cause nobody is replying.
While I'm glad you got things to work, you should probably start from scratch if things start to get weird again. I highly recommend this thread as the proper way to go from CM7/MIUI/OMFGB back to stock, and from there back to whatever you want: http://forum.xda-developers.com/showthread.php?t=1124391
Remember that when you flash stock DL09 or EB01 or ED05, you also have to have the atlas 2.2 pit file and "repartition" checked in ODIN.
Finally, while you still have things working, I recommend you do a nandroid backup. If you need to go all the way back to stock before coming back to gingerbread, you can do an Advanced Restore > Data Restore in order to get your apps and such back pretty painlessly.
Yeah thanks, that's the sticky I was talking about. I didn't know about the re-partition button having to be checked, thanks for that And the Data restore is through CWM? I assume so. And for that, I just need a regular nandroid backup?
Yes, in CWM you can choose backup and restore, and then do a system backup.
When you want to go back to a given setup (i.e. your apps, widgets, etc.) you can do an advanced restore where you choose to restore just data, and not the whole nandroid system backup.
That's pretty cool, I never new about that. So I tried the *228 1 and 2 thing, cause I couldn't download the beta swype, and I thought it I needed too, but it said my phone couldn't be activated, and to try again, then the I lost all signal. I rebooted, and it came back, but I couldn't activate it again. It's being weird still, and in the morning, I'm starting over like you suggested. I'm still receiving calls though, and I get good connection. For the morning, I was wondering if I could just check to see if I have everything I need. I have:
CI500_VZW_ED05_FROYO_REL.tar.md5 from the thread you posted for odin
OMGB 1.2.0
OMFGB nightly build 7/21
Glitch High leakage v11.1
The CWM for all roms (red)
lithid gapps (unless you think the other gapps is good)
and I think that is it. I don't have the atlas 2.2 pit file, can I just search here for that? Thanks for all the help
EDIT:Found the atlas 2.2, and I use that at the same time as the md5 file, right?
EDIT2:Okay, I tried to do a nandroid backup, but with the CWM recovery 4.0.1.0 (I think that's what it is), it didn't show anything, like it said backing up system, then it didn't show what part it was backing up, and the status bar stayed blank, then it moved on to data after a while, and that. It said it failed to back up sd-ext, which I'm guessing is why it wasn't working properly. I'm doing the odin restore to froyo, and if someone could tell me the correct order to install/flash/odin stuff to get to the OMFGB nightlies, that would be amazing!
EDIT3:I think I did it right. Odined to froyo, Odined the ED05 modem, Odined the CWM for CM7, flashed CM7, Rebooted, Flashed Glitch Kernel, then Flashed OMFGB nightly build 7/23. I still need to do gapps though.
EDIT4:I did gapps, and almost everything looks good. I can't activate my phone through *228 1, and when I try to set up my google account, it says it couldn't establish a reliable connection to the servers. And After I call to activate my phone, my service goes dead. I can still text and receive calls though
EDIT5:man, a lot of editing. I flashed OMGB 1.2.0 on top, and now I can set up my google account. Still not activating though :/
Unrelated question, how come sometimes my wifi and signal bars are grey, sometimes blue (I'm using cyanbread)? I think when they are grey, I'm not using signal? How do I make them blue?
Apologies for the state of this question, but it's been a while
I've been using CM7 on my unlocked Defy since I bought it (6-8 months). However, recently it's gotten a lot more unstable; it freezes up all the time, I can't wake it up, google maps will crash half the time, the camera too, and it involves me restarting it a fair bit. I need to sort it out and I thought I could take this opportunity to try out a new ROM
However I haven't done anything ROM related for a while, and the computer I originally rooted/installed a new ROM on my Defy with is no long gone...so I'm not even sure what programs I need to install.
I seem to remember, the way the Defy is set up, it isn't as simple as wiping the phone and installing any ROM on it?
Could anyone point me in the direction of a guide on here dedicated to moving from CM7 to another ROM? From scratch? Failing that, I may be tempted to just try and wipe and get CM7 on there from the beginning...not even sure where to start
Thanks
If you want to flash a stock ROM, you need to flash the SBF through RSDLite.
While to flash a custom ROM(CM7,CM9), boot into recovery, wipe all, flash the zip from sdcard.
neo.ank said:
If you want to flash a stock ROM, you need to flash the SBF through RSDLite.
While to flash a custom ROM(CM7,CM9), boot into recovery, wipe all, flash the zip from sdcard.
Click to expand...
Click to collapse
nice one, thanks. It's just as simple as that when changing from one ROM to another? I thought something to do with how the Defy's memory worked meant some kind of 'backtracking; wasn't possible
insurgente said:
nice one, thanks. It's just as simple as that when changing from one ROM to another? I thought something to do with how the Defy's memory worked meant some kind of 'backtracking; wasn't possible
Click to expand...
Click to collapse
Yep, that simple. You could try Pikachu Edition, for example, which is even easier (just get into Recovery, install zip, choose the zip file and then AROMA installer does almost everything that's needed). I'm just starting to try it, many people like it.
If you move between CM7 nightlies it isn't even necessary to wipe data, but given your condition, I would recommend you to wipe everything and start again (remember to backup apps and data).
Good luck!
great, always good to see a bit of pikachu
can I go straight from CM7 to pikachu via a wipe? isn't CM7 on kernel 2.3.7?
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
jnktechstuff said:
MOD : EDIT
try dleeting you who system, except your recovery , there should be a system whipe that should work, then reflash ur rom
Click to expand...
Click to collapse
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
yeatsie said:
hmm, i already dId a system wipe/reset from CWM recovery (all local data gone, just ext SD card remaining) when i applied CM10?
ps. One thing i noticed last night testing was that if i switch the camera to front-facing, it works. But rear-facing (main) no-go..
Click to expand...
Click to collapse
check you camera connector. It may come lose from the motherboard. Try reseat the connector.
Sent from my A500 using Tapatalk
.
opened up the A500 last night - all looked good, all connectors in place, nothing obviously wrong?
Noticed the screen when i switch to the rear camera has artifacts from other screens in the background (ie Pulse app title heading etc) suggesting some kind of software glitch?
yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
Known issue in the CM10 alpha test ROM. You should go to the one in general rather than making your own thread which WayDownSouth is unlikely to see.
http://forum.xda-developers.com/showthread.php?t=1789711
yeatsie said:
its been like that on my A500 since i installed Taboonay 3.01, and hasn't managed to fix itself even now i'm running the latest 4.1.1 CM10.
Everything else pretty much works. When i switch to camera, i just get green static with occasional pink horizontal stripes, then it just locks up and either the A500 resets, or i have to home-screen.
Any ideas on how to fix?
Click to expand...
Click to collapse
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Moscow Desire said:
There.s really only 2 things it can be;
1. Dirty code.
2. Bad camera.
The camera is not like a radio, you can't update internal drivers like a firmware boot. So that only leaves the software side.
First off, which recovery system are you using? CWM, Public, TWP? And which specific version?
I will guess you are on ICS unlocked bootloader also? Version 4-8?
MD
Click to expand...
Click to collapse
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
yeatsie said:
It started on ICS 4.03 (Taboonay) and its unlocked CWM bootloader (cant remember the version, maybe 3) and still present on latest CM 10 20120821 and unlocked ICS CWM v6 recovery bootloader.
Click to expand...
Click to collapse
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Moscow Desire said:
Well, maybe something with your recovery version (some of them were a little flakey) so you should boot to CWM and just check the version. Currently I use rev 1.7.2 of CWM. Some of the previous versions seemed didn't wipe data very well.
Bootloader version is Fine. Anything above ver4 is great.
Double check your CWM and if it needs updated, I would go ahead and do it. Just remember to make a new recovery backup after updating (just in case it doesn't read the older ones). I really don't think it's a hardware issue. If it is, it was just bad timing.
The camera drivers are pretty much the same more or less. They either work, or they don't, and it's not often cameras mess up. They do, but it's pretty rare I think.
When you install a rom, of course you should always do the following;
Wipes
a. User Data/Factory Reset
b. Cache
c. Dalvik Cache
d. Battery Stats (optional)
Mounts and Storage
a. Format System
b. Format Flexrom
This, with the newer CWM, should effectively clean the partitions of previous data.
Hope it takes care of the camera issue. Follow the above, re-install a rom. Try one of Civato's Flex roms. No camera issues reported there. Check it BEFORE installing any apps. And if you use Titanium Back-up, Check the camera FIRST BEFORE trying to restore any old data.
MD
Click to expand...
Click to collapse
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
yeatsie said:
Cheers, i did as you listed with the wipes. Just checked, im on CWM 1.7.3. The bootloader is part of that right?
Will try the Flex ROM you mention and see if helps..
Click to expand...
Click to collapse
Boot loader is different from cwm recovery. When you boot, it should say in white text.
If in doubt, run Acer recovery installer from the market. It will tell you which version.
MD
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
I have always had this intermittent problem on my a500. I have always used the stock ROM since I purchased it, and it's been the same since each OTA upgrade, so I doubt that it's a problem inherent to one custom ROM or the other.
A Dalvik cache clean has never worked for me, sometimes a restart has helped, but more often than not it doesn't help.
If someone discovers a set of steps that fixes this problem every time it occurs, I would be glad to hear of it.
yeatsie said:
ok, just installed the Acer app from market, it says bootloader is 0.03.14-MUL .
And when I boot up, it says Skrilaxcz boot loader v8.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Hi, What was your final solution to this problem? I'm trying to fix mine right now.
-Thanks-
No fix as yet, pretty much gave up trying to use the camera.
Sent from my Nexus 7 using Tapatalk 2
If anyone else's having this problem with ONE OF THE CAMERAS (Not both of them but frontal OR main) then this should be the solution:
Watch this video someone uploaded https://www.youtube.com/watch?v=Cjevl8I6rIA but HAVE THIS IN MIND:
That cord (FLEX) he's talking about is for the FRONTAL camera. Not related with the main or back camera. So that should fix the green trouble for the frontal one.
But, if the main camera shows green image or weird lines, that's likely because its connector is not correctly attached to the main board. That connector is NOT a flex, but it's a built in block in the board of the same camera unit. You need to remove or lift the main board, totally remove the main camera unit, clean the connector (both male and female) with alcohol and connect it again applying some pressure. If the trouble really was the connector not being correctly placed, that totally fixes it.
If it worked, let me know
That totally worked and fixed my green screen camera problem, thanks! (was a total pain to re-seat the camera but worth it)
So I finally got arround to getting my Nook up-to-date from 7.1 to the 7.2 encore CM7 rom. Thought that Rom Manager would take care of everything for me, and it looked like it was well on its way.
So it finally downloads and I'm all excited to install it, maybe it'll help the random hanging errors when I'm on wifi. (dummy me) Selected just to wipe dlavick (sp?) cache and not backup current rom, and durring the install, it reports a critical error and fails out. Okay, fine, sounds good, i'll just hop online and figure out how to manually install it. I reboot, and it just hangs. Wierd, but I reboot again. And again. And I finally come to the conclusion that it must have screwed over my old rom as well.
If anyone can give me an idea of how to proceede, do i reflash a new rom? And how do I go about it without damaging the current files that I have installed, I've got a few hundred ebooks and comics that i'd hate to lose.
breakneat said:
So I finally got arround to getting my Nook up-to-date from 7.1 to the 7.2 encore CM7 rom. Thought that Rom Manager would take care of everything for me, and it looked like it was well on its way.
So it finally downloads and I'm all excited to install it, maybe it'll help the random hanging errors when I'm on wifi. (dummy me) Selected just to wipe dlavick (sp?) cache and not backup current rom, and durring the install, it reports a critical error and fails out. Okay, fine, sounds good, i'll just hop online and figure out how to manually install it. I reboot, and it just hangs. Wierd, but I reboot again. And again. And I finally come to the conclusion that it must have screwed over my old rom as well.
If anyone can give me an idea of how to proceede, do i reflash a new rom? And how do I go about it without damaging the current files that I have installed, I've got a few hundred ebooks and comics that i'd hate to lose.
Click to expand...
Click to collapse
Go to my tips thread linked in my signature and make a bootable CWM SD per my item A10. If your books and comics are on SD do not use that SD for CWM, use a different one. Then you can flash the new CM7.2 ROM with that. It should boot fine for you. If it still balks on you, go back to CWM and do a wipe data/factory reset. That will wipe out the installed apps and settings, but will not effect the books and comics you have on your media partitions (emmc and sdcard). But you will have to reinstall all of your apps.
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