Database Info

Xoom bricked

Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.

Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.

If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.

Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?

Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.

Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?

eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App

sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.

[SOLVED]Unlockbootloader{fixered}

I have an issue with my oneplusone, I cannot unlock it any more. I tried various ways via fastboot, even tried to fastboot a temporary recovery. It keeps saying locked and rebooting into simple recovery. Before it enters simple recovery, or now cyanogemod recovery non latest cm11 nightlies it shows a red exclamation mark.
cm11 updates are flashable via the cyanogenmod recovery. Other zips are not as they are not properly signed. There seems to be no way I can put the unlock byte to true.
fastboot flashing the factory image also doesnt work, it keps saying locked. So I cannot flash the unlock/tamper zip anymore.
This started when on latest nightlies, when simple recovery went to cyanogenmod recovery. The update cyanogenmod recovery switch in development apperently doesnt always stick. I think something went wrong there.
rolling back to m8 with simple recovery did not work either
anyone have any ideas?

bachera said:
I have an issue with my oneplusone, I cannot unlock it any more. I tried various ways via fastboot, even tried to fastboot a temporary recovery. It keeps saying locked and rebooting into simple recovery. Before it enters simple recovery, or now cyanogemod recovery non latest cm11 nightlies it shows a red exclamation mark.
cm11 updates are flashable via the cyanogenmod recovery. Other zips are not as they are not properly signed. There seems to be no way I can put the unlock byte to true.
fastboot flashing the factory image also doesnt work, it keps saying locked. So I cannot flash the unlock/tamper zip anymore.
This started when on latest nightlies, when simple recovery went to cyanogenmod recovery. The update cyanogenmod recovery switch in development apperently doesnt always stick. I think something went wrong there.
rolling back to m8 with simple recovery did not work either
anyone have any ideas?
Click to expand...
Click to collapse
did you have it unchecked in settings to not update recovery. Also are you saying that putting your phone into recovery and flashing tamper zip does not work

playya said:
did you have it unchecked in settings to not update recovery. Also are you saying that putting your phone into recovery and flashing tamper zip does not work
Click to expand...
Click to collapse
I had it unchecked in settings to not update recovery when I was trying all this.
the cyanogenmod recovery does not flash unsignes stuff. this is the same recovery as people call simple recovery. In latest nightlies its included. I had checked the update recovery when flashing nightlies of cm11.

bachera said:
I had it unchecked in settings to not update recovery when I was trying all this.
the cyanogenmod recovery does not flash unsignes stuff. this is the same recovery as people call simple recovery. In latest nightlies its included. I had checked the update recovery when flashing nightlies of cm11.
Click to expand...
Click to collapse
ok sorry I rooted and flashed TWRP right out the box and dont play around with that other stuff. I am assuming also that you have tried to fastboot TWRP to flash the zip and it just loops back? there was another user with similar issues I will see what happened with him. But unfortunately I have not seen or heard of any fix other than booting into temporary recovery and flashing zip. You are saying you can not flash anything.

playya said:
ok sorry I rooted and flashed TWRP right out the box and dont play around with that other stuff. I am assuming also that you have tried to fastboot TWRP to flash the zip and it just loops back?
Click to expand...
Click to collapse
fastbooting twrp or any other recovery just puts me into cyanogenmod recovery, sadly.

bachera said:
fastbooting twrp or any other recovery just puts me into cyanogenmod recovery, sadly.
Click to expand...
Click to collapse
If cyanogenmod can only flash signed zips have you tried to sign the tamper zip. I am not familiar with CM recovery on nightlies so I apologize for that

playya said:
If cyanogenmod can only flash signed zips have you tried to sign the tamper zip. I am not familiar with CM recovery on nightlies so I apologize for that
Click to expand...
Click to collapse
no problem, I dont know how to sign lol sorry

bachera said:
no problem, I dont know how to sign lol sorry
Click to expand...
Click to collapse
come on man just google it... you must be new to xda there are programs that will sign zips for you...
---------- Post added at 08:40 AM ---------- Previous post was at 08:38 AM ----------
playya said:
come on man just google it... you must be new to xda there are programs that will sign zips for you...
Click to expand...
Click to collapse
Not saying it will work like you want but you can sign a zip file..

playya said:
come on man just google it... you must be new to xda there are programs that will sign zips for you...
---------- Post added at 08:40 AM ---------- Previous post was at 08:38 AM ----------
Not saying it will work like you want but you can sign a zip file..
Click to expand...
Click to collapse
thats not working, can you sign it for me>?

