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?
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
So the title pretty much explains it. What is the likelyhood that someone could port the new kindle fire software to the old KF? If the aspect ratio is the same it seems like it should be possible because both are based off of Gingerbread (I think). It is also possible that Amazon is planning on updating the old KF to the new software but I just went to the website where the updates are (http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620) and I am fairly certain that even though I haven't been on stock for a very long time that it is still the same that it was the last time that I checked. I realize that this isn't the normal type of thread and it may not generate a lot of interest but I just was thinking about it and what better place than here to ask about it? Thanks!
nschiwy said:
So the title pretty much explains it. What is the likelyhood that someone could port the new kindle fire software to the old KF? If the aspect ratio is the same it seems like it should be possible because both are based off of Gingerbread (I think). It is also possible that Amazon is planning on updating the old KF to the new software but I just went to the website where the updates are (http://www.amazon.com/gp/help/customer/display.html?nodeId=200790620) and I am fairly certain that even though I haven't been on stock for a very long time that it is still the same that it was the last time that I checked. I realize that this isn't the normal type of thread and it may not generate a lot of interest but I just was thinking about it and what better place than here to ask about it? Thanks!
Click to expand...
Click to collapse
Its definitely posable, Its just a matter of doing it.
powerpoint45 said:
Its definitely posable, Its just a matter of doing it.
Click to expand...
Click to collapse
I would volunteer to head the project if I knew what I were doing. The only experience I have with cooking roms is in android kitchen so I am pretty much in the dark...
certainly more possible than the reverse
Thepooch said:
certainly more possible than the reverse
Click to expand...
Click to collapse
haha possible is one thing, I think that it's just extremely unlikely that someone would want to. Although, I've sometimes wished I could run GB on my gnex but nobody would ever try to build GB for the gnex because it was shipped with ICS
I got TWRP to attempt to flash the new update for the 2nd generation (it got to 70/80% before hanging), it's just the bootloader files that are keeping me from doing so. There are two flash instructions though... An engineer version, and a production one. Changes to the updater script and removal of some files is all we really need.
I have absolutely no idea how to do that though.
this is certainly the place to find someone that does
Here's the source: http://www.amazon.com/gp/help/customer/display.html?nodeId=200203720
Jessical said:
I got TWRP to attempt to flash the new update for the 2nd generation (it got to 70/80% before hanging), it's just the bootloader files that are keeping me from doing so. There are two flash instructions though... An engineer version, and a production one. Changes to the updater script and removal of some files is all we really need.
I have absolutely no idea how to do that though.
Click to expand...
Click to collapse
That's a pretty gutsy move to try and flash the update without changes to the updater-script. The script tries to flash both the xloader and bootloader. Had it been successful, your device probably would have been bricked and left you only the possibility of usb boot to recover it. Anyway, I was curious about the possibility of getting our KFs to boot with this 2nd generation software, so I did some experimenting.
It's not the bootloaders that keep it from flashing... In fact, there's no way to get it to flash on the 1st generation KF without modifying both the updater-script and the partition table. Here is a list of items that need to be manipulated first...
- The updater-script uses the ICS style by-name references to the partitions. All of them need to be changed to refer to the partitions correctly.
- The section of the script that flashes the bootloaders and the boot partition are enclosed inside of a check of the product name that fails. These conditions have to be removed so the boot image can be flashed. I actually commented out the entire section with the exception of the command that flashes the boot partition.
- The system directory is now larger than the original KF partitioning will allow. The system partition must be enlarged to accommodate the difference. I shrunk the userdata partition to provide more room to the system partition. I suppose one could prune some files out of the system directory and make it fit into the existing partition, but I didn't want to try and figure out what was important or not.
The above changes should be enough to get TWRP to flash the update completely. Unfortunately, it won't even pretend to boot as it never gets out of the bootloader. Unless someone else has some useful insights, I think this particular idea is pretty much dead in the water.
kinfauns said:
That's a pretty gutsy move to try and flash the update without changes to the updater-script. The script tries to flash both the xloader and bootloader. Had it been successful, your device probably would have been bricked and left you only the possibility of usb boot to recover it. Anyway, I was curious about the possibility of getting our KFs to boot with this 2nd generation software, so I did some experimenting.
It's not the bootloaders that keep it from flashing... In fact, there's no way to get it to flash on the 1st generation KF without modifying both the updater-script and the partition table. Here is a list of items that need to be manipulated first...
- The updater-script uses the ICS style by-name references to the partitions. All of them need to be changed to refer to the partitions correctly.
- The section of the script that flashes the bootloaders and the boot partition are enclosed inside of a check of the product name that fails. These conditions have to be removed so the boot image can be flashed. I actually commented out the entire section with the exception of the command that flashes the boot partition.
- The system directory is now larger than the original KF partitioning will allow. The system partition must be enlarged to accommodate the difference. I shrunk the userdata partition to provide more room to the system partition. I suppose one could prune some files out of the system directory and make it fit into the existing partition, but I didn't want to try and figure out what was important or not.
The above changes should be enough to get TWRP to flash the update completely. Unfortunately, it won't even pretend to boot as it never gets out of the bootloader. Unless someone else has some useful insights, I think this particular idea is pretty much dead in the water.
Click to expand...
Click to collapse
yeah!
we need to modify the updater-script!
how can we change the MLO and xloader?
Josepho1997 said:
This is probably a stupid question, but is there supposed to be a updater-script, or at least any apps inside the .tar.gz?
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I'm really glad that we have gotten a conversation started about this. Does anyone think that there is a likelihood of Amazon updating the software for the 1st gen or is the hardware on the new one significantly different from the old one that they are probably going to just continue to send out bug fixes until they stop supporting it?
Hey. I was wondering if somebody could port the new launcher to the original fire because that is what I really want. Is that possible?
2390 said:
Hey. I was wondering if somebody could port the new launcher to the original fire because that is what I really want. Is that possible?
Click to expand...
Click to collapse
Rather than let this go on a lengthy discussion, detracting from the original topic, I'm just going to say...
No, it is not possible.
Hmm... would it be possible to modify an existing ics rom to get just the launcher?
soupmagnet said:
...detracting from the original topic...
Click to expand...
Click to collapse
There are plenty of other posts on that topic.
Where?
Sent from my Kindle Fire using xda app-developers app
How? Please tell me!!!!!!
Sent from my Kindle Fire using xda app-developers app
2390 said:
How? Please tell me!!!!!!
Click to expand...
Click to collapse
Since this is obviously a lesson in futility, I'll play along.
Do you know anything about ROM development and programming?
A little. But I will be willing to try. I can learn quickly.
Sent from my Kindle Fire using xda app-developers app
You can get the Kindle Fire's source code from Amazon's website. Set up your build environment and get to work. I will say this...Many experienced minds before you have tried, and failed.
Hi guys, yesterday i flashed a stock image for my galaxy nexus maguro, because i had 1 problem..
But the problem is still here, and now i have another one..
The 1st problem : When i call somebody or i receive a call, the earphone (or however it is called) doesn't work, the mic not work too, but this happes the most time, and sometimes it works well...
[The 2nd problem : My camera app seems to take pictures, but there is nothing in the gallery... it don't even save the photo in the memory..] <---- SOLVED BY WIPING THE INTERNAL STORAGE !!
For both problems, they happen on any rom...
Actually i'm on Vanir Rom..
Please guys help me :/
follow the return to stock guide in my signature. do not skip any steps.
Zepius said:
follow the return to stock guide in my signature. do not skip any steps.
Click to expand...
Click to collapse
I solved my 2nd problem by my self, i don't know why, but my internal storage was locked, i was't able toi write anything on it.. i just wiped it throught the twrp recovery, but still the 1st problem is still here... and it's really anyoning.. :/
martinko23 said:
I solved my 2nd problem by my self, i don't know why, but my internal storage was locked, i was't able toi write anything on it.. i just wiped it throught the twrp recovery, but still the 1st problem is still here... and it's really anyoning.. :/
Click to expand...
Click to collapse
might be a hardware issue; still, have you tried flashing another baseband, just to see if it changes anything? and please, don't ask me on how to flash a baseband, plenty of guides around here (hint: stickies, general and q&a forums)
beekay201 said:
might be a hardware issue; still, have you tried flashing another baseband, just to see if it changes anything? and please, don't ask me on how to flash a baseband, plenty of guides around here (hint: stickies, general and q&a forums)
Click to expand...
Click to collapse
I'll look at that thanks...
But how it can be a hardware issue ? Sometimes it work all fine, sometime not...
martinko23 said:
I'll look at that thanks...
But how it can be a hardware issue ? Sometimes it work all fine, sometime not...
Click to expand...
Click to collapse
iminent hw failure?
beekay201 said:
iminent hw failure?
Click to expand...
Click to collapse
oh :/ You think it can be fixed somehow ?
martinko23 said:
oh :/ You think it can be fixed somehow ?
Click to expand...
Click to collapse
replacing the damaged hw component? maybe the ifixit guys have a tear down.
beekay201 said:
replacing the damaged hw component? maybe the ifixit guys have a tear down.
Click to expand...
Click to collapse
Okay thx, i'll take a look at it, but now i'm going to try the baseband thing.
Hello users, I have my Mi Max Hydrogen 3/32 bricked since time ago, I tried all the threads out there to revive my device, as a hard bricked no fastboot, no download mode responsive, of course no recovery.
I guess that bootloader is messed due to a bad flashing of a file uploaded by error.
I found a method, idea is to force device to enter to download mode restoring bootloader or turn on responsive again to allow a new flashing cycle.
I´m now using a Redmi 5 Plus and I did this method to prevent any trouble in the future, one never knows.
If some user wants to help just I need that this zip should be flash it through recovery and the file just will dump/backup the first 125MB aproximately of system and it will kept in sdcard with the name of debrick.img and kindly can upload it to the cloud. This will be greatly appreciated and I hope that also can help to other users with same/similar issue now. If things go fine I´ll explain in details to accomplish that
View attachment Partial_Sys_Dump_for_debrick.zip
Reserved.
A brief explanation:
I have found this tutorial https://forum.xda-developers.com/showthread.php?t=2369125 (applying concerning to this model) among several of the same type, the idea behind this is that in a cell phone bricked because the bootloader is damaged and trying to boot it does not find that partition readable, so burning/writing the first lines of the operating system in a sdcard, then putting it in the device then it will search these files to try to boot. If the emmc/motherboard is not totally damaged or the measurement of the files is sufficient for it to do it then after this it will come to turn on, stay or spend a little more of the bootlogo and that will indicate that it is in a condition of flashing all the system files again through the fastboot or MiFlash to make it functional back and bring it back to life.
In my case I have damaged the buttons, the back cover opened in the repair shop and this may have a negative influence to try it properly, therefore I could not recover it yet, or the size of the files is not completely sufficient since the tutorial is based on a Galaxy S3 with a memory lower than This device or plainly emmc is definitely damaged.
However, each case is different and I think that this explanation can help others who are in similar cases.
There you go: deleted
Please, explain what you are doing even if it didn't work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
A great thanks, my device has sleeping maaaany time. I will try it and I´ll report even if this doesn´t work.
nijel8 said:
There you go: hydrogen_3-32_debrick.img
Please, explain what you are doing even if it didn't work.
Click to expand...
Click to collapse
If you want to give me a second chance, I explained the idea behind this. It´s based on a device the half of ram/rom than this so I think that maybe it´s needed at least 200 mb to find working files to let it run. i´m not sure that if you are running in a custom rom and non miui rom it works anyway.
Your help is greatly appreciated and I recommend any user that can keep the zip dumper and Debrick image in a safe place just in case in the future could need it.
View attachment Partial_Sys_Dump_for_debrick-200MB.zip
hydrogen_3-32_debrick.img
Don't think this is going to work...
nijel8 said:
hydrogen_3-32_debrick.img
Don't think this is going to work...
Click to expand...
Click to collapse
Why do you think so? difference in sizes between 128 and 200 doesn´t matter? or plainly this method can´t work in this device in your opinion? I saw this method in other non Samsung devices like Lenovo totally bricked and cause is a similar device I thought that maybe..... and of course one don´t want resign.
Google sent a confirmation to grant access to your file. Thanks for support.