Develop Bugs

[Recovery] ClockworkMod 3.2.0.0 (R4c) Modded for Internal media [UPDATED 10/6]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ClockworkMod Recovery - Modified for Motorola Xoom​
OK, so this recovery will skip /data/media (Internal storage) when performing nandroid backups and also when you perform a factory reset.
This means that we can now perform nandroid backups without backing up our internal media and removing it everytime you want to do a backup.
Thanks to Bigrushdog and MadIndustries for helping out with the concept of the solution for skipping /data/media.
Also thanks to Koush and all the other developers that have contributed to clockworkmod, without you guys the android world would be completely different.
Thanks also to everyone in #xoom that tested this.
The source code for all changes etc are available through the github repository. The two other projects that have been modified to make this recovery possible can also be viewed through my github account.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
==============================================
General Notes
When I refer to /data/media, this is the same as /sdcard when the xoom is booted into honeycomb. So any data that is stored in here should be untouched by this recovery.
If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard. This will revert to the old way of formatting /data. NOTE: by doing this you will lose everything that you have in /data/media.
Versioning of recovery images:
At the moment I don't have a version number as such, instead each recovery image is timestamped in the format of DDMMYY-HHYY. So the file recovery-solarnz-120511-2030.img was produced on 12 May 2011 at 8:30 PM. This versioning is also shown in recovery when it starts.
==============================================
Downloads
SLOW DOWN AND RELAX
Make sure you download the correct version depending on how you want to flash. I have seen at least two xooms bricked now because they have tried to flash the zip file through fastboot.
Recovery Zip (solarnz-R4c-100611-1150) FLASHED THROUGH CWM
MD5: 1ad409db4030635734b27df02b7e7c1a
Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT
MD5: 20575d4b62bf697f77abca9093877ea3
==============================================
Installation Instructions
Method 1 Flashing through CWM
Download the recovery zip file
Place the recovery zip on the sdcard where clockworkmod can read it.
Reboot into recovery using "adb reboot recovery" or any other method
In recovery, select flash zip from sdcard and select the recovery zip you downloaded
Sit back and relax while recovery flashes the new recovery and reboots into it.
Click to expand...
Click to collapse
Method 2 Without CWM
Download the recovery image (not the zip file)
Pull up your command prompt, then
Code:
adb reboot bootloader
fastboot flash recovery recovery-solarnz-XXXXXX-XXXX.img
fastboot reboot
Let your Xoom boot up. Then to check out your shiny new recovery,
Code:
adb reboot recovery
Click to expand...
Click to collapse
Also, you can grab Rom Manager or QuickBoot from the market for easy access to recovery.
==============================================
Changelog
Code:
[url=http://bit.ly/k7cZxJ]3.2.0.0 (R4c-100611-1150)[/url]
- Rebuilt recovery, the previous recovery was built off of bad device files.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4b-060611-1300-cwm.zip]3.2.0.0 (R4b-060611-1300)[/URL]
- Disabled partitioning the sdcard as per request.
[url=http://dl.dropbox.com/u/13093938/XDA/Recovery/recovery-solarnz-R4-050611-1515-cwm.zip]3.2.0.0 (R4-050611-1515)[/URL]
- Included changes from koush's sources upto clockworkmod 3.2.0.0
- Implemented Advanced backup. This allows you to choose what partitions you want to backup.
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-120511-2030.zip]3.0.2.8 (120511-2030)[/url]
- Fixed mounting the sdcard for some users
[url=http://dl.dropbox.com/u/13093938/recovery-solarnz-080511-1630.img] 3.0.2.8 (080511-1630)[/URL]:
- Modified to skip /data/media or /sdcard in nandroid backups.
- Modified formatting /data to remove directories and folders so we can keep media.
- Place a file called eraseData in the clockworkmod directory on your EXTERNAL sdcard to revert to the normal restoration method.

Great job guys!!!!
Sent from my HTC HD2 using XDA Premium App

You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.

Win
Sent From My Evo

Great job folks!!!
We've gotten used to BRD's awesome formatting of his posts and super clear instructions, would be real nice if we can get this on the new sticky

bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?

jland22 said:
might be a stupid question but just to clarify: we would obviously not want to flash any recoveries in rom manager thus not having any need for rom manager at at this point correct?
Click to expand...
Click to collapse
Rom manager is still nice as you can quickly reboot to recovery etc from it. It also allows you to select the operation to do in recovery and then restart it will automatically restart and perform the action.
If you flash recovery from Rom Manager, you will end up with the official 3.0.2.5 recovery from Koush that doesn't contain the method of skipping /data/media

bigrushdog said:
You da man solarnz! Also, you can grab step 1 from my 3.1 thread. That zip will flash recovery from recovery! Mods, please unsticky my Recovery thread and lock and replace with this one. This is recovery we will support going forward.
Click to expand...
Click to collapse
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App

lokko21 said:
What's the difference between this and the one on bigrushdog thread. (3.1)
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.

What folder do i need to flash this too?

b0ricua said:
No difference, BRD used this modified 3.2.8 in his first step on that thread. But this will be the go-forward recovery from now on.
Click to expand...
Click to collapse
Gotcha so I'm cool, thanks.

ok just flashed, looks good

Solarnz, thanks for formatting the OP and adding clear instructions!!
You da man!

very cool, but would it be complicated to just make an "exclude" menu before backing up? That way people can just exclude whatever they want ...

thanks to everyone who contributed. We dont always think about how great CWM is and all the wonderful things it does for us until we dont have it anymore I didnt like the feeling of walking around with that stock recovery

running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.

maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?

Prod1702 said:
running into a problem. I have a wifi only xoom. I had the old 3.0.2.8 recovery installed which i still had after 3.1 update no problems with it at all. I just flashed the 3.0.2.8 one using fastboot but now when i reboot into recovery. All i see is the android with the exclamation mark i do not see clockwork. I have reflash more then once with no luck still.
Edit: wanted to add that if i flash the clockwork from Rom manger which i see is the version 3.0.2.5 i am able to do a adb reboot recovery into recovery with no problems.
Edit2: for some reason the zip flashing in the old recovery works fine and updated to the new recovery. no clue why fastboot is not working. I tried fastboot 5 times every flash said it finished fine but it boots with a android and a exclamation mark. only the zip flashing in recovery works for me.
Click to expand...
Click to collapse
Ok, I'm assuming you are on android 3.1 without a modified kernel.
The issue you are having is that with the default boot image, it flashes back the stock recovery every single time you reboot.
Code:
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
(Thanks Berzerker7)
ltracte said:
maybe this is a stupid question, but i dont even see a "media" folder on my xoom. there are folders for music and video. i have my own folder for movies, one for comics, ect. do i have to create a media directory and move everything into it in order to make sure that it doesnt get included? and if so, where does it go?
Click to expand...
Click to collapse
Ok. on our xooms, /sdcard is actually a symlink (think of a shortcut) to /data/media.
So when I say /data/media, you can think of /sdcard (the internal storage).

random one again - will this be available via ROM Manager? it's still 3.0.2.5 there
thanks!

E: can't mount /sdcard/update.zip
or error mounting /sdcard
anyone has encountered this problem plz?
thks

TWRP v2.4.4.0 help

finally installed twrp v2.4.4.0 successfully on my kindle fire hd 8.9
but when it boots up i get the orange kindle fire logo the blue logo, back to the orange logo and then it loads up twrp.
can any one help as im trying to install cm10.1 and gapps but the files are not on my kindle sdcard and my kindle wont load the original os to allow me to copy the files... please help. thanks

First Information
Code:
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
Code:
this does NOT clear your sdcard space
have you done ?
Second Information
Code:
Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.
mfg
J-P

kodie. said:
finally installed twrp v2.4.4.0 successfully on my kindle fire hd 8.9
but when it boots up i get the orange kindle fire logo the blue logo, back to the orange logo and then it loads up twrp.
can any one help as im trying to install cm10.1 and gapps but the files are not on my kindle sdcard and my kindle wont load the original os to allow me to copy the files... please help. thanks
Click to expand...
Click to collapse
If you have TWRP but do not have CM10.1 or gapps on the device, you can press advanced and ADB sideload - it works in 2.4.4.0.
http://teamw.in/ADBSideload
I've reloaded three times now and each time - even though I moved CM10.1 and gapps to sdcard/download, TWRP couldn't not find the files - I had to sideload each time.
Connect the USB cable to your PC, navigate in TWRP to advanced then start an ADB sideload. On the PC, you'll use
Code:
adb sideload cm-10.1-20130514-UNOFFICIAL-jem.zip
to push the file. The TWRP will automatically import the file, save it as sideload.zip, and then install it.

GermanJPL said:
First Information
Code:
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
Code:
this does NOT clear your sdcard space
have you done ?
Second Information
Code:
Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.
mfg
J-P
Click to expand...
Click to collapse
hey if your still having problems rooting and installing cm10.1. check out this thread, it quick easy and simple. be sure to read the it completely first before you start. good luck, hope this helps you out like you did for me. http://forum.xda-developers.com/showthread.php?t=2277105

[solved] CWM: Can't install .zip from /sdcard ("Couldn't open directory")

Hey everyone,
I completely wiped my phone (did a format of data, system etc. on CWM, wiped dalvik/cache etc.). Now I'm stuck with CWM and want to install a rom. I tried to put the .zip on the phone via "adb push /data/media". However, after doing that when I select "choose zip from /sdcard" it says "Couldn't open directory. No files found.".
If I open the shell via adb, I can find the /data/media folder as well as /sdcard, however, I can't cd into it. But I can see (by the folder-size) that the folder contains the .zip.
Any ideas? Is there maybe another way of installing a rom via CWM than through a zip on /sdcard?
Thanks!
*edit:
adb sideload isn't working either

Go to "install zip via sideload" in CWM (if it's not there, update your CMW first!), connect to PC, and run "adb sideload *PATH-TO-ROM-ON-YOUR-PC*". If your storage is not corrupted then it should load a ROM to your storage AND immediately flash it.
Sent from Google Nexus 4 @ CM11

I tried it through sideload.
After the transfer finished it doesn't install the .zip automatically. However, when I go back in CWM it starts installing but fails with "E: Can't open /tmp/update.zip (bad)"

I solved the problem by flashing TWRP recovery and doing a full data wipe (not just the normal one).

Unable to install TWRP

Hi
I was running stock European android, unlocked bootloader and rooted with trwp
I decided to install lineage 15.1 plus gapps which I have up and running, used adb push to install
What I can't do is reinstall trwp, neither image or zip as always getting error messages, endpoint something or other... Tried fastboot, adp push... Lineage recovery..
I reckon this might be down to the fact that I didn't format before the install getting rid of the encryption
So any ideas how to install trwp so that i can start correctly all over again
The lineageo recovery doesn't give any real options concerning formatting
Running a moto force z2

What command are you running to send the TWRP image to the device in fastboot? You should be in bootloader mode and you cannot flash the TWRP image to the device. Rather, you should use
Code:
fastboot boot twrp-3.x.x-x.img
Once you boot the TWRP image, you can install it with more persistence using the zip installer from the TWRP website. Since this will alter the boot image, you need to flash Magisk after TWRP if you want root.

Hi
did this
adb devices
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
booting into trwp, wiped all - ok
Flashed from trwp lineage 15.1 - ok
Flashed Gapps - NOT ok
Flashed Magisk -NOT Ok
booted into lineage, installed Magisk app and reflashed TRWP using
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
Flashed Magisk from trwp this time - Ok
Now what do I do to get TRWP to stay inplace as still only lineage recovery, though I flashed the image using the Magisk app
then I did
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
installed mindthegapps using trwp, cleared dalvic et cache, but when booting stuck on verification google informations and can't get into google play
rebooted into recovery, again lineasge, cleared cache and system, when rebooted Gapps worked just nicely
so still no TRWP in permanent place (can live without if need be, but would like it) otherwise all is running
This is long winded but might be of use to others as see many questions like mine on various forums
thanks for your help

minty95 said:
Hi
did this
adb devices
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
booting into trwp, wiped all - ok
Flashed from trwp lineage 15.1 - ok
Flashed Gapps - NOT ok
Flashed Magisk -NOT Ok
booted into lineage, installed Magisk app and reflashed TRWP using
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
Flashed Magisk from trwp this time - Ok
Now what do I do to get TRWP to stay inplace as still only lineage recovery, though I flashed the image using the Magisk app
then I did
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
installed mindthegapps using trwp, cleared dalvic et cache, but when booting stuck on verification google informations and can't get into google play
rebooted into recovery, again lineasge, cleared cache and system, when rebooted Gapps worked just nicely
so still no TRWP in permanent place (can live without if need be, but would like it) otherwise all is running
This is long winded but might be of use to others as see many questions like mine on various forums
thanks for your help
Click to expand...
Click to collapse
These are the steps to follow to get lienage 15.1 to work flawless. I went through this so follow closely.
1) Start out with full stock again.
2)Power off phone, and enter fastboot
3)Fastboot boot twrp-3.2.3-2-nash.img
4)Go to wipe and Choose format data
5)Go back to main screen, choose wipe, choose advance wipe, and wipe system only nothing else
6)Go back to main screen, choose install. Install Lineage 15.1 Once finished do NOT reboot.
7)Go back to main, Install and, flash twrp3.2.3-2.zip
8)Go back to main screen, choose reboot, reboot back into recovery.
9) Next this is important. Flash MIndTheGapps first then flash the SprintFix.zip (If you do not do it this way, you will only get 3G not LTE)
10)Go to reboot, reboot back into recovery, the boot system..
If you follow this it will work no problem.. If you don't flash the twrp-3.2.3-2-nash.zip First reboot back into recovery. Then MindTheGapps, and SprintFix won't work. What ever you do, do not skip the flashing the twrp3.2.3-2-nash.zip, or you will enter Lineage recovery, and it dose not work worth a dam.
After all that, enable Developer Option in setting, turn on USB debugging, Then reboot back to recovery and flash the addonsu-15.1-arm64-signed.zip. When back to system go back to developers option, scroll down Root Access and choose your option.. I choose Apps and ADB.

