so i tried to install viper4android and the driver made my phone be stuck at boot, ( i got it to boot by using the unpached boot image, but now i lost my root functionality)
so what i need is a modded recovery that supports adb
i found a tutorial in the oneplus forums to modify the recovery and give it adb shell posibilities, but thusfar i am unsuccessfull in modding the recovery
the original post describiong how to mod the recovery is located here
my post asking for help is here
the reason i post this topic is for references mainly,
if there is a solution i will link it here as well, so if anyone else runs into it, the solution can be found easily
Viper4android does not work on Android 10
subhnish said:
Viper4android does not work on Android 10
Click to expand...
Click to collapse
sadly i figured that out the hard way
because of the installation of the magisk module, if i use the patched bootloader i keep being stuck in loop.
So if you have any idea how to fix that, that would be nice .
so far the only way i found how to fix this is patching the recovery mode so i could adb from there, but sadly my attempts are unsuccessful
i posted a way to uninstall magisk modules with out a custom recovery on the oneplus one forum, there is a working viper4android for Q that works just fine with out any hassle of getting bootloop which is in the app section on xda viper4android fx 2.7 stable version 2.7.1.6 from march 17 2020, i have installed this version on my phone oneplus7t open beta 2 android 10 and it works just fine. try this out to see if it works i had some issues with a magisjk module and my device was stuck on a bootloop and this got me out of it, the only way i was being able to get in was like you said instlaling the stock boot img with out root, once i installed the boot img with root i would get the bootloop again so i found this method online and it saved my ass with out the need to install any extra stuff worked perfect clearing all the magisk modules from my phone with out losing root.
The way i remove my modules without installing any custom recovery is just by turning off the phone, connect to pc, go to command prompt, type the path of the folder where fastboot and adb is, type the following command: adb wait-for-device shell magisk --remove-modules,(while phone is off) turn phone on wait for it to get to the boot screen it will reboot, once it reboots modules will be uninstalled.
lil_kujo said:
type the following command: adb wait-for-device shell magisk --remove-modules,(while phone is off) turn phone on wait for it to get to the boot screen it will reboot, once it reboots modules will be uninstalled.
Click to expand...
Click to collapse
i've been looking in the pixel forums, and i think i also came a cross a post in the oneplus forums, but the command doesn't seem to work. but i guess that's due to not being able to use adb commands
my first idea was to get a recovery that supports adb, but i was unsuccessfull in modifying the recovery.
the same thing seems to happen with th alternative options i found:
what I tried first:
1
I tried to make an updated init file for the boot image that boots magisk in core-only mode. Modules should be disabled in that one.
I compiled magisk, and got the core-only init file, and replaced in the patched boot.img ( instructions I followed are Post #3 on this thread: https://forum.xda-developers.com/pixel-3a-xl/how-to/magisk-modules-disabler-booting-magisk-t3976625
Sadly, this made it still boot loop.
2 I added overlay.dcoreonly1.zip from this thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sadly, this also makes it boot loop.
for a second there I thought extracting and repackaging was the issue, but tried that as well with the non-patched boot version, and no problems there.
I cannot seem to figure out why this doesn’t work.
any suggestions are very welcome.
Now back on non-rooted version.
after resetting / factory whiping from the recovery , i repatched everything and am back on root again, so for now the issue is gone, but still it would be nice to have some backup if this goes wrong again, so if anyone has an answer to the above, that would still be nice.
on one of the oneplus forums i found this promesing news:
https://github.com/topjohnwu/Magisk/commit/a5d7c41d209527fe7b45a2ef7d031add9b6fad24
so i guess with a new magisk version and booting into safe mode it should be possible to recover.
i've been trying to figure out how to get into safemode, but so far i have no clue.
a google search did not really reveal hw to do that.
Did anyone here find out how to boot into safe mode?
https://support.motorola.com/us/en/Solution/MS148713 - When the phone is working.
From the off phone - hold while starting VOL-
subhnish said:
Viper4android does not work on Android 10
Click to expand...
Click to collapse
it works on my 10
3dekstron said:
https://support.motorola.com/us/en/Solution/MS148713 - When the phone is working.
Click to expand...
Click to collapse
i guess when in bootloop this is a bit useless, but still good to know
senz90 said:
From the off phone - hold while starting VOL-
Click to expand...
Click to collapse
This was indeed the info i was looking for. Thnx for that , ... didn't know it was so simple
i tried it a couple of times, and apparently you need to start pressing volume down when you see the first moto logo
if you hold it down right from the start it won't boot into safe mode
anyway,
This would mean with the new magisk ( when it becomes available ) we would have an easy recovery from a faulty module.
as soon as i find out the how and when, I'll post it here with some instructions
senz90 said:
it works on my 10
Click to expand...
Click to collapse
so did you install any other modules for that / do you have a guide for how you got it to work?
Safe mode - nothing will give at the moment, the modules continue to work.
I found this description:
https://www.didgeridoohan.com/magisk/MagiskModuleIssues#
See:
Disabling/uninstalling modules manually
No custom recovery.
3dekstron said:
Safe mode - nothing will give at the moment, the modules continue to work.
I found this description:
https://www.didgeridoohan.com/magisk/MagiskModuleIssues#
See:
Disabling/uninstalling modules manually
No custom recovery.
Click to expand...
Click to collapse
yeah but i think we have to wait on the next magisk version ( that wil be updated soon). that one will respond to auto-disabling modules when booting into safe mode
senz90 said:
it works on my 10
Click to expand...
Click to collapse
How did you get it to work? I can't get the driver to install properly.
Related
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Hello everyone. I started this thread because I don't think I've seen anything with this issue on my specific phone on this forum. Apologies if this has been discussed before.
Anyway, I'm having issues installing a ROM with adb sideload on TWRP recovery.
I got the ROM and the recovery image from blox2.com (I would post the links but apparently the forum doesn't allow me to...)
Everything works fine, I'm able to boot into TWRP recovery and inititiate the adb sideload, but the process gets stuck when it reaches 28% and throws the error message:
serving: 'BLOX2core-v1.1.1-31217.zip' (~28%) * failed to read command: Success
Click to expand...
Click to collapse
In case this has anything to do with ADB version, I'm using Debian and my adb version is 1:7.0.0+r1-4
If you need any more info, please ask.
Thanks in advance.
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
max_157 said:
Ok, an update.
I now tried installing the ROM through TWRP's own installing option, but TWRP crashes and reboots a couple of seconds after the install is initiated.
Click to expand...
Click to collapse
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
ieatgravity said:
Make sure you have MTP turned off. Also DM verity and force encryption needs to be disabled
Click to expand...
Click to collapse
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
I figured it out. I disabled MTP from the mount menu and disabled DM-Verify and encryption from the Advanced menu... same results
max_157 said:
How do I disable MTP? I can't get android to boot. Can you disable it from TWRP or is it done from a fastboot/adb command?
Click to expand...
Click to collapse
Flash supersu then flash the ROM
ieatgravity said:
Flash supersu then flash the ROM
Click to expand...
Click to collapse
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
max_157 said:
OK. I tried
1. Booting into TWRP
2. Selected Install
3. Selected UPDATE-SuperSU-v2.65-20151226141550.zip
It crashed after a couple of seconds.
Tried with MTP disabled and DM-verity and encryption disabled.
Click to expand...
Click to collapse
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Where do you have the files located at? Is it on the SDcard or on the flash drive?
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
ieatgravity said:
I'm would assume the bootloader was unlocked? Are you able to make a nandroid backup? And have you tried flashing twrp to the phone ?
Click to expand...
Click to collapse
The bootloader was indeed unlocked.
I haven't tried flashing TWRP to the phone. Would this make it work? I'm kind of scared of having a recovery image that crashes whenever I try stuff. Can I restore the stock recovery in case anything happens?
AlienTeck said:
Where do you have the files located at? Is it on the SDcard or on the flash
drive?
Click to expand...
Click to collapse
Internal flash drive.
AlienTeck said:
does this work?
fastboot oem unlock
or
fastboot flashing unlock
Click to expand...
Click to collapse
Yup! It works. It says it's already unlocked.
AlienTeck said:
Should also erase/wipe everything except system/recovery/boot...
Also hope you made a nandroid backup first with the fastboot boot recovery.img, then booting into TWRP and backup. to flash drive. Need MTP disabled for some to not reboot.
Click to expand...
Click to collapse
I did wipe cache and everything else, and had MTP disabled.
AlienTeck said:
Also try with the new TWRP where the reboot has been fixed.. and which version 16/2 or 64/4 BLU X2 or mini?
Click to expand...
Click to collapse
64/4 BLU X2 version.
I can't find BLU Life One X2 on the official TWRP website, the only version I tried was on blox2.com, which I think is a modified version of 3.0.2-0.
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
QFIL
I got the QFIL rom from blox2.com
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
AlienTeck said:
When you say fixed, do you mean TWRP is now working? Or that you were able to flash the stock back? Did you already take the BLOX2 OTA update?
Trying to figure out if the update had anything to do with this default rebooting on /system being made writable.. Also did you make a nandroid backup?
QFIL is now on 1.0.0.3
Click to expand...
Click to collapse
I was able to flash the stock back, but via QFIL, not TWRP. The rebooting issue still persists.
I didn't make a nandroip backup, will get to it now.
Oh, I'm actually now trying to fix the rebooting issue. I think it might be a write protection, like the one HTC has. Example: https://www.youtube.com/watch?v=KV3YaMBnEYI
I really really need to be able to modify the system partition because the phone comes with a lot of crawpare and even some malware (https://www.cyberscoop.com/android-malware-china-huawei-zte-kryptowire-blu-products/)
FotaProvider installs some apps without your consent like Uber and some games and supposedly sends some info, too.
When I try to remove it with root uninstallers, the phone reboots. I though I had gotten rid of this issue by reflashing the ROM but apparently not...
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
AlienTeck said:
I only flashed TWRP to cache and booted to it and flashed super SU, then used root essentials to remove some of the bloatware. But noticed supersu was gone now. It was able to remove or disable some of the stuff without rebooting and then later manually rebooting it. I disabled the apps and then removed it, so I think even the update now has the stuff but still disabled. The update also supposedly removes one of the apps that sent data back.
It rebooted at first until I saw that I had to disable MTP in TWRP options. I have not tried the recent TWRP, I was still using the one under development in the beginning.
Click to expand...
Click to collapse
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
max_157 said:
How do I install this update?
Also, I tried removing some system apps with Root Essentials but it still rebooted.
Click to expand...
Click to collapse
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
ieatgravity said:
For the time being you need to boot into TWRP and manually remove apps using ADB. We are currently working on patching the kernel to allow /system to be mounted RW sAo that you can use apps to remove system apps. In the mean time use Blox2core as it has been fully debloated.
Click to expand...
Click to collapse
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
max_157 said:
Sounds great! Looking forward to it.
I can't install Blox2core since TWRP reboots when I try to install it or even wipe the /system partition though. Some people mentioned TWRP 3.0.3 fixed this issue.
Click to expand...
Click to collapse
We have a new tool that you can use to flash TWRP and root. All auto matic. Give it a try and let me know if it works for you.
[TOOL]Draco’s Blox2Autoroot - http://wp.me/p8gYUZ-5x
Afterwards you'll be able to flash Blox2core
Also I was unaware of this TWRP 3.0.3 for the blox2. The only one that has been ported has been 3.0.2 last I checked.
I would say disable MTP in TWRP options and developer options as well. dirst disabled it in developer options before I found out that did not stop the kernel rebooting the phone when /system became writable. I had not installed the oct update BLU sent out and maybe that makes a difference? Although the QFIL should also have the original boot/kernal image? so not sure what is going on..
If that dont stop it we need a new kernal.. I think I have the original kernal/boot saved. If anyone wants to see if that fixed the reboot.
twrp gave a MD5 of it..
152479bd51790d374885cc1a847e4c31 boot.emmc.win
Seems I need a faster course in android.. A few months ago I thought an android was some guy in dr who.
---------- Post added at 12:08 PM ---------- Previous post was at 11:46 AM ----------
The OTA update showed up one day and it installed it.. For the longest time I ignored it but I suppose someone hit ok on it.. But SuperSU seemed to have vanished before that I think. Spending time on 2 other problem phones so this one is not a priority since it works very well comparatively. I love it though it is heavy as a brick. Even my N5x case fits with a little coaxing. Although the DPI setting is set much higher like for a HD screen and not FHD. Maybe we can change it in build.prop to fix it. The N5x has much smaller icons and letters and actually fit 5 icons to a row although they both have the same density screen.. BLU has much better touch though and is far brighter and richer.
---------- Post added at 12:30 PM ---------- Previous post was at 12:08 PM ----------
The 2 boot images ARE different.. But you should first try to write a backup back to itself and see if there are problems and guess I dont have the previlage of attaching files just yet on here.
max_157 said:
Problem fixed!
I flashed the stock firmware using QFIL 1.0.2. Thanks so much to everyone who helped!
I got the QFIL rom from blox2.com
Click to expand...
Click to collapse
Could you share the link to the stock ROM you used with QFIL?
Thanks!
Hey folks. I've installed lineage OS 15.0 following with GApps ARM 8.0 and ran into an issue of infinitelly flashing file 1 of 1.
These are the last logs I get:
...
- Installing speech
- Miscellaneous tasks
- Copying Log To /external_sd
- Installation complete!
Click to expand...
Click to collapse
Check how it looks here: imgur.com/a/3UVVWKf
And that's it... Nothing happens after that. It just says "Flashing file 1 of 1" with an ongoing loading screen. Running for about 2 hours now.
Is there any way to cancel the flashing task or reboot the twrp? Any help would highly appreciated.
PotatoOrgyLt said:
Hey folks. I've installed lineage OS 15.0 following with GApps ARM 8.0 and ran
...
twrp? Any help would highly appreciated.
Click to expand...
Click to collapse
Your TWRP version's is super old , you should update it .
But exit this situation is a problem , it seem that the only solution is a forced reboot to bootloader (by pressing vol down + power button until the phone restarts in bootloader mode) .
I'm not sure at all of this solution , so I can't be responsible for what will happen to your phone.
Then reflash LOS ( if it worked the first time , it may work 2nd time ) with the SU Add-on to root your device .
Then , boot your device , download the TWRP companion app , and download the right and up to date recovery image for your device.
Since your rooted your device , you'll be able to flash the recovery image via the TWRP app .
Flash the recovery and with the app and reboot to recovery.
Finally flash your GApps .
Keep at mind that TWPR (your custom recovery) is the most important thing of your phone , that's what allows you to recover your phone even in critical situation .
So please , until now , keep it up to date
Good luck
RaiZProduction said:
Your TWRP version's is super old , you should update it .
But exit this situation is a problem , it seem that the only solution is a forced reboot to bootloader (by pressing vol down + power button until the phone restarts in bootloader mode) .
I'm not sure at all of this solution , so I can't be responsible for what will happen to your phone.
Then reflash LOS ( if it worked the first time , it may work 2nd time ) with the SU Add-on to root your device .
Then , boot your device , download the TWRP companion app , and download the right and up to date recovery image for your device.
Since your rooted your device , you'll be able to flash the recovery image via the TWRP app .
Flash the recovery and with the app and reboot to recovery.
Finally flash your GApps .
Keep at mind that TWPR (your custom recovery) is the most important thing of your phone , that's what allows you to recover your phone even in critical situation .
So please , until now , keep it up to date
Good luck
Click to expand...
Click to collapse
Hey RaiZ,
Thanks so much for looking into this!
Pressing vol down + power button solved the issue and the OS started perfectly fine. I've updated TWRP as well just like you mentioned, however, I'm having trouble getting the device rooted. I've downloaded the latest SU Add-on from this page: download.lineageos.org/extras and installed LOS with the addon. It did not work.
Then I've decided to switch to Ressurection OS 8.1 which comes with Magisk root inbuilt, yet that did not work either. Access to root was only showing root access for ADB which did not work ("adb shell su" command outputed "su: not found")
Lastly, I've installed latest version of SU-addon for RR OS. Now I'm getting root access options for apps and ADB, but selecting "Manage root access" outputs no applications for root access, "root checker" app still cannot verify root and adb shell su command returns "Permission denied".
Do you have any suggestions what might be wrong?
PotatoOrgyLt said:
Hey RaiZ,
Thanks so much for looking into this!
Pressing vol down + power button solved the issue
...
Do you have any suggestions what might be wrong?
Click to expand...
Click to collapse
Personally , I don't really know a lot about Resurrection Remix , but assuming that it work the same as LOS , you should go to the developer option and see what you got.
If you still got op only 2 option after flashing the add-on , I will advice you to flash Magisk on your device to root it
RaiZProduction said:
Personally , I don't really know a lot about Resurrection Remix , but assuming that it work the same as LOS , you should go to the developer option and see what you got.
If you still got op only 2 option after flashing the add-on , I will advice you to flash Magisk on your device to root it
Click to expand...
Click to collapse
Appreciate your guidance trough this! Flashing Magisk did the trick.
PotatoOrgyLt said:
Appreciate your guidance trough this! Flashing Magisk did the trick.
Click to expand...
Click to collapse
You're welcome ?
wrong thread
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
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
>>> *** UPDATED (see 5. ) *** <<<
Installation guide: (pay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
Code:
fastboot boot twrp-3.4.0-0-evert.img
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
!!! 5. Disable HAB verification by flashing this .zip hab_disabler.zip !!! (*)
6. Flash the TWRP installer.zip
7. Install Magisk (optional)
8. Reboot to system and enjoy!
(*) HAB (High Assurance Boot) is a second verification process/service. It checks /system and /oem partition. The hab_disabler.zip will delete/patch the related files. (for further information see "update-binary")
During first boot...
...your device will reboot once. Don't panic, that's quite normal!
...animation after "Hello Moto" will take 2-3 min.
*** tested on PPWS29.116-20-23
WoKoschekk said:
How to fix stuck on splash screen when TWRP 3.4.0-0 is installed permanently
I've tried several ways myself to get it up and running. As long as the device is encrypted, TWRP cannot start. It gets stuck in an infinite loop. The keymaster-3-0 service starts, but it is stopped immediately. It continues like this in a never ending loop. The only solution is to fully decrypt the device. At least this worked for me.
THE FOLLOWING STEPS WILL DELETE ALL YOUR DATA! IT IS NOT POSSIBLE TO CREATE A BACKUP OF YOUR ENCRYPTED DATA IN TWRP AND RESTORE IT ON A DECRYPTED PARTITION! USE TITANIUM BACKUP OR SIMILAR SOLUTIONS! YOUR DEVICE WILL BE RESET TO FACTORY SETTINGS!!
Installation guidepay attention to keep this order!!)
1. Backup your data!!
2. Boot TWRP via fastboot:
3. Format data to remove encryption. Wipe > Format Data > type 'yes' and swipe to confirm.
4. Flash the Disable_Dm-Verity_ForceEncrypt.zip
5. Flash the TWRP installer.zip
6. Install Magisk (optional)
7. Reboot to system and enjoy!
During first boot your device will reboot once. Don't panic, that's quite normal!
Edit: Tested on build PPWS29.116-20-23
Click to expand...
Click to collapse
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
I tried it on my own. First boot runs fine but the second one ends in a bootloop. I already know whats wrong. Give me a few hours to fix this.
Dk Gautam said:
I follow your process to install TWRP Recovery,
Install successfully working fine,
But when I restart the moto g6 plus
It's everytime stuck on moto boot logo and restart again then stuck on boot logo
After that I restore boot.img using TWRP then flash magisk Manager working fine when I restart the phone agian stuck on boot logo.
(TWRP working fine thanks for your method or work but afterthat I flash magisk Manager first time everything working fine properly but when restart the device every time stuck on moto boot logo, I have to do process again)
I want sell my phone , Mood Off.
Click to expand...
Click to collapse
The problem has been fixed!!
I rebooted several times from system to recovery and vice versa. Magisk and TWRP (installed permanently) work fine. No issues known yet.
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
It works fine fir me. I enabled Magisk Hide to hide some apps but my device doesn't loop after that.
Did you use the updated method?
- Magisk was repacked with new name
- Magisk Hide enabled
- modules installed
- rebooted to recovery and then to system => no looping
- rebooted the device normally => no looping
At this moment I'm using my G6+
Dk Gautam said:
Everything working fine, after flashed permanently TWRP,
Magisk Manager also work fine the main issue here
If we flash magisk Manager using TWRP
You can restart the device several time working fine.
If we open magisk Manager and enable magisk hide for apps , then restart the device stuck on boot logo..
If we flash magisk Manager and don't open magisk Manager it will be working fine no issue , if we open magisk Manager then close after we restart the device stuck on boot logo.
If you find any solution about this then good. Otherwise please don't spent valueable time on it,
This devices create more problems only
Moto G6 Plus
Thanks for work.
Click to expand...
Click to collapse
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
WoKoschekk said:
I don't know why you are having this problem...
Flashed the Stock ROM, followed my guide and enabled Magisk Hide.
But no issues with that.
Click to expand...
Click to collapse
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Dk Gautam said:
The Problem has been fix,
I skip the 5th process, HAB disabler,
I flashed stock rom latest build security patch, PPWS29.116.16.24.
1. Format data using TWRP with Temporary boot.
2. Flash DM Verity Disable.
3. Flash HAB Disabler
4. Flash TWRP 3.4.0.0.zip
5. Re-start tha device.
6. Install magisk manager using TWRP.
7. Everything is working Fine.
8. I have a one question...
Lineage os 17.1 latest build for evert
Can support VoLTE ?????
I flashed Lineage os 17.1 on my moto g6 Plus
Everything is awesome but VoLTE not Show
Then I removed Lineage OS.
Click to expand...
Click to collapse
Great!! Thanks for your reply!
I'm using neither Lineage nor VoLTE so I don't know if it's supported.
hello OP
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
d_g_m_2000 said:
hello.
it stuck on downloading 'boot.img'
does anyone have some tip so i can flash twrp?
thanks in advance for your comments.
Click to expand...
Click to collapse
Are you trying to boot TWRP?
WoKoschekk said:
Are you trying to boot TWRP?
Click to expand...
Click to collapse
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
ok, ia my pc, i try in another and it boot up... i got ryzen 5 2600 just if anyone else find out what da f*ck is going on... thanks in advance for your comments.
d_g_m_2000 said:
thanks for your help.
yes, the command that i use is
fastboot boot twrp.img
i tried with another usb cable, another usb port.... even when i try "fastboot oem device-info" it does not show results yet "fastboot devices" it works.
i try another platform tools, even installed qualcom drivers.. but still it wont boot up to twrp 3.4-0-0
sometimes even it say command failed unknown
i cant even flash stock firmware... it just say fail to all commands
blankflash bat does not work also, it stuck on <waiting device>
i try on usb 3.0 and 2.0 and still the same results.
my device is xt1296-6
Click to expand...
Click to collapse
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
WoKoschekk said:
Have a look at this thread, especially post #4.
https://forum.xda-developers.com/g7-play/help/unlock-bootloader-t4164019
Click to expand...
Click to collapse
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
d_g_m_2000 said:
sorry for spamming your thread, i just want to make clear that my pc is the culprit of my problems.
i try this tutorial in other pc and it got it nice and esay.
i use it to flash lineage 17 official, that i'm now surprised that it replace twrp with their own recovery :/
anyway.. thank in advance for all your help and... people, this tutorial works great!!
Click to expand...
Click to collapse
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
WoKoschekk said:
Since recovery is inside the boot partition Lineage implements a own recovery for their boot.img
Glad to hear that! Thanks a lot!!
Click to expand...
Click to collapse
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
d_g_m_2000 said:
hi OP.
now i'm on pixel experience and they also remove twrp and install their own recovery... is this new normal? or i'm doing something wrong installing twrp.
thanks in advance for your comments.
Click to expand...
Click to collapse
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
WoKoschekk said:
Yes, it's normal. I don't know why they do that... The only useful function there is ADB and that's all.
But you can replace them with TWRP, that's absolutely no problem. Reboot into bootloader and boot your twrp.img to install it.
Click to expand...
Click to collapse
that's is a real bummer... thank you for your comments!
Hi i install pixel experence rom and im having a problem i canflash anything from my device, storage dont shows corrrct size and, shows binders with aleaty names with nothing inside, and i can't transfer with USB