Hi, I try to flash a new boot.img, and it's printed the message Partition table doesn't exit.
Anyone have a solution for this.
Now, my mobile have a infinite bootloop
Thanks
Which boot.img did you try to flash?
cafernan said:
Hi, I try to flash a new boot.img, and it's printed the message Partition table doesn't exit.
Anyone have a solution for this.
Now, my mobile have a infinite bootloop
Thanks
Click to expand...
Click to collapse
Also show which command exactly did you use. "Partition table doesn't exist" error is shown when you try to flash partition which..doesn't exist - usually a typo in command. Also there are some "fake" Mi A1 being sold (Mi 5x with A1 ROM), verify that you have really A1 here https://www.mi.com/verify/#imei_en
Hey man Mi A1 has dual partition. You have to specify which partition you are flashing.
fastboot flash boot_a boot.img
(boot_a or boot_b depending upon your current slot)
mearjunsha said:
Hey man Mi A1 has dual partition. You have to specify which partition you are flashing.
fastboot flash boot_a boot.img
(boot_a or boot_b depending upon your current slot)
Click to expand...
Click to collapse
I was getting that error trying to flash my own personal backed up boot.img. I was using the
Code:
fastboot flash boot_a boot.img
command as well as trying slot b.
I got jack of it and just used MiFlash and flashed the rom without overwriting storage. Problem solved.
ludditefornow said:
I was getting that error trying to flash my own personal backed up boot.img. I was using the
Code:
fastboot flash boot_a boot.img
command as well as trying slot b.
I got jack of it and just used MiFlash and flashed the rom without overwriting storage. Problem solved.
Click to expand...
Click to collapse
thanks, problem solved
Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?
juby2 said:
Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?
Click to expand...
Click to collapse
wait for this answer too,
juby2 said:
Need help also, where do you fill in code (fastboot flash boot_a boot.img)?
Can someone explain the given answer above with the two partition?
Click to expand...
Click to collapse
What do mean, adb&fastboot ? You need it if you don't
want to flash with miflash or twrp.
https://forum.xda-developers.com/showthread.php?t=2317790
The mi a1 has two partition a and b, if you want to flash separately, but you don't have to or what is your question exactly ?
Edit: on one partition a or b you use your current system, the other one is for updating in the background like ota update.
I have custom ROM installed but after using OTA update i lost TWRP, now i have to flash it to certain partition A or B.
How do i know to which partition to flash it, A or B and how to check for that ???
i have that type of problem too
when i write fastboot system system.img it says
C:\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/38 (131056 KB) OKAY [ 5.453s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
godsavesmeeverytime said:
i have that type of problem too
when i write fastboot system system.img it says
C:\platform-tools>fastboot flash system system.img
Sending sparse 'system' 1/38 (131056 KB) OKAY [ 5.453s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Click to expand...
Click to collapse
Did you figure out how to solve it?
Zato83 said:
Did you figure out how to solve it?
Click to expand...
Click to collapse
no but i did recovered my phone using spflash you can do it too
godsavesmeeverytime said:
no but i did recovered my phone using spflash you can do it too
Click to expand...
Click to collapse
hell yeah hahahaha I get recover it back, but my goal gonna figure out how Install TWRP on my phone, thank for reply
wh
Zato83 said:
hell yeah hahahaha I get recover it back, but my goal gonna figure out how Install TWRP on my phone, thank for reply
Click to expand...
Click to collapse
hey where I can get the scatter-loading file for mi a1
Related
First of all, I would like to apologize if this question has been answered in another thread. I have searched the xda forums and others with no success.
My situation is the following:
Running on Windows 8.1
1. Rooted Nexus 4 on 4.4 (if I remember correctly)
2. OTA update to 4.4.2 (loosing root, but device remains unlocked) (I think I also tried flashing the factory image manually, but failed, I don't remember exactly)
I rooted my phone when Kitkat was fresh and found there were no custom roms on 4.4 yet so I went back to stock because it was the easiest way to get the update. Right now I can not flash a custom recovery.
fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
===================================================
fastboot flash recovery.img
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
This is the same for both TWRP and CWM. I am very sure I did NOT misspell the name.
Does anyone have any idea why this is happening and how to fix it?
Thank you for taking the time to read this post!
You have to use this
fastboot flash recovery recovery.img
wrong syntax, must be: fastboot flash recovery recovery.img
Wow.... I am ashamed with myself. I cannot believing I missed that.
Thank you for the quick reply guys.
I was just doing the same here thanks!
command doesnt work for me
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
FastSl0th said:
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
In the xda forum, check carefully whether you are asking a question in the appropriate Q&A section for your device, because you are certainly not writing about Nexus 4.
.
FastSl0th said:
command doesnt work for me
I've tried to use that command but this is all i get after:
Sending 'recovery' (22432 KB) OKAY [ 0.579s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Is there that is wrong and that i may need to fix?
Click to expand...
Click to collapse
Hopefully you may have already asked or solved this question. I am assuming you are issuing command from platform-tools folder. If you have a Windows 10 OS system then, I too could not found USB drivers for my system with windows 10. If 'fastboot devices' command returning some device id then maybe I have guessed wrong reason.
I entered "fastboot flash XXX.img" Too. hahaha
After i see this article, I entered "fastboot flash recovery flash XXX.img"
Thank you anyway.
unsolved
dan60 said:
unsolved
Click to expand...
Click to collapse
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How To Solve This Problem Brother..Please Tell me
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
d4_daman_ said:
fastboot: error: cannot determine image filename for 'bootC:\Android Development\platform-tools\magisk_patched-24300_NP5BG.img' How to Solve This Problem Brother...Please Tell Me
Click to expand...
Click to collapse
Hi there!
It didn't work for me but you can try it >>>
jd1639 said:
You have to use this
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Hi guys, I found the same error when I've tried to install TWRP on mi Xiaomi Mi A3 by FASTBOOT on Linux Terminal.
After a lot of searching, I solved my problem using the syntax below:
"fastboot flash boot XXX.img"
"boot" is the partition about FASTBOOT are asking for.
Hope to be usefull.
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
Hello!
So I've bricked my phone as said... I will tell you what works and what don't, I need that phone, so please help, I've looked throug whole XDA, but whole XDA and no solution for my phone...
So, when trying to boot into system, not even boot works, it just stays at screen "device is unlocked and it cannot be trusted"
Only my fastboot works and force update(clicking up volume button when booting)
TWRP or stock recovery DOESN'T work, tried probably everything, when trying to boot into recovery, it just stays at screen "device is unlocked and it cannot be trusted"
So basicaly, what I have is: fastboot, force update, which btw, tried to install stock rom by huawei (http://consumer.huawei.com/et-en/support/downloads/detail/index.htm?id=91329) - C185B130 Android 6.0 - But it says: "Software install failed! Incompatibility with current version. Please download the correct update package."
BTW, Huawei P9 Lite VNS-21 Single Sim
I would appreciate any help sooooo much! If it's possible, stock rom, or CM13 work fine to, all I need is just this phone to work, to call, sms, camera... Thats all, thank
Please respond quickly, I need help ASAP, because ofcourse I need that phone quick
Thanks
Fastboot flash system, boot.img, and recovery?
StrangerWeather said:
Fastboot flash system, boot.img, and recovery?
Click to expand...
Click to collapse
Didn't tried system, boot and recovery did it, but CUST didn't work, I think it said that cant find partition
Is it possible to get back to TWRP? Because right now, when I flash, it doesn't work at all?
b0xgam1ng said:
Didn't tried system, boot and recovery did it, but CUST didn't work, I think it said that cant find partition
Is it possible to get back to TWRP? Because right now, when I flash, it doesn't work at all?
Click to expand...
Click to collapse
Did you flash TWRP again?
fastboot erase recovery
fastboot flash recovery recovery.img
Alternatively:
fastboot erase boot
fastboot erase system
fastboot erase userdata <-- this will wipe /sdcard
fastboot erase recovery
fastboot erase cache
Then :
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
StrangerWeather said:
Did you flash TWRP again?
fastboot erase recovery
fastboot flash recovery recovery.img
Alternatively:
fastboot erase boot
fastboot erase system
fastboot erase userdata <-- this will wipe /sdcard
fastboot erase recovery
fastboot erase cache
Then :
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I started with erasing recovery and it said "remote: Command not allower"
Bootloader IS unlocked btw
b0xgam1ng said:
I started with erasing recovery and it said "remote: Command not allower"
Bootloader IS unlocked btw
Click to expand...
Click to collapse
and if you flash it?
StrangerWeather said:
and if you flash it?
Click to expand...
Click to collapse
flashing works, just didn't tried system yet, still extracting it from update.app, it will be done soon, probably when you respond
b0xgam1ng said:
flashing works, just didn't tried system yet, still extracting it from update.app, it will be done soon, probably when you respond
Click to expand...
Click to collapse
ok, let's see!
StrangerWeather said:
ok, let's see!
Click to expand...
Click to collapse
OMG, I hate my life
fastboot flash system system.img
FAILED (remote: sparse flash write failure)
What to do now? Please help
b0xgam1ng said:
OMG, I hate my life
fastboot flash system system.img
FAILED (remote: sparse flash write failure)
What to do now? Please help
Click to expand...
Click to collapse
Try fastboot -w
And try flashing again.
StrangerWeather said:
Try fastboot -w
And try flashing again.
Click to expand...
Click to collapse
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.011s
Still no luck with flashing system.img
What does that mean?
b0xgam1ng said:
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.011s
Still no luck with flashing system.img
What does that mean?
Click to expand...
Click to collapse
Your partitions are messed up. I'm not sure there is a lot that can be done. Can you get into stock recovery?
StrangerWeather said:
Your partitions are messed up. I'm not sure there is a lot that can be done. Can you get into stock recovery?
Edit: what happens if you flash system now?
Click to expand...
Click to collapse
Well, if it helps, I can flash "revolutionary recovery" and it works, but problem is, because it's made for Android 7.0 and it cannot mount /data, but it works...
Reply on edit: Still the same
b0xgam1ng said:
Well, if it helps, I can flash "revolutionary recovery" and it works, but problem is, because it's made for Android 7.0 and it cannot mount /data, but it works...
Reply on edit: Still the same
Click to expand...
Click to collapse
Ok, then try wiping everything with "revolutionary recovery". Then try fastboot flashing again.
StrangerWeather said:
Ok, then try wiping everything with "revolutionary recovery". Then try fastboot flashing again.
Click to expand...
Click to collapse
I also have some terminal in this recovery, if it helps
Is there any way that phone can be fixed? Please
b0xgam1ng said:
I also have some terminal in this recovery, if it helps
Is there any way that phone can be fixed? Please
Click to expand...
Click to collapse
You have a recovery so I believe that's good news. Try to google your way out of this.
Maybe flash Nougat if the Nougat recovery works.
StrangerWeather said:
You have a recovery so I believe that's good news. Try to google your way out of this.
Maybe flash Nougat if the Nougat recovery works.
Click to expand...
Click to collapse
I don't think there is anything, as much as I googled..
Can you try finding any rom for my phone?
Huawei P9 Lite VNS-L21 Single Sim
Thanks
b0xgam1ng said:
I don't think there is anything, as much as I googled..
Can you try finding any rom for my phone?
Huawei P9 Lite VNS-L21 Single Sim
Thanks
Click to expand...
Click to collapse
Have you tried Lineage OS 14?
https://forum.xda-developers.com/hu...-lineageos-14-1-huawei-p9-lite-honor-t3545370
StrangerWeather said:
Have you tried Lineage OS 14?
https://forum.xda-developers.com/hu...-lineageos-14-1-huawei-p9-lite-honor-t3545370
Click to expand...
Click to collapse
That's 7.0 android? Ok, wait, I'll try
Thanks
StrangerWeather said:
Have you tried Lineage OS 14?
https://forum.xda-developers.com/hu...-lineageos-14-1-huawei-p9-lite-honor-t3545370
Click to expand...
Click to collapse
It says
"Failed to mount '/data' (Invalid argument)"
"Failed to mount '/system' (Invalid argument)"
Can I recreate those to partitions or something? Thanks
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
I bought a new Moto G6 Plus XT1926. My goal is to install a twrp image as recovery and then next the lineage.
I got a weird issue when trying to flash "twrp-3.2.1-37-evert.img" on my 1926 by using "./fastboot flash recovery twrp-3.2.1-37-evert.img" on a mac console. The output is:
XT1926 myMac$ ./fastboot flash recovery recovery.img
sending 'recovery' (29440 KB)...
OKAY [ 0.630s]
writing 'recovery'..
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.634s
Just before I unlocked the Bootloader. I tried:
1. Locking bootloader again and flash => nope
2. Restoring the partition table by the following commands:
./fastboot oem fb_mode_set
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
./fastboot flash logo logo.bin
./fastboot flash boot boot.img
Does anyone know why the partition "recovery" may be not present and how to make it flashable?
I flashed a XT1039 multiple times without issues, so I got some experiences. But i am out of ideas here.
How can it be that there simple is no recover on the phone I wonder.
Also I downloaded the "TWRP official" App and installed it within the Moto G stock rom and it also says that it can not locate the recovery.
I tried some stuff for two evenings and now i do not know how to continue...
Thanks for hints!
The Recovery is inside the boot, that's why the G6Plus don't have an official TWRP.
The ones we have are the bootable one with decryption enabled, or a flashable one with no decryption
So instead of flashing the TWRP to the recovery partition, I should flash it to the boot partition?
kietob said:
So instead of flashing the TWRP to the recovery partition, I should flash it to the boot partition?
Click to expand...
Click to collapse
No. Do not flash it at all! Load bootloader on your phone, from a pc with a fb and fastboot on it, run "fastboot boot twrp.img" without quotes and twrp.img matches the filename of the twrp IMG file. At this time we can not install twrp to our device. We can only boot it on our device using a pc every single time you need twrp. There was a twrp.img for our device we could flash with fastboot to install on our device but it does not properly flash files sadly. We are trying to raise funds to buy a device for a recognized developer in hopes of making some real progress on modding this device! Look around the G6 forums here and find the thread if you are able to make a PayPal donation or would like to see if you could donate in another way.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
No. Do not flash it at all! Load bootloader on your phone, from a pc with a fb and fastboot on it, run "fastboot boot twrp.img" without quotes and twrp.img matches the filename of the twrp IMG file. At this time we can not install twrp to our device. We can only boot it on our device using a pc every single time you need twrp. There was a twrp.img for our device we could flash with fastboot to install on our device but it does not properly flash files sadly. We are trying to raise funds to buy a device for a recognized developer in hopes of making some real progress on modding this device! Look around the G6 forums here and find the thread if you are able to make a PayPal donation or would like to see if you could donate in another way.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
Hey, any news about flashable TWRP? How can I donate someone who would work on it?
rafikowy said:
Hey, any news about flashable TWRP? How can I donate someone who would work on it?
Click to expand...
Click to collapse
Sadly no news. We have official TWRP now which is good. I'll talk to the devs and try to figure out if it's worth getting a pool started.
Sent from my Moto G6 Plus using XDA Labs