Develop Bugs

Can't get into recovery mode

I flashed JG5, updated to modaco's r3 and then tried to flash mimocan's stall fix which killed my phone (progress bar stayed on 0 and phone went black).
Now I've reflashed JG5 and cannot get into recovery mode.
VolumeUP+Home+Power just starts up the phone as normal ( I have tried multiple times)
VolumeDOWN+Home+Power still gets me into download mode.
Any ideas?
EDIT: Managed to reboot into recovery through adb.

I have the same problem here.
I can enter in recoery mode only with abd or reboot widget ...
Anybody else ? volume up + home + power doesn't semm to work ...
EDIT : the pb occured when I flashed the JG5, and I have the same problem in JM1 and JM2 !
EDIT 2 : I manage to acces to recovery mode.
I pressed volume up + power + home and when the i9000 logo appeared I released power !!

i've had a bad flash with latest firmware, odin became stuck at "do not power off"
now i get the "cannot connect" icon and the device isn't detected when i plug in the usb cable.
i've installed both kies and usb drivers, but still nothing.
any ideas?
i actually get a com 7 usb serial port driver but the device isn't detected by odin. the drivers installed are default from microsoft.
10x.

Had this issue myself.
I disconnected everything. Restarted the computer.
Opened the back of the phone and removed the microsd card, sim and battery.
Put the battery back in. Placed the phone in download mode.
Started ODIN and entered all the files then connected the phone to the computer and flashed as per normal.

Ancient_One said:
Had this issue myself.
I disconnected everything. Restarted the computer.
Opened the back of the phone and removed the microsd card, sim and battery.
Put the battery back in. Placed the phone in download mode.
Started ODIN and entered all the files then connected the phone to the computer and flashed as per normal.
Click to expand...
Click to collapse
Exactly that!
If you don't get into recovery mode by pressing volup+home+power, you are just pressing them too long or short or alternatively didn't turn off the phone before trying it (not necessary but makes it a lot easier)
The symbol of the phone with the
{
"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"
}
and the pc is NOT a "cannot connect" screen it is a "DO CONNECT" screen. Restart in download mode (if necessary by removing the battery as above) and reflash!

it worked, i think i was pressing them in the incorrect order or something.

I found I had to do it a couple of times to get it to work as well.
Just have to keep at it. Maybe my old fingers are not clicking at the same time.

Cant get me Gt-9000I into recovery mode & cant on usb debugging because pattern lock.
I've got an old GT-9000I which cant get into recovery mode with button combinations. The bad thing is phone is stuck in pattern lock as well. I forgot my pattern and phone is showing email verification for unlocking device which is also not working.
Is there anyway I can flash my device with altering some circuitry or applying anything.

