Hi, please help me,
i start update, and i have root before i start. The phone has been updated for over 2 hours. is bootanimation and nothing like that for 2 hours. How long can it take? can you stop the upgrade and go to flashboot and upload the system via flashboot?
flogger998 said:
Hi, please help me,
i start update, and i have root before i start. The phone has been updated for over 2 hours. is bootanimation and nothing like that for 2 hours. How long can it take? can you stop the upgrade and go to flashboot and upload the system via flashboot?
Click to expand...
Click to collapse
Did you flash magisk? Did you flash full update and not just incremental?
whizeguy said:
Did you flash magisk? Did you flash full update and not just incremental?
Click to expand...
Click to collapse
I have installed magisc, the system itself has proposed a full update, wrote that I have root and need to do a full update
Absolutely... But did you flash magisk AFTER the update? Since update will remove it.
What you could do is fastboot in to twrp (if you don't have twrp already) and install magisk
whizeguy said:
Absolutely... But a
Did you flash magisk AFTER the update? Since update will remove it.
What you could do is fastboot in to twrp (if you don't have twrp already) and install magisk
Click to expand...
Click to collapse
No. I did not flash the magisc because the update was done from the system position, not twrp, and I'm from 3 hours on the bootlogo stage.
flogger998 said:
No. I did not flash the magisc because the update was done from the system position, not twrp, and I'm from 3 hours on the bootlogo stage.
Click to expand...
Click to collapse
If I could turn off the update and run the twrp, I would handle it but I do not know how to turn it off, and if it can wait.
flogger998 said:
No. I did not flash the magisc because the update was done from the system position, not twrp, and I'm from 3 hours on the bootlogo stage.
Click to expand...
Click to collapse
There you have the issue. After ota from system you need to get into Magisk app, press install, press install and choose "install to inactive slot" to keep root.
You need to flash magisk from fastboot, or a fast booted twrp to get it working.
You are stuck in bootloop, it won't boot. You can turn the phone off by press and hold power button for 15 seconds.
Also: the update is already done so don't worry about that
And if you did have twrp that is also replaced with the update.
whizeguy said:
There you have the issue. After ota from system you need to get into Magisk app, press install, press install and choose "install to inactive slot" to keep root.
You need to flash magisk from fastboot, or a fast booted twrp to get it working.
You are stuck in bootloop, it won't boot. You can turn the phone off by press and hold power button for 15 seconds
Click to expand...
Click to collapse
can you stop the update? is there any key combination that reboots the phone? I do not care about the roe, I want my phone to work
flogger998 said:
can you stop the update? is there any key combination that reboots the phone? I do not care about the roe, I want my phone to work
Click to expand...
Click to collapse
I have twrp, holding the power button for 30 seconds is not effective
flogger998 said:
I have twrp, holding the power button for 30 seconds is not effective
Click to expand...
Click to collapse
You had it got replaced.
Press power and volume down for 15 seconds then. Should do the trick
After next OTA:
Let it do the update (DO NOT REBOOT!)
start magisk app go to downloads
Search for TWRP A/B
Install that one. (should only be one hit) (DO NOT REBOOT)
Go to main screen of magisk app
Click install, install, install to inactive slot (after ota)
Now reboot and you have twrp and magisk.
whizeguy said:
You had it got replaced.
Press power and volume down for 15 seconds then. Should do the trick
After next OTA:
Let it do the update (DO NOT REBOOT!)
start magisk app go to downloads
Search for TWRP A/B
Install that one. (should only be one hit) (DO NOT REBOOT)
Go to main screen of magisk app
Click install, install, install to inactive slot (after ota)
Now reboot and you have twrp and magisk.
Click to expand...
Click to collapse
THX, holding the power button with volume up works. I am in flashboot and I am loading the system from the beginning with the script found on xda. This script has already helped me once, how I managed to remove the system
flogger998 said:
THX, holding the power button with volume up works. I am in flashboot and I am loading the system from the beginning with the script found on xda. This script has already helped me once, how I managed to remove the system
Click to expand...
Click to collapse
Bro. All you need to do is flash magisk and it will boot
flogger998 said:
THX, holding the power button with volume up works. I am in flashboot and I am loading the system from the beginning with the script found on xda. This script has already helped me once, how I managed to remove the system
Click to expand...
Click to collapse
everything works. good that I made a backup before the upgrade. Thanks to a good man. May God grant in children: D
flogger998 said:
everything works. good that I made a backup before the upgrade. Thanks to a good man. May God grant in children: D
Click to expand...
Click to collapse
Nice to hear man got one already hehe may she be healthy then just remember the steps above for next OTA mate and you will be set
whizeguy said:
You had it got replaced.
Press power and volume down for 15 seconds then. Should do the trick
After next OTA:
Let it do the update (DO NOT REBOOT!)
start magisk app go to downloads
Search for TWRP A/B
Install that one. (should only be one hit) (DO NOT REBOOT)
Go to main screen of magisk app
Click install, install, install to inactive slot (after ota)
Now reboot and you have twrp and magisk.
Click to expand...
Click to collapse
I did as you said. update installed, everything works as it should. Thanks a lot again.
Related
A burst of fearsome energy overtook me tonight and I just had to root my phone
Kingoroot, Kingroot, Towelroot etc didn't work. Then I read about this thing called TWRP.. sounds great, I said.
Unlocked the bootloader, got TWRP recovery going, tested it out, got ready to add SuperSU and the one that gets rid of bootloader unlocked screen.
Boot loop. Stuck on the Motorola logo. It aint going anywhere.
I've tried all of the suggestions I could find so far here, like using mfastboot to clear cache and user data. It's looking like a dead end. I was following the instructions on a youtube video so of course I didn't back up anything before I tried SuperSU Should I cut my losses and try the stock firmware, or could I do more damage that way?
This is going to ruin my weekend, isn't it?
bootloophell said:
A burst of fearsome energy overtook me tonight and I just had to root my phone
Kingoroot, Kingroot, Towelroot etc didn't work. Then I read about this thing called TWRP.. sounds great, I said.
Unlocked the bootloader, got TWRP recovery going, tested it out, got ready to add SuperSU and the one that gets rid of bootloader unlocked screen.
Boot loop. Stuck on the Motorola logo. It aint going anywhere.
I've tried all of the suggestions I could find so far here, like using mfastboot to clear cache and user data. It's looking like a dead end. I was following the instructions on a youtube video so of course I didn't back up anything before I tried SuperSU Should I cut my losses and try the stock firmware, or could I do more damage that way?
This is going to ruin my weekend, isn't it?
Click to expand...
Click to collapse
If you can still boot to your custom recovery its really not a big deal. Just install the ROM zip of your choosing and appropriate gapps. If you are boot looped when it starts to reboot just hold in the power button for about 10 seconds till it powers off then press and hold volume down while still keeping the power button pressed. After about 5 seconds or so of holding both buttons stop pressing both together. If done correctly you should be at the boofloader screen.
n0ts0smart said:
If you can still boot to your custom recovery its really not a big deal. Just install the ROM zip of your choosing and appropriate gapps. If you are boot looped when it starts to reboot just hold in the power button for about 10 seconds till it powers off then press and hold volume down while still keeping the power button pressed. After about 5 seconds or so of holding both buttons stop pressing both together. If done correctly you should be at the boofloader screen.
Click to expand...
Click to collapse
Yes, I can get to the bootloader. Factory reset there and reset using TWRP doesn't fix the bootloop. That's kinda where I am right now.
Uninstalling SuperSU did it! I used the un-su zip file.
Do you have one of the following 1)Motorola USB drivers for your PC and fastboot or mfastboot/adb setup for your device? 2)ROM zip on your internal storage. 3)A USB OTG drive? Any of these will work. Let me know which you have and we will go from there.
n0ts0smart said:
Do you have one of the following 1)Motorola USB drivers for your PC and fastboot or mfastboot/adb setup for your device? 2)ROM zip on your internal storage. 3)A USB OTG drive? Any of these will work. Let me know which you have and we will go from there.
Click to expand...
Click to collapse
It's ok, I'm back in business - the issue was the installation of the latest version of SuperSU. I used Install from SD Card in TWRP to install the SuperSU remover and it booted fine.
Taking my time now because I need this phone, I'm living in a new country. I backed up and tried an older SuperSU but didn't work - I suppose by doing a factory reset I might have done something that stops a root.
Edit: this http://forum.xda-developers.com/showpost.php?p=63615067
Download the latest stable build of super SU from Chainfires site here. http://download.chainfire.eu/supersu-stable
Then just flash the zip you downloaded in TWRP. You don't need the systemless version of SU if that is what you were trying to do.
n0ts0smart said:
Download the latest stable build of super SU from Chainfires site here. http://download.chainfire.eu/supersu-stable
Then just flash the zip you downloaded in TWRP. You don't need the systemless version of SU if that is what you were trying to do.
Click to expand...
Click to collapse
I think that was the one that bootlooped it. I'll be doing a backup first this time
My main reason for posting my solution in this thread is in case the same thing happens to someone else. Removing SuperSU with that un-su.zip solved it for me.
Hey Team, was hoping I could get some assistance. I updated SuperSU (was prompted to) and now I can only boot the phone into TWRP. If I tell TWRP to reboot system it still only boots into TWRP. I think this is probably something simple, but I don't have a clue.
Thanks ahead of time.
for some reason after a dozen reboots it started working on it's own. good luck all.
XD same here but i guess i keep rebooting and see if it gets with it
kingkea said:
Hey Team, was hoping I could get some assistance. I updated SuperSU (was prompted to) and now I can only boot the phone into TWRP. If I tell TWRP to reboot system it still only boots into TWRP. I think this is probably something simple, but I don't have a clue.
Thanks ahead of time.
Click to expand...
Click to collapse
MykieMedjool said:
XD same here but i guess i keep rebooting and see if it gets with it
Click to expand...
Click to collapse
You may experience same issue as I did (started after updating to http://forum.xda-developers.com/p8max/general/marshmallow-dav-701l-real-life-t3409159:). If so, then do these steps:
Make sure you have no DLOAD directory on SD card
Hold POWER + VOLUME UP until phone reboot
Release POWER
Phone should boot into Huawei eRecovery
Release VOLUME UP
Click "Reboot" button
Phone should now boot into system and not recovery (TWRP)
You will have to do the above steps each time you have booted into TWRP
For whatever reason the button combinations seem messed up on my phone. This is how they work on my phone after upgrading to http://forum.xda-developers.com/p8max/general/marshmallow-dav-701l-real-life-t3409159:
POWER + VOLUME UP = Huawei eRecovery
POWER + VOLUME DOWN = fastboot
POWER + VOLUME UP + VOLUME DOWN = recovery (TWRP)
Hello,
I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.
Please help, how to root my Mate 9?
hi, you must install busybox from magisk modules. But huawei changed file system to erofs. Because of some folders only read. We cant delete and change anything from system anymore.
And adaway is not working.
i downgraded to b191.
mavera said:
hi, you must install busybox from magisk modules. But huawei changed file system to erofs. Because of some folders only read. We cant delete and change anything from system anymore.
And adaway is not working.
i downgraded to b191.
Click to expand...
Click to collapse
Magisk does not change anything in system folder. Magisk is not enabled therefore I cannot install busybox. In Emui9 there was a workaround but seems it doesn't work anymore.
You must press to volume up and power buttons when opening for magisk enabling.
SonOfTheRain said:
Hello,
I was using Magisk wihtout any issue until last update of my Mate 9. Now software version is 9.1.0.252 (C432E7R1P8) and as after every upgrade I re-patch my recovery_ramdis.img and patch from fastboot. In order to boot with root, I used recovery mode and it entered in system with root privileges. After the last update I did the same but recovery mode enters in recovery mode and system shows as non-rooted.
Please help, how to root my Mate 9?
Click to expand...
Click to collapse
Huawei disabled booting to Recovery directly using Vol up and power, you end up in eRecovery instead. Easiest way is to flash magisk patched from fastboot, boot phone, enable USB Debugging in dev options (if you haven't already), and use adb to reboot. Command is:
adb reboot recovery
You can also flash patched image, boot to eRecovery and select the Wipe/Factory reset option, this will boot to recovery which is now Magisk so it'll boot to system with magisk. (Be careful though as the wipe command will still be there, so if you flash back recovery and boot to it your phone will automatically wipe. You can remove the file /cache/recovery/command to prevent this)
ante0 said:
Huawei disabled booting to Recovery directly using Vol up and power, you end up in eRecovery instead. Easiest way is to flash magisk patched from fastboot, boot phone, enable USB Debugging in dev options (if you haven't already), and use adb to reboot. Command is:
adb reboot recovery
You can also flash patched image, boot to eRecovery and select the Wipe/Factory reset option, this will boot to recovery which is now Magisk so it'll boot to system with magisk. (Be careful though as the wipe command will still be there, so if you flash back recovery and boot to it your phone will automatically wipe. You can remove the file /cache/recovery/command to prevent this)
Click to expand...
Click to collapse
Thank you for information. So we returned back to "tethered jailbreak" times with Apple Is there any workaround for this or so far the only solution? Wipe data option is quite unsafe for me, easy to forget and after firmware update to have a wiped device.
SonOfTheRain said:
Thank you for information. So we returned back to "tethered jailbreak" times with Apple Is there any workaround for this or so far the only solution? Wipe data option is quite unsafe for me, easy to forget and after firmware update to have a wiped device.
Click to expand...
Click to collapse
It will loop to recovery after you boot to magisk the first time, so each normal reboot will lead to Magisk. You can force eRecovery/normal boot if you plug in USB and boot holding vol up.
ante0 said:
It will loop to recovery after you boot to magisk the first time, so each normal reboot will lead to Magisk. You can force eRecovery/normal boot if you plug in USB and boot holding vol up.
Click to expand...
Click to collapse
It will loop to recovery if battery dies or if I shut down the phone and boot again or it will lead to non Magisk environment?
SonOfTheRain said:
It will loop to recovery if battery dies or if I shut down the phone and boot again or it will lead to non Magisk environment?
Click to expand...
Click to collapse
I haven't actually tested what happens if battery dies. It will loop if you shut down.
ante0 said:
I haven't actually tested what happens if battery dies. It will loop if you shut down.
Click to expand...
Click to collapse
I have rooted my device with 9.1 magisk but after root dialer and messaging app not worked and i rollback to 9.0 with very difficulty. If any one know how to root then i can told.
Azan Mughal said:
I have rooted my device with 9.1 magisk but after root dialer and messaging app not worked and i rollback to 9.0 with very difficulty. If any one know how to root then i can told.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/how-to/fix-messages-dialer-9-1-root-required-t3955964
I need local.prop from product/etc/prop/local.prop from emui 9.1.0.252 any one 9.1 rooted user can help
Azan Mughal said:
I need local.prop from product/etc/prop/local.prop from emui 9.1.0.252 any one 9.1 rooted user can help
Click to expand...
Click to collapse
Here you go
SonOfTheRain said:
Here you go
Click to expand...
Click to collapse
Thanks bro
SonOfTheRain said:
Here you go
Click to expand...
Click to collapse
this file is for root?
Hi guys, so i have an untouched p10 on the version above, to install magisk is it as easy as asking one of you for the RECOVERY_RAMDIS.img (not yet in the firmware database) and patch it if it hasnt using pc then also on the pc rebooting to recovery and done? Also has restart and flat battery been tested? I read above that you must use shutdown
Its a vtr-l29 if it makes a difference
How long does it take normally after installing magisk to reboot back to system?
shAlunite said:
How long does it take normally after installing magisk to reboot back to system?
Click to expand...
Click to collapse
not more than 5-8Min.
By the way what is you device ?
This is an unofficial and experimental build of TWRP which was tested on the Samsung Galaxy Tab S7 FE (SM-T735) model only.
I used TWRP Samsung Galaxy Tab S7+ 5G device tree by ianmacd and modified it.
MTP doesn't work at the moment.
If you flash a GSI, be sure to wipe the metadata partition along with the data partition.
You might need to flash the neutralized vbmeta image.
Installing TWRP: Flash both files with Odin in the AP slot.
Kernel Source (I used the kernel which was in the stock recovery)
Device Tree Source
As always, be sure to backup your data in case something goes wrong.
Edit: I apologize to everyone for taking 1 year to update this thread.
Disclaimer:
No guarantees that everything would work. I am not responsible for any damages caused from this.
Thank You for your contribution, I hope to see a stable TWRP or other recovery
Will this work with T733?
mcgomfer said:
Will this work with T733?
Click to expand...
Click to collapse
Read the description again, slowly.
Sorry to ask such a noob question but how do I download and install this? Ive got my tab s7 fe rooted with magisk on stock rom and Im far from new to flashing recoveries and roms, but there is no zip to flash or anything, how do I use it?
Hi, My bro.
Can this be used to install GSI?
billy996 said:
Hi, My bro.
Can this be used to install GSI?
Click to expand...
Click to collapse
Hello,
Yes, you can install a GSI with this, I've flashed the AOSP GSI and it worked as intended.
BDog21 said:
Sorry to ask such a noob question but how do I download and install this? Ive got my tab s7 fe rooted with magisk on stock rom and Im far from new to flashing recoveries and roms, but there is no zip to flash or anything, how do I use it?
Click to expand...
Click to collapse
Hello,
I've updated the post with the files added.
dhruv22592 said:
Hello,
I've updated the post with the files added.
Click to expand...
Click to collapse
Can you flash these together by putting the vbmeta in userdata and TWRP in AP?
lewmur said:
Can you flash these together by putting the vbmeta in userdata and TWRP in AP?
Click to expand...
Click to collapse
Hello,
How I had flashed these files on my tab was by flashing them one by one. Alternatively, you can flash vbmeta in the USERDATA slot.
dhruv22592 said:
Hello,
How I had flashed these files on my tab was by flashing them one by one. Alternatively, you can flash vbmeta in the USERDATA slot.
Click to expand...
Click to collapse
Doing both at the same time doesn't work. Bootloop. Had to flash stock and start from scratch to get it working again. Then I flashed vbmeta which then required a factory reset. Did minimal setup and then flashed TWRP but couldn't get it to boot to recovery so TWRP got overwritten. I unchecked auto reboot in Odin prior to flash and when it finished held power and vol down till screen blanked and then switch to vol up. But when it reached the screen saying to push power to continue it didn't continue until I finally released vol up. Then it booted system instead of recovery. I held vol up for several minutes before finally releasing it.
lewmur said:
Doing both at the same time doesn't work. Bootloop. Had to flash stock and start from scratch to get it working again. Then I flashed vbmeta which then required a factory reset. Did minimal setup and then flashed TWRP but couldn't get it to boot to recovery so TWRP got overwritten. I unchecked auto reboot in Odin prior to flash and when it finished held power and vol down till screen blanked and then switch to vol up. But when it reached the screen saying to push power to continue it didn't continue until I finally released vol up. Then it booted system instead of recovery. I held vol up for several minutes before finally releasing it.
Click to expand...
Click to collapse
Hello,
This requires a factory reset.
I apologize that i was not clear before but the steps i did were:
1. Reboot my tablet to download mode with adb using "adb reboot download"
2. Flash twrp in the AP slot
3. Then the tab complains about using a custom recovery, force reboot the tab and immediately boot to download mode (by holding both volume buttons and the power button)
4. Then flash vbmeta in the AP slot.
5. Finally, when the tablet automatically reboots, immediately hold the Vol Up+Power button to boot into twrp.
dhruv22592 said:
This requires a factory reset.
I apologize that i was not clear before but the steps i did were:
1. Reboot my tablet to download mode with adb using "adb reboot download"
2. Flash twrp in the AP slot
3. Then the tab complains about using a custom recovery, force reboot the tab and immediately boot to download mode (by holding both volume buttons and the power button)
4. Then flash vbmeta in the AP slot.
Click to expand...
Click to collapse
Tried that. Still wouldn't boot to recovery.
lewmur said:
Tried that. Still wouldn't boot to recovery.
Click to expand...
Click to collapse
Hello,
Which model are you using?
It might slightly differ in the specs, if the model is SM-T733, I would suggest you try this version of TWRP instead.
dhruv22592 said:
Hello,
Which model are you using it might slightly differ in the specs, if the model is SM-T733, I would suggest you try this version of TWRP instead.
Click to expand...
Click to collapse
Sorry, this was meant for another post.
The CPU of SM-T735 is Snapdragon 750G, and the CPU of SM-T733 is Snapdragon 778G.
Does anyone test this TWRP on SM-T733 to run?
dhruv22592 said:
Hello,
This requires a factory reset.
I apologize that i was not clear before but the steps i did were:
1. Reboot my tablet to download mode with adb using "adb reboot download"
2. Flash twrp in the AP slot
3. Then the tab complains about using a custom recovery, force reboot the tab and immediately boot to download mode (by holding both volume buttons and the power button)
4. Then flash vbmeta in the AP slot.
5. Finally, when the tablet automatically reboots, immediately hold the Vol Up+Power button to boot into twrp.
Click to expand...
Click to collapse
after I flash TWRP in step 2 and reboot into download mode. The tablet prompts me to unlock the bootloader again. And as a result, I can't get into TWRP. Please assist thank you
billy996 said:
The CPU of SM-T735 is Snapdragon 750G, and the CPU of SM-T733 is Snapdragon 778G.
Does anyone test this TWRP on SM-T733 to run?
Click to expand...
Click to collapse
did you have any luck getting into TWRP?
dhruv22592 said:
Hello,
This requires a factory reset.
I apologize that i was not clear before but the steps i did were:
1. Reboot my tablet to download mode with adb using "adb reboot download"
2. Flash twrp in the AP slot
3. Then the tab complains about using a custom recovery, force reboot the tab and immediately boot to download mode (by holding both volume buttons and the power button)
4. Then flash vbmeta in the AP slot.
5. Finally, when the tablet automatically reboots, immediately hold the Vol Up+Power button to boot into twrp.
Click to expand...
Click to collapse
Did you ever get TWRP to work? If so, what stock version were you running? I'm thinking I can't get TWRP to run because I'm running the latest update out right now.
mdewii23 said:
Did you ever get TWRP to work? If so, what stock version were you running? I'm thinking I can't get TWRP to run because I'm running the latest update out right now.
Click to expand...
Click to collapse
AFAIK, the ONLY TWRP to work was for the T735 and it was experimental. So far, I'm happy with rooted stock. My performance and battery life seem to be great, so there isn't much pressure to improve with a custom ROM. So long as rooting is possible, you can do your own de-bloating.