This is for anyone who couldnt flash CM5.0.3 due to kernel size. We are working on why the device couldnt flash a large kernel.
If anyone who couldnt flash CM5.0.3 can send me there recovery.log it would be great !!
What to do:-
1.Boot into recovery
2.Nandroid Backup
3.Wipe
4.Flash stock CM(Or the build you are on when you backed up)
5.Nandriod restore
6.Chose Copy recovery.log to SD from the others menu in recoevry
7.Reboot
Send my your recovery.log either on pasebin or as a .txt file
I will get back to you with any findings and or a fix
From my device i can see that it trows bad block errors .... wich points to a bad device, but if a lot of people have it may be a h/w version the drivers dont 100% work with so i need some .logs to compare.
Many thanks in advanced
just doing it now mate.
http://pastebin.com/9rUjK2uD
Humm your bad blocks are at different locations to me :-s strange. Hoping they ate not a bad batch of n1's. ..
Which recovery version did you use to make the failing Nandroid backup?
Some questions (to make sure I understand the problem) :
1. Do you have the same problems when you flash CM via the update.zip?
2. Is the problem only occurring when you try to restore a nandroid?
3. Is the problem occurring with other nandroid backups (so non CM roms)?
4. Do you have the same problem when you extract the boot.img from the faulty nandroid backup and flash it via fastboot or via adb flash_image?
5. Why do you assume it's related to a "big" kernel?
Could someone please upload a failing boot.img from a "faulty" nandroid backup?
1. Not when flashing. Zip with small kernal (5.0.3 had a larger kernel throwing not enough space error)
2. That is the main issue. But when flashing CM5.0.3 from zip recovery.log has tge same errors.
3. Yes for example you can't restore to the desier rom after being on CM
4. Fastboot boot boot.img for the nandroid fails to boot (haven't tried flash image yet wil do when I'm home)
5. Only deviese with this faild to flash cm5.0.3 with tge same (out of space error in recovery)
I see when nandroid restorong stock cm5.0
3.1 over a flash of 5.0.3.1 (same boot) from zip recovery skips writing the boot image as the heders are the same. This only accurs when going from two differing boot.img from nandroids
Ill upload a nandroid backup boot.img all settings that I'm running now.
Oh and CM thinks there are h/w difference with some N1's :-s I'm not too shure. ..
Does recovery wipe boot before writing to it ?
Many thanks for the help
Perhaps the people who are having trouble could post the P/N from the back of the phone. The original P/Ns ended in 00 F and then I began seing devices ending in 01 XH. I'd be curious to know if something was tweaked to improve performance or to save money. I have an original 00 F and have had no issues flashing CM 5.0.3.
Probably just a case of a too tight fit for some devices.
MTD size for boot on Nexus One is 0x280000 (2621440) bytes.
With an eraseblock size of 0x20000 (131072) bytes.
If you happen to have a device with a bad eraseblock or two on the boot part it might hit into the sizelimit.
What was the size of CM 5.0.3 boot.img?
When flashing boot.img From nandroid in fastboot it throws this error ...
F:\and\ADB>fastboot flash boot bootnand.img
sending 'boot' (2560 KB)... OKAY
writing 'boot'... FAILED (remote: image update error)
F:\and\ADB>fastboot flash boot bootcm.img
sending 'boot' (2332 KB)... OKAY
writing 'boot'... OKAY
Click to expand...
Click to collapse
As u can see the stock CM image is fine
and in flash_image
# flash_image boot bootnand.img
flash_image boot bootnand.img
mtd: not writing bad block at 0x00100000
error writing boot: No space left on device
#
Click to expand...
Click to collapse
and yes the system runs fine befor the backup ....
what i cant understand is why the system can run fine but when writing the boot image from backup (which should be the same) doesnt work .... :-S
:-S
heres the image i used
http://www.sendspace.com/file/qhc6hd
Oh and the size of the 5.0.3 boot.img is 252928 bytes i think
and my p/n ends in 00 f
Hmm, it seems dump_image (used by nandroid backup) dumps all of the mtd partition) including bad blocks.
This prevents it to be flashed back to for people which happens to have bad block on boot partition.
Guess we need to patch dump_image, there is new MTD ECC code submitted in AOSP lately. I'll modify dump_image to make it handle bad block on read so this problem can be solved.
asop
how do you guys find out the new patches that is in ASOP code and stuff? like how did oyu guys figure out that the new kernel was pushed to the code?
Failed to flash boot.img
Here's Mine
pastebin . com /85FbrgQu
Im worried if there will be a build that wont run on devices like mine :-(
Just got word of a brand new phone from HTC with this issue so im dabuting its a H/W fault as its so widespread and on new phones.
flashed 5.0.3 ok P/N ending with 00 f
Apache14 said:
Just got word of a brand new phone from HTC with this issue so im dabuting its a H/W fault as its so widespread and on new phones.
Click to expand...
Click to collapse
All NAND flashes are delivered with bad eraseblocks, it's designed that way. It should be handled in software to deal with it. It's nothing "wrong" with your phone.
Btw. Can you hit me up on gtalk? I need a device to test he patched dump_image on with a bad block. [email protected] is the adress.
-- nvm ---
This should be fixed in latest recovery.
http://forum.xda-developers.com/showthread.php?t=611829
Thanks to Apache14 for helping out with testing.
http://pastebin.com/aPiTzgKj
I was not able to flash 5.0.3 or 5.0.3.1
I'm still on 5.0.2
Related
Hi All,
I'm playing a bit with my new shiny toy (unlocked bootloader), and I have few questions:
1) Is there a way to do a fastboot boot (not fastboot flash boot) to keep the flashing (and working ) kernel in place while testing a new one ?
2) Is partition table locked by bootloader or can I repartition the device with fdisk directly on device or by flashing with FlashTool ? I'd like to reduce internal storage to add a new one to put my build.
3) What does fotakernel exactly ? I presume the response is no, else we would have separate recovery, but asking anyway: can't we replace it to have an alternate kernel booting ?
4) Regarding ICS firmware extract, I was not able to mount the extracted ext4, I tried 7z x + sin2img + pad to the proper number of sectors, but no dice, it mounts but it's corrupted. Doesn't seem to be a simg, so what am I missing ? Flashing + dd works, but it's a bit cumbersome.
Thanks,
LeTama
Good to see you here!
I am not sure if memory is locked to bootloader
I dont think so because ics changed the system partition size
We cant edit the .sin files in a .ftf
Sony included a file which contains a long key (like a long md5) which is unique
We cant fastboot boot. ..:... It is not included in the bootloader
If you need any info pm me
Sent from my LT22i using xda app-developers app
Hey Nicholtus!
Thanks for the reply!
So ICS upgrade changed partition layout ? On which model ? And upgrade preserved data or is it a global format ?
You're sure about fastboot boot ? Because it's doing something on Xperia S. Kernel doesn't boot, but something starts as device get stuck, so I was thinking that maybe I was not doing it the right way.
And system ext4, any idea ?
Regarding sin, I know about signature and that we have no way to bypass it.
Hi,
Layout is changed on the xperia s
I thought it was the system partition
If we find a way to bypass the sin header we can re partition the phone
I heard from DooMLoRD that the fastboot boot option is not included
Sent from my LT22i using xda app-developers app
letama said:
Hi All,
I'm playing a bit with my new shiny toy (unlocked bootloader), and I have few questions:
1) Is there a way to do a fastboot boot (not fastboot flash boot) to keep the flashing (and working ) kernel in place while testing a new one ?
2) Is partition table locked by bootloader or can I repartition the device with fdisk directly on device or by flashing with FlashTool ? I'd like to reduce internal storage to add a new one to put my build.
3) What does fotakernel exactly ? I presume the response is no, else we would have separate recovery, but asking anyway: can't we replace it to have an alternate kernel booting ?
4) Regarding ICS firmware extract, I was not able to mount the extracted ext4, I tried 7z x + sin2img + pad to the proper number of sectors, but no dice, it mounts but it's corrupted. Doesn't seem to be a simg, so what am I missing ? Flashing + dd works, but it's a bit cumbersome.
Thanks,
LeTama
Click to expand...
Click to collapse
I allso have problem with fastboot boot... see my post -> http://forum.xda-developers.com/showpost.php?p=32160466&postcount=22
About extracting ICS system.sin I integrated an tool into my CWM recovery so you can "in one click" trought menu extract these system.syn to system.tar
Allso new tool is added yesterday to new CWM version, but now its only for Xpreia GO, for backuping system partition and boot partition to flashable_zip, so you can "in one click" create recovery compatible zip format firmware like for HTC devices!!! I managed fresh ICS instalation in same way without needs for installing ICS bootloader...etc, just only fresh boot and system... see thread -> http://forum.xda-developers.com/showthread.php?t=1912865
munjeni said:
I allso have problem with fastboot boot... see my post -> http://forum.xda-developers.com/showpost.php?p=32160466&postcount=22
About extracting ICS system.sin I integrated an tool into my CWM recovery so you can "in one click" trought menu extract these system.syn to system.tar
Allso new tool is added yesterday to new CWM version, but now its only for Xpreia GO, for backuping system partition and boot partition to flashable_zip, so you can "in one click" create recovery compatible zip format firmware like for HTC devices!!! I managed fresh ICS instalation in same way without needs for installing ICS bootloader...etc, just only fresh boot and system... see thread -> http://forum.xda-developers.com/showthread.php?t=1912865
Click to expand...
Click to collapse
Thanks for the feedback...
I still didn't solve the fastboot boot. You made interesting tests, the problem is that for xperia S at least we need the rpm.bin and I don't see how we could have it in a standard htc img.
I should ask that someday on sony forum I guess.
Regarding the extract of ics, I solved the issue since then, the issue was an incomplete understanding of sin format. Since that time, I wrote a tool that can directly extract sin properly and Androxyde introduced similar changes in recent releases of FlashTool, so now it can be all done on PC without having to flash and dump.
I saw also your investigation regarding boot partitions, isn't the second one the one used for fotakernel ?
Just in case you want to look into this, don't bother if your bootloader is similar to Xperia S . I wanted to use it to have a second kernel for recovery, but after looking at bootloader, booting from this partition is blocked by bootloader as soon as you unlock your bootloader.
This is why I came to this, three different kernels boot with one dedicated to recovery .
letama said:
Thanks for the feedback...
I still didn't solve the fastboot boot. You made interesting tests, the problem is that for xperia S at least we need the rpm.bin and I don't see how we could have it in a standard htc img.
Click to expand...
Click to collapse
Is not rpm.bin part of the boot image? If yes than you can dump boot partition by dd and rename it to boot.img and it will be installed trought recovery without any problem because "ANDROID" img header have no sense for Sony because Sonys bootloader have nothing about checking these headers! You can add raw boot partition dump (boot.img) to recovery zip flashable format and recovery will install it without problem! Do not forget recovery backup create raw boot partition dump but renamed to boot.img, so .img is only prefix! Or maybe you mean something diferent? Maybe this can help you -> http://forum.xda-developers.com/showpost.php?p=31954337&postcount=9
About seccond boot partition... I think you are right! Its fota kernel? I erased these partition so I could not seen any problems and stranges by runing android so now I not understand whats use of these partition. Do you know how fota partition is trigered by bootloader? Maybe diferent boot reason? Maybe we can make something for writing boot reason before boot? For example writing bootreason that will boot recovery partition and if there is no trigers than recovery ramdisk will switch to boot ram sdisk? Is there any triger for example volume_up or something for entering into fota kernel? That have sense if there is some trigers! I just no want to edit boot image on every user reguest when some one make an updated kernel, that have no sense.... so only have sense is separated recovery partition...
How you decompiled bootloader, I tried but I am unable to find what is base address? Sony is really complicated for me now because I had a lot of HTC devices so Sony things is totally diferent than HTC...
munjeni said:
Is not rpm.bin part of the boot image? If yes than you can dump boot partition by dd and rename it to boot.img and it will be installed trought recovery without any problem because "ANDROID" img header have no sense for Sony because Sonys bootloader have nothing about checking these headers! You can add raw boot partition dump (boot.img) to recovery zip flashable format and recovery will install it without problem! Do not forget recovery backup create raw boot partition dump but renamed to boot.img, so .img is only prefix! Or maybe you mean something diferent? Maybe this can help you -> http://forum.xda-developers.com/showpost.php?p=31954337&postcount=9
Click to expand...
Click to collapse
Yes, I know and I meant something else... I thought you tried a pure mkbootimg and not an elf with an img file ext, I guess I missed something in your post.
About seccond boot partition... I think you are right! Its fota kernel? I erased these partition so I could not seen any problems and stranges by runing android so now I not understand whats use of these partition. Do you know how fota partition is trigered by bootloader? Maybe diferent boot reason? Maybe we can make something for writing boot reason before boot? For example writing bootreason that will boot recovery partition and if there is no trigers than recovery ramdisk will switch to boot ram sdisk? Is there any triger for example volume_up or something for entering into fota kernel? That have sense if there is some trigers! I just no want to edit boot image on every user reguest when some one make an updated kernel, that have no sense.... so only have sense is separated recovery partition...
Click to expand...
Click to collapse
I decompiled the firmware updater, and if I interpret correctly what I saw, fota is triggered by a simple "reboot recovery", so yes, it's a different reboot reason, but the standard one. The issue is that I saw explicit string messages in bootloader saying "Phone is unlocked, thus FOTA is not allowed to run!",0xA,0. I didn't find the test, but I tried to replace with dd the fota kernel and do a reboot recovery, the kernel was never launched. Basically, this kernel is launched when ota is downloaded and takes care of ota firmware installation, but I believe it only works on a locked bootloader with a signed ota kernel.
munjeni said:
How you decompiled bootloader, I tried but I am unable to find what is base address? Sony is really complicated for me now because I had a lot of HTC devices so Sony things is totally diferent than HTC...
Click to expand...
Click to collapse
I didn't, I just dumped the partition and located message strings. I was not able to decompile it too, code is weird and it's probably relocated and/or crypted.
letama said:
Yes, I know and I meant something else... I thought you tried a pure mkbootimg and not an elf with an img file ext, I guess I missed something in your post.
I decompiled the firmware updater, and if I interpret correctly what I saw, fota is triggered by a simple "reboot recovery", so yes, it's a different reboot reason, but the standard one. The issue is that I saw explicit string messages in bootloader saying "Phone is unlocked, thus FOTA is not allowed to run!",0xA,0. I didn't find the test, but I tried to replace with dd the fota kernel and do a reboot recovery, the kernel was never launched. Basically, this kernel is launched when ota is downloaded and takes care of ota firmware installation, but I believe it only works on a locked bootloader with a signed ota kernel.
I didn't, I just dumped the partition and located message strings. I was not able to decompile it too, code is weird and it's probably relocated and/or crypted.
Click to expand...
Click to collapse
Yeah, fotakernel is a problem. It can totally be used for recovery, but the bootloader just kills any attempt to boot it Needs some bootloader reverse engineering, and that's kinda dangerous.
Hmmm there is a few parts in "boot loader" partition so maybe dumping one by one part and decompiling? Anyone tried to comunicate with modem firmware... [email protected] commands? Is possible dumping ram memory by fastboot oem xxx ?? Is Gobi inside modem...?
K900 said:
Yeah, fotakernel is a problem. It can totally be used for recovery, but the bootloader just kills any attempt to boot it Needs some bootloader reverse engineering, and that's kinda dangerous.
Click to expand...
Click to collapse
Agreed! That's why I started to work on boot manager and it's more than enough for what I wanted to do. I'd have been happy with two kernels, three (well, more like 2,5 ) is luxury .
munjeni said:
Hmmm there is a few parts in "boot loader" partition so maybe dumping one by one part and decompiling? Anyone tried to comunicate with modem firmware... [email protected] commands? Is possible dumping ram memory by fastboot oem xxx ?? Is Gobi inside modem...?
Click to expand...
Click to collapse
No clue about modem and Gobi, however I disassembled fastboot, the only oem I see there is bootloader unlock.
letama said:
Agreed! That's why I started to work on boot manager and it's more than enough for what I wanted to do. I'd have been happy with two kernels, three (well, more like 2,5 ) is luxury .
No clue about modem and Gobi, however I disassembled fastboot, the only oem I see there is bootloader unlock.
Click to expand...
Click to collapse
Fastboot is actually open source in AOSP.
K900 said:
Fastboot is actually open source in AOSP.
Click to expand...
Click to collapse
Yes, but I was looking for hidden/unknown oem commands, found known
Is bootloader partition locked? We can write to him by dd?
munjeni said:
Is bootloader partition locked? We can write to him by dd?
Click to expand...
Click to collapse
The bootloader is not stored on the eMMC.
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
sj8023ld said:
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
Click to expand...
Click to collapse
Wow. We've got an expert here.
K900 said:
The bootloader is not stored on the eMMC.
Click to expand...
Click to collapse
I'm not surre you are right because I dumped bootloader from emmc by dd but not tried to write back :laugh:
---------- Post added at 06:26 PM ---------- Previous post was at 06:26 PM ----------
sj8023ld said:
You can convert system.sin to system.ext4 by using Flashtool and mount it in Linux
by command sudo mount -t system.ext4 floder
Click to expand...
Click to collapse
Are you tried? Yes you can mount but these data inside these mounted partition you can see very corupted!
munjeni said:
I'm not surre you are right because I dumped bootloader from emmc by dd but not tried to write back :laugh:
Click to expand...
Click to collapse
The lowest level thing is not there, and I'm pretty sure that's what blocks fotakernel.
munjeni said:
Are you tried? Yes you can mount but these data inside these mounted partition you can see very corupted!
Click to expand...
Click to collapse
It should work now with a recent flashtool. Androxyde implemented my sin extraction method that properly extract ext4.
Sent from my LT26i using xda app-developers app
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
maybe you should tell more info about your device, brand,chipset, etc ?
so people can be more easy to help.
just newbie suggestion, ignore this if its no help xD
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
lolet said:
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
Click to expand...
Click to collapse
The system image is not corrupted, because I can safely flash it using Clockworkmod. The filesystem is yaff2, and I have tried opening it using some software and my file is there. I think the problem lies on fastboot who failed flashing properly.
simple
yokowasis said:
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
Click to expand...
Click to collapse
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
I stuck with my Mate 9 Error mode numbers 11 and 2
MEGHSHAH said:
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
Click to expand...
Click to collapse
I would like to tell you my problem, I have a Mate 9 MHA-L09C605B111 which I did a rebrand a while ago and I'm with CUST 432 and installed the version of Oreo 8.0.0.368, a few weeks ago I received the update 369 via OTA. It was interesting to try; the problem is that I had open bootloader, TWRP Pretorian 3.2.0 and Root, take a terrible decision to do a relock of the bootloader.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in a tutorial
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
DooMLoRD said:
As the title states here are the 4.4.4 GPE System, Boot, and FOTAKernel images. The System is prerooted with busybox installed
system [UPLOADING]
MD5HASH: 49aa7777a1c60fc6742f12c2a31f1cdf
Size: 481 MB
Type: disk dump (compressed 7z)
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, flames start shooting from it... It was the other guy... I swear.... Flash at your own risk
Click to expand...
Click to collapse
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
scrubber said:
Hi DOOMLORD!
All users are waiting UPLOADING dump GPE 4.4.4 System!
P.S. Kernel now ported
Click to expand...
Click to collapse
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
DooMLoRD said:
stupid asymmetric ADSL speeds... get 4 MBPS download and only 256KBPS upload :crying::crying:
restarted uploaded twice yesterday...
will try again today
Click to expand...
Click to collapse
Ok. Will arrange topic
scrubber said:
Ok. Will arrange topic
Click to expand...
Click to collapse
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
No problem, any source and can parts
DooMLoRD said:
ok i give up...
again twice today it (filezilla) restarted midway from upload :'(
let me try uploading it to mega.co.nz
Click to expand...
Click to collapse
We can wait
joluke said:
We can wait
Click to expand...
Click to collapse
scrubber said:
No problem, any source and can parts
Click to expand...
Click to collapse
done
https://mega.co.nz/#!4RNx0Jaa!trTgJIXt8bB9R8LW6z3IVejSRV0MfqNvviD769UUsDo
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
pudgewack said:
Sorry for the newbie question, but what is the proper way to flash these files?
This is what I tried:
fastboot flash system <system.img>
fastboot flash boot <boot.img>
fastboot flash FOTAKernel <FOTAKernel.img>
I got an error for the boot.img (same error as ekrunch), but system and FOTAKernel successfully flash.
This is my first Sony device, so not too familiar with flashing this type of phone.
Thanks,
Matt
Click to expand...
Click to collapse
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
ekrunch said:
Forgive the long post
Click to expand...
Click to collapse
Nice, well explained post.
ekrunch said:
@DooMLoRD
Have you seen a XZU GPe get stuck and be unable to flash the boot partition? I get this every time I attempt to flash it.
Code:
[[email protected] 4.4.4 Stock Rooted]# fastboot flash boot boot_4.4.4.img
sending 'boot' (20480 KB)...
OKAY [ 2.462s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 2.466s
Now before we all start screaming bad download, here's the list of things that I've tried...
I've tried multiple boot images from various sources, validating md5 sums accordingly. I even tried the restoration procedure from your thread about restoring to stock.
I've tried to erase the partition using fastboot (which doesn't return an error) but I still can't flash after that.
I've tried using a different OS with fresh drivers. I normally run on a Fedora 20 box but I've tried on Windows 7 using Flashtool as well.
I've tried to wipe & clear cache. (Didn't think this would help, but what the hell?)
Anyway, I'm out of ideas. Any thoughts would be greatly appreciated.
And thank you for all of your hard work on the Xperia line. I've appreciated all of the posts in this forum, the system images and tutorials, as well as the custom recoveries!
Update : flashing boot.img from CM11 works fine. Clearly I'm missing something about how to flash the boot partition on this device. Apparently not all boot.img files are created equal...
Update 2 : I can flash the Advanced Stock Kernel with Dual Recovery without issue, so I'm going to flash my way back to 4.4.3 and go from there.
Fixed! : In the end, it was because I was using an ELF image and fastboot didn't like flashing it for some reason. I reverted my phone back to 4.4.3 using the stock system.img and FOTAKernel.img, then used the Advanced Stock Kernel with Dual Recovery, since they were all flashable via fastboot. Once the system was up, I used adb to push the 4.4.3 stock boot.img to the device and the did an adb shell, su'ed to root, and dd'it onto the boot device. Rebooted, OTA'ed it to 4.4.4. Done.
What a night. This is what I get for starting this project late...
Click to expand...
Click to collapse
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
ddslee said:
Has anyone with a broken camera tried flashing this image?
Does the camera work in 4.4.4 after the flash?
Click to expand...
Click to collapse
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
ekrunch said:
Forgive the long post, I'm sure some of this is repetitive, just trying to be complete for those who don't.
Sounds like you have the same exact problem as mine. Something about restoring an ELF image to the boot partition via Fastboot isn't working. Weird.
Alright, get ready to have some fun!
Get your device working again. I recommend using the 4.4.3 system.img/FOTAKernel.img and DooMLord's Advanced Stock Kernel with Dual Recovery. Worked like a charm for me. Get the 4.4.3 images from here and the kernel from here. Use "fastboot flash" accordingly for these 3 images. Note: The reason I use the custom kernel is b/c the 4.4.3 boot.img didn't flash correctly either.
Now you're running on 4.4.3 again, rooted. If you wiped data, don't bother signing in to your Google account, we're going to wipe again.
Now on to 4.4.4...
Okay so what we're going to do now is flash the boot.img for 4.4.4 on your running 4.4.3. Once you do this, the device probably won't boot Android again without some flashing in the boot loader, so brace yourself. :laugh:
First up, push the boot image to your device. You can do that with an ADB push, or ES File Explorer's handy FTP server, or just download the image with the phone. I used the 4.4.4 images from here. Get the boot-4.4.4.img on your device somehow and leave the system-4.4.4.img and FOTAKernel-4.4.4.img on your PC.
Code:
## [I](Not sure if you need the full path, I didn't push it this way)[/I]
adb push boot-4.4.4.img /storage/sdcard0/Download
Get a shell going
Code:
adb shell
Now that you're in the shell on your device, change to the right directory on the device, and copy the ELF image to the raw device using DD. (Everybody get your UNIX party hat out, we're going old school...)
Code:
su -
cd /storage/sdcard0/Download
dd if=boot4.4.4.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
Alright, you have a 4.4.4 boot image. Now get back to the boot loader.
Code:
adb reboot-bootloader
And now it's time to get those 4.4.4 images onto the system. I'd highly recommend a good wipe of data/cache while you're at it. ("fastboot -w" will do this for you.)
Code:
fastboot flash FOTAKernel FOTAKernel-4.4.4.img
fastboot flash system system-4.4.4.img
That should do it. Reboot, lock on to your Google account, then fire up the developer's menu and crank up ART, then enjoy your device on 4.4.4. (BTW, this still didn't fix my camera. :crying: )
Good luck everyone! Hope this helps someone out. And would somebody please chime in with the simple command that I'm missing that fixes this problem and avoids all of this foolery?
Click to expand...
Click to collapse
thanks for creating it i was lazy to write all this
DooMLoRD said:
....
my camera was working fine (could take pics in 4.4.3)...
after flashing to 4.4.4 i can no longer "take pics" using the camera app... though the camera preview is coming...
...
Click to expand...
Click to collapse
Preview comes out ok as the hardware does initialize. The issue is, from what I have seen and other who may have corroborated this, is the AF on the camera. You see, photosphere actually works well, just not the regular camera. Someone else mentioned that apps using infinity focus work as well.
My guess is that something in 4.4.3 and 4.4.4 (maybe in the kernel?) is looking for the missing DRM keys from devices with unlocked BL. Several people have already stated that they have no issues with their cameras, with the only difference being the locked bootloader in their devices. Considering that Sony had done something similar with the Z1 last year, I would not be surprised if it was the case here as well. Not sure why this would be the case for a GPE unit as it has no proprietary software (other than X-Reality)...
As I said, nothing but a guess albeit it does make sense (to me anyways).
Finally!!
Finally got my GPE to update using ekrunches excellent post..it took a little fiddling, (WIPE!! REALLY!!) but everything else went quite smoothly. I did find that fastboot -w didn't format partitions on cache and data and ended up in stock recovery to do a full wipe, after which things worked perfectly. Before that it was bootlooping on me. Didn't fix the camera though. I may leave this sucker mostly stock until someone fixes the camera...and on that note-I unlocked my bootloader immediately on getting the phone, before any updates ran. I've been considering the idea that if you unlocked before 4.4.2, that might be what's messing the camera up. I don't have any evidence for this though, it's just a guess.
DooMLoRD said:
you should read the "TYPE" mentioned in the OP
you cant flash ELF images using fastboot on newer s1 bootloaders
Click to expand...
Click to collapse
hahahaha I did. But it's the same for the boot and FOTAKernel images. What kept throwing me was one working while the other didn't but they were both the same type of file. How nice of Sony to do this... *cough cough*
DooMLoRD said:
Boot Kernel
MD5HASH: 5e8f72fd24ad3ebd993d6be621423e90
Size: 20 MB
Type: disk dump (ELF)
FOTAKernel
MD5HASH: ce19ddc8ef9c269f431c6387ec769002
Size: 16 MB
Type: disk dump (ELF)
Click to expand...
Click to collapse
So is there a better way to flash that boot image or is this it?
DooMLoRD said:
thanks for creating it i was lazy to write all this
Click to expand...
Click to collapse
You're quite welcome. Thank you for all of the dumps, kernels, write ups, etc. It is much appreciated. I've been leeching information from this forum for years with no contribution other than some donations so I'm glad to help out. I was beating my head up against the wall when I wrote that first post as it was driving me crazy that I couldn't flash that boot image. I've been spoiled by Nexus devices.
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Pallavgarg10 said:
Do i need to flash BootKernel and FOTAKernel as well or will simply flashing the system image work ?
Click to expand...
Click to collapse
Depends what you are trying to achieve?
Fully update your new GPe ZU?
From 4.4.2 to 4.4.4?
Already rooted or not, if not I would just flash the OTAs
I just want to update to 4.4.4 with as little modification as possible
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
PhilipL said:
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
Click to expand...
Click to collapse
I would trying to flash each image in factory image individually (Flash bootloader, flash boot, flash recovery, etc.), flashing them in the order the flash-all script would flash them (If your not sure which order it would flash them in just open the flash-all.bat or flash-all.sh as a text file and look at the order they are flashed in).
PhilipL said:
Hi
I'm trying to flash the factory image recently posted but getting the following error:
Code:
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1814213396 bytes
error: update package missing system.img
Looks like the Nexus 9 doesn't have enough allocated space to take the 820+MB zip file that contains the system images. I've updated to the latest version of SDK tools and have the newest Fastboot EXE, and device state is saying UNLOCKED on the HTC Fastboot screen.
Anyone have any ideas?
Regards
Phil
Click to expand...
Click to collapse
The missing.sig errors are normal. The missing system.img is not. Try downloading the factory image again.
Sent from my Nexus 5 using XDA Free mobile app
Same here, get the same error when trying to flash factory image. I did flash the files individually, but wasn't sure how to flash the vendor.img?
any update on this?
what do we do with vendor.img?
mingiunate said:
any update on this?
what do we do with vendor.img?
Click to expand...
Click to collapse
Just an update - based on the size of vendor.img, I assumed it was the same as userdata.
here are the steps i took to manually flash:
unzip image-volantis-lrx21l.zip
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata vendor.img
from tablet - select hboot
select factory reset
Done!
Hm, I successfully flashed vendor.img using
Code:
fastboot flash vendor vendor.img
But I'm not sure whether that was the correct way to go about things.
Hi
Thanks everyone for the replies/responses.
I will try and flash each image separately, however this shouldn't be necessary and means the image (or some setting on the Nexus 9) is wrong or broken. The whole point of the factory image is that it flashes with ease to get us back to a clean slate (well tablet), so a bit worrying they've not seemingly tested it too well.
Note I've flashed factory images dozens of times to Nexus 4, 5, 7 (both years) and never had this problem.
Perhaps Google will post a fix soon.
Best Regards
Phil
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
ilatimer1 said:
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
here are the steps i took to manually flash:
run the flash-all.bat up until the point where it fails
unzip image-volantis-lrx21l.zip
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash userdata vendor.img - looks like userdata should be vendor? - mine worked with userdata regardless
from tablet - select hboot
select factory reset
Done!
Hi
ilatimer1 said:
I think you need to run these two commands before you flash the rest of the .img files?
fastboot flash bootloader bootloader-flounder-3.43.0.0114.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
I did this as the first step as that is what is in the batch file with all/most Nexus factory images, didn't make a difference though. Something is definitely broken somewhere. However installing the images separately seems to work.
Best Regards
Phil
When was the last time you updated your SDK? Try downloading the latest SDK and run the flash-all
Hi
cundiffr said:
When was the last time you updated your SDK? Try downloading the latest SDK and run the flash-all
Click to expand...
Click to collapse
As I mentioned in the first post, after the first failure I updated my SDK to the very latest version, the result was the same. The image doesn't flash unless you separate out the individual parts and do it separately. Either the Nexus 9 isn't configured to allow enough space to accept the entire image (which clearly Google think it should as that is how they instruct it to be installed), or the image is broken in some way.
I'm sure it will get fixed at some point.
Regards
Phil
The same thing happened to my while I tried to flashed the newly released lollipop image to my nexus 5. I only had to restart my laptop and it worked.
mingiunate said:
[*]fastboot flash userdata vendor.img - looks like userdata should be vendor? - mine worked with userdata regardless
Click to expand...
Click to collapse
Yep, vendor should be flashed to the "vendor" partition.
userdata is emptied during factory reset.
Are you sure the prollem is with the tablet? When running a full ruu on other HTC devices, the failure to allocate space prollem arises from not having enough ram on the pc. Could be why flashing the images separately is working.
scotty1223 said:
Are you sure the prollem is with the tablet? When running a full ruu on other HTC devices, the failure to allocate space prollem arises from not having enough ram on the pc. Could be why flashing the images separately is working.
Click to expand...
Click to collapse
It's the image or tablet that's at fault. I ran the flashing process on a high-end machine equipped with 32 GB of RAM.
Restart your computer!
I sat here forever trying to figure why the hell i couldn't get 5.0 to flash to my nexus 5. I looked everywhere and didn't find anything that helped at all. I restarted my computer and tried again and it worked instantly. The first thing i said to myself was are you ****ing kidding me.... my computer was the issue. Dont tell yourself bull**** about how your computer is the bees knees. Mine may only have 16 gb of ram but restarting it worked perfectly.
Do i make a fullwipe, befor i flash the Image Files, if yes how i do this.
format system
format data
format cache
????????
fastboot flash userdata vender.img actually worked for me
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes. Trying different block sizes didn't help neither.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Thunder Storm said:
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Click to expand...
Click to collapse
Try getting rid of the bs part. Flash the image at it's normal size.
Sent from my XT1609 using Tapatalk
Thanks for your reply.
I flashed both TWRP and stock recovery without the bs parameter. Same results as before: it doesn't boot into recovery.