Database Info

[Q] Bricked Device? Please Help me!!!!!!!!! im LOST

hi, iam new user of TF300t, i installed the Energy.TF201.or.TF300..JB.03.18.2013.( i dont remebmer is the STOCKED or THEMED) ! after that i wanted to install BAKED_TF300T_BB-8, but the device stay on the boot menu! so what i did , installed the 6.0.2.3 CWM ( [CWM][6.0.2.3 / 5.5.0.4] Official CWM Recovery for JB/ICS + ROOT) ! after that i rebooted the device. Stock in the Asus LOGO! After i rebboted by holding the power menu and volume down, i choosed the wipe option ( i dont know why) and from tht time, it rebbots only in the 6.0.2.3 CWM what ever i do!
For 5 days, i have tried to flash via fastboot twrp.blob, i have pushed the firmware from asus to /sdcard and flashed via fastboot always, i have tried and read similaire problems! didt succed! i have always the message tht Can not mount sdcard! cant mound E/data! cant mount anythingg!! What ever i do, always reboot to this CWM !!!!!
please any one help me!!!!!!! thanks a lot!!!

You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.

sbdags said:
You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.
Click to expand...
Click to collapse
but i can use adb commands, and fastboot commande ( except tht i have waiting for device each time) so its bricked for EVER?!

You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........

sbdags said:
You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........
Click to expand...
Click to collapse
yes, it accept nothing! even if i downgrade to ics to apply the nvflash its worse! so should i say bye forever to my tf300t?!! if yes, which tablets tht cn be less bricked than others? thks a lottt! wht would u do if u were at my place? thksssssssssss

buy a new mainboard (motherboard)
Sent from my TF300T using xda app-developers app

How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?

Ti2 said:
How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?
Click to expand...
Click to collapse
thanks for yr reply ill try even im bricked! ill by another tabelt but not asus, maybe samsung, i have a GS2 , i install every thing without problem, i think there tables dont brick easly! true?

You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.

Ti2 said:
You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.
Click to expand...
Click to collapse
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.

sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
Wrong? No.
Harsh? Yes.
Read read read. Learn learn learn. Then read some more. When unsure, ask questions. Don't just try, then read the manual tot learn how you screwed up...
I am unsure tot flash 4.1 bootloader based roms through the 4.2 patched TWRP. I am NOT just going to try, I am awaiting an answer for 3 days now.
Is a Tab(2) as easily to brick as a Transformer? Yes it is.

sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
true wht u said !

Not trying to be harsh but that's why they call it "bleeding edge". You take the risks if you cannot be patient.
Sent from my SCH-I510 using xda app-developers app

hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck

lk2l said:
hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck
Click to expand...
Click to collapse
no succes to flash anything! always back to cwm 6.0.2.3...

when you type fastboot devices or adb devices can you see the device?

lk2l said:
when you type fastboot devices or adb devices can you see the device?
Click to expand...
Click to collapse
i can see this 0123456789ABCDEF, thts not the device name sure! isn't ? i can flash via fastboot ( sending ok, flashing ok) i flashed the blob file tht comes with the Asus frimwork 10.6.1.8 but nothing, always i go back to the 6.0.2.3 CWM! i flashed the twrp.blob file! same thing! im turning in an empty circle! good for trash??

depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how

lk2l said:
depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how
Click to expand...
Click to collapse
hope so! thkssssssssssssssssssssss

can you tell me which procedure you do to flash the recovery?
here you can found all I have used to flash my tf300t with the bootloader 4.2.1
fastboot+twrp recovery 2.4.4.0-4.2
is possible your fastboot dosen't work correctly?

Relock bootloader

Can I relock bootloader, and flash completely stock if I need?

Yes but at this moment don't, BC if something goes wrong u have no way of fixing it unless u call oneplus and wait for them to give u a remote session, don't be scared to have ur bootloader unlocked

