Develop Bugs

back to stock

I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks

No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452

And actually it might even be a safer approach to revert to stock from a stock like rom http://forum.xda-developers.com/showthread.php?t=1439916

Bricked beyond all recognition baby!
Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.

putney1477 said:
I checked the forums and couldnt find my answer.
I am rooted and have twrp, and the android market installed. I would like to go back to bone stock.
I can just reset the KF under device right? How do I uninstall twrp?
Thanks
Click to expand...
Click to collapse
Even if you want to go back to pure stock, keeping/reinstalling both TWRP and FFF are the safest and smartest things to do.

Thepooch said:
No thats incorrect you dont just reset the device you must wipe well and flash stock I must tell you numerous people are bricking themselves fairly bad attempting to do the same personally I would avoid it just flash modaco instead other than that the method to return to stock is in the second post http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2

putney1477 said:
Wow.....looks complicated. I just rooted and flashed twrp yesterday, wish I never had. I want to sell my kf, but I want it stock. Reading the post, it looks like I will mess it up pretty badly. I dont know how to use adb
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).

Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2

tamaker said:
android.process.acore
process.android.providers.calendar
These are wise words indeed. Installed Twrp and MiUI ics rom and played with it but gave up after day or so and was headed back to stock... battery was/is apparently too low AND I keep getting 2 force close errors for (right after boot) ...
-android.process.acore
-process.android.providers.calendar
(happens right after the UI starts loading ... if Im quick enough I can get one of the homescreen apps to load, but I notice the settings menu item or none of the software buttons for home, etc are there
... then after I click the force close button it just starts to boot again... not enough time to try to get twrp back on to handle boot so I can wipe and try to flash update.zip (the fires stock rom).
Oh well, its only 200.00 and I'll be getting another one I guess. glad it was with this and NOT one of my smartphones I tinker with from time to time. lesson learned about playing with rom flashing when battery is low I guess.
Click to expand...
Click to collapse
I have the same problem, but my battery was 100% when flashing back. Is this good night for the kindle then?
It boots in to the 6.2.2 software, but these errors pop up and force close then eventually does a restart. Dammit!

putney1477 said:
Ohhh ok so i just change the file to update.zip and flash it In twrp? Will that break root too? So thats all i have to do to get back to stock? Should i wipe in twrp before i flash?
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.

Dasanko said:
No, that's not all you should do to get back to stock... follow ALL the STEPS. Wiping is VERY important. Ie, don't just rename the file to update.zip and flash it right away, or you'll most likely end up with a soft brick. I was only clarifying that one specific step.
Click to expand...
Click to collapse
oh ok, thanks

Just a side note after restoring to stock you need to then perform a factory restore as well which will wipe your sd card if all goes well it should smooth out from there

Dasanko said:
The only mention of ADB is "adb push C:\kfu\software\update-kindle-6.3.1_D01E_4107720.bin /sdcard/update.zip", which you can easily avoid if you don't want to touch ADB.
Just rename your downloaded file to update.zip (watch out for the file extension, Windows hides most of them on default settings), then just copy it into your KF like you do any other file. Do not place it in any subfolder.
Be sure to follow the steps carefully, or else you may end up with a soft brick (fixable).
Click to expand...
Click to collapse
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?

putney1477 said:
Anyone know how to check to see if windows adds .zip? Like how do I check the default settings for file extensions. Also do I need to unroot before I flash back to stock? or will flashing take care of that for me?
Click to expand...
Click to collapse
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).

Dasanko said:
http://windows.microsoft.com/en-us/windows-vista/show-or-hide-file-name-extensions That applies for Vista/7. XP is almost the same.
Flashing back to stock will undo anything you've ever done or had on the device, except for the contents of /sdcard (the stuff you've copied to it from the computer).
Click to expand...
Click to collapse
OMG! I can't thank you enought for taking the time to answer all of my questions!!! It worked!!!! I am back to stock! (I had no doubt, thanks to you!) THANK YOU!!!
Heather

[Q]Remove TWRP for completely stock kindle?

