Hello everyone
So, after lurking in this forum for quite a while, I finally decided to install a custom ROM for the first time today. In the beginning, everything went fine, I installed all the necessary tools and unlocked the bootloader following the guides on this sub. I then booted into the official TWRP (fastboot boot twrp-3.3.0.0-ali.img) to backup the stock boot and recovery images (as described in https://forum.xda-developers.com/moto-g6/how-to/guide-twrp-root-magisk-installation-t3816569).
The issue happened when I tried to flash TWRP from fastboot mode (fastboot flash recovery twrp-3.3.0.0-ali.img). It didn't work and returned the error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
Does anyone know what might have happened and how it can be fixed?
Some additional things I tried after that:
- I can still boot directly into TWRP (both djellos and the official image)
- I tried flashing the stock recovery, which seems to work, but I can't boot into it afterwards (no command).
- I can still boot android, but when starting, it gives me a warning that the phone is unlocked with ID = BAD_KEY. I don't know if this is normal.
Some additional info:
- I'm running Manjaro Linux on my PC with android-tools updated to the latest version.
- My phone is the XT1925-5 33GB PVT1 variant
Any help is greatly appreciated, thanks for your time
Alright, I'm stupid. Using the latest twrp verison (3.3.1) it worked.
Related
Hi guys,
I am planning to return to Stock 5.1 on my phone, after running CM 13.
So I upgraded from 4.4 to 5.1 my manually flashing the zip in recover.(XT1053_GHOST_TMO-RETAIL_5.1_LPA23.12-15.5_cid9_CFC.xml.zip would be the file from https://firmware.center/firmware/Motorola/Moto X (1st gen-2013)/Stock/XT1053 T-Mobile/)
From there I moved on to CM 12 and then CM 13.
Device version is XT1053.
Been facing issues with bluetooth devices and planning to get back to stock 5.1
So I tried manually(mfastboot) flashing components (boot, recovery and system). Boot and recovery went fine, but system gave me(similar) error.
load_file: could not allocate 829072920 bytes
error: cannot load 'system.img': Not enough space
Referred to this tutorial, http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
and tried the manually method wherein I ran these 2 commands :
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
Threw some error(forgot to note them down) :|
Anyway, nothing work post that.
Tried rebooting, got the "no command" screen.
Eventually flashed TWRP and installed CM13 again from zip and got the phone booted up.
Running fine, but still can't to get back to stock!
Tried RSDLite method from the tutorial above, but RSD doesn't detect my phone on connecting.
adb devices command does list the phone.
Can someone please point me in the right direction ?
btw, noticed something weird after failed partition flash.
Whenever I mfastboot recovery/boot it throws an error unknown command 'recovery' (or boot), but flashes fine.
Is this normal ?
Regards,
Neel Indap
Phone oneplus3t, 64GB model EU
Oxygen OS 3.5.4
Android 6.0.1
Bootloader: unlocked
Im having problems with flashing/booting TWRP
It flasheh succsesfully, but it doesnt boot. This is the error i get in the comand prompt: Boot twrp: failed (remote: dtb not found).
I tried flashing it via oneplus3t "all in one tool" and i tried it with downloading only the TWRP.img and flashing it in comnad prompt myselfe. Always the same problem. I also tried a modified TWRP which i found on the thred here somewhere: same problem.
It flashes, but doesnt "open" or boot. Right after I flash it if i click "recovery" it just goes back to the fastboot menu where i started.
I also tried this before i updated it on the oxygen 3.5.4
Please help, Thanks
Did you use the specific twrp recovery for the 3T? This one: https://dl.twrp.me/oneplus3t/
And did you follow a guide. This one for instance: https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
jann32 said:
Phone oneplus3t, 64GB model EU
Oxygen OS 3.5.4
Android 6.0.1
Bootloader: unlocked
Im having problems with flashing/booting TWRP
It flasheh succsesfully, but it doesnt boot. This is the error i get in the comand prompt: Boot twrp: failed (remote: dtb not found).
I tried flashing it via oneplus3t "all in one tool" and i tried it with downloading only the TWRP.img and flashing it in comnad prompt myselfe. Always the same problem. I also tried a modified TWRP which i found on the thred here somewhere: same problem.
It flashes, but doesnt "open" or boot. Right after I flash it if i click "recovery" it just goes back to the fastboot menu where i started.
I also tried this before i updated it on the oxygen 3.5.4
Please help, Thanks
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=kTdKmceC5xU watch this video
Hi there,
a friend asked me for help with restoring his german Moto G 2014 (XT1068). The last working software on the device was the Marshmallow update. He was having software issues and softbricked the device when trying to install a custom ROM.
Fastboot mode and stock recovery is accesible, the bootloader is unlocked and the device is stuck on the "WARNING: BOOTLOADER UNLOCKED" screen when trying to boot normally.
I have tried following this guide to revert the phone back to stock firmware with a matching system image. Both the XT1068_TITAN_RETDE_6.0_MPB24.65-34-3_cid7_CFC and XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC images will flash without any error messages. However, the device does not boot the new software. Also, when trying to relock the bootloader, the mfastboot oem lock command failes with the error message Not supported command in current status!. I tried to substitute mfastboot with fastboot, changed USB cables and downloaded new copies the images, with no success.
Digging deeper, I found out that I could not wipe cache or data using the stock recovery. This will fail with the error message blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/cache failed. Further troubleshooting attempts lead me to try twrp custom recovery software (Version 3.1.1) which I could only start using the mfastboot boot twrp-3.1.1-0-titan.img command since flashing the image as custom recovery will not fail but the phone instantly and silently reverts to stock recovery - even when not rebooting inbetween. Consequently, any attempts to flash an image using the software will fail with E1001: Failed to update system image.
At this point, I have no idea what else I could try. That's why I turn to you, great community of XDA .
Any help would be greatly appreciated.
Hi,
I just purchased a used Xperia Z1 C6903 and I am trying to put the latest Nougat Resurrection Remix on it. I need to get TWRP going first which I got stuck at trying to flash it.
I was able to get the phone downgraded to 14.1.G.1.534 using flash tool (ver 0.9.24.3). I did this following the guide here https://forum.xda-developers.com/showthread.php?t=2439328.
I was able to root it using Kingoroot.
I was able to unlock the bootloader using flashtool. Using *#*#7378423#*#*, the phone now reports Bootloader Unlocked: yes. See attached screenshot.
The part that I got stuck at is trying to flash TWRP in Fastboot. The command lines and error are below. The main error being "FAILED (remote: Command not allowed)"
I don't have an option in developer's options to "Unlock OEM bootloader". I read some other Xperia users being able to fix this problem by checking this.
I am running Windows 8.1. I am relatively sure that my drivers are correct. I had gotten a "drivers too old" error before in Flashtools but I was able to correct it by reinstalling new drivers.
I tried having debugging checked and unchecked before going into Fastboot and made no difference.
Tried both twrp-2.8.7.0-honami and twrp-3.0.2.0-honami with no success. Tried shortening file name to trp.img with no success.
Tried different 2 different adb files around the web with no success.
I read somewhere someone mentioned briefly that TWRP can be flashed using Flashtools. Is that true? I wasn't able to find a full guide for it.
Any help would be appreciated!
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery trp.img
target didn't report max-download-size
sending 'recovery' (13672 KB)...
OKAY [ 0.433s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.439s
Well I was able to get TWRP on there by installing the XY Dual Recovery. The problem with it is that the Resurrection Remix's installation instruction says to use TWRP 3x or higher. TWRP on XY is only at 2.8.7.0. I couldn't find a TWRP 3x flashable zip file for Honami and TWRP wouldn't flash TWRP 3x IMG file I found. Fastboot is still giving me the same Command Not Allowed error.
Any ways, I went ahead and flashed RR with 2.8.7.0. When I tried to flash GAPPs after it says there is insufficient space. I have at least 9GB+ internal storage. So not sure what the deal is there.
I also lost Dual Recovery and root after first RR boot.
Looking into getting re-rooted and reinstalling XY Dual Recovery now.. And then flashing GAPPS after.
Anyone know what the consequences are for installing RR with a lower rev of TWRP?
So the RR Rom does have root but it just doesn't have apps root. Only ADB root. I cant flash the su add on from Lineage's site since I lost recovery. I ended up FTF back to stock and then reflashed everything, the ROM then pico version of GAPPs (pico worked) and then the su addon. The su addon had an error when flashing in TWRP.
Any ways, long story short the whole thing didn't work. Still stuck with RR Without recovery. Su addon didnt work from the flash. And for whatever reason my SIM is not detected and I lost my IMEI in RR. I read that this is a known issue with C6902 but I have the C6903 and I had confirmed this through the service menu before ROM flash. Maybe problems with flashing RR without the latest TWRP.
The Command Not Allowed is still an issue that I dont know how to resolve. So I still can't flash newer version of TWRP.
Any help would be appreciated....
I guess I will try to find a ROM that 's compatible with TWRP 2.8.7.0.
OK! I figured out what the Command Not Allowed problem is!
I've been following the flash guides from a few websites. And they all reference this syntax for flashing TWRP.
Fastboot flash recovery twrp.img.
This syntax didn't work for me. All those websites properly copycat each other.
That syntax is either incorrect or just didnt work for my setup for some reason. I kept searching for ways to flash TWRP and found another website that uses a different syntax. I gave it a go and TWRP flashed right away. This is the syntax that worked for me.
Fastboot flash boot twrp.img
At least that part of the problem is resolved.
Even after flashing RR with TWRP 3.0.20, the SIM/IMEI is still not showing. Recovery is still lost on first boot. Reinstalling TWRP on top of RR causes RR to not boot any more. I will have to look into the RR thread to investigate more.
I will mark this thread as Solved for the Command Not Allowed.
Crossed out everything cause that was not the correct solution. Striked them out to keep them as part of the troubleshooting steps history.
Oops duplicated post.
OK! So it looks like I have to correct myself here on my previous solution.
My solution from earlier for using "Fastboot flash boot twrp.img" is incorrect apparently. Don't use this!
That was the reason why my TWRP was lost after RR boot. The recovery partition comes after the boot and system partition. By flashing the recovery into boot, it screws up the order.
Nevertheless, the Command Not Allowed was still a problem if I tried to use "Fastboot flash recovery twrp.img"
Any ways I was still looking into this problem and started looking into the boot.img stuff and saw someone uses this command line: "fastboot erase boot". This helps someone being able to flash a boot.img when the user was having the Command not Allowed problem trying to flash a different img for the boot partition.
This gave me an idea to try and use "fastboot erase recovery".
I gave it a try and I was able to use "fastboot flash recovery twrp.img" afterwards! It was done in a second.
Then I went through the normal steps of flashing RR and TWRP stayed this time. So now all is good with everything!
Any ways to recap, my full steps used for my RR Installation:
1. Flashtool to flash an Android 5.1.1 stock rom. I used C6903_14.6.A.1.236_1276. (obtained through Flashtool, Xperifirm) Your phone has to run in 5.1.1 for the SIM and IMEI to work in RR. Don't need to flash modem.zip, that's for C6902 only.
2. Fastboot flash erase recovery
3. Fastboot flash recovery twrp.img
4. Follow instructions to flash RR normally.
5. Resize system partition size (for flashing GAPPS micro size or larger).
6. Flash GAPPS.
7. Flash su addon from Lineage's website to allow root for apps and ADB.
I hope this helps someone with similar problems in the future. Thanks to those who stop in to see me ramble to myself about silly stuff
I had the same error message and was able to successfully flash using the phone and the Android Studio Emulator app.
I was already rooted and had an unlocked bootloader.
I tried this solution and it said error: cannot "recovery": No such file or directory LOL even though it's right here and I use it all the time..........I just can't figure it out.
Hi everybody
Tried to install a custom rom on my device and it has turned out to be a disaster. I'm completely stuck and have no idea what to do next. Tried everything i could find but i keep having the following problem.
Device: mi k20 davinci
Bootloader: unlocked
TWRP file: twrp-3.3.1-0-davinci.img
ROM: davinci_global_images_V11.0.4.0.QFJMIXM_20200117.0000.00_10.0_global_4c094d085a
TWRP had been succesfully installed but i broke it somehow and now i'm back in the fastboot mode. When trying to re-flash and boot twrp i recieve the following error:
"FAILED (remote: Failed to load/authenticate boot image: Load Error)"
If i try to flash the stock ROM with the miflash tool i receive the error
"Antirollback check error" "error"
if possible i just want to go back to stock and forget about this for now
Post it in K20 and not K20 Pro section.
I didn't know K20 had antirollback protection. Maybe try to flash a newer miui version, maybe a beta ?
Have you also tried "fastboot boot twrp.img" ?
oldbait said:
Hi everybody
Tried to install a custom rom on my device and it has turned out to be a disaster. I'm completely stuck and have no idea what to do next. Tried everything i could find but i keep having the following problem.
Device: mi k20 davinci
Bootloader: unlocked
TWRP file: twrp-3.3.1-0-davinci.img
ROM: davinci_global_images_V11.0.4.0.QFJMIXM_20200117.0000.00_10.0_global_4c094d085a
TWRP had been succesfully installed but i broke it somehow and now i'm back in the fastboot mode. When trying to re-flash and boot twrp i recieve the following error:
"FAILED (remote: Failed to load/authenticate boot image: Load Error)"
If i try to flash the stock ROM with the miflash tool i receive the error
"Antirollback check error" "error"
if possible i just want to go back to stock and forget about this for now
Click to expand...
Click to collapse
Flash Fastboot ROM through Command Prompt. https://in.c.mi.com/thread-334-1-1.html?t=1586384142148