Si I tried again,
Still can't get TRWP to stay
adb devices
adb reboot bootloader
fastboot boot twrp-3.2.3-2-nash.img
booted into TRWP recovery
installed TRWP from zip filet 'twrp-installer-nash-3.2.2-2.zip'
No error message said installing in, slots 1 &2
rebooted into recovery , TRWP gone again recovery lineage by default again
Now I really lost.....
any ideas ?

I just unlocked my Z2 Force, and when I try "fastboot boot twrp-3.3.1-0.img" it just sits there.
It shows:
Sending 'boot.img' (33504 kb)
and it will sit there for literal hours.
Any ideas?

mikiemc73 said:
I just unlocked my Z2 Force, and when I try "fastboot boot twrp-3.3.1-0.img" it just sits there.
It shows:
Sending 'boot.img' (33504 kb)
and it will sit there for literal hours.
Any ideas?
Click to expand...
Click to collapse
Use oem cable, change usb ports. Use 2.0 ports if you have them.

I'm in the same situation as you
mikiemc73 said:
I just unlocked my Z2 Force, and when I try "fastboot boot twrp-3.3.1-0.img" it just sits there.
It shows:
Sending 'boot.img' (33504 kb)
and it will sit there for literal hours.
Any ideas?
Click to expand...
Click to collapse
please help if you've found any solution

