Database Develop

[ROM] Adeo v0.2 (REDUX) for Atrix 4G

***MOD EDIT***
THIS ROM ONLY WORKS ON 4.1.26. Please consider another ROM unless you know what you are doing.
History & IntroThe first version was done with 3 different batch files, it ended up being very hacky and even ended up bricking one phone because the cleanup script didn't properly work.
I have rebuilt it from the ground up as a shell script. The initial temp root and file push is done with a batch file, it then fires off the install script on the phone which reports back to the batch with helpful info about what it is doing and what to expect from the phone as it goes. You no longer have to accept any superuser requests either.
The new script has been used on tons of phones now, everything executed exactly as I expected it to. I really didn't want to post this until we had a stock firmware to restore to, after the first release I have been worried about you guys bricking your devices, but what the hell, here it is anyways.
Come chat with us!​FeaturesWorks for rooted and non-rooted devices
Deodexed
Reboot Option
Reboot to Recovery option
Ad Blocking
Removed power options header​ChangelogAdeo v0.2: (3/9/2011)
Added Unknown Sources checkbox
Added Preferred install location (internal, sdcard, let system decide)​Adeo v0.1: (2/28/2011)
Reboot to Recovery option
Ad Blocking
Only remove app/framework Dalvik-Cache (fixes /data app issues)
Removed power options header​Four simple rulesDo NOT do a factory reset if something goes wrong(soft brick), you will lose adb access and have a pretty brick
Do NOT do this if you are not familiar with ADB, if you softbrick you need to use adb to fix it
DO NOT PULL THE BATTERY, EVER WHILE INSTALLING
BE PATIENT​How to Install
Read the four rules above
Read the four rules above, again
Read the four rules above, again, one more time to make sure you've got it
Download the installer (AdeoInstallerv0.1.7z, AdeoUpdaterv0.2.7z)
Hook up your phone via usb with ADB enabled
run INSTALL.bat from the unzipped files
sit back, relax, wait until it reboots (can take upto 5min, be patient!!)
Read the disclaimer below
Enjoy!
DisclaimerIf you brick your device, I cannot be held responsible. Simply restore with the stock SBF to get you phone working again.​Video Walkthru

Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks

A custom ROM?
I'm going to have to buy an Atrix!
EDIT: Bought it!
EDIT2: And Adeo'd it. All UI lag is gone! This is awesome!

I am running this in my Atrix now - I believe my phone was the 4th phone to have this install perfectly on with no issues. Designgears, you are the man, once again! Thank you for this!

PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...

Installed on mine, worked flawlessly. Thanks!

connexion2005 said:
PM sent DG. I cheated an caught link a few minutes early and wanted say thanks! This is running great with no issues and I'm loving the reboot option...
Click to expand...
Click to collapse
Haha, I understand your PM now... you got my file before I posted this.
psufan5 said:
Nice! First basic rom How would someone restore back to stop if you cant do a factory reset? I know on the captivate I had a nice Odin flash to do that.
Thanks
Click to expand...
Click to collapse
the factory reset is only if you brick.
There is no easy way to get back to stock, I will make a thing just like this installer to do that, actually its done, testing it

designgears said:
Haha, I understand your PM now... you got my file before I posted this.
the factory reset is only if you brick.
Click to expand...
Click to collapse
So if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because Im still debating if I want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but I also need to test out custom mods before my decision.
Thanks man.

I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!

psufan5 said:
so if all else fails, the factory reset will bring it back to out of the box shape? Just concerned because im still debating if i want to keep the phone before my 30 days is up etc. Id like to return it as stock obviously, but i also need to test out custom mods before my decision.
Thanks man.
Click to expand...
Click to collapse
no no no, do not factory reset if it bricks!!! Read the op!!!!

shawnbuck said:
I am curious, what changes were made for the reboot mod?
Also, thanks for the rom!
Click to expand...
Click to collapse
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk

I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.

