Develop Bugs

[Q] Help with installing CM7.2.0 FXP049 from the FreeXperia Project

Okay, Ive watched the Noob video when making an account and i have searched around for a while but no luck
Okay basically, I need help! I have an Xperia Arc S and wanted to install the FXP CM7 Rom onto it. Ive seen all the tutorials and unlocked the bootlader, rooted my device etc.
Then I downloaded the CM7 files from the Thread for FXP and then pasted the boot.img file to the fastboot folder. Then i launched fastboot and flashed the boot.img and it was successful. The two zip folders are already in the SD card. I then restart my phone and try to press the volume down key and it doesn't launch the screen that is supposed to appear or anything. and it's just stuck on the boot loop ( I assume that's the blacklight back screen before the Sony erricson logo appears on booting acoording to other threads) I then keep having to flash back to 4.0.2.A.0.42.ftf via the flashtool file.
I then downloaded the recoveryARC file etc and it launches to the Clockworkmod recovery thing at recovery and i try to install the update.zip but it says No such file exists.
What am I doing wrong after I flashed the new boot.img ? Help please.
Thank you guys.

Did you wipe data?
Sent Via LT15i - FXP46-CM7

Is it required to wipe data? As in wipe data in the Clockwordmod before I install the update.zip? Or..

dinesh690 said:
Is it required to wipe data?
Click to expand...
Click to collapse
It does state so in the instructions to do so so yes.
Sent Via LT15i - FXP46-CM7

Didn't work
Okay thanks but that doesn't seem to help it. I booted the recoveryARC.img and it goes into Clockworkmod recovery menu. I wiped data, wiped cache partition etc and try to apply udate from sdcard and it still says E:Can't open /sdcard/udapte.zip No such file or directory Installation aborted.
What am I doing wrong.
This is my fastboot log:
C:\Users\Dinesh\Contacts\Roms etc\fastboot_with_Android_USB_file\fastboot_with_A
ndroid_USB_file\fastboot>fastboot flash boot boot.img
sending 'boot' (5272 KB)...
(bootloader) USB download speed was 9212kB/s
OKAY [ 0.590s]
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.090s]
finished. total time: 1.680s
C:\Users\Dinesh\Contacts\Roms etc\fastboot_with_Android_USB_file\fastboot_with_A
ndroid_USB_file\fastboot>fastboot boot recoveryARC.img
downloading 'boot.img'...
(bootloader) USB download speed was 9207kB/s
OKAY [ 0.465s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.002s]
finished. total time: 0.467s
C:\Users\Dinesh\Contacts\Roms etc\fastboot_with_Android_USB_file\fastboot_with_A
ndroid_USB_file\fastboot>
In my SDCard on the phone i have the GAPPS zip and the CM7 zip which is called update(.zip)
(That boots me into the Clockworkmods, which is where everything starts to go wrong for me) Is the method im doing wrong? But i can't seem to use the method in the FreeXperia thread as after I flash the boot.img file provided, it just goes into a bootloop so i can't press down the volume down key or anything obviously. Thanks again.

Okay Guys I fixed this, I basically installed FXP047 which seems to work perfectly fine, and boots into the freexperia logo and i have installed CM7 now. Moreover, the E:Can't open /sdcard/udapte.zip No such file or directory Installation aborted problem was fixed by ejecting the Arc S from the PC safely and not just pulling out the cable Sorry for wasting your time guys. BUT THANK YOU CM7 IS AWESOME. If anyone has this similair problem then use this and hope it helps

i have a little problem.
-Place the CyanogenMod update.zip file on the root of the SD card.
-Optional: Place the Google Apps .zip on the root of the SD card also.
Click to expand...
Click to collapse
what is the root of sd card? where is it? i put the files in the sd card, but after that i cant flash (this commands dont work fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot)

I have a question
If i have 4.0.2.A.0.58 , can i install the CM 7.2 ?
thanks

Hi
Please , someone can help with my question?
Thanks
Sorry for my bad english

xviu said:
If i have 4.0.2.A.0.58 , can i install the CM 7.2 ?
Click to expand...
Click to collapse
Yes, you can.
http://forum.xda-developers.com/showthread.php?t=1299729

dp94 said:
Yes, you can.
http://forum.xda-developers.com/showthread.php?t=1299729
Click to expand...
Click to collapse
Thanks for your help

