Develop Bugs

[Q] replacing clockwork mod with twrp

Ok, I'm completely self taught as far as this whole arena of technology is concerned. So please bear with me. I rooted using kindle water and clockwork mod was installed as my recovery. But, I need twrp to install any of the 3.0 kernels. Can I install twrp with clockwork mod still on my device our do I need to remove it somehow? Any advice would be great.

No, I don't think it's even remotely possible.
There are several methods you can use to install TWRP; fastboot, script, KFU, depending on whatever you're most comfortable with.
Before you do so I'd highly suggest you read and understand what is laid out in this guide: http://forum.xda-developers.com/showthread.php?t=1552547 (first, second and third posts)
It'll save you a lot of trouble when things "go bad".

Thanks for the reply!

Stage said:
Ok, I'm completely self taught as far as this whole arena of technology is concerned. So please bear with me. I rooted using kindle water and clockwork mod was installed as my recovery. But, I need twrp to install any of the 3.0 kernels. Can I install twrp with clockwork mod still on my device our do I need to remove it somehow? Any advice would be great.
Click to expand...
Click to collapse
Actually, if you wanted to have a completely wacky setup...
They are all boot images, so you can leave CWMR on your recovery partition and flash your boot partition with TWRP. Then you would "normally" boot into TWRP and selecting recovery will take you to CWMR as it did before. If you ever want to boot ICS, you can "fastboot boot" the ICS boot.img file and it should boot into the system for you. This is just all in theory, I've never done anything this insane, but it should work if you wanted.
Now, for a more practical approach....
You can leave CWMR on your recovery partition and just "fastboot boot" the TWRP image. That would get you a "per boot" access to TWRP without ever flashing it onto your device. If all you want to do is flash ICS with it, then this is a doable setup and would just require the extra step of booting directly from the TWRP recovery image with fastboot.

Well I'm on CM9 by hellfire right now so ICS is definitely possible. Just wanted to get HWA going.

Just to piggyback on the OP and maybe a more direct question.
I currently have CWMR installed. Can I simply use KFU to replace it with TWRP by choosing option 3?

dferrey said:
Just to piggyback on the OP and maybe a more direct question.
I currently have CWMR installed. Can I simply use KFU to replace it with TWRP by choosing option 3?
Click to expand...
Click to collapse
That would answer my question add well. Anyone?

dferrey said:
Just to piggyback on the OP and maybe a more direct question.
I currently have CWMR installed. Can I simply use KFU to replace it with TWRP by choosing option 3?
Click to expand...
Click to collapse
Stage said:
That would answer my question add well. Anyone?
Click to expand...
Click to collapse
KFU's TWRP installer is either broken or will install TWRP 2.0.0 (broken reboot) and FFF 1.0 (4 generations old) together. You can either tinker with its run.bat file or learn to use fastboot if you want the latest stuff installed. The latter makes more sense to me...
http://forum.xda-developers.com/showthread.php?t=1552547
The fastboot section is in post #3.

kinfauns said:
KFU's TWRP installer is either broken or will install TWRP 2.0.0 (broken reboot) and FFF 1.0 (4 generations old) together. You can either tinker with its run.bat file or learn to use fastboot if you want the latest stuff installed. The latter makes more sense to me...
http://forum.xda-developers.com/showthread.php?t=1552547
The fastboot section is in post #3.
Click to expand...
Click to collapse
Dang, reading for comprehension is not my strong suit sometimes. I read that guide yesterday and it specifically addresses my question and also says I can play with images without installing them way cool.
Thanks for pointing me in the right direction.

what is the real difference between cwm and twrp besides the interface? I like twrp but i also like to use rom manager when on another rom besides stock....also im using bootmanager for my tri-boot needs... What is the problem with cwm and 3.0 kernel?

I believe that Hashcode updated CWM to support 3.0 ROMs (Check the dev section).
I started with TWRP then CWM. Then I wanted to flash 3.0 ROMs so I used KFU to flash TWRP (Hope that helps someone).
I have not tested the new CWM yet as this old version of TWRP does what I need it to.