psufan5 said:
I saw the no factory reset posts lol... I was just curious what can be done to return the phone back to stock once this is all done with.
Thanks.
Click to expand...
Click to collapse
I designed this script to handle payloads, just need to package up one with a new payload with stock files and upload it.

Installed... Removed Laggyness i was getting with blur UI.
as to refering to the blur UI....
this is my second Atrix.. had to bring my first one back because when i was on tier 3 support the other night they fried the sim card reader with an update which was killing data signal to my phone... that phone had no laggyness whats so ever at all. I got this one today out of the box was having laggyness and slow response to key presses.. this fixed that as of so far.

designgears said:
smali edits in the framework.jar, android.policy.jar and added an image and sting to framework-res.apk
Click to expand...
Click to collapse
Nice, I will give this shot. Although I am already running DeOdexed already but I figured may be you got it running better than mine
I am also going to start editing small things like animations. No sense oh having all this power without some eye candy

Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!

Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.

uskr said:
Hello designgears,
Did you re-signed the apks? If so, could you share the key files you used? The reason I ask for it, it's because I am playing around with the /system/app apks and was getting errors like:
"Package com.motorola.blur.home has no signatures that match those in shared user"
Awesome job, btw!
Click to expand...
Click to collapse
Not sure, I didn't get an errors like that.
airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Try a usb port on the back of your PC

airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Download ADB Wireless from the Market. It'll help solve that one for you.

airbillion said:
Stupid question. How do I hook up the phone with adb enabled? When I run the bat file it says error: device offline, but in my devices I see ADB interface Mot Composite ADB interface.
Click to expand...
Click to collapse
Install the Android SDK
install the MOTO drivers it will also install the moto adb drivers with it.
Install the ADB function drivers into the SDK/tools folder
run...cd to the sdk/tools folder... run... adb devices
should show the device is up which means ADB is enabled

Lenovo Ideapad K1 One-Click Root (Mostly)

First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Second, I take no credit for anything here except for writing the .bat file here used to do the work, as well as assembling the files as per the original post.
All credit goes to djmwj and his article found here:
http://rootzwiki.com/topic/8722-lenovo-ideapad-k1-rooting-guide-messy/
As the title states, it was very messy. The OP figured out how to make it go, but it was a bit fuzzy to follow. So, I thought I'd help folks out a bit and clean things up.
So, I took the instructions presented in the OP, and condensed them into one download with one .bat that does everything from start to finish, minus installing the respective drivers for ADB and NVFlash. However, the drivers are included in the download.
Instructions:
1. Extract K1Root.rar to the directory of your choosing.
2. Connect your tablet to your PC with the USB cable.
3. With your tablet off, press POWER+VOL_UP+VOL_DOWN until the screen turns on, but displays only black.
4. Windows should detect the device, but not install drivers.
5. Go into device manager, select the APX device, choose update drivers, and install the drivers from the aptly named NVFlash_Drivers folder.
6. Open up the NVFLASH_HOME folder and run the file K1Flash.bat
7. Make your desired choices when prompted, and enjoy.
Notes (PLEASE READ BEFORE USING):
THERE MAY BE BUGS! I used it on my own stuff before releasing, and all of the essential components work as they should, however, there may possibly be a minor hiccup somewhere in the script. This should not damage anything. If you have doubts, you're welcome to examine the .bat and check it for yourself.
Please be gentle. I am not a full-time developer. I just wrote this to help make the process simpler for people.
The OP suggests you download and read the partition table, and then name the backup files based on that. This script names the backup files based on the flash.cfg script referenced in the OP, which is what controls the flashes used anyway. So, there shouldn't be any irregularities, however, I can't speak for every device on the planet.
This does NOT use the latest OTA updates. The rooted files being flashed are the default ones from the original download. You can easily adapt this to any files generated from the latest OTA files by simply dropping them in the NVFLASH_HOME file.
To install the SU properly, you have to install ADB drivers midway through the script. There's probably a way around this, but I didn't find it to be too inconvenient.
The ADB drivers are also located in the NVFLASH_HOME folder. Just do like you did when installing drivers in step #5, but instead point to NVFLASH_HOME.
Um...um...
That should be it. Obviously, use at your own risk. Let me know if there are problems with the script, and I will fix them.
Oh, and party on, Wayne.
http://www.megaupload.com/?d=AG10XE25
EDIT:
Attached is an updated .bat file which fixes a few errors in the original script, plus adds more userability. Just extract to the NVFLASH_HOME folder and run.