suzook said:
Can I relock bootloader, and flash completely stock if I need?
Click to expand...
Click to collapse
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Bradl79 said:
Yes but at this moment don't, BC if something goes wrong u have no way of fixing it unless u call oneplus and wait for them to give u a remote session, don't be scared to have ur bootloader unlocked
Click to expand...
Click to collapse
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.

effmsee said:
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
Click to expand...
Click to collapse
just wait until u get it
don't believe u can sideload OS anymore, yes we do have a fastboot mode to restore but u will have to have ur bootloader unlocked, if u have ur bootloader locked there is not way to put on OS on there due to twrp is not mountable and u cannot side load, so its not like other OP devices

effmsee said:
Someone else will have to verify as my OP6 is still shipping but..
YES, OnePlus 6 should still be able to go complete back to stock as it always has.
The same procedure as the 3, 3T, 5, 5T will likely follow:
if you flash a complete stock rom such as (this is a OP6 stock rom): androidfilehost.com/?fid=674106145207488340
then while booted into fastboot mode: fastboot oem lock
This is a standard procedure for OnePlus devices and I'll test it out once I get mine.
The rom i linked to is the stock rom, an OP moderator linked to it.
And the fastboot command is just a standard command. So unless they decide to screw their main audience this time around, :good:.
---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------
Why do you state this?
OP has already shared a link to a stock rom. And the lock/unlock bootloader command is a standard for their devices.
Click to expand...
Click to collapse
Things are missing in recovery. Im hoping they forgot vs take the feature out.

Bradl79 said:
just wait until u get it
don't believe u can sideload OS anymore, yes we do have a fastboot mode to restore but u will have to have ur bootloader unlocked, if u have ur bootloader locked there is not way to put on OS on there due to twrp is not mountable and u cannot side load, so its not like other OP devices
Click to expand...
Click to collapse
Obviously you have to have you bootloader unlocked.
What are you trying to say? I can't follow your sentence structure. Please use proper English structure... or remotely proper...
You're claiming that with the OnePlus 6 you can no longer sideload roms? What??? That would be a HUGE slap in the face to us.
I wouldn't believe what this guy is saying.
I'm not claiming I factually know that the OP6 can be unlocked through that method but it is highly likely it is. As said, I'm still waiting on the OP6. If OnePlus doesn't allow these things, re-locking bootloader and sideloading, they're FU***** all of us over and I'm sure would suffer major backlash from the user base.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
intruda119 said:
Things are missing in recovery. Im hoping they forgot vs take the feature out.
Click to expand...
Click to collapse
Ah, got it. That sucks. :'( Thanks!

effmsee said:
Obviously you have to have you bootloader unlocked.
What are you trying to say? I can't follow your sentence structure. Please use proper English structure... or remotely proper...
You're claiming that with the OnePlus 6 you can no longer sideload roms? What??? That would be a HUGE slap in the face to us.
I wouldn't believe what this guy is saying.
I'm not claiming I factually know that the OP6 can be unlocked through that method but it is highly likely it is. As said, I'm still waiting on the OP6. If OnePlus doesn't allow these things, re-locking bootloader and sideloading, they're FU***** all of us over and I'm sure would suffer major backlash from the user base.
---------- Post added at 02:21 AM ---------- Previous post was at 02:20 AM ----------
Ah, got it. That sucks. :'( Thanks!
Click to expand...
Click to collapse
if all else fails we do have an unbrick tool, but from what i have read, u can no longer sideload with ur bootloader locked and there is not install from internal storage from stock recovery

I learned the hard way. Soft brick in the first hour of ownership.i thought I really broke something until eventually a few others reported on it. B
Op I would wait

I just relocked my bootloader with no issues. I uninstalled magisk through magisk manager, reboot to completely remove, then factory reset, boot into fastboot and relock. No issues. Note I didn't use twrp. I was still on stock bootloader.

BoboBrazil said:
I just relocked my bootloader with no issues. I uninstalled magisk through magisk manager, reboot to completely remove, then factory reset, boot into fastboot and relock. No issues. Note I didn't use twrp. I was still on stock bootloader.
Click to expand...
Click to collapse
Certain I did something wrong. But I tried the same thing initially and would bootloop to recovery after factory reset. Wasn't a biggie learned about the new a/b system in the process