[Q] Galaxy W I8150 Only Samsung Logo !!!

I Am Very New With This Type Of Phone. Please Help Me.
When I Power On The Phone, It Show Only Samsung Logo And Continue Restarting !!! It Can't Go In ''Recovery Mode'' !! Can Go ''Download-Mode'' And RAMDUMP Mode.I Was Try To Flash It With Download Mode And This It The Screen Short
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> amss.mbn download..
<1> 1/7 Finished.
<1> adsp.mbn download..
<1> 2/7 Finished.
<1> boot.img download..
<1> 3/7 Finished.
<1> system.img.ext4 download..
<1> 4/7 Finished.
<1> cache.img.ext4 download..
<1> 5/7 Finished.
<1> recovery.img download..
<1> 6/7 Finished.
<1> preload.img.ext4 download..
<1> 7/7 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
Click to expand...
Click to collapse
But After That Phone Did Not Start Automatically, I Remove The Battery And Power On But Same Problem Like Before
What Is The Problem ? I Made Any Mistake ?? Any Way To Solve The Problem ???
Please Help Me.
Best Regard

maybe your recovery is missing. try to flash recovery, coz i had this similiar problem before. but removing the battery is a bit risky I think, why don't you power off it with power button but with long press?

Do you have any recovery? If so, is it the stock one or the custom one?

minatovladoski said:
maybe your recovery is missing. try to flash recovery, coz i had this similiar problem before. but removing the battery is a bit risky I think, why don't you power off it with power button but with long press?
Click to expand...
Click to collapse
Thank You Sir,How To Flash Recovery ?? Where To Put The File Sir ??? I Have This File recovery-clockwork-5.5.0.4-ancora.tar.md5 Can I Use It ?
Best Regard

SyzwnFrzRdz said:
Do you have any recovery? If so, is it the stock one or the custom one?
Click to expand...
Click to collapse
Thank You Sir, I Have This File recovery-clockwork-5.5.0.4-ancora.tar.md5 Can I Use This File ?? I don't Know This Is Custom Or Not.
Best Regard

Have you decided to go to stock ROM or customed ?
Sent from my GT-I8150 using xda premium

Nazrul Islam said:
Thank You Sir,How To Flash Recovery ?? Where To Put The File Sir ??? I Have This File recovery-clockwork-5.5.0.4-ancora.tar.md5 Can I Use It ?
Best Regard
Click to expand...
Click to collapse
use odin, put cwm in one package.
but i'm not sure it's your recovery causing this problem.
would you please write what you do to your device? and i saw you tried to flash a ROM via odin, what kind of rom you flash?

same problem here
I'm in Indonesia, using stock ROM DXLA2, then rooted my phone, and updating with Kezra V4 and V6 Supercharger, and this morning i found my SGW bootloop, have tried to odin but still no change at all
Any suggestion?

have you tried wipe all data after flashing new rom?
be sure to backup everything important

lncx said:
have you tried wipe all data after flashing new rom?
be sure to backup everything important
Click to expand...
Click to collapse
can't even enter recovery mode, only in download mode?
is there a way to wipe without entering recovery mode?

if you can enter donwload mode, then you able to flash new stock rom with Odin.
Or if you decide to flash custom rom, flash CVM then choose custom rom.
A lot of tutz here and or visit kaskus lounge for Gal W user.

lncx said:
if you can enter donwload mode, then you able to flash new stock rom with Odin.
Or if you decide to flash custom rom, flash CVM then choose custom rom.
A lot of tutz here and or visit kaskus lounge for Gal W user.
Click to expand...
Click to collapse
Hi..
Sorry to say, this problem is cannot be solved by flashing
So don't wasting your time for figure this out...
BTW are you came from Indonesia ?
This problem happened often in Indonesia -_-
Read it carefully
http://forum.xda-developers.com/showthread.php?t=1506765

Rio Saputro said:
Hi..
Sorry to say, this problem is cannot be solved by flashing
So don't wasting your time for figure this out...
BTW are you came from Indonesia ?
This problem happened often in Indonesia -_-
Read it carefully
http://forum.xda-developers.com/showthread.php?t=1506765
Click to expand...
Click to collapse
Yes, I'm from Indonesia, thanks for the information, will go to SSC this evening...
I'll report it later when done

Hello every body ,any one sole this problem.i also face same problem in my i8150 just Samsung logo blinking.i try to boot repair with riff box and try in spt box with different files.and also with odin but all is same plz if any one can find this solution share it here..