digitalhigh said:
First, please forgive me if this is posted in the wrong section. It seemed most appropriate.
Click to expand...
Click to collapse
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.

gallahad2000 said:
You may want to change the title to Ideapad K1, I don't know if this will work for the Thinkpad tablet.
Thanks for this, I just picked up this tablet ($250 at staples) and was worrying about having to tackle linux and "compiling" just to be able to get hulu.com working. You're a lifesaver.
Click to expand...
Click to collapse
Wow. Yeah, I'm pretty sure the key used is just for the Ideapad. Thanks for pointing that out. My dumb a$$ must've blanked out and just used the group name when posting.
And just to be fair, the original poster does include everything needed to do stuff in windows as well - it's just very hard to discern from the post.

question
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.

jfkerekes said:
Is anyone working on a custom ROM for this tablet? I am hopeing that there will be at least a few custom roms available at some point in the near future.
Click to expand...
Click to collapse
We need to be able to root and unlock the bootloader first.

Does the root method work on the 121211 update?
Or is there a way to flash back to the older firmware?

the OTA update 12 12 11.... seems to be update.zip style with no .img files inside. just loose files like normal rom updates. doesnt seeem like you can drop the files in as suggested. or i have the wrong OTA....
oh and is this for LINUX as the OP or work in windows too??

Hi, I was wondering, is this procedure works for the Lenovo ThinkPad 1838-25U? I'm thinking to buy it to give a test ride, i sold my Transformer 101 to buy the Prime but it seems like Asus is taking vacations on the delivery shipments. Is this a good tablet? or is better to wait for another version?

READ THE POST
IDEApad not THINKpad. no it wont work.

First of all- thank you so much for creating this script! I have been putting off rooting this device due to the "messy" nature of the original post.
I was hoping you could help me troubleshoot, I have tried both the new K1 root application and the original .bat file. I know the drivers are working because the script makes it as far as creating and formatting partitions and successfully pushes the bootlooder.bin but then:
bootloader.bin sent successfully
file not found: recovery.img
failed executing command 2147483647 NvError 0x4
command failure: create failed
I've tried everything I can think of... any ideas?
Thanks again.

I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?

taiz said:
I found problem.
after root done follow step. I cannot factory reset and update any ota.
anyone can help me ?
Click to expand...
Click to collapse
Yes you have to roll-back to 04 stock and then apply the OTA's

Backup of the stock lenovo .apks!
File 1:http://www.mediafire.com/?r7iskr3wrfx4u01
File 2:http://www.mediafire.com/?fymdv9e9kmj332s
File 3:http://www.mediafire.com/?w33k205ej4fpbcl
A big thanks to Khanning who was nice enough to walk me through the adb commands and bear with me when I couldn't get adb over usb to work.

This may fix your issues http://forum.xda-developers.com/showpost.php?p=21309379&postcount=50

Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Can someone help I used this and I installed drivers from the drivers folder fine ....I ran option 1 fine and it said completed but said something about nvflash error make sure drivers are installed ....but on my tablet it said phone update success ....when I try option three to flash image it just stays at nvflash started and goes no further and when I try to install Su it won't connect adb , probably cause adb drivers wouldnt install ....any advice ....device is booting and seems stock ....it did not wipe my files either
Sent from my HTC EVO 3D X515a using XDA App
Click to expand...
Click to collapse
It means you are not in APX mode. Read the PDF and follow the instructions for installing the APX drivers. This should fix your issues.http://forum.xda-developers.com/show...9&postcount=50

