I am not responsible for bricked devices,
This is a port of Ubuntu Touch for the LG V20 T-Mobile h918 variant. Not yet stable.
Before install halium-boot.img backup only your boot partition. You can restore your current system after try Ubuntu touch. Ubuntu touch will be install in data partition not in system partition.
Youtube :
Sources:
Kernel:
https://github.com/walidham/android_kernel_lge_msm8996/tree/halium-7.1
Device:
https://github.com/walidham/android_device_lge_h918/tree/halium-7.1
https://github.com/walidham/android_device_lge_msm8996-common/tree/halium-7.1
Manifest file
https://github.com/walidham/lge_manifest/tree/master
Status
Working:
Audio
Calling
SMS
4G
Wifi
GPS
Vibration
Orientation sensor
Missing:
Video recording/decoding
Bluetooth
Flash light
ADB/MTP
Libertine
camera
fingerprint
There are two methods to install Ubuntu Touch
Method 1 : unofficial installation with TWRP
1- Download zip file UT TWRP
2- push it in internal storage or sdcard
3- backup up your current boot partition (to restor it later if you want return to android rom)
4- install zip file, make sure your data partition is ext4 (option if you want fresh install you can wipe data partition)
5- rebbot
Note : password is "1111"
Method 2 : official installation/ hard for newbie
NOTE: As the LGV20 aren't community devices yet, the install process may be a little "non-noobie-friendly"
Install twrp on your device, format data partotion to ext4
Download the latest precompiled system.img and halium-boot.img from : halium-boot
Download the JBB's halium install script
Download either the regular rootfs or the Edge one
While on TWRP:
Code:
halium-install -p ut the_rootfs_you_choose.tar.gz system.img
While on TWRP:
Code:
adb shell 'mkdir /a; mount /data/rootfs.img /a; echo manual | tee /a/etc/init/rsyslog.override; umount /a; sync'
While on TWRP: install halium-boot.img (on boot partition)
Then reboot
Connect to phone with ssh
Code:
ssh [email protected]
When entering in ssh run those commands:
Code:
$ sudo -i
$ mount -o remount,rw /
$ cat /var/lib/lxc/android/rootfs/ueventd*.rc | grep ^/dev | sed -e 's/^\/dev\///' | awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/etc/udev/rules.d/70-h918.rules
$ reboot
If you want suport this project you can donate
Edited : 03-09-2022 :
Now H910 is supported,
For LG V20, i finished the port for H910, its beta version need more test and fixe bugs.
Download link : https://www.androidfilehost.com/?fid=14871746926876820212
Installatio:
1- backup your data and boot partition. System partition you can take it, we not use it.
2- Download ubuntu-touch-h910-01-01-2020.zip
3- Install the zip
4- Rebbot
excellent sir
Got Camera work, but without video record, just take photo on 12mb max
i want to try ubuntu. can you make more detail about instal ubuntu.
because in step 1 . always like this
not found.
thank you
Tried
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
nickhaven said:
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
Click to expand...
Click to collapse
Can you tell to me how to Input step 1 in twrp?
In my device every want to input halium-boot always not found
nickhaven said:
Very little would need to be fixed to get me to use this ROM full time. GREAT WORK!!!!!!
Excited to see this rom/OS take off. Got this loaded on my phone, love the OS, but found a few issue (might be my fault).
Slow but mostly usable.
Can't use keyboard in Settings > Accounts. Configuring NextCloud, can't type anything in at all. Would have been way more usable if i could configure the accounts.
Other places didn't toggle keyboard when selecting a text field.
If anyone else is or is not having those issue, please let me know as I might have done something wrong.
Calls, messaging, tethering all work great
Is there a debug that Ubuntu Touch uses. Doesn't look like it uses JournalCTL. I would like to see the issue in the debug if possible to see if there is a way i can help.
AGAIN, GREAT WORK!!! AMAZING STUFF!!!
Click to expand...
Click to collapse
try to fix display scalling
1- when system boot connect to the phone via ssh
ssh [email protected]
Code:
sudo -i
cd /etc/ubuntu-touch-session.d
nano h918.conf
add this lines
Code:
GRID_UNIT_PX=29
QTWEBKIT_DPR=2.5
NATIVE_ORIENTATION=portrait
FORM_FACTOR=handset
save file and reboot
For debug
Code:
cat /var/log/syslog
dmesg
sudo /system/bin/logcat
raf21 said:
Can you tell to me how to Input step 1 in twrp?
In my device every want to input halium-boot always not found
Click to expand...
Click to collapse
in twrp, select install -> clique button install image (at the bottom)
select halium-boot.img (you must copie from pc to your phone)
walidham said:
in twrp, select install -> clique button install image (at the bottom)
select halium-boot.img (you must copie from pc to your phone)
Click to expand...
Click to collapse
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
raf21 said:
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
Click to expand...
Click to collapse
Look at halium-install link
halium-install is done on a linux pc/livecd/virtual machine that has the following installed
qemu-user-static
qemu-system-arm
e2fsprogs
simg2img
sudo
binfmt-support
Looks like it asks for the phone to be connected via usb as well.
Phoenix591 said:
Look at halium-install link
halium-install is done on a linux pc/livecd/virtual machine that has the following installed
qemu-user-static
qemu-system-arm
e2fsprogs
simg2img
sudo
binfmt-support
Looks like it asks for the phone to be connected via usb as well.
Click to expand...
Click to collapse
i noob in linux
can you make step for install this .... please
iam very interest in ubuntu touch
raf21 said:
To input halium-install, use terminal in twrp ? Or use terminal in pc.
Sorry for my english
Click to expand...
Click to collapse
1- reboot to recovery
2- connect your phone to pc (system ubuntu must be)
3- copy halium-boot.img to interal storage of phone
4- run halium install script
Code:
ex : ./halium-install -p ut ubuntu-touch-hybris-xenial-edge-armhf-rootfs.tar.gz system.img
5-install halium-boot.img with twrp
walidham said:
1- reboot to recovery
2- connect your phone to pc (system ubuntu must be)
3- copy halium-boot.img to interal storage of phone
4- run halium install script
Code:
ex : ./halium-install -p ut ubuntu-touch-hybris-xenial-edge-armhf-rootfs.tar.gz system.img
5-install halium-boot.img with twrp
Click to expand...
Click to collapse
how to run script
every i take halium script in terminal ubuntu always
/home/alienware/Desktop/ubuntu touch/halium-install-master/halium-install.sh' -p
Unsupported post install release! Exiting now
maybe i will try again if anybody can tell to me complete step by step to install ubuntu touch
thank for porting to ubuntu touch to h918
raf21 said:
how to run script
every i take halium script in terminal ubuntu always
/home/alienware/Desktop/ubuntu touch/halium-install-master/halium-install.sh' -p
Unsupported post install release! Exiting now
maybe i will try again if anybody can tell to me complete step by step to install ubuntu touch
thank for porting to ubuntu touch to h918
Click to expand...
Click to collapse
make dot and slash before commande like this ./halium-install.sh
youtub : https://youtu.be/E2FtIR7SUYU
Any chance that this would come to the other LG V20's such as the L997 (sprint)?
Americancosworth said:
Any chance that this would come to the other LG V20's such as the L997 (sprint)?
Click to expand...
Click to collapse
I have just h918, but i can build UT for others variant and i need tester for it.
walidham said:
I have just h918, but i can build UT for others variant and i need tester for it.
Click to expand...
Click to collapse
Can you help me to build Ubuntu touch for us998 lg v30 sir
raf21 said:
Can you help me to build Ubuntu touch for us998 lg v30 sir
Click to expand...
Click to collapse
for help you can join us at telegram
https://t.me/ubports_porting
unofficial installation with TWRP
1- Download zip file UT TWRP
2- push it in internal storage or sdcard
3- backup up your current boot partition (to restor it later if you want return to android rom)
4- install zip file, make sure your data partition is ext4 (option if you want fresh install you can wipe data partition)
5- rebbot
Related
Hi...
I am using a Milestone XT720 now, and had rooted my handheld.
Would appreciate to have any tutorial how to have the Apps2SD work on my XT720, please.
Thank you.
Rgds,
Andika
i have been trying different apps which work on nexus one. it doesn't seem to work on the xt720.
I successfully did it on Motoroi Xt720. i just use the rom manager to partition my sd card
But the rom have to be prepared to app2sd, isnt true?
Sent from my Milestone XT720
I just copied this to other forum i forgot cause i've saved this as txt file. credits to this are for the owner.
1. App2SD Version 2 (Download the attachment)
This revised version of App2SD is more refine. It moves cache as well as apps to MicroSD.
Steps to prepare for installation:
1. Unzip the downloaded file and you should see a folder "APP2SD Package".
2. Rename "APP2SD Package" folder to "app2sd" and move this folder to MicroSD. (place it in the root: MicroSD card/)
Next, simply connect the Milestone to your computer.
Ensure it is "Charge Only" for USB connection and USB Debugging mode for USB is turned on under Settings > Applications > Development.
Once you have the above checked, go ahead to launch a command prompt and perform the following:
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
I did this on my Motoroi XT720 I dont know in the other model, but i think it will work.
not successful.
first of all, you need to create ext2 partition on your SD card.
but even i got ext2 partition,
i got this error "mount: block device required"
I suggest you use the rom manager's "partition sdcard"
Sent from my XT720 using Tapatalk
jakelights said:
I suggest you use the rom manager's "partition sdcard"
Sent from my XT720 using Tapatalk
Click to expand...
Click to collapse
You mentioned that you are using rom manager to partition the sd card. have you tried installing the clockworks recovery mod thru it? the drop down menu in the app shows motorola milestone but not sure if it will work for XT720.
bu2askoor said:
You mentioned that you are using rom manager to partition the sd card. have you tried installing the clockworks recovery mod thru it? the drop down menu in the app shows motorola milestone but not sure if it will work for XT720.
Click to expand...
Click to collapse
same thing here ..............i cant find XT720 .....................
Got It To Work!!
I tried the Rom partition method but that didn't work for me so I got it to work using Hiren's Boot Cd (available for free to download) and used it to partition my mini-sd card. When using it to format please remember to create partitions in the following order:
1) Fat32 [I gave it around 6.4gb]
2) ext2 or ext3 (I used ext3) [I gave it around 1gb]
3) swap [gave it what was left around 140mb or so; give it atleast 128mb]
You can also use Gparted (again available for free to download) to create the partitions.
Don't forget to mark all your partition's active before you exit for it to work or else your milestone will mark it damaged and you will have to restart the entire process.
Once the formatting was done i followed the following steps to successfully install Apps2SD.
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
Couple of things:
1) I don't take credit for any of the mentioned steps, all goes to the original poster.
2) Please be aware that this is all at your own risk.
3) If you do need any help please feel free to ask.
Have fun ,
Yash
yadvani said:
I tried the Rom partition method but that didn't work for me so I got it to work using Hiren's Boot Cd (available for free to download) and used it to partition my mini-sd card. When using it to format please remember to create partitions in the following order:
1) Fat32 [I gave it around 6.4gb]
2) ext2 or ext3 (I used ext3) [I gave it around 1gb]
3) swap [gave it what was left around 140mb or so; give it atleast 128mb]
You can also use Gparted (again available for free to download) to create the partitions.
Don't forget to mark all your partition's active before you exit for it to work or else your milestone will mark it damaged and you will have to restart the entire process.
Once the formatting was done i followed the following steps to successfully install Apps2SD.
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
Couple of things:
1) I don't take credit for any of the mentioned steps, all goes to the original poster.
2) Please be aware that this is all at your own risk.
3) If you do need any help please feel free to ask.
Have fun ,
Yash
Click to expand...
Click to collapse
hi thanks for the steps, just to confirm a few things:
1) i think we don't need the swap partition right? swap partition is used for linux swap which only custom kernel can use right?
2) is there a way to reverse app2sd later? i am asking because i believe the froyo is near. will we have problem upgrading later with app2sd?
thanks all for al these wonderful guide
en0203 said:
hi thanks for the steps, just to confirm a few things:
1) i think we don't need the swap partition right? swap partition is used for linux swap which only custom kernel can use right?
2) is there a way to reverse app2sd later? i am asking because i believe the froyo is near. will we have problem upgrading later with app2sd?
thanks all for al these wonderful guide
Click to expand...
Click to collapse
1) Yes, but from all the tutorials i've read they all created a swap, so I just created it incase. Better be safe than sorry
2) I'm enjoying apps2sd way to much right now to even try uninstalling it and correct me if I'm wrong when froyo update is released our phone will be back to scratch one.. so format sd card and start all over again.
This is why i'm looking into nandroid backup/open recovery right now but can't seem to find it for xt720
Have a good one,
Yash
yadvani said:
I tried the Rom partition method but that didn't work for me so I got it to work using Hiren's Boot Cd (available for free to download) and used it to partition my mini-sd card. When using it to format please remember to create partitions in the following order:
1) Fat32 [I gave it around 6.4gb]
2) ext2 or ext3 (I used ext3) [I gave it around 1gb]
3) swap [gave it what was left around 140mb or so; give it atleast 128mb]
You can also use Gparted (again available for free to download) to create the partitions.
Don't forget to mark all your partition's active before you exit for it to work or else your milestone will mark it damaged and you will have to restart the entire process.
Once the formatting was done i followed the following steps to successfully install Apps2SD.
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
Couple of things:
1) I don't take credit for any of the mentioned steps, all goes to the original poster.
2) Please be aware that this is all at your own risk.
3) If you do need any help please feel free to ask.
Have fun ,
Yash
Click to expand...
Click to collapse
it goes endless loop. see the attachment.
can you give some details on how u use hiren boot cd to format card? (What program were you use? and how did you do?). Thanks a lot
yadvani said:
I tried the Rom partition method but that didn't work for me so I got it to work using Hiren's Boot Cd (available for free to download) and used it to partition my mini-sd card. When using it to format please remember to create partitions in the following order:
1) Fat32 [I gave it around 6.4gb]
2) ext2 or ext3 (I used ext3) [I gave it around 1gb]
3) swap [gave it what was left around 140mb or so; give it atleast 128mb]
You can also use Gparted (again available for free to download) to create the partitions.
Don't forget to mark all your partition's active before you exit for it to work or else your milestone will mark it damaged and you will have to restart the entire process.
Once the formatting was done i followed the following steps to successfully install Apps2SD.
Type: cd/ (to get to the root of your C: drive)
Type: cd /android/tools (to get to the folder of the Android SDK which i mentioned earlier)
Type: adb devices (you should see your Milestone serial number showing up. If you do not see serial number, it means there is no connection to your Milestone)
Type: adb shell
Type: su (make sure you do not see a prompt window on your Milestone. If you do, grant permission for it to access)
Type: cd /sdcard/apps2sd
Type: sh install_use_busybox.sh (trigger installation of App2SD)
Type: y (to confirm that you want to install)
wait for the prompt to show you that App2SD is complete and a reboot is needed for it to take effect.
Type: y (to confirm reboot. You might notice that Milestone do not reboot by self which is normal)
Type: reboot (if you find Milestone do not reboot after you enter y as above mentioned)
Enjoy after the reboot...
Couple of things:
1) I don't take credit for any of the mentioned steps, all goes to the original poster.
2) Please be aware that this is all at your own risk.
3) If you do need any help please feel free to ask.
Have fun ,
Yash
Click to expand...
Click to collapse
Hello i used linux gnome partition to partition my sd card (8GB) i made the 3 partition in the correct order as you instructed but when i get the sdcard in my xt720 it says blank card or unsuported filesystem and it promts me to format the card.
you said that i had to mark the partitions as active you meant to make them all primary right?
vaggoulas said:
Hello i used linux gnome partition to partition my sd card (8GB) i made the 3 partition in the correct order as you instructed but when i get the sdcard in my xt720 it says blank card or unsuported filesystem and it promts me to format the card.
you said that i had to mark the partitions as active you meant to make them all primary right?
Click to expand...
Click to collapse
Yes i forgot to mention you have to make them all primary and also mark them as active, these are two different things.
Give me sometime ill be uploading the instructions with screenshots.
spiderx_mm said:
it goes endless loop. see the attachment.
Click to expand...
Click to collapse
I didn't encounter any such problem, you may have better luck trying the Apps2sd forum. BTW stupid question but is your device rooted. Also what step did you encounter the problem, I may be able to repeat it and try and solve it.
Sorry not a dev just a user
Partition Tutorial with Screenshots
1) Download Hiren's Boot Cd (search torrent sites). The screenshots I am providing are using Hiren's Boot CD 10.6
2) Boot from the CD
3) Choose "Boot Mini Xp/Windows" (sorry no screenshots: boot menu)
4) Once minixp is loaded, connect your milestone with memory card access.
5) Heres where the screenshots start
6) Mount your milestone by double-clicking "Mount Removable" on the desktop
7) Check My Computer if your SD Card has been mounted. Mine as per the image is E: FAT32
8) Run "HBCD Menu" from the desktop and you should get the below image
9) Run Partition Wizard Home Edition
10) This is my setup below
11) Like I mentioned before create three primary partitions in the following order: FAT32; EXT2/3; SWAP as per your size preference. Don't forget ext2/3 partition is used for applications and fat32 for media
12) Here is how you mark them active and primary
13) Apply the changes by clicking the green arrow or apply button
14) Once the operation is done, exit the app and then safely remove your disk
15) Hopefully if everything went well, your milestone will now detect the sd card. If not try restarting
16) If all went well restart anyways and then follow the above steps to adb into your device and install apps2sd. Don't forget to enable USB debugging for it.
Long post I know... tried to be as descriptive as possible.
have a good one
spiderx_mm said:
it goes endless loop. see the attachment.
Click to expand...
Click to collapse
When doing this step Type: sh install_use_busybox.sh (trigger installation of App2SD)
try Type: sh install_use_busybox.sh -f
to force the installation ..
also try this thread other people have faced similar problem
sorry can't be of more help .. try re-doing the steps..
just wanna add that this works on the Milestone XT720.
but i might add that the script doesn't remove the backups made so you have to manually remove the backups created by the script. the backup folders are:
Code:
/data/app-private1
/data/app1
/data/dalvik-cache1
thanks
ok i did it!!! thx everybody!!!
Hello,
I have prepared a few update.zip's with kernels to boot linux:
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE.
1. Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==". http://ac100.gudinna.com/README/
2. Extract contents to a folder and follow instructions below.
copy the update.zip to a sdcard, and insert sdcard into folio.
Enter "Recovery menu" when folio is just turned on and press (POWER) once and (VOL up) next.
press (VOL up) Factory reset or system update.
press(VOL down) to continue to system update.
press (VOL up) to confirm system update.
during installation progress bar will show har far it is.
folio will reboot after installation.
insert the usb or flashdrive with the prepared filesystem into the folio and the tablet will boot automaticly from it
This sounds very interesting, might give it a try when im done playing with my new folio, ubuntu on it would be awesome
Does it boot to a full Ubuntu desktop or a bash prompt?
key combination to boot ubuntu
DerArtem said:
Hello,
I have prepared a few update.zip's with kernels to boot linux:
Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==".
Unzip the zip and then use the zip inside to update your kernel.
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Click to expand...
Click to collapse
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
zoken4 said:
Does it boot to a full Ubuntu desktop or a bash prompt?
Click to expand...
Click to collapse
It depends on what you have put on your sd / usb flash.
Ivalex said:
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
Click to expand...
Click to collapse
I have updated the 1st post.
DerArtem said:
It depends on what you have put on your sd / usb flash.
I have updated the 1st post.
Click to expand...
Click to collapse
gorgeous!
got it, the first step, is exactly the same as uploading a mod. then the SD modified as per gudinna instr. will bring you to linux.
thanks again.
how fast/responsive is this? Can you benchmark it against the AC100 netbook running the same image - that had a noticeable lag at least on SD card access.
How prepare the SD?
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Shark17 said:
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Click to expand...
Click to collapse
I have not tested it using a SD-Card. I will try it out when I have some time...
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
USB tried
I tried with the USB and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
Click to expand...
Click to collapse
I'm agree with your opinion.
I confirm that the method is not agressive for the tablet, restore android works for me.
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Hi,
eraph2 said:
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
Click to expand...
Click to collapse
I have used gentoo linux on a usb flash:
http://dev.gentoo.org/~armin76/arm/tegra2/install.xml
http://www.gentoo.org/doc/en/handbook/handbook-arm.xml
eraph2 said:
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Click to expand...
Click to collapse
Yes, this files exists in the gentoo in the .tgz ....
I think that ubuntu might require a initrd...
And ubuntu works?
Can you start ubuntu fixing this?
Console
Creating the console in the dev..., ¿are you started ubuntu?
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
eraph2 said:
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
Click to expand...
Click to collapse
Hi,
please search on the web how to rebuild the boot.img. This is not a problem. My zip also contains the config to rebuild the kernel. The sources of the kernel are also documented in the readme inside the zip. The initrd is just empty.
But running ubunu on the folio might be a bad idea. Ubuntu is compiled for NEON instruction set, but the Tegra 2 CPU does not support this, so a lot of applications can crash when they will try to execute more advanced code....
Debian (optimized for ARMv6 without NEON) or Gentoo are better for the Folio.
Then, if I want to install gentoo instead ubuntu, do I have to follow the same steps but changing the distro linux for the gentoo? Or is it necessary to do anything else?
Thanks
I tried to install gentoo in a USB, but it's a long process and it's not usual for me.
I'm very lost!
halu:
If you obtain a opetative distro image, can you upload in any place?
I'm thinking in write a howto with the results.
Bests
(Saludos desde Mallorca!! )
Hello guys.
I know there's no way to make CWM work with encrypted memory and SD and also there's no way to decrypt.
So, any other encryption solution that allows backups?
Using android's encryption feature, what to do in case of problems?
Any way to recover?
What happens if the system bricks and a recovery is needed?
What happens flashing a non disruptive update? Is a wipe needed?
Thank you so much!
Flashing to an encrypted ICS gs2/i9100
ultradj83 said:
Hello guys.
I know there's no way to make CWM work with encrypted memory and SD and also there's no way to decrypt.
So, any other encryption solution that allows backups?
Using android's encryption feature, what to do in case of problems?
Any way to recover?
What happens if the system bricks and a recovery is needed?
What happens flashing a non disruptive update? Is a wipe needed?
Thank you so much!
Click to expand...
Click to collapse
There are two options I've found that will work for flashing encrypted ICS, one is TWRP, which you would use instead of CWM, which would allow you to enter your password & flash what ever ROM you wanted like you were working with an unencrypted phone. But it's not (yet?) available for gs2/i9100.
The other option (original post here ) outlines how to do this from the command line of a computer with the Android SDK installed. I've spelled it out to include Android SDK installation since I didn't have that installed already when I had to do this.
Download, Install & configure Android SDK
Run SDK Manager
install "Android SDK Platform-tools"
Add <whatever>/android-sdk/platform-tools/ to path
in a command prompt / terminal window type "abd" to Check that your path includes the correct folders in the SDK (I had to do this manually on Win7)
On Phone
Reboot phone into Recovery mode
in CWM format cache partition
from your PC use adb to mount /sdcard as tmpfs:
Code:
adb shell mount -t tmpfs none /sdcard
put your ROM on the (fake) sdcard
Code:
adb push <your rom> /sdcard
Use the recovery to flesh the ROM as usual
Once you reboot the device will ask for you password as normal then finish the app installation/configuration after reboot. I was able to do this upgrading from CM9.0.0 RC1 to CM9.1. All data was preserved. Phone seems to be behaving itself but I only did this an hour ago so still too soon to tell.
Props to orcruin for sharing this. :highfive:
Ed
After breaking the screen on my phone I spent the following months reading about how to extract data. It all comes down to enabling ADB debugging and having your computer authorised. Usually this can be done from recovery and you're good to go. However, if you have a broken phone that is fully stock, with ADB disabled and with no custom recovery support then your data is as good as bricked. Such was the case with me when I broke my rare Samsung G360G. However, my phone was supported by CF-AutoRoot by Chainfire, and this gave just the opening I needed to go full wide.
Prerequisites:
Your phone needs to be supported by CF-AutoRoot. Check on there and the new site linked for support of your phone. If it's not there then you will need to download a stock ROM and use the CF-AutoRoot site tool to generate a root package for you. But that is outside the scope of this tutorial. This procedure has only been tested on Samsung. Your phone should have a minimal working charge.
https://autoroot.chainfire.eu/
This tutorial is also based on Linux. It should be translatable to Windows and Cygwin. But for simplicity I'll just use the method I used on Linux. However, if using Odin like I do, you'll need Windows to finish it off.
Aside from this it assumes files in are named in a particular format with a certain file format.
Tutorial:
1. First you need to download a CF-AutoRoot package for your phone. Won't get far without it.
2. Open up a terminal in Linux. We need to download some depends so enter this command:
Code:
sudo apt-get install android-tools-adb android-tools-fsutils
3. We need to extract the archive contents out. Create a suitable folder inside your home folder to build the patch in and cd to it. This uses an example file named CF-AutoRoot-example.tar.md5. Substitute with your actual archive name. Like so.
Code:
mkdir cfar-adb
cd cfar-adb
tar -xf CF-AutoRoot-example.tar.md5
4. There should be a recovery.img and a cache.img.ext4 extracted out. We just need to modify the cache.img.ext4. But first we need to convert it to a workable format. From a sparse to a raw image.
Code:
simg2img cache.img.ext4 cache.raw.ext4
5. We need to mount the cache image
Code:
mkdir cache
sudo mount -t ext4 -o loop cache.raw.ext4 cache
6. The big one. Doing the mod. So now we need to modify the cfar cleanup script. We need to insert commands on the end to enable ADB and add the key to authorise the computer. The following will do just that in this fashion.
a)
You will need to load in the cfar-cleanup.sh file inside the cfroot folder from the cache point mounted. Locate the end and paste the following lines before the reboot and exit commands on the end. Don't save yet.
Code:
echo -n 'mtp,adb' > /data/property/persist.sys.usb.config
mount -o remount,rw /system
echo '' >> /system/build.prop
echo 'persist.service.adb.enable=1' >> /system/build.prop
echo 'persist.service.debuggable=1' >> /system/build.prop
echo 'persist.sys.usb.config=mtp,adb' >> /system/build.prop
chmod 644 /system/build.prop
mount -o remount,ro /system
mkdir -p /data/misc/adb/
echo '' >/data/misc/adb/adb_keys
chmod 640 /data/misc/adb/adb_keys
b)
Load up the ~/.android/adbkey.pub file in a text editor and copy the entire contents in the clipboard. Now back at the script locate that last echo command you pasted into it and set the cursor just after the first single quotation mark. Now paste the clipboard in! This will add your key in. Make sure it's only between the single quotes with no extra characters or line feeds. The lines will naturally split if they don't fit on screen. Otherwise it should be good to go.
c)
Okay now save the file. The above will enable ADB and authorise your computer on the main Android system after the rooting script has done it's work. Before it reboots normally.
7. We need to unmount the cache so it's ready for use.
Code:
sudo umount cache
8. We need to convert the raw image back into a sparse image.
Code:
img2simg cache.raw.ext4 cache.img.ext4
9. Okay were almost done. Now we repack the files into a new Odin archive. Choose a suitable new filename. Like I have done here with my example file.
Code:
tar -H ustar -c recovery.img cache.img.ext4 > cfar-adb.tar
md5sum -t cfar-adb.tar >> cfar-adb.tar
mv cfar-adb.tar cfar-adb.tar.md5
10. The final step! So now the new package is ready for use. We just to use Odin and flash it to the phone. Save the package to a USB stick if needed.
a)
Reboot into Windows. Or you can run it virtualised from Linux. But I prefer to use the real things when dealing with things of a delicate manner and working blindly. Unplug your phone from the computer if connected. Now load up Odin in admin mode.
b)
Just to make sure pull the battery from your phone. Give it a few seconds then put the battery back in and click the back cover on. Now hold down volume down, then home key, and finally hold down power. Wait for the vibration. Then release power after a few moments. Finally release the other keys. At this point press volume up briefly. You should have just put your phone blindly into download mode. I've done this numerous times.
c)
Plug your phone into your computer. After a moment you should see Odin respond with a device added. Usually the phone can vibrate also when it connects giving more positive signs. If nothing happens disconnect the phone from the computer and retry the last step again to put it into download mode. Took me a few tries before I could do it blindly. It helps if you have a working Samsung to test it out on so you can see what happens before you can only feel it.
d)
Now in Odin press the PDA (or AP) button. Select the cfar-adb.tar.md5 package you made up. If the package is fine it will pass the md5 test. Now press the Start button and watch it go! If all goes well it will upload recovery, cache, give you a pass and then the phone will reset. At this point it will be in the process of being rooted, enable ADB, then reboot. If something goes wrong then you may need to go back and check all the patched files. Then rebuild the package again. But be careful, if the ADB has been enabled in the build.prop file one time, you don't want to add it in again and create duplicates, no matter how keen. Once I had it added the only other major problem I encountered was using the correct adb key.
e)
Hopefully now your phone is rooted, has ADB enabled and is booting up normally. Give it a few minutes. You can even see signs of life in Odin with adds and removes on USB activity. Your phone should also vibrate at times. And making noises is also a good sign.
1.1. So I just cranked it up to eleven. Open a Linux terminal again and give it a test. With your phone plugged in.
Code:
adb devices
If all goes well then adb will find your phone as well as list your device as authorised. You can now open shell to the inside. USB debugging is now enabled.
Conclusion:
Well I hope this helps those who have their app data stuck under a broken screen. As long as it was to type in this tutorial It still took me less time to write this tutorial than to learn all that was needed and apply it to my phone. This ends here but for you it may be only the beginning. A next step would be a screen mirroring app which I think is a must have for visual feedback. And USB debugging opens up these possibilities. One thing to be careful of, in a related issue, is that just because you can use adb and the phone is also rooted doesn't mean it will all work at once. If you are tempted to "su" it in an adb shell and get right in there then SuperSU will ask for permission on a blank screen. As will also happen if you try to do an adb backup, it will ask for confirmation on screen. So just expect to work with USB debugging blindly unless you already have a screen mirroring app installed. If you don't have one installed that is your next step.
And on that note. Good luck!
Hi there,
Your tutorial on how to achieve this on Linux looks real neat and complete. Unfortunately, i'm on Windows and i would like to know if you would be able to rewrite this totorial for a Windows user?
I've been reading online for about a week and i've never saw such a complete guide to help newbies to ADB to be able to retrieve data on their locked broken devices.
Cheers!
Hi RaiM1986 and thanks for your kind words. Yes I wrote it so it would be useful to newbies and seasoned hackers alike. Plus I needed to write down some instructions in case I need to do it all again.
Looking at the tutorial it is a bit Linux-centric. I don't know how well it would translate to Windows. Though there would be Windows version of the tools used the main problem would be mounting the filesystem image and making modifications without corrupting it. Because of things like Linux file modes.
However the following tools may be of assistance.
ADB tools:
https://wiki.lineageos.org/adb_fastboot_guide.html
Cygwin provides Linux tools if needed:
http://www.cygwin.com
simg2img:
https://github.com/KinglyWayne/simg2img_win
For mounting the ext4 image:
https://www.osforensics.com/tools/mount-disk-images.html
img2simg and other tools:
https://forum.xda-developers.com/showpost.php?p=49235638&postcount=5
For the ADB key it should be in %USERPOFILE%\.android and other spots I've read of are C:\Windows\System32\config\systemprofile\.android
In case any of the above fails, since I haven't tested them, the easiest alternative might be to just download a Linux live CD, boot it and do the steps inside. Of course any work is lost when you shut it down. You could also boot it in VM program running on Windows.
Amazing guide, Hypexed! The amount of work you put in to figure this out is incredible.
However, I'm stuck on step 6c, where I'm supposed to save the cfar-cleanup.sh file. It's not letting me save it at all, either within the mount point or to another location, it says that I don't have permissions to save the file. I tried the 'sudo chown' to change ownership to try to edit the permissions, but that didn't work either with it still saying I can't have access to the file. Any ideas? There is probably a simple solution, but this is my first time really using Linux so I'm a noob. I'm using Ubuntu 18.04.1LTS installed, not live, dual-booted with Windows, if that's important to know
SpinningQyarks said:
Amazing guide, Hypexed! The amount of work you put in to figure this out is incredible.
Click to expand...
Click to collapse
Thank you for noticing. It really was the culmination of months of hacking and cracking. Not to mention research. I decided I had to write a guide so I could document what I did in case I needed to do it again. And of course if it helped anyone else.
However, I'm stuck on step 6c, where I'm supposed to save the cfar-cleanup.sh file. It's not letting me save it at all, either within the mount point or to another location, it says that I don't have permissions to save the file. I tried the 'sudo chown' to change ownership to try to edit the permissions, but that didn't work either with it still saying I can't have access to the file. Any ideas? There is probably a simple solution, but this is my first time really using Linux so I'm a noob. I'm using Ubuntu 18.04.1LTS installed, not live, dual-booted with Windows, if that's important to know
Click to expand...
Click to collapse
Sorry you got stuck. I can see some issues in my guide. Especially after trying to do 6c again. First I notice I didn't specify where to store all the folders. Somewhere in the home folder obviously but it looks like you sorted that out fine.
I have tested a working solution to the permissions problem. In fact two:
1. Locate cf folder in the cache mount point on the desktop and go into it. Now right click in the window to bring up the context menu and select "Open as Root". Open up the editor as before.
2.. In the terminal run the editor as root. For example:
sudo gedit cfar-cleanup.sh
I've tested this on Mint which is a "relation" of Ubuntu so should work the same.
Now the original permissions should be left intact. I checked and they didn't have the execute bit set which is unusual. It may help here to save your work on the file to a place you can save to in the meantime. So you don't get stuck again. And then unmount your cache mount point, extract the raw image again as per step 4 and remount as per step 5, if the permissions need restoring. They really should be as they are originally set in the image.
Then continue through to step 6 and beyond as you were.
Good luck!
None of this is my work and all recognition goes to the awesome developers that made this possible, I will link their guides in here with some minor notes for newbies like me that may had some issues trying to unlock and root the Fire Stick (FS) 4K
DISCLAIMER: BE WARNED THAT YOU HAVE TO OPEN YOUR FIRE STICK AND IT WILL VOID YOUR WARRANTY, THIS IS NOT FOR THE FAINT OF HEART AND NEITHER THE DEVELOPERS OR MYSELF ARE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR VOID YOUR WARRANTY
Ok, now let's begin:
UPDATE: Per Sus_i, this makes perfect sense:
"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."
First very important, I wish I would have known this before but make sure you have a Laptop and a Monitor to Connect the FS to, so basically the USB Power cable from the FS connect it to your laptop and connect the HDMI portion to a monitor or TV
I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting
In order to unlock the bootloader follow "THIS GUIDE"
I made a quick video on how to open your device and how to Short it using Aluminum Foil:
https://www.youtube.com/watch?v=h4I6ifBLWJ4
Process is pretty self explanitory, make a USB ISO from the image provided on that thread, boot into it and open terminal, make sure you put the file he provides on a RW location, my mistake was that I put it inside a RO folder and it would not load the script, so I mounted the kamakiri-mantis-v1.2.zip unto the /mnt directory of the usb and I was able to run the script successfully, make sure to run the commands quickly as the first time that I it finished the ./bootrom-step.sh script and I left it sitting for 10 minutes to grab a bite, I couldn't run the second script and had to start all over. After the second ./fastboot-step.sh script, your device will be on the TWRP recovery, now on the same terminal page or a new one enter these commands:
Code:
adb devices
adb shell
exit
You should see your device's serial number from the first command with "device" to the right of it and the second command will basically put you inside the device's directory assuming you have established a successful connection. The last command just put you back to your starting point, now open the firefox browser on the FireOS USB and navigate to the URL below
Download the Pre-Rooted Image from "HERE" This image contains Magisk already so you don't have to worry about installing it separately, the image is larger than the available partition on this USB so this is a good time to either get a second USB or if you want to download the file to your local hdd and pull them from there its up to you, then run these commands:
Code:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
This basically installs the pre-rooted image to your device, after the last command, you should see on your monitor the Fire Stick Reboot and boot to the Amazon GUI Splash Screen, now very important if you followed my previous instructions of deregistering your device before performing all these steps, it should bring you up to the Amazon Initial Setup Screen, now what you want to do is do the following commands before continuing on terminal:
Code:
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
Now it should show you in terminal your serial number and "device" next to it, meaning you can run adb commands in which you will run the following to disable OTA updates:
Code:
adb shell
su *after this command you should see something again on your screen, click the check the box "Always Remember" and click ok" *
if "su" was successful, you should see something like this:
mantis:/ $ su
mantis:/ # *the hash means you're running as root, if you don't have a "#" you are not running as root"
Than continue with these commands and should get the following results:
pm disable com.amazon.tv.forcedotaupdater.v2
***Package com.amazon.tv.forcedotaupdater.v2 new state: disabled***
pm disable com.amazon.device.software.ota
***Package om.amazon.device.software.ota new state: disabled***
pm disable com.amazon.device.software.ota.override
***Package com.amazon.device.software.ota.override new state: disabled***
After running all these commands exit adb and continue with the normal Amazon Setup including adding your amazon account. After you get to the screen where you can see all the apps, open a new web page browser in firefox and download "This Add-On" , this one is less than 200MB so it should fit on the Fire OS USB, so I would download it and copy it to /mnt for ease of access, go back to terminal and type this:
Code:
adb devices
adb push <your download location you decided earlier here>/AFTV-MM-1.7-6.2.6.8.zip/ sdcard/
adb reboot recovery *it will boot into TWRP*
adb shell
twrp install /sdcard/AFTV-MM-1.7-6.2.6.8.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Your device will reboot and if everything went smoothly, you should have a rooted amazon fire stick 4k, Congrats :good:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Edit: S̵i̵n̵c̵e̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵ ̵c̵a̵n̵'̵t̵ ̵b̵e̵ ̵p̵a̵t̵c̵h̵e̵d̵,̵ ̵i̵t̵'̵s̵ ̵i̵n̵ ̵m̵y̵ ̵o̵p̵i̵n̵i̵o̵n̵ ̵t̵h̵e̵ ̵b̵e̵s̵t̵ ̵t̵o̵ ̵d̵o̵ ̵t̵h̵e̵ ̵s̵e̵t̵u̵p̵ ̵a̵t̵ ̵t̵h̵e̵ ̵b̵e̵g̵i̵n̵n̵i̵n̵g̵,̵ ̵p̵a̵i̵r̵ ̵t̵h̵e̵ ̵r̵e̵m̵o̵t̵e̵,̵ ̵t̵h̵e̵n̵ ̵u̵p̵d̵a̵t̵e̵ ̵t̵o̵ ̵t̵h̵e̵ ̵l̵a̵t̵e̵s̵t̵ ̵o̵v̵e̵r̵ ̵f̵i̵r̵e̵O̵S̵.̵ ̵T̵h̵a̵t̵ ̵w̵a̵y̵ ̵y̵o̵u̵ ̵a̵v̵o̵i̵d̵ ̵a̵ ̵p̵e̵n̵d̵i̵n̵g̵ ̵u̵p̵d̵a̵t̵e̵ ̵n̵a̵g̵ ̵s̵e̵t̵u̵p̵ ̵s̵c̵r̵e̵e̵n̵ ̵a̵f̵t̵e̵r̵ ̵d̵o̵i̵n̵g̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵.̵ ̵T̵h̵e̵n̵ ̵e̵n̵a̵b̵l̵e̵ ̵A̵D̵B̵ ̵a̵n̵d̵ ̵u̵n̵k̵n̵o̵w̵n̵ ̵s̵o̵u̵r̵c̵e̵s̵.̵ ̵ After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Edit: Update: meanwhile, the fix for the mentioned 'contact manufacturer' error is known...
Take a look here and here.
Edit/Update: Due to efuses (blocking the bootrom access), it isn't recommended to do any update infront of the unlock...
Sus_i said:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Click to expand...
Click to collapse
Ops Typo let me edit it, I meant to put 6.2.6.8 on the command lol, and aaaa I see I didn't know the exploit couldn't be patched great info, so than yes I will revise my instructions thank so much
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
nandroidint said:
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
Click to expand...
Click to collapse
No. If I remember correct, it has something to do with flashing, i.e. the vendor partition wasn't flashed propperly.
Maybe you flashed not the prerooted!? With the Kamakiri TWRP version is flashing full ota update packages (renamed to zip) also possible... and in the prerooted thread is such a full 6.2.6.8 ota linked.
Edit: Could be that this error is prime video related, idk. rbox said he looks into it soon...
Just for clarification: The prerooted rom is a perfect thing since years.
My suggestion 'avoid any rom flashing' from my last post is just an attempt to keep it simple for beginners.
By the way, if the stick gets all updates in front of the unlock, it makes no sense to update it after the unlock again (unless addon.d support is needed).
I hope that has become clear I very much appreciate all the prerooted stuff
thanx for the tut nandroidint this is exactly what I needed, I wasn't sure how to do the shorting so the video helped out a lot now I'm ready to do this. But I'm sorta a noob when it comes to android so I got few questions tho, 1) what are the main benefits in rooting the fIrestick 4K 2) are there different roms to install? 3) are there root only .apks? 4)also one main thing I would like to be able to do is spoofing the Mac address any idea if that's possible?
5)Oh and lastly what OTB cable do you recommend? sorry for all the questions ?
'std::bad_alloc'
After running the adb push of the manthis.zip Im getting terminate called after throwing an instance of 'std::bad_alloc'.... What Im I doing wrong?
i gave root can i remove amazon services
i dont want google launcher jsut remove services
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable ?
Can I please get some support guys ? previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
davinci2798 said:
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
Click to expand...
Click to collapse
Did you deregister before rooting like the tut says? This is why I’ve been hesitant on rooting because of the lack of support on this forum
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
tsynik said:
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
Click to expand...
Click to collapse
Nice! That’s awesome thanx for the info and reply.
davinci2798 said:
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
Click to expand...
Click to collapse
Hey so have you figured out what was the problem yet? If so could u explain how you managed to fix it? I’m going to root sometime this week and would hate to run into this issue.
USB drive for storage
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
Yes, You can use a USB drive for App loading and Movie storage.
See Troypoint.com for good video.
I suggest a single USB OTG Cable and a USB HUB for your drive.
Then you can add a Keyboard and Mouse which make it MUCH easier to type commands.
Good Luck
How might one do this on a Mac?
Thanks
gogorman said:
How might one do this on a Mac?
Thanks
Click to expand...
Click to collapse
Do what? The only thing u can do on the MacOS is to create the bootable iso usb, you can follow these steps to do so https://www.google.com/amp/s/www.le...-on-an-apple-mac-os-x-from-an-iso?hs_amp=true
After your create the bootable usb just reboot and hold down option and select the bootable usb, once in open up Firefox and download the kamakiri-mantis-v1 and open a terminal window and change the directory to where u have the kamakiri folder, in terminal type cd then just drop in the kamakiri and hit enter. From there u can just follow the tut, FYI the bootable usb you create is a Linux OS so that’s how you can do it on a Mac, you just can’t do the rooting on MacOS, just clarifying Incase that was your question.
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Step by step instructions would be great?
chinkster said:
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
RPM99 said:
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
Click to expand...
Click to collapse
The link he provided explains all that https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459 all except for when to connect to the tv, but I assume it’s after running the kamakiri script, btw it’s not software, you just download the kamakiri mantis while in the Linux usb os, open a terminal and change the directory of the terminal to the kamakiri folder in order to run the ./bootrom-step.sh and ./fastboot-step.sh commands
Edit: just follow the main guide from the link above then read this guide after, that’s the best way to understand it.