bachera said:
thats not working, can you sign it for me>?
Click to expand...
Click to collapse
whats not working?

playya said:
whats not working?
Click to expand...
Click to collapse
I dont know how to sign it, and random method of sigining does nothing.
can you sign it for me

signed zip also doesnt work

I am having this same issue, I was having the audiofx has stopped issue that rendered my phone useless, tried reflashing stock images, still didnt get rid of it so i tried to lock and re unlock my bootloader and now everytime i put fastboot oem unlock just boots me into twrp.... if i cant unlock the bootloader cant flash anything....im stuck

joshyy_rey said:
I am having this same issue, I was having the audiofx has stopped issue that rendered my phone useless, tried reflashing stock images, still didnt get rid of it so i tried to lock and re unlock my bootloader and now everytime i put fastboot oem unlock just boots me into twrp.... if i cant unlock the bootloader cant flash anything....im stuck
Click to expand...
Click to collapse
I have a victory.
Now I tried twrp from playstore. didnt work.
Tried flashify from playstore, with the original recovery I was on before things went amuck. It said flash succesful like twrp, didnt trust it. However I tried flashing the zip from the temper/unlock thread. Lo and behold upon reboot a custom recovery screen was shown, flashing a zipfile. Victory!
So even when fastboot was locked status, fastboot didnt succesfully flash anything, booting on temp recovery also failed, flashify fixed it. Lucky me. Guess you can add that to the list

this can be locked

How to uninstall twrp?

It's an lg g3 on lollipop. Basically I want to remove all root and custom recovery from my phone.By I don t want to lose all settings and data and hours of configuring the phone the way I like it. So don't tell me how to flash stock Rom back on phone. I know that. I want to remove twrp without messing anything up on phone. Is this possible.

Are you not able to reflash a stock bootloader. You can then unroot by using SuperSU in its settings page.
Hope this helps a little.

Agent_Sm1th said:
Are you not able to reflash a stock bootloader. You can then unroot by using SuperSU in its settings page.
Hope this helps a little.
Click to expand...
Click to collapse
Does reflashing the boot loader reset and erase phone? If not how do I do it in detail please. I already unrooted super su. But still stuck with twrp.

Flashing a recovery doesn't wipe the phone. Just like if you flash cwm over twrp for example, your phone wouldn't wipe it'd just boot to cwm recovery instead of twrp. You'll need to search for your phones stock one.

On the Galaxy Note 4 I would flash a PDA file with the bootloader CSC etc that's all Stock. It would be a tar file and I would flash this using Odin. I believe this is only on Samsung though. Not sure how it is done for LG but I can imagine it's similar. You could attempt to flash everything stock using your computer I believe but I am not sure as this only applies to Samsung devices. But you get the idea, perhaps a Google search can further help you though! Hope this helped √
Sent from my SM-N910T using Tapatalk

Agent_Sm1th said:
Flashing a recovery doesn't wipe the phone. Just like if you flash cwm over twrp for example, your phone wouldn't wipe it'd just boot to cwm recovery instead of twrp. You'll need to search for your phones stock one.
Click to expand...
Click to collapse
I can't seem to find it. Could use some help. My phone is lg g3 d850 att. Running 5.0.1
I need the stock recovery to flash using flashify

AndrewG1299 said:
I can't seem to find it. Could use some help. My phone is lg g3 d850 att. Running 5.0.1
I need the stock recovery to flash using flashify
Click to expand...
Click to collapse
I'll have a look, but can't promise anything as I use an S4. I flash stock recovery via Odin on the PC or custom via cwm or twrp.
---------- Post added at 06:35 PM ---------- Previous post was at 06:29 PM ----------
I can only find stock firmware. Unfortunately this will wipe your phone if you flash it.
Is there no one who can advise you in the lg parts of these forums.
Here's the link to the stock firmware. Careful you pick the right one.
http://lgg3root.com/lg-g3-stock-factory-firmware/

I know about that but I need the recovery so I don't erase phone

Yeah I know it'll wipe it. Just thought in case you decided to fresh install. It doesn't take that long really to set back up even if you do go down that route.

[N_7.0][NPJ25.93-14][TWRP][Boot]TWRP Backup of Stock Boot Partition