I just completed step 3 flashing the image went fine up to bootloader .bin sent successfully ...then it says
File not found recovery.img
Failed executing command 2147473647 Nverror 0x4
Command failure : create failed
Edit the link u posted is not working and the drivers are installed
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Sent from my HTC EVO 3D X515a using XDA App

maek_it_happen said:
Edit 2 I just downloaded ur v2 root tool in ur other thread ....for some reason ur flash me Command actualy went past the recovery img error I was having with this tool .... But yours is flawless
Click to expand...
Click to collapse
Glad to hear it worked for you.
TD

I recently got this device and looking for a way to root this device without having to roll back to the factory default rom and then having to update again using OTA.
Question, am I in luck, is that at all possible or do I have to really rollback and reinstall everything again?
Thanks!
Sent from my K1 using Tapatalk

Anyone have the root? Megaupload is down forever.

[Q]Bricked Kindle fire HD 7"on TWRP

Hi everyone, today i would like to ask for your help with a pretty big problem i have with my Kindle fire HD, you see, i was updating from my current rom 7.4.4 to CM 10.2. to achieve thi i followed this tutorial http://forum.xda-developers.com/showthread.php?t=2271909 , everything was going fine until i installed 2nd-Bootloader and TWRP recovery. The problem came up here, when i realized that i forgot to move the rom and the files for google play into the SD card, now whenever i try to do this i can't seem to get my PC to recognize the Kindle with TWRP (i can browse my files and such with TWRP directly through the kindle itself) i tried to move the required file with adb and fastboot but i can't get it to work.
The kindle is rooted and running version 7.4.6 from amazon.
i have a backup for the rom and the files but i can't use fastboot.
i have a backup for each of the following files: boot0block, stock-boot, stock-recovery, stock-system
all the adb drivers and sdk are functioning perfectly.
When i connect it to my PC with windows 7 i can see the kindle recognized by the device manager but it has yellow triangle next to the icon.
i also tried using an otg cable but the kindke did not recognize it.
any and all help is appreciated, i don't want my tablet to die Dx

I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<

Ph0enix_216 said:
I've never had to do this, but in TWRP, if you go to "Advanced," there's a button labeled "ADB Sideload." Then you should be able to use ADB to sideload files onto your Kindle using the "adb sideload" command.
Example:
Code:
adb sideload name of.zip
Hope this helped
>>Sent from my homebuilt TARDIS running Android 4.3... or maybe it's a rooted Kindle Fire HD running ChameleonOS<<
Click to expand...
Click to collapse
I tried this but the problem is that the pc not find device , it show me in device manager yellow triangle next to the icon of kindle
When i send a adb command , the adb say "Device not found"
Thanks you anyway!

Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9

stunts513 said:
Try updating the device driver for the device with mark next to it, use these drivers from this post, they should work. http://forum.xda-developers.com/showpost.php?p=44446906&postcount=9
Click to expand...
Click to collapse
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file

Shur'tugal said:
Hi and thanks for your help now i try send the next command adb push file.zip /sdcard
but adb say this menssage:
C:\Users\Cristian>adb push file.zip /sdcard
cannot stat 'file.zip': No such file or directory
I put a rom in C:\adt-bundle-windows-x86_64-20130729\sdk\platform-tools in the same folder that adb.exe
and the name of the rom file is : file
Click to expand...
Click to collapse
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Ok if u want to simply type file.zip u need to be CD's into the directory of where u put the ROM, but as it seems u have the SDK in your paths simply putting the ROM in c:\users\cristian should suffice. Try moving the ROM there and running the command again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for your help your save my tablet
Thanks you very much
Finally i exit for this bricked
Enviado desde mi GT-I9300 usando Tapatalk 4

I have a dude im install CM 10.2 perfect , but i dont remember install de google apps as i have to do now?
Thanks

One step further
My apologies for hijacking this thread. I had made the same error as the OP. however, instead of searching here for solution, I panicked and wiped the cache and user data using the SR tool and wiped everything. Now unfortunately my kfhd tells me it can't boot, which my incompetent mind tells me is likely because I have no rom?
I've tried to use first aide to do a system recovery but I get told the files are too large and it can't do anything.... Any suggestions or thoughts from people? Appreciate any help I can get. Been up late the last 3 days trying to sort this out, while I thought I was going to provide m wife with a slick android device!!