PHP:
adb reboot bootloader
fastboot boot '(drag n drop twrp img here)

41rw4lk said:
PHP:
adb reboot bootloader
fastboot boot '(drag n drop twrp img here)
Click to expand...
Click to collapse
no use, it says downloading 'boot.img'
And says FAILED in about 40 secs and the phone gets disconnected.
Am I missing any step in the bootloader before executing command??
or anything else??
Please help
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Rooting problems

I do this to root my firestick: https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-tv-stick-4k-mantis.3978459/
I succeeded, but i also wanted to disable OTA and install Magisk. So i watch this tutorial: https://miguelmota.com/blog/rooting-a-fire-tv-stick-4k/
But, i stuck in page when i need to: # adb devices and # adb shell.
Advices??
I also have a question, can i check if bootloader if unlocked?
Also, what i want now is to have custom launcher or custom rom and to enable ntfs and exfat support. Do i need root for this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to check is twrp installed?
Also, can i now assemble firestick?

stefss said:
I do this to root my firestick: https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-tv-stick-4k-mantis.3978459/
I succeeded, but i also wanted to disable OTA and install Magisk. So i watch this tutorial: https://miguelmota.com/blog/rooting-a-fire-tv-stick-4k/
But, i stuck in page when i need to: # adb devices and # adb shell.
Advices??
I also have a question, can i check if bootloader if unlocked?
Also, what i want now is to have custom launcher or custom rom and to enable ntfs and exfat support. Do i need root for this?
View attachment 5146395
How to check is twrp installed?
Also, can i now assemble firestick?
Click to expand...
Click to collapse
@stefss Hello my friend, Everything is looking good this is normal, you are in twrp within shell (root only becomes available once you install your rom)
TWRP is waiting commands
So.... what we do next is tell him..
Type : exit
adb push /path/to/pre-rooted mantisrom /sdcard
adb push /path/to/Magisk-v21. 1.zip /sdcard
Then you do
Type :
adb shell
You'll see the # sign appear again
Then type:
twrp wipe data
twrp wipe /system
twrp wipe dalvik
twrp wipe cache
Then you're ready to install your rom & Magisk
Type:
twrp install (copy/paste name of Rom.zip)
twrp install Magisk-v21.1.zip
Your stick will then install whatever rom and then flash/update magisk.
Next you goto main Twrp screen and select Reboot system
Then sort magisk permissions and enable adb when you have completed registration process.
go back to terminal/command prompt and
Type :
adb shell
su (accept permission, you may have to go into magisk and select the toggle for shell if you cannot navigate to "grant" on the popup)
Then we want to
Type :
pm disable com.amazon.tv.forcedotaupdater.v2
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.device.software.ota
This disables ota updates
Regards