DISCLAIMER: I AM NOT LIABLE TO ANY DAMAGE THAT HAPPENS TO YOUR DEVICE BECAUSE OF DOING ANYTHING WRONG.
MOTO G4 PLUS [XT1643]
This is for those who had flashed a custom kernel on their stock ROM and now want to revert to stock.
REQUIREMENTS:
1. TWRP 3.0.3-n2 by @Shreps .
https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
This one is more updated/maintained than the official 3.0.2 version.
2. 7Zip Compression Utility:
Download and install on your PC. I use this as it gives the maximum ultra level compression. See Downloads below.
PROCEDURE:
1. Download and extract the TWRP.7z using 7Zip.
2. Place the TWRP folder it in the root directory of your INTERNAL STORAGE.
2. Just reboot TWRP once and choose Restore and then choose this: athene_93-14_boot
3. Swipe to restore.
NOTE: As a general recommendation for all zip installations and backup/restore using twrp, Wipe Cache and ART Cache before you Reboot to System.
4. You're DONE
DOWNLOADS:
Google Drive Link for the file:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
7-ZIP Download Link:
http://www.7-zip.org/download.html
IF YOU WANT ENTIRE STOCK ROM ( TWRP BACKUP) VISIT THIS THREAD BY @Greekgodmerwyn .
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-moto-g4-plus-npj25-93-14-t3544601
HIT LIKE IF I HELPED YOU! :fingers-crossed: :good:

Hey I need the file bit it is in bin so give a alternative link

Can i install this to xt1644 retus?

Dont know bro I just want the 1643 one

dedik46 said:
Can i install this to xt1644 retus?
Click to expand...
Click to collapse
Not tried. Make additional backups and try. :good:

https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
Not Found
Error 404
Please re-upload.

nextheart said:
https://drive.google.com/open?id=0B25DpDahxm52MDlBRlVqNElkaUE
Not Found
Error 404
Please re-upload.
Click to expand...
Click to collapse
Oh wait. Try this, @nextheart
https://www.androidfilehost.com/?fid=745425885120722570

@tywinlannister7 Thanks for quick reply.
As far as I can understand, this file should be flashed (restored) after restoring my TWRP back up of nougat stock rom taken in January-2017. Currently I am on RR-MM.
Shall I able to take OTA then?

nextheart said:
@tywinlannister7 Thanks for quick reply.
As far as I can understand, this file should be flashed (restored) after restoring my TWRP back up of nougat stock rom taken in January-2017. Currently I am on RR-MM.
Shall I able to take OTA then?
Click to expand...
Click to collapse
For OTA updates to work, you'd need a stock recovery on your device too; TWRP is a no go. Once you've restored your TWRP backup of your Nougat stock ROM (which hopefully may have the stock boot still), you can flash the stock recovery linked here https://forum.xda-developers.com/moto-g4-plus/how-to/how-to-ota-rooting-nougat-npj-25-93-14-t3601747
I imagine the easiest option is to flash the recovery in fastboot (same as you did with TWRP) using 'fastboot flash recovery recovery.img', then rebooting into recovery.
I think, though I've not tried it with a stock recovery, that you should be able to flash the recovery image in TWRP:
tap Install in the TWRP menu
Select 'install image's
Find your stock recovery image and select
Choose recovery as the image type
Flash and reboot to recovery.
Then, provided your system has a stock kernel, no modifications to your system and a stock recovery (bootloader doesn't matter), you should be able to update via OTA.

@echo92 Thanks for detailed guide.
I had flashed SuperSU on Nougat stock ROM, so stock boot might be affected. Am I right?
In short, I want to sell the device, so I want to return to stock.

nextheart said:
@echo92 Thanks for detailed guide.
I had flashed SuperSU on Nougat stock ROM, so stock boot might be affected. Am I right?
In short, I want to sell the device, so I want to return to stock.
Click to expand...
Click to collapse
You could have directly flashed the latest March 1 Security firmware via fastboot and lock your bootloader too.

tywinlannister7 said:
You could have directly flashed the latest March 1 Security firmware via fastboot and lock your bootloader too.
Click to expand...
Click to collapse
Thank you for pointing out.
Will I lose my IMEI or WIFI MAK or any thing else by fastboot method? Because I have read that some users are losing such things by fastboot method.

nextheart said:
Thank you for pointing out.
Will I lose my IMEI or WIFI MAK or any thing else by fastboot method? Because I have read that some users are losing such things by fastboot method.
Click to expand...
Click to collapse
Shouldn't create any such issues. Anyways, you can make an entire backup of the fsg and other partitions in twrp.
Yes, your data will be wiped though.

Unresponsive touch screen in TWRP - how can install a ROM?

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.