That's odd, I wouldn't think wipe your data partition and cache would cause that to happen, then again there are some files stored under data the system uses out side of apk's so I guess that could be why. Did you get your kindle into fastboot? If you did I would suggest trying to use kfhd system restore tool if kffa didn't work.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.

deeman77 said:
Yes, can fast boot. Shows up when I plug in the factory cable. When I use the system restore tool, and try and do a basic recovery, it can't copy the images over as it says the files are too big.
Click to expand...
Click to collapse
All the files, or just the system.img?

soupmagnet said:
All the files, or just the system.img?
Click to expand...
Click to collapse
each one of them unfort.

Do you have twrp installed?

hloomsc some
soupmagnet said:
Do you have twrp installed?
Click to expand...
Click to collapse
I did. Not sure i do now post trying to do a wipe. Don't see any blue when I start up, just the original kindle letter coloring, after which I get a message saying it can't boot

any suggestions anyone or is my kfhd pretty much killed? there's got to be a way to load some rom on to it!!

You should be able to load the original images over fastboot, something just isn't working right. I would say its far from hard bricked, it should still be fixable, its just a matter of troubleshooting it. If you have the kindle fire system image I would try manually flashing it but you need to know what you are doing. If you CD into the SRT folder where im assuming the IMG files are in the same folder as fastboot, try running "fastboot -i 0x1949 flash system system.img" think I got the syntax right, haven't had to ever use fastboot myself, anyways if you run that what does it report back? Hopefully not the same error, or it might be something messed up with the image.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

thanks for the advice. ended up re downloading the images again and this time it worked. go figure.
back to starting again to get my custom rom on.
once i have a custom rom, guessing there are no amazon bits left in there that would cause any updates to come through right?

Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Thank god there isn't, I would scream if there was, just make sure to wipe system, cache, dalvik cache and do a factory reset when coming from amazon to cm based ROMs.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Good afternoon: I bricked a nice 8.9 tablet several weeks ago using ADB sideload...
I used ADB Sideload to install Gapps since I was already in TWRP and was too lazy to reboot and transfer the gapps.zip file to my tablet.
The sideload installed the gapps.zip as I expected it to and I was brought back to the main TWRP screen.
When I clicked on reboot/reboot system, the tablet started flashing the three partitions (boot, recovery and system) as I was watching. TWRP then left me at the booting screen doing nothing. I did not know why the tablet decided to flash the three main partitions but, I opted to push the power button and that was the last time I saw my tablet.....
Apparently ADB sideload is only for ROM's? I had only used it to flash ROMs prior but, I thought ADB Sideload should be able to install any properly zipped file designed to flash with TWRP?
Regards

[SOLVED] Some Help please? A Strange Brick...

So last night, I was beta testing a ROM. After playing with it for a while, decided to go back to my previous setup and work on something. I rebooted into TWRP, wiped my Dalvik Cache, data, cache, and system partitions, and tried to flash the nandroid of Kinology I had been running before testing the beta ROM. I rebooted... only to discover that my Kindle wouldn't boot past the 2nd bootloader.
I thought, "okay, no biggie, I can fix this. I tried wiping and then flashing a couple of other ROMs I had on my SD card. Didn't work. I rebooted the bootloader and flashed a trio of images I had on my hard drive via fastboot. Nope. I tried sideloading CM10.2. Still nope. I tried mounting USB and pushing a ROM to my SD card and flashing from there. Again, no (anyone noticing a pattern?).
No matter what I do, I can't flash anything or get anything to transfer over to my device.
Help!!

Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
Why do I get the feeling this has something to do with the boot image... Does it ever boot to the point you can logcat? Also I thought I read about some issues restoring nandroid's after the system was using selinux, though I haven't experienced this with mine. You tried cm 11? I know it had full selinux support. If you can't get the logcat to work I think there's a module that gets dumped that you can access in twrp over adb. And of all things to ask, if you flash the ROM in testing back does it still boot? If so that would make me think something weird is going on with the boot image. Also what version of twrp are you using?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for answering. "adb logcat" doesn't work. It only shows "-waiting for device-". I tried flashing CM11 this morning, but the install failed. I also tried re-flashing your ROM again this morning, but same result. I've got TWRP 2.6.0.0. I've been meaning to flash the latest one from @Hashcode, but it slips my mind every time I think of it.
Something weird: whenever I push anything to the device over ADB, I push it to the SD card. But when I run "ls /sdcard/" in ADB shell, there's nothing there (even though it says it has been successfully pushed).
EDIT: Okay, I flashed the latest version of TWRP (2.6.3.1). I flashed CM11, and it reported that the flash was sucessful. But when I rebooted... nope.

