Flashtool error "0017" - Xperia Z2 Q&A, Help & Troubleshooting

I have decided to stick with the new European unbrande .402 flashtool and have flashed a lot of little things from mobile without problem until it started flashing "System" here he stopped and threw the error: "Processing of system.sin finished with errors." .
I have searched xda and have not found that it may be that mistake, but I have a couple of questions,? Before connecting the mobile must check "USB debugging" and "unknown origins"?
Can also be the FTF I had got me some error?
I tested on a computer with Windows 8.1,and another with Windows Xp,with different usb cables and differents usb ports,always get the same error
The fact is that the cell would not start and I could retrieve it with Update Service.
Can anyone help?
Thanks and sorry for my bad english

This is the log file

pacomicro said:
Before connecting the mobile must check "USB debugging" and "unknown origins"?
Can also be the FTF I had got me some error?
Click to expand...
Click to collapse
"USB debugging" must be checked but I'm not sure about "unknown origins". If you don't have USB debugging checked it will not start flashing, giving an error. At least that happened to me. I tuned on the phone, I checked "USB debugging" and gave it another try.
Just to be sure, download another firmware (from another source) and try connecting the phone again in flash mode to see if FlashTool sees it.

Well.
I've tried with "Usb debugging" checked,also "unknown origins"..and get the same error.
I've tried two sources for firmware...and get the same error.
This is driving me crazy,in theory is very simple, but I do not find solution.

pacomicro said:
Well.
I've tried with "Usb debugging" checked,also "unknown origins"..and get the same error.
I've tried two sources for firmware...and get the same error.
This is driving me crazy,in theory is very simple, but I do not find solution.
Click to expand...
Click to collapse
Have you tried to download the ftf again?

harfot said:
Have you tried to download the ftf again?
Click to expand...
Click to collapse
Yes,two times,differents sources.
can you recommend some reliable source to download it again?

what surprises me, is that more flashes several parts and the error is always when you try to flash system.sin...

Try using another computer, fresh drivers, etc. I have no other idea.

More info about my software

any more suggestions?

pacomicro said:
any more suggestions?
Click to expand...
Click to collapse
your on windows right?
anyway in your flashtool folder there should a drivers folder within there should be a exe or something of sorts open it and select flashtool fastboot and any Z2 files
next open flashtool as admin (right click)
next redownload the FTF, some odd reason Z2 FTFs corrupt very easily

Try to check is there new flashtool.
Then, set flashtool and choose firmware, let the flashtool prepares firmware for flashing and connect device when system shows msg.
It's very common that device exit flashmode while flashtool prepares files...
Sent from my D6503 using Tapatalk

if you look at the log I put in the second post,will see that all is well until it starts to flash the "system.sin",until then everything goes well.
I'll re-download the ftf and try again, maybe the file is corrupt when downloading because I have low download speed.

Don't know if this is any help but when I was using FlashTool to flash firmwares it would pause for between 4-5 mins when flashing system.sin which made me think there was a issue, I just left it & after the above mentioned time it finished flashing with no issues.

BanziBaby said:
Don't know if this is any help but when I was using FlashTool to flash firmwares it would pause for between 4-5 mins when flashing system.sin which made me think there was a issue, I just left it & after the above mentioned time it finished flashing with no issues.
Click to expand...
Click to collapse
this is not my case, is the flashtool itself which aborts the operation.
thanks anyway

I downloaded the German Unbranded 17.1.1.A.0.402.....and I have not had any problems,so we can reach the conclusion that the other downloaded files for some reason were corrupt.
Thank you all for your help.

Glad you got it sorted mate, so far I have not had any issues with downloaded firmwares, maybe a antivirus program you have that scans downloads might be corrupting them?

BanziBaby said:
Glad you got it sorted mate, so far I have not had any issues with downloaded firmwares, maybe a antivirus program you have that scans downloads might be corrupting them?
Click to expand...
Click to collapse
when a new major upgrade, KK 4.4.3?,I'll try to completely disable the program that I think is causing my problem (Spybot)

I wouldn't bother with Spybot mate, it a well known resource hog with protection turned on, v1 was ok with it disabled but v2 was crippling my cousins PC, removed it & installed 360 Internet Security & the PC was fast & speedy again.

If your on windows best anti virus is windows security essentials
Tested, proven and fact
Sent from my D6503 using XDA Premium 4 mobile app

Related

[Q] X10 Proces system error, cant do anything.

Hello all,
I was using this rom: http://forum.xda-developers.com/showthread.php?t=1002836
for a few weeks and all was working fine until today. All just worked fine until some moment that all stoped to work. Now i dont have any service anymore and when i try to reboot it and it starts again i get:
-No widgets load
-"Process system is not responding" Force close or wait.
-Cant boot into xRecovery
-Flashtool wont recognize the phone
-phone keeps making notification sounds for no reason
-i get no service
-cant connect to wifi
-wont recognize SD card
-randomly freezes
I found on this forum that this problem causes because i install a new busybox thats what created this error. But i cant get back in to xrecovery again or back to my SD card since my pc doeosnt connect to my phone. So also SEUS doesnt connect, what can i do to reset it all or atleast to get back into xrecovery?
Yours,
anyone have any solutions? i'm in the same exact boat.
Try reinstalling xrecovery from flashtool. You should be able to even with force closes.
Sent from my X10i using XDA App
Go to Application -> Dev Tools -> Bad Behavior -> Crash the system server then reboot. Give it a few minutes to settle then if that doesn't work, download xrec v0.3 from below. If xrec installs then wipe cache & clear Dalvik cache. If none of those work you have no choice but to reflash.
http://www.mediafire.com/?eyihuzn4h96xw4c
Hi I had this exact same problem so I reflashed but now I can't get rooted. Can anybody help me root?
06bgoggin said:
Hi I had this exact same problem so I reflashed but now I can't get rooted. Can anybody help me root?
Click to expand...
Click to collapse
How exactly are you trying to root? Have you tried the flashtool, z4root or super one click?
Sent from my X10i using XDA App
Lockon Stratos said:
How exactly are you trying to root? Have you tried the flashtool, z4root or super one click?
Sent from my X10i using XDA App
Click to expand...
Click to collapse
I've tried all of them. Flashtool has always worked for me in the past but all I can do on it at the moment is flash the stock firmware it won't let me click the root option.
Z4root would go through everything but then when I donloaded busybox it said I wasn't rooted.
And with super one click it would spend for ever trying to find the device, never find it then the programme would freeze.
Do you have any other ideas?
06bgoggin said:
I've tried all of them. Flashtool has always worked for me in the past but all I can do on it at the moment is flash the stock firmware it won't let me click the root option.
Z4root would go through everything but then when I donloaded busybox it said I wasn't rooted.
And with super one click it would spend for ever trying to find the device, never find it then the programme would freeze.
Do you have any other ideas?
Click to expand...
Click to collapse
Z4root & Superclick are my backup procedure in case I'm not infront of a pc and I always use the flashtool to root.
Are you sure usb debugging is enabled? I know I've made that mistake before then realized that it wasn't enabled. Stock 2.1 does not enabled this function by default as far as I know.
Sent from my X10i using XDA App
Lockon Stratos said:
Z4root & Superclick are my backup procedure in case I'm not infront of a pc and I always use the flashtool to root.
Are you sure usb debugging is enabled? I know I've made that mistake before then realized that it wasn't enabled. Stock 2.1 does not enabled this function by default as far as I know.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
Yeah I made sure I wasn't making that mistake I've tried turning usb debugging on the plugging in my phone, plugging in the phone then turning on usb debugging, I have no idea whats going on. It has really confused me :/
06bgoggin said:
Yeah I made sure I wasn't making that mistake I've tried turning usb debugging on the plugging in my phone, plugging in the phone then turning on usb debugging, I have no idea whats going on. It has really confused me :/
Click to expand...
Click to collapse
BTW what firmware are you using? If you are still on the branded firmware that might be the reason why so flash a generic 2.1 firmware then try rooting again. Here's an example:
http://forum.xda-developers.com/showthread.php?p=15711725#post15711725
If you look at the last few posts Uberlight25 was using branded firmware and had the same problem as yours. After flashing generic 2.1, he/she was able to root again.
Good luck.
Lockon Stratos said:
BTW what firmware are you using? If you are still on the branded firmware that might be the reason why so flash a generic 2.1 firmware then try rooting again. Here's an example:
http://forum.xda-developers.com/showthread.php?p=15711725#post15711725
If you look at the last few posts Uberlight25 was using branded firmware and had the same problem as yours. After flashing generic 2.1, he/she was able to root again.
Good luck.
Click to expand...
Click to collapse
Thanks but I worked out that the problem was that I didn't have the debug driver installed, I fixed this by reinstalling PC Companion
Cannot flash x10, driver missing
Metalbuster said:
Hello all,
I was using this rom: http://forum.xda-developers.com/showthread.php?t=1002836
for a few weeks and all was working fine until today. All just worked fine until some moment that all stoped to work. Now i dont have any service anymore and when i try to reboot it and it starts again i get:
-No widgets load
-"Process system is not responding" Force close or wait.
-Cant boot into xRecovery
-Flashtool wont recognize the phone
-phone keeps making notification sounds for no reason
-i get no service
-cant connect to wifi
-wont recognize SD card
-randomly freezes
I found on this forum that this problem causes because i install a new busybox thats what created this error. But i cant get back in to xrecovery again or back to my SD card since my pc doeosnt connect to my phone. So also SEUS doesnt connect, what can i do to reset it all or atleast to get back into xrecovery?
Yours,
Click to expand...
Click to collapse
I have the exact same problem. Did you solve it?
I device maneger SEMC USB Flash show up with a yellow warning sign that indicate that drivers are missing. I have tried to install SE companion but that did not help. Also I cannot flash to a stock rom via SEUS.
Someone suggested to install xrecovery again ... but how?
/anders76

