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?
i was just wondering if anyone knows if its possible to change the splash screen on the galaxy nexus.
I have tried the "fastboot flash splash1 .img" that i used on my nexus one, to no surprise it didnt work, there isnt a 'splash' partition on samsungs as far as im aware.
If i remember correctly on my mates nexus s, he managed to change his by flashing this kernel he found. If it is in the kernel, could anyone tell me how to change it?
cheers in advance
Anyone? really want to change it ...
Bumpppppp.
http://forum.xda-developers.com/showthread.php?t=1364044&highlight=boot
It's in /system/media, but that will be wiped out every time you flash a new ROM. /data/local is where it should go for a permanent fix.
alanid said:
http://forum.xda-developers.com/showthread.php?t=1364044&highlight=boot
It's in /system/media, but that will be wiped out every time you flash a new ROM. /data/local is where it should go for a permanent fix.
Click to expand...
Click to collapse
I appreciate the reply, but what you posted was referring to the bootanimaion, i want to change the splash screen, thats the "Google" logo screen, the first thing you see when you boot your phone
maxib123 said:
I appreciate the reply, but what you posted was referring to the bootanimaion, i want to change the splash screen, thats the "Google" logo screen, the first thing you see when you boot your phone
Click to expand...
Click to collapse
I can't give you a complete answer, but I could maybe point you in the right direction.
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name. That is a list of all the partitions on the GN. We know it's not boot, system, user data, cache, efs, radio, recovery, sbl and xloader. That leaves param, misc, metadata and dgs. Maybe try dumping these and see if any of them can be converted to images (using nbimg.exe).
Sent from my Galaxy Nexus using Tapatalk
efrant said:
I can't give you a complete answer, but I could maybe point you in the right direction.
Look in /dev/block/platform/omap/omap_hsmmc.0/by-name. That is a list of all the partitions on the GN. We know it's not boot, system, user data, cache, efs, radio, recovery, sbl and xloader. That leaves param, misc, metadata and dgs. Maybe try dumping these and see if any of them can be converted to images (using nbimg.exe).
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks, much appreciated! i'll post back what i find...
Yeah I would really like some help if anyone is willing?
maxib123 said:
Yeah I would really like some help if anyone is willing?
Click to expand...
Click to collapse
Although I'm no expert, I'll try and have a go at it a little later if I have some time.
its in param...ive tried...i couldn't do it
Try to look at ramdisk, but i think the nexus has a different approach.
Bump, still wondering about this one...
Splash Scren
I came across with your question now!!!
The command is not "fastboot flash splash1 .img" but is "fastboot flash splash1 splash1.img". I hope that helped. If you have tried this please let us know!
I'd suppose it's in the param partition, or better I used to use the param.lfs in a tar, flashed via Odin and did it that way... I'll give it a try and see how that works out...
On second thoughts, I haven't got Windows, I'm running Ubuntu and that usaually has problems with Odin, I'll still try, though!
TheLiTTle said:
I came across with your question now!!!
The command is not "fastboot flash splash1 .img" but is "fastboot flash splash1 splash1.img". I hope that helped. If you have tried this please let us know!
Click to expand...
Click to collapse
Are you posting in the right forum?
I think you are talking about HTC devices...
Hey, i'd also be interested in changing boot screen i Nexus, especially Nexus 5. Could anyone help me?
LexanderPL said:
Hey, i'd also be interested in changing boot screen i Nexus, especially Nexus 5. Could anyone help me?
Click to expand...
Click to collapse
1. Why bumping a thread from 2 years ago? 2. Why are you on the galaxy nexus forum asking about the nexus 5?
Sent from my Nexus 10 using XDA Free mobile app
Hi,
I am fairly new to rooting (infact this is my first post).So,please be gentle if i am violating any rules.
I had put JELLY BAM on my GNEX and it was running fine. I tried partitioning my memory which did not go well so then I tried reflashing my ROM , which again did not go well and accidentally i deleted my ROM and all of my backups. So basically I am not able to use my GNEX .
I have no ROM and was only able to access bootloader and recovery menu (TWRP) . So i tried flashing it thru NRT(by wugsfresh) and since then I am stuck in bootloop(Was trying to flash stock JDQ39) & upon that I am back to stock recovery of android. Also, now PC is not ready to detect my GNEX as ADB device.
Please help me out, I am in dire need of it. Cant find a simillar issue any where else.
Thanks in advance.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
work in progress
Zepius said:
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thanks for the prompt reply. Halfway thru ..
Zepius said:
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
madforsoccer said:
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
Click to expand...
Click to collapse
put simply you probably trashed your partitions. you might have to use ODIN to repartition
madforsoccer said:
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
Click to expand...
Click to collapse
I had a similar problem. I thought it was because my disk was partitioned-screwed. So I tried this: http://forum.xda-developers.com/showthread.php?t=2065470
It didn't work for me, but it's worth a shot for you. Give it a go.
Will try the ODIN method.
Also, do you think I am experiencing persistent boot-looping because I wiped off my 'system' (did it for the first time)
coz i have been flashing ROM's and kernels on weekly basis now and this has never happened before.
Still not working, tried the ODIN part also, still stuck in boot-loop.
I jus want to know what exactly is the problem here..!!
getting frustrated now.
Hi all,
Since I am facing difficulties flashing ROM. IF only someone can share a backup image of ROM (CWM/TWRP) with me I can get it restored and flash another ROM later on as need be.
You said you partitioned your memory. What exactly do you mean by this, what did you do?
cupfulloflol said:
You said you partitioned your memory. What exactly do you mean by this, what did you do?
Click to expand...
Click to collapse
I was trying to implement swapper on my gnex , which when failed led to this mess i am in currently.
Hi,
My nexus stop at the booloop so i decided to flash the stock rom with nexus root toolkit but after i tried but is stuck on the part of "writing the system".
Someone know how to solve this?
Have you tried doing it manually from fastboot? If so, does the problem persist?
bananagranola said:
Have you tried doing it manually from fastboot? If so, does the problem persist?
Click to expand...
Click to collapse
I'm trying that now. i think it is taking a little in "erasing userdata".
I hope that this just take a little but i dont know.
still stuck on the "erasing data" :|
i'm really worried about this. well i will continue trying.
i will let you know if i made any progress.
Well guys i have good news
After a while i tried fastboot all the images one-by-one and i could unbrick my nexus yeyyyyyyyyyy xD
Well after thinking a little i tried flash the image of the TWRP then i thought "i can do this for the other images" and pufff start working
DavidFarinha said:
Well guys i have good news
After a while i tried fastboot all the images one-by-one and i could unbrick my nexus yeyyyyyyyyyy xD
Well after thinking a little i tried flash the image of the TWRP then i thought "i can do this for the other images" and pufff start working
Click to expand...
Click to collapse
That's good. In general, if you do use a toolkit and it doesn't work as expected, give the manual method a shot. Toolkits may be more convenient for some people, but they simply can't always be as reliable as the manual method.