This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Ph0enix_216 said:
No matter what I do, I can't flash anything or get anything to transfer over to my device. Help!!
Click to expand...
Click to collapse
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.

stunts513 said:
This is weird... So weird. I'm almost at a loss, have you tried flashing a boot.IMG via fastboot corresponding with whatever ROM you flashed? I know I keep saying I think it's this without any real proof but this is kinda bizarre and if no ROM's are working and all you see is the kindkle logo I would assume that the init.RC scripts never got passed the pvrsrvinit or somewhere around that, possibly even before that since adb isn't working when the device is on the logo. You using adb from windows or Linux?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
The init.RC scripts are still there, no matter how much I wipe in TWRP. I can see them using TWRPs file explorer. I haven't tried flashing the boot.img, I will try that. As for ADB, I'm using it on Windows 8, of all things.

LinearEquation said:
After I read this, I decided to try and restore and everything restored just fine *whew*. What I do know is that when ever this situation has come up (and a few people have stated they had this problem) only a complete factory restore fixed the problem. You're gonna have to break out the fastboot cord.
Click to expand...
Click to collapse
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?

UPDATE
Okay, I tried re-installing CM10.2, and then flashing the boot.img from it via fastboot. Still no dice.
Is there any hope of recovering from this? It's been longer than a year, so I don't think Amazon will simply switch it out under warranty.

Agh, I was going to ask hashcode about it on the irc earlier and I forgot about it because my friend asked me to fix his pc...
Also remind me to slap this phone's spell check. It took me way longer to write the previous statement than it should have.
Edit: he's still in there but I think he's afk right now.
Sent from my LG-P769 using xda app-developers app

Ph0enix_216 said:
As I said before, I tried flashing two different sets of images via fastboot. Thanks for the response though. What all did you do in your restore process?
Click to expand...
Click to collapse
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
---------- Post added at 04:18 AM ---------- Previous post was at 04:14 AM ----------
LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was gonna suggest to flash CM10.2 first and then move up to CM11 because that was the route those with this problem had to go (4.3 then 4.4.) Restoring CM11 right off the bat did not seem to work for some reason. That's why I keep a 4.3 nandroid in TWRP, for just such a case. But I see you tried that.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

LinearEquation said:
I just wiped and then restore 4.3 PA nandroid. That was another thin I forgot to mention.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That's weird, because I wiped then tried to restore my Kinology nandroid. Am I looking at an irreparable brick, or do I want to look into investing in a new tablet?

Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app