[Q] New member new phone (Now a big problem as well)

Hi, everyone I just joined this forum. I have X10i with firmware 2.1. While searching the thread i came acrosss terms like root, xrecovery, flashing, MT, generic etc. Can someone help me out what these terms mean. I wanted to upgrade my phone to gingerbread. Previously I am an iphone user So i am total noob to this OS and the phone
Thanks in advance
good get away from iphone
root--same thing as jailbreak
xrecovery-- a badass tool that lets you flash roms onto your phone.
flashing-- umm... it is like installing a modified version of even the legit version on the device
generic-- A product having no brand name or registered trademark
example= for device there is branded or non branded
branded means that a company like ATT or Rogers approves that firmware or OS version. So when you turn your phone on, you will usually see something related to them. like an animation of the att world
generic--- clean install. no company restrictions. just regular
ok links for all that crap above
2.3.3 firmware (does not matter if you download x10a or x10i)
Generic-----
http://forum.xda-developers.com/showthread.php?t=936733
do yourself a favor and read
http://forum.xda-developers.com/showthread.php?t=936733 before and download the program WINDOWS only
Thanks for your help. I am going to upgrade my phone soon so is their any problem in doing so and by the way should i just use the SEUS or flash tool
angel eyes said:
Thanks for your help. I am going to upgrade my phone soon so is their any problem in doing so and by the way should i just use the SEUS or flash tool
Click to expand...
Click to collapse
Either will do.
ok thanks for the advice going for the upgrade now lets hope everything goes smoothly will post the results
Now this is the end result of upgrading my phone I used SEUS to upgrade my X10i the phone went into flash mode and the SEUS detect that new software is available soit downloads it but when it comes to installing it stopped at about 15% and said that updATE cannot continue check battary is fully charged and than again try. As far is i remember phone was fully charged when i put it for update now what should i do. The phone doesnt restarts now and when I power up my phone only th egreen led blinks and it vibrates for split second than nothing I waited for it but the phone is not responding what should i do now
HELP NEEDED
to tell you the truth i dont know what SEUS is
i think it is for drivers or something but you should use PC comapanion for drivers
ok
use flashtool in the first link i gave you and download one of the 2.3.3 files
or use a 2.3.3 rom
and flash the sucker on
it should work
Try flashtool if doesn't work let your phone on charge for 1 hour and take it off try again whit seus should be good to go
Sent from my X10i using xda premium
Thanks for the help guys now i have downlaoded flashtool 0.2.8, 2.9,3.0 i also downloaded the firmware and did all the steps according to the toturiol but that what happens it detect the phone in flash mode the flashing starts but at fato1.sin it gives as error message "error flashing abort". I also tried other firmwares but the same error.
Now guys I think I am great trouble so need help
What to do next
And I used the desktop charger to charge the battery for whole two houra but SEUS gives the same error plus pc companion gives error as well i am stuck
Go to pc application manager, close seus and pc companion. Try flashtool tool once again http://forum.xda-developers.com/showthread.php?t=928343. I hope this work for you.
Sent from my SO-01C using Tapatalk
Ok i will try that one too thanks alot lets see wat happens
ok tried that too nu luck
What should i Do now One thing more i was goignaround the threads looking for solution So in one thread it said that firmware can ber installed through flash tool 0.2.5
I tried that too and amazingly the flashing goes all the way to the end on 0.2.5 in the end i get the msg that flashing complete and remove the phone but when i remove the phone and turn it on it just vibrates and small blip of green flash led than nothing
What could be the problem
1. Download Flashtool from
http://doomlord.sylvester20007.com/x10/x10_gb/FlashTool_0.2.9.1-GBready_root_xRec.exe
2. Download the generic 2.3 ROM of your choice
http://forum.xda-developers.com/showpost.php?p=11038646&postcount=1
Personally I would get the Global version unless you can find your country specific one.
Global version download - http://www.multiupload.com/JEXUAHAZTL
3.
a) connect your phone to your PC, make sure it installs the drivers (if your Sony software is working it is fine)
b) Extract Flashtool into a directory you know
c) Extract the firmware file you downloaded. And move the ftf file into the "firmware" directory of Flashtool
d) Make sure your phone is not connected to the PC and is off.
e) Run Flashtool, click on Flash and select the firmware you have just downloaded.
f) It will give you the same instruction - holding the "back" key, (phone still off) connect it to the PC. If you did this correctly, the light will be green and it will start flashing your phone.
g) After it is completed, reboot your phone once or twice and check that it is working.
4. Installing xrecovery and rooting refer to instructions (you already have all the files from when you download in step 1)
http://forum.xda-developers.com/showthread.php?t=1196808
Let me know when you have completed the steps above.
Thanks for advice downloading it now and going to try and will let now about the results
sasukewa said:
1. Download Flashtool from
http://doomlord.sylvester20007.com/x10/x10_gb/FlashTool_0.2.9.1-GBready_root_xRec.exe
2. Download the generic 2.3 ROM of your choice
http://forum.xda-developers.com/showpost.php?p=11038646&postcount=1
Personally I would get the Global version unless you can find your country specific one.
Global version download - http://www.multiupload.com/JEXUAHAZTL
3.
a) connect your phone to your PC, make sure it installs the drivers (if your Sony software is working it is fine)
b) Extract Flashtool into a directory you know
c) Extract the firmware file you downloaded. And move the ftf file into the "firmware" directory of Flashtool
d) Make sure your phone is not connected to the PC and is off.
e) Run Flashtool, click on Flash and select the firmware you have just downloaded.
f) It will give you the same instruction - holding the "back" key, (phone still off) connect it to the PC. If you did this correctly, the light will be green and it will start flashing your phone.
g) After it is completed, reboot your phone once or twice and check that it is working.
4. Installing xrecovery and rooting refer to instructions (you already have all the files from when you download in step 1)
http://forum.xda-developers.com/showthread.php?t=1196808
Let me know when you have completed the steps above.
Click to expand...
Click to collapse
I have done it as adviced but no luck flashing aborts in the middle and giving error message now wehat should i do
Do you have the new flash tool?
angel eyes said:
I have done it as adviced but no luck flashing aborts in the middle and giving error message now wehat should i do
Click to expand...
Click to collapse
Can u do a screen shot or tell us what the error message is?
Thx.
Dark Nightmare said:
Do you have the new flash tool?
Click to expand...
Click to collapse
I have flash tool 0.2.5,0.2.8,0.2.9,0.3.0
Have tried them all only 0.2.5 goes all the way to the end but when i turn on the phone it only virbrates and green led flashes for sec than nothing
When you reboot is there anything showing on the screen? Sony logo...anything? If yes, wait it can take a long time for a new rom to install. If no, I think you need to revert back to the 2.1 rom, root and install busybox, superuser, and xrecovery. once thats done you can backup your rom and data so you don't get stuck updating or if you have trouble with a custom rom etc. Also I think your battery stats should be wiped using xrecovery, it sounds like SEUS checked this and the file said your battery was too low to continue the update. Here is a good place to start.
http://forum.xda-developers.com/showthread.php?t=928343&highlight=flashtool+for+noobs
Here is a video on youtube that may help too:http://www.youtube.com/watch?v=HmX-IYNYqL8
Hope this helps you, Good Luck.
angel eyes said:
I have flash tool 0.2.5,0.2.8,0.2.9,0.3.0
Have tried them all only 0.2.5 goes all the way to the end but when i turn on the phone it only virbrates and green led flashes for sec than nothing
Click to expand...
Click to collapse
Try taking the battery out and then try flashing again. Which ftf file are you flashing or selecting in the flash program. You need to use at least a 0.2.9 version of the flashtool.... if you use 0.2.5 start with the 2.1.54 ROM first.