hgigh said:
I believe that Hashcode updated CWM to support 3.0 ROMs (Check the dev section).
I started with TWRP then CWM. Then I wanted to flash 3.0 ROMs so I used KFU to flash TWRP (Hope that helps someone).
I have not tested the new CWM yet as this old version of TWRP does what I need it to.
Click to expand...
Click to collapse
I believe that CWM is more streamlined in that it can work with ROM Manager as well, whereas TWRP requires you go to recovery in order to flash anything. However, I like to stick with TWRP for its ability to compress backups, since there isn't much free space on the Fire. I'll probably switch over to CWM eventually, but, like you, TWRP does just what I need.

YayILikePie said:
I believe that CWM is more streamlined in that it can work with ROM Manager as well, whereas TWRP requires you go to recovery in order to flash anything. However, I like to stick with TWRP for its ability to compress backups, since there isn't much free space on the Fire. I'll probably switch over to CWM eventually, but, like you, TWRP does just what I need.
Click to expand...
Click to collapse
I agree completely! Not much space at all. ROM Manager is cool but I have had more problems than solutions using it (G2X) so I am used to going into recovery to flash (CWM included).

thanks for the help. Im used to using rom manager/cwm on my indulge so im not really used to having to go into recovery for everything. but as stated earlier with the limited space on the kindle ill still with twrp then so i can compress my backups. also stated rom manager will have some problems untill they can find a way to link cwm for kindle fire to rom manager otherwise you will run into the same issues that happens when you use it with twrp....it boots into recovery and then does nothing else. lol

Alright so I tried installing TWRP via goo manager. I downloaded the app and installed the openrecoveryscript. It shows that it's installed, yet whenever I tried and reboot into recovery it still boots into clockwork... I have gone as far as trying to delete Rom Manager app from my phone and I tried installing the openrecoveryscript again. Any suggestions on how I should go about fixing this. I`m currently running 11.0-installerXNPQ02R.

Root attempt failing

I purchased a Kindle Fire for my wife, I want to root it to allow Google Play to be installed
I dl'd the KFU v0.9.6, got the ADB driver, installed, showing as a android composite device
I run the utility following these instructions
from the liliputing.com
it gets to this point, screen cap attached
and dies, it leaves me at the TWRP screen, I have recovered several times using this site here
rootkindlefire.com hot to /how-to-unrootunbrick-rooted-kindle-fire
I must have read 100 threads today but nothing seems to help
Any suggestions or should I just wait for a utility update?
I'm no expert but I have rooted my phones in the past and installed custom ROMs, I'm no developer by a long shot but I'm not out in the woods clueless either.
Thanks

Hopefully you have the latest FFF installed (blue Kindle Fire logo?). If so, when you see it, hold the power button until you see the boot options appear. Select normal or reset boot mode.

soupmagnet said:
Hopefully you have the latest FFF installed (blue Kindle Fire logo?). If so, when you see it, hold the power button until you see the boot options appear. Select normal or reset boot mode.
Click to expand...
Click to collapse
At the moment I am back to stock, kind of skittish as it seems I am not the only person having a similar issue

Well, looking at screenshot, I see that TWRP was installed successfully. As long as have that, you're good. You can use TWRP to install FFF and a new rom which fixes just about everything. When TWRP first installs it will reboot and leave your device in fastboot mode (stuck at boot logo). To fix it, simply change your bootmode. Using the latest FFF (blue Kindle Fire logo) is the easiest way, but it can also be done via command line.
Being "stuck" at the boot logo is a normal process of modifying the KF, it doesn't mean it's bricked. I suggest you take the time to read up on some Kindle Fire basics before you proceed.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it, not to identify your exact problem like so many do, but to educate yourself on how this thing called Kindle Fire/Android works. If you've already read it, read it again. Doing so will help you and those trying to help you, tremendously.

I got the same screen last night as well. TWRP is installed as I can reboot into Normal/Recovery/Reset Boot..
I can use the KFU to reset the bootloader as well (normal/fastboot, etc)..
but for some reason, KFU doesn't seem to root my device when selecting option 2. I get the blue KF boot logo, can access TWRP, but then what? Do I need to install some other software?
I am soo confused...
I want to root my device so I can install programs. I would also like to install custom ROMs (which I understand that I do not NEED to be rooted to do this), but to install other programs I do.

