my kindle fire hd/ tate only seems to install omnirom, whenever i try to install cm or paranoid android, it never gets past the boot up screen. Can anybody help? Has anyone else had this issue? i have twrp 2.6.3.1, i have done a factory reset, factory reset and system wipe, wiped dalvik cache after the install, didnt wipe after the install, so many combinations, thinking it would solve the issue, but nothing. omnirom on the other hand installs perfectly? the only reason i want Paranoid android is because it has tap to wake and my kindle has no power button at all, and the volume buttons work.. but its annoying to press them because they have to be pressed with something small like a pencil point. also paranoid android is my favorite rom from all the devs out there. please help if possible thanks.
Which logo did it loop at? I'm guessing selinux related but I don't know for sure, might have to format the internal storage but that's a last resort.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Which logo did it loop at? I'm guessing selinux related but I don't know for sure, might have to format the internal storage but that's a last resort.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
it gets stuck on the pa boot up screen. 4 colors come from the sides and merge together then they turn into the pa eye from the dpi changer thing lol thats as best as i can say haha. i know it doesnt freeze because its constantly moving. I never knew wiping internal storage could help? can it really solve the issue? i would be glad to do it if it really does help. and thank you for replying!
Well it could but I don't have a vast understanding of she Linux so it might not help but I this k its one of the solutions to the problem. Someone flashed a pre-alpha ROM I am working on that was cm 10.2 based, so it had some selinux support and after trying to flash any ROM on the device after testing it it did something similar u til we had tomdomsomething a bit different involving him running a command to actually reformat the /data partition which is similar to what a internal storage wipe does, but I thought he wasn't able to even get to the animated logo, I'll have to ask him. If you want to try a internal storage wipe I'd suggest backing up the sdcard so you don't lose your data, run something like "adb pull /sdcard/ /backup/" from recovery or just flash back to previous os temporarily.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Well it could but I don't have a vast understanding of she Linux so it might not help but I this k its one of the solutions to the problem. Someone flashed a pre-alpha ROM I am working on that was cm 10.2 based, so it had some selinux support and after trying to flash any ROM on the device after testing it it did something similar u til we had tomdomsomething a bit different involving him running a command to actually reformat the /data partition which is similar to what a internal storage wipe does, but I thought he wasn't able to even get to the animated logo, I'll have to ask him. If you want to try a internal storage wipe I'd suggest backing up the sdcard so you don't lose your data, run something like "adb pull /sdcard/ /backup/" from recovery or just flash back to previous os temporarily.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I assume you're talking about me. Nope, never was able to get past the 2nd bootloader until formatting the data partition. After that, flashing ROMs was no problem at all. You have to format it (backup your SD card over ADB first), mount the system and data partitions, and run the command. After that, flashing should be no problem at all.
EDIT: This was the command:
Code:
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
So I did an internal storage wipe and it didn't help at all... I'm still stuck in the boot up animation for the ROM for Any aosp ROM except for omnirom. Am I the only one with this issue? Should I use the recovery image tool to go back to amazon os and redo everything? I love paranoid android, and I especially love/ need Double tap to wake because the power button is broken.
Try running Ph0enix_216's command from an adb shell while in recovery.
Sent from my Amazon Kindle Fire HD using Tapatalk
Ph0enix_216 said:
I assume you're talking about me. Nope, never was able to get past the 2nd bootloader until formatting the data partition. After that, flashing ROMs was no problem at all. You have to format it (backup your SD card over ADB first), mount the system and data partitions, and run the command. After that, flashing should be no problem at all.
EDIT: This was the command:
Code:
mke2fs -T ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/userdata
Click to expand...
Click to collapse
Does it matter whether I can access the SD card in recovery? When I plug in the device, my computer notices its connected but when I mount it, I can't access these card. I'm wondering whether the command will be useless if this is the case? I can mount the device normally on omnirom no problem, in twrp I can't mount it. I'm going to do this tomorrow, just wanted to ask before I have more trouble haha.
The sdcard isn't mountable from twrp, the feature is broken for some reason. Everyone has to rely on "adb push" to actually transfer files to the device when in twrp because of this.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
The sdcard isn't mountable from twrp, the feature is broken for some reason. Everyone has to rely on "adb push" to actually transfer files to the device when in twrp because of this.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
so i tried the command he gave me and it says,
'mke2fs' is not recognized as an internal or external command,
operable program or batch file.
i have done multiple sideloads for roms on this, so i dont think its an adb issue.
You have to run it from a adb shell, in the command prompt run "adb shell" then run that command, make sure you are in recovery when you do this.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You have to run it from a adb shell, in the command prompt run "adb shell" then run that command, make sure you are in recovery when you do this.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I just wiped the internal storage using the system restore image thing. It worked! I'm running IOAP or something like that. Turns out PA is really laggy haha. Luckily IOAP has double tap to wake as well. Thank you
Related
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
I have a Kindle Fire HD 7" system version 7.4.3 that has the proverbial "Red Triangle" of death.
This unit has not been rooted and I am very much a newbie.
I have rebooted the unit many times. Periodically it will work and then lock up again with the Red Triangle.
90% of the time I no longer have wireless access as this has been disabled with the error.
After reading many of the posts here, I have considered rooting it to a) back up my system files (including email) and b) reloading the software. However, if I am not mistaken, I need to load an ADB file. Since the "Enable ADB" under Security Settings is on OFF and cannot be turned on, is there any way that I can revive this unit?
What I would really like is to back up those hidden system files that include email files, program data, etc. as well as make this work like it used to.
Can any one help me?
Without adb on you can't do much, you could just reflash the system image from fastboot, but you would probably need a fastboot cable since u don't have adb or root access. On the bright side a system reflash only reflashes the system partition, you won't lose any of the data for any of the apps. It also is prerooted, so you don't have to worry about doing that later. There's a tool that does the work for you in the android development section called kindle fire system restore tool. You will still need a fastboot viable to run this tool though. Also I haven't looked into it but I thought the red triangle thing was a kf2 error, but maybe I am mistaken?
Edit: I'm a moron, red triangle is the useless stock recovery on the kindle. Least thats my best guess.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Without adb on you can't do much, you could just reflash the system image from fastboot, but you would probably need a fastboot cable since u don't have adb or root access. On the bright side a system reflash only reflashes the system partition, you won't lose any of the data for any of the apps. It also is prerooted, so you don't have to worry about doing that later. There's a tool that does the work for you in the android development section called kindle fire system restore tool. You will still need a fastboot viable to run this tool though. Also I haven't looked into it but I thought the red triangle thing was a kf2 error, but maybe I am mistaken?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I do have a factory cable (same as fastboot cable?) from SkOrPn, but will have to look through the forum for how to do a system reflash. I am glad to know that I have an option to save all of my data.
Unfortunately the red triangle is not limited to the kf2, but don't I wish it was.
Thank you.
Try this: http://forum.xda-developers.com/showthread.php?t=1951254
If that doesn't work try kffa in the general 7" forum.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Since I am such a newbie, I have a couple of questions:
1) Can I assume that the "KFHD_SRT_v1.3.5- 7.3.0 (separate option for restoring factory recovery)" would be the option that I should use for my KFHD running system version 7.4.3? If I read thru this correctly, it will reset the system back to 7.3.0 and then auto update to 7.4.3 once connected to the internet. Is that correct?
2) If so, step 2 says to enter a command if your device recognizes ADB. Will this work on my device since the ADB option is turned off?
Thank you again for walking me through this process. [And by the way, you are not a moron. ]
Step 2 is misleading, you only need that command if you don't have a fastboot cable. I personally haven't had to use this tool, but from what I know it kinda downgrades the system but it should update on its own which also unroots it. And yes the download you were talking about it should be the right one.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
After downloading the KFHD System Recovery Tool (that took a long while) and installing the driver for my KFHD, I am now running the SRT batch file. I am afraid that I am a bit confused here. The batch file gives you the following 7 choices:
1) Restore-Factory Rooted with SuperSU.apk
2) Restore-Factory Rooted with SuperSU.apk, Apex Launcher, and PlayStore
3) Restore-Factory Recovery
4) Erase cache & userdata
5) Check fastboot status
6) Reboot normally (must have a standard cable connected to work)
0) Exit
According to the instructions, I am to select #4 and Erase cache & userdata. Won't this erase my hidden system data (i.e., program data, email, etc.)?
Please advise before I take the next step.
I would use option 1 or 2, idk y it says to use 4.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I would use option 1 or 2, idk y it says to use 4.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay, my KFHD is in Fastboot mode (or at least that is what is displayed on it's screen).
However, my PC found new hardware - Tate-PVT-08 and needs the driver for it. Do you know where I can find this driver?
The SRT Tool is stuck in "trying to locate device" in the interim.
UGH, I am so close and yet so far away.
Just FYI, I had to go way back to remember CMD line instructions, but I also tried typing in the "fastboot -i 0x1949 flash boot boot.img" command. This generated an error message of "fastboot is not recognized as an internal or external command, operable program or batch file."
pi lady said:
Okay, my KFHD is in Fastboot mode (or at least that is what is displayed on it's screen).
However, my PC found new hardware - Tate-PVT-08 and needs the driver for it. Do you know where I can find this driver?
The SRT Tool is stuck in "trying to locate device" in the interim.
UGH, I am so close and yet so far away.
Just FYI, I had to go way back to remember CMD line instructions, but I also tried typing in the "fastboot -i 0x1949 flash boot boot.img" command. This generated an error message of "fastboot is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
Oops, now I am the moron.
I was in the wrong folder/directory. However, when I moved to the KFHD_SRTv.1.3.5 folder and entered this command, the new error message is "cannot load 'boot.img' - so what gives?
I have no idea, usually if someone gets stuck with this app I recommend using kindle fire first aid, it can do the same thing and probably has a better rep. I just prefer individual apps so I recommended this. http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I have no idea, usually if someone gets stuck with this app I recommend using kindle fire first aid, it can do the same thing and probably has a better rep. I just prefer individual apps so I recommended this. http://forum.xda-developers.com/showthread.php?t=2096888
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay I have my KFHD temporarily back up again. It is more functional than it was, but not all applications are running yet.
I haven't tried the KF First Aid yet, but will. I have downloaded the zip file and extracted the files so that I will be ready. Not sure yet if I have to upgrade my Java (it is SE v7up25, but not the developer version).
However, before I proceed much further, I really want to back up my KFHD.
- My data has been "backed up" by making a copy via a USB cable and Windows Explorer to my flash drive.
- What is left to back up is the hidden section/partition of my KFHD. All the postings I have seen so far discuss backing up the system (OS) of the KFHD, but what about the area where applications store user profiles and/or data. For example, the email program stores all the email data in this hidden area. How can I get that backed up?
Once this is accomplished, I would feel much more comfortable in running the KFFA as well as the replacement of image files.
Any clues?
If u can find the email app's internal name you are using then goto "/data/com.emailappname" and copy that folder, usually that's where a program stores its data, not positive about that on the kindle is though, last time cleared my cache and dalvik cache on that os, I had to reset up my email account so I don't know for sure if that's correct exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Try this dude
https://www.youtube.com/watch?v=k-8lTMLCGfE&feature=youtube_gdata_player
Sent from my SGH-T989 using Tapatalk 2
stunts513 said:
If u can find the email app's internal name you are using then goto "/data/com.emailappname" and copy that folder, usually that's where a program stores its data, not positive about that on the kindle is though, last time cleared my cache and dalvik cache on that os, I had to reset up my email account so I don't know for sure if that's correct exactly.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Okay after multiple manipulations, I have run the KFHD SRT using Option 1) Restore-Factory Rooted with SuperSU.apk (WooHoo!)
Can I assume that my KFHD is rooted? If so, what do I need to do to actually see these hidden files? (The email program is e-mail.apk or so I have been told.)
Of course with the standard USB cable, I still see the usual stuff with Win Explorer.
What is my next step?
:victory:
Hello,
I tried to copy files into the internal storage of my KFHD from Windows 7. The copy process failed. Since I am not able to access the storage anymore.
I read the dir, but I can not remove or create new files.
I booted into TWRP und tried to fix permissions. I got an error message.
Any idea?
Regards
I'm a bit confused what you did so lemme say a few things, mounting internal storage in twrp doesn't work on second gen kindles last I checked. If you flashed cm and can't view the internal storage from windows, its because you need to uninstall the kindle portable device in the device manager and then let it scan for devices again so it can install the drivers that work with cm. Does this answer your question or am I way off base?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I think my description was not sufficient.
After installation of CM10.1 everything worked just fine. The device showed up in Windows.
I tried to copy CM10.2 and gapps to the KFHD USB drive, while doing that an error occured.
Since I do not have write access to the KFHD /sdcard anymore neither under Windows nor under TWRP.
Ah that is weird, I'd go with just pushing the files over adb and see if then problem still exists after upgrading. I have a tutorial that covers it in the kindle general section under something like recovery boot loop after flashing twrp/2nd boot loader, need to put a link to that in my signature...
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hi,
I will try to push the CM zip file and the gapps to the "sdcard" directory using ADB.
I will report back tonight.
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
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