irfansamsia said:
Hello every body ,any one sole this problem.i also face same problem in my i8150 just Samsung logo blinking.i try to boot repair with riff box and try in spt box with different files.and also with odin but all is same plz if any one can find this solution share it here..
Click to expand...
Click to collapse
did exactly what rio saputro said, get to SSC, have my wonder flashed but failed, then wait for about 3 days, and get a new board in my wonder

boot loop after factory reset

Basicly my gio is stuck on boot loop
ived tryed a lot of flashing roms with Odin.
My gio can enter download mode but cant enter recovery mode.
Can some one help me please
i would be apreciated
ived started this thread but someone said that the place to be is in the development section so...
http://forum.xda-developers.com/showthread.php?p=40806190#post40806190

Delete this thread bro

Andrea19 said:
Delete this thread bro
Click to expand...
Click to collapse
Ty Bro ,thats really the help i need. :good:

mnunes01 said:
Ty Bro ,thats really the help i need. :good:
Click to expand...
Click to collapse
It's an GENERAL thread thing. It's not that hard to know I think... development thread is for things you develop. Ask a moderator to move it. If everyone place his problems and questions in the dev sections...
Sent from my GT-5660 using xda premium

hi man, which rom and which recovery was you using when you did that factory reset?

ro_bo said:
hi man, which rom and which recovery was you using when you did that factory reset?
Click to expand...
Click to collapse
i think it was on the 2.2.1 the recovery i dont really know.
FlemishDroid i know you're rigth, but man, you really remember my boss talking about putting hours into the redmine....
anyway and since you're rigth my thread is:
http://forum.xda-developers.com/show...0#post40806190

mnunes01 said:
i think it was on the 2.2.1 the recovery i dont really know.
FlemishDroid i know you're rigth, but man, you really remember my boss talking about putting hours into the redmine....
anyway and since you're rigth my thread is:
http://forum.xda-developers.com/show...0#post40806190
Click to expand...
Click to collapse
Try flashing 2.3.6 and don't select auto reboot in odin and i don't think that CWM v5.x.x.x works on 2.2

CataHd said:
Try flashing 2.3.6 and don't select auto reboot in odin and i don't think that CWM v5.x.x.x works on 2.2
Click to expand...
Click to collapse
One stupid question, do i need to have the microsd inserted to flash or enter recovery mode ?

mnunes01 said:
One stupid question, do i need to have the microsd inserted to flash or enter recovery mode ?
Click to expand...
Click to collapse
I think you need sdcard because CWM saves some files there but i don't really know because i never used my phone without sdcard

CataHd said:
I think you need sdcard because CWM saves some files there but i don't really know because i never used my phone without sdcard
Click to expand...
Click to collapse
try'd everithing I could imagine, flashed 2.3.6, 2.3.5, 2.3.3, always boot loop
flashed 2.2.1 odin still recognizes the phone on usb connecting, but screen went completely black thoug i had brick the phone that time but still can enter donwloading mode. flahsed again 2.3.3 and boot loop again.
Iam starting to think that it was something to do with ext4 and rfs, maybe some partitions went bad...
Any clue?
I would really apreciate a recovery mode screen....

Download firmware from (is 2.3.6, January 2013) here (link 1)
Use ODIN from here (link 2)
To enter download mode hold volume-down button + home then turn on the phone.
Open ODIN press OPS button and point Odin to the OPS file from the archive from link 2
Check "One package" then press One Package button and point Odin to the file from link 1
Click Start and wait, I don't know what can go wrong now - I never really understand how people can brick their phones, I personally flashed today Froyo, then got back to ICS!
Remember! If you flash Froyo and you want to come back to Gingerbread/ICS/CM/etc., first flash a 2.3.5/2.3.6 rom! Only after flashing 2.3.5/2.3.6 you can flash CWM recovery and install your custom ROM