Nevermind. didn't see the sticky.
how do I delete?

I have been having the same problem... and have been very fed up working on and off for a few months trying to fix this problem. My kindle boots into recovery mode no matter what bootmode i set it to using KFU 0.9.6. I have tried going into fastboot, restarting the device, then booting into normal mode, then it flashes on and of a few times, then boots into recovery(I have mostly been running TWRP 2.0.0 but have recently received TWRP 2.1.1). It seems as if i have tried every possible variable!!!!! It is very annoying and it would be extraordinarily appreciated if somebody can find an answer!!! Please help!!
PS I will gladly post additional information upon request

This belongs in questions and answers, but you can get rid of it by using kindle software update which also unroots the device.

I wish that it was true ("factory defaults")
jji7skyline said:
This belongs in questions and answers, but you can get rid of it by using kindle software update which also unroots the device.
Click to expand...
Click to collapse
Unfortunately, going back to "factory defaults" is a misnomer. It only replaces the rooting operation. The bootloader is not updated.

Angeloftheafterlife said:
Nevermind. didn't see the sticky.
how do I delete?
Click to expand...
Click to collapse
PM a Moderator ask to remove the topic. I typically ask MikeChannon to remove any threads I make.
Sent from my Amazon Kindle Fire using xda app-developers app

Yet another bricked A100 - Need to restore locked bootloader

So, I'm on vacation last week, watching a movie on my tablet when it starts to become very laggy. After a minute or two, it locks up completely. Just like everyone else, I reboot it to find that it doesn't get any farther that the green Acer logo. I was running CWM recovery, but nothing seems to work... every command gives me an error. After reading this thread by NighPlayer32: http://forum.xda-developers.com/showthread.php?t=1749967 I switch to TWRP recovery and am able to push an update.zip to the internal sdcard, but still can't install it because none of my partitions will mount.
At this point, I've given up on getting this thing to work. I can get into fastboot and recovery, but beyond that I've had no luck and I'm guessing it's fault hardware (EMMC?). It was purchased in December, so it should be under warranty but it has a unlocked bootloader, which will cause some problems if I send it to Acer. Does anyone know of a way to restore it to a stock bootloader via fastboot or recovery? OR... has anyone with missing partitions been able to load an update.zip successfully?
Any help would be GREATLY appreciated!
Thanks in advance!

ED2O9 said:
So, I'm on vacation last week, watching a movie on my tablet when it starts to become very laggy. After a minute or two, it locks up completely. Just like everyone else, I reboot it to find that it doesn't get any farther that the green Acer logo. I was running CWM recovery, but nothing seems to work... every command gives me an error. After reading this thread by NighPlayer32: http://forum.xda-developers.com/showthread.php?t=1749967 I switch to TWRP recovery and am able to push an update.zip to the internal sdcard, but still can't install it because none of my partitions will mount.
At this point, I've given up on getting this thing to work. I can get into fastboot and recovery, but beyond that I've had no luck and I'm guessing it's fault hardware (EMMC?). It was purchased in December, so it should be under warranty but it has a unlocked bootloader, which will cause some problems if I send it to Acer. Does anyone know of a way to restore it to a stock bootloader via fastboot or recovery? OR... has anyone with missing partitions been able to load an update.zip successfully?
Any help would be GREATLY appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Sorry to hear another one died. We've attempted a few methods but none have so far worked. If you can still push to internal SD you can try to push the a100 boot loader in recovery via adb but you'll lose cwm and fast boot so it will still go back with a custom recovery. There is a stock recovery image around which can also be flashed in recovery via abd which should put it back to normal aside from any custom ROM you may be running. If you're interested I'll try to find the stuff for you and setup some instructions. It'll be tomorrow though I'm about to head to bed.
Tapatalked from my A100 - CM10

I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium

-DarkKnight- said:
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Hardbricks you can't , its faulty emmc, you either have it or you don't.
Tapatalked from my A100 - CM10

