I can not pass files through twrp - Moto G4 Plus Questions & Answers

My cell phone corrupted the HW partition. Then the SIM cards stopped picking up a signal. I found the solution, but I'm facing a problem that I can not solve.
My TWRP simply hangs when I do
adb push hw.img /dev/block/mmcblk0p43
Stop working, I've left it for more than an hour. And because of that I just can not get past the file.
And when I use dd=/if with the system turned on. It seems that the file does not pass, or is it necessary to change the permissions after passing this command?

make a clean restore by flashing latest firmware, wipe rom, return into bootloader, flash TWRP (32bit) , try to repair or repartition, no guarantee for this, just a try to help

Related

[HELP!] Failed CM flash & now wont mount /system

EDIT: SOLVED. Sorry, please ignore
I am using TWRP, I factory reset fine.
I then lined up 3 zip files to flash. CM10.1, Gapps and Cerberus
The screen turned off while flashing and I panicked. It wouldnt turn on again. I'm thinking it was because of the screen off delay.
I panicked and pushed all of the buttons several times but couldn't get the screen to turn on again.
Now I've turned off the screen off delay and now I'm trying to re install CM but it keeps getting the following
E: Unable to mount ' /system '
I can still access TWRP recovery and Download.
Is there any way to restore the partitions?
--------------------------------------------------------
Edit from here on:
I was able to recover the partitions by downloading this following PIT file:
http://d-h.st/v7C
I used it with ODIN, I put my phone in download mode and put pushed the PIT file onto my phone, which fixed the partitions. From there I was able to just install CM10.1 like normal

Soft bricked Nexus 6P, bootloop

EDIT: A lot of Users have the same Issues, read about it here: https://productforums.google.com/forum/#!topic/nexus/iPnYjg322Q8
Edit2: this thread can be closed, thanks.
Hi,
i am stuck in a bootloop. I tried to find a thread with the same issue, but i wasn't succesful.
So here's what i've done and what's my problem.
Problem:
The Phone is stuck after the google logo, restarts .
i CAN get into TWRP/recovery/bootloader
what i did:
I flashed the factory images (even different versions) both via flashall.bat and manually typing.
after that i tried a new install and hard reseting, erasing cache afterwards.
I treid to adb sideload the Full OTA Roms, no luck either.
I tried installing Custom Roms(lineage, DU)/ EX Kernel on top of stock rom.
& the usual stuff like changing pcs, cables and usb ports.
The Flashing works fine everytime.
When i connect my N6P to my pc after flashing, it says 110GB free out of 110Gb.
EDIT: when i open file manager in twrp, i see a lot of folders (root, recovery, system, cache boot etc)
I thought maybe it is a permission problem or a filesystem problem?
Maybe i need to change filesystems in twrp?
please shre any ideas with me, i appreciate your help. My ohone is now bricked for nearly 24hours... I have no backup phone.
madddiiin said:
Hi,
i am stuck in a bootloop. I tried to find a thread with the same issue, but i wasn't succesful.
So here's what i've done and what's my problem.
Problem:
The Phone is stuck after the google logo, restarts .
i CAN get into TWRP/recovery/bootloader
what i did:
I flashed the factory images (even different versions) both via flashall.bat and manually typing.
after that i tried a new install and hard reseting, erasing cache afterwards.
I treid to adb sideload the Full OTA Roms, no luck either.
I tried installing Custom Roms(lineage, DU)/ EX Kernel on top of stock rom.
& the usual stuff like changing pcs, cables and usb ports.
The Flashing works fine everytime.
When i connect my N6P to my pc after flashing, it says 110GB free out of 110Gb.
I thought maybe it is a permission problem or a filesystem problem?
Maybe i need to change filesystems in twrp?
please shre any ideas with me, i appreciate your help. My ohone is now bricked for nearly 24hours... I have no backup phone.
Click to expand...
Click to collapse
So if i go into twrp/wipe/advanced
select system + repair r change filesystem it says:
Size: 2929 MB, Used: 2597 MB, ext4
select data, ".."
Size: 113661 MB, Used:0 MB, ext4
I can Repair System , but not data.
data: it says /sbin/e2fsck -fp /dev/block/mmcblk0p44 process ended with error: 1 unable to repair data.
EDIT:
I tried to format every partition;
chache, userdata and system format fine,
but boot cant be formatted; it report error: "Formatting is not supported for filesystem with type ' '."
is my boot partition broken?