bgm92 said:
Download firmware from (is 2.3.6, January 2013) here (link 1)
Use ODIN from here (link 2)
To enter download mode hold volume-down button + home then turn on the phone.
Open ODIN press OPS button and point Odin to the OPS file from the archive from link 2
Check "One package" then press One Package button and point Odin to the file from link 1
Click Start and wait, I don't know what can go wrong now - I never really understand how people can brick their phones, I personally flashed today Froyo, then got back to ICS!
Remember! If you flash Froyo and you want to come back to Gingerbread/ICS/CM/etc., first flash a 2.3.5/2.3.6 rom! Only after flashing 2.3.5/2.3.6 you can flash CWM recovery and install your custom ROM
Click to expand...
Click to collapse
ty for the response. I'ved tryied that, but still in bootloop... i really think i got a corrupeted partitions or something...
anyway theres is the odin log:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
<1> 1/9 Finished.
<1> qcsbl download..
<1> 2/9 Finished.
<1> oemsbl download..
<1> 3/9 Finished.
<1> amss download..
<1> 4/9 Finished.
<1> arm11boot download..
<1> 5/9 Finished.
<1> boot.img download..
<1> 6/9 Finished.
<1> recovery.img download..
<1> 7/9 Finished.
<1> system.rfs download..
<1> 8/9 Finished.
<1> csc.rfs download..
<1> 9/9 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
when it gets to hte reset pda, the phone just starts blinking the screen and never reboot

man try erase your sd with cm and then try put a good rom on the sd when the sd is on another phone...than do a full wipe (not to the sd)
and flash-it on your phone...i think these will work...
soory for my bad englesh

FyJy said:
man try erase your sd with cm and then try put a good rom on the sd when the sd is on another phone...than do a full wipe (not to the sd)
and flash-it on your phone...i think these will work...
soory for my bad englesh
Click to expand...
Click to collapse
But didn i need to have acess to recovery mode on my phone to do that?

i had the same problem as you
what i did was disconnect the phone from usb and take out the battery
then i entered recovery and factory reset
and it worked
i flashed 2.3.6 for my country, find out what firmware you need and flash only that

Try flashing recovery.img manually using fastboot, then reboot to recovery (via fastboot)

Help - I've stuffed my Pixel C up and cant get beyond recovery

