[Q] Recovery partition not found - Xperia SP Q&A, Help & Troubleshooting

It's not the first time I try to flash a recovery without success:
---------------------------------
fastboot flash recovery twrp.img
sending 'recovery' (10615 KB)...
(bootloader) USB download speed was 13864kB/s
OKAY [ 0.800s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
finished. total time: 0.814s
---------------------------------
Attached: driver loaded in fastboot mode, and drivers used when phone has booted
So, I don't think it's a problem of drivers. I'am able to flash a kernel, I can use fastboot commands (like devices, getvar, etc) ... but not to flash recovery.
I'm running a cm11 LBL with williams kernel v9.1
Any idea ??
Thanks

sambastrakan said:
It's not the first time I try to flash a recovery without success:
---------------------------------
fastboot flash recovery twrp.img
sending 'recovery' (10615 KB)...
(bootloader) USB download speed was 13864kB/s
OKAY [ 0.800s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
finished. total time: 0.814s
---------------------------------
Attached: driver loaded in fastboot mode, and drivers used when phone has booted
So, I don't think it's a problem of drivers. I'am able to flash a kernel, I can use fastboot commands (like devices, getvar, etc) ... but not to flash recovery.
I'm running a cm11 LBL with williams kernel v9.1
Any idea ??
Thanks
Click to expand...
Click to collapse
I am guessing the reason you are running CM11 LBL is due to the restriction imposed by a locked bootloader and not because you are choosing to miss out on all the Lollipop fun. If that's the case, I don't think you can flash a recovery via fastboot the same way you can with an UBL. You said it yourself that you have tried flashing recoveries multiple times w/o success. As far as I know, your bootloader needs to be unlocked for flashing via fastboot commands.
On the other hand if your bootloader's unlockable or you relocked it sometime in the past and forgot about it, I suppose unlocking it would do the trick. Just in case you don't know, dial up *#*#7378423#*#* and see if its unlockable.
Also what is your current recovery? I am guessing it one that came with the kernel you are using and not something you flashed separately?
Btw did you flash Williams kernel separately or did it come with the ROM? If you did flash it separately then how did you do it? Also you mentioned you flashed a kernel - did you mean via fastboot or something else like FlashTool?

No. My bootloader is unlocked (verified and I have a custom kernel running).
At the present time my recoveries are in the rom. But williams kernel is compatible with fotakernel so I should be able to flash a recovery and use it but ...
thanks

sambastrakan said:
No. My bootloader is unlocked (verified and I have a custom kernel running).
At the present time my recoveries are in the rom. But williams kernel is compatible with fotakernel so I should be able to flash a recovery and use it but ...
thanks
Click to expand...
Click to collapse
Since your bootloader's unlocked and your phone's probably rooted, why don't you use Rashr to flash the file? It will replace the recovery you have right now (cyanogenmod recovery?) with the one you wanna flash.
Note: This recovery stays even when you flash new ROMs so if want something else you will have to reflash via Rashr or flash stock firmware kernel with FlashTool.
Also if you switch to Lollipop, you can have dual recoveries if you follow the instructions on the Tangerine kernel thread.
http://forum.xda-developers.com/xperia-sp/orig-development/kernel-tangerine-kernel-v1-t3073297
Edit: What recovery do you have with Williams kernel right now?

Williams kernel.
Way back when i was using it v8 i tried flashing recovery.img from Rasht, it said recovery flashed, but nothing changed.
I did tried fastboot it also failed (can't remember what was the message in flashtool).
I think the culprit here is the kernel.

akashsaini7 said:
Williams kernel.
Way back when i was using it v8 i tried flashing recovery.img from Rasht, it said recovery flashed, but nothing changed.
I did tried fastboot it also failed (can't remember what was the message in flashtool).
I think the culprit here is the kernel.
Click to expand...
Click to collapse
It is very possible ...
Thx

Useful
There is a program called AdbDriverInstaller.exe. If you want me to send to you just P.M. me. It's actually very good in finding drivers. I used to have a problem installing CM11 in CWM and this one helped me.

kojata said:
There is a program called AdbDriverInstaller.exe. If you want me to send to you just P.M. me. It's actually very good in finding drivers. I used to have a problem installing CM11 in CWM and this one helped me.
Click to expand...
Click to collapse
thank you. i will have a look.

facing the same problem.. did u manage to fix it yet?

l2azoredge said:
facing the same problem.. did u manage to fix it yet?
Click to expand...
Click to collapse
not fixed neither understanded but there are 2 turnarounds:
1- using rashr app to flash the img
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
if you can't enter your recovery after that the guilty is the kernel. Williams kernel is not compatible with recovery partition even if it says it is in 1st post.

sambastrakan said:
not fixed neither understanded but there are 2 turnarounds:
1- using rashr app to flash the img
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
if you can't enter your recovery after that the guilty is the kernel. Williams kernel is not compatible with recovery partition even if it says it is in 1st post.
Click to expand...
Click to collapse
ive already tried using rashr...it seems to flash..but the recovery which i enter afterwards is still the same..
for the 2nd one ive placed recovery.img in the root of both internal and external storage..when using the 2nd command says...no such file or directory exists..
can this problem be rectified if we flash stock kernel thru fastboot??? and then flash the new recovery?

l2azoredge said:
ive already tried using rashr...it seems to flash..but the recovery which i enter afterwards is still the same..
for the 2nd one ive placed recovery.img in the root of both internal and external storage..when using the 2nd command says...no such file or directory exists..
can this problem be rectified if we flash stock kernel thru fastboot??? and then flash the new recovery?
Click to expand...
Click to collapse
I don't think so. what kernel are you using ? Seems your kernel ignore recovery partition....

Having the same problem after upgrading to CM 13. Any solution would be appreciated.
2- using command: dd if=recovery.img of=/dev/block/mmcblk0p11
Click to expand...
Click to collapse
Thank god this nasty hack did the trick. However I placed my recovery.img inside the /system, so my command was 2- using command: dd if=/system/recovery.img of=/dev/block/mmcblk0p11

Try to flash with minimal adb fastboot.
If not,try this method: flash your recovery as boot(fastboot flash boot recovery.img), see if it works,then flash your kernel again.

Instead of
Code:
fastboot flash recovery twrp.img
use
Code:
fastboot flash boot twrp.img
//I didn't notice that this was already said

IiroP said:
Instead of
Code:
fastboot flash recovery twrp.img
use
Code:
fastboot flash boot twrp.img
//I didn't notice that this was already said
Click to expand...
Click to collapse
Has someone tried it already? I am afraid after installing the recovery in the boot partition and something goes wrong, that then the phone will be bricked.
Might it be the afore mentioned Kernel issue? My Xperisa XP has the kernel: 3.4.0-perf-g4c8352f-00783-gce6e17b
Thx for replies.
[EDIT]
Installing TWRP in boot partition worked fine. Let us see how it works with an Update.

The same problem
I have the same problem. Maybe Sony didn't create a recovery partition on this Phone, I unlocked it in 2016 and now i don't remember how i did this.
I only can flash boot, but afeter install system from twrp or cwm, this recovery disappear so i can't install gapps.

My experience with "Partition Not Found" is:
1.- Install Stock Rom, later of install Root
2.- Install TWRP with CMD (But the 2.8 high version, (On the internet there is a version of CMD that only makes one click and ready) Note* i Update to 3.0.1, later of install 2.8 version.
(Now update to device to Android 7, or 6, or 5)
3.- Install Rom + Gapps + Root (Note* Install Root because later u need install TWRP App)
4.- After of install rom, install TWRP App, Download and Flash Image TWRP (in the same app) on device
5.- Finally check u TWRP if all install is correct.
Saludos!
Actually i have Android 7 (Candy Rom + Fusion Kernel) with TWRP y everything is fine!

Related

[GUIDE] Update stock rooted/modified rom to last 6.0 Marshmallow w/o losing your data

Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
unlocked bootloader
a working backup just in case
Pro:
you will not lose your data / application
Cons:
you will lose all system modification (root, busybox, custom kernel...)
you'll take all the risk of operation (I've tested on my device)
Guide:
some file names changes depending on version so please complete the {version_here} placeholder with the file you download
* prepend "sudo" on command line if you are on a Linux machine
download last version for your device here (if you want to root download the zip file in the section below to speed up the operations)
extract
extract image-{device_here}-{version_here}.zip in the same folder (no subdir)
command line* (or reboot device with vol down pressed):
Code:
adb reboot bootloader
command line*:
Code:
cd {your_path_here}
command line*:
Code:
fastboot flash bootloader bootloader-{device_here}-{version_here}.img
command line*:
Code:
fastboot reboot-bootloader
command line*:
Code:
fastboot flash radio radio-{device_here}-{version_here}.img
command line*:
Code:
fastboot flash system system.img
command line*:
Code:
fastboot flash boot boot.img
ONLY IF YOU FOUND A VENDOR.IMG IN THE ZIP command line*:
Code:
fastboot flash vendor vendor.img
command line*:
Code:
fastboot flash cache cache.img
command line*:
Code:
fastboot reboot
Now you have the lastest stock image and all your data.
Change recovery (TWRP) and root:
Note that we haven't flash the stock recovery, but during every boot of an unmodified system there's a script that do that (supersu usually deactive this behavior during install).
If you had TWRP installed and the SuperSU zip on your device, at the end of the above procedure you can boot directly from bootloader to recovery and go directly to last step:
download: TWRP image (twrp-{version_here}-{device_here}.img) for your device
download: chainfire SuperSU 2.71 on your device
command line*:
Code:
fastboot flash recovery twrp-{version_here}-{device_here}.img
alternatively you can keep the original recovery and use TWRP one time with
Code:
fastboot boot twrp-{version_here}-{device_here}.img
boot in recovery and flash supersu zip
working fine for me, all correct, thanks
Just tried with flash_all.bat. I'm getting the message "Can not generate image". How can I solve this, please?
Thank you, works like a charm!
Same here, cant flash system
There's not flash-all.bat in my steps (that delete you data!), can't give help about it sorry
i've gone your way, but i tried also the flash-all.bat with the -w switch, didnt work.
Tnx mate. Helped a lot
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
c3k said:
Requirements:
you need to have a pc with adb working
a stock firmware on your device (any)
a working backup just in case
Click to expand...
Click to collapse
so if i have twrp, before i have to return stock 5.0.1??
or i flash directly 5.1 over twrp?
tnx
chikess said:
I think that all who has flashed the developer preview got an broken filesystem or the partitions missmatch.
Before i used the preview the -w update flag worked well to rebuild the partitions, now it didnt work anymore, tried all factory images don to 4.4
Click to expand...
Click to collapse
I didn't flash the preview.
Sp0KI said:
I didn't flash the preview.
Click to expand...
Click to collapse
Hmm ok, but u got the same problems. So, in this way we had to wait for a flashable zip or maybe ota.
@c3k why do you mention to flash twrp while in steps above stock recovery is not included to flash... ? Doesn't that mean that custom recovery (twrp) is still on device?
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Sp0KI said:
Cant flash the system.img manually. All the other img are working. I get this error message :
Code:
target reported max download size of 1073741824 bytes
error: cannot load 'system.img'
The old system.img from lrx22c works also.
Someone know whats going on?
Click to expand...
Click to collapse
Are you using the latest version for the fastboot.exe file?
foosion said:
Doesn't this require an unlocked bootloader, and not necessarily root, or am I confused?
Click to expand...
Click to collapse
This requires an unlocked bootloader. But, there are users like us who have rooted the stock ROM.
This guide is meant for the users who has unlocked bootloader with rooted stock ROM.
This guide will also work for phones with unlocked bootloaders with STOCK ROM(rooted or un-rooted).
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I had faced the same issue while flashing LRX22C. It got fixed by rebooting the phone and switching the cable to a different USB port. Might work for him too.
PS: I have flashed the images from Linux.
In my case I guess all the issues are from a previous attempt to flash OptiPop ROM. The flashing process it's a little tricky to understand (with that F2FS file system). I remember that after flashed OptiPop and the phone didn't boot, I tried to restore to stock ROM and it was a lot of errors until it worked fine again.
efrant said:
Are you using the latest version for the fastboot.exe file?
Click to expand...
Click to collapse
I'm using the newest Minimal ADB.
The strange thing is, that i can flash the LRX22C system.img and all other new lmy47d files but not the lmy47d system.img.
I guess i'll wait for the OTA update and hope it works then.
Tried rebooting and switching port and usb cabel..
You actually don't need to manually install supersu or root. Flash the 5.1 images and then (after the first full boot) flash twrp.
Once you boot into twrp and exit out of it, you will be promoted with a message that your phone is not rooted, and you're asked if you want to install supersu. It's built into twrp.

After flash zip via twrp BRICKED

Hi I need help,
1. I used "Huawei update etractor" to create fleshable zip from official ROM (boot.img, system.img, cache,img, cust.img, userdata.img)
2. I flashed this zip via TWRP
3. after reboot is phone in BOOTLOOP and recovery(volume + and powerbutton ) dont work and ADB dont work too,
4. BOOTLOADER is UNLOCKED still
5. fastboot is working BUT I tried flash (boot.img and recovery.img) from many ROMs this is unsucessfully
Exist some solution for me?
I have HUAWEI ASCEND P7-L10
Could you still enter twrp(after flashing)?
Try to wipe everything and than flash all images via fastboot
But it should be the same version as you previously installed, otherwise it won't work
RangerP7 said:
Could you still enter twrp(after flashing)?
Try to wipe everything and than flash all images via fastboot
But it should be the same version as you previously installed, otherwise it won't work
Click to expand...
Click to collapse
THX for answer.
I cannot enter to twrp after flashed.
How can I wipe everything when I have available only fastboot.?
I don't know previously version. I tried flash images via fastboot several ROMS - without successfully.
Problem is in flash ROM version only ? really? If is it true I will be flash all rom order by version
Try to enter twrp via fastboot
"fastboot boot (YourTWRPName).img"
Could you now enter twrp?
Otherwise you can try (for wipe partitions)
"fastboot erase (partition = data, cache, system, boot)"
(do not type() )
And you need to flash the version you had previously installed... Don't flash any other roms or other versions... It won't work
RangerP7 said:
Try to enter twrp via fastboot
"fastboot boot (YourTWRPName).img"
Could you now enter twrp?
Otherwise you can try (for wipe partitions)
"fastboot erase (partition = data, cache, system, boot)"
(do not type() )
And you need to flash the version you had previously installed... Don't flash any other roms or other versions... It won't work
Click to expand...
Click to collapse
C:\adb>fastboot boot TWRP-2.8.7.0.img
downloading 'boot.img'...
OKAY [ 0.512s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.522s
C:\adb>fastboot erase boot
erasing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.003s
i cannot enter to twrp.
After flash previously instaled version rom ->> it is Without progress ->> Phone is in bootloop still
soki.niva said:
C:\adb>fastboot boot TWRP-2.8.7.0.img
downloading 'boot.img'...
OKAY [ 0.512s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.522s
Click to expand...
Click to collapse
Are your drivers correctly installed?
Is your bootloader really unlocked?
Did you previously installed Android 5.1 (B852/839)?
So you need to flash the version 3.0.0-0 of twrp
RangerP7 said:
Are your drivers correctly installed?
Is your bootloader really unlocked?
Did you previously installed Android 5.1 (B852/839)?
So you need to flash the version 3.0.0-0 of twrp
Click to expand...
Click to collapse
Yes is unlocked. If I reboot into bootloader There it is red title "PHONE UNLOCKED"
And comands "fastboot -S 512M flash boot boot.img" finished without fail...
1.. step: STOCK installed B129
2. step: i flash custom rom "Miui_HP7_4.9.18_GER_longest" via twrp -> all functionally after this step.
3.step. I flash "P7-L10C900B852_eu_channel_SW (wirhout recovery.img)"" via twrp -> BOOTLOOP(and recovery no work) after this step
twrp 3.0.0-0 not work too.
-maybe I use bad key combination for enter to recovery? (i use VOLUME UP + POWER BUTTON) or (VOLUME UP DOWN +POWERBUTTON)
Thats very strange...
Actually I don't know what to do now
I never had this problems
Did the B129 work without bootloop?
What exactly is B129?
I'm from Europe the first version I had on this phone was B126/B133
RangerP7 said:
Thats very strange...
Actually I don't know what to do now
I never had this problems
Did the B129 work without bootloop?
What exactly is B129?
I'm from Europe the first version I had on this phone was B126/B133
Click to expand...
Click to collapse
B129 is Vodafone version and worked without bootloop.
do you have any idea?
soki.niva said:
B129 is Vodafone version and worked without bootloop.
do you have any idea?
Click to expand...
Click to collapse
So your phone was branded before?
Now it would make sense why you can not install any other software...
You need to use original Vodafone software not the free public versions
But why twrp is not working... I don't know...
RangerP7 said:
So your phone was branded before?
Now it would make sense why you can not install any other software...
You need to use original Vodafone software not the free public versions
But why twrp is not working... I don't know...
Click to expand...
Click to collapse
I read other post, problem was made :
I created fleshable zip(via huawei extractor), BUT with bad profile(ASCEND P6 profile) because profile for P7 is missing.
Is it any solution for me?
Could you flash the images via fastboot?
RangerP7 said:
Could you flash the images via fastboot?
Click to expand...
Click to collapse
It appears that is working.
Commands of type: fastboot flash boot boot.img - are finised without error.
And all other images?
recovery data system
Flash them and try now the 3 buttons method
You know how this works?
RangerP7 said:
And all other images?
recovery data system
Flash them and try now the 3 buttons method
You know how this works?
Click to expand...
Click to collapse
I flashed all images (boot,recovery, cache, cust, userdata, and system)
No, I don't know 3 buttons method. What is it ? hold volume up volume down and power button. without changes...
Please I need name of partition for ASCEND P7 -> Do you know? for example : What is number of partition is for recovery partition="/dev/block/mmcblk0pXX" ...?
<File type="recovery" partition="/dev/block/mmcblk0p11">recovery.img</File>
<File type="boot" partition="/dev/block/mmcblk0p12">.boot.img</File>
<File type="system" partition="/dev/block/mmcblk0p16">system.img</File>
<File type="cache" partition="/dev/block/mmcblk0p17">cache.img</File>
<File type="cust" partition="/dev/block/mmcblk0p18">cust.img</File>
<File type="userdata" partition="/dev/block/mmcblk0p19">userdata.img</File>
The 3 buttons method is a direct flash of all partitions
You need to flash the stock recovery, put the full update.app into the dload folder on your external storage and boot up while holding all 3 buttons
But why you can't flash the stock recovery... I don't know... I never had this problems
If you find a fix for this it will be easy to do the rest
But without a working recovery a can't help you... Sorry
soki.niva said:
Yes is unlocked. If I reboot into bootloader There it is red title "PHONE UNLOCKED"
And comands "fastboot -S 512M flash boot boot.img" finished without fail...
1.. step: STOCK installed B129
2. step: i flash custom rom "Miui_HP7_4.9.18_GER_longest" via twrp -> all functionally after this step.
3.step. I flash "P7-L10C900B852_eu_channel_SW (wirhout recovery.img)"" via twrp -> BOOTLOOP(and recovery no work) after this step
twrp 3.0.0-0 not work too.
-maybe I use bad key combination for enter to recovery? (i use VOLUME UP + POWER BUTTON) or (VOLUME UP DOWN +POWERBUTTON)
Click to expand...
Click to collapse
Step 3 is wrong. You cannot flash official Huawei ROMs via custom recovery, even if they've been made bootable by Huawei Update Extractor.
What you need to do is use Update Extractor again to extract RECOVERY.IMG of the ROM that is currently installed on your phone. Then flash it with following command:
fastboot flash recovery RECOVERY.IMG
If that's not sufficient you can try the same thing with BOOT.IMG | SYSTEM.IMG | CUST.IMG
---------- Post added at 04:26 AM ---------- Previous post was at 04:21 AM ----------
RangerP7 said:
The 3 buttons method is a direct flash of all partitions
You need to flash the stock recovery, put the full update.app into the dload folder on your internal storage and boot up while holding all 3 buttons
But why you can't flash the stock recovery... I don't know... I never had this problems
If you find a fix for this it will be easy to do the rest
But without a working recovery a can't help you... Sorry
Click to expand...
Click to collapse
@RangerP7 I believe that the dload folder MUST be on a SD card and not on internal storage as 3 button method wipes internal storage.
Milan-XDA said:
@RangerP7 I believe that the dload folder MUST be on a SD card and not on internal storage as 3 button method wipes internal storage.
Click to expand...
Click to collapse
Sorry my fault... Of cause the external storage
Thank you
RangerP7 said:
Sorry my fault... Of cause the external storage
Thank you
Click to expand...
Click to collapse
I tried but no results... why not solution not work(not exists?)when fastboot menu still works?
What exactly is not working? I (we) cannot help you with no information?

Solved with Corrections: Unable to flash TWRP, Failed (Remote: command not allowed)

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.

error flashing with fastboot

my phone is moto g2 xt1068
i flash it with fastboot very much because after 3 days restarting and hang in boot but after flash it is work for 3-5 days
now i want to flash it but have this error fastboot
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.979s]
writing 'partition'...
FAILED (status read failed (Too many links))
finished. total time: 1.778
please help me
thanks
Do you have twrp?
Have you tried flashing twrp if you don't have it installed?
Which ROM are you flashing?
It looks like you don't have enough space if I'm reading that error correctly
We need to know so we can help you
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
This is stock firmware, yes?
Are all your Moto G drivers up to date?
There are a number of different ways to install depending on the package type.
Some packages are flashable zips. Needs Twrp (Team Win Recovery Project)
Some are sideload packages installed via Fastboot.
Some are OTA packages (OTA, over the air) installed via phone update.
amir58hz said:
what is twrp?
now my error (too many link) is resolved when changed my usb cable but my problem that need flash after 3-5 days
please help to solved it
my frimware is
XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thanks
Click to expand...
Click to collapse
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
bejunk said:
make sure you have motorola drivers installed https://motorola-global-en-aus.custhelp.com/app/answers/prod_detail/a_id/86934/p/154,153
make sure adb is up to date, you can use this https://forum.xda-developers.com/showthread.php?t=2317790
You want to flash stock rom again? You have to know, that you must follow exact steps, else it fails.
I would recommend you to re-flash stock ROM and if it still breaks after 3-5 days, you know something is faulty with your hardware.
-- re-flashing stock rom, will erase ALL your data + internal storage, backup all your data to SD first!
You can get latest stock rom for your device here: https://firmware.center/firmware/ make sure its xt1068 model and for your country/region
reboot to bootloader, connect to pc,
in cmd, type
Code:
fastboot devices
-> it should show your device, proceed:
Code:
fastboot.exe flash partition gpt.bin
fastboot.exe flash motoboot motoboot.img
fastboot.exe flash logo logo.bin
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash system system.img_sparsechunk.0
fastboot.exe flash system system.img_sparsechunk.1
fastboot.exe flash system system.img_sparsechunk.2
fastboot.exe flash system system.img_sparsechunk.3
fastboot.exe flash modem NON-HLOS.bin
fastboot.exe erase modemst1
fastboot.exe erase modemst2
fastboot.exe flash fsg fsg.mbn
fastboot.exe erase cache
fastboot.exe erase userdata
-> you need to follow exact the flashing steps, else it might fail! (if you have ...sparsechunk.4 or even .5 flash it also)
-> TWRP is a custom recovery. You dont need it, if you want to install a custom rom, you need TWRP.
peace & good luck!
Click to expand...
Click to collapse
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
amir58hz said:
thanks for replying
i flashing with this metod to many about 50rd but after 3-5 days mobile is restarting and some of program is stoping (google play service and other progrm)then i know that mobile is after some restart stop on boot and after boot page show black page then i start to flashing again with above method and i download all of latest frimeware and flash it
now i thinking my emmc have problem?
thanks
Click to expand...
Click to collapse
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
bejunk said:
Can you make a picture of your bootloader? And can you post me the name of the update you allways flash?
Im not sure, but that really sounds like emmc is faulty... I mean above method makes sure all is good with software, so can be only HW. Its typical, when itcomes to write to some damaged cluster of emmc, all gets f#+"ed up & it than cant start again. Hmm if it happens again, i would try to first format internal fully, maybe it gets fixed.
For formatiing internal storage, you need TWRP (recovery), to install it:
1. unlock your bootloader here: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2. download latest TWRP here https://dl.twrp.me/titan/
3. connect to bootloader then type:
Code:
fastboot flash recovery twrp-3.2.3-0-titan.img
after it flashes, choose "recovery" in bootloader using volume down. Volume up selects.
In TWRP enable modifies to system if asked
then in WIPE tab choose advanced & format Internal.
You can then reboot to system. Hopefully it goes well then.
If not, you can try install a custom ROM, but honestly, if the emmc broken it will probably not help.
Also if you are very experienced/know someone you could try located the exact location of broken clusters & then exclude them from filesystem, but this is very hard to examine...
Peace!
Click to expand...
Click to collapse
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
amir58hz said:
my frimware is: XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml
thi is my boot picture:
https://photoland.io/i/2mQe79
https://photoland.io/i/2mQuFx
https://photoland.io/i/2mQ0qZ
Click to expand...
Click to collapse
Thx. But i need a picture of bootloader screen, see my picture!
-> hmm in your case i would try it now with formatting internal completly.. But even better would be full formating, so when you have TWRP:
- format Internal storage
- then tick system + data + cache and format them.
- You have to reflash stock then OR (i recommend) try it with a custom rom, like you said allready tried stock many times...
To install custom rom, get these files
ROM: https://forum.xda-developers.com/moto-g-2014/orig-development/rom-lineageos-15-1-t3786749 get latest build
GApps: https://opengapps.org/ choose ARM -> 8.1 -> nano version
put everything in sdcard or storage (after wiping it)
Then in TWRP -> factory reset in wipe menu -> install ROM zip -> install GApps -> reboot. 1st boot can take some time. Test & report.
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
bejunk said:
Thx. But i need a picture of bootloader screen, see my picture!
EDIT: I read in other threads who have the same problem, that they have a wrong recovery or things dont get flashed..
Did in commandline window, when you execute a command get a [OKAY] in terminal after EVERY operation?
EDIT2: Your rom file seems okay. If you are sure that you have xt1068, i would try it with formatting internal, see above. When you unlock bootloader, it will completly wipe your device! Backup stuff 1st!
good luck
Click to expand...
Click to collapse
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
amir58hz said:
sorry for my mistake
yes is that xt1068 and after flashing all of step is ok and finished wirted in fastboot command
now in recovery twrp format all thing and flash it
https://photoland.io/i/2mQyAW
Click to expand...
Click to collapse
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
Thanks very much
I dont have custom rom can you advise me to download it
I flashed it if is not have problem is very good but it crash and dont work i send here my problem
Thanks again good luck
bejunk said:
Yeah i updated my post, i would really recommend to try a custom rom and see how its there... But full format 1st..
You can allways go back to stock, so its worth a try..
I will be afk for some time now, good luck, bro :good:
Click to expand...
Click to collapse
hi man
after one day mobile is work true thanks alot
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
amir58hz said:
after 3 days restart phone but then stop in black page
now flash again
what is my problem?
Click to expand...
Click to collapse
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
bejunk said:
So you flashed custom ROM -> it worked for 3 days normal -> then black screen (page) ??
When yes, probably something with your HW is faulty (most likely the eMMC has a bad block or something..)
Click to expand...
Click to collapse
No i flash it with same my frimware
Now for flashing with custom rom it need download rom android8?
i have this error in wipping and installing rombut instal it
my error is:
e:recv error on uevent
But now flashed to 8.1 android
Thanks

Troubles reinstalling TWRP [Failed to load/authenticate boot image: Load Error]

I dirty flashed a new version of xiaomi.eu stable build, and it caused TWRP to uninstall itself.
Whenever I hold power on and volume up it just goes to fastboot.
Now I tried reinstalling TWRP like I've done many times before, but it keeps throwing an error. The error I get is when trying to boot without flashing the img. When I do this, I get the error:
Code:
fastboot boot TWRP.img"
downloading 'boot.img'...
OKAY [ 1.609s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 1.675s
Anyone gotten any ideas on what could be going on here? I'm scared to try anything as my phone currently works, but I need TWRP back to update my phone to a different versions and to install the clock mod again.
Thanks!
Got it to load once, but now back to square one. Throwing same error.
Now when running the command fastboot reboot recovery it's saying
Code:
fastboot: usage: unknown reboot target recovery
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Try on a computer with a USB 2.0 port, or a different usb cable, had the same issue once
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
I have the same error. How can I fix this pls?
MrkoZino said:
I have the same error. How can I fix this pls?
Click to expand...
Click to collapse
Flash the latest official rom then start all over again. Follow the post above you about miflash.
Hello, I've had the same problem, then flashed latest dev rom via MiFlash and it booted, but now after I flash any custom ROM in TWRP i have this issue again and need to reflash chinese ROM. How can I flash any custom rom?
i'm stuck in the same issue. stuck in fastboot and it would not load recovery. any fix?
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
greendra8 said:
And writing 'fastboot boot twrp.img' turns the phone off / makes the screen go black. Fully bricked now as the OS wont load either.
Click to expand...
Click to collapse
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
DJPlaya said:
Hi, i fixed the "Failed to load/authenticate boot image: Load Error" by simply restarting the Device.
It seems to appear randomly when flashing partitions and then block all further Transfers.
If the Device loops in Fastboot, the only Solution to me was re flashing the Stock Firmware.
I have the same Issue, but reflashing Stock Firmware or making OTA Updates dident helped for me. Ive already tried TWRP and OrangeFox without success. The Screen always turns black and Fastboot stays active in an limited Mode, any Ideas? My host Computer only has 3.0+ Ports only, but ive used an 2.0 Extender so it should be fine?
Click to expand...
Click to collapse
long time ago now. but i remember at one point having to flash the stock firmware using the mi unlock tool. i also remember trying every single version of twrp and rom until one finally worked. sorry i can't help much but i believe that's how i eventually fixed it.
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Marihot said:
hi, I've experienced with the same thing.
this methode help me out from it.
try to reflashing some file image from the rom where youre want to install in hh with adb.
copy this files below from rom image to adb folder
1. system.img (command in adb >> fastboot flash system system.img)
2. boot.img (command in adb like #1, change the name of img file) do till #6
3. vendor.img
4. dtbo.img
5. cust.img
6. misc.img
7. now flashing twrp/recovery.img (choose twrp compatible with rom you want to install) with adb
8. the "fastboot boot recovery.img" with adb
9. flashing the rom by twrp
Click to expand...
Click to collapse
Where do you get these .img files?
iconoclasthero said:
Where do you get these .img files?
Click to expand...
Click to collapse
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Marihot said:
all img files come from the official rom china stable V12.0.2.0.QEBCNXM (.tgz), download and extract the tgz file then find img files from images folder
Click to expand...
Click to collapse
Please tell the details for this method
greendra8 said:
Ended up having to reinstall dev rom. Device relocked, so have to wait 15 days again. @BusterBg_18 Thanks, will do when I unlock the device
EDIT: When using Mi Flash tool, make sure to check 'clean all' and not 'clean all and lock' in the bottom right. That's what set me back 2 weeks.
Click to expand...
Click to collapse
BROOOOOOOOOO HAHAHAHAHAHA I LITERALLY JUST READ YOUR COMMENT AND 10 SECONDS LATER I FLASH THE ROM WITH "CLEAN ALL AND LOCK" Im a f-king dumb bro
Marihot said:
你好,我也经历过同样的事情。
这个方法帮助我摆脱它。
尝试使用 adb 从要在 hh 中安装的 rom 中重新刷新一些文件映像。
将下面的文件从 rom 映像复制到 adb 文件夹
1.system.img(adb >> fastboot flash system system.img中的命令)
2. boot.img(adb 中的命令,如#1,更改 img 文件的名称)直到 #6
3. 供应商.img
4.dtbo.img
5. 自定义.img
6. 杂项.img
7. 现在用adb刷twrp/recovery.img(选择twrp与你要安装的rom兼容)
8. adb 的“fastboot boot recovery.img”
9. twrp刷入rom
Click to expand...
Click to collapse
Thank you, brother
try fastboot set_active a
or fastboot set_active b

Categories

Resources