Bertonumber1 said:
@stefss Hello my friend, Everything is looking good this is normal, you are in twrp within shell (root only becomes available once you install your rom)
TWRP is waiting commands
So.... what we do next is tell him..
Type : exit
adb push /path/to/pre-rooted mantisrom /sdcard
adb push /path/to/Magisk-v21. 1.zip /sdcard
Then you do
Type :
adb shell
You'll see the # sign appear again
Then type:
twrp wipe data
twrp wipe /system
twrp wipe dalvik
twrp wipe cache
Then you're ready to install your rom & Magisk
Type:
twrp install (copy/paste name of Rom.zip)
twrp install Magisk-v21.1.zip
Your stick will then install whatever rom and then flash/update magisk.
Next you goto main Twrp screen and select Reboot system
Then sort magisk permissions and enable adb when you have completed registration process.
go back to terminal/command prompt and
Type :
adb shell
su (accept permission, you may have to go into magisk and select the toggle for shell if you cannot navigate to "grant" on the popup)
Then we want to
Type :
pm disable com.amazon.tv.forcedotaupdater.v2
pm disable com.amazon.device.software.ota.override
pm disable com.amazon.device.software.ota
This disables ota updates
Regards
Click to expand...
Click to collapse
Thank you, i turn off everything, i will turn on again.
But i am confused, where to start right now?
So i will just start to type in command?
adb push /path/to/pre-rooted mantisrom /sdcard
adb push /path/to/Magisk-v21. 1.zip /sdcard
Or something else? Sorry my english is not perfect so i want to be sure.
Can i assemble firestick now?