Need help returning to stock, have constant issues, please HELP!!!

Hi,
I initially had G935FXXS3ERHD_G935FXEO3ERG2_XEO installed and flashed Glamour ROM S9+ port some time ago, now i need to return it to stock but no luck...
Using latest odin i flashed:
G935FXXU3ERL3_G935FXEO3ERKF_XEO
and
G935FXXU3ERJE_G935FXEO3ERJF_XEO
(i need to remain on 3 bootloader)
after each flash i receive the NO COMMAND screen, and cannot boot into stock recovery... only way to boot the phone is to install TWRP... I have noticed when i plug the phone is it comes up as GALAXY S9+ so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
i have no idea what else to try
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot 
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try

Soft-bricked, messed up /vendor partition?

Ok, so I’m trying to fix this phone my friend messed up like a year ago and then gave up on..
Huawei P10 Lite
Build No: WAS-LX1C432B183
Bootloader: unlock
FRP: unlock
Rooted (or used to be I guess)
These are his notes from back then:
Flashed an unstable Lineage build and provided the wrong vendor.img –
tried to flash stock Nandroid backup through TWRP, which failed, phone was still running Lineage. Bugs got worse every reboot, finally stuck in bootloop on Lineage booting screen. Then did a full wipe and flashed stock ROM again - update_data_full_public.zip worked, update_full_WAS-L01_hw_eu.zip failed ("error:9")
finally flashed vendor.img the same way as with the wrong file in the beginning dd if=/external_sd/vendor.img of=/dev/block/bootdevice/by-name/vendor
now device can't mount /vendor anymore and bootlooping on the “ur device can’t be trusted” screen
Ok, so now I honestly don’t know what the last command actually does or if he got it wrong, he can't remember where he got it from and so far I didn't really find anything on it either..
I can now
• boot into erecovery, which starts but fails every time ("file does not exist"),
• do 3 button method, which gets to 5% then stuck again and returns to bootloop
• fastboot flash just about anything successfully according to logs – still bootloop
• use Unbrick option in the Multi Tool (which does the same as far as I can tell), again successful according to logs but still bootloop
• get into TWRP, flash stuff from there (stock, Lineage), also success but no change
I keep getting “failed to mount /vendor” in the logs though, and still can’t mount /vendor from TWRP and it says it’s 0MB.. I honestly don’t dare messing with partitions on my own as I’m not sure what the exact problem is..
Can someone please help?
Thanks already (and sorry this is so long..)

Asus Zenpad Z380M Wont turn on or boot to any mode after attempted magisk root with locked bootloader

Okay, Let me explain exactly what I did here... I first flashed Twrp using SP flash tool which worked without too much problem. Then I attempted to install the latest super su zip which told me the boot.img was already patched and it could not find a ramdisk... So I moved on and flashed the latest Magisk zip which flashed no problem. Rebooted the device and it came up with a red boot state telling me it would boot in 5 sec. It did not boot at all. Turned off the tablet and rebooted into twrp again. I then flashed the OTA update system.img, boot.img, and re-flashed twrp from twrp itself instead of the SP flash tool. It booted into twrp no problem, however now it said it could not mount the system partition. I did a full data wipe, factory reset, rebooted into twrp again. Same issue. So I attempted to re-flash the firmware with SP flash tool. Did not notice i had it set to format and download and not only download. It said formatting for maybe 2 sec and gave me an error. Now the device will not turn on at all... no screen whatsoever, no recovery, etc... I have had no luck getting the asus flash tool to even recognize a com port however SP flash tool seems to be able to flash the device no problem. I extracted the .raw firmware file I have for the latest firmware, modified the scatter file to allow flashing all partitions, and I did a full firmware flash of the device using SP flash tool. However it still does not turn on... it does nothing... So I'm assuming that I accidentally formatted over the bootloader... And I cannot find a bootloader flash file for this device anywhere... So I'm stuck with an Asus ZenBrick... Does anyone know a way to fix this issue? When I plug the device into my computer and open device manager it switches between the preloader and mtk serial port very quickly not staying on either one very long. I'm assuming this is why I cant get the asus flash tool to work and SP flash tool works off just the initial preloader. I just bought this tablet from someone and managed to hard brick it in less than a days time... Any help at all with a way to revive this device will be greatly appreciated. Thank You in advance to anyone who tries to help me fix my mess up.

Categories

Resources