ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
zendick said:
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
Click to expand...
Click to collapse
There should be an option on fastboot to go to bootloader and then from there recovery should be available, is that option available to you?
yes but recovery won't boot, sits at mt4g boot screen or sits at 3 skaters in center screen, depending on how I access it (ie go to fastboot then back again)
Power down your phone, hold volume down and the power button. That will take you into the hboot screen. You can then select to go into recovery from there.
thats what I have tried, it goes to three skaters center screen does nothing
I have tried flashing recovery from fastboot
tried hboot from fastboot
tried radio from fastboot
NOTHING flashes trust me I have been androiding for a while now never had I had a problem like this.
zendick said:
thats what I have tried, it goes to three skaters center screen does nothing
Click to expand...
Click to collapse
Is three skaters your boot animation or splash screen? Not sure what that is referring to.
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
zendick said:
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
Click to expand...
Click to collapse
Oh ok, i know what your talking about now. Your on the bootloader screen under fastboot. And when you select recovery option it does not boot into recovery?
correct and like i said I have tried to reflash everything from fastboot but no go
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
got recovery to boot but get
e:can't mount /cache/recovery/command
etc
tried to mount, tried to format
no go
What do you mean tried ruu??
zendick said:
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
Click to expand...
Click to collapse
Edit: nvm. Is doing RUU better option than loading PD15IMG.ZIP on sdcard and doing it that way?
Sent from my SGH-T959 using XDA App
tried a pd15 and it doesn't complete, drops a failed message
Sounds like you maybe victim of fail-pu. But if thats not the case and you don't care about your "/data" and just want working phone again then I suggest from fastboot you do "fastboot flash recovery recovery.img" which will replace the current recovery.img and flash it to mmcblk0p21. Once thats done do "fastboot erase system -w" and it will nuke everything so /system, /data, ect will all be erased. After that you can enter recovery by selecting it from hboot and then do factory wipe and flash another rom.
Keep in mind you will run in to errors in recovery after -w as its normal but depending on the fail-pu if you do get the failed partition update flag you can't make any changes as the errors will stick because you can't format the drives. Also the new recovery.img for CWMR can be found in dev section if not post here and ill send you.
I don't care at all about the data (I am well backed up) but I can't flash a recovery I have tried through fastboot, I agree the partition is F_D but I will try the erase system -w and see if that lets me do anything
thanks
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Exactly what I got too, seems we have bricked our phones. Wish I had a way of making the phone unable to boot to recovery or at all.
zendick said:
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App
I dont get how a phone can run for weeks since its last flash and have this happen, I made no changes updates etc just running as normal.
Is there a way to wipe evidence of cm of so I can get this phone repaired? To me this obviously a faulty emmc, I just can't see it being anything else.
or is it possible to boot recovery on sd like the nook?
any ideas on how to wipe cm bits atleast?
Related
Error in CACHE: recovery/log (No space left on device) ...
After trying to flashing MTD pathes.... ****.... What i should to do?
I can't falsh any rom now. always had Error in CACHE: recovery/log (No space left on device) ...
try to wipe all, try to fastboot erase system -w...
Always the same result
i can log on Fastboot and Recovery RA 1.7 all fine
****... now i try
fastboot erase recovery
fastboot flash recovery C:/recovery.img
and get
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
....agrrrrrrrrrrrr
after this reboot in recovery... and logo of my phone i see only... in left upper side of screen line: FASTBOOT USB
after this i try :
fastboot erase recovery
got > erasing 'recovery'....
and stack... about 10 minutes i wait... scary.... what i should to do?
i can power off my phone? (battery)
ANtiHazarD said:
Error in CACHE: recovery/log (No space left on device) ...
After trying to flashing MTD pathes.... ****.... What i should to do?
I can't falsh any rom now. always had Error in CACHE: recovery/log (No space left on device) ...
try to wipe all, try to fastboot erase system -w...
Always the same result
i can log on Fastboot and Recovery RA 1.7 all fine
Click to expand...
Click to collapse
ANtiHazarD said:
****... now i try
fastboot erase recovery
fastboot flash recovery C:/recovery.img
and get
sending 'recovery' <4594kb>... OKAY [ 1.734s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verigy fail>
finished. total time: 3.125
....agrrrrrrrrrrrr
Click to expand...
Click to collapse
ANtiHazarD said:
after this reboot in recovery... and logo of my phone i see only... in left upper side of screen line: FASTBOOT USB
after this i try :
fastboot erase recovery
got > erasing 'recovery'....
and stack... about 10 minutes i wait... scary.... what i should to do?
i can power off my phone? (battery)
Click to expand...
Click to collapse
I had the same thing yesterday happen but before freaking out I left my phone connected to my pc in recovery with the error on the screen and used ADB to flash a new recovery right over the old one and it worked try that. Boot phone into recovery (if you still can after everything you have done) with your phone connected to your PC, open up ADB and flash the recovery file that way.
i can't boot recovery now... when USB connected and when i try to boot recovery i see only first bootscreen (Orange MTN logo)
and in left upper side of screen "FASTBOOT USB"
and that's all....... =(
coz now i don't have any recovery... only HBOOT...
ANtiHazarD said:
i can't boot recovery now... when USB connected and when i try to boot recovery i see only first bootscreen (Orange MTN logo)
and in left upper side of screen "FASTBOOT USB"
and that's all....... =(
Click to expand...
Click to collapse
Anti I am not trying to be mean but thats cause you freaked out when you saw something you never have before instead of taking a breath and asking first.
If you can hold down the back button and power on your phone and get into the fastboot menu you should still be good. you can flash the recovery image from fastboot. Follow the instructions on amons page to do it.
thx... i trying to flash via fastboot... but always got fast line :
FAILED <remote: signature verify fail>
ANtiHazarD said:
thx... i trying to flash via fastboot... but always got fast line :
FAILED <remote: signature verify fail>
Click to expand...
Click to collapse
I dont really use fastboot much, so I cant help you there but you should be able to flash the recovery. try a different recovery, try Cyanogens recovery file. All I do know is it has to be in the tools folder.
okey! thx, now will try!
ANtiHazarD said:
okey! thx, now will try!
Click to expand...
Click to collapse
No Problem, let me know how it turns out.
=(( it's crazy..
can i flash any rom via Fastboot mode???
Any rom! But for NoneDanger SPL...
ANtiHazarD said:
=(( it's crazy..
can i flash any rom via Fastboot mode???
Any rom! But for NoneDanger SPL...
Click to expand...
Click to collapse
Not that I know of. I could be mistaken but that all has to be done through recovery. But maybe somebody else will chime in on the conversation. If fastboot isnt fixing recovery then, I am sorry to say it but you might just be SOL and you might want to see if your phone is under warranty still. haha
So in CMD on windows you are typing this in:
Copy recovery-RA-dream-v1.7.0.img to a location where fastboot can find it.
Boot your G1 into fastboot mode (boot while holding BACK)
Connect your G1 via usb to your pc/mac/...
fastboot devices (to make sure that fastboot "sees" your device)
fastboot flash recovery recovery-RA-dream-v1.7.0.img
and its not working? And you placed the recovery img in the tools folder where your sdk is right.
i don't understand what is it:
Boot your G1 into fastboot mode (boot while holding BACK)
I boot into fastbook like this:
Camera+Power, then press SEND
and i got FASTBOOT USB
it is not right?
and all other steps is right!
fastboot devices :
HT94XNG01269
than :
fastboot flash recovery recovery-RA-dream-v1.7.0.img
got:
sending recovery 'recovery' <4602kb>... OKAY [1.750s]
writing 'recovery'... INFOsignature checking...
FAILED <remote: signature verify fail>
finished. total time: 3.141s
Click to expand...
Click to collapse
MD5 sum FINE!...
It's scary... what i should to do... i don't know...
ANtiHazarD said:
i don't understand what is it:
Boot your G1 into fastboot mode (boot while holding BACK)
I boot into fastbook like this:
Camera+Power, then press SEND
and i got FASTBOOT USB
it is not right?
Click to expand...
Click to collapse
I am just going to ask a simple question is your G1 Rooted? with your phone off hold the back button which is the button at the bottom with the arrow then hit the power button you should get a white screen with a little android at the top.
my G1 is rooted... and have NoneDanger SPL. I can't find information about it (HBOOT 1.42.0000, DREA20000)
when i press BACK+POWER i got first boot logo screen and thats all... orange color background and the MTN logo in i square in the middle of the screen.
I got 3 android skaters when press camera+power... only like this...
maybe i can use this:
fastboot flash system rom.zip
Click to expand...
Click to collapse
?
as i remember here http://developer.htc.com/adp.html
file - signed-dream_devphone_userdebug-ota-14721.zip
flash official 1.6 android rom and standart htc recovery....
Maybe i'll try this? how u think?
ANtiHazarD said:
my G1 is rooted... and have NoneDanger SPL. I can't find information about it (HBOOT 1.42.0000, DREA20000)
when i press BACK+POWER i got first boot logo screen and thats all... orange color background and the MTN logo in i square in the middle of the screen.
I got 3 android skaters when press camera+power... only like this...
Click to expand...
Click to collapse
See I am running Danger just like most people, thats the difference in the fastboot access. the 3 android skaters is the proper screen. So you are in the right spot. You should have also menu options like hit menu to reboot etc...I cant remember the others. But still its right. So if you are doing the fastboot commands as posted and it still gives you an error then it was something to do with when you did all those remove commands.
I think you pretty much have a nice heavy paperweight sorry bro. Only thing I think of is keep trying the fastboot command or maybe see if there is a way to flash stuff through fastboot. I dont think there is but you can look and see. Good luck, let me know how it turns out. If I was you I would just go get a slide or the new Galaxy S
ANtiHazarD said:
maybe i can use this:
?
as i remember here http://developer.htc.com/adp.html
file - signed-dream_devphone_userdebug-ota-14721.zip
flash official 1.6 android rom and standart htc recovery....
Maybe i'll try this? how u think?
Click to expand...
Click to collapse
That looks promising you can try that. good luck
Hi, I bricked my n7 so badly. Here is what I did.
I accidentally flashed nakasig factory image on my wifi n7 from google factory images. It gave me a lots of errors.
I already had screen jamming issues when battery is < 5. Now my userdata partition is broken. I can't erase or format using recovery/fastboot. It always gives me errors. When I stay too much at recovery or bootloader it starts jamming. I can flash roms but it doesn't boots because of not working userdata partition and after waiting a while at boot animation. I can't turn my n7 on by just holding it for 2-3 seconds. I almost hold for 30-40 seconds everytime(Unless I choose reboot to recovery or reboot to bootloader from recovery or fastboot). Before people start saying flash the wifi factory image, yes I tried, even the 4.1.2 factory image. System partition gives me this error
Code:
sending 'system' (446268 KB)...
FAILED (status read failed (Unknown error)
finished. total time: 1.169s
I also found I can erase userdata partition after erasing system boot and cache it says ok but looks like its not working.
I can flash custom roms using sideloading but they don't boot.
Nexus 7 (grouper) doesn't boot - Bootloader says "FAILED (remote: (FileWriteFailed))"
Hi,
My Nexus 7 (grouper) won't boot Android anymore. It automatically boots into the bootloader and when I select 'Start' or 'Recovery Mode' it just says "Booting failed".
When I try to flash a new recovery Image over fastboot I get the following Output:
[[email protected] Downloads]$ sudo fastboot flash recovery twrp-2.8.7.0-grouper.img
sending 'recovery' (11850 KB)...
OKAY [ 1.409s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 1.441s
Click to expand...
Click to collapse
It's the same, when I try to flash anything else. So I have no chance to flash a Stock-Image. I also get the same error when I try to format a partition. I'm pretty much out of ideas now. Can anybdoy help me?
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
productofusa said:
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
Click to expand...
Click to collapse
When I try to flash the bootloader I get:
[[email protected] Downloads]$ sudo fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.403s
Click to expand...
Click to collapse
And when flashing other partitions it says "FAILED (remote: (FileWriteFailed))".
Something seems to be really screwed up with my storage. Is there a way to repartition the device from fastboot? Maybe that would be help.
I'm willing to try out everything, by now.
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
productofusa said:
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
Click to expand...
Click to collapse
I already downloaded them multiple times. And even if they are corrupt, formatting the partitions should still work. I'm guessing on corrupt storage now, as I can't find any other explanation. Maybe I can find a cheap Motherboard somewhere on the internet. Thanks, anyways
Hi so I want to revert back to factory image, however I keep on getting "file not found" or "target didn't report max-download-size" error. I already installed the drivers, unlock the bootloader and when I check fastboot devices, the phone shows up.
Any help would be greatly appreciated.
Ive had similar performance within the bootloader menu. Some things to check on your pc verify that the phone is showing up in device manager as essential phone fastboot. You may need to restart the pc or change usb port to get it to properly communicate.
You should also be able to revert to the factory image through the normal recovery; instead of attempting to install twrp to flash the stock image (sounds like what you might be trying to do your post is a little unclear) you can always just run the normal essential recovery partition and then use adb sideload from there to restore the factory image.
From essential's website
https://www.essential.com/developer/beta-builds
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen.
Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command: adb devices. Then check that your device shows up with “sideload” next to its name
Run the following command: adb sideload ota_file.zip where ota_file.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Halp
Zargone said:
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Click to expand...
Click to collapse
Did you manage to successfully flash the stock image? If yes, would you kindly provide the steps that you performed? Im trying to get back to Oreo from Android P Beta so that I can have my unit replaced
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
lolifer said:
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
Click to expand...
Click to collapse
Have you enabled oem unlock in developer options?
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
lolifer said:
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
Click to expand...
Click to collapse
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
gm007 said:
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
Click to expand...
Click to collapse
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
lolifer said:
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
Click to expand...
Click to collapse
You will need to side load the OTA.
You cannot flash.
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
But I cannot get adb to work, only fastboot. I install essentials ADB, download Essential drivers. Am I missing something? In Device Manager while in fastboot it says Essential Fastboot Phone.
Im starting to think the original owner must have had twrp and installed OTA update without going back to stock recovery. If I were to assume this the case, what would be the next step to recover?
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
How do I go about sideloading from fastboot?
Don't know. My phone is rooted and bl unlocked
lolifer said:
How do I go about sideloading from fastboot?
Click to expand...
Click to collapse
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
galakanokis said:
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
Click to expand...
Click to collapse
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Yeah, was just curious about what you were seeing in recovery. If your bootloader is locked and you have somehow lost recovery I am not to sure what else you can do. You said you switched slots and still were unable to boot to recovery?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
rignfool said:
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
Click to expand...
Click to collapse
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
lolifer said:
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
Click to expand...
Click to collapse
Damn...
I woulda thought for sure you could flash signed image...
just fired up miraclebox and did a read info under the qualcomm section and this was my result.
Starting..
Waiting for Phone...
Phone Found..
version:0.5
unlocked:no
off-mode-charge:1
charger-screen-enabled:1
battery-soc-ok:yes
battery-voltage:3721
version-baseband:2.0.c4-M1.2
version-bootloader:mata-4452425
variant:
partition-type:userdata:ext4
partition-size:userdata: 0x1987357000
partition-type:system_b:ext4
partition-size:system_b: 0x100000000
has-slot:nvdef:yes
has-slot:dsp:yes
has-slot:vendor:yes
has-slot:devcfg:yes
has-slot:cmnlib64:yes
has-slot:cmnlib:yes
has-slot:boot:yes
has-slot:keymaster:yes
has-slot:abl:yes
has-slot:mdtp:yes
has-slot:mdtpsecapp:yes
has-slot:bluetooth:yes
has-slot:modem:yes
has-slotmic:yes
has-slot:hyp:yes
has-slot:tz:yes
has-slot:rpm:yes
has-slot:xbl:yes
has-slot:system:yes
current-slot:_b
slot-retry-count:_b:0
slot-unbootable:_b:no
slot-successful:_b:no
slot-retry-count:_a:0
slot-unbootable:_a:yes
slot-successful:_a:no
slot-count:2
slot-suffixes:_a,_b,
secure:yes
serialnoM1LHMD762601033
product:Mata
max-download-size:0x20000000
kernel:uefi
all:
0.011s
>>Process Done...
My main rooted v20 phone got bumped and now is stuck in a bootloop. I can enter fastboot (some commands working) but can't access TWRP recovery using either VOL + UP and USB cable or VOL DOWN + POWER. I believe the phone is on 10j or 10k if I remember correctly. Bootloader and carrier are unlocked.
Is there a way to just reflash TWRP safely and attempt data recovery and ROM installation without factory reset?
My goal is to attempt recovery first. If that is not an option, I would like to flash to 10p so I can start the rooting process using Lafsploit.
DirtyBreakz said:
My main rooted v20 phone got bumped and now is stuck in a bootloop. I can enter fastboot (some commands working) but can't access TWRP recovery using either VOL + UP and USB cable or VOL DOWN + POWER. I believe the phone is on 10j or 10k if I remember correctly. Bootloader and carrier are unlocked.
Is there a way to just reflash TWRP safely and attempt data recovery and ROM installation without factory reset?
My goal is to attempt recovery first. If that is not an option, I would like to flash to 10p so I can start the rooting process using Lafsploit.
Click to expand...
Click to collapse
Sure, to flash twrp in fastboot mode you do this.
Download latest twrp
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h918.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
U
Darnrain1 said:
Sure, to flash twrp in fastboot mode you do this.
Download latest twrp
With the phone off hold vol down plug USB into phone and computer.
type on your computer:
fastboot flash recovery twrp-3.6.2_9-0-h918.img
fastbboot reboot
take battery out
put back in
go into twrp by doing a factory reset. How to factory reset the Lgv20
Click to expand...
Click to collapse
Unfortunately no joy. I tried fastboot boot and flash commands and even tried renaming the img file. I tried with 3 different versions of twrp. This was the result:
PS C:\Users\User\NexusTools> fastboot boot twrp-3.6.2_9-0-h918.img
Sending 'boot.img' (24948 KB) OKAY [ 0.771s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
PS C:\Users\User\NexusTools> fastboot flash recovery twrp.img
Sending 'recovery' (23512 KB) OKAY [ 0.854s]
Writing 'recovery' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
I've searched the forums and internet for hours and not coming up with anything. Any other ideas?
Just a note when trying to cold boot to twrp using 'UP VOLUME + CONNECT USB' that the screen flashes download mode for a split second and then reboots.
DirtyBreakz said:
U
Unfortunately no joy. I tried fastboot boot and flash commands and even tried renaming the img file. I tried with 3 different versions of twrp. This was the result:
I've searched the forums and internet for hours and not coming up with anything. Any other ideas?
Just a note when trying to cold boot to twrp using 'UP VOLUME + CONNECT USB' that the screen flashes download mode for a split second and then reboots.
Click to expand...
Click to collapse
That's so odd I have never seen this issue before.
You can try flashing the twrp image to the boot partition.
fastboot flash boot twrp.img
fastboot reboot
Should boot rite into twrp then because the twrp image is on the boot partition. Sounds to be like there may be a hardware problem with this phone.
Darnrain1 said:
That's so odd I have never seen this issue before.
You can try flashing the twrp image to the boot partition.
fastboot flash boot twrp.img
fastboot reboot
Should boot rite into twrp then because the twrp image is on the boot partition. Sounds to be like there may be a hardware problem with this phone.
Click to expand...
Click to collapse
Well unfortunately the flash boot command failed also. I'm guessing because it shows the boot partition size is 0. Any possible way around this?
I'm hoping not but I think you might be right about a possible hardware issue...
PS C:\Users\User\NexusTools> fastboot flash boot twrp.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 24076288).
Sending 'boot' (23512 KB) OKAY [ 0.817s]
Writing 'boot' FAILED (remote: 'unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
DirtyBreakz said:
Well unfortunately the flash boot command failed also. I'm guessing because it shows the boot partition size is 0. Any possible way around this?
Click to expand...
Click to collapse
I think it's a hardware issue with the ram. I cant think of anything else.
Do a search online for the error message.
Writing 'boot' FAILED (remote: 'unknown command')