Somewhat related question:
If you relock the bootloader, does Widevine go back to L1?
One user reported no. Is it really a permanent change of the Widevine status to unlock it?
I might be able to deal with 480p netflix, but if I sell this phone someday it sucks for the next owner.

No worry just try mega unbrick guide used it to relock bootloader and flash stock hydrogen os it can recover your device from even hardbrick I tested it for safety it works like charm so I recommend you that

Can anyone who has unlocked and re-locked their bootloader check their Widevine status in DRM info?

I have relocked because netflix quality was to low on when unlocked. When i relocked i got the drm lvl 1 back so it works

noppoer2 said:
I have relocked because netflix quality was to low on when unlocked. When i relocked i got the drm lvl 1 back so it works
Click to expand...
Click to collapse
What's the procedure to re lock the bootloader and revert to stock recovery along with no root.
I unlocked the boot loader, installed TWRP and Magisk but would like to go back to stock. Any help will be appreciated

kailashnj said:
What's the procedure to re lock the bootloader and revert to stock recovery along with no root.
I unlocked the boot loader, installed TWRP and Magisk but would like to go back to stock. Any help will be appreciated
Click to expand...
Click to collapse
Reinstall your rom ( i believe 5.1.6 ) to get rid of TWRP & root
Factory reset
Then on fastboot " fastboot oem lock"
Data & internal storage will be wiped

Which means post following the steps origins bootloader will be locked and I will not get the warning again right at the start of the phone

All you can do is try but first make a Nandroid just in case this falls through

Hi, I want to lock my bootloader after recently unlocking it on my OP6 to install Oxygen OS as was originally on Hydrogen OS. If I use CMD and type fastboot oem lock, what are the risks of the phone going into a boot loop, and also, does the factory reset revert the phone back to Hydrogen OS? Cheers.

thealexwu said:
Hi, I want to lock my bootloader after recently unlocking it on my OP6 to install Oxygen OS as was originally on Hydrogen OS. If I use CMD and type fastboot oem lock, what are the risks of the phone going into a boot loop, and also, does the factory reset revert the phone back to Hydrogen OS? Cheers.
Click to expand...
Click to collapse
Lock as you unlocked in cmd by typing lock instead of unlock. It will make a wipe, so I recommend make backup before.

November 2019 security update is now available

83.7MB
Installation without any troubles. No major changes. d2tw still not working.

Nothing to say

My device gives an error when i try to install.
Says: Failed to install update, tap here for more information.
When i tap, there is no 'more information' !
Stupid Android!

Install and nothing change, still have problem on sim1, when turn on data on sim1 i lost network.

perfect_ said:
My device gives an error when i try to install.
Says: Failed to install update, tap here for more information.
When i tap, there is no 'more information' !
Stupid Android!
Click to expand...
Click to collapse
Same Problem With My Device.
Anyways, Solution Is Here...
1st We Need To Unlock Bootloader Then Flash Currently Available Stock Rom Through MI Flash Tool.
Thanks,
MUHAMMAD Asif Qasim

perfect_ said:
My device gives an error when i try to install.
Click to expand...
Click to collapse
If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions. I have had to restore both system.img and vendor.img since 10.0.10.0 (the fact that I've been using a custom bootanim definitely does not help).
Code:
adb logcat | grep update_engine

a1291762 said:
If the OTA fails, you can find out which partitions it doesn't like from the logcat. If you have a fastboot image, you can reflash the affected partitions. I have had to restore both system.img and vendor.img since 10.0.10.0 (the fact that I've been using a custom bootanim definitely does not help).
Code:
adb logcat | grep update_engine
Click to expand...
Click to collapse
Hello Dear,
Can You Guide Stepwise How To Fix Partition ? I Do Not Want To Unlock The Bootloader Or Flashing The Stock ROM. I Just Want To Fix Issue That Causing The Update.
In Addition to That My Device Is Updated aon Last October.
Your Help Will Be Highly Appreciated In This Regards.
Thank You In Advance