iRock48 said:
I got the same screen last night as well. TWRP is installed as I can reboot into Normal/Recovery/Reset Boot..
I can use the KFU to reset the bootloader as well (normal/fastboot, etc)..
but for some reason, KFU doesn't seem to root my device when selecting option 2. I get the blue KF boot logo, can access TWRP, but then what? Do I need to install some other software?
I am soo confused...
I want to root my device so I can install programs. I would also like to install custom ROMs (which I understand that I do not NEED to be rooted to do this), but to install other programs I do.
Click to expand...
Click to collapse
Transfer the ROM you want to your sdcard and use TWRP to install it. Be sure to "factory reset" (wipe) before you install the ROM or there will be conflicts. It is usually a good idea to wipe cache and dalvik after the ROM installation. There's no need to root a custom ROM.

soupmagnet said:
Well, looking at screenshot, I see that TWRP was installed successfully. As long as have that, you're good. You can use TWRP to install FFF and a new rom which fixes just about everything. When TWRP first installs it will reboot and leave your device in fastboot mode (stuck at boot logo). To fix it, simply change your bootmode. Using the latest FFF (blue Kindle Fire logo) is the easiest way, but it can also be done via command line.
Being "stuck" at the boot logo is a normal process of modifying the KF, it doesn't mean it's bricked. I suggest you take the time to read up on some Kindle Fire basics before you proceed.
http://forum.xda-developers.com/showpost.php?p=23747567
Read it, not to identify your exact problem like so many do, but to educate yourself on how this thing called Kindle Fire/Android works. If you've already read it, read it again. Doing so will help you and those trying to help you, tremendously.
Click to expand...
Click to collapse
Thanks, I reread it last night and will do so again, will likely get back to this over the weekend

soupmagnet said:
Transfer the ROM you want to your sdcard and use TWRP to install it. Be sure to "factory reset" (wipe) before you install the ROM or there will be conflicts. It is usually a good idea to wipe cache and dalvik after the ROM installation. There's no need to root a custom ROM.
Click to expand...
Click to collapse
Thank you for the reply. I assume to transfer the ROM I want I'd use something like Window Explorer to drag/drop or should I use the command language?
Wiping the cache and dalvik - is that also done through TWRP?
one last thing; it is my understanding that once you install a custom ROM, you have "root" access.. will this access allow me to install the App Store/Android Market and install apps that normally require root, such as Titanium backup?

iRock48 said:
Thank you for the reply. I assume to transfer the ROM I want I'd use something like Window Explorer to drag/drop or should I use the command language?
Click to expand...
Click to collapse
In TWRP you can use "abd push" or there is "mount" function that it comes with that will allow you to mount your sdcard as an external drive, much like with the stock Amazon software.
Wiping the cache and dalvik - is that also done through TWRP?
Click to expand...
Click to collapse
Yes, after you install the ROM, you'll be given the option to.
one last thing; it is my understanding that once you install a custom ROM, you have "root" access.. will this access allow me to install the App Store/Android Market and install apps that normally require root, such as Titanium backup?
Click to expand...
Click to collapse
Yes, but the "Market" (Google Play) must be installed in TWRP as a "gapps" package. Just Google gapps for the version of android you're installing (CM10-JB, CM9-ICS, or CM7-GB).

ye i have the same issue "mv: can't rename '/system/bin/check_rooted': No such file or directory". I'm sitting at TWRP recovery screen, so I'm guessing just download rom of choice use the mount function to transfer the rom, full wipe and install. this should solve my getting no further in rooting process problem?

radici said:
ye i have the same issue "mv: can't rename '/system/bin/check_rooted': No such file or directory". I'm sitting at TWRP recovery screen, so I'm guessing just download rom of choice use the mount function to transfer the rom, full wipe and install. this should solve my getting no further in rooting process problem?
Click to expand...
Click to collapse
If your only error is "mv: can't rename '/system/bin/check_rooted': then chances are, you're already rooted. It just means there was no check_rooted file to rename, so you're good.
Not that it matters anyway because installing a custom ROM gives you "root" anyway.

