Develop Bugs

Recovery mode

Hi GN users -
Rooted my phone this evening and all (I thought) was going well. I've been trying to do a backup via rom manager but when the phone reboots i get the android with a red exclamation point. This happens when trying to get to recovery mode using ROM manager or just using the volume buttons. Can't get a clean back up.
Used the following files:
recovery-clockwork-5.8.3.1-toroplus.img
Superuser-3.0.7.efghi-signed
Should I have used CWM-SuperSU-v0.87?
If i can access the boot loader can I go ahead and flash with CWM?
Thanks
Denver

Apparently telling people where to post is frowned upon in this establishment. Please refer to my other post

ÜBER™ said:
You did it wrong. You need to flash the toroplus big dog.zip please search before posting and do not post questions in android development.
http://forum.xda-developers.com/showthread.php?t=1614922
This has the how to.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
Please stop being a douche and just answer the question and notify mods if you think posts are in the wrong section.
Sent from my Galaxy Nexus using XDA

So the problem is that you flashed custom recovery and when you reboot it reverts to stock recovery? If so it's because you're on the stock ROM and it's got a script that restores stock recovery upon reboot. You can either install a custom ROM or do this:
juliano_q said:
-remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
-rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak
(note: you could delete it, but renaming is much safer since its easily reversible)
yes, it is easier to use a script, but in my opinion it is much better to know what is going on behind it.
Click to expand...
Click to collapse

riggsandroid said:
Please stop being a douche and just answer the question and notify mods if you think posts are in the wrong section.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Apparently somebody is blind because I did answer the question... idiot.
Back to the OP you have to reflash your recovery.img then once in recovery flash the super user.zip located here http://tinyurl.com/77cfowp
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
Apparently somebody is blind because I did answer the question... idiot.
Back to the OP you have to reflash your recovery.img then once in recovery flash the super user.zip located here http://tinyurl.com/77cfowp
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
He flashed the correct zips.

jesusice said:
He flashed the correct zips.
Click to expand...
Click to collapse
He must not have if he is getting the broken android. So no he did not. The one I linked is the correct zip to flash to keep recovery and root without having to delete all that stuff. I know I did the exact same thing when I first attempted to root my phone.
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
He must not have if he is getting the broken android. So no he did not. The one I linked is the correct zip to flash to keep recovery and root without having to delete all that stuff. I know I did the exact same thing when I first attempted to root my phone.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
And I flashed the zips he posted when I rooted. I trust that Bigrushdog does know what he's doing but that zip seems to have a lot of things in there that he may or may not need. Like, why does it contain a boot.img? He only needs the SU binary to obtain root. His problem must be that he's rebooting. He should fastboot flash recovery, then fastboot reboot recovery and then flash the SU zip from there. And if he wants to stay on the stock ROM he should follow the instructions I posted. I'm not saying you're *wrong* but I am saying that I'm more right
EDIT: Rereading his post I'm pretty sure he does have root already, his problem is just that recovery isn't sticking which is a known issue with a known solution as I posted previously. Its the exact same thing on the Nexus S.

If anything we are equally correct and my method is much simpler. And yes the boot.img is required this is the stock kernel image without the recovery.sh that runs on the stock kernel. This will keep him from having to delete it manually. I know this because the same method was needed for my epic. You have to flash a tweaked stock kernel without the recovery.sh then flash the recovery. Then everything will stick. His issue is he didn't flash the tweaked kernel and upon booting the stock kernel deleted his custom recovery.
Sent From My Sprint Galaxy Nexus via XDA Premium

denverdesktop said:
Hi GN users -
Rooted my phone this evening and all (I thought) was going well. I've been trying to do a backup via rom manager but when the phone reboots i get the android with a red exclamation point. This happens when trying to get to recovery mode using ROM manager or just using the volume buttons. Can't get a clean back up.
Used the following files:
recovery-clockwork-5.8.3.1-toroplus.img
Superuser-3.0.7.efghi-signed
Should I have used CWM-SuperSU-v0.87?
If i can access the boot loader can I go ahead and flash with CWM?
Thanks
Denver
Click to expand...
Click to collapse
Ignore all the previous comments and once you follow This You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3

msedek said:
Ignore all the previous comments and once you follow http://forum.xda-developers.com/showthread.php?p=23229558 You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
Actually he would be even more lost and confused.
Sent From My Sprint Galaxy Nexus via XDA Premium

