My unbranded non-rooted Desire would not update to a higher version than 2.09.405.8. While the OTA update to 2.10.405.2 downloaded it never installed - no errors, nothing. I tried to do it with update.zip but it never succeeded.
The regular reminders about the available download were annoying me (and I'm a compulsive updater) and so I decided to downgrade to see what would happen. I successfully installed 1.21.405.2 but can't get back to 2.09.405.8 or any other version. Using PB99IMG files to update to either 2.09.405.8 or 2.10.405.2 resulted in the following error.
Parsing....[SD ZIP]
[1] BOOTLOADER - OK
[2] RADIO_V2 - OK
[3] RADIO_CUST - OK
[4] BOOT -OK
[5] RECOVERY - Fail-PU
[6] SYSTEM - OK
[7] USERDATA - OK
[8] SPLASH1 - OK
Partition update fail!
Update fail!
Do you want to reboot device?
Following advise on another forum I downloaded and installed the latest RUU file 2.29.405.5 and it returned the following error.
ERROR [152]: IMAGE UPDATER ERROR
The Desire reported the same Partition Update error as mentioned above.
The same happened for the 2.29.405.2 RUU file also.
The 2.09.405.8 RUU file fails installation with ERROR [110]: FILE OPEN ERROR.
The only RUU file that worked was the 1.21.405.2 version so don't know what to do next???? Its wrecking my head now - why did I bother in the first place?
Have a bit of a problem updating back to 4.0.2.A.0.62. Since I got my phone all updates was done via PC Companion until I finally decided to take the big step forward and unlocking the bootloader and removing the sim lock. This was done by jinx13 (Thanks again!) My next big step was to root it simply just to get rid of all the bloatware.
My phone was already on the latest version, 4.0.2.A.0.62 via PC Companion as as I understand from the forums, it cannot be rooted and you have to downgrade and then upgrade OTA to maintain root as updating using PC Companion will remove the root functionality.
I got Flastool version 0.6.8.0 and then obtained the LT15i 4.0.2.A.0.42 Generic Global World ftf image from jlmc87's post "ARC/ARC S (ROOT.FTF&.IMG)4.0.2.A.0.62 Generic Global World+Flashtool+Ringtones+Other"
I downgraded to 4.0.2.A.0.42 without a hitch, then removed all the crap using constin's post "The Complete Comprehensive List of System Apps for Xperia Arc" as guidance. I then checked the OTA update and 4.0.2.A.0.62 was listed as available. I then proceeded to download and instaal this upgrade. The phone went through the motions of rebooting a few times and appeared to be upgrading but in the end a dialogue box shows "Software update. Could not install new software version. Try again" I have tried about seven times with the same end result before giving up on this option.
Next I tried to upgrade with a .img and proceeded to download Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img also from jlmc87's post, but how do I install this?
I searched a bit on the forums but could not get instructions suitable for a n00b like me to follow, so it was mostly trial and error and a lot more searching.
Once again I used flashtool and this time round I selected to flash using "Fastboot mode". In the fastboot toolbox I then selected "Reboot into fastboot mode (via ADB) and once this was done and drivers installed I selected the option "Select kernel to Flash" I selected the image and the process started.
I thought I did it and my phone is now back to the latest version whilst maintaining root, but unfortunately I got excited way too soon as the upgrade was not successfull as the "Image wont fit because the partition is too small"
Could this too small partition also be the reason why OTA upgrade didnt work? What to do next? Any help and advice greatly appreciated.
Here is the output of the logfile:
24/039/2012 00:39:27 - INFO - Device Status: FASTBOOT mode
24/040/2012 00:40:09 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img
24/040/2012 00:40:09 - INFO - Flashing selected kernel
24/040/2012 00:40:35 - INFO - FASTBOOT Output:
sending 'boot' (231660 KB)...
(bootloader) USB download speed was 9191kB/s
OKAY [ 25.993s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
FAILED (remote: Image won't fit, partition too small!)
finished. total time: 25.996s
24/040/2012 00:40:35 - INFO - Please check the log before rebooting into system
24/041/2012 00:41:20 - INFO - Log written to C:\Flashtool\flashtool_2012-03-23_12-21-56.log
24/021/2012 01:21:13 - INFO - Device will now exit fastboot mode and start booting into system
24/021/2012 01:21:13 - INFO - Device disconnected
24/021/2012 01:21:29 - INFO - Device connected with USB debugging off
24/021/2012 01:21:29 - INFO - For 2011 devices line, be sure you are not in MTP mode
24/021/2012 01:21:31 - INFO - Device disconnected
24/021/2012 01:21:33 - INFO - Device connected with USB debugging on
24/021/2012 01:21:33 - INFO - Connected device : LT15
24/021/2012 01:21:34 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
24/021/2012 01:21:34 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
24/021/2012 01:21:55 - INFO - Root Access Allowed
JJD809 said:
Have a bit of a problem updating back to 4.0.2.A.0.62. Since I got my phone all updates was done via PC Companion until I finally decided to take the big step forward and unlocking the bootloader and removing the sim lock. This was done by jinx13 (Thanks again!) My next big step was to root it simply just to get rid of all the bloatware.
My phone was already on the latest version, 4.0.2.A.0.62 via PC Companion as as I understand from the forums, it cannot be rooted and you have to downgrade and then upgrade OTA to maintain root as updating using PC Companion will remove the root functionality.
I got Flastool version 0.6.8.0 and then obtained the LT15i 4.0.2.A.0.42 Generic Global World ftf image from jlmc87's post "ARC/ARC S (ROOT.FTF&.IMG)4.0.2.A.0.62 Generic Global World+Flashtool+Ringtones+Other"
I downgraded to 4.0.2.A.0.42 without a hitch, then removed all the crap using constin's post "The Complete Comprehensive List of System Apps for Xperia Arc" as guidance. I then checked the OTA update and 4.0.2.A.0.62 was listed as available. I then proceeded to download and instaal this upgrade. The phone went through the motions of rebooting a few times and appeared to be upgrading but in the end a dialogue box shows "Software update. Could not install new software version. Try again" I have tried about seven times with the same end result before giving up on this option.
Next I tried to upgrade with a .img and proceeded to download Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img also from jlmc87's post, but how do I install this?
I searched a bit on the forums but could not get instructions suitable for a n00b like me to follow, so it was mostly trial and error and a lot more searching.
Once again I used flashtool and this time round I selected to flash using "Fastboot mode". In the fastboot toolbox I then selected "Reboot into fastboot mode (via ADB) and once this was done and drivers installed I selected the option "Select kernel to Flash" I selected the image and the process started.
I thought I did it and my phone is now back to the latest version whilst maintaining root, but unfortunately I got excited way too soon as the upgrade was not successfull as the "Image wont fit because the partition is too small"
Could this too small partition also be the reason why OTA upgrade didnt work? What to do next? Any help and advice greatly appreciated.
Here is the output of the logfile:
24/039/2012 00:39:27 - INFO - Device Status: FASTBOOT mode
24/040/2012 00:40:09 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img
24/040/2012 00:40:09 - INFO - Flashing selected kernel
24/040/2012 00:40:35 - INFO - FASTBOOT Output:
sending 'boot' (231660 KB)...
(bootloader) USB download speed was 9191kB/s
OKAY [ 25.993s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
FAILED (remote: Image won't fit, partition too small!)
finished. total time: 25.996s
24/040/2012 00:40:35 - INFO - Please check the log before rebooting into system
24/041/2012 00:41:20 - INFO - Log written to C:\Flashtool\flashtool_2012-03-23_12-21-56.log
24/021/2012 01:21:13 - INFO - Device will now exit fastboot mode and start booting into system
24/021/2012 01:21:13 - INFO - Device disconnected
24/021/2012 01:21:29 - INFO - Device connected with USB debugging off
24/021/2012 01:21:29 - INFO - For 2011 devices line, be sure you are not in MTP mode
24/021/2012 01:21:31 - INFO - Device disconnected
24/021/2012 01:21:33 - INFO - Device connected with USB debugging on
24/021/2012 01:21:33 - INFO - Connected device : LT15
24/021/2012 01:21:34 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
24/021/2012 01:21:34 - INFO - Android version : 2.3.4 / kernel version : 2.6.32.9-perf
24/021/2012 01:21:55 - INFO - Root Access Allowed
Click to expand...
Click to collapse
Dude, once you unlock the bootloader, you must not update your phone using any of the Sony update utilities like pc companion or ota update service.This would brick your phone.
Go to general section of this forum and search for the thread named. "FOTA Bricked devices" or something like that...The thread will guide you on how to get your phone back to normal.And the download links in the first post are not working I guess,so navigate yourself to the 16 or 17th pages of that thread to find the working download links.
Sent from my LT15i using XDA
Hi KingWickedd, thanks for your comments. My phone is not bricked, it is fine, all I want is to upgrade it to firmware version 4.0.2.A.0.62 whilst still maintaining root. Currently it is still on 4.0.2.A.0.42
I will not upgrate using PC Companion or OTA but can not install a pre-rooted IMG image of .62 firmware.
JJD809 said:
Once again I used flashtool and this time round I selected to flash using "Fastboot mode". In the fastboot toolbox I then selected "Reboot into fastboot mode (via ADB) and once this was done and drivers installed I selected the option "Select kernel to Flash" I selected the image and the process started.
I thought I did it and my phone is now back to the latest version whilst maintaining root, but unfortunately I got excited way too soon as the upgrade was not successfull as the "Image wont fit because the partition is too small"
Could this too small partition also be the reason why OTA upgrade didnt work? What to do next? Any help and advice greatly appreciated.
Here is the output of the logfile:
24/039/2012 00:39:27 - INFO - Device Status: FASTBOOT mode
24/040/2012 00:40:09 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\Pre-rooted_LT15i_4.0.2.A.0.62_Generic Global World.img
24/040/2012 00:40:09 - INFO - Flashing selected kernel
24/040/2012 00:40:35 - INFO - FASTBOOT Output:
sending 'boot' (231660 KB)...
(bootloader) USB download speed was 9191kB/s
OKAY [ 25.993s]
writing 'boot'...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
FAILED (remote: Image won't fit, partition too small!)
finished. total time: 25.996s
24/040/2012 00:40:35 - INFO - Please check the log before rebooting into system
24/041/2012 00:41:20 - INFO - Log written to C:\Flashtool\flashtool_2012-03-23_12-21-56.log
Click to expand...
Click to collapse
OMG! You are trying to flash a system image in the boot partition!?
Instead of using Flash Tool, use fastboot and command prompt to flash the img file to the system partition.
Code:
fastboot flash system system.img
Remember to download the fastboot package and then copy the img file to fastboot folder, rename it to system.img and run the above code in the command prompt after navigating to the fastboot directory.
Or simply use this : http://forum.xda-developers.com/showthread.php?t=1551073
Remember to flash that img file to "system" partition and not the boot partition.
Thank you very much!! That did the trick!! Thanks for pointing out the huge mistake I (almost) made!!
I updated using QuickIMG
Hi everyone.
I accidently bricked my ZUK while i'm flashing it by QFIL becouse i lost connection with my phone, and instead checked this out i turned it on. At first zuk starts vibrating about 10 sec non stop then starts never ending loop back - all this action was with no sign onto screen. Now loop looks like: one short vibe> long time nothing with no sign of life at the screen(this take about 30s)>one short vibe>...
When I take off baterry and i'll tried enter in to fastboot with port 9008 visible nothing new happend. It takes me to my never ending loop with black screen.
Sometimes i see my diod is lighting when i pressing any buttons (up or down with power - i really dont know when it shows).
Here is last few lines from flashing procedure log, maybe this will say something:
Code:
21:14:22: INFO: =======================================================
21:14:22: INFO: ==================== {SUCCESS} ========================
21:14:22: INFO: =======================================================
21:14:22: INFO: {percent files transferred 43.93%}
21:14:22: INFO: In handleProgram('system_23.img')
21:14:22: INFO: Looking for file 'system_23.img'
21:14:22: INFO: =======================================================
21:14:22: INFO: {<program> FILE: 'F:\Documets\Download\ZUK_stuff\Z2131\system_23.img'}
21:14:22: INFO: {<program> (126.01 MB) 258064 sectors needed at location 3573672 on LUN 0}
21:14:22: INFO: =======================================================
21:14:22: INFO: TARGET SAID: 'start 3573672, num 258064'
21:14:24: INFO: Overall to target 2.015 seconds (25.31 MBps)
21:14:24: INFO: {percent files transferred 45.48%}
21:14:26: INFO: Overall to target 3.578 seconds (35.22 MBps)
21:14:26: INFO: {percent files transferred 47.74%}
_____
| ___|
| |__ _ __ _ __ ___ _ __
| __| '__| '__/ _ \| '__|
| |__| | | | | (_) | |
\____/_| |_| \___/|_|
21:16:06: {ERROR: Could not read from '\\.\COM13', Windows API ReadFile failed! Your device is probably *not* on this port
}
Writing log to 'C:\Users\user\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\user\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Fail:FireHose Fail FHLoader Fail:Process fail
Finish Download
borsaldg said:
Hi everyone.
I accidently bricked my ZUK while i'm flashing it by QFIL becouse i lost connection with my phone, and instead checked this out i turned it on. At first zuk starts vibrating about 10 sec non stop then starts never ending loop back - all this action was with no sign onto screen. Now loop looks like: one short vibe> long time nothing with no sign of life at the screen(this take about 30s)>one short vibe>...
When I take off baterry and i'll tried enter in to fastboot with port 9008 visible nothing new happend. It takes me to my never ending loop with black screen.
Sometimes i see my diod is lighting when i pressing any buttons (up or down with power - i really dont know when it shows).
Here is last few lines from flashing procedure log, maybe this will say something:
Click to expand...
Click to collapse
You need diy wire method. Touch black and green wires. And power on phone while being connected to pc. After 4-5 sec. Seprate them. You will go into 9008 mode. Just flash qpst rom. Be happy.
P.s. in near future- You will get bootloader status as locked. Just post here one thing. Please. When you update from 2.0.133st to 2.5.104st. did you get any error. While updating.
Hello,
LOCKED
M8QL_UL
Hboot : 3.19.0.0000
[email protected]
0S-2.10.401.1
CID: HTC__031
MID : 0PKV1000
I have 3 problems :
- The Play Store appli doesn't work, once launched immediatly stopped.
- The first problem :
I lauch the system update to install 2.21.401.1
The installation stop at 25%, the M8s go to the recovery system. It stays several minutes then it reboots,and the updating system is cancelled.
- The second problem :
I have these messages :
"Unfortunately, Photos has stopped"
"Unfortunately, com.google.android.talk has stopped"
"Unfortunately,Google Play Movies & TV has stopped"
I need help,
Thank you
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?