[Q] Twrp won't install custom rom gives error message

the error message was error flashing zip then it went to updating partition details.should i just continue with it or what?edit:it also shows the 3 buttons that you get at the end of an installation and the rom i was flashing was cyanogenmod 10

Jacobloveskindles said:
the error message was error flashing zip then it went to updating partition details.should i just continue with it or what?edit:it also shows the 3 buttons that you get at the end of an installation and the rom i was flashing was cyanogenmod 10
Click to expand...
Click to collapse
That's a known bug in TWRP. Install a version previous to the one you're using, or install COTR.

safe method of doing that
soupmagnet said:
That's a known bug in TWRP. Install a version previous to the one you're using, or install COTR.
Click to expand...
Click to collapse
my kindle has no system files and i forgot to make a backup.how do i do that in linux

Jacobloveskindles said:
my kindle has no system files and i forgot to make a backup.how do i do that in linux
Click to expand...
Click to collapse
fastboot

soupmagnet said:
fastboot
Click to expand...
Click to collapse
not to sound like a total noob but how do I do it in fastboot

http://forum.xda-developers.com/showthread.php?t=1668159

if i do this will it overwrite my other recovery?
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1668159
Click to expand...
Click to collapse
If I use your soup kit to change into fast boot can I just install twrp on soup kit and it will downgrade me to an older version?

Jacobloveskindles said:
If I use your soup kit to change into fast boot can I just install twrp on soup kit and it will downgrade me to an older version?
Click to expand...
Click to collapse
Yes, the SoupKit that is posted now has an older version of TWRP. I'm in the process of updating it so you should probably grab it while you have the chance, should you decide to go that route. You could also install Cannibal Open Touch Recovery. All versions of it are quite stable.

confused
soupmagnet said:
Yes, the SoupKit that is posted now has an older version of TWRP. I'm in the process of updating it so you should probably grab it while you have the chance, should you decide to go that route. You could also install Cannibal Open Touch Recovery. All versions of it are quite stable.
Click to expand...
Click to collapse
So if I'm inside twrp and have soupkit up on the PC and have my kindle plugged in and change it to fast boot then hit flash twrp will it do its thing and downgrade me and reboot my kindle into twrp 2.2 and let me install a ROM.

It has been brought to my attention that you may be confused between the KFU (Kindle Fire Utility) and TWRP (Team Win Recovery Project). The KFU is a Windows based utility used to change bootmodes, install custom versions of the recovery and bootloader partition images along with various other tasks. It has no affiliation with TWRP, COTR, or FireFireFire, other than it installs them to your device for you.
However, the "bug" in TWRP mentioned earlier is due to that way it handles the updater scripts in certain ROMS. It has nothing to do with your system files. The reason you have no system files right now, is because you wiped them prior to attempting to flash a ROM. Since the ROM was never successfully flashed, you have no system files in place, therefore nothing to boot to.
Downgrade your version of TWRP, or install a different recovery altogether, make sure you have wiped data (factory reset) and reinstall your ROM. After that, you should no longer have any problems.
I strongly suggest you take the time to read the guides and tutorials available for the Kindle Fire and make sure you understand how everything works before you do something and get yourself in a situation that you can't get out of on your own.

soupmagnet said:
It has been brought to my attention that you may be confused between the KFU (Kindle Fire Utility) and TWRP (Team Win Recovery Project). The KFU is a Windows based utility used to change bootmodes, and install custom versions of the recovery and bootloader partition images. It has no affiliation with TWRP, COTR, or FireFireFire, other than it installs them to your device for you.
However, the "bug" in TWRP mentioned earlier is due to that way it handles the updater scripts in certain ROMS. It has nothing to do with your system files. The reason you have no system files right now, is because you wiped them prior to attempting to flash a ROM. Since the ROM was never successfully flashed, you have no system files in place, therefore nothing to boot to.
Downgrade your version of TWRP, or install a different recovery altogether, make sure you have wiped data (factory reset) and reinstall your ROM. After that, you should no longer have any problems.
I strongly suggest you take the time to read the guides and tutorials available for the Kindle Fire and make sure you understand how everything works before you do something and get yourself in a situation that you can't get out of on your own.
Click to expand...
Click to collapse
There are no tutorials on how to downgrade twrp on kindle fire.look at my previous post its not about kfu its about your soup kit.I checked your thumbnails.it allows me to install twrp but,please I need to know how to downgrade twrp without using the command line.the last time I used the command prompt or typed a command windows gave me a bsod.but now I'm in Linux because of that,anyways,in other words,I don't wanna use a command line.just pleez read my previous post over entirely.

