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.
Related
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.
how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.
crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.
Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..
Hello all,
I was looking through, the development section when I realized there was no thread about how to edit the build.prop file.
The build.prop file helps Google Play and other apps identify what device you have.
This guide will show how to edit the file to get maximum app availability. You can also edit the file in order to change the pixel density and there are quite a few other changes as well.
(Note: This does not work on the stock kindle fire rom)
The first thing you should do is backup the build.prop file to your enternal storage.
(The build.prop file is located in the folder)
Once you have made a backup, you are free to edit it.
Change the following lines to:
ro.product.model=GT-I9100
ro.product.brand=samsung
ro.product.name=GT-I9100
ro.product.device=GT-I9100
ro.product.board=GT-I9100
(a few more rows down)
ro.product.manufacturer:samsung
Save your changes, reboot your device and you will have access to the complete android market. Gameloft games that say, "Your device is not compatible with this, game please request a refund" will work. Please note that it could take up to an hour before Google starts to think that you have a GT-I9100.
Enjoy the full market experience right from Cm7-9,
Greg
Thanks. This is a great guide!
Just a warning though: Some games/apps really are incompatible even though they may show up.
veeman said:
Just a warning though: Some games/apps really are incompatible even though they may show up.
Click to expand...
Click to collapse
This is true, but a majority of the games at least will work. It is more the Gameloft games that can start having problems.
Lemme throw this out there...
Many ROMs already have a device ID set. Currently on my gedeROM, I'm listed as a Galaxy Tab. Is the build.prop easy enough to change to any device? And could we take time to post in this thread, settings for other compatible devices? I do like my KF to be registered as a Kindle. And I would guess some device IDs offer benefits over others?
TinkerToyTommy said:
Lemme throw this out there...
Many ROMs already have a device ID set. Currently on my gedeROM, I'm listed as a Galaxy Tab. Is the build.prop easy enough to change to any device? And could we take time to post in this thread, settings for other compatible devices? I do like my KF to be registered as a Kindle. And I would guess some device IDs offer benefits over others?
Click to expand...
Click to collapse
The steps that I just posted above will work on almost any device running a stock rom or a custom rom. For some reason, it just does not work on Kindle Fire stock rom. There are benefits to each device, some device's have similar hardware as others. But if you are looking for more apps, the Nexus devices have the best app availability. just as a random example, the GT-I9100 might have a more similar processor to the Kindle then a Galaxy Nexus.
Sent from my Galaxy Nexus.
Could someone please post the original build.prop settings before making these changes.I didn't save a copy of it before I changed them and my KF has been stuck in portrait mode for some reason ever since I did this several days ago. Unfourtunately it didn't yield any better results for me in the Google Play store anyway even though my KF is rooted with KFU and I use GoLauncher.Thanks guys :laugh:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
technut said:
Could someone please post the original build.prop settings before making these changes.I didn't save a copy of it before I changed them and my KF has been stuck in portrait mode for some reason ever since I did this several days ago. Unfourtunately it didn't yield any better results for me in the Google Play store anyway even though my KF is rooted with KFU and I use GoLauncher.Thanks guys :laugh:
Click to expand...
Click to collapse
If you use root explorer it will save a backup for you
Sent from my LG-P999 using xda premium
eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
I am using the same ROM and am wondering the same thing. I will try it to see if the same thing happens to me.
Sent from my Kingle Fire running CM10 Jellybean
eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
It should be fine as long as you don't change anything important.
veeman said:
It should be fine as long as you don't change anything important.
Click to expand...
Click to collapse
What's an example of an app that doesn't show up using the default build.prop on my ROM?
I did this and after reboot everything seems fine except my brightness is stuck on high and nothing I've found will adjust it.
Any ideas?
Sent from Epic Touch ICS
eoy4 said:
Does this work for Jellybean ROMs? I followed this guide but my Kindle Fire wouldn't boot afterwards... I'm using twa_priv's CM10 rom
Click to expand...
Click to collapse
Had the same problem, so i booted in to recovery and wiped dalvik and cache then rebooted system.
I follow all the steps and the result is that phone is booting but the screen is tatally in black. Already did Dalvik and chache wiping proces with no lucky results...
Any idea what else I could do...
I did it on a LG Hub...
Regards
Thank you for this.........thank you very much
Wouldnt it be better if the build.prop was of a Nexus 7
All u really need to change in the build.prop is two lines
ro.product.model=Kindle Fire(or whatever it is)
ro.product.brand=Amazon(whatever it may be)
To
ro.product.model=Nexus 7
ro.product.brand=google
BTW this will work on any ROM
Sent from my Nexus 7 using XDA Premium HD app
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!
Anyone tried building a clockworkmod image from builder.clockworkmod.com? If we can get a good image maybe we can mod the rootingkit to flash that image instead of the Xperia S one. I am going to try in a day or two, but this will be my first time trying.
Just a follow up on this: I think I finally found the right way to build this, but I am afraid it will take more than a few attempts to get it right. I did find the dev/block locations to pull. I just have to get everything finalized on my new Ubuntu partition so I can do this properly. (Man, a lot more work then what I thought it would be)
popfan said:
Just a follow up on this: I think I finally found the right way to build this, but I am afraid it will take more than a few attempts to get it right. I did find the dev/block locations to pull. I just have to get everything finalized on my new Ubuntu partition so I can do this properly. (Man, a lot more work then what I thought it would be)
Click to expand...
Click to collapse
I'm willing to test for you. when you are ready, just message me.
That goes for ALL devs for this phone... I am NOT afraid to test, so hit me up. Email and personal number via PM if you prefer faster more reliable communication.
Pl. Look into this.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Sent from my LT28h using xda premium
ganeshbiyer said:
Pl. Look into this.
http://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
I was using that, but the problem is that is not updated for the newer stuff. I am using http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-os-x-part2/ as a guide which has more compressive information about how to build it.
Ok, I was able to find what I think was the kernal but the recovery sector is messed up a little I think, due to having a bad recovery sector. Looks like I am going to have to root without the Clockworkmod recovery built into it, so I can extract the recovery sector correctly.
Well, I think I might be able to fix the Xperia S one as I could not figure out how to extract the right folders and stuff. I was looking at the recovery.fstab and it has the wrong mounts for us. So I think that if I fix them then we can have a usable recovery.
popfan said:
Well, I think I might be able to fix the Xperia S one as I could not figure out how to extract the right folders and stuff. I was looking at the recovery.fstab and it has the wrong mounts for us. So I think that if I fix them then we can have a usable recovery.
Click to expand...
Click to collapse
Doesn't look like it worked.
I'm trying to unroot my kindle but I'm getting the binary error every time, and on forums they said it could be a problem with twrp and therefore, I'm here trying to figure this out, Thank you!
Could you be more specific? Also, the title of the post and the content therein seem to contradict each other. What exactly are you trying to accomplish?
soupmagnet said:
Could you be more specific? Also, the title of the post and the content therein seem to contradict each other. What exactly are you trying to accomplish?
Click to expand...
Click to collapse
I'm trying to unroot my kindle fire and revert back to STOCK ROM so I can send it back to Amazon due to touch screen issues, and I've read several forums that say it's an issue with TWRP 2.5 and that I should install 2.3, but I'm not sure how to do this.
It will take some searching on your part, but typically every version of TWRP in the KFDev forum has a recovery flashable .zip posted by other users. Or you could go to the TWRP website and download an older version and flash it in fastboot.
carlybelle said:
I'm trying to unroot my kindle fire and revert back to STOCK ROM so I can send it back to Amazon due to touch screen issues, and I've read several forums that say it's an issue with TWRP 2.5 and that I should install 2.3, but I'm not sure how to do this.
Click to expand...
Click to collapse
Use COTR instead flash it using KFU.
Thepooch said:
Use COTR instead flash it using KFU.
Click to expand...
Click to collapse
Thank you but I already bricked my kindle! Looks like it's gonna be my 10th kindle.
carlybelle said:
Thank you but I already bricked my kindle! Looks like it's gonna be my 10th kindle.
Click to expand...
Click to collapse
Nice maybe don`t attempt to modify them
Thepooch said:
Nice maybe don`t attempt to modify them
Click to expand...
Click to collapse
Exactly, I don't think I'll be rooting my new kindle fire...
carlybelle said:
Exactly, I don't think I'll be rooting my new kindle fire...
Click to expand...
Click to collapse
Very likely this go around will not be a first gen device anyway and the second gen. are a bit more complex you can actually permanently brick them. Unlike the first gen device which is nearly almost impossible to permanently brick. I would think every device you bricked was able to be repaired except the last with the touch screen issue. Unless perhaps that was just an indication of a partially corrupted system.
Thepooch said:
Very likely this go around will not be a first gen device anyway and the second gen. are a bit more complex you can actually permanently brick them. Unlike the first gen device which is nearly almost impossible to permanently brick. I would think every device you bricked was able to be repaired except the last with the touch screen issue. Unless perhaps that was just an indication of a partially corrupted system.
Click to expand...
Click to collapse
Of course, I look back on my previous kindles and realize I could have definitely fixed that if only I had the knowledge I had now thanks to guys like you all at xda!
I used kfu to install twrp2.2 but you could replace the twrp2.2 .IMG to a twrp2.3 solved!!!
Sent from my Amazon Kindle Fire using xda app-developers app