Hi everyone,
I was in the process of unlocking my bootloader, flashing a recovery and rooting my Pixel C with the Skipsoft Toolkit when something went wrong.
The bootloader unlocked (30 sec screen and chirp) and I flashed TWRP but it got stuck there.
TWRP kept asking for the password to decrypt data, and now everytime I start my Pixel C it goes straight there again.
I've tried different options in the Skipsoft Toolkit but nothing seems to work and goes back to the 'Mount Decrypt Data' TWRP screen.
A few things that Ive tried are listed below.
Any help with me getting back to stock and having the Pixel C working again would be greatly appreciated.
Thankyou
4. Root/UnRoot/Disable Encryption/Flash Stock Boot/Check Root Status [ADB Mode]
7. Unroot, Uninstall Busybox and Restore Stock Boot/Recovery [ADB Mode]
1. Push file, reboot to Custom Recovery and install manually [simplest method]
Working out the best location to set for Internal Storage..
Waiting for Adb Mode ...
Device mode detected [recovery adb]
Android Version Detected: 7.1.2 Serial Number:
Pushing Unroot-SuperSU.zip to: /sdcard/
root\Unroot-SuperSU.zip: 1 file pushed. 0.1 MB/s (3574 bytes in 0.064s)
File/s pushed successfully
Device mode detected [recovery adb]
Device Serial Number:
Rebooting to Fastboot Mode and continuing..
Device mode detected: Fastboot Mode
Device Serial Number:
Device Bootloader State: Locked
Booting TWRP recovery-twrp-3.1.1.1-ryu.img ..
creating boot image...
creating boot image - 13051904 bytes
downloading 'boot.img'...
OKAY [ 0.323s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.328s
An Error Occured
Press any key to return to the Main Menu..
5. Rename Recovery Restore Files [Fix system flashing stock recovery on boot]
Device Bootloader State: Locked
Booting TWRP recovery-twrp-3.1.1.1-ryu.img ..
creating boot image...
creating boot image - 13051904 bytes
downloading 'boot.img'...
OKAY [ 0.331s]
booting...
FAILED (remote: image verification failed)
finished. total time: 0.331s
An Error Occured
Press any key to return to the Main Menu..
9. Download/Extract/Flash Google Factory Stock Image [Flash Part or Whole Rom]
2. Flash Google Stock Image [in the put_google_factory_image_here\device folder]
image-ryu-opm1.171019.015.zip
ryu-opm1.171019.015-factory-64c65be2.zip
Are you ready to proceed? Type y[yes] or n[no]:
Google Stock Image found [.zip format] in the correct folder.
Filename of image to flash: ryu-opm1.171019.015-factory-64c65be2.zip
Processing archive: put_google_factory_image_here\GooglePixelC\image-ryu-opm1.171019.015.zip
Extracting android-info.txt
Extracting boot.img
Extracting cache.img
Extracting recovery.img
Extracting system.img
Extracting vendor.img
Everything is Ok
Starting Flash Process..
Flashing Bootloader Image..
target reported max download size of 268435456 bytes
sending 'bootloader' (16384 KB)...
OKAY [ 0.416s]
writing 'bootloader'...
FAILED (remote: unsupported command)
finished. total time: 0.431s
An error occured when flashing the image
Try rebooting the device manually back to fastboot mode:
1. Unplug the usb cable
2. Stand the tablet in landscape mode [power button on top] and Press and Hold the
Power and Volume Down buttons for 10-15 seconds until it reboots to Bootloader
mode. Then select 'Switch to fastboot mode' using the volume button and press
the power button. The device will say 'Waiting for fastboot command...'
From the main menu in the Toolkit choose the Download/Extract/Flash menu, then
select Flash previously downloaded image.
Sometimes there is a glitch in the flash process and doing it again will fix it.

You can skip the password and change data file system partition to ext3. Then install custom systems like lineage os.

rhmanoa said:
You can skip the password and change data file system partition to ext3. Then install custom systems like lineage os.
Click to expand...
Click to collapse
Hi and thanks for the response.
How do I change data file system partition to ext3?
I can skip the decrypt password screen in TWRP and go into the general settings, but I dont know how to convert the system partition to ext3.
Thanks

Go to wipe data/cache then advanced wipe then change partition setting select data partition change to ext3.

Xperia M boot loop after 29 sec. whatever installed/done (TWRP, ROM sony flash tools)

Dear Xperia M experts of the xda community,
I really messed up my Sony Xperia M single sim C1905, android 4.3 and it is continious (boot?) looping, that means whatever mode I put the device (TWRP, fastboot, ADB, Hardware: Flash-Mode (as well while flashing system.sin), Fastboot-Mode) -> reboot latest after 29 seconds.
Xüeria M is in usage since 5 yeas and has long lasting battery - on day at least - an did a very good job. Device was bought in Germany. It never let me down, so I somehow stick to it. I'm new to the xda forum.
With some tricks I can install working TWRP 2.8.7.0 or CWM6 (ohter TWRP will freeze), but there is no chance to install a file bigger than approx. 80 MB within the given time.
So formatting an deleting works with TWRP 2.8.7.0.
I "just" wanted to update to a new ROM i.e. like this Resurrection Remix Nougat v5.8.5
https://forum.xda-developers.com/legacy/xperia-m/rom-resurrection-remix-nougat-v5-8-0-t3512094
Before I made a full android backup to my SD Card by installing twrp-3.0.2-0-nicki.img. At this ime TWRP worked properly.
As well I used the Sony Android 4.3 Backup & Restore tool in advance to backup via SD card (At this time the android system was still working).
I wanted to install a new ROM (CM13, cM14, Resurrection Remix Nougat v5.8.5, or something similar xda-dev. is full of options) according to this really nice instruction:
https://www.youtube.com/watch?v=SJBLq19NrfY
Bottomline is, whatever I found out to be a possible solution -> reboot latest after 29 seconds.
Here is what I did until now (since 7 days and night I'm really trying hard, and google must be emty...). I learned a lot about android devices.
P.S.: 3 days ago I escaped the boot loop and could enter TWRP2.8.7 - but I messed up because my knowledge (full data wipe) wasn't to big at this time and I didn't remember what I exactly did in the night before. Now I could bit myself into the ass....
The good point: I 'm convinced, that the bricked device still has a chance. I have more ideas, so at the end, but I don't have such deep knowledge as an developer.
Here we go: my Computers are
Lenovo M57, Win10
Lenovo W540, Linux Mint 20
1) checked if my Xperia M can be unlocked -> yes. Mobile Phone rooted with SuperSu. At this time under still working Android
2) installed minimal ADB & Fastboot (on both computer)
3) got my sony bootloader unlock code and unlocked bootloader via Terminal:
fastboot oem unlock 0x<mycode>
-> OKAY
4) Start twrp-3.0.2-0-nicki.img and tried to install ROM. Something went wrong an I got into a boot loop. Then my trouble started. ADB didn't work anymore. Only fastboot and flash mode.
At the end nothing seemed to work an final I decided to flash new
1) install sony moile flash tool and drivers. I reinstalled the drivers und WIN10 several times until all systems were running. Under Linux, things were easier and there were no driver issues at all.
At the end I installed 0.9.8, 0.9.12.1, 0.9.13.0, 0.9.16.0, 0.9.18.6, 0.9.20.0, 0.9.22.3, 0.9.28.0, 0.9.29.0
on windows and linux.
2) for all flash tool I had the same issue:
I could flash all ftf files (*.sin) perfectly and without error message, except:
system.sin
ended with an error message (because device disconnected after 29 seconds)!
Same procedure for all these firmwares:
C1905_15.1.C.2.8_Customized ZA.ftf (stock firmware)
C1905_15.4.A.1.9_Customized MEA.ftf
C1905_15.4.A.1.9_Customized+UK.ftf
Xperia_M_C1904_4.3_15.4.A.1.9.ftf
I tried all firmwares with all versions of flashtools (yes I really did...)
error message:
20/014/2020 18:14:17 - INFO - Current device : C1905 - YT910V0YHX - 1274-5576_R2C - 1272-2325_15.4.A.1.9 - WORLD-i_15.4.A.1.9
20/007/2020 21:07:14 - INFO - Processing system.sin
20/007/2020 21:07:14 - INFO - Checking header
20/007/2020 21:07:14 - INFO - Flashing data
20/007/2020 21:07:43 - ERROR - Processing of system.sin finished with errors.
20/007/2020 21:07:43 - INFO - Ending flash session
20/007/2020 21:07:43 - ERROR - null
20/007/2020 21:07:43 - ERROR - Error flashing. Aborted
20/007/2020 21:07:43 - INFO - Flashing finished.
I also flashed for all flash tool versions everything except system.sin -> worked with nearly all versions perfectly
An then flashed for all flash tool versions only system.sin -> worked produced the same error messeage after 29. sec.
Another issue: after flashing (with system.sin error) I wasn't able to enter ADB mode again, so only possibility is i.e. to
fastboot flash boot twrp-3.0.2.0-nicki.img -> only then I will be able to access ADB interface again during TWRP bootup.
With the Sony boot-up (logo appears) no ADB access is granted. But I partially solved, see 4.0)
3) Because of system.sin error I tried to access the device via TWRP in order to install CM13, CM14 or Resurrection Remix Nougat v5.8.5, see https://forum.xda-developers.com/legacy/xperia-m/rom-resurrection-remix-nougat-v5-8-0-t3512094
fastboot flash boot twrp-3.0.2-0-nicki.img -> Frezze of Startimage at boot -> reboot after 29 sec.
fastboot flash boot twrp-3.0.1-0-nicki.img -> Frezze of Startimage at boot -> reboot after 29 sec.
fastboot flash boot twrp-3.0.0-0-nicki.img -> Frezze of Startimage at boot -> reboot after 29 sec.
fastboot flash boot twrp-2.8.7.0-nicki.img -> full action possible, but: -> reboot after 29 sec.
fastboot flash boot <file from here>:
https://forum.xda-developers.com/showthread.php?t=2480556
-> full action possible, but: -> reboot after 29 sec.
Re-gaining ADB access for 29 sec.:
4.0) OK again flash with flash tool - I kept sticking to 0.9.18.6 and C1905_15.1.C.2.8_Customized ZA.ftf (stock firmware) which seem to have reproducible results:
fastboot flash boot twrp-2.8.7.0-nicki.img -> full action possible, but: -> reboot after 29 sec.
Then for 29 sec. I could access the internal storage via Linux und use ADB:
What I tried to interupt bootloop:
4.1)
adb shell
dd if=/sdcard/twrp-2.8.7.0-nicki.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
-> OKAY, but has no effect -> -reboot after 29 sec.
4.2)
adb shell
dd if=/sdcard/twrp-3.0.2.0-nicki.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
-> OKAY, but has no effect, that is: current twrp in boot install stays in place -> -reboot after 29 sec.
yes, I rebooted into recovery as well: VOL-UP but nothing changed
4.3)
try to interrup boot loop with
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc
4.4)
use flashtool to flash everything except system.sin an then:
fastboot flash system system.sin
error message:
target didn't report max-download-size
sending 'system' (1012135 KB)...
FAILED (remote: data too large)
finished. total time: 0.002s
fastboot flash -S 512M system system43.sin
error message:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 484528096 is not a multiple of the block size 4096
sending sparse 'system' 1/2 (517800 KB)...
error: write_sparse_skip_chunk: don't care size 484528096 is not a multiple of the block size 4096
FAILED (data write failure (Protocol error))
finished. total time: 14.530s
data failure by: -> -reboot after 29 sec.
4.4)
I can do:
# fastboot erase system:
erasing 'system'...
OKAY [ 0.294s]
finished. total time: 0.294s
# fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.128s]
finished. total time: 0.128s
But not:
# fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
# fastboot erase data
erasing 'data'...
FAILED (remote: Command not allowed)
finished. total time: 0.002s
# fastboot format system
Formatting is not supported for file system with type ''.
# fastboot format data
Formatting is not supported for file system with type ''.
# fastboot format userdata
Formatting is not supported for file system with type ''.
4.5) I'm aware of all button combinations
Vol. Up + USB = Fastboot Mode
Vol. Down + USB = Flash Mode
Vol Up during startup = boot recovery (if flash wir system.sin error -> no effect nothing appears)
4.6 Sony PCC
Tried, but can't register the device anymore.
4.6.1) Software reapair -> USB & Vol. Down attached to PC -> Devices is locked is stated.
4.6.2) If connected before and repair process is started, the process end after 29 sec. ahhhh!
4.7)
With
fastboot flash boot twrp-2.8.7.0-nicki.img
I can access the interal storage, mount all partition, do a factory reset, wipe data, dalvik cache etc. no effect -> reboot after 29 sec.
fastboot flash boot twrp-3.0.2-0-nicki.img or any other 3.x.x.x for nicki will free at the start-up picture. Don't ask me why, shouldn't be this way.
So the issue: I can't backup the 3.0.2.0 with 2.8.7.0. At least I tried. The issue are:
a) no partitons are asked for an twrp does not know where to write
b) -> reboot after 29 sec. even if it would work...
4.8)
After flash rooted with
-magiskV20.zip
and tried to install or do something useful with TWRP2.8.7.0 nicki
-> reboot after 29 sec.
4.9)
Also this doenst finally work, but its a very nice instruction, an works "best" until the 29 sec. are over
https://forum.xda-developers.com/showthread.php?t=2480556
-> -reboot after 29 sec.
5.0) My possibilities are limited an I only have some ideas but dont know how to proceed
5.1) Why does the loop after flash show the sony logo and then the devices seems to be fored to go into reboot. For me it looks like there is a file or a process on the boot partition, which tries to find something - if not -> interrupt an reboot.
Possible solution find the file an interrupt this Sony procedure. Maybe someone has a clue where to search or which file could be corrupted.
5.2) Flash tool is sending packages (can be seen from the debug mode). for system.sin the reboot comes aber about 150 packages are transferred to the system partition. I could think to start sending the file packages 1 to 150 first, then 151 to 300, then 301 to 450 etc.
Is there any possibility to write packagewise with flashtool?
5.3) Since I can access the internal storage I thought about just copying the linux files from a 4.3 Android there, or the files which are required by the sony boot loop checking process, so the boot loop interrupts and the linux an fix itsself.
5.4) Is it possible to place an smaller recovery file at the adequate place, so that there is a chance to rebuild the linux system sucessively
5.5) Is it possible to flash an small system file, which acesses the *.tft file on the sd card an can do the installation process (only possible if the device stops rebooting after 29 sec.)
5.6) Extrakt something useful from the TWRP 3.0.2.0 backup, that might interrupt the boot loop? I don't know how to.
5.7) Maybe things are simple and somebody has a set of proven files for Xperia C1905 (tft, DRM-fix.zip? ), that would help to exclude failures possibilities.
You see I spent over a week on this issue, now my holiday time is over, and I'm almost fed up. But I have the ambition to fix it. Of course its easier an cheaper to simply buy a new android device - but thats not the point, since I'm a technical geek, but have no experiance fixing android devices.
So I'm positive, that some superman in this forum here in this xda-forum who has an idea.
Appreciate any ideas from experts.
Best regards
Dirk