[Q] p769 - softbricked by noob

i finally figured out how to get CWM installed and working, after a couple of months of fighting with it, off and on. so, i guessed that meant i have my bootloader unlocked - "wrong!".
i deleted some thing that wasn't supposed to be deleted, then the damned cell network and lan network stopped working (keeps saying com.android.phone has stopped). so i was going to put cyanogenmod on it, because i thought that i could, and just be done with the whole "missing apps" crap. it turns out "just because you CAN put CM on it doesn't mean you CAN put CM on it". i bricked it. i have NO options to "load" or "flash" or "boot" any thing when the phone is booting up. i would love some clarification as to what i CAN do from here.
i would rather install CM and be done with all of this, but i'll take any advice that gets rid of the problem. the biggest problem is understanding how to put CM on your phone, or to do any thing at all like that, when you cant get into any kind of recovery / boot menu, even though you ARE rooted... i don't care if i have to install cyanogenmod or some one else's CWM backup, i just don't know HOW to do it - especially with no windows (only linux). it's a rooted p769v20d (originally p769v10g).
thanks
sentientsystem said:
i AM rooted, but i have NO options to "load" or "flash" or "boot" any thing when the phone is booting up. i deleted some thing that wasn't supposed to be deleted, now the damned thing doesn't work (keeps saying com.android.phone has stopped), so i was going to put cyanogenmod on it, but not sure how. i keep seeing people mention CWM, and i installed that from google play, but i don't know what to do with it.
i was going to try some stuff mentioned in other threads, but i don't have access to a windows computer - and i don't think i need to root my phone again any way, considering it is still rooted.
i would love some clarification, and assistance, as to what i CAN do from here. i am rooted, i don't care if i have to install cyanogenmod or some one else's CWM backup, i just don't know HOW to do it - especially with no windows (only linux). it's a rooted p769v20d (originally p769v10g).
fwiw, regarding the mysterious deleted app:
i lose my internet signal as soon as it says "com.android.phone has stopped", then i get it back again right before it says that message again - it ALSO shows a cell-phone signal right before that message. this repeats over and over and over every few seconds - aggravating as hell...
here's the apps that i still have installed: http://forum.xda-developers.com/showthread.php?p=45774770
again, i would rather install CM and be done with all of this, but i'll take any advice that gets rid of the problem. the biggest problem is understanding how to put CM on your phone, or to do any thing at all like that, when you cant get into any kind of recovery / boot menu, even though you ARE rooted...
thanks
=== EDIT ===
i finally figured out how to get CWM installed and working, after a couple of months of fighting with it, off and on. so, now i guess that means i have my bootloader unlocked?
Click to expand...
Click to collapse
Nice thread title. That is how I am feeling right now with this phone. I feel like calling tech care and yell at them for a bit to vent. Anyway, why not install fastboot for Linux and flash the ics u and x? I uploaded my u and x folder in the Unlock Bootloader for Noobs thread. Then, flash the 20h.....oh, dang.... sorry. Forgot.... no Windows. Maybe do the built-in restore by holding the volume down, home and power keys?
Sent from my TBD753B using XDA Premium HD app
thanks, but i think i finally got it working. i never knew, after all this time, that after you do the l9recoveryinstaller, at the reboot, there are no cues to tell when when to hit some buttons, and it's not clear what buttons to hit. here's what i did, and, so far, its progress:
1: be rooted
2: install busy box, completely
3: install l9recoveryinstaller
4: reboot
5: after you see the LG logo, hold vol-down until you see the flashing lights (i thought you see the flashing lights and THEN you hit vol-down, but i was wrong).
still fighting to get a rooted rom installed ...
if i choose "install zip from external sdcard" is says:
"finding update ... opening update ... installing update ...installation aborted".
if i choose "restore" instead of "install" it will not let me select any thing, it just keeps saying file not found, when i try to select any further options, whether "restore" or "restore from external sdcard" or "advanced restore from external sdcard". and i already checked to make sure the sdcard was mounted...
sentientsystem said:
thanks, but i think i finally got it working. i never knew, after all this time, that after you do the l9recoveryinstaller, at the reboot, there are no cues to tell when when to hit some buttons, and it's not clear what buttons to hit. here's what i did, and, so far, its progress:
1: be rooted
2: install busy box, completely
3: install l9recoveryinstaller
4: reboot
5: after you see the LG logo, hold vol-down until you see the flashing lights (i thought you see the flashing lights and THEN you hit vol-down, but i was wrong).
still fighting to get a rooted rom installed ...
if i choose "install zip from external sdcard" is says:
"finding update ... opening update ... installing update ...installation aborted".
if i choose "restore" instead of "install" it will not let me select any thing, it just keeps saying file not found, when i try to select any further options, whether "restore" or "restore from external sdcard" or "advanced restore from external sdcard". and i already checked to make sure the sdcard was mounted...
Click to expand...
Click to collapse
I think your phone bootloader is locked, you cannot flash any custom rom zip file. It will soft brick your phone.
Please restore P769 CWM back from this thread http://forum.xda-developers.com/showthread.php?t=2136204. Download backup file and unbzip it. Put extract files in your sdcard /clockworkmod/backup/2013-08-30.12.00.00 folder. Extract file should contain several .img, .tar, .a, .log and .md5
artit said:
I think your phone bootloader is locked, you cannot flash any custom rom zip file. It will soft brick your phone.
Please restore P769 CWM back from this thread http://forum.xda-developers.com/showthread.php?t=2136204
Click to expand...
Click to collapse
too late - bricked it... currently looking for a way to unf*ck myself...
BTW, those were the ones i WAS trying to flash...
thanks
sentientsystem said:
too late - bricked it... currently looking for a way to unf*ck myself...
BTW, those were the ones i WAS trying to flash...
thanks
Click to expand...
Click to collapse
Then try to use LG mobile support tool to recover your phone. Load it from LG website, start your phone to S/W upload mode, connect usb then start program and select recover phone from menu.
artit said:
Then try to use LG mobile support tool to recover your phone. Load it from LG website, start your phone to S/W upload mode, connect usb then start program and select recover phone from menu.
Click to expand...
Click to collapse
i don't have a windows computer. looks like i'm out a 350$ phone. lesson learned. never will cease to be amazed that so many mobile hackers are using windows... seems like they would be linux users too... that would be awesome, because then there are likely to be linux tools to do this with... and i don't have a windows img to load into a virtual machine... lucky lucky lucky...
thanks any way...
sentientsystem said:
i don't have a windows computer. looks like i'm out a 350$ phone. lesson learned. never will cease to be amazed that so many mobile hackers are using windows... seems like they would be linux users too... that would be awesome, because then there are likely to be linux tools to do this with... and i don't have a windows img to load into a virtual machine... lucky lucky lucky...
thanks any way...
Click to expand...
Click to collapse
Well correct me if I am wrong, but I guess you "only" deleted some system files, right? Do you remember which ones were the ones? Or at least the folder they were in? Then you only need to extract that stuff from a kdz/ the bin file and push them on your phone using adb or maybe even the dd command.
Maybe if someone is kind enough, he ll probably provide you with the files you need. And cmiiw, but I guess you deleted stuff from /system/app...
Sent from my LG-P760 using xda app-developers app
sentientsystem said:
i don't have a windows computer. looks like i'm out a 350$ phone. lesson learned. never will cease to be amazed that so many mobile hackers are using windows... seems like they would be linux users too... that would be awesome, because then there are likely to be linux tools to do this with... and i don't have a windows img to load into a virtual machine... lucky lucky lucky...
thanks any way...
Click to expand...
Click to collapse
Lol, you are a Linux user, you should know how to get your hands on a windows.iso
However, i would recommend using a portable windows xp (bootable usb)
VR is not the best option IMO
You will need this program http://unetbootin.sourceforge.net/
&
Sorry I can't provide a link to the iso but do a google search for
portable windows xp bootable usb Osheraj
artit said:
Then try to use LG mobile support tool to recover your phone. Load it from LG website, start your phone to S/W upload mode, connect usb then start program and select recover phone from menu.
Click to expand...
Click to collapse
okay, what do i need to download to load onto the phone? kdz images, right? i'll check and see if i can find a kdz in the forum, and borrow a windows computer. i think i got it - this thread: http://forum.xda-developers.com/showthread.php?t=2107971
sentientsystem said:
okay, what do i need to download to load onto the phone? kdz images, right? i'll check and see if i can find a kdz in the forum, and borrow a windows computer.
Click to expand...
Click to collapse
It's depend on what method you use. You can flash kdz using offline method here http://forum.xda-developers.com/showthread.php?t=2085344
or use LG mobile support tools from LG website. If you choose this you don't need to download any kdz. It'll download kdz automatically from LG server then flash it on your phone. It take about an hour or two.
artit said:
It's depend on what method you use. You can flash kdz using offline method here http://forum.xda-developers.com/showthread.php?t=2085344
or use LG mobile support tools from LG website. If you choose this you don't need to download any kdz. It'll download kdz automatically from LG server then flash it on your phone. It take about an hour or two.
Click to expand...
Click to collapse
thats awesome - i wonder if i can get by with using that on wine on linux, instead of borrowing a windows computer... i'm gonna try it...
well, the verdict is in, on this one: i'm screwed. i've tried and tried and tried and tried and tried and tried and tried and tried and tried and tried and tried and tried, and i can NOT flash this damned phone. it's BRICKED.
i borrowed / hijacked my brother's computer (windows7), all day. i tried a few different things - i even tried the same way i flashed it to update it ( http://forum.xda-developers.com/showthread.php?t=2356536 ), which was worthless to unbrick it.
the problem in every case was that every time the damned flasher got so far along it would "lose the connection to the phone". drivers installed, etc, etc, no difference. i suspect its because i couldnt connect it in all the various modes (mtp ptp etc), since the ONLY way it would connect is in "software upgrade mode".
i had to buy another phone, won't have it till tuesday. lesson learned: NEVER buy a phone that didn't come from samsung... you just can't do what you want with them, without a lot of time, patience, experience, and a windows computer.
thanks for all the help.
sentientsystem said:
well, the verdict is in, on this one: i'm screwed. i've tried and tried and tried and tried and tried and tried and tried and tried and tried and tried and tried and tried, and i can NOT flash this damned phone. it's BRICKED.
i borrowed / hijacked my brother's computer (windows7), all day. i tried a few different things - i even tried the same way i flashed it to update it ( http://forum.xda-developers.com/showthread.php?t=2356536 ), which was worthless to unbrick it.
the problem in every case was that every time the damned flasher got so far along it would "lose the connection to the phone". drivers installed, etc, etc, no difference. i suspect its because i couldnt connect it in all the various modes (mtp ptp etc), since the ONLY way it would connect is in "software upgrade mode".
i had to buy another phone, won't have it till tuesday. lesson learned: NEVER buy a phone that didn't come from samsung... you just can't do what you want with them, without a lot of time, patience, experience, and a windows computer.
thanks for all the help.
Click to expand...
Click to collapse
Did you try to recover your phone with LG mobile support tool. It can reinstall rom in almost any soft-brick case. Please try it if you haven't try it yet. Many people restore their phone by that software. The steps are
- Download LG mobile support tool from LG web site
- Boot you phone to S/W update mode
- Run Tool and select recover phone
- Wait about 1-2 hours to download and flash
If it's not hardware problem, this should solve your problem
artit said:
Did you try to recover your phone with LG mobile support tool.
Click to expand...
Click to collapse
i never found that on their website, and i looked quite a few times. however, i noticed when i used the b2clientsetup.exe that if i run it without running the shttp server first, that it downloads a support tool from the net, which does not work - keeps saying phone lost connection. not sure if its the same tool.
sentientsystem said:
i never found that on their website, and i looked quite a few times. however, i noticed when i used the b2clientsetup.exe that if i run it without running the shttp server first, that it downloads a support tool from the net, which does not work - keeps saying phone lost connection. not sure if its the same tool.
Click to expand...
Click to collapse
Yes that tool. In my region, it has download link but for P769 it has request repair service.
Download from http://tool.xcdn.gdms.lge.com/client/app/B2CAppSetup.exe
You must remove following lines from hosts file
127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com
Then run it
artit said:
Yes that tool. You must remove lines from hosts file. Then run it
Click to expand...
Click to collapse
yeah, that's exactly what i did, but it would keep "losing the connection to the phone". not sure why, but i suspect it was a driver issue - and i installed the latest drivers, which made no difference. i also went back and installed older drivers, which made no difference. i must just be lucky as hell, or some thing .
sentientsystem said:
yeah, that's exactly what i did, but it would keep "losing the connection to the phone". not sure why, but i suspect it was a driver issue - and i installed the latest drivers, which made no difference. i also went back and installed older drivers, which made no difference. i must just be lucky as hell, or some thing .
Click to expand...
Click to collapse
Try to use others USB ports, if that also doesn't work maybe you have to try on other computer.
artit said:
Try to use others USB ports, if that also doesn't work maybe you have to try on other computer.
Click to expand...
Click to collapse
yeah, i tried switching between the usb 3.0 ports and usb 2.0 ports, but it made no difference. i have no access to any other computers, so, that's why i ended up ordering another phone. i'll never buy another phone that is not a samsung...
thanks
In my country (RO) there are some GSM Repair Centers. You should not give up and you should go to them. Par example, I flashed an HTC Mozart when the battery was dead and I bricked it (idiot, I know). I went to a shop like the ones mentioned above and I think he said that he has to flash the phone using a JTAG or something like that (I know that he has to open the phone to reach it's motherboard, solder some **** out there and... flash I guess). The whole thing was about ~20E. Anyway, keep digging, maybe you'll eventually find something that works for you. If not, go to someone who can "force flash" it and maybe you can save the device.

[RESOLVED] Please help, I think I bricked my Z3v when trying to update with flashtool

So, I tried using flashtool for the first time today with my xperia z3v (verizon version). I wanted to update it to the fairly recently leaked lollipop rom (verizon is still on kitkat).
Anyways, I think what happened is that I forgot to turn on usb debugging before flashing the FTF. And now my phone is stuck saying: "the software update failed. Make sure that your phone is connected to the computer and try again."
I've tried reflashing multiple times to no avail. I've tried factory resetting by holding the volume down and power button but that won't work. And Sony PC companion won't pick up the device at all either. Can anyone help me get my phone working again? Maybe I should try flashing a different version? I've been googling for the last 4 hours trying to solve this so any input would be greatly appreciated!!
**EDIT: Nevermind I figured it out here is what I did when I had trouble with flashtool:
Quote:
Originally Posted by fixmewireless
I tired update Z3v with Flashtool to latest version and phone got soft bricked. I downloaded ftr file from server and flashed with flashtool. flashing process went thru, but phone shows message "software update failed".
Only error message I had during flash is ERROR - Error parsing TA file. Skipping
I noticed that flashtool does not have fsc preinstalled for D6708 (z3v). Did that cause the problem?
Can anybody upload fsc for z3v?
thanks
I actually ran into this same exact problem. After I had it soft bricked as you stated, I opened back up flash tool and when to set up the flash, and inside the flashtool I checked every box under Wipe, Also check all boxes under Exclude, EXCEPT SYSTEM. Leave SYSTEM un checked! Check everything under MiscTA Exclude too. I Then ran Flash and let it do its thing until it prompt me to plug in device into flashmode. It the ran the flash successfully and rebooted my device. I then followed the rest of the steps from page one and was able to root the device with no problems. Hope this helps!
If you hold volume down, and plug the usb into the pc, does the updating message appear?
zackdadams said:
If you hold volume down, and plug the usb into the pc, does the updating message appear?
Click to expand...
Click to collapse
Yes it does. So I am able to attempt re-flashing it at least but so far haven't gotten anywhere. Why?
actionjaxon77 said:
Yes it does. So I am able to attempt re-flashing it at least but so far haven't gotten anywhere. Why?
Click to expand...
Click to collapse
It's cusrious you are geting the error parsing TA file. You have a verizon phone so you must be bootloader locked. Were you roted before? Maybe just corrupt FTF file, try downloading it again or try to convert the SIN files to ext4 within flashtool and see if you can read everything correctly with ext4explore.
Sounds to me you soft bricked the phone, which is what I and others also experienced when attempting to flash.
I simply started up flashtool again, loaded the leaked lollipop ftf, and when asked, get back to the "updating" screen on the phone.
The phone should flash correctly.
Like mentioned above, try downloading the ftf again, or download the stock/shipped ftf.
http://forum.xda-developers.com/z3/xperia-z3v-general/guide-sony-xperia-z3v-t3100402
He mentions "1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download..."
That's the shipped version ftf.
The leaked Lollipop ftf link was down, so I used this one:
http://www.androidvillaz.com/2015/09/verizon-sony-xperia-z3v-d6708-android.html
zackdadams said:
Sounds to me you soft bricked the phone, which is what I and others also experienced when attempting to flash.
I simply started up flashtool again, loaded the leaked lollipop ftf, and when asked, get back to the "updating" screen on the phone.
The phone should flash correctly.
Like mentioned above, try downloading the ftf again, or download the stock/shipped ftf.
http://forum.xda-developers.com/z3/xperia-z3v-general/guide-sony-xperia-z3v-t3100402
He mentions "1. If you are NOT on stock shipped ROM, 23.0.E.0.376 / R15B, please download..."
That's the shipped version ftf.
The leaked Lollipop ftf link was down, so I used this one:
http://www.androidvillaz.com/2015/09/verizon-sony-xperia-z3v-d6708-android.html
Click to expand...
Click to collapse
Thanks for the help, I was able to successfully flash it using the info I pasted in my edit to the original post!

Xperia Z Ultra (C6833) - SIM not recognized

I'm new to this forum and I hope to get some help from the community...
Device:
Sony Xperia Z Ultra (C6833), Android 5.1.1 (Lollipop) rooted, Built: 14.6.A.1.236 , Developer's mode & USB-Debugging enabled
Problem:
After updating SuperSU to 2.82 I had a bootloop. Did shutdown using small red button, restarted using recobery mode of TRWP (2.8.7.0) and did factory reset. Everything works again (WLAN, Apps, SD card access) but except the SIM card which is not recognized. IMEI not shown "About the phone", but correctly shown in diagnosis tool
Already tried:
- SuperSU 2.82 installed manually via TWRP. Works.
- Restored a full backup Sony PC-Companion, no success. Same with a Snappea backup.
- SIM proofed with different cell phone, works
- Other working SIM card tried with this phone, no success
- I blew a couple of times into the SIM card slot, no success
- Flashed the full ROM (14.6.A.1.236, rooted), no success
- Tried another factory reset, no success
I guess, there is a problem with the modem driver for the SIM card reader. Any ideas how to fix this?
I'm a newby to root & stuff but I'm hoping, that somebody could help me. I'm very thankful for any hints!
Greetings from Germany!
Not sure how the imei got tweaked by updating the supersu..?
But I had the same bootloop with the new supersu on latest stock rom rooted.
Manually removing all root and manually flash the new via twrp didn't work for me either.
Flashed the old supersu and it boots fine.. so I just keep the update in playstore and don't press it.
Perhaps I will repack the supersu app to generate a unique file signature so it won't show up in play store on installed apps.
Perhaps the simcard got tweaked in the tray when you pushed the red button somehow? ...I dunno. Just a thought.
I have had issues with mine too. The tray is very flippy floppy and have gotten stuck several times inside the phone.
But have you tried flashing stock rom with flashtool?
http://www.flashtool.net/downloads.php
Make sure that none of the options is ticked in "exceptions" so all partitions being flashed.
Do you know how to use flashtool?
SUPERUSER said:
Not sure how the imei got tweaked by updating the supersu..?
But I had the same bootloop with the new supersu on latest stock rom rooted.
Manually removing all root and manually flash the new via twrp didn't work for me either.
Flashed the old supersu and it boots fine.. so I just keep the update in playstore and don't press it.
Perhaps I will repack the supersu app to generate a unique file signature so it won't show up in play store on installed apps.
Perhaps the simcard got tweaked in the tray when you pushed the red button somehow? ...I dunno. Just a thought.
I have had issues with mine too. The tray is very flippy floppy and have gotten stuck several times inside the phone.
But have you tried flashing stock rom with flashtool?
http://www.flashtool.net/downloads.php
Make sure that none of the options is ticked in "exceptions" so all partitions being flashed.
Do you know how to use flashtool?
Click to expand...
Click to collapse
Hi @SUPERUSER can you please look int this thread and advise ... i am freaking out due to this
https://forum.xda-developers.com/xp...ev-plz-help-m-options-modem-baseband-t3623391
rgds
SUPERUSER said:
Not sure how the imei got tweaked by updating the supersu..?
But I had the same bootloop with the new supersu on latest stock rom rooted.
Manually removing all root and manually flash the new via twrp didn't work for me either.
Flashed the old supersu and it boots fine.. so I just keep the update in playstore and don't press it.
Perhaps I will repack the supersu app to generate a unique file signature so it won't show up in play store on installed apps.
Perhaps the simcard got tweaked in the tray when you pushed the red button somehow? ...I dunno. Just a thought.
I have had issues with mine too. The tray is very flippy floppy and have gotten stuck several times inside the phone.
But have you tried flashing stock rom with flashtool?
...URL...
Make sure that none of the options is ticked in "exceptions" so all partitions being flashed.
Do you know how to use flashtool?
Click to expand...
Click to collapse
Hi SUPERUSER, thanks for your quick reply!
It can't be the SIM card itself, since it works with my other phone. Also tried my GFs SIM in the C6833, also failed. Should be a ROM problem.
Tried to go back to SuperSU 2.79, 'cause that's how this mess all started (updating SuperSU), have the bootloop again, went back to 2.82. Works fine except the undetected SIM card.
Also tried 2 (probably dirty) modem fixes, this caused also loose of IMEI. Went back to my full backup using TWRP, where everything works (IMEI ok) except SIM card problem.
Just installed the flashtool, but it says, that the bootloader is locked. Unlocking it officially thru Sony website (developer.. sonymobile..com/unlockbootloader) requires installing full Android Suite (1.9GB) and further driver installtion using SDK manager. Is this the only way to use the flashtool? Other question regarding the Flashtool: Tutorials say: Copy ftf-File into the "firmware" folder, but there is no folder with this name. I checked the entire flashtool folder tree.
Isn't it possible to flash ROM in zip-format only using TWRP? Should I give DualRecovery a try too?
Thanks a lot! Appreciate your help!
ac845 said:
Hi SUPERUSER, thanks for your quick reply!
It can't be the SIM card itself, since it works with my other phone. Also tried my GFs SIM in the C6833, also failed. Should be a ROM problem.
Tried to go back to SuperSU 2.79, 'cause that's how this mess all started (updating SuperSU), have the bootloop again, went back to 2.82. Works fine except the undetected SIM card.
Also tried 2 (probably dirty) modem fixes, this caused also loose of IMEI. Went back to my full backup using TWRP, where everything works (IMEI ok) except SIM card problem.
Just installed the flashtool, but it says, that the bootloader is locked. Unlocking it officially thru Sony website (developer.. sonymobile..com/unlockbootloader) requires installing full Android Suite (1.9GB) and further driver installtion using SDK manager. Is this the only way to use the flashtool? Other question regarding the Flashtool: Tutorials say: Copy ftf-File into the "firmware" folder, but there is no folder with this name. I checked the entire flashtool folder tree.
Isn't it possible to flash ROM in zip-format only using TWRP? Should I give DualRecovery a try too?
Thanks a lot! Appreciate your help!
Click to expand...
Click to collapse
Whats causing your problem is probably that your bootloader is locked.
But I'm not getting how you use twrp and flashing files if the bootloader is locked?
You can flash stock roms with locked bootloader. It dont require to unlock it.
You don't need to download the whole SDK for just using fastboot.
If you need fastboot you can download fastboot from here: https://forum.xda-developers.com/showthread.php?t=2588979
After install choose the right driver for your togari in device manager to "Android bootloader interface"
SUPERUSER said:
Whats causing your problem is probably that your bootloader is locked.
But I'm not getting how you use twrp and flashing files if the bootloader is locked?
You can flash stock roms with locked bootloader. It dont require to unlock it.
You don't need to download the whole SDK for just using fastboot.
If you need fastboot you can download fastboot from here: https://forum.xda-developers.com/showthread.php?t=2588979
After install choose the right driver for your togari in device manager to "Android bootloader interface"
Click to expand...
Click to collapse
Thanks again!
Fastboot sucessfully installed using your link, but I have a driver problem. The device works fine connected to the pc using Sony PC Companion oder Snappea. Do I need a different driver for running fastboot? Found "S1Boot Fastboot" in "Devices and printers" on my pc and I'm aware that the correct driver has to be installed manually, just don't know where to get it. Google didn't help much, I'm only found a zip on Sony web, which probably does not contain the one file I need for running fastboot.... Any hints?
ac845 said:
Thanks again!
Fastboot sucessfully installed using your link, but I have a driver problem. The device works fine connected to the pc using Sony PC Companion oder Snappea. Do I need a different driver for running fastboot? Found "S1Boot Fastboot" in "Devices and printers" on my pc and I'm aware that the correct driver has to be installed manually, just don't know where to get it. Google didn't help much, I'm only found a zip on Sony web, which probably does not contain the one file I need for running fastboot.... Any hints?
Click to expand...
Click to collapse
PC companion is screwing you over because it has its own signed drivers. Perhaps these are proprietary and don't work with universal fastboot.
If you installed the 15 seconds ADB Installer v1.4.3 from the thread I linked AND installed the google driver when you were asked if you wanted.
Connect your phone in fastboot. Then choose the driver manually from a list. Scroll down to "Android Device" and select "Android Bootloader Interface"
You will get a warning that the driver might not work. Click yes and soon the device will be found and your phone will respond to fastboot commands.
If you need all drivers for example the flashmode driver you can download and install flashtool.
Then you get a folder with a driver pack in C:\Flashtool\drivers. The executable contains all the drivers to every xperia device.
Edit:
If you ever need the driver pack from flashtool I uploaded it to mega:
https://mega.nz/#!BdIlEIAQ!QQyFnhLYBZjMwe-rkfWmyVagMg9GL5qr7zwPuBKSjQw
SUPERUSER said:
PC companion is screwing you over because it has its own signed drivers. Perhaps these are proprietary and don't work with universal fastboot.
If you installed the 15 seconds ADB Installer v1.4.3 from the thread I linked AND installed the google driver when you were asked if you wanted.
Connect your phone in fastboot. Then choose the driver manually from a list. Scroll down to "Android Device" and select "Android Bootloader Interface"
You will get a warning that the driver might not work. Click yes and soon the device will be found and your phone will respond to fastboot commands.
If you need all drivers for example the flashmode driver you can download and install flashtool.
Then you get a folder with a driver pack in C:\Flashtool\drivers. The executable contains all the drivers to every xperia device.
Edit:
If you ever need the driver pack from flashtool I uploaded it to mega:
https://mega.nz/#!BdIlEIAQ!QQyFnhLYBZjMwe-rkfWmyVagMg9GL5qr7zwPuBKSjQw
Click to expand...
Click to collapse
Cheers! Couple of steps further! Drivers installed, fastboot detects the device now, I unlocked the bootloader successfully using fastboot. Device now recognized by the Flashtool too.
How to flash the custom ROM now? Better using fastboot or the Flashtool? I'd prefer the flashtool due to my limited cmd experiences. But I don't know how to select the FTF-file, which I already downloaded.
Don't know how to add screenshots here directly, so I added 2 attechments: Flashtool Main Screen and Folder sctructure of Emma. There is no "firmware" folder where I can drop the FTF-file to.
If using fastboot, ftf-file won't work, right? Zip-Files only?
How to proceed? Cheers, again!
ac845 said:
Cheers! Couple of steps further! Drivers installed, fastboot detects the device now, I unlocked the bootloader successfully using fastboot. Device now recognized by the Flashtool too.
How to flash the custom ROM now? Better using fastboot or the Flashtool? I'd prefer the flashtool due to my limited cmd experiences. But I don't know how to select the FTF-file, which I already downloaded.
Don't know how to add screenshots here directly, so I added 2 attechments: Flashtool Main Screen and Folder sctructure of Emma. There is no "firmware" folder where I can drop the FTF-file to.
If using fastboot, ftf-file won't work, right? Zip-Files only?
How to proceed? Cheers, again!
Click to expand...
Click to collapse
You downloaded the SONY EMMA flashtool. Not the one we need.
The name is a bit confusing because they are called the same.
The flashtool we need is this one. Download it via torrent its the fastest way.
http://www.flashtool.net/downloads.php
Uninstall Emma and install this flashtool.
...time for some ugly doodling
When you are done installing flashtool and are met with the UI you will see a main window as in image one. Press this button on the far right with the XF logo.
A new window will open with the name XperiFirm as in image two. Scroll down the list on the far left until you see the Togari.
Select your device. In my case I have the C6833. Now go to the list in in the middle. Click the "check all" button to fetch all updates.
When this is finished you will see a the latest "version number" on every "operator" in the collumn to the right.
Click the stock rom you would like to download in the list that correspond to where you live.
I always download customized DE because it includes the region I live in. Now look at the list to the right.
A list will appear under the "Available Firmware:". Click on the one you want to download. In this case there is only one entry.
Almost all older stock rom has been removed lately so it is very rare that you will find any old based on jelly bean or kitkat.
Anyway. When you click the one you want to download a new window will open as shown in image three
You will see some info. Double check the name is the one you want to download. If its right. Click download and make a coup of coffee.
When the download is finished you can close the window and let flashtool do its job. When its done.
You can see it in the log when it says its finished.
Now you want to press the button all the way to the left. That thunderbolt icon as shown in image four
A new window will open. Select flashmode and press ok as shown in image five
A new window will open and here you can see a list of which stock roms you have downloaded as shown in image six
Select the one you want to flash and look to the right in the "Exclude:" box. Make sure nothing is ticked.
And press flash when you are ready. And follow the instructions following by flashtool when it is ready.
Optional
If your phone is not detected in flashmode you need to install S1 - flashmode driver. You can do so by follow these steps.
Go to this folder as shown here in image seven
Execute the file as shown here in image eight
Select Flashmode Drivers as shown in image nine You don't need to select fastboot drivers. Because you already have this working.
If you want you can scroll down and select Xperia Z Ultra drivers as shown in image ten however this seems to fail in Windows due to driver signature verification.
Its not necessary to select it. Click install and hopefully the device will be seen when connected in flashmode.
For zip files. What you find here on the forum. You flash these in recovery. Not very difficult. You can find loads of guide on how to get started learning how to use recovery mode.
.img files. You flash via fastboot with cmd. Not very difficult either. Key tip here is to don't make typos or you need to rewrite the whole command again..which get boring fast.
SUPERUSER said:
You downloaded the SONY EMMA flashtool. Not the one we need.
The name is a bit confusing because they are called the same.
The flashtool we need is this one. Download it via torrent its the fastest way.
http://www.flashtool.net/downloads.php
Uninstall Emma and install this flashtool.
...time for some ugly doodling
When you are done installing flashtool and are met with the UI you will see a main window as in image one. Press this button on the far right with the XF logo.
A new window will open with the name XperiFirm as in image two. Scroll down the list on the far left until you see the Togari.
Select your device. In my case I have the C6833. Now go to the list in in the middle. Click the "check all" button to fetch all updates.
When this is finished you will see a the latest "version number" on every "operator" in the collumn to the right.
Click the stock rom you would like to download in the list that correspond to where you live.
I always download customized DE because it includes the region I live in. Now look at the list to the right.
A list will appear under the "Available Firmware:". Click on the one you want to download. In this case there is only one entry.
Almost all older stock rom has been removed lately so it is very rare that you will find any old based on jelly bean or kitkat.
Anyway. When you click the one you want to download a new window will open as shown in image three
You will see some info. Double check the name is the one you want to download. If its right. Click download and make a coup of coffee.
When the download is finished you can close the window and let flashtool do its job. When its done.
You can see it in the log when it says its finished.
Now you want to press the button all the way to the left. That thunderbolt icon as shown in image four
A new window will open. Select flashmode and press ok as shown in image five
A new window will open and here you can see a list of which stock roms you have downloaded as shown in image six
Select the one you want to flash and look to the right in the "Exclude:" box. Make sure nothing is ticked.
And press flash when you are ready. And follow the instructions following by flashtool when it is ready.
Optional
If your phone is not detected in flashmode you need to install S1 - flashmode driver. You can do so by follow these steps.
Go to this folder as shown here in image seven
Execute the file as shown here in image eight
Select Flashmode Drivers as shown in image nine You don't need to select fastboot drivers. Because you already have this working.
If you want you can scroll down and select Xperia Z Ultra drivers as shown in image ten however this seems to fail in Windows due to driver signature verification.
Its not necessary to select it. Click install and hopefully the device will be seen when connected in flashmode.
For zip files. What you find here on the forum. You flash these in recovery. Not very difficult. You can find loads of guide on how to get started learning how to use recovery mode.
.img files. You flash via fastboot with cmd. Not very difficult either. Key tip here is to don't make typos or you need to rewrite the whole command again..which get boring fast.
Click to expand...
Click to collapse
Followed all your instructions. Custom ROM flash with (the correct) Flashtool was succesful. Now comes the hopefully magic moment, where I'm gonna reboot and see if SIM card will be detected....
ac845 said:
Followed all your instructions. Custom ROM flash (C6833_14.6.A.1.236_Customized_DE.ftf) with (the correct) Flashtool was succesful. Now comes the hopefully magic moment, where I'm gonna reboot and see if SIM card will be detected....
Click to expand...
Click to collapse
SIM card NOT detected. I'm freakin' out!
Again tried the SIM card in 2 other phones, no problems. Tray and contacts shouldn't be the problem either, because I didn't to anything with SIM card and tray when the problem came up first after the stupid update of SuperSU and the following bootloop. Just pressed the tiny red panic button to shut down and went into recovery mode.
Just tried to use some thin folie between the tray and the SIM card in order to have some more pressure between SIM card and the contacts, failed.
Is it technically possible that a full custom ROM flash (with no ticked exceptions) still not formated the probably damaged SIM card modem portion/driver?
User pintspin has the same problem as above and he is much more into the topic than I am.
Still any hints? Wanted to avoid buying a new smartphone, still love the Ultra C6833 and its large screen...
ac845 said:
SIM card NOT detected. I'm freakin' out!
Again tried the SIM card in 2 other phones, no problems. Tray and contacts shouldn't be the problem either, because I didn't to anything with SIM card and tray when the problem came up first after the stupid update of SuperSU and the following bootloop. Just pressed the tiny red panic button to shut down and went into recovery mode.
Just tried to use some thin folie between the tray and the SIM card in order to have some more pressure between SIM card and the contacts, failed.
Is it technically possible that a full custom ROM flash (with no ticked exceptions) still not formated the probably damaged SIM card modem portion/driver?
User pintspin has the same problem as above and he is much more into the topic than I am.
Still any hints? Wanted to avoid buying a new smartphone, still love the Ultra C6833 and its large screen...
Click to expand...
Click to collapse
I will ask him if I can obtain the ones that worked for him/her.
The modem should be flashed when you flashed the ftf file if the baseband portion is included.
This is the one I found in the thread ResurrectionRemix 5.8.3 25/05/17 [7.1.2] Nougat for Togari,
https://forum.xda-developers.com/showpost.php?p=56234199&postcount=16
And this:
https://forum.xda-developers.com/xperia-z-ultra/help/aosp-rom-sim-detection-t3185526/post62481536
I know I have used one other way back. It was two zips. You flashed them in a specific order or the phone would not boot.
But I can't find this one.
I uploaded my own modem files. Its the same files that is in the zip above but with the stock rom Im running.
Im guessing it might do something because its working on my phone. And its the same files that is being flash in the above zip file.
File is not flashable. Unzip and replace the in system/etc/firmware. Permissions 644. And reboot.
Or you could do it from twrp. Take a bit longer. Manually delete the three files one by one and then copying the files one by one.
Setting the permissions to 644 one by one.
SUPERUSER said:
I will ask him if I can obtain the ones that worked for him/her.
The modem should be flashed when you flashed the ftf file if the baseband portion is included.
This is the one I found in the thread ResurrectionRemix 5.8.3 25/05/17 [7.1.2] Nougat for Togari,
https://forum.xda-developers.com/showpost.php?p=56234199&postcount=16
And this:
https://forum.xda-developers.com/xperia-z-ultra/help/aosp-rom-sim-detection-t3185526/post62481536
I know I have used one other way back. It was two zips. You flashed them in a specific order or the phone would not boot.
But I can't find this one.
I uploaded my own modem files. Its the same files that is in the zip above but with the stock rom Im running.
Im guessing it might do something because its working on my phone. And its the same files that is being flash in the above zip file.
File is not flash-able. Unzip and replace the in system/etc/firmware. Permissions 644. And reboot.
Or you could do it from twrp. Take a bit longer. Manually delete the three files one by one and then copying the files one by one.
Setting the permissions to 644 one by one.
Click to expand...
Click to collapse
@SUPERUSER done , uploaded here the working modem patch strangely from a different variant but worked fine... thanks for above help as well.
I can confirm that the attached modem patch is working perfectly fine ... on AOSP build ( 6.0.1 )
(*) @ac845 steps i suppose you already have your system.img and boot.img
Flash the aosp Rom images ( system.img ) and (boot.img) via fast boot OR if you dont have images of stock then just flash any stock rom zip from recovery i used twrp recovery after FULL WIPE OR if you even dont have both then just use Scrubber port GPE for togari 6833 z ultra
don't reboot
Flash the attached modem patch i.e. C6802_modem_patch.zip
reboot to system
on first boot it will take a bit ( 1 minute may be ) to detect and register the sim.
I have finished worked on my rom as well , will going to upload it hopefully today ... its purest aosp stock , can be rooted and gapps are also tested working fine , there is no Imei base band issue as well.
pintspin said:
@SUPERUSER done , uploaded here the working modem patch strangely from a different variant but worked fine... thanks for above help as well.
I can confirm that the attached modem patch is working perfectly fine ... on AOSP build ( 6.0.1 )
(*) @ac845 steps i suppose you already have your system.img and boot.img
Flash the aosp Rom images ( system.img ) and (boot.img) via fast boot OR if you dont have images of stock then just flash any stock rom zip from recovery i used twrp recovery after FULL WIPE OR if you even dont have both then just use Scrubber port GPE for togari 6833 z ultra
don't reboot
Flash the attached modem patch i.e. C6802_modem_patch.zip
reboot to system
on first boot it will take a bit ( 1 minute may be ) to detect and register the sim.
I have finished worked on my rom as well , will going to upload it hopefully today ... its purest aosp stock , can be rooted and gapps are also tested working fine , there is no Imei base band issue as well.
Click to expand...
Click to collapse
I (partially) understand, what you guys mean, but I don't know how to proceed and thus have to ask more beginner questions:
As recommened by SUPERUSER like 2 days ago I flashed a the .276 stock ROM. The device is of course unrooted now, bootloader open. I don't have a recovery mode (f.i. TWRP) where I can flash ZIPs. What would be the easeast way to flash a ZIP-file in this situation? I could try flashing with fastboot, but I don't know where to get the right .imgs. Wished I still had TWRP though. Sorry for bothering you, but for beginners like me it's too complex sometimes...
ac845 said:
I (partially) understand, what you guys mean, but I don't know how to proceed and thus have to ask more beginner questions:
As recommened by SUPERUSER like 2 days ago I flashed a the .276 stock ROM. The device is of course unrooted now, bootloader open. I don't have a recovery mode (f.i. TWRP) where I can flash ZIPs. What would be the easeast way to flash a ZIP-file in this situation? I could try flashing with fastboot, but I don't know where to get the right .imgs. Wished I still had TWRP though. Sorry for bothering you, but for beginners like me it's too complex sometimes...
Click to expand...
Click to collapse
Download this file https://www.androidfilehost.com/?fid=24415232478676273
To make it more simple. Rename the file to "recovery" without the quotes when the download is finished.
In your download folder on your computer hold down shift on your keyboard and right click on an empty space.
In the right click menu select "open command window here".
In the cmd. Type "fastboot flash recovery recovery.img".
Turn your phone off. And boot it to fastboot. Hold volume up or down and simultaneously connect the usb cable to the computer.
If you did it right the phone should have a blue led on.
Now press enter on your keyboard inside the command window.
Hopefully you will see something like flashing and then finished.
How to boot to recovery?
Pull out the usb cable.
Now hold volume down and press power button.
When it vibrates let go. A few seconds you will se the twrp ui.
In addition to super user post above : For fast boot you need to press volume up and then connect PC USB cable when your PC is on and USB cable is connected to it ( you also need yo ensure that USB debugging is turned on ) goto phone setting and you need to press 8 times on build number in your about phone n phone will open a hiden option called developers option under phone settings and goto developer options n under that option you need yo select USB debugging on .
pintspin said:
In addition to super user post above : For fast boot you need to press volume up and then connect PC USB cable when your PC is on and USB cable is connected to it ( you also need yo ensure that USB debugging is turned on ) goto phone setting and you need to press 8 times on build number in your about phone n phone will open a hiden option called developers option under phone settings and goto developer options n under that option you need yo select USB debugging on .
Click to expand...
Click to collapse
TWRP succesfully installed. Great to have it back!
But now it comes: SIM CARD DETECTED AGAIN after 2 weeks and endless hours of fiddling, reading forums and bothering you guys. You both are awesome :angel: and made my day!
What I did:
1. TWRP installed
2. full wipe
3. installed prerooted custom rom 14.6.A.1.236: Customized Germany (DE), source: https://www.android-hilfe.de/thema/stock-roms-mirror-root-tools-anleitung.559556/ Link: https://mega.nz/#!PoEElBZa!DlejjkTzCZGMXbJR0ZvgTk5i0gNqo4QSM0LIyyRKl1M
4. installed SUPERUSER's modem patch from above
5. rebooted: 1. time no SIM card detected. Wanted start crying :crying:, but rebooted 2nd time: SUCCESS! Broadband of my provider is back!
Now restoring messages, contacts and apps right now using Snappea. After reorganzing apps I'll do full TWRP backup and I hope that this problem never will occur.
During restore app process I'll go to a German beer garden and will raise my glass to you guys! :laugh: Want to donate both of you some money, please let me know how. Paypal?
Greetings from Germany!
George
Happy midsummer!
Well I find my joy in helping someone with their technical issues and it makes me happy when we find a solution. Its why I'm here..
I don't believe in exchanging knowledge for money unless its my job.
But I thank you for your gratefulness! cheers! :highfive:
:good::laugh: great to know you solved this ... Enjoy the weekend with ur phone revive ... I am glad that it worked coz I can feel what it like to be Co I went some what same situation .... Just keep us in ur prayers ...
pintspin said:
:good::laugh: great to know you solved this ... Enjoy the weekend with ur phone revive ... I am glad that it worked coz I can feel what it like to be Co I went some what same situation .... Just keep us in ur prayers ...
Click to expand...
Click to collapse
Unfortunately it's not over yet!
SIM still not detected very often, but sometimes it does. SIM works for some hours but then it's accidently not detected anymore in locked-screen mode or in the middle of operation, app usage etc. Rebooting with detected SIM works in 1 of 5 times maybe. Restoring full backups doesn't make any difference.
Had the idea that it is a temperature problem and cooled the device down in the frosting fridge for a couple of minutes, but rebooting incl SIM detection works more often, but not always. Beside SIM problem operation is normal, no problems with WLAN, apps etc.
IMO it can't be a software bug since problem occures not generally. Before I'd send it in to Sony I wanted to ask the community if you have any ideas or recommendations?
Cheers!

Categories

Resources