Jacobloveskindles said:
There are no tutorials on how to downgrade twrp on kindle fire.look at my previous post its not about kfu its about your soup kit.I checked your thumbnails.it allows me to install twrp but,please I need to know how to downgrade twrp without using the command line.the last time I used the command prompt or typed a command windows gave me a bsod.but now I'm in Linux because of that,anyways,in other words,I don't wanna use a command line.just pleez read my previous post over entirely.
Click to expand...
Click to collapse
I did read your post, entirely.
I'm addressing the fact that you contacted the developer of the KFU, and due to your confusion about things work, gave him the impression that I said something that I clearly haven't.
The "bug" mentioned earlier in this thread has nothing at all to do with the KFU, therefore the developer of that utility is not responsible for it. That being said, the bug in TWRP that prevented you from flashing a ROM has nothing to do with the fact that you don't have system files, as you erroneously assumed.
Even with that, you as the user, assume all responsibility for anything you do to your device, not the developers of this community. This is a community of developers, for developers. This is not a community of developers, for people that don't know what they're getting into, and run into trouble as a result of it.
Now, for your problem at hand...
If you go through this thread carefully, you'll see that I have already answered your question. Go back and pay attention to what's been said and you should be fine.

last question
soupmagnet said:
Yes, the SoupKit that is posted now has an older version of TWRP. I'm in the process of updating it so you should probably grab it while you have the chance, should you decide to go that route. You could also install Cannibal Open Touch Recovery. All versions of it are quite stable.
Click to expand...
Click to collapse
stupid question:do i need to be in fastboot because it says i can do it in any bootmode but of course im gonna be in twrp and downgrading

