when i try to flash twrp img, its showing "partition table doesn't exist"
what to do???
What version of Android are you using?
What boot.img version of TWRP are you using?
Why are you trying to flash TWRP when every guideline, help and snippet of info for TWRP on this phone states specifically to not flash it?
You only boot into TWRP using the fastboot boot *.IMG command as far as I am aware.
Related
I used the WonderHowTo site incorrectly to flash a nexus 5 version of twrp unto my nexus 4.
My device at this point booted to a blank screen. It could still boot the boot loader at this point.
To "fix" this I found the correct version of twrp for my device and proceeded to flash that unto my device.
This has appeared to work since I can access twrp on my device but it is only thing I can access on the phone. When I attempt to boot to system through twrp I am sent back into twrp.
I have attempted to use the wugfresh root tool kit to unroot and return to stock using both soft bricked and phone is still working normally options with no success.
It can still boot to the boot loader currently.
I have logs from the toolkit if these can shed more light on my issue.
Is there anyway I can return my device to stock? Thanks for any response
Flash factory image
https://developers.google.com/android/nexus/images#occam
attempted
attempted to flash stock and got the following error message
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
codebam said:
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
Click to expand...
Click to collapse
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
MrTalk said:
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
Click to expand...
Click to collapse
Okay adb push a cyanogenmod zip from here and flash it in recovery. It should automatically install a working boot image. You should also flash the latest bootloader in the factory image with "fastboot flash bootloader bootloader.img" if you're using an outdated bootloader.
used the advice
I pushed the zip file using cmd and it appears to have been successful since I was given the summary of data transferred and how long it took once the process was finished.
I can't find the zip file in twrp to attempt to flash it.. Is there any reason the file name would change inside the device once it has been pushed?
Is there a way to flash the zip in question without pushing it unto the device?
When I try to flash TWRP (via "fastboot flash recovery twrp.img" then "fastboot boot twrp.img") I receive the following error:
Downloading 'boot.img'
OKAY [1.477s]
booting...
FAILED (remote: dtb not found)
finished. total time: 1.534s
I've tried manually booting it into recovery with power button and volume down but it just freezes on the oneplus logo where I have to turn off and on again.
Any help is greatly appreciated!
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
that link just saved me!
I tried this recovery (I had the same problem as the OP) but although I can boot into twrp, I get stuck on the oneplus logo if I try a normal boot?
Sent from my Nexus 9 using XDA-Developers mobile app
I managed to get it working by flashing CM after flashing the recovery.
Sent from my Nexus 9 using XDA-Developers mobile app
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
pitrus- said:
Next time, correct command is the following:
Fastboot flash recovery twrp.img
You tried to flash the recovery image onto the kernel/boot partition, luckily it doesn't allow this, unless it's an actual kernel image fitting that partition. ?
Click to expand...
Click to collapse
Actually, fastboot boot twrp.img boots the TWRP image without flashing it.
fastboot flash recovery twrp.img flashes the TWRP image to the recovery partition.
Both are valid commands and have their uses.
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Spannaa said:
fastboot flash boot twrp.img would be the command to try to flash the recovery image to the boot partition and shouldn't be used.
Click to expand...
Click to collapse
That's exactly what I meant to convey.
Similar problem while flashing recovery
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
bhanuodin said:
hi,
After OOS3.0 installation my OP2`s recovery is not working. i tried installing it again and it shows the error :
FAILED <data Transfer failure <unknown error>>
Please help
Click to expand...
Click to collapse
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
pitrus- said:
Are you sure you flashed the correct OOS3 bootloader compatible version of TWRP? Latest official 3.0.0-2 should be compatible.
Click to expand...
Click to collapse
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
bhanuodin said:
how do i flash a bootloader? problem is that i am unable to flash/write on recovery partition. every time it gives the same error mentioned above.
Click to expand...
Click to collapse
The bootloader (also called fastboot) comes with the original ROM. In your case you're already on the newer bootloader since you flashed OOS3 which means you will have to flash recoverys and ROMs compatible with this newer bootloader.
This TWRP should be compatible
https://dl.twrp.me/oneplus2/twrp-3.0.2-1-oneplus2.img.html
Also you can't run ROMs not compatible with this newer bootloader (which means pretty much any ROM that's not using the official Cyanogenmod source tree for building). That is except for OOS3 or newest HOS of course since these are made for the newer bootloader.
However I would say the error message you get might be caused by bad cable, faulty driver setup, faulty fastboot tool version or in worst case damaged partition layout on phone. The last one can be fixed by the Qualcomm OOS2 factory restore solution.
Hi, i am having the same problem.
some background: I was on Oxygen OS 2.x.x, i wanted to upgrade to Exodus 6. I had the older version of TWRP. So I tryed to install the new twrp image within twrp. When i rebooted i couldnt boot into twrp, receiving the same error message as in OP title, when using fastboot.
Using the tool all in one toolkit I was able to flash stock recovery.
But I still cant flash Twrp.
I can still boot into system though.
Any advice? Thanks.
That explains why you're having problems. You're doing it the wrong way.
First you must upgrade the bootloader by either flashing the convert to Marshmallow zip file which also installs the correct TWRP for the new bootloader (easiest way). Or you could flash the latest official OOS3, then fastboot flash the latest TWRP and from there format system and flash the ROM that's using the newer bootloader.
Does that Link work with oneplus x also? Having same problem as Higgings when trying to install twrp and cyanogenmod.
thnx a lot for sharing
:good:
Higgings said:
I found the solution.
For anyone else with this problem
http://forum.xda-developers.com/showpost.php?p=66336492&postcount=3
Click to expand...
Click to collapse
Hi there.
I'm trying to update my phone to Oreo January patch, I'm currently with December patch that is such bugged. Well as I read I have to download the update and before installing it I have to uninstall Magisk restoring the boot image and then after the update installing the boot image of Magisk again, I tried to flash the ROM with MiFlash saving the user data to solve it, and I did it but all my data just gone I don't know why, well the thing is that I updated, I thought, and then I flashed the patched boot image of Magisk in fastboot mode, and there is where I missed the boot image and I lost the update maybe...
Is there an option to flash JUST the boot image and not all the ROM or put the stock boot image just into a Magisk folder to have it?
If you install magisk using magisk manager, it will backup your original boot image and when you uninstall magisk, it will restore your boot image.
If you want to manually flash your boot image, you can do that in fastboot mode.
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
You can get your stock boot image from the rom files that you used in MiFlash tool. (boot image is inside that rom folder/zip file)
In miflash, you need to make sure you select the"save user data" option in the lower right corner. The file it will use is the "flash all except storage" file. Then, don't flash magisk. Update, them worry about rooting.
RavinduSha said:
If you install magisk using magisk manager, it will backup your original boot image and when you uninstall magisk, it will restore your boot image.
If you want to manually flash your boot image, you can do that in fastboot mode.
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
You can get your stock boot image from the rom files that you used in MiFlash tool. (boot image is inside that rom folder/zip file)
Click to expand...
Click to collapse
Hey, thanks for your answer, I manually flashed my boot image to update my phone to January Update but it didn't work, when I try to install the update it says "Couldn't install the update, try again later"
Any idea to solve this?
Hey, I need to flash a persist.img file, because my phon restarts every 2 Minutes and does not find any WiFi, but it gives me out the error: remote:Error : persist partition not allowed download. Is there a way to flash it without twrp, since when I try to flash a custom recovery, it says partition table not found. Is there a way to flash persist.img in Mi Flash Tool?
use the link given below
it will help you
https://forum.xda-developers.com/showpost.php?p=75782887&postcount=2
raaz1431994 said:
use the link given below
it will help you
https://forum.xda-developers.com/showpost.php?p=75782887&postcount=2
Click to expand...
Click to collapse
Don't have Twrp, can't flash custom recovery, it says partition table does not exist
boot to fastboot and
give the command
fastboot boot twrp.img
instead of fastboot flash recovery twrp.img
Hey guys,
I tried flashing TWRP to recovery partition, but I get: FAILED: remote: partition table doesn't exist. I could only boot to TWRP by flashing it into the boot_a partition, flashing everythong I need and then replacing boot_a from twrp.img back to stock boot.img. I could flash Magisk, but when I rebbot it to system, it just stays on the android one screen and I have to use flash_all script to restore it. My Mi A1 has Android 8 Oreo. please help.
Have you solved? if you've solved how did you do? thank
You need to use the correct twrp boot image and twrp installer zip file. Go to mohancm's twrp thread and download the correct files according to your android version.
cicciobaciccio said:
Have you solved? if you've solved how did you do? thank
Click to expand...
Click to collapse
Most probably by following one of the available guides Mi A1 doesn't have recovery partition for example.