Related
Hi,
I come here, because I somehow bricked my MK16 Xperia Pro with GB, and don't now what to do. I sent it to Sony, but they told me, I changed the software and refused any service. So I'am on my own. The phone was rooted and the bootloader was open, I did that months ago and the phone worked good. Then one evening, I switched it off and I wasn't able to switch it on next morning. Don't know what happend. The phone is simply dead.
No switching on, display stays off
No charging
No connections to the PC
Battery is full and I also have another one to test.
If it's connected to the PC (Win7) I hear a small beep from windows, that something is pluged in via USB, in the device-manager I see a new ZEUS Flash Device.
I tried several methods to unbrick it, but
flashtool doesn't recognize it (it says plug the phone in, but it does not recognize it)
Sony Updateservice with the same problem
fastboot says "Waiting for Device"
I tried all magic keys to enter the booloader, menu-key, vol-down/up, back-key, back and menu-key, together with power key or plugging in USB-Cable. Maybe I did something wrong?
The guys from the service must have made it run, because they told me, I changed the software. How did they got in?
The funny thing is, after I got it back, it worked again once (the service people said, they did not repair it), I was able to boot. The last thing was, I accepted an OTA-Update and the Phone rebooted and never woke up. It bricked again and I have no idea how to make it work again.
So any hint is really welcome.
Recover Bootloader?
Hi,
I spent the night to recover my phone. My findings are, that I can boot sometimes, if I plug USB in and pressing Vol-Down. The phone boots until I can login. I made a factory reset over the menu, but after switching off, I can't switch it on with the power button. So I tried fastboot mode with the flashtool and my firmware. After a few attempts I was able to flash it. But again, no switching on via power button.
I have to plug in an out USB 10-20 times, and then the phone starts to live again. But regardless what I do, the phone denies to start via power button.
This leads me to the conclusion, that maybe my Bootloader is broken? I'am not a phone pro, but on a PC I'd rewrite MBR and Bootsector with this symptoms.
What do you say folks? And how can I do that? I only found how to unlock the Bootloader, but not how to reinstall it.
Please help
Flash in flash mode, not fast boot. The OTA is what's caused this, check FXP's OTA unbrick thread.
Sent from myushi
Check the tutorial in my signature, I have all the information about unbricking after OTA update.
OTA not the cause
@Xperience, the OTA is not the cause for my problems. I accepted the OTA after I had the problems, because I thought I could fix it with formatting and rewriting everything (what I thought is the case with an OTA-Update). And I'am sorry, I searched the forum with the words you mentioned, and I can't find the OTA unbrick thread. If you have a more detailed pointer, I'll be happy.
@Someguy, thanks for your help, I looked into your tutorial, but excuse me for being blind, I can't see where is the point, which can help me. Could you be more precise please?
It's a sticky in the dev section. You might need to swap a few files to suit your Phone.
Sent from myushi
After UnbrickingXperia2011.zip
Hi, I found in @Someguys tutorial Point 6, howto unbrick. I installed the new Loader using flashtool. Turned off, and ONCE it turned on again, using the power button. But after reinstalling SIM-Card (and battey), the phone again refuses to start with the power button.
WTH is that? So I flashed the firmware and the loader, but it had no impact. Anything else I can do?
That's the log of flashtool:
Code:
evice connected in flash mode
13/035/2012 16:35:08 - INFO - Opening device for R/W
13/035/2012 16:35:08 - INFO - Reading device information
13/035/2012 16:35:08 - INFO - Phone ready for flashmode operations.
13/035/2012 16:35:09 - INFO - Start Flashing
13/035/2012 16:35:09 - INFO - Processing loader
13/035/2012 16:35:09 - INFO - Checking header
13/035/2012 16:35:09 - INFO - Flashing data
13/035/2012 16:35:11 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
13/035/2012 16:35:11 - INFO - Flashing preset.ta
13/035/2012 16:35:11 - INFO - Writing TA unit : [00, 00, 08, FD, 00, 00, 00, 02, 00, 00]
13/035/2012 16:35:11 - INFO - Ending flash session
13/035/2012 16:35:11 - INFO - Flashing finished.
13/035/2012 16:35:11 - INFO - Please unplug and start your phone
13/035/2012 16:35:11 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
13/035/2012 16:35:11 - INFO - Device connected in flash mode
13/035/2012 16:35:28 - INFO - Device disconnected
P.S: I tried to relock the Bootloader with the mentioned methods and flashed the file -> no change
I used S1Tool and took Restore -> no change
It says:
Welcome to S1 tool.
That is small and crippled subset of SETOOL2 service tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
PRESS AND HOLD "Volume Down" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R9A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A069"
NOTHING TO RESTORE
Elapsed:12 secs.
FXP said:
Hi,
This will fix your unlocked Phones which got bricked through OTA update and are dead now!
Please download this package:
http://www.multiupload.com/Q103V01CV1
Let it extract to a destination of your choice.
After that run Flashtool.exe.
Now hit the button FLASH and select the package which is included.
Follow the steps and connect your phone in flashmode. This is the same mode Pc Companion and SEUS uses to flash your phone to newer firmare (Indicated by green LED), if you got BLUE LED you are in the wrong mode!
Flashtool will now detect your phone and start the repair.
After all is done your phone should be up and running again.
ADVICE:
PLEASE DO NOT ACCEPT ANY OTA'S ! If you receive a OTA message just decline, if you accept it you will end with a brick AGAIN! So please do NOT accept them until SonyEricsson provides a OTA solution for unlocked Bootloaders!
Best Regards
Team FreeXperia
Click to expand...
Click to collapse
Not sure why you removed your SIM and SD, but try the above.
I'll see
Hi,
thanks for your quoting. But I'am suspicious, because I was able to use the SE Update-Service Tool (after 20 times reconnecting USB) and upgraded to ICS (and have choosen the option to overwrite an kill everything on the phone). The tool downloaded an flashed 224 MB, the phone worked and even started again once with the power button. And now, again, dead phone. I'am not sure, if these kind of flashing is a solution to my problem. IMHO the OTAs are not the problem, because I had these problems with the dead powerkey BEFORE I used one OTA.
Mr.Dros said:
Hi,
thanks for your quoting. But I'am suspicious, because I was able to use the SE Update-Service Tool (after 20 times reconnecting USB) and upgraded to ICS (and have choosen the option to overwrite an kill everything on the phone). The tool downloaded an flashed 224 MB, the phone worked and even started again once with the power button. And now, again, dead phone. I'am not sure, if these kind of flashing is a solution to my problem. IMHO the OTAs are not the problem, because I had these problems with the dead powerkey BEFORE I used one OTA.
Click to expand...
Click to collapse
Try it or don't, your Phone is dead anyway, the Service doesn't want to know, so your only options are to try what's being suggested here or take it off to a repair shop, which you might need to do anyway by the sounds of it, but you won't know unless you try.
Of course you're right, I'am stuck with a brick and have nothing to loose. I tried what you've provided, but it is the same file to flash, as mentionend in the HowTos of @Someguy. I already did this. This time with SD and SIM. Once again, no effect.
I'd like to bring it to the shop, but the repair shop denied any service, because the "Origininal-Software has been changed", I think they meant the open Bootloader. They don't have even asked to repair it for money.
One Question: If I flash with flashtool an choose one fsf-file, there are more files in this fsf-file (like loader.sin and preset.ta). Do I have to flash everything seperatly or does flashtool write it alltogether?
Mr.Dros said:
This time with SD and SIM. Once again, no effect...
One Question: If I flash with flashtool an choose one fsf-file, there are more files in this fsf-file (like loader.sin and preset.ta). Do I have to flash everything seperatly or does flashtool write it alltogether?
Click to expand...
Click to collapse
I would have found out by now. Yes, click flash, click ok, then report back.
XperienceD said:
I would have found out by now. Yes, click flash, click ok, then report back.
Click to expand...
Click to collapse
What makes you think I didn't? I tried it already (again), and I wrote it had no effect. The log didn't say that it is flashing all files of the fsf-container, just preset.ta has been mentioned by name. Sorry, for not being an Android-Pro, I'm working on it.
At the moment the phone is running and I try not to switch it off. It is also no mechanical problem of the power switch, because if the phone is running, I can use it.
I really would like to know, what happens in first stage, when the power button is pressed or an USB-cable is connecting. There must be something before the Bootloader. It looks like, the routine which starts the Bootloader stucks. On a PC I'd say, there is a POST problem in the BIOS, right before the Bootmanager can be started. Any idea how to debug that?
BTW: The SE-ICS implementation sucks, the Pro-Keyboard is not supported correctly (at least the german layout).
I thought you hadn't by the way you had worded your post. I don't know what else to suggest.
Sent from myushi
XperienceD said:
I thought you hadn't by the way you had worded your post. I don't know what else to suggest.
Click to expand...
Click to collapse
Thanks anyway for your help!
Just remembered, contact Alejandrissimo or Jinx13, they have the full SETool and Alejandrissimo has a thread about repairing the BL. There's a link to their profiles in my guide. Now I am fully out of ideas.
Sent from myushi
Thx. I managed to root the new ICS, sometimes the powerbutton works as it should. I also found, that pulling out the battery an re-inserting it a few times, will also make the phone start via the powerbutton, not only plugging in the USB-Cable.
I have a phone Lenovo Vibe shot z90a40 . Few days ago I have successfully flashed firmware with root facilities with Miflash . Phone was working fine . Then I tried to flash again another firmware with QFIL . I marked the options "Reset after Download" . After downloding the new ROM my vibe shot never start , it always stuck on Lenovo logo/text .
The problem are below -
1. When I press/hold Volume + button and plug in usb cable , the phone vibarte 2 times . So Miflash/QFIL could not detect com port .
2. I could not enable usb debugging mode because my phone never startup after last flashing , so ' adb reboot edl' command not working . device not found .
3. Also I can't enter any Mode , so I could not reset data , could not update from any update.zip from recovery .
4. If I press and hold volume + , volume - and power button at same time , PC detect comport as 9006 , its shows not writable .
5. I tried eMMC downloader to switch to Download mode but failed . :crying:
Please help me . Thanks
zahidbd2 said:
I have a phone Lenovo Vibe shot z90a40 . Few days ago I have successfully flashed firmware with root facilities with Miflash . Phone was working fine . Then I tried to flash again another firmware with QFIL . I marked the options "Reset after Download" . After downloding the new ROM my vibe shot never start , it always stuck on Lenovo logo/text .
The problem are below -
1. When I press/hold Volume + button and plug in usb cable , the phone vibarte 2 times . So Miflash/QFIL could not detect com port .
2. I could not enable usb debugging mode because my phone never startup after last flashing , so ' adb reboot edl' command not working . device not found .
3. Also I can't enter any Mode , so I could not reset data , could not update from any update.zip from recovery .
4. If I press and hold volume + , volume - and power button at same time , PC detect comport as 9006 , its shows not writable .
5. I tried eMMC downloader to switch to Download mode but failed . :crying:
Please help me . Thanks
Click to expand...
Click to collapse
Hello, it seems I really am facing the same problem here.
I tried all those steps above, and then I even tried to wipe and formal users data, even factory reset, but then, when I boot the phone, it is stuck on the booting screen saying Initializing. I wish I could give you all screenshot for this.
So, would anyone help us?
Hello
I m facing the same problem... initializing. http://forum.xda-developers.com/android/help/lenovo-vibe-z90-7-brick-stucking-t3328123
3 night that I m investigating this... No luck...
Hello! This happened to me just yesterday and I managed to solve it by following these steps:
- Download an official rom update (in a QSB file) - try googling Lenovo Z90-7 Vibe Shot - QSB.
- Create sdfuse folder on the sdcard (using computer) and copying qsb file there.
- Insert sdcard into phone
- Enter factory menu by powering off and then turning it on using POWER BUTTON + VOLUME DOWN
- There's an "SD Update" option, use it.
After that, my phone booted successfully!
Hooray. BUT: the first problem ("1. When I press/hold Volume + button and plug in usb cable , the phone vibarte 2 times . ") persisted
So, still haven't found a way to use miflash again
If anyone finds a way to solve this one, I will buy him a beer. Or a cat.
---------- Post added at 05:29 PM ---------- Previous post was at 05:28 PM ----------
If links are allowed here, you will find both rom and info here:
http://www.needrom.com/download/lenovo-z90-7-vibe-shot/
I tried the qsb files but my phone simply ignore them on the external sd , i saw some ppl that put them on the internal sd but i ve no access to the drive.
zahidbd2 said:
I have a phone Lenovo Vibe shot z90a40 . Few days ago I have successfully flashed firmware with root facilities with Miflash . Phone was working fine . Then I tried to flash again another firmware with QFIL . I marked the options "Reset after Download" . After downloding the new ROM my vibe shot never start , it always stuck on Lenovo logo/text .
The problem are below -
1. When I press/hold Volume + button and plug in usb cable , the phone vibarte 2 times . So Miflash/QFIL could not detect com port .
2. I could not enable usb debugging mode because my phone never startup after last flashing , so ' adb reboot edl' command not working . device not found .
3. Also I can't enter any Mode , so I could not reset data , could not update from any update.zip from recovery .
4. If I press and hold volume + , volume - and power button at same time , PC detect comport as 9006 , its shows not writable .
5. I tried eMMC downloader to switch to Download mode but failed . :crying:
Please help me . Thanks
Click to expand...
Click to collapse
Hi,
here is my solution if can help.
I had on my vibe shot s208 rooted ROW. It stacked after SU update in boot loop.
1. I did wipe data without formatting from recovery mode (Vol+ and Vol- and Power button. When Logo is on release power button and hold Vol+ and Vol - until you are in recovery mode). STILL boot loop.
2. I did wipe data with formatting from the same menu. - STILL boot loop.
3. I did factory reset from recovery menu (Vol - and Power after logo is on release Power and hold Vol - until you get recovery mode) - STILL boot loop.
Then I did next:
1. I downloaded and installed QFIL (QPST_2.7.422) - I am not allowed to post links yet.
2. I have connected OTG adapter to phone. Phone was off.
3. then connected OTG to PC. It was some HDD activities but I did not hear any sound.
4. press Vol- for as long as something is going on - HDD activities. Then I think came up sound too - but not sure.
5. I had installed Qualcomm USB drivers from before I suppose.
6. Because I couldn't see my device as ...908 I disconnected and connected again usb cable... then I got my device as ...908 in device manager, but it was written "RECONNECTED" or similar in front of word "QUALCOM".
7. Then just follow instructions for QFIL. and ROM will be installed.
First I have installed INTERNATIONAL no root ROM. But because I needed phone to be rooted in order to use data recovery software I flashed again with s240 ROOTED. When I flashed second time I did not use OTG, just direct usb cable connection to PC, and my phone was again recognized after I reconnected usb cable and in device manger was "RECONNECTED" in front of word "QUALCOM".
Hello and thanks!
Could you please provide more details regarding last step - quoted below?
Did you use the same software for flashing? What state was the phone in? How did you get it there?
dejxda said:
First I have installed INTERNATIONAL no root ROM. But because I needed phone to be rooted in order to use data recovery software I flashed again with s240 ROOTED. When I flashed second time I did not use OTG, just direct usb cable connection to PC, and my phone was again recognized after I reconnected usb cable and in device manger was "RECONNECTED" in front of word "QUALCOM".
Click to expand...
Click to collapse
daddy32 said:
Hello and thanks!
Could you please provide more details regarding last step - quoted below?
Did you use the same software for flashing? What state was the phone in? How did you get it there?
Click to expand...
Click to collapse
Well, after phone was recognized I did exactly the same procedure like in step 7. - Followed QFIL procedure (brows for 3 files and hit download).
lenovo vibe shot z90-7 brick
Hi.Before few days i had to flash an official rom on my vibe shot (s208) and after I was requested for OTA update the mobile stopped working.Trying to turn it on using recovery mode doesn't work.I tried several tricks but still nothing.The recovery mode,though,seems to work.But when I try to run a zipped rom on the external sd fails.I tried MiFlash too.When flashing begins it stops with the following notification:faulted function(0x80070001:WriteFile position 0x00000004000000,size 1048576).I also tried QFIL.I get this notification:Qualcomm HS-USB Diagnostics 9006(COM 5).I am desperate.I find no way to fix my mobile.pls help!
How To fix This Issue
I had a similar problem 2 days ago. I tried all methods but was unsuccessful. My computer couldn't detect my port as Qualcomm HS-USB QDLoader 9008 but rather Qualcomm HS-USB Diagnostic 9008 .
I found a way to fix that driver issue and i was able to flash my phone. And now My lenovo vibe shot is back to life.
I am not allowed to post links yet but i have provided the name of the sites
I hope this works for you
First Make sure your phone is turned off. U can do that by booting to recovery mode and sellect shutdown
Step 0
Download the right firmware for your device. I use other ones they didnt work.
This one worked perfectly for my device firmware version S118: Z90a40_USR_S118_1505272046_Q2020131.4_ROW_qpst.7z
Find it at boycracked forum or xda-developers forum
Step 1
Disable driver signature enforcement
Find the steps here
Step 2
Install the qdLoader HS-USB Driver
Find the steps at androidbrick
at this point your computer cant still recognise the device as Qualcomm HS-USB QDLoader 9008. You have to do the next step
Step 3
Manually Install VCOM Drivers on your Computer. This will enable your computer to detect your device as Qualcomm HS-USB QDLoader 9008
Find the steps at hovatek forum
Step 4
Head to this site and use the second method to flash your phone
( SECOND METHODS ) Installing the firmware using QPST/QFIL
Find the steps here
_ go to boycracked blog
dejxda said:
Hi,
3. then connected OTG to PC. It was some HDD activities but I did not hear any sound.
Click to expand...
Click to collapse
How do you connect your OTG to your PC?
This is how it looks...
{
"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"
}
How I fixed this
I fixed it installing a update.zip via recovery (vol + plus vol - plus power) I found here
http://forum.xda-developers.com/andr...posed-t3409989
This not fixed the phone , but allowed me to unlock bootloader entering in fastboot mode (vol + plus vol - plus plug usb) using this
http://lenovo-forums.ru/topic/18149-...B0-bootloader/
Then I was allowed to install TWRP as explained here
http://lenovo-forums.ru/topic/18150-...-by-sevenmaxs/
Then I was able to go to TWRP terminal and type
reboot edl
Phone rebooted into downloader mode and I was able to install this rom with QFIL
http://www.needrom.com/download/leno...encn-unlocked/
and I restored NVRAM with a qcn file I found in Ebay after putting the phone in diagnostics mode. Then I changed imeis, meid and esn to the original ones I found in the box. Phone fixed.
Just note that this file was for a Z90-7 rom and it will not work with a Z40a20 rom.
Hope this helps someone.
Lenovo Vibe shot z90a40 unbircked sucessfully
i posted a video on youtube about it where i sucessfully unbrick the device
josepgb said:
I fixed it installing a update.zip via recovery (vol + plus vol - plus power) I found here
http://forum.xda-developers.com/andr...posed-t3409989
This not fixed the phone , but allowed me to unlock bootloader entering in fastboot mode (vol + plus vol - plus plug usb) using this
http://lenovo-forums.ru/topic/18149-...B0-bootloader/
Then I was allowed to install TWRP as explained here
http://lenovo-forums.ru/topic/18150-...-by-sevenmaxs/
Then I was able to go to TWRP terminal and type
reboot edl
Phone rebooted into downloader mode and I was able to install this rom with QFIL
http://www.needrom.com/download/leno...encn-unlocked/
and I restored NVRAM with a qcn file I found in Ebay after putting the phone in diagnostics mode. Then I changed imeis, meid and esn to the original ones I found in the box. Phone fixed.
Just note that this file was for a Z90-7 rom and it will not work with a Z40a20 rom.
Hope this helps someone.
Click to expand...
Click to collapse
Hi, I managed to install twrp ( Chinese) but I can't install any rom .. After successful flashing ROM via twrp, system reboot with lenovo logo, then long vibrates.. When I connect it to PC. It show number of partition and need to format popup.. I tried different ROMs.. All via twrp. I don't use miflash or qfil.. Do I have to use miflash or qfil to solve the problem?? Mi or qfil?
I got this error in lenovo vibe x3 using QPST ..
any onehelp me?
Start Download
Program Path:E:\New folder\myphone\twrp3.0.2 QPST\prog_emmc_firehose_8974.mbn
Binary build date: May 13 2015 @ 14:41:37
QSAHARASERVER CALLED LIKE THIS: 'C:\Program Files\Qualcomm\QPST\bin\QSaharaServer.exe -p \\.\COM7 -s 13:E:\New folder\myphone\twrp3.0.2 QPST\prog_emmc_firehose_8974.mbn 'Current working dir: C:\Users\Ketul\AppData\Roaming\Qualcomm\QFIL
Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: E:\New
19:11:49: ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
19:11:49: ERROR: function: sahara_main:854 Sahara protocol error
19:11:49: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download
appu1988 said:
Hi, I managed to install twrp ( Chinese) but I can't install any rom .. After successful flashing ROM via twrp, system reboot with lenovo logo, then long vibrates.. When I connect it to PC. It show number of partition and need to format popup.. I tried different ROMs.. All via twrp. I don't use miflash or qfil.. Do I have to use miflash or qfil to solve the problem?? Mi or qfil?
Click to expand...
Click to collapse
miflash and qfil cannot help at this state.
go into twrp, and restore backup.
if you dont have backup, dont know how to help.
i cannot flash any other rom too with twrp.
Hi
I have tried a lot to unbrick my Lenovo Vibe Shot. Now I am helpless and looking for some workable solution:
I used Lenovo Smart Assistant to download a proper firmware so it turned out it is:
z90a40_USR_S363_1606250500_Q202533.1_ROW.zip
I tried to use Lenovo Smart drive assistant to update ROM or Device Rescue, but both wont detect phone
The phone default Lenovo recovery can be loaded by pressing VOL+, VOL- and power button, and then releasing power button
when logo appears. I used an Update.zip in 8GB mem card and used the option: ‘install update package’ then it complete the process 100% I was happy that I was going to get my phone unbrick
{
"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"
}
but when it asked for reboot and I rebooted it, it vibrated
2 times, first it vibrated, and showed logo of Lenovo for 1 second then it vibrated long like 2/3 seconds and turned off. I repeated many times these steps but still it behaves same.
Another thing is after brick, it showed this in My Computer:
And with each new drive letter it shows following. I tried to format but it then says Write protected error.
Then tried 3 or 4 methods from following
https://boycracked.com/2016/02/07/stock-rom-frimware-lenovo-vibe-shot-z90/
I was just simply not able to use Qualcomm Lenovo HS-USB QDLoader 9008
as on all my PCs it is detecting as some Diagnostic 9006 version instead of above.
Tried on different PCs and ROMs/Firmwares titling Lenovo Vibe Shot, Either the following error or Delete drive layout comes.
Then I followed next method for QFIL but still it cannot download it.
Please help me how can get things right, I have tried on 3 PCs (2 of them were 32 bit windows, and a Win 10 laptop)
Still no luck
I have the same problem. tried everything, QFIL MiFlash Recovery. no luck. Partition tool does not delete the partition. tried deleting all of them and creating a new 1. nothing happened. the pc no longer detected the multiple write protected drives but the partition tool still does and when I plugged it in a different PC, the multiple write protected drives appeared again. Hope we find a solution for this. I haven't been sleeping that much for the past week because of this.
babui21 said:
I have the same problem. tried everything, QFIL MiFlash Recovery. no luck. Partition tool does not delete the partition. tried deleting all of them and creating a new 1. nothing happened. the pc no longer detected the multiple write protected drives but the partition tool still does and when I plugged it in a different PC, the multiple write protected drives appeared again. Hope we find a solution for this. I haven't been sleeping that much for the past week because of this.
Click to expand...
Click to collapse
I figured it out from my semi-sleepless nights. But b4 the solution that worked for me, I had to
learn a lot out of my desperation to finally get it worked on the day I decided to hand over to
some technical guy from local market
The full comment form Francisco Kadzi helped me finally do it from following youtube link:
https://www.youtube.com/watch?v=SmMg00Wqabc&t=1s
Besides I had to take care of many things. First here are the things I was doing wrong:
- Not taking care of a heavily charged phone, I would try to unbrick after just 1 hour
or less charging from a total uncharged device.
- I was going to a backward step whenever I failed on something (Reboot in
fastboot mode, trying with QFIL etc.). Whereas many different forums (mainly XDA),
people were saying to try again and again.
- I was using improper ROMS or flash files my device was: Z90a40_USR_S363_1606250500_Q202533.1_ROW
- When I would see 9006 mode again I would be disappointed and would try different solution.
The correct thing to try was uninstall this driver and then connect the device again with
PC in fastboot mode .
Then I used Lenovo Smart Assistant and got this proper file:
Z90a40_USR_S363_1606250500_Q202533.1_ROW
OK read my first post to know what problems I faced, but at the end the multiple
partitions were not really the problem. The actual problem was getting 9008 mode
in Device Manager of my Windows 7. I always got it as Diagnostics 9006 mode. One
I started getting 9008, things went in my way gradually. So the person posting on
above comment from youtube link helped me
Am a happy fellow at the moment and will help anyone with same problem if needed
My email id is: usman400 on G Mail
usman400 said:
I figured it out from my semi-sleepless nights. But b4 the solution that worked for me, I had to
learn a lot out of my desperation to finally get it worked on the day I decided to hand over to
some technical guy from local market
The full comment form Francisco Kadzi helped me finally do it from following youtube link:
https://www.youtube.com/watch?v=SmMg00Wqabc&t=1s
Besides I had to take care of many things. First here are the things I was doing wrong:
- Not taking care of a heavily charged phone, I would try to unbrick after just 1 hour
or less charging from a total uncharged device.
- I was going to a backward step whenever I failed on something (Reboot in
fastboot mode, trying with QFIL etc.). Whereas many different forums (mainly XDA),
people were saying to try again and again.
- I was using improper ROMS or flash files my device was: Z90a40_USR_S363_1606250500_Q202533.1_ROW
- When I would see 9006 mode again I would be disappointed and would try different solution.
The correct thing to try was uninstall this driver and then connect the device again with
PC in fastboot mode .
Then I used Lenovo Smart Assistant and got this proper file:
Z90a40_USR_S363_1606250500_Q202533.1_ROW
OK read my first post to know what problems I faced, but at the end the multiple
partitions were not really the problem. The actual problem was getting 9008 mode
in Device Manager of my Windows 7. I always got it as Diagnostics 9006 mode. One
I started getting 9008, things went in my way gradually. So the person posting on
above comment from youtube link helped me
Am a happy fellow at the moment and will help anyone with same problem if needed
My email id is: usman400 on G Mail
Click to expand...
Click to collapse
I had problem like you, and i couldnt solve it so i sent it to repair shop and waiting now to hear from them.
I managed to get 9008 port, tryed to downgrade, upgrade, flash would complete, i tried literaly all row and china rom, no way to boot up sucessfully.
I even flashed twrp and tryed cm rom and mokee, i could boot after lenovo sign.
But i have same situation like you, many partitions and thats all. I think problem is read only partitions...
Can you tell me what drivers did you use?
I was able to fix exactly same problem this morning an hour before important meeting. All contacts and location puns were on gdrive and hadn't slept full night. You need to download correct qualcom drivers. Enter in Google: android qualcom urdu checked. Inside the zip unpack "checked" folder, right click and select install all infs. Run adb reboot bootloader while phone attempts to boot, when command succeeds run adb reboot edl, or fastboot reboot-edl whichever works. Keep miflash open and refresh. Then you see a short Comm port name. Now shoot flash with any rom that you have. If you do Chinese version then SNAPit lags badly, install correct version.
To sum up, focus on implementing correct qualcom drivers. In windows 10 run command testsign off and reboot in advance.
Actually I bricked my phone a whole lot of times even after my post thats because once I knew that it is just soft bricked and I can get it back somehow, I got the confidence and tried advanced things that bricked my phone again and again
And it was only the recent time (around 3 weeks ago), that I figured the 100% working 9008 method for my phone
actually u have to drain the battery completely out then it will get 9008 mode to do it u shall try turning your phone on again and again so that battery goes off
For example: Press Power button for a few seconds to turn it on.
Or press 3 buttons at same time (VOL+, VOL- and Power), then release only Power button when you get vibration. Then after 2 seconds release both VOL buttons as well (this is for going to recovery mode)
This way you can drain all battery of phone, and you will know when the battery is all gone when you will press the Power button and phone will not show any LED light or screen light, it will just vibrate and will be off
Now you connect ur phone to PC in following way:
If at bricking you you were on Lollipop (Android 5): Pressing VOL+ key and plug the USB cable in WITHOUT PRESSING POWER BUTTON ! 9008 will open use Qfil to flash the ROM u want
OR If at bricking you were on Marshmallow (Android 6): Plug the USB cable in phone, then connect cable to PC and exactly at the same time press power button (some times u dont need to press power button so try with both options). Then if you see 9008 mode in Qfil, then immediately press the Download button in Qfil
If you see Qfil error then repeat the above process to get 9008 mode and use miflash instead of Qfil miflash worked for me better than Qfil from such situation as Qfil often gives error in between
And when you get the flashing 100% then phone will either auto restart or you have to restart it manually Using Qfil it shows u message when it is restarting the phone, and I think using miflash it just says process 100% complete then u have to restart phone yourself
Remember at this point (after restart) connect your phone charger properly in a electricity power socket instead of PC as the battery was already drained so you need to charge the device while it shows the long booting process due to new ROM flashed.
Good luck,
I had the same problem from two days my phone is bricked and when i connect it to my pc too many partitions appears and when flashing by miflash it says (incorrect function) and i tried too many methods without any good result
But I finally unbricked my vibe shot successfully
At first i downloaded Qualcomm Lenovo HS-USB QDLoader 9008 driver definition, i searched for it by google until i get a zip file with the driver definition. i installed it manually from device manager on computer when my phone was connected to pc.
After that i downloaded an official z90a40_s240 for flashing via Qfil.
Steps:
1- disconnect your phone
2- go to recovery mode by ( holding power button with volume+ and volume- at the same time) until booting to recovery mode.
3-In recovery mode chose English then power off
4- open Qfil and get it ready to flash the official firmware
5-connect the USB to your pc then keep holding volume up and connect your phone to USB.
6- your phone screen should be turned off, also the LED light and you should see 9008 mode
7- click to download button and the flashing will start.
And congratulations your phone unbricked successfully ?
I have facing same problem on my phone. Could you help to show me hơ to unbricked it . Thanks you so much.
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Fredelbert said:
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Click to expand...
Click to collapse
You tried xdadevelopers search box ?
RuedasLocas said:
You tried xdadevelopers search box ?
Click to expand...
Click to collapse
Not yet actually . Can't find it under TOOLS . Is this available yet ?
RuedasLocas said:
You tried xdadevelopers search box ?
Click to expand...
Click to collapse
Sorry, I misunderstood your answer ...
Searching for related posts using the keywords 'boot loop' or 'recovery gone' really doesn't help me ...
As I said, I can't use
- Recovery
- adb
- FlashTool
- odin
anymore in any way . All posts I've found suggest things related to them ...
Most bootloop topics recommend using one of them in different ways ...
Is there a tool not mentioned yet that will help me with my problem ?
As I said, thre search function does'nt bring me to a clue
Fredelbert said:
Sorry, I misunderstood your answer ...
Searching for related posts using the keywords 'boot loop' or 'recovery gone' really doesn't help me ...
As I said, I can't use
- Recovery
- adb
- FlashTool
- odin
anymore in any way . All posts I've found suggest things related to them ...
Most bootloop topics recommend using one of them in different ways ...
Is there a tool not mentioned yet that will help me with my problem ?
As I said, thre search function does'nt bring me to a clue
Click to expand...
Click to collapse
Connect your device to the computer and see how is detected by "Windows Device Manager".
If not as it should, try to uninstall all related hardware drivers, like modem, adb device, whatever...
Reinstall "LGMobileDriver_WHQL_Ver_4.2.0"
Reinstall "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All"
Reinstall "Minimal ADB and Fastboot"
Reboot your computer and reconnect yout device. It should work.
RuedasLocas said:
Connect your device to the computer and see how is detected by "Windows Device Manager".
If not as it should, try to uninstall all related hardware drivers, like modem, adb device, whatever...
Reinstall "LGMobileDriver_WHQL_Ver_4.2.0"
Reinstall "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All"
Reinstall "Minimal ADB and Fastboot"
Reboot your computer and reconnect yout device. It should work.
Click to expand...
Click to collapse
When I go to the download mode (the only one starting) it is shown as
LGE AndroidNet USB Serial Port (COM11)
My other LG G4 is working fine with all of the tools and the drivers on my PC (Win 10 64)
and also on my notebook (WIN 10 64) and so did the other one before my attempt of changing the recovery ...
Fredelbert said:
Hello all,
I've got a big problem after resetting my LG G4 to default settings.
But let's start chronologically :
My LG G4 (bootloader unlocked, rooted, TWRP, Freedom Rom V7.5) should have been reset for being used by another person.
I started TWRP, did a factory reset and a full wipe and restarted it.
By then, the phone only started in TWRP... REBOOT SYSTEM also caused a TWRP restart.
I tried to fix this by flashing CWM recovery via adb and then reinstall an image.
Connecting via adb succeeded, flash recovery succeeded .....
But now, there isn't any recovery anymore. Entering recovery by POWER /VOL DOWN causes the
same boot loop as starting the system. The LG logo appears and it restarts immediately.
I only can start in download mode via POWER UP / CONNECT, but the phone isn't recognized in adb
or in odin anymore.
Doing a complete STOCK FLASH via LGUP TOOL can't be done due to the tool telling me that the
model is unknown....
Is there any way to bring the phone back to life again ? I'm totally clueless ... Thanks in advance !
Click to expand...
Click to collapse
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
ThePiGuy said:
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
Click to expand...
Click to collapse
OK, it will take some time downloading and trying it. I'll be back when having results
THANX
ThePiGuy said:
What modem and bootloader (is it v29a nougat beta?)
FWUL is good (https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755) as it avoids any driver issues - it is a bootable linux distro with LG tools built in.
In there, SALT can tell you what your bootloader stack is. Let me know as the version depends on the steps you should take next
Click to expand...
Click to collapse
I've started it and also I've found SALT.
Starting SALT and connecting in Download Mode gives me following informations ( haven't found informations about bootloader stack) :
{
"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"
}
Fredelbert said:
I've started it and also I've found SALT.
Starting SALT and connecting in Download Mode gives me following informations ( haven't found informations about bootloader stack) :
Click to expand...
Click to collapse
Good enough for me
Look at the system one - It says v29a.
So what I want you to try now. Power off your phone. Then, hold power and volume up and hopefully it will boot into the bootloader (at which point you can reflash twrp from twrp.me - cwm is completely outdated)
Fredelbert said:
When I go to the download mode (the only one starting) it is shown as
LGE AndroidNet USB Serial Port (COM11)
My other LG G4 is working fine with all of the tools and the drivers on my PC (Win 10 64)
and also on my notebook (WIN 10 64) and so did the other one before my attempt of changing the recovery ...
Click to expand...
Click to collapse
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
If the phone had v29a installed, you need v20p.kdz and respective "8994.dll", you can extract it from the .kdz. Than you can use LGUP.
ThePiGuy said:
Good enough for me
Look at the system one - It says v29a.
So what I want you to try now. Power off your phone. Then, hold power and volume up and hopefully it will boot into the bootloader (at which point you can reflash twrp from twrp.me - cwm is completely outdated)
Click to expand...
Click to collapse
Unfortunately it doesn't ... Same as normal start :
I did
REMOVE / INSERT BATTERY
POWER / VOL UP same time
then
short flash of BOOTLOADER STATE : BOOTLOADER UNLOCKED including LG Logo, then immediate reboot
Fredelbert said:
Unfortunately it doesn't ... Same as normal start :
I did
REMOVE / INSERT BATTERY
POWER / VOL UP same time
then
short flash of BOOTLOADER STATE : BOOTLOADER UNLOCKED including LG Logo, then immediate reboot
Click to expand...
Click to collapse
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
ThePiGuy said:
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
Click to expand...
Click to collapse
Look at the firmware(laf): v20g
That's his bootloader stack
He flashed freedom ROM which has v29a as base that's why system shows v29a.
Sent from my LG-H815 using XDA Labs
ThePiGuy said:
Strange. Sounds like you may have a mixture of v29 and v20
Try pulling the battery. Then put it back in, hold vol down and plug in the usb cable and keep holding vol down.
Click to expand...
Click to collapse
That has no effect, same behaviour as before
RuedasLocas said:
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
If the phone had v29a installed, you need v20p.kdz and respective "8994.dll", you can extract it from the .kdz. Than you can use LGUP.
Click to expand...
Click to collapse
Sorry, as I mentioned, LGUP can't be used because the tool reject the phone selection because it's "unknown"
Fredelbert said:
Sorry, as I mentioned, LGUP can't be used because the tool reject the phone selection because it's "unknown"
Click to expand...
Click to collapse
Do you have the right "8994.dll" ???
Because to get out from v29a you need the v20p.kdz and the ""8994.dll"" from it. Thats probably why your phone is "unknown"
RuedasLocas said:
Do you have the right "8994.dll" ???
Because to get out from v29a you need the v20p.kdz and the ""8994.dll"" from it. Thats probably why your phone is "unknown"
Click to expand...
Click to collapse
That might be... But how can I make neccessary modifications, when I get no access to the phone at all...
Fredelbert said:
That might be... But how can I make neccessary modifications, when I get no access to the phone at all...
Click to expand...
Click to collapse
You just need the right "8994.dll" on the folder "C:\Program Files (x86)\LG Electronics\LGUP\model\8994", replace the one that you have there with the one extracted from the v20p.kdz.
After that run LGUP.
RuedasLocas said:
You just need the right "8994.dll" on the folder "C:\Program Files (x86)\LG Electronics\LGUP\model\8994", replace the one that you have there with the one extracted from the v20p.kdz.
After that run LGUP.
Click to expand...
Click to collapse
OK, then I will search for the mentioned Kdz file and download it. I will be able to continue tomorrow. Thanks to everybody so far. I will post the result as fast as I can
Hello Guys
I had Chroma 5.01 installed on my phone since 4 years. I re-partitioned the SDCARD properly and installed Marshmallow from the tutorial at https://forum.xda-developers.com/xperia-s/s-development/pure-aosp-lollipop-t2940839.
There was no error at any different error than what told on tutorials. Everything went smooth but at the time of first boot up, my phone is struck at AOSP colourful logo of 4 balls animation . I waited for 5-6 hours for setup to finish but no use. During my efforts to restore it, I discovered that root access is not available.
fastboot mode and adb method not working as phone cant be switched off or get into fastboot mode.
Tried flashing Stock rom but still the same.
Is there any way where this problem can be overcome. No hard reset or soft reset method working so far as to my knowledge( If i am not doing anything wrong).
Please help as i love this phone for its dedicated HDMI output feature.
gaurav560 said:
Hello Guys
I had Chroma 5.01 installed on my phone since 4 years. I re-partitioned the SDCARD properly and installed Marshmallow from the tutorial at https://forum.xda-developers.com/xperia-s/s-development/pure-aosp-lollipop-t2940839.
There was no error at any different error than what told on tutorials. Everything went smooth but at the time of first boot up, my phone is struck at AOSP colourful logo of 4 balls animation . I waited for 5-6 hours for setup to finish but no use. During my efforts to restore it, I discovered that root access is not available.
fastboot mode and adb method not working as phone cant be switched off or get into fastboot mode.
Tried flashing Stock rom but still the same.
Is there any way where this problem can be overcome. No hard reset or soft reset method working so far as to my knowledge( If i am not doing anything wrong).
Please help as i love this phone for its dedicated HDMI output feature.
Click to expand...
Click to collapse
Don't panic bud..remember one thing fastboot and flashmode will always work at any circumstances. 1st install proper driver.you can find driver on the installations folder after you install flashtool.After installing drivers do the below steps.
Open flashtool
Connect USB cable to phone and PC.
Then press and hold volume down button for fastboot and vol up for flashmode as per your choice.then flash what you want
nageswarswain said:
Don't panic bud..remember one thing fastboot and flashmode will always work at any circumstances. 1st install proper driver.you can find driver on the installations folder after you install flashtool.After installing drivers do the below steps.
Open flashtool
Connect USB cable to phone and PC.
Then press and hold volume down button for fastboot and vol up for flashmode as per your choice.then flash what you want
Click to expand...
Click to collapse
thanks for the prompt reply however sorry for the delay as i was out of town. The problem with all this is that there is no root access on the phone therefore fastboot and flashmode are not working.
this is the screen msg i receive.....
05/002/2019 15:02:02 - INFO - Device connected with USB debugging on
05/002/2019 15:02:03 - INFO - Connected device : Sony Xperia S
05/002/2019 15:02:03 - INFO - Installed version of busybox : BusyBox v1.22.1 bionic (2015-10-16 22:49 +0800) multi-call binary.
05/002/2019 15:02:03 - INFO - Android version : 6.0.1 / kernel version : 3.4.0-perf-gfa085ac-00328-g7e6b23a / Build number : MXB48T
05/002/2019 15:02:03 - INFO - Checking root access
05/002/2019 15:02:04 - INFO - Root access denied
05/004/2019 15:04:24 - INFO - Flash canceled
gaurav560 said:
thanks for the prompt reply however sorry for the delay as i was out of town. The problem with all this is that there is no root access on the phone therefore fastboot and flashmode are not working.
this is the screen msg i receive.....
05/002/2019 15:02:02 - INFO - Device connected with USB debugging on
05/002/2019 15:02:03 - INFO - Connected device : Sony Xperia S
05/002/2019 15:02:03 - INFO - Installed version of busybox : BusyBox v1.22.1 bionic (2015-10-16 22:49 +0800) multi-call binary.
05/002/2019 15:02:03 - INFO - Android version : 6.0.1 / kernel version : 3.4.0-perf-gfa085ac-00328-g7e6b23a / Build number : MXB48T
05/002/2019 15:02:03 - INFO - Checking root access
05/002/2019 15:02:04 - INFO - Root access denied
05/004/2019 15:04:24 - INFO - Flash canceled
Click to expand...
Click to collapse
Have you installed the drivers from flashtool folder?Again remember fastboot or flashmode does not need root access ..if your phone is not switched off then keep pressing power+vol up to force shut down the phone and release the power key only to enter the flashmode (do this when connected to PC.).
nageswarswain said:
Have you installed the drivers from flashtool folder?Again remember fastboot or flashmode does not need root access ..if your phone is not switched off then keep pressing power+vol up to force shut down the phone and release the power key only to enter the flashmode (do this when connected to PC.).
Click to expand...
Click to collapse
thanks for the guidance. I could get into recovery by ADB command as follows
ADB reboot recovery
I had done the partition work earlier itself before i was hung upon Android 6.
wiped boot, cache and sdcard couple of times.
converted boot and cache to f2fs also.
However, somehow, i am in a bigger trouble now. My phone was showing 0 mb space for SDCARD due to which neither could I update to TWRp 3.x.x nor flash a new rom 8.1.
Rebooted to recovery couple of times and repeated earlier steps while trying to flash rom also but no use as sdcard space was still 0.
Accidentally, I reboot the phone to system and since then I am knee deep in Garbage.
Now my phone is struck on white SONY logo. I cant shut down the battery untill unless out of battery. As soon as battery is charged, it shows SONY. ADB failed to detect or connect to device.
Flash tool not working as cant get the phone in flash mode. Tried Xperia companion but still the same as cant get into flashmode.
Is there a way now to comeout of all this and fix the phone to its glory.
thanks in advance for looking into my trouble.
gaurav560 said:
thanks for the guidance. I could get into recovery by ADB command as follows
ADB reboot recovery
I had done the partition work earlier itself before i was hung upon Android 6.
wiped boot, cache and sdcard couple of times.
converted boot and cache to f2fs also.
However, somehow, i am in a bigger trouble now. My phone was showing 0 mb space for SDCARD due to which neither could I update to TWRp 3.x.x nor flash a new rom 8.1.
Rebooted to recovery couple of times and repeated earlier steps while trying to flash rom also but no use as sdcard space was still 0.
Accidentally, I reboot the phone to system and since then I am knee deep in Garbage.
Now my phone is struck on white SONY logo. I cant shut down the battery untill unless out of battery. As soon as battery is charged, it shows SONY. ADB failed to detect or connect to device.
Flash tool not working as cant get the phone in flash mode. Tried Xperia companion but still the same as cant get into flashmode.
Is there a way now to comeout of all this and fix the phone to its glory.
thanks in advance for looking into my trouble.
Click to expand...
Click to collapse
Dear my answer is still the same.open flashtool on your computer.force reboot the phone and connect the phone to computer by pressing the vol up button then it will go to flashmode.
Have you installed the drivers.yes or no?