Hey bro,
it's been 3 years since I first flashed my Xperia M so I am not sure whether I can give any solutions but try this if it helps: https://forum.xda-developers.com/xp...cypheros-3-1-cheesecake-t3505798/post72627720

hhjadeja007 said:
Hey bro,
it's been 3 years since I first flashed my Xperia M so I am not sure whether I can give any solutions but try this if it helps: https://forum.xda-developers.com/xp...cypheros-3-1-cheesecake-t3505798/post72627720
Click to expand...
Click to collapse
Hey bro, tnx a lot for your reply. Good hint. Tried to install according your instruction, partially in some way an advance to before: ...
1. Boot into TWRP recovery
->fastboot flash boot bootAOSP.img
->TWRP3.0.2.0 booted properly and this was new I could it would fully work again!
-> This step OK
2. Wipe system, data, cache, dalvik - cache
->TWRP3.0.2.0 boot - and deleted each single partition bit by bit (I had to hurry), because: After 29. sec. reboot.
The system, cache, data, sd card etc. were properly mounted and no errors were shown
-> This step OK
3. Flash ROM
-> ->TWRP3.0.2.0 boot and installed ROM: aoscp_nicki-3.6.3-20170610-unofficial.zip
will start to install the ROM without error message, until the screen turns black und is interruptecd by -> reboot
After this mount "system" error is indicated and with the help of flashtool 09.18.6 the *.ftf firmeware, see above, will properly fix the partiation and everything is mountable again -> so I ran over the proceedure several times.
At least an advance, compared to the state before, where only TWRP 2.8.6.0 was fully operational ( until -> reboot after approx. 29 sec.)
Some how the reboot has to be stopped.
I found a log file unter /cache/recovery/last_log (opend it shortly before the . reboot occoured) an here are the boot protocols. I saw Jan 2020
So some old system files still remain in the linux depths oif the android which seem to cause the reboot.
I managed to extract via TRWP the recovery.log to sd card. I don't know how to attach the log-file here. Just ask for it via PM.
The pity is, whatever I (sucessfully) do - I have appro29 sec. time. Its like mission impossible and the bomb . If this time lock could be broken things would appear possible. Shell script to fix (but I don't have any Idea)?
Best regards an Thank you for your help/ideas.
Dirk
P.S.:
What I tried as well:
Somehow it has a similar effect like here: reboot after 30 sec. reason Firmware corrupted
https://forum.xda-developers.com/xperia-z/help/solved-phone-disconnects-flashmode-t2240960/page2
so maybe someone has proper tested firmeware for 4.1 or 4.3...
Boot loop issue. A pity this didn't work
https://forum.xda-developers.com/showthread.php?t=2513568&page=2
because system.sin flash doesnt finish, because the mobile is switching off due to reboot after 29 sec.
I also tested backup C1905 stock firmware
https://forum.xda-developers.com/showthread.php?t=2703161
CWM and everything installs nicely until comes to flash proceedure, which is nicely starting, but interrupted by the continious reboot...
Maybe a little chance is this, but I can't manage to find sony flash tool 0.6.6 and according driver. Maye somebody still has the stuff?
Solve system.sin flashing error with sony flash tool 09.18.8.8 and sony flash tool 0.6.6
https://forum.xda-developers.com/showthread.php?t=2658952&page=24
Page 24:
Hi all, if anyone is having trouble flashing with flash tool because usb debugging isn't enabled error then do this procedure.......
1. Dowload latest flash tool 0.9.18.8 and also version 0.6.6
2. Try use the latest version first to Flash the tft rom. NOTE: remember the file it has error flashing e.g on my experia sp file system.sin was not able to Flash bcoz usb debugging error (enable usb debugging and unknown sources) ALL THE REST of the files flashed ok!
3.try flash again the rom but this time tick system.sin (or error file) in flashtool to exclude it from flashing. Make sure all other files are included. Also tick all wipe caches options and flash rom without system.sin (or error file).
4. Flash procedure will work. Now disconnect phone and leave it off without restarting it.
5. Uninstall flashtool latest version 0.9.18.8 and install flashtool 0.6.6 old version and open it to Flash the same rom BUT THIS TIME only select the system.sin file (or error file) to be flashed and rest excluded. Make sure all wipe options in flashtool are enabled and Flash! THE FLASH WILL WORK WITHOUT USB DEBUGGING ERROR and your phone will be fixed!
Maybe a chance?