hi
yesterday i tried to flash the latest LineageOS rom on my Mi pad 1
i booted into fastboot, erased everything and tried a command "Fastboot flash rom xxxx.zip"
and there i got the error FAILED (remote: Invalid Partition Name.)
anyone know what to do? it's two years since i worked in adb/fastboot and i cant remember :crying: :crying:
i have also tried to boot into CWM and 2 versions of TWRP - witch only the latest TWRP started and "froze" on boot(?) the totch did not work and the tablet rebooted after a while
Related
I tried flashing Kitkat from 4.3 using the Minimal ADB and Fastboot method and after rebooting, my phone didn't start and is stuck in recovery mode, not the CWM i had previously installed, just the default Android system Recovery, tried wiping everything but no success.
I have x1032 with 4.3 rooted and bootloader unlocked, also CWM installed now i don't know what to do, please help, how do i make my phone functional again?
thanks
edit: i can boot fastboot mode too but none of the options work, tried reflashing KitKat with the same method and this is what i've found
when i put ''mfastboot.exe flash partition gpt.bin ''
it says
''(bootloader) preflash validation failed
FAILED (remote failure)''
and the phone says ''version downgraded for primary_gpt''
then i get these error while putting the other commands
''hab check failed for boot''
''hab check failed for recovery''
''hab check failed for system''
''Invalid PIV signed system image''
Check the forum, it's all there.
Hey guys. Today I tried to update my Moto G XT1039 EU version from CM12.1 to CM13. Firstly I tried to update my recovery... after some time i made it with problems. To open recovery i had to use command "fastboot boot recovery.img" and then it opened (I occured Boot up failed problem). Once I made it i went straing to erase any necessary data and I tried to install newest ROM which is CM13 and new gapps file. CM13 installed properly but gapps didnt. But i tried to turn on phone and see if it works anyway. Well... since then now i cant turn on phone becasue the only thing works is fastboot flash mode. I cant install any recovery file becasue i have Boot up fail problem, yet i cant open it via command prompt because Failed (Remote Failure). When i type "fastboot devices" my PC sees it. My bootloader version is 41.1A.
Is there any chance i can have that CM13 installed properly or at least to have it working at all?
Hello.
What I did:
I was using TugaPower 32 and unfortunately decided to install this rom https://forum.xda-developers.com/showthread.php?t=3497300.
Installation was successful but rom won't start properly so I did a full wipe and tried to install last version of TugaPower, when Error 7 occurred.
I've thought that Error 7 means that i'm using old recovery, so I made an attempt to install the lastest version of TWRP through fastboot.
Installation was successful but now I'm not able to boot into recovery at all, tried philz and twrp recovery.
So what do I have now:
No Rom installed
Completely working fastboot
No working recovery.
Really need your help guys!
P.S. When trying to made fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 0.300s]
booting... FAILED (remote: dtb not found)
finished. total time: 0.331s
EDIT: flashed original firmware with fastboot, lost all data but everything works perfect.
AlexOPS said:
Hello.
What I did:
I was using TugaPower 32 and unfortunately decided to install this rom https://forum.xda-developers.com/showthread.php?t=3497300.
Installation was successful but rom won't start properly so I did a full wipe and tried to install last version of TugaPower, when Error 7 occurred.
I've thought that Error 7 means that i'm using old recovery, so I made an attempt to install the lastest version of TWRP through fastboot.
Installation was successful but now I'm not able to boot into recovery at all, tried philz and twrp recovery.
So what do I have now:
No Rom installed
Completely working fastboot
No working recovery.
Really need your help guys!
P.S. When trying to made fastboot boot recovery.img
downloading 'boot.img'... OKAY [ 0.300s]
booting... FAILED (remote: dtb not found)
finished. total time: 0.331s
EDIT: flashed original firmware with fastboot, lost all data but everything works perfect.
Click to expand...
Click to collapse
Now that you're on stock Cos13.1,try to flash the OOs rom with TWRP 3.1.0
AlexOPS said:
EDIT: flashed original firmware with fastboot, lost all data but everything works perfect.
Click to expand...
Click to collapse
Hi,
I have the very same issue (also got error 7 and tried to update twrp)
Can you please link where you found the original firmware and the fastboot command to flash it?
EDIT:
fastboot flash zip firmware.zip
I can;t post the link to the original firmware, but a short google search should help
Thanks a lot!
obatzer said:
Hi,
I have the very same issue (also got error 7 and tried to update twrp)
Can you please link where you found the original firmware and the fastboot command to flash it?
Thanks a lot!
Click to expand...
Click to collapse
Here you go
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
HI I AM FACING THIS ERROR
While trying to flash recovery
It is showing "FAILED (remote: partition[recovery] doesn't exist)
please help???
sunny000140 said:
HI I AM FACING THIS ERROR
While trying to flash recovery
It is showing "FAILED (remote: partition[recovery] doesn't exist)
Click to expand...
Click to collapse
Pixel has a new partition layout, there is no recovery partition, everything now happens on the boot.img
So if you're trying to flash twrp you have to "fastboot boot x.img" and then flash the recovery zip once booted to the temporary recovery.
Hope this helps
Dear community. I screwed up.
I purchased my new OP7P and in all my excitement, logically, the first thing I went to do was to unlock the bootloader, install TWRP and root it, which I did successfully because I am pretty familiar with this on multiple phones. Long story short, here's what I did, and where my problem lies:
1. Went to install the Havoc Custom ROM by following their installation instructions, went ahead and booted to TWRP recovery
2. As instructed, wiped dalvik and /data
3. Flashed Havoc ROM and here is the part where I was supposed to flash TWRP installer
4. Forgot to reflash TWRP installer and rebooted to the now nonexisting recovery. - getting the dead android icon with the message "NO COMMAND"
5. After holding VOLUP + POWER managed to turn it off and then turn it on again with just POWER to be greeted with a message warning me that I am in a bootloop
and that I have two options; to try again or to "reset to factory settings", which I did, which booted me into the HavocOS.
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
I have tried this on both Linux & Windows, same deal. The TWRP website has mentioned that if this happens I need root, but how do I root my phone without TWRP or "fastboot boot", and how do I install TWRP on the OP7P without livebooting TWRP?
Any help at all is truly appreciated. Thanks guys.
Download the MSM tool here and restore your phone. I've never used it but it gets everyone out of a brick.
I've used this tool a few times and it has gotten me out of a jam, just be sure to download the correct version for your phone. AFA your fastboot error, I got that until I let the OTA update to 9.5.11, then it worked again. https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862
x3lade said:
The main problem here is that for some reason whenever I try to repeat the TWRP installation process using fastboot, by entering "fastboot boot twrp.img", it gives me the following error:
downloading 'boot.img'...
OKAY [ 1.340s]
booting...
FAILED (remote: unknown command)
finished. total time: 1.343s
Click to expand...
Click to collapse
Try to fastboot boot the TWRP build -70 from here: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
It fixes the problem with "fastboot boot" not working on the official Android Q update. Not sure why that would apply to your case (custom ROM after already successfully installing TWRP). But it's very easy to try, and certainly can't hurt. And the error message you are getting is exactly the same as the official Android Q problem.