stefss said:
Thank you, i turn off everything, i will turn on again.
But i am confused, where to start right now?
So i will just start to type in command?
adb push /path/to/pre-rooted mantisrom /sdcard
adb push /path/to/Magisk-v21. 1.zip /sdcard
Or something else? Sorry my english is not perfect so i want to be sure.
Can i assemble firestick now?
Click to expand...
Click to collapse
Turn on and type adb devices
If stick shows up (it probably won't) type adb reboot recovery
If normal amazon loads up activate adb in developer options then type above.
Failing that if rom doesn't boot you will need OTG cable to access recovery, just plug otg into stick and use a mouse to cancel boot and reboot to recovery
Then follow my instructions as per above (last post)

I do this, and i install magisk, but i dont see there is twrp?

stefss said:
I do this, and i install magisk, but i dont see there is twrp?
Click to expand...
Click to collapse
Did your device boot to fireos normal Rom, once you've enabled adb and accepted pc permission you should be able to type, adb reboot recovery and device should goto twrp recovery. You have to boot into TWRP using commands it won't appear on your fireos rom anywhere
When you get to twrp don't switch the device off as this causes (in most cases) the device to brick.
So where are you at now? What is on
your screen
Also note you don't have to use the fireiso kamikiri anymore now that exploit is done, a simple shell or terminal will suffice from your normal windows/linux with adb installed ofc

My device boot to fire os normal. But i see magisk app.

stefss said:
My device boot to fire os normal. But i see magisk app.View attachment 5147291
Click to expand...
Click to collapse
This is perfect, you can up date the magisk app if you have Internet connected. NEVER UPDATE THE ONE WITH THE TICK VIA THE APP. OK (You have to download the newest zip 21.1 and flash via twrp or you will brick device if you try to update from the app) so update magisk app (you may need to goto manage installed applications and give magisk "allow" permission) then you want to goto adb in settings developer options, enable adb and apps from unknown sources, reboot and enter adb on your pc again (terminal/command prompt) and let stick boot up then type adb reboot recovery.
After you do this
You can then follow the instructions to push a pre-rooted rom and Magisk 21.1.zip to the stick /sdcard remember? adb push nameofyourrom.zip /sdcard
And adb push Magisk-v21.1.zip /sdcard
Then when your in twrp
adb shell
twrp wipe cache
twrp wipe data
twrp wipe /system
twrp wipe dalvik
Then
adb shell
twrp install nameofyourrom.zip
twrp install Magisk-v21. 1.zip
twrp wipe cache
twrp wipe dalvik
reboot

But how to flash via twrp if i cant see twrp?
And how to flash apps with twrp?
I download zip on firestick, but what to do next?
What i exactly need to write in adb?
adb devices and the adb reboot recovery?
I want to install this, but i am not sure how exaclty to do this:
[Magisk][Module] Amazon FireTV4k NTFS/F2FS/EXT4/exFAT OTG support
Warning !!! Use this module on your own risk !!! I can't be held responsible for any kind of damage or data loss !!! Version 1.3 and higher requires my custom kernel 6.2.7.1_v3 or higher + Selinux magisk module from the kernel thread Magisk 20.3...
forum.xda-developers.com
Again, sorry but my english is not perfect so i want to ask about everything a couple of times to be sure that i will not make a mistake.

stefss said:
But how to flash via twrp if i cant see twrp?
And how to flash apps with twrp?
I download zip on firestick, but what to do next?
What i exactly need to write in adb?
adb devices and the adb reboot recovery?
I want to install this, but i am not sure how exaclty to do this:
[Magisk][Module] Amazon FireTV4k NTFS/F2FS/EXT4/exFAT OTG support
Warning !!! Use this module on your own risk !!! I can't be held responsible for any kind of damage or data loss !!! Version 1.3 and higher requires my custom kernel 6.2.7.1_v3 or higher + Selinux magisk module from the kernel thread Magisk 20.3...
forum.xda-developers.com
Again, sorry but my english is not perfect so i want to ask about everything a couple of times to be sure that i will not make a mistake.
Click to expand...
Click to collapse
Yes you can do the addons later but first you have to get the basics done.
Once you have granted magisk the permission in installed apps and enabled developer options/unknown sources. All you need to do is connect to your stick by plugging the USB end into pc and type adb devices. Then a screen will popup, accept the request, (you may need to open magisk and allow shell root permission on the little shield at bottom of magisk app)
When you have done this and flashed your new pre-rooted rom or whatever.
Then we can worry about atv addons magisk modules.
So once you've done the above you want to open up a command prompt and type adb reboot recovery. You have to do this to get into the twrp GUI. Then you can install whatever you want but please note you will only see TWRP when you do what I've said
1. From fireos goto settings>my firetv >developer options> enable adb/unknown sources
2.open your terminal/command prompt on pc and make sure your firestick is plugged into a USB on pc
3. Type : adb reboot recovery
4.your device should now reboot to twrp, first wipe the stick data dalvik cache system from advanced wipe.
5. In twrp if you have downloaded the rom/magisk to stick then goto install>downloads>nameofyourrom
6. Repeat the same process if you've downloaded magisk 21.1.zip there too
7.if you have pushed step 5/6 to /sdcard then they should be there as soon as you select install in twrp.
8. Install the zip files.
9. Wipe cache dalvik if you want
Everything you need to do is in my posts mate, read over them and you shall succeed

Bertonumber1 said:
This is perfect, you can up date the magisk app if you have Internet connected. NEVER UPDATE THE ONE WITH THE TICK VIA THE APP. OK (You have to download the newest zip 21.1 and flash via twrp or you will brick device if you try to update from the app) so update magisk app (you may need to goto manage installed applications and give magisk "allow" permission) then you want to goto adb in settings developer options, enable adb and apps from unknown sources, reboot and enter adb on your pc again (terminal/command prompt) and let stick boot up then type adb reboot recovery.
After you do this
You can then follow the instructions to push a pre-rooted rom and Magisk 21.1.zip to the stick /sdcard remember? adb push nameofyourrom.zip /sdcard
And adb push Magisk-v21.1.zip /sdcard
Then when your in twrp
adb shell
twrp wipe cache
twrp wipe data
twrp wipe /system
twrp wipe dalvik
Then
adb shell
twrp install nameofyourrom.zip
twrp install Magisk-v21. 1.zip
twrp wipe cache
twrp wipe dalvik
reboot
Click to expand...
Click to collapse
I messed up with something, i almost finished, and go to twrp wipe dalvik, and then to adb shell, and i get
error: adb not found. I try a couple of times, and i still get same message, so i wanted to reboot and start again, but now i am stuck in fire tv logo, help?
For now i just want to update magisk, next tim, when i do this, i will try to do other things.
Help?

stefss said:
I messed up with something, i almost finished, and go to twrp wipe dalvik, and then to adb shell, and i get
error: adb not found. I try a couple of times, and i still get same message, so i wanted to reboot and start again, but now i am stuck in fire tv logo, help?
For now i just want to update magisk, next tim, when i do this, i will try to do other things.
Help?
View attachment 5147335
Click to expand...
Click to collapse
Did you reboot twrp after you wipe? You have to install pre-rooted rom first mate that's why I didn't write "reboot" until the end of instructions. If you reboot the stick without an installed rom the device will brick.
What exactly did you do tell me step by step?
My instructions must not be clear enough or there is language misunderstanding I do apologise for this.
But we will fix it is easy to fix
Try typing : adb reboot recovery once more
You have to understand TWRP isn't an app as such you can access on the rom via menus.
Twrp is a recovery that the unlock process flashes to the stick to enable you to install roms etc.
In order to access TWRP you have to follow those instructions in the post #8 above this one to the letter.
If adb reboot recovery doesn't work for you
Try an OTG cable and mouse to enable recovery menu and select cancel to goto twrp.
If these steps fail then you'll have to do the short method again (which probably would've been quicker).
Once you do the short again via FireISO and get to twrp DO NOT REBOOT TWRP UNTIL YOU HAVE PUSHED ROM AND LATEST MAGISK TO SDCARD AND HAVE INSTALLED AS PER POST#2 (I'm not shouting I'm simply stressing how important this is) I cannot stress thatEnough I have bricked devices many times myself. But you will get this sorted mate once you get the hang of the commands

