I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
target reported max download size of 536870912 bytes
sending 'recovery' (45048 KB)...
OLAY [ 1.385s]
writing 'recovery'...
FAILED (remote: No such partition.)
finished. total time: 1.405s
Click to expand...
Click to collapse
So there is no recovery partition on my phone currently, but I can still boot to stock recovery
th3 game said:
I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
So there is no recovery partition on my phone currently, but I can still boot to stock recovery
Click to expand...
Click to collapse
Its likely a dodgy lead or try a different usb port!
I had it before and had to reboot my laptop that was all
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
th3 game said:
I am not sure when or how this happened, but I have installed Magisk and Xposed a while back (about a month ago) and had no issues. Today I was looking at kernels to install and decided to go into TWRP to do a backup, only to find the stock recovery on my device. Following Rooting Your Essential this time, I was greeted with the error
So there is no recovery partition on my phone currently, but I can still boot to stock recovery
Click to expand...
Click to collapse
This should be in the "Help" forum.
There is no recovery partition.
The boot partition holds the recovery.
tech_head said:
This should be in the "Help" forum.
There is no recovery partition.
The boot partition holds the recovery.
Click to expand...
Click to collapse
My apologies, I thought I had it in that section. Thanks!
Also having trouble ..I can't flash return to stock .no boot partition also .. can flash twrp but from there I'm not sure what to do now .. any help would be great thanks
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
i did that and couldn't boot my phone
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
WOW!!! Really appreciate that!
@Somcom3X life savor, thank you
Djcall11 said:
i did that and couldn't boot my phone
Click to expand...
Click to collapse
If you flash TWRP (twrp-mata_11.img) to the boot partition, that's true. You can only go in recovery. Once you're in TWRP, you need to rewrite the boot image.
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Thanks...this fixed an issue I had as well rolling back to a Beta version.
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
im having this issue. is the <filename>.image you are flashing just the boot.img from the system image zip?
sruel3216 said:
im having this issue. is the <filename>.image you are flashing just the boot.img from the system image zip?
Click to expand...
Click to collapse
Thanks that worked. Rooted on elementalX now!
I did that, but nothing happens
kfhughes said:
If you flash TWRP (twrp-mata_11.img) to the boot partition, that's true. You can only go in recovery. Once your in TWRP, you need to rewrite the boot image.
Click to expand...
Click to collapse
I'm using a Pixel XL 2, so sorry for the post in the wrong forum, but I lucklily found the post so thought to send the query which was already ongoing here. Nothing still happens and Im stuck, it shows the logo of teamwin recovery porject 3.2.3.1 and it's stuck there. I've no clue how to proceed further.
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
alright, so I did this now I can't get back to twrp.. can you help?
Update: I opened a new thread here: https://forum.xda-developers.com/oneplus-6/help/screwed-flashing-twrp-t3846690
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Interesting, I did
Code:
fastboot flash [U][B]boot[/B][/U] stock.img
Sending 'boot__b' (20769 KB) OKAY [ 0.559s]
Writing 'boot__b' FAILED (remote: 'No such partition.')
then did
Code:
fastboot flash [B][U]boot_b[/U][/B] stock.img
Sending 'boot_b' (20769 KB) OKAY [ 0.557s]
Writing 'boot_b' OKAY [ 0.831s]
Any idea why it does the double underscore when not specifying
Code:
__b
....and the single underscore when specifying?
Code:
_b
Very odd behavior. Either way, thanks for the tip!
New Issue after this solution
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
So I did this and it worked to get twrp booted up, but now a new issue has come up. TWRP is stuck on the splash screen, and I can no longer boot up my phone since this overwrote my boot partition. So I ****ed up and tried to unplug and reboot, but when I did that I reset my USB debugging. So now I can't even get to my phone through adb or fastboot. I can boot into the bootloader, but other than that and starting at the TWRP screen I'm stuck. Any Ideas or solutions? I'm hoping I get lucky and TWRP boots up after a while, but so far it's not looking good.
Recovery Done But Not boot in Recovery
Recovery is successfully finished but device not boot in recovery
C:\Users\HitMer\Desktop\one plus 7 pro>fastboot flash boot test-twrp-3.3.1-2-guacamole.img
target reported max download size of 805306368 bytes
sending 'boot' (55976 KB)...
OKAY [ 1.242s]
writing 'boot'...
OKAY [ 0.161s]
finished. total time: 1.412s
C:\Users\HitMer\Desktop\one plus 7 pro>fastboot boot test-twrp-3.3.1-2-guacamole.img
downloading 'boot.img'...
OKAY [ 1.233s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.262s
Somcom3X said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
Click to expand...
Click to collapse
Thanking you in 2019! :laugh::good:
there is a reason guides tell you to use
fastboot getvar current-slot
fastboot set_active other
because the device will flip flop between active slots depending on OTA
if you simply just specify a slot with fastboot flash boot boot_*
you could flash the wrong slot, which is bad
you do not want to overwrite your current active slot with twrp or you won't be-able to boot
once again the steps are
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot yourtwrpimagehere.img
reboot normally it will boot to twrp
then if your touch screen is not working
adb shell
twrp sideload
adb sideload twrp-installerzip
Related
Hello,
So I decided to unlock and root my Pure today. Originally I was going to flash Lineage, but I later decided not to. Anyway, I was following the instructions here.
So I unlocked and installed TWRP succesfully. Then I decided to root. And that's where I screwed up.
Following these instructions, I now have a phone that won't boot past the "M" logo. Apparently my mistake was not using the current SU version.
I have been Googling for an hour now, but almost every solution I've come across has involved plugging the phone into the computer. My issue is that my computer isn't recognizing the phone when I plug it in, so my knowledge of how to fix this is limited (and my expertise in this topic was minimal to begin with...). I can get to recovery mode, and have tried a factory reset. No dice. I also put the latest official factory image from Motorola on the SD card, but when I went to install it, it wouldn't show up.
As you can tell I am quite stuck here. I haven't tried to root a phone since my Incredible back in the day. Any help would be greatly appreciated.
Thanks!
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
jason2678 said:
Did you use TWRP to make a nandroid backup before attempting to root? If so, just restore it.
If not, you're going to have to either fastboot flash it back to stock. More info in the firmware thread.
Or you could give a custom rom, or this TWRP flashable stock rom a try. I've never used the TWRP flashable stock rom, but it might be an easy way out of your predicament if you aren't comfortable and familiar with fastboot and want to stay stock.
For future rooting attempts of the stock rom I'd recommend Magisk. It always works systemless, so there's no need to force it to install systemless like SuperSU. Just flash the zip in recovery and install the Magisk manager from the Play Store and you're rooted. No more soft bricks.
Click to expand...
Click to collapse
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
bootloopohgod said:
Ok, first, thanks for the response.
I think somehow I didn't actually install TWRP. Not sure how.
I followed that thread link and tried everything, but to no avail. Maybe I was doing it wrong? I did this:
- Downloaded everything under "6.0 MPH24.49-18 FIRMWARE"
- Put it on my SD card
- Booted into recovery
- Selected Install from SD Card
And there was nothing listed. I tried the same with the "6.0 MPH24.49-18-3 FIRMWARE".
I also did the "AutoFlashFirmwareScript", but I'm assuming that didn't work since I can't turn on USB Debugging. Is there a possibility I somehow wiped the entire OS and there isn't anything to boot into?
Click to expand...
Click to collapse
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Sagar_1401 said:
okay so you are wrong here..
firmware needs to be flashed via fastboot they are not available in flashable zips they are .xml file.. you need to follow the instructions given here
https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486
or if you want latest firmware of any version of style or pure
download from here
https://firmware.center/firmware/Motorola/
and follow the same instructions given in the first link
hope this helps
Click to expand...
Click to collapse
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
bootloopohgod said:
This definitely seems helpful, but when I tried it gave me a bunch of Failures.
For "fastboot flash partition gpt.bin":
Code:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.382s
And then a Failure for every command from "fastboot flash boot boot.img" to "fastboot flash system system.img_sparsechunk.8" (the build I used doesn't have sparsechunk 9 or else I'd assume that would have been a failure as well). It is encouraging to know I can at least somewhat communicate with the phone, for some reason yesterday I couldn't even do that.
Click to expand...
Click to collapse
ignore that partition error
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem lock
fastboot reboot
make sure
while flashing NON-HLOS.bin you might get error
dont worry
when you reach that step do type it again when you see that error and it'll successful flash the NON-HLOS.bin which is your main step for your modem
im sure this will 100% work
edit: all the files have different no of system system.img_sparsechunk
if you are flashin sept patch it should have 8 i assume but if you just type system system.img_sparsechunk.9 it'll say file not found u won't encounter any error by that
Hi Guys,
I installed Oxygen OS 3.5.8 sometime back. Now i tired to flash TWRP recovery using fastboot commands.
I am able to see my device is detected and also fastboot flash command is success.
Code:
D:\adb-fastboot\platform-tools-latest-windows\platform-tools>fastboot flash reco
very twrp-3.0.2-2-oneplus2.img
target reported max download size of 536870912 bytes
sending 'recovery' (22032 KB)...
OKAY [ 0.804s]
writing 'recovery'...
OKAY [ 1.139s]
finished. total time: 1.943s
But when i reboot to recovery, i am always going to Oxygen Recovery(default) one.
I tried flashing twrp 3.0.2, 3.1.0 as well as 3.1.1.
All having the same result. Am i missing something here ?
Note: i was earlier rooted
Cheers!!!
fastboot erase recovery
fastboot flash recovery twrp-3.0.2-2-oneplus2.img
fastboot boot twrp-3.0.2-2-oneplus2.img
MZO said:
fastboot erase recovery
fastboot flash recovery twrp-3.0.2-2-oneplus2.img
fastboot boot twrp-3.0.2-2-oneplus2.img
Click to expand...
Click to collapse
Wow that was fast and it fixed the issue.. Thanks a ton!!!
MZO said:
fastboot erase recovery
fastboot flash recovery twrp-3.0.2-2-oneplus2.img
fastboot boot twrp-3.0.2-2-oneplus2.img
Click to expand...
Click to collapse
now he can't boot os right?
chxei said:
now he can't boot os right?
Click to expand...
Click to collapse
He can of course. That boot command is temporary
Greetings everyone, I just got a new XT1640. I installed on it the ATHENE_NPJS25.93-14-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ROM from here. Went to motorola's site and unlocked the phone. But I still can't flash TWRP.
this is what happens:
Code:
fastboot flash boot twrp-3.0.2-0-athene.img
target reported max download size of 536870912 bytes
sending 'boot' (12496 KB)...
OKAY [ 0.435s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.186s]
finished. total time: 0.621s
I tried versions 3.1.1, 3.1.0 and 3.0.2 , all from the twrp site. Any ideas?
@yohanleafheart
Why do you want to brick your device ?
Check the command that you are entering, "BOOT" ???? That's "RECOVERY"
write command: fastboot flash recovery xyz.img
(Refer any Recovery or flashing thread)
EDIT:
When you used "fastboot flash boot twrp.img"
you got OKAY at last,
That means you flashed Recovery into Boot/kernel !!
If you face any kernel related problem on startup, then you will need to get original Boot.img and flash it...
Haha hey bro be careful while using commands .. u gonna poision your phone
In addition to ____Mdd's reply about TWRP being flashed to your boot (i.e. kernel!) partition, which isn't good...
The 'Image not signed or corrupt' error is normal because TWRP isn't cryptographically signed, so the bootloader reports as so. Normally, if you see [OKAY], the flash has succeeded (though in your case it's succeeded flashing to the wrong partition...) and you'd boot to recovery to ensure TWRP is not overwritten by the stock recovery (after which you can boot as normal).
If you need a stock kernel, you can pull the boot.img from the stock ROM you have and flash that to the boot partition or find the stock kernels here https://forum.xda-developers.com/showpost.php?p=72378739&postcount=262
Hopefully your device is working!
Gaaaaaaaaah didn't realize I was flashing to the wrong partition. Zomfg.
It didn't brick, i reverted to the stock before booting and relock the bootloader. I don't want the stock, I want to flash loa (did this on my s5 normally)
The problem is that even using the right command, it says that it is not signed, and wglhen I reboot in Dev mode it still won't boot on TWRP. It goes back to fastboot.
Any ideas?
I was on MIUI Global 12.0.2 Stable. I tried to flash Pig's latest Lineage (2020.07.21) from TWRP. The flash failed with an "Error 7". When I tried to reboot, the device went to "fastboot" mode.
After that, every attempt of a reboot ended in fastboot mode. So I tried to flash TWRP.img. Flashing went OK. But "fastboot boot twrp.img" gave the error "FAILED (remote: Failed to load/authenticate boot image: Load Error)". The result was same with "fastboot oem reboot-recovery" command.
So I was stuck in fastboot mode with the risk of battery depletion. Below is the commands I ran to flash the TWRP.
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 805306368 bytes
sending 'recovery' (65536 KB)...
OKAY [ 2.016s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 2.179s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 2.016s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.046s
C:\adb>
Click to expand...
Click to collapse
SOLUTION: One needs to flash the fastboot ROM in MiFlash.
My situation had an extra issue as there were no fastboot ROM for MIUI Global 12.0.2. So, I downloaded MIUI 11.0.5 Global Fastboot ROM and flashed it. One needs to keep in mind about the "Anti-Rollback Protection" (https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/) and take necessary steps to avoid an anti-rollback brick.
If anti-rollback compatible ROM not available, then just delete first lines in all .bat files (.bat for Windows; .sh for Linux) up to the first line that starts with "fastboot %* getvar product..." of the available fastboot ROM. Those lines are the anti-rollback check. After than you can flash it via MiFlash.
Stillness said:
So I try to flash TWRP.img. Flashing goes OK. But "fastboot boot twrp.img" gives this error "FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Thanks for the reply. I tried that command too, but ended with the same error.
Now, downloading the 11.0.5 Global Fastboot ROM since no 12.0.2 Fastboot available. My plan is to just delete first lines in .bat files of the ROM to avoid 'rollback protection' and flash via MiFlash before the battery goes zero. According to google, it seems flashing the full Fastboot ROM is the only solution
SOLVED
Solved. Edited the OP.
zgfg said:
There is a Fastboot command to reboot to recovery (TWRP if you previously flashed it):
>> fastboot oem reboot-recovery
Click to expand...
Click to collapse
Wow, thank you so much for pointing this out!
I just had a close to two hour journey through all emotions after trying to restart my phone and suddenly ending up in a seemingly inescapable fastboot hell...
I've tried booting different recoveries, all failing with
Code:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
and was already at the point of giving up getting my system back, just trying to save my data if possible. Flashing seemed to work, but
Code:
fastboot reboot recovery
just threw me back into fastboot, which I assumed to be due to the phone rejecting the flashed recoveries just as it was rejecting them when I tried to boot them directly.
When I saw this comment I wondered whether Xiaomi implemented rebooting directly to the recovery differently (as it turns out, it doesn't seem to be standardized) and
Code:
fastboot oem reboot-recovery
worked perfectly! After reflashing my ROM from TWRP I was booted back up into my system with everything intact, as if nothing has happened.
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')