aasiaasi said:
Can You Guide Stepwise How To Fix Partition ? I Do Not Want To Unlock The Bootloader Or Flashing The Stock ROM. I Just Want To Fix Issue That Causing The Update.
Click to expand...
Click to collapse
I'm used to flashing from fastboot but I'm pretty sure that only works with an unlocked bootloader. I've read that you can use miflash with a locked bootloader but you need a complete rom and the most recent one is 10.0.13.0
Sorry

a1291762 said:
I'm used to flashing from fastboot but I'm pretty sure that only works with an unlocked bootloader. I've read that you can use miflash with a locked bootloader but you need a complete rom and the most recent one is 10.0.13.0
Sorry
Click to expand...
Click to collapse
Thank You For Time And Reply.
OKay What Should We Do To Fix The (Partition) Problem. ? Complete Stepwise Guide Will Be Beneficial To Us.
One More Question.
Is There A Way To Get Every Month OTA Installed Without Interrupting (Unlock Bootloader , Rooted With Magisk) ? If Yes , So What Could Be The Steps/Guide.
Thanks.

aasiaasi said:
Is There A Way To Get Every Month OTA Installed Without Interrupting (Unlock Bootloader , Rooted With Magisk) ? If Yes , So What Could Be The Steps/Guide.
Click to expand...
Click to collapse
If you just have Magisk, this is all you should need to do.
https://forum.xda-developers.com/mi...ll-magisk-proper-support-ota-t3836952/page100
If you have other stuff that breaks that process (eg. Magisk + TWRP) then you need extra steps.
https://forum.xda-developers.com/mi...to-10-0-7-0-ota-keeping-magisk-t3916863/page9
---------- Post added at 12:23 AM ---------- Previous post was at 12:13 AM ----------
aasiaasi said:
OKay What Should We Do To Fix The (Partition) Problem. ? Complete Stepwise Guide Will Be Beneficial To Us.
Click to expand...
Click to collapse
Previously you said you did not have an unlocked bootloader, but you asked for OTA instructions with Magisk...
Since you don't have backups of the modified partitions, you should backup your data then install 10.0.13.0 from fastboot image. This is the only option if your bootloader is locked (I think that miflash allows this?)
If you are modifying your device I'd suggest backing up the partitions that were rejected by the upgrade (logcat). See the advanced guide I posted for details.
If you have backups you just need to restore the partitions the upgrade is complaining about (logcat).

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.

Vortex V22 Standup Wireless Firmware Error

Hello!
I tried the search function but my search-fu isn't strong today. I got a Vortex V22 phone from Standup Wireless. I must have been half asleep, because when i flashed what I assumed was the correct boot.img, I got stuck in a boot loop.
On further investigation, I had flashed the boot for another device called Vortex. I am having incredible difficulty in finding the right boot image. The info I have from the side of the box is:
Vortex V22 4G LTE
Color: Graphite Blue
ROM 32GB
RAM 3GB
OS Android 11
FCC ID 2ADLJ-V22
I deeply appreciate any and all help. Thanks so much!

i was trying to find a phone case for the phone what model number is yours ?

If you're still searching I can try to make a rom dump, I have this phone as well brand new untouched or registered.
I'd just need a tutorial on the proper way to dump and extract the files so I can upload the boot.img
_
I've never used it cause I put the StandUp Wireless sim in my T-Mo InSeeGo 5G HotSpot and prefer to use my Galaxy S8 with Keyboard Cover Case and Unihertz Titan Pocket

Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.

PicelBoi said:
Just dumping the firmware from mine, using SP Flash Tool. Used this guide: https://www.hovatek.com/forum/thread-12719.html
Will remove userdata & cache, but there is a LOT of gbs of system data. This phone is appearently Treble-enabled with VNDK ver 30, so yes, you can flash a GSI on there. Will provide a custom recovery necessary.
Edit: if you were wondering, this phone has a MT6761 with a eMMC flash.
Click to expand...
Click to collapse
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.