stunts513 said:
Wait until Monday, think you might get more info on a weekday... I have a theory of something that might fix your kindle but it could potentially hard brick it as well so I don't want to explain it yet until it's a last resort.
Edit: just talked to hashcode, he says to "adb pull /sdcard/ ." your sdcard and wipe internal storage, he also said because of kinology kernel not having selinux that if you want to use it you will have to downgrade twrp first and wipe everything again, you might find it easier to do it after flashing cm11 first. So basically back up the sdcard and wipe everything, check off everything including internal storage then push a Rom and flash it.
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Checked everything. Wiped it all. Pushed a ROM via ADB. Not working.
I did some exploring with TWRP's built in file explorer. Despite wiping internal storage, I can still see some things I had on there previously. At the root of my device, however, I can also see this:
Code:
boot
cache
data
dev
efs
etc
license
proc
recovery
res
root
sbin
sdcard
supersu
sys
system
tmp
vendor
default.prop
file_contevts
fstab.bowser
fstab.goldfish
init
init.rc
property_contexts
seapp contexts
sepolicy
ueventd.bowser.rc
ueventd.goldfish.rc
ueventd.rc
I may be mistaken, but isn't that some of Firefox OS's stuff? The init.rc files you were talking about? It all may just mean nothing. Also, all my SD contents seem to be preserved in "/data/media/". I tried flashing CM11 from there as well. The flash was successful, but at boot... nada.
Still, thank you all for trying

Umm sorry I'm a little late to the party... Or funeral(if we cant fix your kindle) I was testing stunt's FireFox OS too and after testing I flashed back to my CM11 back up just fine, why not use the system image restore tool in the development section (minimize error, the tool is 99.9% fool proof) bailed me out multiple times when I thought my kindle was a goner(i know you manually flashed images. But why not try a tool?), and I have a theory... Stunt PMd me instructions on how to get the kindle to pick up/read the SD card I didn't try implementing the code because I'm not that techy but did you try it? What if the solution messed with your internal SD card since Firefox OS and Android Have their differences? Or something went wrong will modifying the commands stunts gave you?
And no...I'm not trying to insult Stunt's work or defame it, nothing is perfect and anything is possible so sorry if my response seems a bit disrespectful to the devs work.
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app

I still think this has something to do with selinux... I would know more if you had a serial hookup to the kindles motherboard but I don't even have that, if I had some kernel output it would be useful... Those files you saw that I mentioned aren't Firefox OS specific, they are Linux specific, they are going to always appear there because they are loaded from the initial ram disk in the boot.IMG, since android uses a Linux kernel you have init.rc files and such. Some of those directories are from recovery, the folders that should know appear empty I think are /data, /cache, /system and I can't remember the rest offhand. I will have to ask hashcode about this more tomorrow. I can think of something you might do from fastboot that might fix this but I don't know the specifics and it might wipe the boot loader, which wouldn't necessarily be bad as long as you reflash it before rebooting, but I'd like to avoid my idea because it seems rather risky, anyways I will ask about this tomorrow, so don't look into my concept idea....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?

stunts513 said:
when you said your sdcard contents are preserved, did you mean even after wiping internal storage that the sdcard's contents were still there?
Click to expand...
Click to collapse
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<

Ph0enix_216 said:
Correct. Not only are they still there, but I can't seem to add anything to it. Pushing via ADB is successful on the PC end, but if I check the SD card, no change. Also, everything I had before the brick on my SD card is still in "/data/app", if that tells you anything.
Thanks for taking time to they and help me
>>>Sent from my ZTE Valet Z665C<<<
Click to expand...
Click to collapse
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.

SUCESS!!!
stunts513 said:
ok um at this point hashcoed is helping me out and i tink i can fix it but it will be easier if i can msg you on skype or in the irc, whatever works best for ya, because this will involve some trial an error over an adb shell... i would try it on my own but it will involve me backing up quite a bit of data and you already have done that so i thought this might be easier than me formatting my own in the process...
Edit: Ok actaully try this first and see what happens, boot into recovery and run this in an adb shell
Code:
umount /data
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
that should actually format the userdata partition and hopefully fix this. though make sure that the unmount worked first, you don't want to try to format a partition while its mounted.
2nd edit:actually i'm a moron, you don't even need to umount /data, just uncheck it in the mount section, you can tell i'm way to used to normal linux... always a good idea to run mount and double check its not on the list but it shouldn't be.
Click to expand...
Click to collapse
SUCESS!!! I did what you said and formated the data partition, and I was able to successfully push CM11 to my Kindle. I flashed it, it reported the flash as successful, and I rebooted.. I was greeted by new CM11 boot animation (right now, it's one of the most beautiful things I've ever seen.
Thank you to everyone who responded to this thread. It's nice to know that there are people nice enough out there to take the time and help someone in need.
Some questions though:
1.) With this SELinux or whatever, can I still switch ROMs as easily as I did before? Or am I now limited to CM11 and such?
2.) What exactly happened? I've never had this happen before, where my /data partition derped out and TWRP wouldn't flash anything.

