Can somebody help me, please?
I can't install CWM, it says that the SU binary is not found.
I want to install the ultimate v11, but i'm stuck in getting CWM to work.
Thanks,
Vinicius
deliz said:
Can somebody help me, please?
I can't install CWM, it says that the SU binary is not found.
I want to install the ultimate v11, but i'm stuck in getting CWM to work.
Thanks,
Vinicius
Click to expand...
Click to collapse
Well you need root first.
ChikeD said:
Well you need root first.
Click to expand...
Click to collapse
This is what happens when i try to root via flashtool:
16/057/2013 15:57:25 - INFO - Device connected with USB debugging on
16/057/2013 15:57:26 - INFO - Connected device : MT27
16/057/2013 15:57:26 - INFO - Installed version of busybox : N/A
16/057/2013 15:57:26 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
16/001/2013 16:01:27 - INFO - Pushing C:\Flashtool\.\devices\MT27\busybox\1.20.2\busybox to /data/local/tmp/busybox
16/001/2013 16:01:28 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
16/001/2013 16:01:28 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
16/001/2013 16:01:29 - INFO - Pushing C:\Flashtool\custom\root\AdbRestore\RootMe.tar to /data/local/tmp/RootMe.tar
16/001/2013 16:01:30 - INFO - Now open your device and restore "RootMe" backup. Waiting ...
16/001/2013 16:01:30 - INFO - You have 60 seconds to follow the restore advice
16/001/2013 16:01:30 - INFO - Running adbrestoreexploit
16/001/2013 16:01:32 - INFO - Restore worked fine. Rebooting device. Please wait ...
16/001/2013 16:01:33 - INFO - Waiting for device
16/001/2013 16:01:34 - INFO - Device disconnected
16/001/2013 16:01:59 - INFO - Device connected with USB debugging on
16/002/2013 16:02:01 - INFO - Root hack did not work.
16/002/2013 16:02:01 - INFO - Cleaning hack files
16/002/2013 16:02:01 - INFO - Rebooting device. Please wait.
16/002/2013 16:02:02 - INFO - Device disconnected
deliz said:
This is what happens when i try to root via flashtool:
Click to expand...
Click to collapse
I guess you will have to find the method that work for your firmware version.
ChikeD said:
I guess you will have to find the method that work for your firmware version.
Click to expand...
Click to collapse
Im trying http://forum.xda-developers.com/showthread.php?t=1886460 now and this is the report:
{
"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"
}
deliz said:
Im trying http://forum.xda-developers.com/showthread.php?t=1886460 now and this is the report:
Click to expand...
Click to collapse
Find one the target your firmware version specificaly.
---------- Post added at 10:34 PM ---------- Previous post was at 10:21 PM ----------
Try this
http://forum.xda-developers.com/showthread.php?t=2029756
What worked:
Closed every ADB program (like PC companion)
Had to flash the version .180 and then used root_restore by bin4ry...after that i flashed .54 again and it was rooted (checked with rootchecker)
Then i could install CWM normally
:good:
Related
Hello
Flashtool can be downloaded on the Flashtool Homepage (on Installation tab)
As Flashtool was originally developped for X10, you can find a lot of information on the Original X10 Flashtool thread
Major update for 0.6.8.0 : Ability to now install CWM from Flashtool on locked bootloader for LT15/LT18.
Fastboot now works fine under linux
Major new feature :
- Fastboot toolbox for 2011 line devices.
- BL Unlock for X10 Mini/PRo and X8
Please post device related issues here in this thread
Does Dual touch work for 2.1 mini/pro
Does Dual touch work for 2.1 mini/pro?
sridharrn said:
Does Dual touch work for 2.1 mini/pro?
Click to expand...
Click to collapse
Firmwares posted on the X10 section are only for X10.
Androxyde said:
Firmwares posted on the X10 section are only for X10.
Click to expand...
Click to collapse
whats new? changelog?
Biodegradable said:
whats new? changelog?
Click to expand...
Click to collapse
Check the link at first post.
x10 mini pro
where can we find firmwares for u20i/e10i?
most people here are actually looking for the 2.1.1.A.0.6 update, including myself, to use with the FlasherTool.
but thanks for the tool!
how do you use this so that it'll recognize the firmware? i've tried moving the copies of firmware that I have but it doesn't detect any of them.
donetus said:
how do you use this so that it'll recognize the firmware? i've tried moving the copies of firmware that I have but it doesn't detect any of them.
Click to expand...
Click to collapse
last time i did a flash using flashtool, (0.24) i moved the fw to the 'firmware' folder. but those are .sin files, so i am not sure if that's the same thing when using ftf.
A new version (0.5.0.0) is here.
What's new for X10 Mini Pro comunity : BL Unlock for X10 Mini
Here is a small update that resolves the following issue :
Device not recognized correctly when plugged.
https://github.com/downloads/Androxyde/Flashtool/Flashtool-0.5.1.0-update.exe
can i unlock my boot loader with this directly?? or do i need to download s1 tool and all??
siddardha21 said:
can i unlock my boot loader with this directly?? or do i need to download s1 tool and all??
Click to expand...
Click to collapse
Yes you can.
how to unlocked BL with this flashtool?
Fantastic, that you add the option to unlock the BL. It doesn`t work so far with my u20i mini pro. I get only this:
{
"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"
}
when i plug my phone. Not even the "not reconized device message" installed the new github driver and the update. Nothing happend. I`m sure i did something wrong, didn`t y ?
domics said:
Fantastic, that you add the option to unlock the BL. It doesn`t work so far with my u20i mini pro. I get only this:
when i plug my phone. Not even the "not reconized device message" installed the new github driver and the update. Nothing happend. I`m sure i did something wrong, didn`t y ?
Click to expand...
Click to collapse
plug your phone and go to Help -> Check drivers
what is the output ?
Neither 0.5.1.0 nor 0.5.2.0 recognise my phone either (WinXP laptop), yet 0.5.0.0 works fine.
scook94 said:
Neither 0.5.1.0 nor 0.5.2.0 recognise my phone either (WinXP laptop), yet 0.5.0.0 works fine.
Click to expand...
Click to collapse
you mean it finds a phone and does not identify it (you are prompted for the type of phone you have ?) or absolutely nothing happens when you plug the phone ?
Androxyde said:
you mean it finds a phone and does not identify it (you are prompted for the type of phone you have ?) or absolutely nothing happens when you plug the phone ?
Click to expand...
Click to collapse
I just get the first line, "This level is successfully initialized"
When I run "Check Drivers" I get
23/031/2011 20:31:12 - INFO - List of connected devices (Device Id) :
23/031/2011 20:31:12 - INFO - - USB\VID_0FCE&PID_2138\434235313150445A4D51: OK
23/031/2011 20:31:12 - INFO - List of ADB devices :
23/031/2011 20:31:12 - INFO - - 434235313150445A4D51
23/031/2011 20:31:12 - INFO - List of fastboot devices :
Click to expand...
Click to collapse
Running Check Drivers on 0.5.0.0 gives me -
23/034/2011 20:34:15 - INFO - USB\VID_0FCE&PID_2138\434235313150445A4D51 : OK
23/034/2011 20:34:15 - INFO - USB\VID_0FCE&PID_2138&MI_00\6&5585D86&0&0000 : OK
23/034/2011 20:34:15 - INFO - USB\VID_0FCE&PID_2138&MI_01\6&5585D86&0&0001 : OK
Click to expand...
Click to collapse
scook94 said:
I just get the first line, "This level is successfully initialized"
When I run "Check Drivers" I get
Running Check Drivers on 0.5.0.0 gives me -
Click to expand...
Click to collapse
Ok I know where the problem is so
Will post here a fix that, I hope, will correct this issue.
scook94 said:
I just get the first line, "This level is successfully initialized"
When I run "Check Drivers" I get
Running Check Drivers on 0.5.0.0 gives me -
Click to expand...
Click to collapse
Can you try this file ?
HotFix
replace x10flasher.jar from Flashtool folder with this one on multiupload
Hello everyone,
I have a Xperia Z Ultra C6802 running on 14.2.A.0.290 locked bootloader with root and custom recovery.
Two days ago I flashed an audio mod zip using custom recovery, but it ended up with a bootloop. Then I tried to wipe the cache and dalvik cache from recovery, but did not realize that I checked the wipe system too. Now I also lost my custom recovery from the phone.
The phone stuck at Sony logo (not even showing a beam animation) like this:
{
"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"
}
Whenever I connect the phone to a wall charger, it will blink a red led notification and after few seconds will show the same Sony logo as shown above, but it will charge the battery (the charger gets hot but the phone also getting so hot because the screen will not turned off). I have to use hard reset button or power button + volume up to turn the phone off.
I downloaded some ftf files to be flashed in order to bring the phone back to a stock rom. I download some ftf from
http://forum.xda-developers.com/xpe...tf-depository-sony-firmware-releases-t2829387
The ftf files I downloaded are:
1. Xperia Z Ultra (C6802) 14.4.A.0.108 "Generic MY"
2. Xperia Z Ultra (C6802) 14.2.A.0.290 "Generic"
3. Xperia Z Ultra (C6833) 14.3.A.0.757 "EURO"
I also installed Flashtool 0.9.18.2 with Z Ultra drivers, flashmode driver, and fastboot driver on my PC (Win 7 64 bit). Whenever I try to flash a ftf file, I got errors like this:
08/000/2014 05:00:01 - INFO - Flashtool Version 0.9.18.2 built on 09-06-2014 22:30:00
08/000/2014 05:00:02 - INFO - Executing search strategies to find proxy selector
08/000/2014 05:00:02 - INFO - No proxy found for IE. Trying next one
08/000/2014 05:00:02 - INFO - Strategy firefox failed trying next one : No Firefox installation found
08/000/2014 05:00:02 - INFO - No proxy found for java. Trying next one
08/000/2014 05:00:02 - INFO - Syncing devices from github
08/000/2014 05:00:02 - INFO - Scanning devices folder for changes.
08/000/2014 05:00:12 - INFO - Pulling changes from github.
08/000/2014 05:00:20 - INFO - Devices sync finished.
08/000/2014 05:00:25 - INFO - Device disconnected
08/000/2014 05:00:31 - INFO - Selected Bundle for Sony Xperia Z Ultra (C6802). FW release : 14.2.A.0.290. Customization : R4B
08/000/2014 05:00:31 - INFO - Preparing files for flashing
08/002/2014 05:02:06 - INFO - Please connect your device into flashmode.
08/003/2014 05:03:36 - INFO - Device connected in flash mode
08/003/2014 05:03:36 - INFO - Opening device for R/W
08/003/2014 05:03:37 - INFO - Reading device information
08/004/2014 05:04:34 - INFO - Unable to read from phone after having opened it.
08/004/2014 05:04:34 - INFO - trying to continue anyway
08/004/2014 05:04:34 - INFO - Start Flashing
08/004/2014 05:04:34 - INFO - Processing loader.sin
08/004/2014 05:04:34 - INFO - Checking header
08/004/2014 05:04:34 - ERROR - Processing of loader.sin finished with errors.
08/004/2014 05:04:34 - INFO - Ending flash session
08/004/2014 05:04:34 - ERROR - Error in processHeader : 995 : The I/O operation has been aborted because of either a thread exit or an application request.
08/004/2014 05:04:34 - ERROR - Error flashing. Aborted
08/004/2014 05:04:34 - INFO - Device disconnected
This errors always showed up no matter ftf file I was trying to flash. I never get this kind of errors when I played around with Xperia ZL.
Whenever I connect the phone to PC it will automatically running in flashmode (without pressing power button + volume down).
I also tried to fix the phone with Sony PC Companion, but the software will not detect the phone when it ask me to connect the phone in flashmode (the PC recognize my phone).
Please help me guys to solve this problem. I need your help. I have no idea what to do :crying:
Perhaps you could try SUS
However the software is today discontinued but it still works
http://www.xperiablog.net/2014/07/24/rip-sus-sony-ends-support-for-update-service-software/
direct link, (SONY has removed their link from their website)
http://www.mediafire.com/download/2x830xdr3srskss/Update_Service_Setup-2.14.10.201407111005.exe
{
"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"
}
General:
Hey guys,
Welcome to my All-in-1-FlashTool for the Nexus 6
My target is to publish my All-in-1-FlashTool for several devices.
This tool helps you to flash .img files or similar things. It' a alternative for my Univeral_ADB-Helper tool which you can use as well.
It includes the most important commands to flash your phone.
The tool is an easy batch file, so you only need to unpack the .zip and run the batch file.
It is still in development and new features will be added soon.
I don't have this phone for my own, I've just developed this tool for its.
Your do everything at your own risk
Click to expand...
Click to collapse
Requirements: Unlocked Bootloader, Phone Drivers
Alternative: http://forum.xda-developers.com/android/software/utility-universaladb-helper-1-0-t2969165
Function:
- Flash Stock/Custom Recovery.img
- Flash Boot.img
- Factory Reset
- Wipe Cache & Dalvik Cache
- Reboot Recovery/Bootloader
- Unlock Bootloader
- Relock Bootloader
- Device Properties
- Root
Click to expand...
Click to collapse
Downloads:
https://goo.gl/kxYqqE
Click to expand...
Click to collapse
Changelog:
Newest version: 1.1 [25.05.2015]
- Take a look at the 2nd. post -
Click to expand...
Click to collapse
If you want to request this tool for your device, please send me an e-mail at:
[email protected]
Please report other bugs and hit "Thanks" if you appreciate this work.
Follow me on Google+ | Community
XDA:DevDB Information
FlashTool_Nexus6[Shamu], Tool/Utility for the Nexus 6
Contributors
Lars124
Version Information
Status: Testing
Created 2015-05-18
Last Updated 2015-05-18
Changelog:
25.05.2015: [1.1]
- Added "Wipe Cache" function
- Added "Lock Bootloader" function
- Some other minor changes
18.05.2015: [1.0]
- Initial Release
Click to expand...
Click to collapse
In
Update
1.1 available
please send me a link
i installed twrp on stock nexus 6 just out of the box google pushed ota for 7,1.1 and encrypted now have no recovery or abd
kudabee61 said:
please send me a link
i installed twrp on stock nexus 6 just out of the box google pushed ota for 7,1.1 and encrypted now have no recovery or abd
Click to expand...
Click to collapse
Did you realize that this thread wasn't updated since 4 years? So reviving it might not help much.
The behavior you see is perfectly normal.
If you flash a factory image the recovery you have is overwritten with the factory one.
Also adb has to be enabled in settings.
abd settings
Elektroschmock said:
Did you realize that this thread wasn't updated since 4 years? So reviving it might not help much.
The behavior you see is perfectly normal.
If you flash a factory image the recovery you have is overwritten with the factory one.
Also adb has to be enabled in settings.
Click to expand...
Click to collapse
As in the phone set for mtp? it will only connect to windows media player regardless sorry i have flashed w oden a bunch of Samsung motto is new to me and guess i dont quite understand the process yet ty for the info will read more forums to understand this process
Hi Guys
Why Flashtool Cannot Flash Build 273 or later?
This photo is error:
{
"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"
}
you need to add a flash script, you could use the flash script of the 266 firmware and rename it to 273 or 292
kistigun said:
you need to add a flash script, you could use the flash script of the 266 firmware and rename it to 273 or 292
Click to expand...
Click to collapse
thanks @kistigun
Can you explain further?
How to do it?
pmrk74 said:
thanks @kistigun
Can you explain further?
How to do it?
Click to expand...
Click to collapse
in the flashtool folder(C:/user/.flashtool or something like that) there is a folder devices(not sure it's called devices) look up the folder of your device(f5121 or f5122) and open that folder. Here you can find the flash scripts, now copy/paste the flash script file from 266 firmware and rename it into 273 or 292
also make sure you have the lastest version of flashtool installed
kistigun said:
in the flashtool folder(C:/user/.flashtool or something like that) there is a folder devices(not sure it's called devices) look up the folder of your device(f5121 or f5122) and open that folder. Here you can find the flash scripts, now copy/paste the flash script file from 266 firmware and rename it into 273 or 292
also make sure you have the lastest version of flashtool installed
Click to expand...
Click to collapse
how to copy/paste flash script file from 266 firmware?where is it 266 script on firmware?
pmrk74 said:
how to copy/paste flash script file from 266 firmware?is where 266 script on firmware
Click to expand...
Click to collapse
In the folder of your last screenshot copy/past the file F5121_34.2.A.0.266 rename it to F5121_34.2.A.0.273 or F5121_34.2.A.0.292 after this you can flash 273 or 292 firmware
kistigun said:
In the folder of your last screenshot copy/past the file F5121_34.2.A.0.266 rename it to F5121_34.2.A.0.273 or F5121_34.2.A.0.292 after this you can flash 273 or 292 firmware
Click to expand...
Click to collapse
Very thanks @kistigun
Flashed and Done.
pmrk74 said:
Very thanks @kistigun
Flashed and Done.
Click to expand...
Click to collapse
Hi I am using windows 7 but when I go to that location for the flash scrip it shows two files, 34.0.fsc. and 34.2.fsc, can you please upload or send me the files in your devices folder?
carlos1984 said:
Hi I am using windows 7 but when I go to that location for the flash scrip it shows two files, 34.0.fsc. and 34.2.fsc, can you please upload or send me the files in your devices folder?
Click to expand...
Click to collapse
Hi my friend
Download Devices.zip and unzip and replace F51XX Folder to C:/Users/Your User/.flashtool/devices
Thanks man. I did what you said but it still errors. So what i did to fix it was to download the 0.9.23.2 x10flasher.jar and replaced the original . and then when i hit flash it asked if i wanted to use the new fsc. So it worked flashed android 6 on xperia x android 7.
lol
carlos1984 said:
Thanks man. I did what you said but it still errors. So what i did to fix it was to download the 0.9.23.2 x10flasher.jar and replaced the original . and then when i hit flash it asked if i wanted to use the new fsc. So it worked flashed android 6 on xperia x android 7.
Click to expand...
Click to collapse
hi man~I downloaded the 0.9.23.2 x10flasher and when i hit flash it didn't ask me to use the new fsc and still "No flash script found." don't know what to do now.
I was also want to flash 6 from 7
@kistigun I still have the same issue. I tried the original files that come with Flashtool, they are only called 34.0.fsc/34.2.fsc of it asked me to use the 34.0.fsc i said yes no luck for me there. so i thought maybe the file is broken and i took the files from @pmrk74 i took his 34.0.xxxx.fsc, renamed it like my rom (34.0.A.1.289) and it asked me to use that fsc i said yes. still not working.
06/030/2017 16:30:30 - INFO - Opening device for R/W
06/030/2017 16:30:30 - INFO - Reading device information
06/030/2017 16:30:30 - INFO - Unable to read from phone after having opened it.
06/030/2017 16:30:30 - INFO - trying to continue anyway
06/030/2017 16:30:30 - INFO - Phone ready for flashmode operations.
06/030/2017 16:30:30 - INFO - Opening TA partition 2
06/030/2017 16:30:30 - INFO - Start Flashing
06/030/2017 16:30:30 - INFO - No loader in the bundle. Searching for one
06/030/2017 16:30:36 - INFO - No matching loader found
06/030/2017 16:30:36 - WARN - No loader found or set manually. Skipping loader
06/030/2017 16:30:36 - INFO - Ending flash session
06/030/2017 16:30:36 - ERROR - null
06/030/2017 16:30:36 - ERROR - Error flashing. Aborted
06/030/2017 16:30:37 - INFO - Device connected in flash mode
Can someone help me with this problem? I've problem when try to flash stock ftf firmware file using flashtool, can someone please tell me how to solve it?
08/038/2017 15:38:25 - INFO - Device connected in flash mode
08/038/2017 15:38:40 - INFO - Selected Bundle for Sony Xperia M(C1905). FW release : 15.4.A.1.9. Customization : Indonesia
08/038/2017 15:38:40 - INFO - Preparing files for flashing
08/038/2017 15:38:41 - INFO - Please connect your device into flashmode.
08/038/2017 15:38:42 - INFO - Opening device for R/W
08/038/2017 15:38:42 - INFO - Device ready for R/W.
08/038/2017 15:38:42 - INFO - Reading device information
08/038/2017 15:38:42 - INFO - Phone ready for flashmode operations.
08/038/2017 15:38:42 - INFO - Opening TA partition 2
08/038/2017 15:38:42 - INFO - Current device : Unknown: May 9 2014/12:58:25 - YT910L3Q6M - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25 - Unknown: May 9 2014/12:58:25
08/038/2017 15:38:42 - INFO - Closing TA partition
08/038/2017 15:38:42 - INFO - Start Flashing
08/038/2017 15:38:42 - INFO - Processing loader.sin
08/038/2017 15:38:42 - INFO - Checking header
08/038/2017 15:38:42 - INFO - Flashing data
it's only stuck in that mode and never going through to another process?
EDIT : Additional Log "Read error :31 : A device attached to the system is not functioning. "
Please anyone????
I'd try a different file to flash. Could be an issue. I need more info. Android version, for one. Is usb debugging enabled? Also why bother with stock ROM? Just get a custom ROM that's close to stock and flash it from recovery. It's much easier
godkingofcanada said:
I'd try a different file to flash. Could be an issue. I need more info. Android version, for one. Is usb debugging enabled? Also why bother with stock ROM? Just get a custom ROM that's close to stock and flash it from recovery. It's much easier
Click to expand...
Click to collapse
different FTF? that sony ftf 4.3 firmware for xperia m (c1905) with 15.4.A.1.9 build number, that flash in flashmode using flashtool by androxyide and i'm using windows 10 with installed flashmode and fastboot drivers for xperia m. But that log happen when i'm reflashing stock ROM, i've cpu problem with custom ROM and that make me must revert to stock rom for a while and i need stablity because i'm in semester examination in my university now.
Please, can you help me?
godkingofcanada said:
I'd try a different file to flash. Could be an issue. I need more info. Android version, for one. Is usb debugging enabled? Also why bother with stock ROM? Just get a custom ROM that's close to stock and flash it from recovery. It's much easier
Click to expand...
Click to collapse
Okay, i can full flash system now using s1tool software. but i get this error and i can't avoid or even fix this error from flashing. Can you help me with this error?
{
"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"
}
HDR is your dynamic range if if not mistaken. I'd try a different download of the ftf still. I also did some Google searching and one thing that it could be us you don't have the correct PC drivers. Also you may have locked your bootloader when downgrading or trying to flash stock. Try a different ftf download, something could be corrupt. If that fails then its phone related and not firmware related. Its going to be a step by step process to isolate the problem.
Try EMMA instead.
godkingofcanada said:
HDR is your dynamic range if if not mistaken. I'd try a different download of the ftf still. I also did some Google searching and one thing that it could be us you don't have the correct PC drivers. Also you may have locked your bootloader when downgrading or trying to flash stock. Try a different ftf download, something could be corrupt. If that fails then its phone related and not firmware related. Its going to be a step by step process to isolate the problem.
Click to expand...
Click to collapse
XperienceD said:
Try EMMA instead.
Click to expand...
Click to collapse
Thanks, I'm try to re-download new ftf from xperiafirm using flashtool and I can flash firmware without problem. But i don't know why my old firmware can give this problem, because I'm usually use this firmware.
Anyway, thanks for all of your suggest
Sent from my Xperia M using XDA Labs
Nicklas Van Dam said:
Thanks, I'm try to re-download new ftf from xperiafirm using flashtool and I can flash firmware without problem. But i don't know why my old firmware can give this problem, because I'm usually use this firmware.
Anyway, thanks for all of your suggest
Sent from my Xperia M using XDA Labs
Click to expand...
Click to collapse
You are welcome. I am glad your phone is now working.