In fastboot not fastboot d do
Fastboot flash unlocking
And it'll ask ya if u agree bs....
& Click yes.
Mtkclient unlocks bootloader as well

defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!

PicelBoi said:
Sorry for waiting so long! Yeah, I got the firmware! Also follow previous guys post! Do you want my boot.img? Make sure you disable Android Verified Boot too!
Click to expand...
Click to collapse
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.

mee too

defcondoc said:
No worries. Yes! Do you have the entire rom? The boot.img would definitiely be great as well.
Click to expand...
Click to collapse
Yea, will post it later this day! Do you need anything else like my super partition?

PicelBoi said:
Yea, will post it later this day!
Click to expand...
Click to collapse
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.

defcondoc said:
Hi PicelBoi,
I have the V22. I've unlocked the BL and trying to install a custom rom via ADB or Fastboot but have had no luck. I try to erase or flash and I get errors saying partitions don't exist. Can you please help out with a recovery file?
I tried the hovatek guide but didn't have any luck, but I tried it before the BL was unlocked. Would that be an issue with the sp flash tool? I was told it shouldn't matter.
Click to expand...
Click to collapse
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.

PicelBoi said:
Also this is a GSI image that works with this device - https://github.com/phhusson/treble_experimentations/releases/tag/v313 - newer versions might not work unfortunately.
Click to expand...
Click to collapse
I was able to get a bunch of GSI's that work with it, including the phone you posted, but I was looking to get root and found a couple pre-rooted GSI's that work as well. Newer ones do work as well I has 13 rooted and working. However, I liked the Pixel ROMs the best and would prefer to install those instead and then root. So I need the firmware for that so I can patch a modified boot.img.

PicelBoi said:
You need to reboot to userland fastboot, which you could do by rebooting to normal fastboot then telling fastboot to reboot to fastboot by typing in fastboot reboot fastboot. You will see a new screen, and now you could flash a GSI to the phone.
Click to expand...
Click to collapse
Thank you. I understand and have a lot of experience with this. However, I still never understood why there is two Fastboot's.

I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?

atsalchenberg said:
I can't get it to boot in one I flash the super that I backed up that don't get it to boot maybe I could use a good super. What about vbmeta?
Click to expand...
Click to collapse
Are you looking for a good GSI ROM?

As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.

But yes I am indeed looking for a good running a12 rom

atsalchenberg said:
As of right now I'm just trying to get it booted up with any room. I got it rooted and then something I ****ed up when I tried to flash a GSI. And I started messing with the boot a boot b vbMeta from system and blank. And I don't have the firmware an the super that I backed up won't boot when I flash it.
Click to expand...
Click to collapse
I completely messed up one messing with partitions and it took many tries trying to get to was able to still get to the bootloader fastboot and then recovery to fastbootD. You should be able to get it booted into fastbootd and flash as it seems you can.
Try the one below. you should be able to find it with a google search. If you can't let me know and I will try to look and see where I downloaded it from as I cannot remember where I found it.
I've tried many GSI ROM's Some boot fully, some only boot to the boot screen and some won't boot at all.
I'm using 13 rooted LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
It is vanilla. I can't remember if there is a GAPPS version or not. But you can load it all after with magisk. But its rooted.
I still would like if picelboi could share the stock rom, so we can have a boot.img. I would like to try other ROM's that are not PRE-Rooted.

atsalchenberg said:
But yes I am indeed looking for a good running a12 rom
Click to expand...
Click to collapse
I can't remember which A12 I had working but I was looking for root and the one A12 that was prerooted I had issues with so I went to A13.
This is an A13. LineageOS GSI version 20-20230324-UNOFFICIAL-arm64_bvS
There may be a newer version of it now.
Also, these phones seem have that internet connect issue with some GSI ROMS and this is one of them I think, they connect to wifi but they won't actually connect to internet, but there is a easy fix for it.