Jacobloveskindles said:
So if I'm inside twrp and have soupkit up on the PC and have my kindle plugged in and change it to fast boot then hit flash twrp will it do its thing and downgrade me and reboot my kindle into twrp 2.2 and let me install a ROM.
Click to expand...
Click to collapse
I'm not an expert on this but let do together. I want to learn something too.
According to the previous post, you asked and soupmagnet already answered that it will install a previous version of TWRP.
Why don't you do that then?
Next question is can you get into TWRP (whatever version you're using now, new or old)?

Jacobloveskindles said:
stupid question:do i need to be in fastboot because it says i can do it in any bootmode but of course im gonna be in twrp and downgrading
Click to expand...
Click to collapse
Just flash this in recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=1204340&d=1342535659

the kindle will boot into recovery
votinh said:
I'm not an expert on this but let do together. I want to learn something too.
According to the previous post, you asked and soupmagnet already answered that it will install a previous version of TWRP.
Why don't you do that then?
Next question is can you get into TWRP (whatever version you're using now, new or old)?
Click to expand...
Click to collapse
because i don't know if it needs fastboot and yes i can get into twrp

that sounds a bit weird
soupmagnet said:
Just flash this in recovery...
http://forum.xda-developers.com/attachment.php?attachmentid=1204340&d=1342535659
Click to expand...
Click to collapse
i flash a recovery in the recovery?lolwut

Jacobloveskindles said:
because i don't know if it needs fastboot and yes i can get into twrp
Click to expand...
Click to collapse
Well, if you can get into TWRP then why not just flash it
What are you waiting for?
Did soupmagnet or someone already say it? flash either the previous version of TWRP or COTR.

Jacobloveskindles said:
i flash a recovery in the recovery?lolwut
Click to expand...
Click to collapse
I can't believe this is still being discussed.
Yes, you can flash recovery in recovery using a flashable .zip (like the one I posted) or via the command line. And SoupKit will install recovery whether you are booted into fastboot, recovery, or a normally booted device.
You're making this way harder than it needs to be. You could have avoided all of this if you would have just read the guides and tutorials available to you from the start.

srry this took so long
soupmagnet said:
I can't believe this is still being discussed.
Yes, you can flash recovery in recovery using a flashable .zip (like the one I posted) or via the command line. And SoupKit will install recovery whether you are booted into fastboot, recovery, or a normally booted device.
You're making this way harder than it needs to be. You could have avoided all of this if you would have just read the guides and tutorials available to you from the start.
Click to expand...
Click to collapse
That was my final thing.just yeah.thanks for staying with me BTW,know how you said the kfu thing wasn't discussed between this page.that was something I discovered I guess the dev thought we discussed that.I'll give you a thanks

[Q] Will installing new ROM wipe X-Parts CWM?

Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks

Artemicion said:
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Click to expand...
Click to collapse
Yes, if you wipe the system partition there will be no more CWM. For CM10, you need to flash a custom kernel for it to work. This custom kernel will usually come with a CWM recovery so it will not be wiped when you flash a new ROM.
僕のLT18iから送られてきた

Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?

Artemicion said:
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Click to expand...
Click to collapse
Is your bootloader unlocked?
And yes you will have to flash GB ftf using flashtool
Sent from my LT18i

Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks

Artemicion said:
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Click to expand...
Click to collapse
If I am not mistaken the kernel boot img should be inside the ROM zip. Check the ROM zip. Just flash the boot img using fastboot, boot into CWM recovery and flash ROM & gapps.
僕のLT18iから送られてきた

Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks

fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium

Artemicion said:
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
Click to expand...
Click to collapse
You don't need to add -i 0xfce to the command. Just type fastboot flash boot <name of boot image>.img
僕のLT18iから送られてきた

tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Thanks, I'll give that a go, not going to be able to try for a few days now, but will. FYI, I took the line of code I was trying directly from the Cyanogenmod wiki for Anzu

tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks

Artemicion said:
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Click to expand...
Click to collapse
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた

popthosegaskets said:
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Looks to just be "boot.img" to me, no spaces or anything.

Have you tried flashtool?
Sent from my LT18i using xda premium

tangosierra_ said:
Have you tried flashtool?
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
No, guess I'll try that next. As I remember, that's what I used to flash in order to root it ages ago. Thanks

Haven't flashed in over 2 years. Missing anything?

I went to the dark side in April 2016, and haven't flashed anything in about 2 years. Wife's tablet (flo) needs an update, MM is getting laggy though the tablet has always been good to us.
Titanium was getting to be crap around the last time I used it, with problems mostly restoring, does that still hold true? Might just use it to back up a couple apps she uses a lot and just use Play Store to restore the rest. It's not really important, just curious.
Downloading the TWRP app, I know TWRP is installed but willing to bet it needs to be updated and the app can do that.
Tablet is near its EOL, not planning on rooting it if the ROM doesn't come pre-rooted. I have no idea what Magisk is.
So I'm gonna go into TWRP, wipe system, wipe data, wipe cache, wipe dalvik. Flash ROM (going with Lineage 15.1). Now at one point 2-3 years ago the common wisdom was starting to become "flash ROM, boot ROM, reboot to recovery and then flash Gapps." Y'all still doing that? Or can I just flash Gapps right after flashing ROM and reboot then?
Bit nervous as I haven't flashed in a while, but also kind of exciting.

We've got Android 8.1 Oreo now... Working perfectly on our Nexus 7... You should check it out...

Any suggestions for which are the most stable roms to try? I'm in the same boat. I'm on android 6.0.1, stopped flashing things a while ago and it might even be official! But mine's running like a dog so think I wanna try something to jazz it up!

You should try pure Nexus rom based on 7.1.2 for ultimate good battery life. Oreo is Good but battery isn't the greatest.

Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING

ganggreen777 said:
Well i have been rooting for a bit.
My N7 2013 Flo is not rooted. It is unlocked.
I thought i have via adb fastboot put latest twrp on it...but i turn it off (go into bootloader) toggle into recovery...tarp is not there (triangle with red 'i').....
I dont want to go ballistic but I never would have thought I am having such a hard time putting recovery image onto it.
It is stock 6.1
CF root doesn't exist anymore...some say use majisk....that's not working....
Without a recovery tool....(twrp) nothing can be flashed..
AM I MISSING SOMETHING
Click to expand...
Click to collapse
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
Thanks so much for responding back!!!!
Tonight I will follow the steps. I trust it will go fine.
Excited to do this. ......yep I waited this long to root this device

k23m said:
Firstly, your stock 6.1 is ancient and obsolete. Here are detailed instructions to install a modern Android, TWRP and root....
https://wiki.lineageos.org/devices/flo/install
ROM - https://download.lineageos.org/flo
native root solution, no need for CF, Magisk, etc. - https://download.lineageos.org/extras (install addonsu-14.1-arm-signed.zip and activate it in the developer options)
:good:
Click to expand...
Click to collapse
I did the 'install lineageOS on flo and installed TWRP latest. Seem like fastboot went into a slew of commands
and finished. I followed the steps to reboot into recovery and twrp is not there. Android dude opened with red triangle.
I have no clue whats up. I leave it sit, and it reboots into android splash screen and bootsup so i can use the tablet. I guess this is why I am soo perplexed. "Am i missing something?"

ganggreen777 said:
....twrp is not there. Android dude opened with red triangle.
...."Am i missing something?"
Click to expand...
Click to collapse
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html

k23m said:
I think you have missed this step.... "Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install." - https://twrp.me/asus/asusnexus72013wifi.html
Click to expand...
Click to collapse
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device

Kevin_McLaughlin said:
Thank you for 'helping me'......I have googled this combo everywhere and tried it all. Nothing is allowing the tablet to populate into twrp.....
Perhaps its really not fastbooting twrp into the device
Click to expand...
Click to collapse
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this ordecr or else TWRP will be gone again.
Click to expand...
Click to collapse
Why u asking???? Have we chatted b4?¿?
I will do as stated above (I swear I am (thinking) I am doing it as above all the other times. (when you say copy output...is that from the fastboot dialogue? ) ...is it as easy as copy paste ...I dont remember how to copy via adb fastboot...
(Makes me wonder if twrp is really being fastbooted into the n7 2013
Thanks for helping.

k23m said:
Wait, is Kevin_McLaughlin=ganggreen777 ?
Anyway, here is an alternative way:
- fastboot flash recovery twrp-3.2.3-0-flo.img (please copy the output and post it here)
- fastboot reboot-bootloader
- select recovery in the bootloader
That's it, but you must do it in this order or else TWRP will be gone again.
Click to expand...
Click to collapse
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs

ganggreen777 said:
So I did the steps and it appeared. THANKS!!!
I downloaded the latest nightly of the link you told me to go to. I tried to flash it......it didnt flash.
Click to expand...
Click to collapse
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:

beachfl said:
Did you try a factory reset immediately prior to installing it?
Sent from my Asus P027 using XDA Labs
Click to expand...
Click to collapse
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS

ganggreen777 said:
Lol
Hell no....totally forgot.
I will do the next thing you posted....and check back.
THANKS
Click to expand...
Click to collapse
BTW
I am great to go.....thanks very much for helping me thru
---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------
k23m said:
You need to do the following in TWRP:
(Optional, but recommended): Select the Backup button to create a backup.
Select Wipe and then Advanced Wipe.
Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
Go back to return to main menu, then select Install.
Navigate to /sdcard , and select the LineageOS .zip package.
next install the addonsu-14.1-arm-signed.zip (root addon)
and finally GApps (Google Apps) from https://opengapps.org/ - select ARM 7.1 pico
"Note: If you want any Google Apps on your device, you must follow this step before the first boot into Android!"
:highfive:
Click to expand...
Click to collapse
BTW I am great to go... Thanks for sticking thru with me