-DarkKnight- said:
I'm scared
How can I prevent my own a100's death
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
me too lol, i just have rooted my tab but i preffer to not touching the bootloader.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
pio_masaki said:
Hardbricks you can't , its faulty emmc, you either have it or you don't.
Tapatalked from my A100 - CM10
Click to expand...
Click to collapse
hey pio! sorry but my english is a lil short, i dont understand that part, what do u mean?

pio_masaki said:
If you're interested I'll try to find the stuff for you and setup some instructions.
Click to expand...
Click to collapse
Thanks! Like I said, I've tried everything to get a ROM to load and all I get is "can't mount" failures, so I'm assuming that it need to go back to Acer. If you could give me any tips to restore it to the stock bootloader, I'd really appreciate it. There was a thread I found that had a link to a LOCKED bootloader restore script, but the link was dead.

Deshabilitado said:
me too lol, i just have rooted my tab but i preffer to not touching the bootloader.
---------- Post added at 05:19 PM ---------- Previous post was at 05:17 PM ----------
hey pio! sorry but my english is a lil short, i dont understand that part, what do u mean?
Click to expand...
Click to collapse
emmc is the part of the device where the storage is, everything from recovery, bootloader, system, data, internal sd, etc, are all on this chip, if it's damaged or faulty, you can't use that portion of the the memory. The first sign of it failing generally seems to be laggy, slow running, followed by a freeze. Then you are forced to hard reboot, and then you have problems of any partitions mounting.
@ED209 - I'll see if I have some time to hunt this stuff down, although the script pack that zeronull has for unlocking the bootloader also has the a100 and a revert script to restore the stock locked bootloader. The script may or may not work in recovery as it was meant to run from android, but it should be easy enough to either adapt to recovery, or just manually issue the commands over adb in recovery. The PC side will push the bootloader.blob and the script for the tablet side, then run the script on the tablet which will do the bootloader flash, then reboot, however we don't want it to reboot until you have stock recovery or you get locked out.

I know that flashing update.zip fails due to corrupt or missing partitions, but do you think restoring a backup package might work? I guess I'd need a stock backup image, push it to the internal sdcard and just try to run a restore from TWRP. I have a feeling it won't get any farther than the update.zip, but at this point I'll try anything. Do you remember ever seeming if someone posted a link to a stock restore .img?
Beyond that, is it possible to recreate the partitions through ADB?
Thanks again...

ED2O9 said:
I know that flashing update.zip fails due to corrupt or missing partitions, but do you think restoring a backup package might work? I guess I'd need a stock backup image, push it to the internal sdcard and just try to run a restore from TWRP. I have a feeling it won't get any farther than the update.zip, but at this point I'll try anything. Do you remember ever seeming if someone posted a link to a stock restore .img?
Beyond that, is it possible to recreate the partitions through ADB?
Thanks again...
Click to expand...
Click to collapse
There is parted in custom recovery which would in theory work, but its never been attempted before. I'm supposedly getting a brick sent to me (not 100% if it will happen or not) and it's one of the many things I plan to try.
Flashing and restoring will fail since the partitions can't be accessed.
A restore image will fail for the same reason.
I have tons of ideas but until I get ahold of a brick its all purely theory and speculation and until I'm sitting there looking at it I can't figure out how to do it, its weird I know but I can't just bust out what I want to do, I have to be doing it.....
Tapatalked from my A100 - CM10

I suggest you erase all evidence of it being rooted/modded then your warrenty is ok
Do you have a method to check if it is there so i can pretend to wipe everything and brick it, while pretending it wasn't my fault while my warrenty is still here?

