I DIDN'T DO THIS
Thanks to @TheDevFreak for the download link
I put it here so we can find it faster.
Here's the TWRP 3.0 version that supports SquashFS filesystem to avoid the error
Code:
NO OS INSTALLED
bootlooping when flashing Wear 2.0 ROM
Download:
-attached to this post-
http://www.mediafire.com/file/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
https://mega.nz/#!AB9BnBjC!GRVW_eLtPRezC_Jxvw9-FBn80meeZkXRemdUfukZmpE
flash it on fastboot
Code:
Fastboot flash recovery twrp-3.0.0-0-dory+squashfs.img
I dont get do you mean that it will work with AW 2.0 or is it a bug ?
I have permanent bootloop. I've already flashed my LG G Watch few times and still no luck. Do you have any advice how to boot?
[edit]
If you have permanent bootloop after factory reset of AW2, you have to reflash your watch with Mysterious Magic than update to 6.0.1 with OTA and then reflash to AW2.
I'm confused, TWRP is still reporting that there is no OS with my watch flashed to AW 2.0
ShapeShifter499 said:
I'm confused, TWRP is still reporting that there is no OS with my watch flashed to AW 2.0
Click to expand...
Click to collapse
Ignore this, that's a known bug...
It will work nonetheless
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Ignore this, that's a known bug...
It will work nonetheless
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Is it safe to try to root AW 2.0 with this version of TWRP? I only want to root in order to increase the vibration time for notifications.
ShapeShifter499 said:
Is it safe to try to root AW 2.0 with this version of TWRP? I only want to root in order to increase the vibration time for notifications.
Click to expand...
Click to collapse
Yeah, it flashes latest magisk (even beta) just fine...
You can adb install kernel adiutor to regulate vibration
You theoretically could also use SuperSU in systemless mode, imported is that changes to system won't work as the system file system (squashfs) is read only, it cannot be modified but this does not matter with systemless solutions like magisk as it only patches the kernel (hence systemless)
Sent from my OnePlus 3T using XDA Labs
Sam Nakamura said:
Yeah, it flashes latest magisk (even beta) just fine...
You can adb install kernel adiutor to regulate vibration
You theoretically could also use SuperSU in systemless mode, imported is that changes to system won't work as the system file system (squashfs) is read only, it cannot be modified but this does not matter with systemless solutions like magisk as it only patches the kernel (hence systemless)
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I'll try running magisk. I didn't even think magisk would work on AW. Also thanks for pointing out kernel adiutor.
Sam Nakamura said:
Yeah, it flashes latest magisk (even beta) just fine...
You can adb install kernel adiutor to regulate vibration
You theoretically could also use SuperSU in systemless mode, imported is that changes to system won't work as the system file system (squashfs) is read only, it cannot be modified but this does not matter with systemless solutions like magisk as it only patches the kernel (hence systemless)
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
which version of adiutor are you using, it displays much to big to navigate anything
ShapeShifter499 said:
which version of adiutor are you using, it displays much to big to navigate anything
Click to expand...
Click to collapse
You'll need to set a custom screen density
Code:
adb shell vm density 180
Default density is 240p, you can play a little what suits you best but I'm comfortable with 180 and all apps so far ran flawlessly, this command will keep the custom screen resolution across reboots, keep this in mind but as long as you can boot to bootloader you can change this to default or your liking, of course you'll need to reboot to take effect (in case you just use adb while watch is booted)
Sent from my OnePlus 3T using XDA Labs
Deleted
after selecting system reset to pair with another phone i'm stuck in a boot loop, where i get to twrp recovery no matter what i do. any idea what to do? thanks.
Jaocagomez said:
I DIDN'T DO THIS
Thanks to @TheDevFreak for the download link
I put it here so we can find it faster.
Here's the TWRP 3.0 version that supports SquashFS filesystem to avoid the error
Code:
NO OS INSTALLED
bootlooping when flashing Wear 2.0 ROM
Download:
-attached to this post-
http://www.mediafire.com/file/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
https://mega.nz/#!AB9BnBjC!GRVW_eLtPRezC_Jxvw9-FBn80meeZkXRemdUfukZmpE
flash it on fastboot
Code:
Fastboot flash recovery twrp-3.0.0-0-dory+squashfs.img
Click to expand...
Click to collapse
Hi, i have created a twrp for a pioneer tablet, but it has squashfs like your watch, do you know where can I contact to help me fix this like your twrp?
This recovery does not work anymore with the latest ota from 2017 on my lg g watch r:
NWS2.170620.003
I used the latest official image and following commands to backup my factory image:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
exit
adb pull /sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
also the image should be available here: https://forum.xda-developers.com/t/...003-fastboot-twrp-zip-factory-images.3405311/
madejackson said:
This recovery does not work anymore with the latest ota from 2017 on my lg g watch r:
NWS2.170620.003
I used the latest official image and following commands to backup my factory image:
adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
exit
adb pull /sdcard/boot.img
adb pull /sdcard/system.img
adb pull /sdcard/recovery.img
also the image should be available here: https://forum.xda-developers.com/t/...003-fastboot-twrp-zip-factory-images.3405311/
Click to expand...
Click to collapse
You are looking in the wrong place for the TWRP recovery, this is for the LG G watch w100.
I believe you were instead looking for this: https://forum.xda-developers.com/t/recovery-lenok-twrp-3-1-1-0-touch-recovery-2017-05-19.3001890/
Have a good one!
Related
http://forum.xda-developers.com/xpe.../recovery-twrp-3-0-0-touch-recovery-t3309938/
This is deprecated.
In this thread I'll share the .img files of the latest TWRP available for our device, so you can flash them with Rashr/PhilZ/Cyanogen recovery.
Disclaimer:
you are responsible for what you do. If your device stops working after you follow this guide, it's not my fault. However, as usual, if you do things in a correct way, you won't face any problems.
Requirements:
any ROM with any kernel
unlocked bootloader
Don't flash it if you have got a locked bootloader!
Features:
up-to-date source
flashable signed zip
f2fs support
Changelog:
TWRP 2.8.7.0_8
- other cleanups
- startup now is not slow! It just takes 3 - 4 seconds!
- Reboot bug is fixed - maybe
TWRP 2.8.7.0_7
- optimizations and cleanups
TWRP 2.8.7.0_6
- f2fs for /system is supported (this is for Temasek users)
TWRP 2.8.7.0_5
- f2fs support improved
- minor optimizations
- less overheating
TWRP 2.8.7.0_4
- attempt to fix issues with reboot option
TWRP 2.8.7.0_3
- signed flashable zip added
TWRP 2.8.7.0_2
- f2fs bugs fixed
- fixed overheating
How to install:
flash the zip through any recovery (even Cyanogen recovery!)
Download from Android File Host:
[url]https://www.androidfilehost.com/?fid=24052804347826443[/URL]
Stock FOTAKernel to remove any recovery (included this one): [url]http://forum.xda-developers.com/xperia-sp/general/stock-components-flashable-zips-t3184111[/URL]
Be sure to select the right variant of your device!
Thanks to:
@[NUT]
@antr34
@TechnoSparks
This work in miui v6
Thanks a lot for this quick update :thumbup:
Working fine on AICP's official nightlies with stock kernel.
The TITAN has landed. Hide your works from this critic! The official maintainer of the XSP Lollipop and M Hub.
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
pilger said:
Rashr was not working for me. I got it to work with this command on the terminal (with root):
Code:
su
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Notice that you'd have to save the .img file on the proper directory prior to using the command.
You can find more details of my struggle here: http://forum.xda-developers.com/xpe...rnel-tangerine-kernel-v1-t3073297/page28#1379
Hope this helps someone with the same issue.
Click to expand...
Click to collapse
I use it and i cant flash nothing
Guizão BR said:
I use it and i cant flash nothing
Click to expand...
Click to collapse
What is the output of the command? Does it throw you an error or anything?
@pilger i'm here, what to do next?
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
pilger said:
Here's a more detailed description of what I did in order for this to be flashed on my FOTAKernel:
Booted into default Cyanogen Recovery;
Wiped Dalvik and everything else I could in order to flash a new ROM;
Flashed the UNOFFICIAL CM from July 26th;
Flashed Pico Gapps (I guess it doesn't matter which Gapps you install, though);
Booted into system and set up everything (accounts, wi-fi, etc.);
DID NOT install Rashr;
Plugged my device to PC using USB;
Transfered the twrp-2.8.7.0_huashan.img to the root of the internal storage;
Unplugged the device from the computer;
Enabled Developer options on Settings (by tapping like crazy on the build number);
On the Developer options, I turned on Terminal Command, and root access to both ADB and apps;
Opened the terminal and entered "su" command to get root;
Allowed root and set it to remember its choice;
Entered up the command:
Code:
dd if=/ext_card/twrp-2.8.7.0_huashan.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Rebooted on recovery mode;
TWRP 2.8.7.0 was functioning as expected.
Click to expand...
Click to collapse
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
J73 said:
I've got TWRP now, one question though, if I flash the next CM nightly, it wouldn't be overwrote by the cyanogen recovery?
Click to expand...
Click to collapse
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
pilger said:
Glad you got it to work, mate! Flashing CM shouldn't overwrite the recovery. I guess that's the purpose of having the recovery on FOTA.
I'm not an expert though. But I've tested a couple of times myself and TWRP is there after every flash.
Click to expand...
Click to collapse
Thanks to you! All's well now, I'm so glad to have TWRP again thank you!
pilger said:
What is the output of the command? Does it throw you an error or anything?
Click to expand...
Click to collapse
Sorry i Forgot to edit the play, this have more time to flash
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Tomoms said:
There's a bug with f2fs, it will be fixed tomorrow. Thanks to @Adrian DC for pointing this out.
Click to expand...
Click to collapse
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
kunal9007 said:
Can you tell me about that bug cause I'm using f2fs for cache,data and media that's formatted through your recovery
Sent from my Xperia SP using Tapatalk
Click to expand...
Click to collapse
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Tomoms said:
Are you using Tangerine? This bug is not present in Tangerine's TWRP.
Click to expand...
Click to collapse
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
kunal9007 said:
I'm using tangerine but I've flashed this TWRP first, and this recovery has fotakernel so i geuss it can't be overwritten
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Well, strange. f2fs volumes couldn't be mounted.
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Adrian DC said:
Tangerine probably fixed the issue, same as my CM-12.1 boot image fixed the TWRP image.
The goal of the fix is to have F2FS working without the boot image flashed over TWRP to make clean installs.
Click to expand...
Click to collapse
just realized that I didn't had tangerine installed i was on first build of official cm and then before flashing radium i formated to f2fs
Sent from my XT1033 using Tapatalk
---------- Post added at 09:00 PM ---------- Previous post was at 08:58 PM ----------
and i flashed tangerine after atleast 1 day use of stock kernel
Sent from my XT1033 using Tapatalk
It's finally here! TWRP recovery for the Fire TV 1. Most likely, I will not be updating this thread with new releases, as the prerooted ROMs will always contain the latest version. This thread is just here so people on Fire OS 3 can install TWRP and people on rooted but locked bootloader Fire TV 1's can get recovery initially installed.
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
Installing this requires root. If you are not rooted, figure that out first.
Installation for Unlocked Bootloader
Make sure you are on a FULLY unlocked bootloader. From within FireOS and after running su run this:
Code:
cat /proc/cmdline
And MAKE SURE unlocked_kernel=true is present! If it is not, you are NOT fully unlocked and you must Fully Unlock first!
Make sure you are on at least 51.1.4.0 ROM and the latest CWM installed.
Copy the bueller-twrp_3.0.0-6.img file to /sdcard
From within adb shell, use su to become root, and run this command (are you sure you did step 1?)
Code:
dd if=/data/media/0/bueller-twrp_3.0.0-6.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
From outside adb shell, reboot to recovery
Code:
adb reboot recovery
TWRP should load, you can install a FireOS5 prerooted ROM now.
Installation for Locked Bootloader
This requires that you are on at least version 5.0.5 and rooted.
Copy the bueller_recovery_vX.zip file to /sdcard
From within adb shell, use su to become root, and run this command (replace vX with the actual version you downloaded)
Code:
sh /data/media/0/bueller_recovery_vX.zip
Reboot
Notes
This includes bootmenu. For everyone that loved the old bootmenu with Comic Sans, I'm sorry to disappoint you, but the Comic Sans is gone. When the FireTV boots, it will present you with the bootmenu where you can leave it alone and it will boot normally or you can select recovery and it will boot in to recovery. You do need a USB keyboard to interact with the bootmenu. To force it to boot in to Recovery, you can create a file /cache/bootmenu_recovery.
DHCP for Ethernet is enabled, and if there is enough demand I may add in wifi at some point. The IP address should show up in the top left corner.
USB storage and USB keyboard/mice should all work. Hotplugging works, so you should be able to plug and unplug devices as needed.
You can use a USB keyboard, mouse, or the mouse emulator to interact with it. To use a keyboard, you can use the arrow keys to move the cursor and the enter key to select buttons. Sliders don't require sliding, so you can just hit enter/click on them. To use the mouse emulator, use adb shell and then run the program mouse and follow the instructions.
ROMs
Recovery must be included in all ROMs. If you want to develop a ROM, please contact me about including recovery in it.
Installing zips
You can push zips to /sdcard, put it on a USB storage, or use adb sideload. Do note you need adb version 1.0.32 to use adb sideload.
Stuck in a loop?
If you cannot boot normally and keep going back to the bootmenu, wipe Cache from Wipe -> Advanced Wipe.
Source Code
You can find the source code here:
https://github.com/androidrbox/firetv-2ndinit
https://github.com/androidrbox/android_bootable_recovery
WARNINGS
It is extremely important you never reboot after a failure. This will most likely lead to a brick. If recovery is hung, you can use adb shell to run
Code:
killall recovery
to restart it
It is also extremely important to never reboot after wiping /system.
Finally, thanks to everyone who has donated to me.
Changelog and Downloads:
July 7, 2016 - v2 (md5sum: 8f65187cb0cbc190a7d64f512ae3ede2)
This is the updated version with TWRP 3.0.0-7.
July 4, 2016 - TWRP Image 3.0.0-7 (md5sum: cda1a1c1cdd3e25a1caa86f5a5de1eee)
May 20, 2016 - v1 (md5sum: 9208d81fd07cff9952de5be33c62f730)
This is for use by people who have FireOS5 and are rooted.
This includes 2ndinit version a7a48c and TWRP version 3.0.0-6.
May 20, 2016 - TWRP Image (md5sum: 5dc83370046e5b50755ddb55fe8424ad)
This is for use by people who have FireOS3 and CWM and is TWRP version 3.0.0-6.
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
mrchrister said:
thanks so much rbox! just tested it and i can confirm that my firetv 1 with fireos3 and fully unlocked bootloader just installed twrp successfully - woot!
i still have the old boot menu though with comic sans..?
Click to expand...
Click to collapse
For unlocked bootloaders, this step JUST installs recovery. You need to install the prerooted rom to get the new bootmenu.
got you, downloading now
Sent from my iPhone using Tapatalk
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
If you unplug the power and replug it, it should boot normally, then you can see if the recovery log got saved, /cache/recovery/last_log and pastebin it.
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
ssgelm said:
The log at /cache/recovery/last_log is from CWM from the last time I flashed a new rom.
Click to expand...
Click to collapse
Can't really explain why it would be doing that. Can you connect via adb?
I am not on ethernet right now. When I get a chance I'll do that and see if I can connect. Thanks so much for your work on this!
ssgelm said:
I successfully dd'ed the recovery image onto my ftv with unlocked bootloader but attempting to boot it causes the TWRP logo to show for a few seconds, then the screen goes black and the cycle repeats. Any idea how to fix this?
Click to expand...
Click to collapse
I'm also getting this, what can I do?
here's last_log
gehx said:
I'm also getting this, what can I do?
Click to expand...
Click to collapse
Can you connect via adb?
rbox said:
Can you connect via adb?
Click to expand...
Click to collapse
yep, that's how I pulled last_log
gehx said:
yep, that's how I pulled last_log
Click to expand...
Click to collapse
I meant while recovery is running.
rbox said:
I meant while recovery is running.
Click to expand...
Click to collapse
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
gehx said:
recovery never fully loads, i just get the twrp splash screen over and over and over again...it's in a loop
Click to expand...
Click to collapse
Yes. But have you tried using adb...
rbox said:
Yes. But have you tried using adb...
Click to expand...
Click to collapse
I'm not sure what IP to use?
gehx said:
I'm not sure what IP to use?
Click to expand...
Click to collapse
The same one the firetv would be using when it's booted... via ethernet of course.
rbox said:
The same one the firetv would be using when it's booted... via ethernet of course.
Click to expand...
Click to collapse
the connection times out:
adb connect 192.168.1.6
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.6:5555: Operation timed out
Click to expand...
Click to collapse
gehx said:
the connection times out:
Click to expand...
Click to collapse
Can you pull the log again? It should say the ip in it actually.
rbox said:
Can you pull the log again? It should say the ip in it actually.
Click to expand...
Click to collapse
new last_log
it shows 192.168.1.8; I'm unable to adb connect to that IP too
Hello guys, I have few questions and hopefully someone can answer them.
I am trying to root my mate 10 pro with version:
BLA-L29 8.0.0.127(C432)
I want to root it with magisk and since twrp is not available yet,
is it possible to root by patching the boot image?
If it is possible, how do I extract the boot image without root?
This is what i found online.
Method 2: Patching Stock Boot Image
This method doesn’t require you to have TWRP in order to install Magisk 15.0 update.
1. Download the latest Magisk Manager APK: MagiskManager-v5.5.1.apk
2. Use a file manager to install the downloaded app on your device.
3. Grab the stock boot image (kernel) and it should be corresponding to the firmware installed on your device.
For Nexus and Pixel devices, you can extract it from the factory image. For other OEM devices, you might need to check it with your manufacturer’s support.
4. Copy the downloaded “boot.img” to the internal storage of your Android device.
5.Open the Magisk Manager app and tap on the ‘Install’ button.
6. Again, choose ‘Install’ and then ‘Patch Boot Image File’.
7. Navigate to the storage and select the ‘boot.img’ file you just transferred.
8. The Magisk Manager app will patch the stock boot image and place the resultant ‘patched_boot.img’ in the ‘MagiskManager’ folder.
9. Transfer the file from your phone to C:\adb folder on your PC.
10. Hold the SHIFT key on your PC and right-click on an empty space inside the folder. Then select ‘Open PowerShell window here’ from the menu.
11. Boot your Android into Fastboot mode and connect it to the PC.
Enter the following command to root your Android phone using Magisk 15.0 update:
fastboot flash boot patched_boot.img
Finally, reboot your device.
fastboot reboot
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Dagda-Esus said:
I have tried this method and got a boot loop... Don't try this if you don't know what you do
with some ressources in others threads you can download the firmware, unpack it and try to patch this with magisk. But if you don't know how to do that, you shouldn't do that
Read these scripts to learn how flash works with mate 10 => https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
Click to expand...
Click to collapse
Did you get the boot.img file ? or did you do it in another way ?
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
trackloading said:
I'm interested in this as well...
I have downloaded full OTAs, but there is no boot.img? I have tried the above method with the ramdisk.img since it's usually part of the boot.img, but I get bootloop.
Click to expand...
Click to collapse
ramdisk.img is correct. boot.img is ramdisk and kernel combined, but as of Oreo it's now ramdisk.img and kernel.img.
So patching ramdisk.img is the way to go?
yfaykya said:
So patching ramdisk.img is the way to go?
Click to expand...
Click to collapse
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
dawnc said:
My devices is Huawei Honor V10 with Emui 8.0 (OREO), I can't find the stock boot.img by extracting the official full OTA update.app.
I got the stock boot.img from a third party rom for V10 (Kangvip mod rom for v10 B122) , and patched it in Magisk manager.
I use ' fastboot flash ramdisk patched_boot.img ' to flash the pathed boot. And i got boot loop...
There's isn't a custom recovery for V10, so i can't flash supersu.
Anyone got a solution for this?
Click to expand...
Click to collapse
Do you know your model number?
Like
xxx-CxxxBxxx
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
Did you get magisk working ?
lisa99 said:
Did you get magisk working ?
Click to expand...
Click to collapse
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the "Your device is unlocked" screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
ante0 said:
Loop device support is not available yet, so Magisk can't be installed (System less only). The only option is Supersu.
Edit: Magisk can be installed, but it ends in a bootloop (Actually just a reboot before boot animation starts).
So it's not loop support that's wrong, because I've tested now and it does work.
Click to expand...
Click to collapse
ante0 said:
Nope. Magisk replaces original INIT in ramdisk, that makes it reboot after the Your devices is unlocked screen.
I'm trying some other things.
I read that newer devices might actually read initramfs from recovery rather than ramdisk (boot) so I'm trying that out now...
Click to expand...
Click to collapse
let me know if you figure something out.
ante0 said:
do you know your model number?
Like
xxx-cxxxbxxx
Click to expand...
Click to collapse
bkl-al20c00
dawnc said:
bkl-al20c00
Click to expand...
Click to collapse
You seem to have fixed it already?
ante0 said:
You seem to have fixed it already?
Click to expand...
Click to collapse
I've made a boot.img with supersu inside.
But can't fix magisk root
dawnc said:
I've made a boot.img with supersu inside.
But can't fix magisk root
Click to expand...
Click to collapse
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
ante0 said:
Nope. I've tested a lot.
First you need extract magisk zip then open common/util_functions.sh and edit
BOOTIMAGE=`find /dev/block -iname boot$SLOT | head -n 1` 2>/dev/null
to
BOOTIMAGE=`find /dev/block -iname ramdisk$SLOT | head -n 1` 2>/dev/null
save and repack.
But I'm pretty sure it's because of the INIT it places in RAMDISK...
You have to modify kernel too, because RAMDISK contains an empty kernel and it applies the hexpatch to RAMDISK instead of the real KERNEL.
But either way it ends in a boot loop. And before logcat can start so no logs either... :/
Click to expand...
Click to collapse
Have u found a way to make magisk work?
dawnc said:
Have u found a way to make magisk work?
Click to expand...
Click to collapse
It might be because loop is not fully working.
But no, haven't found any way.
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
dawnc said:
@ante0 Have you tested both flashing patched ramdisk.img and patched recovery_ramdisk.img ? Will this make magisk work?
Click to expand...
Click to collapse
Not both at once no.
How to use magisk to twrp from 2.3.5 gingerbread without a computer?
@Didgeridoohan
Do you think its possible to flash twrp from a terminal emulator? Or what are my options?
If you really can't get a hold of a computer you might be lucky with an app like Franco Kernel Manager, Flashify, etc. Problem is that most apps likely won't support or be compatible with that ancient version of Android or whatever root you currently have installed. And, you're also risking bricking your device if you don't have access to a computer...
I really think your best bet is to somehow get access to a computer. Friend/school/work/something...
If you can't install stuff on that borrowed computer you could create a bootable USB with a Linux distro and run everything from there. Linux Mint is quite user friendly, they've got good documentation on how to get things running with a Live Boot USB, and it's not too hard to get adb & fastboot up and running.
Ill try and get a hold of a computer because nothing seems to work on 2.3.5
@Didgeridoohan
I had rooted using framaroot but after a factory reset it wont install supersu or superuser to my app drawer, can you give me a suggestion? Btw im using my xbox one to type this.
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
jwoegerbauer said:
@chris1892006
don't waste your time with this: Magisk works only on Android 5.0 and above.
Click to expand...
Click to collapse
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
chris1892006 said:
thanks so do u know if its possiblle to flash a twrp.zip using terminal on 2.3.5?
Click to expand...
Click to collapse
Is it so hard to read posts carefully?
I found this https://www.youtube.com/watch?v=-YAKGRblIuw
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p9
What part of the command do i change for a yp-g70 venturi? Also can i extract my twrp 2.8.0.0.zip and get the .img out of it or can i flash the .zip?
This what i used to flash cwm/ entropys daily driver kernel
https://forum.xda-developers.com/showthread.php?t=1445840
su
dd if=/sdcard/zImage of=/dev/block/mmcblk0p11
Well i got cwm installed! Now i just need to flash twrp and then a rom
chris1892006 said:
... Now i just need to flash twrp and then a rom
Click to expand...
Click to collapse
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
jwoegerbauer said:
Notice, that for Lollipop and up to get it running smoothly, you need a device with minimum 2GB RAM and at least 2GHz dual core processor - what since Android 4.4+ must be a ARMv7 one.
Click to expand...
Click to collapse
Thanks i had 4.4.4 up and running but tried flashing 5.1.1 lollipop on cwm and it corrupted the bootloader. Now i cant get into recovery because twrp wouldnt flash over cwm, i tried to flash twrp 2.8.0.0 & it succeeded yet didnt work after a reboot, why? I read the op but i still cant figure out why it didnt work after a reboot? Still remained cwm.
https://forum.xda-developers.com/galaxy-player/development/recovery-twrp-v2-8-0-0-t2867742
http://www.meticulus.co.vu/p/yp-g70.html
@Didgeridoohan
How do i flash twrp over cwm?
Hey... Look at that, you had some progress. Nice.
I've never used CWM, so I wouldn't know.... Sorry.
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
jwoegerbauer said:
@chris1892006
Have you backed up stock recovery IMG through e.g. Flashify app before installing a custom recovery by means of CWM ? Do remember that restoring a backup will essentially wipe any changes made after that backup.
If so then
1. you can restore or flash stock recovery IMG through Fastboot to get CWM out of your system.
2. you can install through TWRP any custom recovery IMG of your choice.
Click to expand...
Click to collapse
thanks only problem is they only make a .zip for twrp for my device... I don't know how to flash it.
That's a really old android version, I'm not sure if it's possible. If you don't have access to a PC, try to ask a friend if they could do it for you, just to be safe. Trying to modify stuff within android, especially on such an old version, with probably unsupported software could result in a bricked device.
Thanks but I finally got TWRP and Lollipop 5.1.1 installed it took an ADB Sideload from a PC to sideload the twrp.zip file for my device and now I'm up and running and very happy to say the very least. Sure I bricked it 3 times in the process but was always able to recover using ODIN and having the proper files on hand.
Now im having an issue with xda on the device where the xda app wont let me sign in and the browser will sign me in but go right back to the sign in page again, idk how to fix it?
I install a dalvik cache wiper with root required and it corrupted the recovery again. So I figured out the exact steps to get this device working perfectly again. Firstly the twrp folder on the external sd card has to be renamed TWRP because it has extra strange characters after the TWRP. Now we know how to restore our backup, we can start by ODIN back to stock, then Framaroot v1.4.1 root the device then download entropys daily driver kernel cwm, the flash it via terminal emulator, reboot, then you have to install meticulous carbon 4.4.4 to fix the partitions and update the cwm to adb sideload the twrp. So you can then flash Meticulus Carbon 5.1.1 and both updates and 5.1.1 pico gapps. Good to go. Meticulus made the kernel overclock to 1.7ghz and it runs pretty darn good honestly. I modded the build.prop vm dalvik heap limit to 384m from 128m to get some extra performance out of it.
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Catter38 said:
Hi,
I just updated to 10.0.9.HD01BA on my OP7T Pro and after that I tried to root it with Magisk by patching the OTA update.
This didn't work and it was stuck at the boot animation, so I extracted the boot.img and patched it with Magisk.
But with the patched version I'm also always stuck at the boot animation.
If I flash the original boot.img again, everything is fine, except that there is no root of course.
I already rooted many OP7 and OP7T and never got this result.
Is Magisk currently not supporting 10.0.9, or am I doing something wrong?
I really don't know what else I could do.
Is someone else experiencing this issue?
Click to expand...
Click to collapse
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Unfortunately, I forgot to uninstall the modules.
I tried the adb command and the device reboots, but it's still in the same bootloop.
I also tried to uninstall the modules with TWRP, but since there isn't a fully working version for the OP7T Pro, this also didn't work.
What's weird is, that the magisk patched version of the boot.img always results in a way smaller file than the original.
The original file is ~100mb, while the patched version is ~40mb.
I don't know if this is normal, but it seems odd.
I also tried it with the canary version of magisk, which results in the same small boot.img.
Looks like I have to stay unrooted until this is fixed.
Ok, finally I got it to work.
Since my girlfriend also has a OP7T Pro and still is on 10.0.8 with root, I simply took her boot image and booted it with fastboot. This also resulted in the same bootloop, but now the adb command worked and I was able to boot a rooted 10.0.8 boot.img. Now I was able to use the direct install of magisk and patched the 10.0.9 installation with it.
I think my problem was, that I did't remove the modules in the first place, which screwed up the whole update.
I still can't explain why I wasn't able to patch the boot.img with magisk. It didn't work on my phone with the canary build of magisk, neither did it work on the phone of my girlfriend with magisk 20.4.
Anyway. Now I have a working 10.0.9 boot.img and can safely upgrade my girlfriends phone too.
Thanks for the help!
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img..... ?
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... Last build... Patched and the original img..... ?
Click to expand...
Click to collapse
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
https://app.box.com/s/at1mhbvpkspg4wfzp16cqppgdvvidese
I'm using it now.... Without problem
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
It seems to be normal. I'm not sure why but it might be due to compression. Anyway, glad you figured it out.
Catter38 said:
Interesting, your patched image also is way smaller than the original.
Did you verify, that it's working?
Click to expand...
Click to collapse
kovacsabesz said:
https://app.box.com/s/9r77wcvk2dnbos87rpr1lfcnmnd091le
Here is.... HD10.0.9BA Patched and the original boot.img.....
Click to expand...
Click to collapse
Would you mind uploading the files again if you can? I'm struggling with my device being in bootloop and I can't remove the module causing it bc I can't access adb with the bootloop. With the stock boot img I'm hoping to boot the device again and remove the bad module via adb
Macusercom said:
Did you disable and delete all Magisk modules before updating to OOS 10.0.9? If not, do the following:
- Boot your phone and enable ADB debugging in dev settings.
- Flash the patched Magisk boot.img.
- During boot connect your device to a PC and enter:
"adb wait-for-device shell magisk --remove-modules"
- Your device should reboot without any modules and you can install them again.
Click to expand...
Click to collapse
Im im a similar situation now, is there a way before removing the modules all i can backup them or atleast access a file or something with the modules names ?
kovacsabesz: can you please reupload the file? Thanks