Related
Just unlocked the bl of my Z5 E6653 flashed
http://forum.xda-developers.com/xperia-z5/development/kernel-andropluskernel-v1-t3246100
and then twrp and now my phone wont boot but i cand connect it is fast boot. What filesh should i flash to get it fixed?
I want to install this rom but i'm new to the z5 and don't know what other kernel/recovery ti try.
http://forum.xda-developers.com/xperia-z5/development/xperia-x-rom-e6653-e6683-z5p-t3388183
NexusGTS said:
Just unlocked the bl of my Z5 E6653 flashed
http://forum.xda-developers.com/xperia-z5/development/kernel-andropluskernel-v1-t3246100
and then twrp and now my phone wont boot but i cand connect it is fast boot. What filesh should i flash to get it fixed?
I want to install this rom but i'm new to the z5 and don't know what other kernel/recovery ti try.
http://forum.xda-developers.com/xperia-z5/development/xperia-x-rom-e6653-e6683-z5p-t3388183
Click to expand...
Click to collapse
If I was you I would use this: http://forum.xda-developers.com/xperia-z5/development/kernel-andropluskernel-v1-t3246100
instead of the XZ rom. I tried this rom and it worked, but at the time I tried it it was a little buggy atleast.
Download Androplus kernel from the page above.
Extraxt the boot.img from the androplus kernel rar file and download and install minimal adb and fastboot.
Make sure you have all drivers installed
Connect your phone in fastboot mode and in the command line opened from minimal adb and fastbot type:
fastboot flash boot boot.img
After that you can download from the same link I put above a twrp recovery img.
Put this img file also in your adb root directory and type fastboot flash recovery twrp.img (your recovery img file might be named different) make sure you change twrp.img as I typed to your filename.
If you want to root your phone (ofcourse probably :laugh download latest supersu zip file which you can flash from within recovery.
First after flashing the kernel and recovery let it make a full boot and see if all is good.
If everything is fine then you can put the supersu zip file on your phone or sd card.
Turn off your phone and turn it back on. As soon as the orange /yellow kinda led starts burning keep pressing volume down button and then you should get into recovery.
Flash the supersu zip and reboot, first reboot might be a bootloop but dont interrupt it, it is supposed to be like that for first boot.
If everything went well you should now be rooted on custom androplus kernel and have recovery
hope this helps
I'm wondering if anyone tried to root Shield Tablet with Magisk without custom recovery? In the guide it says you have to patch the stock boot.img. I'm just a bit worried since the stock boot.img you can download from Nvidia is for firmware 5.2 and I have the 5.3 OTA on my tablet.
I want to do the following:
"Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the*latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select*.img.tar. For normal users leave it as the default*.img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in*[Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img"
This method hasn't any sense for our tablet. If you don't want install twrp you can do "boot only" twrp.
Make full backup and flash Magisk.zip.
fastboot boot NameOfTwrp.img
dzidexx said:
This method hasn't any sense for our tablet. If you don't want install twrp you can do "boot only" twrp.
Make full backup and flash Magisk.zip.
fastboot boot NameOfTwrp.img
Click to expand...
Click to collapse
Thanks! This was a better method! I successfully installed Magisk without installing twrp.
erik90 said:
Thanks! This was a better method! I successfully installed Magisk without installing twrp.
Click to expand...
Click to collapse
What is the point in not installing TWRP? TWRP is much more functional in every way than stock recovery.
redpoint73 said:
What is the point in not installing TWRP? TWRP is much more functional in every way than stock recovery.
Click to expand...
Click to collapse
I just wanted to root my Shield Tablet and still be able to receive OTA´s if there will be any more.
Don´t have the need for custom recovery since I like the tablet stock with exception for root, I tried a few custom roms but there was always some bugs.
One feature from stock I can´t live without is the Button Mapper, it´s amazing that it works with all bluetooth controllers that I have tried.
erik90 said:
I just wanted to root my Shield Tablet and still be able to receive OTA´s if there will be any more.
Click to expand...
Click to collapse
The OTAs install properly with TWRP and root.
https://www.xda-developers.com/motorola-one-power-moto-z3-play-twrp/
Support Status: Current
Maintainer: kaneawk, erfanoabdi
Code Name: beckham
Device Tree / files
NOTE: Monthly security updates may break
decryption of /data in TWRP. MTP does not
work at this time, but you can use adb to transfer files.
Click to expand...
Click to collapse
https://twrp.me/motorola/motorolamotoz3play.html
The new twrp works fine
Hopefully this means more support in the future. Did you flash or boot? Curious if it will bootloop if I flash the img
Installation:
If you do not already have TWRP installed: Download twrp img. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot twrp.img
This will temporarily boot TWRP on your device.
I'm aware of how to boot TWRP on my device. I was wondering if it would be possible to *flash* it though. As I understand it you need the TWRP zip compiled and was wondering if you got that working or not for this device.
Booting is fine for now but I need to have TWRP as recovery for bootloops when I don't have my PC available
Edit for spelling
what works
I have downloaded the twrp.img
I ran fastboot boot twrp.img
I have downloaded magisk 17.1 and flashed it via twrp
Installed Magisk Modules: AdgaurdDNS, Greenify4Magisk, and Viper4Android FX
what doesn't work
installed xposed framework via magisk -> caused bootloop
Pretty sure it's an Xposed bug because Xposed bootloops on any device that's got 8.1 with latest patches
So if we can unlock the bootloader, and boot to twrp, can we not install supersu from there? Or am I understanding this wrong?
Magisk is superior in about every way. Also super su isn't being developed anymore
Ah, I'll look into it more. My last phone was forever old, and my only option was SuperSU. Thanks!
please any help update the download TWRP file, because in github the developers say mount vendor is working, but the file in twrp webpage its old.
Has anyone tried booting this on the Sprint version
Help me plz
hello, Im trying to install the twrp recovery but i cant, its happing a error
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.999s
and i dont know how to solve, please help me
Trwp can't be installed on this device as far as I know. Available twrp is for booting purposes only.
Fastboot boot twrp.img
Click to expand...
Click to collapse
Whenever I use the command fastboot boot twrp.img, it boots just fine but if I try to use fastboot flash recovery twrp.img, it gives me an invalid partition name recovery error. I am trying to root the device. To my understanding, if you just boot into TWP, its only temporary. I guess my question is, is flashing the .img necessary and if so, why is it giving me this error? I got the .img from the offical website, its in the same folder as fastboot, and even boots right up if using the boot command so the image isnt corrupt. Any suggestions?
You don't need twrp for root. Boot the image and use magisk to root your device systemlessly. SuperSU is depreciated. And twrp hasn't been built for this device in a flashable format. You can only boot temporarily and install magisk.
?
darkdaemon32 said:
You don't need twrp for root. Boot the image and use magisk to root your device systemlessly. SuperSU is depreciated. And twrp hasn't been built for this device in a flashable format. You can only boot temporarily and install magisk.
Click to expand...
Click to collapse
So can I root this device without installing TWRP? I want to continue using my mods (which I believe TWRP will break) and I don't really care about the custom recovery at this point but want root access for a few select items like AdAway.
There isn't even a way to currently INSTALL TWRP on the z3. The only way to use twrp is with fastboot boot. And you use this to temporarily boot to twrp and flash the magisk installer zip for root. Magisk is systemless and doesn't modify system so you should be able to use all apps that detect system modifications such as gpay etc.
Would anyone help me? I saved the Magisk file to internal memory, but when I try to install TWRP (fastboot boot twrp.img) the internal memory files are encrypted.
How do I decrypt these files so I can do the Root?
Hi there,
I´ve got an Update for my BV9900.
My Problem is, I can use this BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 Version
only for non rooted StockRom.
If I root my phone first, the Update will reboot TWRP Recovery and not his Flashmode.
If I Start the Update on an unrooted System it works.
But then I have the Problem, that I cannot root it anymore with my boot.img and twrp.img.
Can someone help me?
Kind Regards,
Chris
Please install the magisk manager app on your phone and check what if the ramdisk is "no" or "yes"
Ramdisk is Set "no"
dhchris said:
Ramdisk is Set "no"
View attachment 5267407
Click to expand...
Click to collapse
Here is a detailed guide
Install Magisk in Recovery and Root Android [No Ramdisk]
In this guide, we will show you how to install Magisk in the recovery partition and then root your Android device that doesn't have Ramdisk.
www.droidwin.com
dhchris said:
Hi there,
I´ve got an Update for my BV9900.
My Problem is, I can use this BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 Version
only for non rooted StockRom.
If I root my phone first, the Update will reboot TWRP Recovery and not his Flashmode.
If I Start the Update on an unrooted System it works.
But then I have the Problem, that I cannot root it anymore with my boot.img and twrp.img.
Can someone help me?
Kind Regards,
Chris
Click to expand...
Click to collapse
The problem is that your phone doesn't support 'ramdisk'. So to root, you now have to patch recovery.img
This will also disable DM verity
Hope i have understood your question properly. Very sorry if i have misunderstood it.
I tried it with my patched File before but get a bootloop.
I'll try it a seconds time with patching from my rooted System
Tab E said:
The problem is that your phone doesn't support 'ramdisk'. So to root, you now have to patch recovery.img
Magisk will also disable DM verity.
Click to expand...
Click to collapse
dhchris said:
I tried it with my patched File before but get a bootloop.
I'll try it a seconds time with patching from my rooted System
Click to expand...
Click to collapse
Once you solve the bootloop, before patching the img try the command
adb disable-verity
It might be DM verity that is stopping your phone to boot
I´ve got a TWRP Recovery image that I flashed.
Should I patch these or the recovery from stock Image?
The Stock that I have is the actual running version not the version that I want to update (come from OTA)?
adb disable-vertiy doesn´t work:
"verity cannot be disabled/enabled - USER build"
flashing the magisk-patched file generated in new version doesn´t work. bootloop
Do you know about a flashable BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 ?
dhchris said:
flashing the magisk-patched file generated in new version doesn´t work. bootloop
Do you know about a flashable BV9900_EEA_S900AA_V1.0_20200522V12_20200523-0035 ?
Click to expand...
Click to collapse
Sorry I didn't see your earlier message. Did you flash the patched TWRP recovery or patched stock recovery?
patched stock from older rom. the newer rom is only on ota.
I´ve no files from this
EDIT:
The ways I tried it:
1. Stock system with installed magisk/TWRP - root works but many functions are buggy
so I tried to flash the new version by OTA. Download fine, but reboot to recovery (not flashing update)
2. Installed OTA (new version) on clean stock first rom.
Update flashing works fine but cannot install root (TWRP/Magisk from patched old recovery version)
Should I try to patch the older twrp(working on stock)?
Or should I disable the option in magisk "perserve force encryption"?
Or can I find any patchable file on running system?
Many questions :-(
When you flashed TWRP did you flash it to both partitions?
fastboot flash recovery_a twrp.img
fastboot flash recovery_b recovery.img
Things i="dhchris, post: 84768453, member: 598070"]
patched stock from older rom. the newer rom is only on ota.
I´ve no files from this
EDIT:
The ways I tried it:
1. Stock system with installed magisk/TWRP - root works but many functions are buggy
so I tried to flash the new version by OTA. Download fine, but reboot to recovery (not flashing update)
2. Installed OTA (new version) on clean stock first rom.
Update flashing works fine but cannot install root (TWRP/Magisk from patched old recovery version)
Should I try to patch the older twrp(working on stock)?
Or should I disable the option in magisk "perserve force encryption"?
Or can I find any patchable file on running system?
Many questions :-(
[/QUOTE]
I think try disabling that option. It sometimes causes bootloops
Tab E said:
When you flashed TWRP did you flash it to both partitions?
fastboot flash recovery_a twrp.img
fastboot flash recovery_b recovery.img
Click to expand...
Click to collapse
No, ok
Must try it a bit later.
Have to go out with the family
Try to flash the patched on a and b.
If doesnt work, will try flashing without encryption.
Okay flash recovery_a / recovery_b doesn´t work. command error.
flashing patched without verification works, but no twrp
dhchris said:
Okay flash recovery_a / recovery_b doesn´t work. command error.
flashing patched without verification works, but no twrp
Click to expand...
Click to collapse
OK. Now that you have root access, try flashing TWRP with the TWRP app. After flashing, Reboot to recovery from the TWRP app
TWRP-App in Rootmode crashes, trwp-app non rootmode showns not my device
Told me, device not rooted
Try https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en
App
had to reflash the stock system. bootloop...
now I tried it again.
Installed Stock, then updated it by OTA.
Installed MagiskManager and patched...
rebooted and flashed patched twrp.img in recovery.
installed the twrp manager... no root
MagiskManager shows me Installed N/A
dhchris said:
had to reflash the stock system. bootloop...
now I tried it again.
Installed Stock, then updated it by OTA.
Installed MagiskManager and patched...
rebooted and flashed patched twrp.img in recovery.
installed the twrp manager... no root
Click to expand...
Click to collapse
Do you have twrp? If yes flash the magisk zip. By installing twrp, you are removing the root access gains by patching the stock recovery.
So, backround is, I want to use AFWall+, which requires root, which I would like to use Magisk for.
In order to get Magisk I need TWRP, I learned so far.
I run LOS 18.1 and I used the lineage recovery/fastboot to flash it (according to the offical LOS-guide).
Changing the recovery is not the easiest thing for me.
Found this thread: https://forum.xda-developers.com/t/from-lineage-recovery-to-twrp-recovery.4253669/
but this seems to be very Samsung specific using Odin (I use a Pixel 4)
I also tried this guide: https://www.droidwin.com/boot-into-recovery-from-fastboot-mode/
but this just "deleted" my OS.
This is why I will be asking a few questions prior starting a new attempt, so please bear with my incompetence
At TWRP I read, I have to install a LZMA ramdisk kernel in order to get TWRP (https://twrp.me/google/googlepixel4.html).
I would go for elementalx, assuming it does support lzma.
From here things are getting tricky for me.
TWRPs guide tells me to get the kernel first, at Elementalx I get the instructions to use TWRP to install
It does say however its not neccessary to install TWRP permanently, but I would like to, because no matter what I want to do with my phone it requires TWRP. So I would like to change the recovery permanently.
The easiest way to do all of this seems to be this guide: https://elementalx.org/how-to-install/
But that will not change my recovery permanently...
What I would do (using a videoguide, because you know, I'm a noobish newbie):
1. Download TWRP img + zip, Magisk zip, Elementalx zip to my fastboot folder
2. Copy the Zips of TWRP, Magisk and Elementalx to my device
3. On my PC -> in the fastboot folder I run cmd as administrator
4. boot into bootloader
5. using cmd -> fastboot boot twrp.img
6. using TWRP -> flash the custom kernel
7. using TWRP -> flash TWRP
8. check if TWRP was proper installed: in TWRP -> boot -> recovery
hopefully the recovery was replaced
9. using TWRP - > flash Magisk
10. reboot
Would anyone please tell me if this will work?
Is there anything I need to do to avoid horrible things to happen?
This is not a request to blame something that could happen on someone afterwards. I just want to minimize the risk...
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Thank you.
TWRP got stuck booting: I see the logo, "teamwin" and the version used 3.5.2_10-0
Everything was up to date, I'll try it again with an older version of TWRP.
Well, I dont know how to boot into LOS. It just froze on the mentioned screen.
Has anyone a idea what to do?
CodyF86 said:
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Click to expand...
Click to collapse
Ok, I tried it my way - it wont work (of course). Maybe TWRP is still not supported for Android 11.
Now I'll try it your way (thx again).
In order to flash the kernel, I'll have to unzip the elementalx file, I assume. And boot the avaible image, which is called "dtbo.img".
I'll give this a go...
CodyF86 said:
You can just flash the kernel from fastboot no twrp needed. Just fastboot flash boot boot.img.
You can have magisk patch a boot image then flash it from fastboot as mentioned above.
Usually its just recommended to fastboot boot twrp.img instead of flashing it to the actual device incase you want to revert back and install an OTA.
You can also just download the magisk apk from the device to patch the boot image, flash kernel from fastboot, then reboot with root and have magisk finish doing what it needs to do.
Click to expand...
Click to collapse
fastboot flash boot boot.img did not work. I renamed the file to boot.img (did not mention this before).
Tried it twice, but nothing worked afterwards, not even recovery and I was not able to turn the device off.
Had to flash LOS again.
I also tried flashing the kernel using sideload while flashing the rom again.
Sideload did work, BUT the wifi was not working at all.
I dont want to bother you, but might there be another way?
I might have found something:
[VERY EASY GUIDE] ADB/FASTBOOT/RECOVORY *FULL GUIDE* for flashing ROMs, Kernels, APKs
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details. This procedure is designed to be EXTREMELY EASY and for people using...
forum.xda-developers.com
uppon2 said:
That is all. Keep in mind things like wifi might not work if you forget to flash the kernel modules! - Just be sure it is always a 2 step process.
Click to expand...
Click to collapse
This is what I am experiencing when using sideload. It does install the kernel, but wifi wont work. I guess I do need a working (permanently or temporarly) recovery.
caraman said:
I might have found something:
[VERY EASY GUIDE] ADB/FASTBOOT/RECOVORY *FULL GUIDE* for flashing ROMs, Kernels, APKs
Keep in mind bootloader unlock will not work if you have done the latest OTA update without previously using supercid. See bootloader unlock guide below for more details. This procedure is designed to be EXTREMELY EASY and for people using...
forum.xda-developers.com
This is what I am experiencing when using sideload. It does install the kernel, but wifi wont work. I guess I do need a working (permanently or temporarly) recovery.
Click to expand...
Click to collapse
Wifi is usually a kernel module that gets loaded through an init script on boot. It's possible to build the wifi module built-in to the kernel, which makes it so it doesn't have to load separately through an init script.
So if youre not using the stock kernel you'd have to ask whoever makes the kernel you are using.
caraman said:
So, backround is, I want to use AFWall+, which requires root, which I would like to use Magisk for.
In order to get Magisk I need TWRP, I learned so far.
I run LOS 18.1 and I used the lineage recovery/fastboot to flash it (according to the offical LOS-guide).
Changing the recovery is not the easiest thing for me.
Found this thread: https://forum.xda-developers.com/t/from-lineage-recovery-to-twrp-recovery.4253669/
but this seems to be very Samsung specific using Odin (I use a Pixel 4)
I also tried this guide: https://www.droidwin.com/boot-into-recovery-from-fastboot-mode/
but this just "deleted" my OS.
This is why I will be asking a few questions prior starting a new attempt, so please bear with my incompetence
At TWRP I read, I have to install a LZMA ramdisk kernel in order to get TWRP (https://twrp.me/google/googlepixel4.html).
I would go for elementalx, assuming it does support lzma.
From here things are getting tricky for me.
TWRPs guide tells me to get the kernel first, at Elementalx I get the instructions to use TWRP to install
It does say however its not neccessary to install TWRP permanently, but I would like to, because no matter what I want to do with my phone it requires TWRP. So I would like to change the recovery permanently.
The easiest way to do all of this seems to be this guide: https://elementalx.org/how-to-install/
But that will not change my recovery permanently...
What I would do (using a videoguide, because you know, I'm a noobish newbie):
1. Download TWRP img + zip, Magisk zip, Elementalx zip to my fastboot folder
2. Copy the Zips of TWRP, Magisk and Elementalx to my device
3. On my PC -> in the fastboot folder I run cmd as administrator
4. boot into bootloader
5. using cmd -> fastboot boot twrp.img
6. using TWRP -> flash the custom kernel
7. using TWRP -> flash TWRP
8. check if TWRP was proper installed: in TWRP -> boot -> recovery
hopefully the recovery was replaced
9. using TWRP - > flash Magisk
10. reboot
Would anyone please tell me if this will work?
Is there anything I need to do to avoid horrible things to happen?
This is not a request to blame something that could happen on someone afterwards. I just want to minimize the risk...
Click to expand...
Click to collapse
Magisk should not be that complicated. All the hard work has been done and can be found in Magisk documentation. There are install instructions for just about any type device and if there is LOS for your device I'm sure it is covered. The latest Magisk is not TWRP flashable the same way as it used to be and newer devices often don't have ramdisk in boot image and root is achieved thru recovery instead. You referenced several threads and guides but no indication of Magisk instructions. Read the Magisk installation instructions for your device type, they're not just suggestions, they work.