Okkaayy guys, so, i'll take you to the end of the whole thing which is, I installed and downgraded 2 versions in stock rom, which was V12.5.1.0 worked like a charm, then I updated the version with Xiaomi's original it's own system updater to newer version and it was still fine then I updated it to Android 12, MIUI 13 and it bootlooped.
So, I wasn't able to get into recovery, trieedd soo many times and neither I was able to get in to fastboot mode. What did I do? Flashed it again with Format All + Download option. I got the bar and everything but I waited a bit and nothing happened. I'm like, is this working? And I did the mistake. I pulled the plug. And here I am. Surely I've 60+ battery. Besides that I charged it for more than 15 minutes. No power button works, no fastboot, no recovery. Nothing "HAPPENS". Literally. No matter what I do, how long I press to any button, device won't turn on in any sort of way. Libusb still detects it as Mediatek driver but I can't use SP Flash Tool because simply device won't turn on. Bypass utility stays like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Held power button for 5 min (literally I did) nothing happened
No fastboot or recovery
SP Flash Tool simply can't do the trick because device doesn't turn on
I have 60+ battery %100 surely.
USBLIB still able to detect the port.
What do? Is it even possible to rescue this poor guy? It was my main phone btw...
EDIT - UPDATE: I have no idea how but I was playing around with SP Flash Tool, trying to do some things, nothing was actually happening but like after few minutes phone just gone back into bootloop, It turned on, I genuinely don't know how and just for confirmation, after I installed stock rom back my charge is %73 so surely it wasn't related to my battery. IDK this devices are weird. Sorry for the topic mods..
Related
It is showing a small round mobile phone, 2 dots, a ! inside an orange triangle, 2 more dots, and a computer.
This is the first time I'm seeing this screen.
Edit: Just to give some insight as to what I was doing...
I was using a SGT7 build of CM9, and I noticed USB Tethering wasn't working (native nor Wired Tether 1.4 worked). I had to run to a friends house for the night real fast, so I figured I'd just go back to Stock firmware and use that for a few hours just so my desktop could get Internet.
I am also using Windows 8 Release Preview. Odin could see my device fine, but upon pressing Start to start the flashing process, it did nothing (I'm guessing Odin or Samsung's drivers don't work well on W8RP). No progress was made on either Odin or my tab for about 5 minutes. Since nothing was done, I figured I could close Odin, and restart my Tab. Now I only get this 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"
}
I immediately went to the "How To Unbrick Your Galaxy Tab!" thread, but didn't find mention of the screen I described in this post, and then I made this post in panic.
When I went back to Windows 7, Odin was able to reflash my tab successfully, and USB Tethering was working fine. So perhaps Windows 8 has some weird incompatibility with Samsung Drivers? In any case, this might serve as a warning to anyone trying to use Odin in Windows 8.
I think it was mentioned in a few threads.
Many confirmed that it is another download mode.
You just have to make sure it is fully charged, and keep trying Odin restocking. It will go through.
(I never experienced it myself)
Edit: many reference, just search in here fore "phone exclamation pc"
Yea it would seem it's another download mode. I was able to flash with Odin just fine in Windows 7, so all is well again
i have said this in many threads. this is the result of faulty flashing. just use the latest version of odin
please thank me if you found this helpful
Sorry I posted in another section, I will not change it some moderator
Playing I decided to make a setback from the B584 to the B052 (damn idea), well I put the B300 transition file in the dload folder and finish in the ALE-L21C432B300 then update it also copying the dload with the complete B188 by pressing vol + y Vol - at the same time, it was restarted and started to update wait a good while until it restarted again, as is normal to re-update by OTA.
I got the problem my phone left the screen between gray and black, it makes the sound on power up, the keys work and the graph of the mobile phone I think it does not recognize the drivers and it is not seen.
Bootloader works and the touch but not seen (attached photo) connects well with the PC and I can get into fastboot in fact I have recorded the full B052 by fastboot and boot the phone does not see anything but hear the boot sound And the tactile works.
Also if I connect it to the PC I recognize the internal and the Micro SD only with the B052.
Only works (the boot sound is heard but nothing is seen with the B059) and now that is the b596 v2 of sokkoban and wanted to try it who would send me to make the recoil, well that everything is for science and forum: )
Any idea to solve this problem I know that the screen is not new since two months ago rather it will be the partition or something internal Software ?.
Could you repair it from the ODB console, FASTBOOT, ETC.?
{
"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 had the exactly same issue about a month ago. Solved it by sending the phone to Huawei for repairs.
I don't think it's a driver issue, as they replaced the whole display (among with reinstalling the firmware).
vhristenco said:
I had the exactly same issue about a month ago. Solved it by sending the phone to Huawei for repairs.
I don't think it's a driver issue, as they replaced the whole display (among with reinstalling the firmware).
Click to expand...
Click to collapse
Then you think it's from the screen, if it has not had any hits, it's new for two months, this happened to you when you installed the firmware. thank you very much.
Many thanks to all I have solved it for whatever it is the display but by chance it broke me at the same time I made the recoil, well I will have to spend again € 30 per screen change.
THEME CLOSED thank you.
I'm working on a Galaxy Note 5 that I am trying to reset the firmware on. Someone's installed a custom build (that's verified in the "about phone" details) and it co-opts the volume down button boot sequence, so I can't get into download or safe mode. I've attached a screenshot. Has anyone seen this before and how to I purge this thing?
{
"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"
}
Your image isn't showing.
Image not showing
Ok, let's hope this works as a link to the image:
This happens with the power-volume down and power-volume down-home sequences, so I can't get it into safe mode. Someone's definitely put a custom image on, but I'm not sure how to clean it/replace it.
The power-volume up sequence works fine, but since this is a custom image, it won't get cleaned off by wiping the cache and/or factory reset.
Apparently, since I'm a newbie here, I can't post external links, which makes the forced external URLs for images a little useless to me right now...
Can't you just power off, boot into download mode and Odin a stock firmware, then re-root after?
blud7 said:
Can't you just power off, boot into download mode and Odin a stock firmware, then re-root after?
Click to expand...
Click to collapse
That's the thing - whoever did this co-opted the sequence to boot into download mode - power + volume-down/power + volume-down + home. I did find a way to do it without needing to go into boot mode, but I can't post the link here because I'm a newbie! That should solve my problem - I'm just setting it up on Linux and I'll keep people posted on the solution.
What's happened is that someone's basically done a custom firmware/kernel combo that makes it impossible to get into download mode, so you have to totally backdoor it. When I get it working and verify it, I'll post the solution here.
After upgrade to miui 13 yesterday, everything was fine.
Today, play extensive mobile legend halfway got reboot.
I haven't try to wipe data because have not backup my stuff yet.
Try to connect Mi assistant, it stuck when connect USB to pc under MiPCsuite. No response at all.
The rest, after 5 to 10 second at home screen, reboot again.
Any idea how to backup files before i hard reset this problem. ? Or
how to resolve this reboot issue?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you could try to boot into twrp and transfer the files to your pc
get your twrp and info here
Goodluck
I am in the same boat, keep restarting as soon as you swith mobile or wi fi, if you keep those off it stay without re-booting. What the hell is broken with the update? I don't want to factory reset all? Any suggestions?
MrScarl3t said:
you could try to boot into twrp and transfer the files to your pc
get your twrp and info here
Goodluck
Click to expand...
Click to collapse
1/ the device must be unlocked.
2/TWRP does not work 100% in Android 12 and restoring from Android 11 to 12 will cause problems assuming that the backup is possible.
arnasx69 said:
I am in the same boat, keep restarting as soon as you swith mobile or wi fi, if you keep those off it stay without re-booting. What the hell is broken with the update? I don't want to factory reset all? Any suggestions?
Click to expand...
Click to collapse
Were you able to find a fix for this problem. Had updated it to MIUI13 (India) a month back but had suddenly started rebooting immediately when data or wifi is turned on.
surya1078 said:
Were you able to find a fix for this problem. Had updated it to MIUI13 (India) a month back but had suddenly started rebooting immediately when data or wifi is turned on.
Click to expand...
Click to collapse
yeah the annoying fix called the factory reset. I didn't find any other fix for this.
Hi
So uhh, I followed this link about flashing 10R firmware into oneplus ace racing, I followed it and not sure where it went wrong.
now my phone is hard bricked with a blank screen like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can turn it off when it's unplugged, by holding power and vol+ button. But when a cable is plugged in, the phone will keep rebooting into that screen.
I found the stock firmware to reflash into this phone, but my computer doesn't see the device when it's plugged in, and it won't turn off.
I can't see the phone on adb or fastboot powershell either.
Anything advice please?
The only way is to send it back to oneplus center. 10R firmware doesn't fit ACE Racing Edition.
sidluk said:
The only way is to send it back to oneplus center. 10R firmware doesn't fit ACE Racing Edition.
Click to expand...
Click to collapse
what if I can't? is there any online fix? people who sold me the phone said they can't send it back..
wanderingwan said:
Hi
So uhh, I followed this link about flashing 10R firmware into oneplus ace racing, I followed it and not sure where it went wrong.
now my phone is hard bricked with a blank screen like this.View attachment 5731211
I can turn it off when it's unplugged, by holding power and vol+ button. But when a cable is plugged in, the phone will keep rebooting into that screen.
I found the stock firmware to reflash into this phone, but my computer doesn't see the device when it's plugged in, and it won't turn off.
I can't see the phone on adb or fastboot powershell either.
Anything advice please?
Click to expand...
Click to collapse
You should not have done that. That guide was specifically for OnePlus Ace because Ace(Released in China with ColorOS) and 10R(Released in India with OxygenOS) are same device, just for different region so it's firmware is inter-changeable.
OnePlus Ace Racing is different device entirely. It will not have OxygenOS since it is not released in any other region expect China.