Related
it's a pretty long story but currently my system partition is wiped after it soft bricked, i also couldn't reflash stock roms with twrp so i tried to extract the recovery.img from the stock rom and flashing it over twrp to get the original recovery mode back to flash the update but for some reason it didn't work.
so now i can only boot into EMUI which keeps telling 'getting package info failed' meaning i can't update through it. i'm also able to reach the 'fastboot&rescue mode' screen but i know nothing about adb and even tho i watched 2-3 tutorial videos i couldn't really get it to work. all videos wanted me to boot up the phone and enable usb debugging which i can't. my phone was rooted before and i'm positive i've enabled it in the past but i'm not sure if it's still enabled or not, either way i'm not able to get it working.
is this salvageable?
i'd really appreciate some help if possible, thnx
nope. but even when i had twrp it wouldnt let me flash update.zip's
i still have fastboot screen so my guess is that i have to run it through adb, which i don't know how to do
Rommco05 said:
Hm, and which is your model and last function system?
edit: u can boot to system? If good understand u can
Click to expand...
Click to collapse
last update i had working was frd-l09c432b120
can't boot system
can't boot recovery mode (twrp)
i CAN boot to 'fastboot&recovery mode'
i CAN boot to EMUI (but EMUI keeps telling me 'Getting package info failed', it tries to connect and download but from what i can tell on the screen the download never starts)
Ok. Ive tried running 'adb devices' but i cant see my device, if i type 'fastboot devices' i find one device.
Dont know if im missing something or if this even matters.
But i'll try flashing twrp with fastboot
Rommco05 said:
This is right way
edit: frp is unlocked?
edit1: you need to flash old twrp 3.0.2.0 I think is right (if was your last firmware Marshmallow
Click to expand...
Click to collapse
TWRP is back!!
but how do i flash marshmallow with twrp? and what marshmallow file are you talking about, the one i mentioned above?
because i tried flashing these update.zip's with twrp before but it wouldn't let me.
i'm currently packaging the update.app files into a zip and moving it to the sdcard, that's the only way i can think of to flash these update files with twrp.
since it didn't work last time, i have my doubts but i'll give it a try
Rommco05 said:
Ok, just for clarification, your model is frd-l09c432, right?
Click to expand...
Click to collapse
yes. can't remember how to double check but way back when i downloaded these update files i was extremely careful to download the correct files.
and they worked and been working since they were the newest version, so i guess that has to be my model.
EDIT: and it's twrp-3.1.1-0
yea now it told me corrupt zip, last time i tried i got some other error, think it was some error about writing to system partition.
U can also flash this https://drive.google.com/file/d/0BwXB-CJiljwpS1o4UXo5b1JlRjQ/view and after
Dload this link once http://www.hihonor.com/uk/support/details/index.html?DOC_ID=92101
Rommco05 said:
Ok download this firmware B120 and flash via twrp https://www.androidfilehost.com/?w=files&flid=129477 after this go to reboot and tap reboot recovery. Now you should be in stock recovery and tap factory reset and after reboot. Now you hopefully will be able boot to ROM. (If u got some errors in twrp, don't care, installation must take about with minutes)
Click to expand...
Click to collapse
there's no B120 on that site, only B101 and B131. should i take B131 instead?
Any updates for your issue OP?
Sent from my Honor 8 using XDA Labs
Rommco05 said:
Sorry so flash B131 is better then B120
Click to expand...
Click to collapse
it's up and running again thank you so much, you're a life saver. i'd actually kiss you if you were here lol
i spent a few hours yesterday trying to find zipped update files ready for flashing in twrp, like the ones you linked.
do i have to do a factory reset after that? i haven't tried everything yet but my phone looks and works as if it never even stopped working in the first place.
i'm just happy i got all my files, numbers, photos etc back...
thank you so much once again
EDIT: yea sorry for the delayed response, i had to run an errand
Wow another one rommoco05 :highfive:
Add the fixed tag to the thread OP. Enjoy the device
You both are awesome ???
Rommco05 said:
lol. No u don't need to make factory reset, phone start from like factory reset. Upgrade to Nougat . If u want kiss me, kiss thanks button you're welcome
Click to expand...
Click to collapse
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
JimZiii said:
i'm trying to backup everything i need before doing a factory reset and i have a problem.
first time booting up i get the contact names on call logs for a few seconds and then they disappear because the contacts are gone. if i restore my data partition in twrp and boot up the system again i get the exact same thing. i'm guessing the contacts are saved at least temporarily somewhere on the data partition, is it possible to extract them somehow? i don't care if i have to write them down one by one from a .log, i got some important numbers that are worth the hassle for me
Click to expand...
Click to collapse
If you synced the contacts already then you can from google contacts.
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
JimZiii said:
I know this is completely backwards, but i found a twrp backup i did on my broken systems partition before i tried anything else. Maybe if i can undo what soft-bricked my phone i can get them back.
I installed/flashed a magisk module for xposed and after that i wasnt able to boot the system any longer. Is it possible to somehow uninstall this module and get the phone to boot again? Or is the only solution to flash a new stock rom?
Edit: havent synced with google in a while
Click to expand...
Click to collapse
Flash the backup of boot files
venugopalu007 said:
Flash the backup of boot files
Click to expand...
Click to collapse
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
JimZiii said:
the backup of the boot partition made no difference. even after flashing the new rom and the boot after nothing changed.
but i just solved it, i found a magisk uninstaller and after flashing that the phone booted up with all contacts, photos, apps+data intact.
when i first posted here i had wiped the systems partition and didn't know i still had a backup hidden away in a folder, so i'm extremely grateful for all your help and patience.
i still think i'm gonna update to nougat and i'm using hisuite that came with the phone, do you recommend any other backup application? do you know if app backups work if i update to nougat from marshmallow?
Click to expand...
Click to collapse
For apps backup just download from playstore , because some apps are compitable with mm and some are nougat .so better to download again from playstore after updating to nougat.
Rommco05 said:
Huawei backup is pretty good I start saving my SMS on P8lite and now I have +15000 SMS saved and 2 years old calls logs
Click to expand...
Click to collapse
That was huge bro
Rommco05 said:
Yes, resume SMS take about 15 minutes
Click to expand...
Click to collapse
Bro can you make a guide how to backup and restore in Huawei.
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
HighOnLinux said:
seems the open beta install was more bad for you than mine. Upgraded from op29 to op30 like you, but i had everything stock. No unlocked bootloader, no big customizations, etc. I just tried entering recovery mode via fastboot and it worked like normal for me, had to enter my pin to decrypt my data, and the rest like normal. I'd suggest to downgrade back to pie and reflash the open beta software to see if the issue is gone or not, but that's your call to do so.
Click to expand...
Click to collapse
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
verbatim7 said:
Hi everyone!
Issue is pretty simple to explain - after upgrading via OTA from the latest open beta Pie (29) to open beta Android 10 (30), I can't boot into recovery.
System works normally, the only thing I'm having trouble with are the generic issues discussed on the OP community forum (autorotate and other sensors, Gboard gap...). It is recommended repeatedly that one should reboot to recovery and wipe the cache partition.
The problem is that I can only get into fastboot mode - tried the advanced boot menu, adb/fastboot and selecting recovery mode while in the fastboot mode but it always goes into fastboot.
TWRP doesn't support android 10 yet as far as I know and I've found no other reference of this issue anywhere else. Only thing that comes to mind is to wait for the next open beta and hope it will be resolved after another OTA.
Thanks for your help!
Click to expand...
Click to collapse
Had read somewhere that flashing stock boot.img will help restore stock recovery.. Have you tried doing that
brashmadcap said:
I think you stumbled across the answer everyone has been searching for. How did you upgrade? Did you download the whole zip and flash through updated?
This kinda makes sense. Do you remember how big the update file was? It could have been an incremental rather than a full if you weren't unlocked and thus (maybe) didn't change fastboot.
Click to expand...
Click to collapse
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me.
Edit: this part down was meant for OP, sorry for confusion
so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
HighOnLinux said:
i grabbed the update file from this news article from xda itself: https://www.xda-developers.com/oneplus-android-10-oxygenos-beta-oneplus-6-6t/
the update zip was the full update and not incremental. i updated my device using the local device upgrader found under the system update settings to do the job for me. so far when i updated last night, the auto rotate was tripping, until you mentioned that wiping the cache should do the trick (and it did do the trick thanks for that).
But back to your problem, you should try flashing the file under the link i put into this reply and if it doesn't work, just back up your data, downgrade back to pie, and flash the full update file that is present within that article and you should be back to normal
Click to expand...
Click to collapse
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Use an older version of magisk and you won't lose twrp
verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
how did u get back the recovery?
LazerH said:
how did u get back the recovery?
Click to expand...
Click to collapse
As stated above - just downloaded the OTA Android 10 update file for the right device, installed it and didn't install magisk to inactive slot and I had it back. If I tried to install magisk to keep root I didn't have the recovery mode. My guest guess is that magisk still isn't fully compatible with the new Android 10 boot changes.
verbatim7 said:
Thanks for the idea. Unfortunately, it seems that having root and having recovery isn't possible for me at this point.
I've installed the OTA, got the recovery back and managed to wipe cache and everything worked - except I didn't have root. Then I've installed the magisk boot image to get back root, but then the same issues started happening and I was unable to access recovery.
Now I have to decide what's more important :crying:
Click to expand...
Click to collapse
To me having a stable phone is much more important than a heavily modified device that's unstable at any given time. I'd say use the msm tool, flash back to a fresh build of pie, download the full open beta 30 zip, after its done flashing, reboot twice to iron out any present issues, then unlock the bootloader, and then you should be good to go. If you want root, just fastboot boot into twrp and flash the latest magisk zip and you're good to go. At the end you should have root, an unlocked bootloader, all while on the open beta android 10 build, with access to the stock recovery
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
terrorblade23 said:
Can u guys help me please, i just flashed by mistake with " fastboot flash boot" a TWRP enchilada file and now i'm stuck in fastboot and i cant boot ...i dont know how to factory reset or flash firmware from fastboot (
Click to expand...
Click to collapse
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Schnullifax said:
Had the same problem. Flash this one: https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
OOS 10 Open Beta 1 Stock Boot
Click to expand...
Click to collapse
thanks..this is what i was looking for ...the problem is that now i'm in a boot loop , the dots keep spinning 4ever...and i did factory reset it from recovery
up1: i managed to install on slot a (i guess) Twrp.. but the whole memory is empty and i cant place anything (firmware) with pc on phone
formated data from twrp (to some format ntfc4 or smth like that ) and installed back android q and is working .
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device
vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group
vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.
kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted
vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.
FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant
I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.
kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.
I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work
This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.
Just a heads up to anyone who is wondering about root for this phone - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. Obviously you need to have already unlocked the bootloader before doing any of this.
I got the stock boot.img from the firmware linked in this thread. I patched it using Magisk Manager (v8.0.7) then flashed it via fastboot. My installed Magisk version is 21.4 (21400).
-- A WORD OF CAUTION: --
As of now there is no TWRP or any other custom recovery for this phone that I am aware of, so if you mess something up due to root, your only option to fix it might be to reflash the stock firmware.
A note about mobile banking apps:
After I installed Magisk Manager, my banking app stopped working and SafetyNet check was failing. After flashing the patched boot.img and rebooting, the SafetyNet check passed but my banking app still wasn't working. I used Magisk Hide and checked off the banking app in the list, but that didn't help either. What I had to do was use the Hide Magisk Manager option where it reinstalls Magisk Manager under a different name. Now my banking app is working again.
DM.IDOL said:
... - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus model, and it worked. ...
Click to expand...
Click to collapse
It worked for me too. It was also easy for me because the only RETUS upload on the mirrors.lolinet site was my exact firmware version. Downloaded that, extracted and used that boot.img for magisk-patching.
The only issues I'm left with are:
1. Adaway isn't working (can't write to any of the canned hosts file paths) and I haven't figured out where I might be able to store a writable hosts file, and . . .
2. Titanium Backup (Pro) works to freeze almost every app that I wanted to disable. The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications. So I dunno . . . it's not a deal breaker as long as auto updating stays turned off.
Bootloader is unlocked and rooting via Magisk worked on my Stylus 2021, exactly as advertised.
Update: My solution for AdAway was here, AdAway 5.3 (newest version I believe).
Update2: Sans freezing Motorola Update Service, updates are of course frozen from actually running because of system changes by root & TWRP. So no big worries, just the nuisance of notifications.
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Mr.Morgan said:
cant the new maagisk be used as an alternative custom recovery? Something about renaming the apk to zip and then flashing zip file on recovery?
Click to expand...
Click to collapse
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
sd_shadow said:
No, Magisk is not custom recovery.
There are two ways to install Magisk, using the .zip version, with a custom recovery like TWRP or
Using the magisk app to patch a boot.img then flash with fastboot.exe
Click to expand...
Click to collapse
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Mr.Morgan said:
I appreciate the knowledge, but perhaps you can shed some light on what the app means by " Custom Recovery lovers, no worries! The Magisk app APK itself is a custom recovery flashable zip, just like MAGIC. Check out the updated installation guide for more info"
Click to expand...
Click to collapse
You are partly correct, there has been a big change with Magisk.
You can just change the Magisk.apk to Magisk.zip
But the zip does not replace a custom recovery.
It just eliminates the need for a separate manager.zip
In some custom recoveries, the installation may fail silently (it might look like success but in reality it bootloops). This is because the installer scripts cannot properly detect the correct device info or the recovery environment does not meet its expectation. If you face any issues, use the Patch Image method as it is guaranteed to work 100% of the time. Due to this reason, installing Magisk through custom recoveries on modern devices is no longer recommended. The custom recovery installation method exists purely for legacy support
Click to expand...
Click to collapse
Magisk in Recovery
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Click to expand...
Click to collapse
This does not replace the stock recovery, just patches the recovery.
I recently purchased this phone, Moto G Stylus 2021, from Amazon. When I enter the dev options menu, OEM Unlocking is greyed out. I did a bit of research and found another thread online where another two users had the same problem, for all of two days.
After two days, the option to enable OEM Unlocking was no longer greyed out for the both of them. Fascinating! I may return this phone before that time is up, but if I don't, I'll report back on any changes for sure.
EDIT: I've decided to return this phone and get a Galaxy Tab S7 instead; there's more room to draw and a better pen!
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
I can't remember exactly where I seen someone else commenting on this topic but they had lost their cellular network after rooting ,
My problem / question is that I have also my lost my cellular network connection after rooting but not completley only to the original carrier I got t this phone with witch is boost, but if I try another carrier such as tmobile or sprint or even metro it will work because they are basically all 1 company now , but how do I fix this problem to get my phone to read my sim card as valid (I get the invalid sim msg) when I put my original sim in and I just went and got a brand new replacement sim from them to see if that would solve the issue.also going off reading the forums on here I went with the mask retus firmware for flashing because there isn't one on there anywhere for so any help would be hysteria l greatly appreciated. This is my only problem I'm having since rooting everything else is working perfectly fine.
BobbyBlunt said:
Can't find my firmware on lolinet (boost mobile qpc30.q4-31-93)
Tried lenovo's rescue tool to see if I could grab the firmware that way and it just kept giving me errors.
If anyone has some how acquired the appropriate firmware would you mind sending it to me?
Click to expand...
Click to collapse
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
I tried the lenovo recovery tool again and this time it was able to find the appropriate firmware. I was able to successfully root
Hey well i just installed latest magisk and patched boot img and moved it to my pc and went thru fast boot and just did fastboot flash boot patched.img and it works fine. I dunno if latest update fixed whatever was wrong on yours but if i installed the older one it would not even let me pick the boot img to patch *shrugs* but all working on mine now...we just need full device tree etc so we can get us a a recovery def want that before i go adding mods. If it helps any I have cricket same as ATT the person who lost cell may need to redo their apn or take sim card out and reapply it hope that works.
Moondroid said:
The one exception was Motorola Update Service. TiBu toasts that it was disabled and "invisible from the app drawer", but it actually wasn't disabled and still isn't. It still shows under System Applications.
Click to expand...
Click to collapse
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Well after a few days of LTE connection my own unlock now works got root
riggin said:
just an idea but on the site that has all the firmware im thinking could submit a request to them using that telegram messenger thing for the firmware needed.....it may be kind of a longshot but just thought of that myself and the closest one i see to what you posted is the metro version
Click to expand...
Click to collapse
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
riggin said:
hey was just wondering since im kinda in the same situation you were in with not being able to obtain exact firmware need at first for boost model if maybe you can proovide tthe brief steps you made to get the lmsa tool to recognize it and pull the corerct firmware....ty so much if u can
Click to expand...
Click to collapse
Unfortunately, either LMSA determines the correct firmware or it doesn't, there isn't anything that can be done to fix it, except contacting Motorola.
For other options see
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
steppinthrax said:
Hey Guys, I'm continuing on this thread since I've gotten further. I used LMSA to download the firmware zip using the Resuce button. Afterwards I copy that zip (2+ gigs) to my download folder. I open up Magisk and select intall and select the firmware zip. I starts out successfully but then fails. I get this in the log folder.
- Device platform: arm64-v8a
- Installing: 23.0 (23000)
- Copying image to cache
- Unpacking boot image
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Unsupported/Unknown image format
! Installation failed
I even tried to resuce the phone using the firmware provided by the LMSA program which essentially wipes my phone and try again with a clean Magisk load and I'm getting the same. The only thing I'm thinking is I could be getting my Magisk from another source. I'm using version 23 from github.
Click to expand...
Click to collapse
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
sd_shadow said:
It isn't a zip file it's a folder or at least every firmware I have downloaded is automatically unzipped by LMSA.
You only need to copy the boot.img and maybe the recovery.img to the device.
Click to expand...
Click to collapse
Thanks I figured it out last night. I also figured out pretty quickly that once you root a phone certain applications will no longer function. I didn't deal with this before, but since I work from home I have to use some of those apps that create a "Work Profile". The one app "Intelligent Hub" removed itself and my work profile. When trying to re-install and authenticate with my work it literally said "Won't provision a compromised device".
Within Magsik I used the Magsik hide feature and tried selected that app and hiding all methods that it could detect root. I even then rebooted, removed/reinstall etc. Nothing worked. The app still kept detecting root. I know that the Xposed Framework modules may work in hiding root but I decided to go all the way back to normal since there's little benefit for me to root except for the ability for me to remove bloatware. This is a retail unlocked and there's little if any bloatware on the device.
I removed Magsik and any other junk, turned on OEM locking and rebooted and I'm back to mormal. Thank you everyone this was a leaning exp. I haven't rooted in like 5 years.
DM.IDOL said:
I've been having the same problem trying to disable the update prompts. Titanium Backup doesn't work, nor can I disable it via terminal using pm. The system update screen will pop up multiple times a day, interrupting whatever I'm currently doing to tell me I have an update. It's really annoying that it can't be frozen.
Click to expand...
Click to collapse
FYI, for posterity, instead of getting multiple notifs per day I just tap and let it try to update. It fails quickly and the notification is nixed for a while.