Develop Bugs

[Q] Unlocking bootloader - Xperia S does not stay in fastboot mode

Hey guys!
I'm trying to unlock boot loader on my Xperia S.
I tried the official way - via Sony Development site but I get stuck on the step where you have to connect the phone and push Volume Up button. Problem is that the phone enters the fastboot mode for 5 seconds, but then shows the battery charging logo and it 'quits' the fastboot mode.
Also, when the phone enters the fastboot mode, I should be asked for a driver, but I'm not.
{
"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"
}
Later I tried using the fastboot tool, found here, but the instructions aren't clear, because it seems that the new version is slightly different as the older one. Anyways, when I want to fastboot it (labeled with B) it enters the fastboot mode for 5 seconds, then the phone turns on again.

The problem is your windows system doesn't have the right fastboot usb drivers installed for your device. If those are not detected it will leave fastboot.
I can't help you with how to get those installed fully. But i think I ended up manually updating a hidden device in device manager. I think it stays around there as a disconnected device which you can update.
Hope this at least points you in the right direction.

elupus2 said:
The problem is your windows system doesn't have the right fastboot usb drivers installed for your device. If those are not detected it will leave fastboot.
I can't help you with how to get those installed fully. But i think I ended up manually updating a hidden device in device manager. I think it stays around there as a disconnected device which you can update.
Hope this at least points you in the right direction.
Click to expand...
Click to collapse
I can also confirm I did something similar on my Win7 64x - had to manually force some drivers for the fastboot mode.

