i get 3 bad blocks encountered when i flash userdata is it anything to worry about??
thanks
elspanish88 said:
i get 3 bad blocks encountered when i flash userdata is it anything to worry about??
thanks
Click to expand...
Click to collapse
The 3 Bad Blocks Get Removed I think Have you tried Booting Up in the Kernel or You can boot up get a Backup I made In My thread and Use that If you want its Stock Offical beta Requires Advance Kernel
Xperia4life said:
The 3 Bad Blocks Get Removed I think Have you tried Booting Up in the Kernel or You can boot up get a Backup I made In My thread and Use that If you want its Stock Offical beta Requires Advance Kernel
Click to expand...
Click to collapse
thanks for replying, my phone boots up and works fine, just wondered if i should be extra careful or if i should worry because i have no warranty
No You Should Be Good To go mate Bad Blocks Means Just File errors Corrected But Still Be cautius
Xperia4life said:
No You Should Be Good To go mate Bad Blocks Means Just File errors Corrected But Still Be cautius
Click to expand...
Click to collapse
Thats not true, Bad blocks are unuseable, once the controller gets unacceptable errors it marks the block as bad and it's assigned to a dead pool.
AndroHero said:
Thats not true, Bad blocks are unuseable, once the controller gets unacceptable errors it marks the block as bad and it's assigned to a dead pool.
Click to expand...
Click to collapse
Dont listen To me Listen To AndroidHero!
Although according to this, it should be possible to use jTag to recover bad blocks http://wiki.openmoko.org/wiki/NAND_bad_blocks
I would doubt the effort would be worth it though, the bad blocks are only in /data/ and 3 prob only account for only a few mb in lost internal storage
I always have 1 bad block when flashing system.img and it still boots fine...
TheCraig said:
I always have 1 bad block when flashing system.img and it still boots fine...
Click to expand...
Click to collapse
It will, the only partition you don't want bad blocks is /boot/. /boot/ is a small partition as it is, loosing blocks means that you would not be able to flash alot of custom kernels.
Thanks guys
Sent from my R800i using XDA
AndroHero said:
It will, the only partition you don't want bad blocks is /boot/. /boot/ is a small partition as it is, loosing blocks means that you would not be able to flash alot of custom kernels.
Click to expand...
Click to collapse
I have no bad blocks on /boot/, but boot partition is 15MB?
Sent from my R800i using Darkforest ICS
Mine's Normal Keiran Flash it agin ? or flash back to 42 and then flash agin what i did
Related
When I try the new MCR with FroYo, I get the following error message:
Writing BOOT:
E:Error finishing BOOT:
E: Failure at line 386:
write_raw_image PACKAGE:boot.img BOOT:
installation aborted.
Click to expand...
Click to collapse
I read reports of other people having this issue with this ROM, and even people having this issue with DeFroST. Some people said that it's due to a 'messed up' boot partition, that can't fit the boot image included in the ROM. How can our boot partition be messed up like that?
When I try the new MCR with FroYo, I get the following error message:
Writing BOOT:
E:Error finishing BOOT:
E: Failure at line 386:
write_raw_image PACKAGE:boot.img BOOT:
installation aborted.
Click to expand...
Click to collapse
I read reports of other people having this issue with this ROM, and even people having this issue with DeFroST. Some people said that it's due to a 'messed up' boot partition, that can't fit the boot image included in the ROM. How can our boot partition be messed up like that?
Click to expand...
Click to collapse
That's because you have bad blocks on your boot partition. With 2 bad blocks the boot.img must be < 2304 kb. Will make one tomorrow for defrost.
I see. So how did I end up having bad blocks? Or are they already present out of the box on some devices?
franklinvv said:
I see. So how did I end up having bad blocks? Or are they already present out of the box on some devices?
Click to expand...
Click to collapse
Any info on this yet, as to how, why, way out?
franklinvv said:
I see. So how did I end up having bad blocks? Or are they already present out of the box on some devices?
Click to expand...
Click to collapse
I think all flash memory has bad blocks. There is nothing you can do about it.
My Nintendo Wii also has bad blocks on the NAND, totally normal.
StuMcBill said:
I think all flash memory has bad blocks. There is nothing you can do about it.
My Nintendo Wii also has bad blocks on the NAND, totally normal.
Click to expand...
Click to collapse
Interms of installing a new rom, (tried MCR r17) do I have to wait until one will actually fit? If I am right in thinking, the bad blocks mean there is not enough space to install the rom?
So hopefully when the MCR r18 is out, as long as it is smaller then the r17 it will install.
I am learning fast, but there is so much reading, it can be a lot to take in. Yesterday I messed up big time trying to install the rom many different ways, I ended up formatting the sd card before I backed up the back up to the PC. Luckily it was fairly easy launch recovery and install a freshly baked MCR 3.1, and then use Titanium to restore the apps and data. So no harm done, and thanks to everyone here and at Modaco who posted all the info I needed to acheive that.
sucramco said:
Interms of installing a new rom, (tried MCR r17) do I have to wait until one will actually fit? If I am right in thinking, the bad blocks mean there is not enough space to install the rom?
So hopefully when the MCR r18 is out, as long as it is smaller then the r17 it will install.
I am learning fast, but there is so much reading, it can be a lot to take in. Yesterday I messed up big time trying to install the rom many different ways, I ended up formatting the sd card before I backed up the back up to the PC. Luckily it was fairly easy launch recovery and install a freshly baked MCR 3.1, and then use Titanium to restore the apps and data. So no harm done, and thanks to everyone here and at Modaco who posted all the info I needed to acheive that.
Click to expand...
Click to collapse
Yeah I think you will have to wait until a boot.img is made that is small enough to fit on your memory, its a bit of a pain, but I don't think there is anything you can do?
I'll just have to hope and pray like the football then.
franklinvv said:
When I try the new MCR with FroYo, I get the following error message:
I read reports of other people having this issue with this ROM, and even people having this issue with DeFroST. Some people said that it's due to a 'messed up' boot partition, that can't fit the boot image included in the ROM. How can our boot partition be messed up like that?
Click to expand...
Click to collapse
Guys,
I also have the same problem and dont know what to do next.
I am on CM but the new CM 5.0.8 also have the boot img more than 2.2 MB so i am stuck.
Neither can upgrade to FROYO as well.
Not sure if any one can help on this
richardtrip said:
That's because you have bad blocks on your boot partition. With 2 bad blocks the boot.img must be < 2304 kb. Will make one tomorrow for defrost.
Click to expand...
Click to collapse
Hi richard, I am new to defrost.
Please let em knwo if you make one. i would like to try it out.
Thanks a lot.
I have issues using large boot images as with modaco roms and richard's earlier rom's but richard's work fine for me now after about 0.6 ish. Hope this helps.
Cheers,
Drew
-------------------------------------
Sent via the XDA Tapatalk App
jedisquirrel said:
I have issues using large boot images as with modaco roms and richard's earlier rom's but richard's work fine for me now after about 0.6 ish. Hope this helps.
Cheers,
Drew
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Can i put this ROM on N1
Is there a way to fix the badblocks?
peewster said:
Is there a way to fix the badblocks?
Click to expand...
Click to collapse
I have asked. The only real option is the guys that mod the roms make a smaller boot image. So I have been informed.
It's not good.
peewster said:
Is there a way to fix the badblocks?
Click to expand...
Click to collapse
These are physical parts of your NAND flash being broken. Small parts, but still.
So no, they can't be repaired.
ieftm said:
These are physical parts of your NAND flash being broken. Small parts, but still.
So no, they can't be repaired.
Click to expand...
Click to collapse
Could we unroot, and get a faulty replacement.
Sorry I didn't reply earlier, didn't see your message.
No because the kernel is different for majority of devices. There would probably be other issues that I'm not aware of either also would imagine.
Drew
I have issues using large boot images as with modaco roms and richard's earlier rom's but richard's work fine for me now after about 0.6 ish. Hope thi
Click to expand...
Click to collapse
Can i put this ROM on N1
Click to expand...
Click to collapse
-------------------------------------
Sent via the XDA Tapatalk App
I'm kinda hoping that the official froyo rom will bork the device for us with bad blocks. But I'm almost certain htc will be aware of the issue and the boot image will fit on our devices no problem.
If you were however to accidentally brick your desire, I'm sure they would replace your device.
Drew
-------------------------------------
Sent via the XDA Tapatalk App
jedisquirrel said:
I'm kinda hoping that the official froyo rom will bork the device for us with bad blocks. But I'm almost certain htc will be aware of the issue and the boot image will fit on our devices no problem.
If you were however to accidentally brick your desire, I'm sure they would replace your device.
Drew
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Guys,
Any idea on the boot image size of froyo?
Will froyo fix our issues?
Hello guys,
i was checking the forum about this issue but I haven't found any explanation.
How does this corruption work? I mean, is it a type of protection for booting unofficial roms? Or it just happens?
How common is this problem? How does it happen? Is there a particular procedure that corrupts these blocks? or it just happens?
Is there a test to check if any corrupted block is present? an fsck?
Thank you in advance.
Regards,
Daemon
It just happens. ALL NAND flash have errors, in some cases it' on the boot blocks
Any sources? I dont believe this.
xtcislove said:
Any sources? I dont believe this.
Click to expand...
Click to collapse
Not our fault u dont believe this..
Read some article on wiki about nand memory or somewhere else. Its particulary known that that a certain % of the memory has errors. If u got bad luck some of theses corrupt blocks lays on the boot sector of your memory..
I suppose you can ask for a substitution in this case, because it can blocks your upgrades, right?
I hope so cause I have bad blocks on mine and most custom roms don't work
HTC 's updates have small boot images, so no problem to updates
If that's the case then why can't devs make roms with small boot images?
Hi all,
Can anyone tell me how (if possible) to downgrade back to 2.1 (JM5 or JM8) successfully as each time i try all i get on the first reboot is an error (cannot see error as to quick) which then reboots?
DemolitionManHD said:
Hi all,
Can anyone tell me how (if possible) to downgrade back to 2.1 (JM5 or JM8) successfully as each time i try all i get on the first reboot is an error (cannot see error as to quick) which then reboots?
Click to expand...
Click to collapse
And you didnt read the big explanation of how to do it in first posts in jm6 (not sure), jm7, jm8 and ji1 threads why?
dupel said:
And you didnt read the big explanation of how to do it in first posts in jm6 (not sure), jm7, jm8 and ji1 threads why?
Click to expand...
Click to collapse
Which post?
DemolitionManHD said:
Which post?
Click to expand...
Click to collapse
Ever heard of search function? Or at least look through 2-3 pages, its not that hard.
dupel said:
Ever heard of search function? Or at least look through 2-3 pages, its not that hard.
Click to expand...
Click to collapse
Not to be funny but looking through there is a number of post referring to this, thats why i ask which one you are referring to
yep. downgrade straight off the bat, JPC is the wicked error rom which raped yer efs
Just page 2 (and when you started this thread - page one) contains 2 topics by the name:
Release: I9000XWJM8 - Multi CSC(s) Europe (and ji1 obviously) with deteiled instructions on how to install, downgrade and possible solutions to problems.
azuresystem said:
yep. downgrade straight off the bat, JPC is the wicked error rom which raped yer efs
Click to expand...
Click to collapse
Is there a way without errors, if i could see the error as it reboots of screen to fast.
Oops. My bad please ignore
format the drive, i.e hardreset it before you reflash pull out yer sim n external SD etc
1 : hard reset
2 : DLmode
3 : flash yer rom
4 : recovery mode
5 : new hardreset
6 : start up yer rom
if you still keep getting errors i have no clue, only managed to get those while the sd still being in the phone and another partition mounted on the sd
best of luck and read the guides
azuresystem said:
format the drive, i.e hardreset it before you reflash pull out yer sim n external SD etc
1 : hard reset
2 : DLmode
3 : flash yer rom
4 : recovery mode
5 : new hardreset
6 : start up yer rom
if you still keep getting errors i have no clue, only managed to get those while the sd still being in the phone and another partition mounted on the sd
best of luck and read the guides
Click to expand...
Click to collapse
Cheers m8
Interesting to know why would want to downgrade to eclair?
Hi, mainly for reference and current issues i have
Sent from my GT-I9000 using XDA App
nandihno said:
Interesting to know why would want to downgrade to eclair?
Click to expand...
Click to collapse
Possibly as JPH sux big time.. just spent hours trying all sorts of combinations and man it spoils the phone.
Hope Samsung get the REAL release working well..
TrOjAn
TrOjAnUK said:
Possibly as JPH sux big time.. just spent hours trying all sorts of combinations and man it spoils the phone.
Hope Samsung get the REAL release working well..
TrOjAn
Click to expand...
Click to collapse
You should try it with the rombie mod. It freakin rocks
Woolios said:
You should try it with the rombie mod. It freakin rocks
Click to expand...
Click to collapse
yes it's awesome, but also a battery monster
azuresystem said:
yep. downgrade straight off the bat, JPC is the wicked error rom which raped yer efs
Click to expand...
Click to collapse
JPH raped my EFS too. I had JPC doing it, fixed it by deleting /efs/nv*. Funny thing is, right after flashing JPH it had my normal nordic product code - but later it had changed to KOR. Very strange. I wonder if it might have happened when I rooted it? Well, anyway, be careful out there, check product code before up/downgrading.
Does anyone have the sd card files for the sims 3 xperia play version? It appears ea deleted them from their servers or something as i get NaN 0MB of 0MB and eventually download failed whenever i try to download the data files. Thanks.
The Sims 3 for Xperia Play
Did you ever find a solution?
swing4thefence said:
Did you ever find a solution?
Click to expand...
Click to collapse
Nope. Couldn't get it to work..
Oh i think ive got it backed up lol let me get it for you.
EDIT: Uploaded. You just need to unzip it: http://www.mediafire.com/?75r2i224t9brx64
AzNTypeR said:
Oh i think ive got it backed up lol let me get it for you.
EDIT: Uploaded. You just need to unzip it: http://www.mediafire.com/?75r2i224t9brx64
Click to expand...
Click to collapse
wouldn't this be warez? free for our device but not for all, i dunno though just saying.
fma965 said:
wouldn't this be warez? free for our device but not for all, i dunno though just saying.
Click to expand...
Click to collapse
Yeah but the data only supports our device because its the only one that supports the buttons (ie Optimized..)
AzNTypeR said:
Yeah but the data only supports our device because its the only one that supports the buttons (ie Optimized..)
Click to expand...
Click to collapse
like I said maybe I dunno so let's leave this one as allowed
Sent from my R800i using Tapatalk 2
Thanks! I had been looking for this since May. Idk if EA has just stopped hosting the data for this version or what. I tried the data files from two other sources and they would crash after trying to start a game. Definitely backing up this for when my sd card decides to erase itself again...
xperia64 said:
Thanks! I had been looking for this since May. Idk if EA has just stopped hosting the data for this version or what. I tried the data files from two other sources and they would crash after trying to start a game. Definitely backing up this for when my sd card decides to erase itself again...
Click to expand...
Click to collapse
Your Welcome! Just click the thanks button
Hi,
does anoybody know how to use CM11 as main os and Fire OS as second OS in Safestrap?
My acutal problem is that the Safestrap partition can't be bigger than 1,2GB while the flashable zip from ggow has some MB's more. Does anybody know a solution for this problem?
I'm sorry for spelling mistakes or wrong grammar
Thanks ^^
From what ggow stated this is currently impossible. If the boot loader was unlocked I'm sure it would be possible. But right now you can only write an OS to the stock slot. Otherwise you would brick your phone.
Sent from my Fire Phone using XDA-Developers mobile app
JDubbed said:
From what ggow stated this is currently impossible. If the boot loader was unlocked I'm sure it would be possible. But right now you can only write an OS to the stock slot. Otherwise you would brick your phone.
Sent from my Fire Phone using XDA-Developers mobile app
Click to expand...
Click to collapse
It won't brick the phone. The most commonly reported problem is loss of connectivity using the ROM in the non-stock slot.
So there's no chance at the moment?
Thank for for replying btw ^^
Exordos said:
So there's no chance at the moment?
Click to expand...
Click to collapse
It depends...
Would you be fine with using Fire OS in "WiFi only" mode? (since there is no connectivity via mobile data, SIM card isn't recognized)
If you are planning on using Fire OS only for a handful of things, I could test* a slimmed down version in slot 1...
* not before Saturday though...
Did a quick calculation, I'm down to 1.27 GB uncompressed data (from 1.8), so it's not looking good, I'll update given it works out...
edit: Successfully flashed it to slot 1 with 54 Mbytes space left, yeesh... ^^ Not stable at all, I'll give it a whirl with flashing a customized backup to slot 1 on the weekend, maybe this approach is useful...
Hi,
so first of all I apologize for my late reply, had a hard week :c
Second thing is that I want to thank you very much for your support ^^ And as long as the small version works it would be great if you could give me the link to it ^^
Just to say it again: Thank you!
Exordos said:
Hi,
so first of all I apologize for my late reply, had a hard week :c
Click to expand...
Click to collapse
Me too, expect an update within the next week, I hope it works with WiFi only and has no FCs...
edit 1: the TWRP backup image is ready for testing but I have to "reset" my device: whenever I create the "rom-slot-1", system partition shows up with 0 MB... working now...
edit 2: Welp, with my final image I had around 200 MB free space on the system partition but the biggest problem is again the hardware identification on non-stock slots, e.g. the mac address is "missing", so no WiFi at all, screen turns on & off by itself after a couple of minutes. I'm not going to upload the image, since it's only a case study titled "crash & burn".