Bertonumber1 said:
Did you reboot twrp after you wipe? You have to install pre-rooted rom first mate that's why I didn't write "reboot" until the end of instructions. If you reboot the stick without an installed rom the device will brick.
What exactly did you do tell me step by step?
My instructions must not be clear enough or there is language misunderstanding I do apologise for this.
But we will fix it is easy to fix
Try typing : adb reboot recovery once more
You have to understand TWRP isn't an app as such you can access on the rom via menus.
Twrp is a recovery that the unlock process flashes to the stick to enable you to install roms etc.
In order to access TWRP you have to follow those instructions in the post #8 above this one to the letter.
If adb reboot recovery doesn't work for you
Try an OTG cable and mouse to enable recovery menu and select cancel to goto twrp.
If these steps fail then you'll have to do the short method again (which probably would've been quicker).
Once you do the short again via FireISO and get to twrp DO NOT REBOOT TWRP UNTIL YOU HAVE PUSHED ROM AND LATEST MAGISK TO SDCARD AND HAVE INSTALLED AS PER POST#2 (I'm not shouting I'm simply stressing how important this is) I cannot stress thatEnough I have bricked devices many times myself. But you will get this sorted mate once you get the hang of the commands
Click to expand...
Click to collapse
You dont need to apologize, its my bad.
The problem is adb just dont recongnize my firestick, so i get mouse i try to wipe.
But still problem its the same. Its still stuck in fire tv logo.
I want to clarify what i want. Because i dont find any custom rom that i want, i want to install custom kernel, this:
[KERNEL][FireTV Stick 4K] Custom Kernel For AFTV 4k - 6.2.9.4
Warning !!! Use this kernel on your own risk !!! I can't be held responsible for any kind of damage or data loss !!! Features: SDCARDFS exFAT and F2FS support Wireguard Advanced TCP options CIFS and NFS support Insecure ADB v1...
forum.xda-developers.com
And later this: https://forum.xda-developers.com/t/...v4k-ntfs-f2fs-ext4-exfat-otg-support.3991981/
And later when finish this to add custom launcher, and basically thats all.