I'm not to familiar with how selinux works but from we hat I remember I think it was something like this. You had a recovery that I think may have supported selinux but I'm not positive about that. The kinology ROM you had on there had no selinux support in the kernel. My ROM has some selinux support in it since I based it on 4.3, and I have no idea what happened that messed it up after that, all I can tell based on what you had to do to fix it is that the xattributes for selinux were not getting cleared off the partition and for some reason the ROM's that could handle selinux didn't seem to like it either. If you want to run kinology again you may need to downgrade twrp so you can reformat the partition again so it reformats without selinux but I'm a bit confused on this myself, this isn't my best field in computers.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

[Q] changing custom ROM

Hello everyone....
I have a kindle fire HD 7" 7.4.6
I rooted and added TWRP with 7.2.3 bootloader
I installed CM11 Kitkat the ROM is a bit buggy but nice.
I tried to go from kitkat to kinology which allows use of Amazon and Google services.
But flashing failed.... I can't seem to get kinology to work.
This is the set of walkthroughs I used.
To root & add TWRP. I used a rootjunkie YouTube video ( can't post link)
To install cm 11:
also a rootjunkie video
knowing this, I tried installing kinology using this walkthrough:
Original kinology page.
No luck, does anyone know how I can move my system to kinology?
please help,
Thanks to all in advance

OK, 2 things, one you didn't mention if you factory reset when trying to goto kinology and I believe that is a must. Second, you are probably going to have to wipe internal storage with a command from an adb shell to clear the xattrb's from the data partition that cm 11 has set as last I checked kinology uses a stock amazon kernel or something close to Amazon's kernel, and ipamazon,s kernel didn't support selinux so it presents problems going back and forth between those 2 ROMs. BTW wiping internal storage means anything on your sdcard goes bye bye. I will have to go grab the command you will more than likely need to run so gimme a moment.
Edit: I'm lazy tonight, here is a link to a post I made with the commands to run in it: http://forum.xda-developers.com/showthread.php?p=49408371
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
OK, 2 things, one you didn't mention if you factory reset when trying to goto kinology and I believe that is a must. Second, you are probably going to have to wipe internal storage with a command from an adb shell to clear the xattrb's from the data partition that cm 11 has set as last I checked kinology uses a stock amazon kernel or something close to Amazon's kernel, and ipamazon,s kernel didn't support selinux so it presents problems going back and forth between those 2 ROMs. BTW wiping internal storage means anything on your sdcard goes bye bye. I will have to go grab the command you will more than likely need to run so gimme a moment.
Edit: I'm lazy tonight, here is a link to a post I made with the commands to run in it: http://forum.xda-developers.com/showthread.php?p=49408371
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok first, thanks for the reply. Second, yes i did do a wipe before the install.
I am going to go check out your link now and see.... ill keep you posted.
Thanks again....

Quick question.... can the process in your thread be done through fire flash 11? ( i am an absolute noob at this, so it may be a silly question...)
i can follow along as to what must be done, but i dont feel comfortable doing a process without a guide.....do you know of any threads with a walk through for this?

There aren't any tutorials for this as far as I know, I got this command from Hashcode in the irc, just run the command mentioned above from a command prompt (while in recovery) while cd'd into a utility that came with a copy of adb, like my wallpaper fix for example that's in my signature. If you don't know anything of command prompt like what CD commands normally I would say read up on basic command prompt because its very simple, but because of a nice trick I remembered recently you can avoid the CD command, just shift + right click the folder with adb in it and hit "open command prompt here", then run the command I posted (while in recovery).
Sent from my Amazon Kindle Fire HD using Tapatalk