-DarkKnight- said:
I suggest you erase all evidence of it being rooted/modded then your warrenty is ok
Do you have a method to check if it is there so i can pretend to wipe everything and brick it, while pretending it wasn't my fault while my warrenty is still here?
Click to expand...
Click to collapse
A pretend wipe is obvious. And what you just suggested isn't exactly honorable, returning an item as broken when its not. And wiping isn't bricking, during my time making the black hole tools I soft bricked at least 20 times, full out wrecked corrupted effed up partitions, always came back. You can't invoke this brick, you have it or you don't.
As for wiping it clean of mods, that is what we were discussing in this thread already. Its also kinda shady as the warranty expires when you root and again when you unlock, and yet again with the custom recovery and also the custom ROM. However it is a straight hardware failure, an issue Acer knows of. I would suggest calling or maybe chatting on their site, I'm pretty sure another brick victim is getting a replacement even rooted and unlocked.
As for checking, no I don't know of a way. The brick thread had aimed to condense all known information to try to isolate it to any build dates or anything specific, but not enough information was provided to do it. For awhile I thought cm9 was safe, but recently a brick occurred on cm9 as well.
I would advise your next step be to visit the Acer site, try to chat with a rep and ask about the hardware failure and your options with it rooted. You may get the same deal the other user did and just pay shipping.
Tapatalked from my A100 - CM10

I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.

ED2O9 said:
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
Click to expand...
Click to collapse
That wasn't aimed at you, no worries. I still suggest you go chat with Acer on their site, calling charges you, and see what they say about the tablet in its current state.
Tapatalked from my A100 - CM10

ED2O9 said:
I wouldn't send it in under warranty coverage if I felt that the issue was due to improper modifications that I made to the device. I'm typically pretty meticulous about following directions, and I was running the stock ROM. I had unlocked the bootloader and added CWM for back-up purposes (which I never got around to because I needed to make space on my SD card), and the lock-up occurred when I was watching a video clip I recorded that afternoon. Based on the severity of the "brick", I'm fairly certain that it's a hardware issue. I'm hearing people mention $150 repair bills, and I'd hate to pitch this tablet because of a EMMC failure, which appears to be increasingly common on this device.
Click to expand...
Click to collapse
Well 150 is less than the original price
And pio said its the hardware fault its either broken or not broken so modding wouldn't do anything
Sent from my LG-P500 using xda premium

fastboot oem unlock?

droc.noles said:
fastboot oem unlock?
Click to expand...
Click to collapse
What does that have to do with anything in this thread?
Tapatalked from my Galaxy S II - CM10

Probably trolling
Sent from my Full AOSP on a100 using XDA Premium HD app

pio_masaki said:
What does that have to do with anything in this thread?
Tapatalked from my Galaxy S II - CM10
Click to expand...
Click to collapse
Misinterpreted what OP was trying to get done, don't mind me.
I had an issue where I was locked out due to ignorantly running the revert to locked bootloader script. Boot verified failed, recovery verified failed. fastboot oem unlock got me back to the toggle between lock and unlock. My apologies, carry on.

droc.noles said:
Misinterpreted what OP was trying to get done, don't mind me.
I had an issue where I was locked out due to ignorantly running the revert to locked bootloader script. Boot verified failed, verified failed. fastboot oem unlock got me back to the toggle between lock and unlock. My apologies, carry on.
Click to expand...
Click to collapse
Ah ok. And glad you got that squared away, that info may be useful should that occur again.
Tapatalked from my A100 - CM10

pio_masaki said:
That wasn't aimed at you, no worries. I still suggest you go chat with Acer on their site, calling charges you, and see what they say about the tablet in its current state.
Tapatalked from my A100 - CM10
Click to expand...
Click to collapse
In looking back over the brick threads, I realized that you are the member that posted the scripts to return the tablet to a locked bootloader. The link is dead, so I was wondering if you could repost it.
Thanks!

Porting the new Kindle Fire

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.

[Q] Tried to install ROM, Galaxy Nexus won't boot at all

I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?

hulslanderam said:
I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?
Click to expand...
Click to collapse
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app

FIXED
sensation lover said:
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.

Awesome!
hulslanderam said:
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.
Click to expand...
Click to collapse
Congrats! That's gotta feel good to resurrect a "dead" phone!
I've tried to use the OMAP flash to fix mine, but I still can't get into Odin mode (even tho the drivers and bat file seem to install successfully). If you have any tips, then please let me know.