stefss said:
You dont need to apologize, its my bad.
The problem is adb just dont recongnize my firestick, so i get mouse i try to wipe.
View attachment 5147359
But still problem its the same. Its still stuck in fire tv logo.
I want to clarify what i want. Because i dont find any custom rom that i want, i want to install custom kernel, this:
[KERNEL][FireTV Stick 4K] Custom Kernel For AFTV 4k - 6.2.9.4
Warning !!! Use this kernel on your own risk !!! I can't be held responsible for any kind of damage or data loss !!! Features: SDCARDFS exFAT and F2FS support Wireguard Advanced TCP options CIFS and NFS support Insecure ADB v1...
forum.xda-developers.com
And later this: https://forum.xda-developers.com/t/...v4k-ntfs-f2fs-ext4-exfat-otg-support.3991981/
And later when finish this to add custom launcher, and basically thats all.
Click to expand...
Click to collapse
@stefss Yes you are in twrp, you have selected all the correct boxes now slide the slider to wipe,
once you have done that goto twrp main screen (don't reboot, just use home icon or back icon) and then select install
If you have the rom and magisk zip files on the stick /sdcard already select and install by sliding the slider again.
Then wipe cache and dalvik
You wil see twrp screen saying installing
system img
Installing vendor image
(this takes about 90 seconds and then magisk will flash straight after it flashes amazon prerooted rom)
Then when you are sure it's installed
Reboot
Ps I would not mess with kernels etc until you have learned some more about terminal/ adb processes we all have to start somewhere buddy. If you note the developer has basically slapped a warning on this Addon as it can/may cause your device damage. This kernel adjustment is only if you choose to use a particular addon and can cause serious problems to your device if you don't know what you're doing. I'd stick with prerooted rom just now until you learn the mechanics of the root/adb/terminal integration and how the fireos/bootloader etc works. That's just IMO though it's your device

But i dont want any rom to install. I install magisk 21.1 from TWRP and now just want to back to normal and then install kernel and launcher.
The problem is i cant install anything because i cant connect with adb, so i cant add new things to firestick now. Maybe i can put usb drive and than install from it? Just add kernel to usb drive and then install from twrp?
Will this fix things?

No
stefss said:
But i dont want any rom to install. I install magisk 21.1 from TWRP and now just want to back to normal and then install kernel and launcher.
The problem is i cant install anything because i cant connect with adb, so i cant add new things to firestick now. Maybe i can put usb drive and than install from it? Just add kernel to usb drive and then install from twrp?
Will this fix things?
Click to expand...
Click to collapse
No, you are missing what I am saying. TWRP is what installs everything here, adb is only used to convey the files to TWRP. So forget about everything and focus on using TWRP to install your Prerooted mantis rom(you have to do this first)
Twrp is Used to install roms, zips such as magisk and we need to use this to install rom and magisk OK?
You have just wiped your stick so you must push a prerooted mantis rom to your stick along with latest magisk and install those if you want to do anything
A failure to do so will result in a possible brick (again)
to do that if you have a USB hub to plug into otg cable so you can maybe put your mantis rom and magisk onto that and select external storage and just install that way to skip adb pushing?

Bertonumber1 said:
No
No, you are missing what I am saying.
Twrp is Used to install roms, zips such as magisk.
If you don't want to install a rom and have flashed magisk 21 then just goto
Reboot >system but you must have a a fireos rom installed to do this which is my point.
You have just wiped your stick so you must push a prerooted mantis rom to your stick along with latest magisk and install those if you want to do anything
A failure to do so will result in a possible brick (again)
Click to expand...
Click to collapse
So i must find a prerroted rom to install?
Do u have suggestions? Do u know any with custom launcher?

stefss said:
So i must find a prerroted rom to install?
Do u have suggestions? Do u know any with custom launcher?
Click to expand...
Click to collapse
Download this https://www.mediafire.com/file/8pe6v9n3wvqipbx/mantis-6.2.7.1-rooted_r1.zip/file
This is the latest
Install this and magisk latest then we'll install launcher OK?
Let me know when you've rebooted and completed the registration process, and have enabled adb debugging/apps from unknown sources in settings.

I was thinking to instal 6.2.7.3 this?
Because its removed all apps i dont use.
Fire TV Stick 4K (mantis) Debloated Rom 6.2.7.1 93/6.2.7.7
Debloated Rom For The Fire TV Stick 4K 6.2.7.1 93/6.2.7.7 Revised NOTE: Firmware versions after 6.2.7.7 will not work with this debloated rom. It's been a few months since I've updated this guide so be cautious with installing this. The latest...
forum.xda-developers.com

stefss said:
I was thinking to instal 6.2.7.3 this?
Because its removed all apps i dont use.
Fire TV Stick 4K (mantis) Debloated Rom 6.2.7.1 93/6.2.7.7
Debloated Rom For The Fire TV Stick 4K 6.2.7.1 93/6.2.7.7 Revised NOTE: Firmware versions after 6.2.7.7 will not work with this debloated rom. It's been a few months since I've updated this guide so be cautious with installing this. The latest...
forum.xda-developers.com
Click to expand...
Click to collapse
Yeah sure go for it, it's your stick mate, I'm only advising what to do to get you up and running.
Just be sure to follow skel40 instructions for the Debloated 6.2.7.3 Twrp install ie wipe cache, system, dalvik etc etc