From A to Z, please
Okay guys,
first of all, thank you!
Ok, let me explain:
1. what I want: get rid of sony's firmware and flash CyanogenMod11
2. phone: Xperia S, my current firmware: 6.2.B.1.96, (still) locked bootloader , no CWM, no root access, SONY PC companion installed
3. I'm following this tutorial: http://www.androidhogger.com/how-to-install-cyanogenmod-11-android-4-4-xperia-s.html
4. I stuck when it comes to root xperia s http://www.ibtimes.co.uk/xperia-s-lt26i-root-android412-jellybean-ota-501291, but this tutorial says I have to unlock bootloader before. Well okay.
5. http://forum.xda-developers.com/showthread.php?t=2447319
I DID everything as said in instructions till the 10th step, but then the ******* phone does not stay in Fastboot mode. My computer installs (apparently) some random drivers -> it does not ask me what I want to do, 'because the driver wasn't installed successfully'., so I can not point to the usb_driver folder.
I tried updating the driver through the Device manager where 'S1 Boot Fastboot' shows when I enter the fastboot mode, but can't finish because the phone quits fastboot and the SONY's logo apperas before I manage to do anything.
I also installed alternate driver pack (link in DooMLoRD's tutorial), but it doesn't change anything.
That's it, guys. I REALLY hope you can help me, because I can't stand the official firware anymoreeeee. I know you rock the stage of phones
Cheers!

From A to Z, please
Sry for 2 posts, can't delete the second one.

[Fixed] I hard bricked my Vibe P1

Dear developers!
After successfully flashing and upgrading a friend's Samsung, I got the courage to do the same with my Lenovo Vibe P1.
I followed this video and everything was perfectly: I unlocked the bootloader, connected using QFIL and flashed the TWRP recovery he provided, until the 8:00 minute in the video the program said "Waiting for reset done..." and my QFIL just stucked on that message, so after waiting 5-7 minutes I disconnected the cable in hope that it will reboot to recovery, got some log errors and since then the phone is hard bricked.
Turning on does not work, recovery/bootloader/charging does not work, essentially the screen is dead, the only thing that works is recognization in QFIL program.
When I try to flash stock rom or that recovery from that video again, it first says a protocol error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I try to Download again, now it gets stuck at the Working folder (last message in the log, see below)
EDIT: Depending on the QFIL version, the version below actually gives the same error as above after few minutes.
In addition, any attempt to connect the phone to Windows using USB results in numerous partitions being shown from the phone internal memory (many of which Windows does not recognize as formatted):
(https://i.imgur.com/otd7e0M.png)
Is there anything that could be done to recover my phone please? Not having the right financial situation to purchase a new one and school starts soon so pretty bad situation for me now.
Kind regards,
kangarko

Update! I deleted all partitions from the phone and was successfully able to flash a couple of ROMs from the Internet (including a stock one). However, after each flash one, I get the "Waiting for reset done..." message and than the phone gets disconnected from my Fusion (virtual Windows 7 in Mac), and when it gets connected again it says Finished but the phone is completely black. No signs of any activity, it does not restart itself nor vibrates, and I end up with the problem in my first post again ;(

Help still needed... noticed I typed "Lenovo" in the thread title instead of Vibe, I corrected that but the PHONE IS STILL BROKEN.

Alright, got it solved somehow.
Flashed "P1a42_S272_160506_ROW_QPST" using QFIL 2.0.0.3 and Lenovo usb drivers v1.1.33 + Qualcomm drivers 1.0.
Newer QFIL versions are disfunctional over my device.
Always make sure to hold Power button for 13 seconds to make sure the device is OFF, then connect to QFIL. After it finishes the flashing process, simply disconnect and hold Volume UP button + Power button for 13 seconds and than again to make it boot.
You can find some useful stuff here (including TWRP):
https://forum.xda-developers.com/vibe-p1/how-to/qpst-flashing-vibeui-3-1-s272-rom-t3386650

kangarko said:
Alright, got it solved somehow.
Flashed "P1a42_S272_160506_ROW_QPST" using QFIL 2.0.0.3 and Lenovo usb drivers v1.1.33 + Qualcomm drivers 1.0.
Newer QFIL versions are disfunctional over my device.
Always make sure to hold Power button for 13 seconds to make sure the device is OFF, then connect to QFIL. After it finishes the flashing process, simply disconnect and hold Volume UP button + Power button for 13 seconds and than again to make it boot.
You can find some useful stuff here (including TWRP):
https://forum.xda-developers.com/vibe-p1/how-to/qpst-flashing-vibeui-3-1-s272-rom-t3386650
Click to expand...
Click to collapse
Hi there.Did you experience USB not recognized?I already removed the battery-reconnect-hold volume + then connect the usb cable but still USB not recognized.

[STOCK ROM] [QFIL] [GUIDE] Stock CyanogenOS 13.1 for QFIL + Unbrick from 900E/9008

Hey XDA!
I found somewhere in web stock rom for QFIL, that you can flash when your phone is hard bricked (like mine was) or when you want to remove Add-X for free. Here are the downloads:
Qualcomm 64Bit drivers
Full Qualcomm flashing suite
QFIL image
My mirror of QFIL image (use when AndroidFileHost is slow for you)
Here are the steps to flash it:
1. If your phone is in 900E mode and you can't reboot to 9008, get a spare USB type C cable or microUSB to USB-C adapter.
1a. If your phone can boot into 9008 mode without problems by holding all 3 buttons, go to step 5.
2. Now you must cut your cable like this (image credit: [email protected] from MIUI forums)
{
"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"
}
3. Burn plastic on green and black cable
Something like that:
4. Now when your phone is fully turned off (you can get back cover off and disconnect battery), connect cable to your pc, short green and black cables together and connect it to your phone. After about 10 seconds separate the wires. Now your phone will boot into 9008 (aka EDL) mode. If you will get Unrecognized USB device prompt, connect battery when phone is turned on into 9008, detach EDL cable and connect normal cable.
5. Launch QFIL and set it like that:
6. Click "Download" and wait until finish. If QFIL will error with "system.img/cache.img/userdata.img not found" create empty files named "system.img", "userdata.img" and "cache.img" in stock rom folder.
7. When QFIL will finish flashing, hold power button in your Swift 2. It should boot to system now. If not, try to flash TWRP/Stock rom via fastboot, doing factory reset in Cyanogen Recovery or "fastboot format userdata".
Credits:
Me
Mike's Tech Life from http://mikestechlife.blogspot.com that posted stock QFIL rom, Add-X removal tutorial (http://mikestechlife.blogspot.com/2018/01/removing-add-x-from-wileyfox-swift-2-2.html) and QFIL Screenshots
[email protected] from MIUI Forums EDL cable images
​

I have long written the exact same guide. What is yours for?

JavaVOBIS said:
I have long written the exact same guide. What is yours for?
Click to expand...
Click to collapse
I see your point about duplicate but I guess you could say @puszekkkkk added photos and info on kicking into 9008 ...your guide was the inspiration or first but both guides are useful to people ...hopefully i won't need either but neat trick with spare usb to get into qfil mode

This destroyed my computer :'-(
I'm sad/frustrated to report that I attempted to follow this guide and completely destroyed my desktop computer in the process! ? I made the cable exactly as instructed and made sure everything was carefully wired with nothing touching anything it wasn't supposed to. I tried repeatedly to get my ZTE device to boot into EDL mode but it simply would not. And then, when I was trying once again, holding the green and black wires together for a few seconds, I suddenly noticed an electrical burning smell. Looking at my beloved little mini-desktop PC, I noticed a very bright orange-yellow piercing light coming from within and then realized this was a flame!! ? I quickly unplugged the PC and ripped the case off, and then blew out the small flame that had started to burn a specific chip on my motherboard. I think this chip must have something to do with USB-port power supply/support. It's a very specific chip and not one I can find online to purchase to repair/re-solder myself. My device is four years old now and is unfortunately out of warranty. I called the tech support center for my device anyway (ASUS) to see if they could do anything, and also wanted to inform them that their product had caught on fire, but they just took my information and said they were sorry but that they couldn't help me with this at all.
So now I am without my main desktop PC. ???
And my stupid ZTE device is still a useless paperweight... ?

richaardvark said:
I'm sad/frustrated to report that I attempted to follow this gu ?
... Homemade cables are a bad way to enter edl
Use fastboot :
fastboot oem edl
Using test point:
Search on YouTube for a video on how to open your phone and "shorting" two contacts to enter edl ( this is the method used by technicians and manufacturers)
Click to expand...
Click to collapse

I Bricked my phone, Please Help

Hello, Friends from XDA
So long story short, I was trying to fix my Redmi Note 8's charging issue (slow charging and charges only when booted to OS). Then I decided to install a new rom from twrp (current was MIUI China, trying to install Xiaomi .eu) hoping that it might solve the issue but dumb me accidentally wiped the "system" partition during the wiping proccess. Now I am greeted with "The system has been destroyed" message". Cannot boot to twrp anymore. I really regretted doing that.
P.S. tried fastboot, doesn't work, ask for more
Anyone, please help. All suggestions are welcome.

When flashing a ROM you have wipe the system as well. This will fix that issue you are having(flash this after flashing ROM. This is a VBmeta.img):
https://mega.nz/#!r54FzQIZ!LgD3zSOBm1gOIzY6w8r8l-A8GChgWk_Z7HIN6y_bVLc
Use this command on fastboot mode
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
I suggest that you join the Telegram group as that's where I got this file from. Plus you will get help much faster.

@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
{
"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"
}

LiamPotat said:
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
Click to expand...
Click to collapse
That is alarming, so your device can boot into fastboot mode but won't be recognized by the PC?
Try using it on another PC because if you can't use fastboot or Recovery, the only thing that will save you is the EDL mode, and I have heard people say that the only way to access that is with an authorized account (which only xiaomi service centers have) or you will have to open the back of your phone and short circuit the EDL Chip.

LiamPotat said:
@Judroidz, Thanks for replying friend
Bro I don't know why but my pc doesn't detect the Redmi Note 8 in fastboot. Tried MiFlash, still not detecting.
Tested my friend's Xiaomi Phone and behold, it is recognized. ???
Here's a pic
Click to expand...
Click to collapse
Brother don't get panic , I had faced this many time's. Just remvoe your slicon back cover and connect device to PC( The ****y back cover interfere in connection), ( You need to put device in fastboot mode first) Flash fastboot ROM V11.0.3.0 via MiFlashTool(Note: Don't select clean all and lock)
Enjoy

Zulfi said:
Brother don't get panic , I had faced this many time's. Just remvoe your slicon back cover and connect device to PC( The ****y back cover interfere in connection), ( You need to put device in fastboot mode first) Flash fastboot ROM V11.0.3.0 via MiFlashTool(Note: Don't select clean all and lock)
Enjoy
Click to expand...
Click to collapse
He didn't put a cover on the phone. And he said that fastboot mode isn't being recognized

Judroidz said:
He didn't put a cover on the phone. And he said that fastboot mode isn't being recognized
Click to expand...
Click to collapse
In SS you can see the cover on device clearly

Zulfi said:
In SS you can see the cover on device clearly
Click to expand...
Click to collapse
Oh sorry I didn't see that. OP did you get anywhere with fixing your device

Judroidz said:
Oh sorry I didn't see that. OP did you get anywhere with fixing your device
Click to expand...
Click to collapse
Well bro, I'm still trying. Going to give the EDL mode a try and as you can probably tell, I am a newbie.
Any precautions, maybe tips that I should know about?
here's what I've gathered
1. Remove back cover
2. Find the edl testing points
3. Short circuit the testing points
4. Plug the device to pc (asap after shorting)
5. Flash using MiFlash (Hopefully recognizes the device)

So, it seems like you need an Authorized Account for flashing in EDL. I was hoping to find a diy solution but things get complicated. Well, I'm just going to send the device to a trusted local Xiaomi repair center and get it fixed (they have authorized accounts) and also solve the charging issue. Again, Thanks to everyone and XDA.
P e a c e

Xiaomi Redmi 7 - bricked/only EDL mode available

Hello,
I got an issue with my Xiaomi Redmi 7. I was trying to install TWRP with adb, but something got wrong, and now my phone seems dead, bricked.
Nothing happens when I try to turn on, can put on fastboot mode (with power+volume down), nor restart it with power+volume up. The screen are just black, and even the notification led doesn't light up when I connect the charger. My guess is the phone is in EDL mode.
Connecting to my computer it recognizes it as "Qualcomm HS-USB Diagnostics 900E", and I can see it on MiFlash, but when I try to flash any stock rom, it stucks in the very beginning. Here's a screenshot:
{
"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"
}
I've tried different versions of the stock rom, MiFlash and computers, but got the very same result.
Do you have any idea what can I try to bring it back to life?
Thank you in advance!
Tamas

tamasv said:
Hello,
I got an issue with my Xiaomi Redmi 7. I was trying to install TWRP with adb, but something got wrong, and now my phone seems dead, bricked.
Nothing happens when I try to turn on, can put on fastboot mode (with power+volume down), nor restart it with power+volume up. The screen are just black, and even the notification led doesn't light up when I connect the charger. My guess is the phone is in EDL mode.
Connecting to my computer it recognizes it as "Qualcomm HS-USB Diagnostics 900E", and I can see it on MiFlash, but when I try to flash any stock rom, it stucks in the very beginning. Here's a screenshot:
I've tried different versions of the stock rom, MiFlash and computers, but got the very same result.
Do you have any idea what can I try to bring it back to life?
Thank you in advance!
Tamas
Click to expand...
Click to collapse
Hey mate, I'm not sure if you fixed it or not but I'm pretty sure that if it can boot to fastboot it's not bricked. What I suggest you would do right now is install xiaomi drivers onto your pc first and foremost (this actually fixed all my problems) then try to use adb and fastboot tools to fastboot flash recovery twrp.img. if that works you're safe and then proceed to advanced wipe, then vendors and system wipe then in an SD card or an otg flash USB install the lastest global or Europe ROM for miui 11.