Just do this:
-remount /system in read/write mode (use something like the Root Explorer app or ES File Explorer; both have root modes (check the app's settings) for remounting /system as writable)
-rename the /system/recovery-from-boot.p to /system/recovery-from-boot.p-bak (note: you could delete it, but renaming is much safer since its easily reversible)
yes, it is easier to use a script, but in my opinion it is much better to know what is going on behind it.
Click to expand...
Click to collapse
Then flash your custom recovery and it'll stick.
No need to make it complicated.
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
msedek said:
Ignore all the previous comments and once you follow This You will be back on track and will be more wise..
Enjoy and cheers
Galaxy Nexus AOKP m5 Franco kernel m3
Click to expand...
Click to collapse
That has nothing to do with the problem.

nodstuff said:
Just do this:
Then flash your custom recovery and it'll stick.
No need to make it complicated.
Click to expand...
Click to collapse
Seriously this again? Why are y'all making it much more complicated than it needs to be? Reflash recovery... in recovery flash the zip I linked to. Done.
Sent From My Sprint Galaxy Nexus via XDA Premium

ÜBER™ said:
Seriously this again? Why are y'all making it much more complicated than it needs to be? Reflash recovery... in recovery flash the zip I linked to. Done.
Sent From My Sprint Galaxy Nexus via XDA Premium
Click to expand...
Click to collapse
What's complicated about erasing a script? Flashing a kernel to do the same thing seems much more complicated.

jesusice said:
What's complicated about erasing a script? Flashing a kernel to do the same thing seems much more complicated.
Click to expand...
Click to collapse
It takes longer.. takes more effort.
Its simpler to flash the su.zip and call it a day. Than have to flash recovery flash a subinary.zip delete the script the reflash recovery.
Sent From My Sprint Galaxy Nexus via XDA Premium

nodstuff said:
Just do this:
Then flash your custom recovery and it'll stick.
No need to make it complicated.
---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------
That has nothing to do with the problem.
Click to expand...
Click to collapse
It always has to do with the problem.. Why to do a Mess with your phone and not doing a fresh start???
Also in the way getting a wise android man while learning how to fastboot /adb?...
Thats all i got to say.. In my case id start all over and not going deep complicating things and messing up the os
Galaxy Nexus AOKP m5 Franco kernel m3

Thanks for the assistance.
Ended up reflashing with bigdog and now all seems well.
The assistance is appreciated.
Denver

denverdesktop said:
Thanks for the assistance.
Ended up reflashing with bigdog and now all seems well.
The assistance is appreciated.
Denver
Click to expand...
Click to collapse
Lol I'm sorry for clouding your thread with a semi-argument. Glad your up and running
Sent From My Sprint Galaxy Nexus via XDA Premium

it happens
No problem. It happens.
I can comfortably flash AOPK with CMW, correct?
Thanks
Denver

Yes but make sure you wipe all
Galaxy Nexus AOKP m5 Franco kernel m3

Help backing up stock JB kernel

I am really liking the stock JB kernel but I also have been using and liked Franco's kernel for the past few months, especially the customizability. I want to try it out too but I don't want to lose the stock kernel in the process. Can someone provide any of the following:
1. A guide to extracting/backing up the stock kernel.
2. A link to any such guide. (I looked around but couldn't find one.)
3. A link to the actual kernel. (If someone, somewhere has already done this and posted it.)
Thanks in advance!

mtmjr90 said:
I am really liking the stock JB kernel but I also have been using and liked Franco's kernel for the past few months, especially the customizability. I want to try it out too but I don't want to lose the stock kernel in the process. Can someone provide any of the following:
1. A guide to extracting/backing up the stock kernel.
2. A link to any such guide. (I looked around but couldn't find one.)
3. A link to the actual kernel. (If someone, somewhere has already done this and posted it.)
Thanks in advance!
Click to expand...
Click to collapse
Here's the stock kernel for you

Thanks! Out of curiosity, do you mind explaining how you got it? Is it super complicated? I'm just trying to learn by doing as much as I can to avoid having to ask all the time=/
Edit: Oh, also is that zip flashable via CWM?
Sent from my Galaxy Nexus using Tapatalk 2

I got it from one of the Jellybean threads, but with the sheer volume of JB threads today, I can't remember which. I think it's the main JB thread in General.
The only thing I did was rename it from StockKernel.zip and added the JB prefix so as not to lose it in my mess of files

Ah, sounds good. Thanks again!
Sent from my Galaxy Nexus using Tapatalk 2

mtmjr90 said:
Thanks! Out of curiosity, do you mind explaining how you got it? Is it super complicated? I'm just trying to learn by doing as much as I can to avoid having to ask all the time=/
Click to expand...
Click to collapse
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Another way, but less elegant, is to use dd (root and busybox required of course):
dd if=dev/block/platform/omap/omap_hsmmc.0/by-name/boot of=/sdcard/boot.img
That will place a file called boot.img in the root of /sdcard. (Not this file will likely not be flashable via fastboot, but can easily be flashed with dd:
dd if=/sdcard/boot.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/boot

efrant said:
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Another way, but less elegant, is to use dd (root and busybox required of course):
dd if=dev/block/platform/omap/omap_hsmmc.0/by-name/boot of=/sdcard/boot.img
That will place a file called boot.img in the root of /sdcard. (Not this file will likely not be flashable via fastboot, but can easily be flashed with dd:
dd if=/sdcard/boot.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/boot
Click to expand...
Click to collapse
Is that via a terminal emulator on the device then?

efrant said:
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Click to expand...
Click to collapse
Can you go into more details on this? I don't see an option to backup just the kernel. Do you have to pull it out of a complete backup?

mtmjr90 said:
Is that via a terminal emulator on the device then?
Click to expand...
Click to collapse
Either or.
---------- Post added at 11:59 AM ---------- Previous post was at 11:53 AM ----------
drewcam888 said:
Can you go into more details on this? I don't see an option to backup just the kernel. Do you have to pull it out of a complete backup?
Click to expand...
Click to collapse
You are right, you can NOT back up just the kernel using CWM, but you CAN restore just the kernel. (I was thinking of a different recovery.)

efrant said:
You are right, you can NOT back up just the kernel using CWM, but you CAN restore just the kernel. (I was thinking of a different recovery.)
Click to expand...
Click to collapse
I don't see any option to restore only the kernel. Where is this option?

drewcam888 said:
I don't see any option to restore only the kernel. Where is this option?
Click to expand...
Click to collapse
Under "backup and restore" under "advanced restore", select boot image.
Sent from my Galaxy Nexus using Tapatalk 2

Only a little bug for me:
From settings-->storage (memoria in italian) It can't see all the files in the sdcard, also doesn't see a lot of music (but I can see those music files with play music app)...
Any other thing is working fine, good battery life, much faster on homescreen and on the appdrawer, maybe a little laggier on temple run...
Waiting for the official release...

So I guess that if I download factory image for my NS and extract boot.img out of it (it is in tgz-tar-zip ), I should be able to flash it and restore stock kernel using fastboot flash boot boot.img. Am I right?
But I noticed that boot.img in zip provided by harveydent takes 2x more space than the one in the factory image.

jenda.69 said:
So I guess that if I download factory image for my NS and extract boot.img out of it (it is in tgz-tar-zip ), I should be able to flash it and restore stock kernel using fastboot flash boot boot.img. Am I right?
Click to expand...
Click to collapse
Yes, you are right.
jenda.69 said:
But I noticed that boot.img in zip provided by harveydent takes 2x more space than the one in the factory image.
Click to expand...
Click to collapse
If harveydent used dd to dump the image, it will be padded with a bunch of zeros at the end. Both will work fine, although you cannot flash the untrimmed one using fastboot, you need to use recovery or dd.
Sent from my Galaxy Nexus using Tapatalk 2

[ROM][d802] Recovery Flashable STOCK 80220B Vodafone DE (+root)

Made this from the new 80220B Vodafone DE kdz.
This is the complete LG KK 20B ROM - nothing missing or messed with.
If you follow the method below exactly, no Audio glitches, no Touchscreen problems.
You can flash SuperSU and get root if you wish - your choice.
I provide this assuming you have an understanding of the terminology used below and appreciate that any flashing activity has some risk.
I strongly advise against using any form of restore from previous backups, such as TB or Nandroid.
Once the process is complete, custom recovery will be lost.
Method:
Download both the ROM zip file linked below and SuperSU zip file (if you want root) and copy to your SD card.
You need to be already on Rooted JB or PURE CM11 with either TWRP 2.6.3.3 or 2.6.3.4 or TWRP 2.7.0.0 (nothing else).
Reboot to TWRP recovery
Wipe: System, Data, Cache. Dalvik (nothing else)
Flash the ROM zip - ignore any "FAIL" warnings.
Wipe Cache and Dalvik (nothing else)
Go to the Mount page in TWRP and select System (leave the other defaults alone)
Flash the SuperSU zip - ignore any "FAIL" warnings
Reboot
Done
Don't use AutoRec to flash TWRP - you will lose Knock code.
Alternatively - if you have flashed TWRP on another KK Stock ROM (using AutoRec), you can full wipe (not SDCard) and flash this directly without going back to JB.
Download from here:
https://mega.co.nz/#!7EB0URZI!aYN6pBx9v7duPm2IaYFS0x_QEY89f0rhR66P9WP1EUc

Hey, you mentioned in this thread that you were going to upload a flashable ROM with knockcode.
Is this what you were talking about? You don't mention Knockcode in the OP. Also at the moment I'm running Stock Kitkat, rooted and with custom recovery. Do I just go into recovery and flash this? (Assuming I have the right TWRP and I wipe Cache and Davlik) You have said its okay to be on rooted JB, just wondering if being on rooted KK changes anything.

Yes this is the latest with Knock code. It would be fine to flash from any other KitKat ROM with custom recovery. Make sure you make the correct wipes.
You forgot download link!
Also PrimaryGPT.bin is partition table so may have issues with phone storage size after flash... I could be wrong and it could be fine...
Sent from my LG-D802 using Tapatalk

ephumuris said:
Yes this is the latest with Knock code. It would be fine to flash from any other KitKat ROM with custom recovery. Make sure you make the correct wipes.
You forgot download link!
Also PrimaryGPT.bin is partition table so may have issues with phone storage size after flash... I could be wrong and it could be fine...
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Download link on its way - uploading to G Drive this time not effing Mega.
I'm not testing this build - I don't want Voda bloat and 80220C Open is perfectly fine for me in all ways - I cannot for the life of me understand the hankering for Kock code.

Tried knock code and its awful...seems like its basically a pattern/number pin with invisible buttons...
Sent from my LG-D802 using Tapatalk

ephumuris said:
Tried knock code and its awful...seems like its basically a pattern/number pin with invisible buttons...
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Quite! lol
I did this on request from a couple of members.
Link now live

Thanks. Personally I like knock code. It is easier to unlock while driving. . What could those two binaries do?

If anyone has a Pioneering Spirit, or the necessary cajones to try it, please report back!

You are scaring me to try it.

PrimaryGPT.bin
is for the partition( 16gb or 32gb)
and it can be excluded from the rom

albsat said:
You are scaring me to try it.
Click to expand...
Click to collapse
well... of course the 2 additional .bin files could be excluded together or one by one... or left there.
Vodafone DE have both 16GB and 32GB variants, IIRC. Which may be why those files are there. So in theory it shouldn't matter if the whole ROM is flashed.

ROM wouldn't be stock if those files were removed.
Sent from my LG-D802 using Tapatalk

ephumuris said:
ROM wouldn't be stock if those files were removed.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Anyone who has flashed the kdz itself would have had the 2 files anyway, and it works.
Just need some feedback from those who have downloaded my flashable ROM and flashed in its entirety.

Hi, i have a stock 80220A and AutoRec installed. Do i need to go back to JB, or i can flash dirctly?
Sent from my LG-D802 using XDA Premium 4 mobile app

hristo2000 said:
Hi, i have a stock 80220A and AutoRec installed. Do i need to go back to JB, or i can flash dirctly?
Sent from my LG-D802 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This info is in the OP...
Wipe everything except SDCard and flash.

I will give this rom a try in the afternoon. I have a 32 gb version. Hope no bad surprises for Easter.

Hi flash this as per instruction from open. I was previously on cloudystock rom so all I did was install twrp recovery and then flash rom then flash supersu. ....Rom is running smooth on a UK d802. ... plus knock code is working as it should. But I don't particularly like it but it's working ..
Will run this rom for rest of day to see if any problems
Thanks
Sent from my LG-D802 using XDA Premium 4 mobile app
Been running rom for about 5 hours

Just installed myself too. So far so good... Later on I will report for issues, if any. Installed recovery as well... Thanks for the rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:33 PM ----------
I think I got my first issue. Double touch to waken the screen and knock code do not respond while I am charging. Don't know why.

leegreggs said:
Hi flash this as per instruction from open. I was previously on cloudystock rom so all I did was install twrp recovery and then flash rom then flash supersu. ....Rom is running smooth on a UK d802. ... plus knock code is working as it should. But I don't particularly like it but it's working ..
Will run this rom for rest of day to see if any problems
Thanks
Sent from my LG-D802 using XDA Premium 4 mobile app
Been running rom for about 5 hours
Click to expand...
Click to collapse
Thanks!

albsat said:
Just installed myself too. So far so good... Later on I will report for issues, if any. Installed recovery as well... Thanks for the rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:33 PM ----------
I think I got my first issue. Double touch to waken the screen and knock code do not respond while I am charging. Don't know why.
Click to expand...
Click to collapse
Thanks

[Q] What steps am I missing with my install to kitkat?

To start off the kindle had an older version of twrp and had a version of ice cream sandwich. Those work correctly and it continues to work correctly after a nandroid restore.
Fast forward to now, I installed the latest twrp and flashed the latest FFF v1.5 bootloader.
I flashed this CM11 nightly cm-11-20140702-NIGHTLY-otter.zip
and flashed latest gapps gapps-kk-20140606-signed.zip
After I finish flashing everything I can setup the kindle but once I reboot it goes into a bootloop at the CM logo that results in a colorful screen. If I power off and power on it just bootlopps at the CM logo. Not sure what else I can do. Any help is appreciated.
Forgot to add. I have tried flashing Pacman rom: pac_otter-nightly-20140701.zip and I get same results as above.

Verify md5 for rom and gapps after downloading?
[How to] Verify that your download is complete with MD5/SHA-1 Hash Checksums

try gapps-kk-20140105-signed.zip
---------- Post added at 07:30 PM ---------- Previous post was at 07:30 PM ----------
newer is not always better

Dirty flash or clean?
Sent from my Nexus 5 using XDA Free mobile app

sd_shadow said:
Verify md5 for rom and gapps after downloading?
[How to] Verify that your download is complete with MD5/SHA-1 Hash Checksums
Click to expand...
Click to collapse
Matching md5 for the roms and gapps
sd_shadow said:
try gapps-kk-20140105-signed.zip
---------- Post added at 07:30 PM ---------- Previous post was at 07:30 PM ----------
newer is not always better
Click to expand...
Click to collapse
Going to try with these
dokie80 said:
Dirty flash or clean?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
It's always been a clean flash
On a side note installing a jelly bean rom works fine and I can reboot without a problem.

JJsevol said:
Matching md5 for the roms and gapps
Going to try with these
It's always been a clean flash
On a side note installing a jelly bean rom works fine and I can reboot without a problem.
Click to expand...
Click to collapse
If u install JB with out problem with the same twrp, then ur twrp is twrp6?
Afaik, kitkat need twrp7, JB need twrp6.
I had bootloop when I flashed JB with twrp7. Check ur twrp version?
Sent from my Nexus 5 using XDA Free mobile app

dokie80 said:
If u install JB with out problem with the same twrp, then ur twrp is twrp6?
Afaik, kitkat need twrp7, JB need twrp6.
I had bootloop when I flashed JB with twrp7. Check ur twrp version?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That is what I was thinking, recheck twrp version

dokie80 said:
If u install JB with out problem with the same twrp, then ur twrp is twrp6?
Afaik, kitkat need twrp7, JB need twrp6.
I had bootloop when I flashed JB with twrp7. Check ur twrp version?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
sd_shadow said:
That is what I was thinking, recheck twrp version
Click to expand...
Click to collapse
Never thought about that. I just downloaded the version in the twrp thread.

OK so I have twrp 2.7.0.1. Here's the screenshot in recovery. Does your twrp look like that because my other twrp on other devices look different logo wise.

JJsevol said:
OK so I have twrp 2.7.0.1. Here's the screenshot in recovery. Does your twrp look like that because my other twrp on other devices look different logo wise.
Click to expand...
Click to collapse
that should be fine, unless it did not install correctly. try the 2.7.1.0 zip version zip-openrecovery-twrp-2.7.1.0-otter.zip Install in old TWRP>wipe cache and dalvik>reboot

sd_shadow said:
that should be fine, unless it did not install correctly. try the 2.7.1.0 zip version zip-openrecovery-twrp-2.7.1.0-otter.zip Install in old TWRP>wipe cache and dalvik>reboot
Click to expand...
Click to collapse
I installed this and same thing as before. Not sure what's going on, but ended up just using jb.

Still stuck at logo?
U need to inform ur version of bootloader, twrp, and which ROM u r trying to flash. Let us know the name of the file.
Did u wipe before flashing?
Twrp7 can't be use for flashing JB. U ending up using JB by flashing ur old twrp and ROM? Or by flashing via twrp7?
Last.. Are u sure u device is kindle fire original?
Sent from my Nexus 5 using XDA Free mobile app

dokie80 said:
Still stuck at logo?
U need to inform ur version of bootloader, twrp, and which ROM u r trying to flash. Let us know the name of the file.
Did u wipe before flashing?
Twrp7 can't be use for flashing JB. U ending up using JB by flashing ur old twrp and ROM? Or by flashing via twrp7?
Last.. Are u sure u device is kindle fire original?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still stuck at cm logo after powering back on or rebooting. File names are in the op but let me know if you need anything else. Clean instalI with a wipe. I even used the twrp version SD_shadow provided and I still installed KitKat and installed jb bit still see the issue. And positive to original kindle. I'm thinking I should make a video of my install process. Thanks for the help guys.

JJsevol said:
Yeah still stuck at cm logo after powering back on or rebooting. File names are in the op but let me know if you need anything else. Clean instalI with a wipe. I even used the twrp version SD_shadow provided and I still installed KitKat and installed jb bit still see the issue. And positive to original kindle. I'm thinking I should make a video of my install process. Thanks for the help guys.
Click to expand...
Click to collapse
No idea.. Sorry.
Anyway, if you successfully install JB with TWRP 7.. That's weird.
Sent from my Nexus 5 using XDA Free mobile app

dokie80 said:
No idea.. Sorry.
Anyway, if you successfully install JB with TWRP 7.. That's weird.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Here's a better look of twrp version and zips I have. Also the bootloader version is v1.5 not v1.4.

JJsevol said:
Here's a better look of twrp version and zips I have. Also the bootloader version is v1.5 not v1.4.
Click to expand...
Click to collapse
This is all with a full wipe including the system?

Thepooch said:
This is all with a full wipe including the system?
Click to expand...
Click to collapse
At first it wasn't. I was just doing the normal Factory Reset in twrp but on the last try I included system as well. Let me try again.

JJsevol said:
At first it wasn't. I was just doing the normal Factory Reset in twrp but on the last try I included system as well. Let me try again.
Click to expand...
Click to collapse
Full wipe recommended when changing a system. Wait for boot don`t be impatient.

Thepooch said:
Full wipe recommended when changing a system. Wait for boot don`t be impatient.
Click to expand...
Click to collapse
Doing that now. I don't have to flash the bootloader every time, right?

JJsevol said:
Doing that now. I don't have to flash the bootloader every time, right?
Click to expand...
Click to collapse
The bootloader gets flashed 1 time and 1 time only. Unless perhaps there is an upgrade you never do this in correlation with flashing a new ROM period.
---------- Post added at 11:01 AM ---------- Previous post was at 10:26 AM ----------
Swipe factory reset then go advanced select dalvik, cache, system then swipe again. Flash rom.zip, flash gapps.zip in zip form mind you then select reboot system.

stock rom zip?

hey guys, I was just searching for a stock rom zip, is there any? thanks for your attention.

throcker said:
hey guys, I was just searching for a stock rom zip, is there any? thanks for your attention.
Click to expand...
Click to collapse
For what software version ? Carrier ? their are dozens of them >> http://www.androidruu.com/?developer=M9

I suggest using this for all your stock needs: https://docs.google.com/spreadsheets/d/15K6xhb6wtosp9j8yu4xHBZ6n9v5OaFSW6ZVWxC4u_qc/pubhtml
Helped me tons when going back to stock, courtesy to @Flippy498

thank you all and sorry for my lack of info!
I'm on 2.10.401.1
a ruu is just too much.....I was searching for a simple twrp flashable stock zip if there isn't any don't mind, I got used to have some available for m7 and m8

throcker said:
thank you all and sorry for my lack of info!
I'm on 2.10.401.1
a ruu is just too much.....I was searching for a simple twrp flashable stock zip if there isn't any don't mind, I got used to have some available for m7 and m8
Click to expand...
Click to collapse
Well, my google sheet doesn't contain flashable zip's but nevertheless you can restore the Nandroids via TWRP. (If you ask me I actually don't see a reason why someone should take the time to make a flashable stock zip if a restorable Nandroid that only contains the Boot Image, a System Image and the Stock Recovery behaves the same way as a clean installed stock rom. And if you don't need the Stock Recovery you don't need to restore it. Just my 2 cents. )

Here you go! ? https://www.androidfilehost.com/?fid=24052804347811705
Sent from my HTC One M9 using XDA Free mobile app
---------- Post added at 09:22 AM ---------- Previous post was at 09:21 AM ----------
throcker said:
thank you all and sorry for my lack of info!
I'm on 2.10.401.1
a ruu is just too much.....I was searching for a simple twrp flashable stock zip if there isn't any don't mind, I got used to have some available for m7 and m8
Click to expand...
Click to collapse
Here you go mate ? https://www.androidfilehost.com/?fid=24052804347811705
Sent from my HTC One M9 using XDA Free mobile app

Flippy498 said:
Well, my google sheet doesn't contain flashable zip's but nevertheless you can restore the Nandroids via TWRP. (If you ask me I actually don't see a reason why someone should take the time to make a flashable stock zip if a restorable Nandroid that only contains the Boot Image, a System Image and the Stock Recovery behaves the same way as a clean installed stock rom. And if you don't need the Stock Recovery you don't need to restore it. Just my 2 cents. )
Click to expand...
Click to collapse
yes, but I think I am a little....traditional!....this twrp backup method doesn't convince me!....like if could be dirty in some way....
I'm more a "cmd img flash" or "zip" guy
K00li79 said:
Here you go! https://www.androidfilehost.com/?fid=24052804347811705
Sent from my HTC One M9 using XDA Free mobile app
---------- Post added at 09:22 AM ---------- Previous post was at 09:21 AM ----------
Here you go mate https://www.androidfilehost.com/?fid=24052804347811705
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
no way where were you hiding this?!? post it on development section! thank you so much. how did you get this?
two questions: untouched? unrooted? also, is this good one to get OTA?

throcker said:
yes, but I think I am a little....traditional!....this twrp backup method doesn't convince me!....like if could be dirty in some way....
I'm more a "cmd img flash" or "zip" guy
no way where were you hiding this?!? post it on development section! thank you so much. how did you get this?
two questions: untouched? unrooted? also, is this good one to get OTA?
Click to expand...
Click to collapse
I made this from the systemdump by liabtoofer . This is rooted, unsecure boot image (so you can use the color calibration MOD ? ) and busybox and initd support. No tweaks and other mods . ?
I can make one completely stock, Unrooted etc. Don't really see the point but I can.
Maybe I will make a separate thread.
Don't think you can take ota. Since you don't have stock recovery .
Glad I could help.
Sent from my HTC One M9 using XDA Free mobile app

thank you very much for this again. flashing right now
EDIT: error executing updater binary. too bad! twrp 2.8.7.0
also want to ask what do you use to calibrate the screen

throcker said:
thank you very much for this again. flashing right now
EDIT: error executing updater binary. too bad! twrp 2.8.7.0
also want to ask what do you use to calibrate the screen
Click to expand...
Click to collapse
Huh? That's odd.... Didn't hear about that error when flashing this rom. However been reading about this on other threads . Are you on the newest firmware?
For color control I use the apk provided in the kcal thread. (The one with the parrots ? )
Sent from my HTC One M9 using XDA Free mobile app

K00li79 said:
Huh? That's odd.... Didn't hear about that error when flashing this rom. However been reading about this on other threads . Are you on the newest firmware?
For color control I use the apk provided in the kcal thread. (The one with the parrots )
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
2.14.401.1 I think is the lastest (unless an update came out today)