[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.

Fastboot / Bootloader doesn't exist..?

Hello,
I've tried researching this issue but nobody seems to have the same issue that I do.
Background: I've had my Pixel C with the stock OS (Android 8.1.0) and everything else stock. It is not rooted, and the bootloader is not unlocked as far as I know. I bought it on eBay like 4 years ago. Never had an issue with anything. I have connected it with multiple USB A to C cables (to rule cables out) on multiple Windows computers (to rule out specific computer issue) that I've used with ADB on my OnePlus 7 Pro before, so all the platform tools should be good (ruled out that the platform tools were the issue).
Issue: I cannot boot this thing into fastboot mode. I can connect it to adb and get it listed in adb devices just fine. I set it to always trust the computer. I try issuing a "adb reboot bootloader" and the Pixel C screen shuts off like I would expect. The screen goes black, then...nothing. The rainbow lights on the back light up as though it's powered on, but nothing ever happens.
Troubleshooting:
So far, I've tried turning off the device completely, then powering it up while holding down the volume- button. This gets me the same black screen with the rainbow lights turned on.
I've tried holding volume- & volume+ while booting, and that gets me into Safe Mode (whatever that is). I've tried volume+ and power, which doesn't seem to do anything at all.
I checked device manager, and the device gets detected when it is in OS, but when I issue it the adb reboot bootloader command, and get the black screen, NOTHING shows up in device manager. No "other device" or "unknown device" or "android device" anything. In fact, listening for Windows audio alerts, I hear the device disconnect when it reboots, then I never hear it reconnect.
At some point after boot cycling it multiple times, it came up saying "The device is having trouble booting, you can click try again or you can try reformatting." It looked like the stock recovery, but not fastboot or anything. Haven't gotten that to show up again. I did go through with the device wipe.
If anybody has ANY ideas for how to get this thing booted into fastboot, please send them my way. It would absolutely make my week
EDIT:
Just tried this and am getting somewhere hopefully...
I did "adb reboot recovery" and it gave me the dead Android screen. Did Power & Volume+ and got the menu opened. Was able to get an adb sideload working and I sideloaded the latest OTA. Here is the logs shown on screen:
{
"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"
}

Stuck in a bootloop but can't go into recovery and phone isn't recognized by pc.

Ok, so this is my first phone without a removable battery so very new in terms of fixing bootloops. I just have to deplete the battery because I can't turn off the phone in said bootloop, and also when I plug the charger it goes into loop again...
So anyways, it's very sketchy but 1 out of 20 power-ons I can get it into bootloader/fastboot? but I can't get adb or MiFlash tool to recognize the phone. So for now it's a brick. Is there any way to fix this? My phone has unlocked bootloader and had pixel experience 9, and it was years ago since I did all the romming so I don't have the old files nor the old drivers because of fresh Windows install.
Looking forward for your answers.

How did you get in bootloop in the first place? Did you try to boot to the recovery using volume up and power button?

Phone used to freeze and reboot lately because of high ram and storage usage (like 2gb free) I think. Or could be an entirely different thing but I didn't mess with system level apps in a long time. Just that in one of these freezes it never finished booting up.
I tried the recovery but it freezes before I can get to the menu. I have TWRP by the way.

Fedegblack said:
Phone used to freeze and reboot lately because of high ram and storage usage (like 2gb free) I think. Or could be an entirely different thing but I didn't mess with system level apps in a long time. Just that in one of these freezes it never finished booting up.
I tried the recovery but it freezes before I can get to the menu. I have TWRP by the way.
Click to expand...
Click to collapse
When the phone is turned off press first the volume up and while holding it press the power button. After phone vibrates release the power button but still keep the volume up button pressed and wait until twrp starts. If it gets stuck again tell where exactly.

I think I managed to understand how f'd up it was. The phone freezes even in Fastboot mode, I just didn't realize it and it was the reason it didn't get detected by the pc. Seems like I have few windows of time where it detects the phone and button inputs, but mostly freezes where it likes and can't do anything until battery drains. And then charging makes it go into loop again.
I'm tempted to take advantage of the phone being recognized and flash something into it. Maybe boot.img or twrp.img, what are your thoughts on this?

Fedegblack said:
I think I managed to understand how f'd up it was. The phone freezes even in Fastboot mode, I just didn't realize it and it was the reason it didn't get detected by the pc. Seems like I have few windows of time where it detects the phone and button inputs, but mostly freezes where it likes and can't do anything until battery drains. And then charging makes it go into loop again.
I'm tempted to take advantage of the phone being recognized and flash something into it. Maybe boot.img or twrp.img, what are your thoughts on this?
Click to expand...
Click to collapse
If USB debugging is working you can try to flash twrp or even fastboot rom with MiFlash.

Ok, tried to flash twrp but it says write protected, so I did "fastboot boot twrp.img" but freezes in the same place as my old twrp. Seems likely I have to flash stock now.
Edit: On second thought I might be able to do something else now, even if it freezes before the twrp menu it's showing with "adb devices" instead of "fastboot devices" so I will try dirty flashing what I think is the same rom as before.
Also, if it's likely this issue with twrp I will be sad. I have no idea when my internal memory got encrypted since it was one of the first things I didn't want when I first romed this.

Welp, after days of trying to enter fastboot again I find myself with this problem.
Spoiler: Image
{
"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"
}
Tried fastboot -w or flashing twrp and orangefox recoveries but same ol' same ol'. Write protection error, it's likely to be hardware issues, but I'm open to suggestions.

Your Odyssey might have an end!
Try to flash the factory rom instead, the one that came with the device, not the most recent one!
I'll guarantee it will work!
I also would try OrangeFox recovery if I was you... way better then twrp. Both my devices have OF as recovery.
Note 5 Pro and Note 8T. My willow have Carbon OS on it but I'm not using it since it only serves as a backup device, in worst case scenario...

[Help me]Xperia XA2 Brick I also don't know what the reason for this is

I use this phone normally to watch youtube, and use social apps, and he changed wallpaper without i do nothing, i try change to my wallpaper to normally, but he dont response, and i reset the phone and when turn on, stayed like this, i try format and no sucess, any have idea how to fix him ?

Hmmm...
Custom ROM or not, root or not?
Go into recovery mode and clear the cache.

ze7zez said:
Hmmm...
Custom ROM or not, root or not?
Go into recovery mode and clear the cache.
Click to expand...
Click to collapse
not custom rom and not root, in video i show recovery mode and i cant enter in android configuration

Go into recovery mode (with the device powered off, hold Volume Down + Power) and you see what options are available. I'm not suggesting anything because I don't know the device, but I'll hint when I see a screenshot in recovery mode.

ze7zez said:
Go into recovery mode (with the device powered off, hold Volume Down + Power) and you see what options are available. I'm not suggesting anything because I don't know the device, but I'll hint when I see a screenshot in recovery mode.
Click to expand...
Click to collapse
{
"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"
}
this is recovery mode i turn on hold volume down and power, in this phone, he call "Security Mode" in my language, dont have options in screen

and i try turn on with hold volume up and power, one blue light appears and the phone dont response

HeenryL said:
this is recovery mode i turn on hold volume down and power, in this phone, he call "Security Mode" in my language, dont have options in screen
Click to expand...
Click to collapse
The image shows that the system booted into safe mode, not recovery mode. Can you check with the adb devices command how the phone connected to the PC responds?
Recovery mode looks like >this< video at 1:30.

ze7zez said:
The image shows that the system booted into safe mode, not recovery mode. Can you check with the adb devices command how the phone connected to the PC responds?
Recovery mode looks like >this< video at 1:30.
Click to expand...
Click to collapse
i try enter in recovery mode according to the video, he fixed in loop boot and use the ADB commands in CMD the phone dont response, just returning "waiting device", i buy new battery for my old phone to the fix him, will arrive in two days, I bought this xperia 2 months ago, its already broken its very sad for me, in my country this phone cost 2 salary, and sony dont offer oficial support here, i just put he in closet and forgget him, guy very very thanks so much to try help me, and your time too, thanks

try download the firmware with xperfirm later flash with newflasher but the newflasher files in firmware downloaded archive next cilck the newflasher exe and good luck i hope make a back up of yoru drm keys

sony xperia xa2 ultra stuck on dead battery and sony screen and wont go past them
so this morning in class I lightly dropped my phone from my hand onto the table lightly, and that was it, I had this phone for a while so its filled with stuff. Its stuck on loop on the Dead battery sign to the white sony screen and none of the...
forum.xda-developers.com