Hey! so first post to the forums.
But i recently got a second hand find x3 pro as my new phone after my last one was broken. Ive had it around a week and just noticed a software update so went ahead and installed it. the phone then proceeded to restart and is now stuck on a bootloop, usb debugging is not enabled nor is oem unlocking. i am unable to access recovery so i am assuming it was removed or corrupted and i have no clue what to do.
Global version of the phone if that helps in any way shape or form.
Related
Hi guys,
I've bought an P9 and wanted to get rid of the booting screen with the resellers logo.
So I thought I'd be smart, unlocked the device, flashed TWRP 3.1.1-1-eva.img onto it. Got an SuperSu-file and tried to install it...
I never got to experience the rooted version. Got stuck in a bootloop, somehow got out of it. Logged in, saw an green SuperSu-app, opend it and it saidthe device has to be rooted to use the device, ergo i failed to root it. [Forgot some steps here] and I found myself in another bootloop. A friendly guy suggested to flash these 2 files
[Link-Removed]update.zip
[Link-Removed]update_data_full_hw_eu.zip
which I did with dload. After that, I was still in a bootloop, but with WipeCache I was able to get myself back into my phone [hooraay].
The happyness-phase was a short, because i soon found out, that it doesn't have an keyboard (only googleVoice, should be fun to type in a wifi-password). Huawei-ID tab is also missing (usually located below Accounts), Update Phone, which was between Advanced Settings and About Phone is also missing, and bluetooth doesn't seem to work. That's when I noticed that I'm on NRD90M test-keys build.
After reading some threads here i downloaded rollback from huawei (for west-europe). Now I'm on C900B300 but all settings still missing.
Now I'm here crying for help.
Any suggestions? Please?
Ryan
You got to rebrand your phone.
movizdb said:
You got to rebrand your phone.
Click to expand...
Click to collapse
do you mean, that i have to put the bootlogo back into it?
could be a meanie to do, because it's a swiss brand and I don't think that there's a version here for me to use.
//or do an OEM-Flash, which worked
My mi5 is stuck on this screen.
I have access to TWRP on the mi5.
It has unlocked bootloader.
Adb and mi drivers are installed.
Have access to OTG.
Can anyone kindly guide me through the simplest process here?
For recovering my phone do I have to flash global stable/developer necessarily?
I had global developer previously (miui9) to which I flashed TWRP successfully but when I was flashing the SuperSU zip, it got stuck here.
Kindly help me fix this and tell me what I did wrong to get softbricked.
I know it's in bad condition lol, I drove over it and then bought a new phone so decided to experiment with it.
Sadly it's he hardest phone to root/recover I've ever encountered.
I've played with Samsung Galaxy Alpha/Few Sony Ericsson phones and a spare Gionee M5 lite, even though they had less support I figured them out pretty easily.
My phone suddenly get stucked into Redmi boot logo, cannot access system recovery but can access fastboot menu.
The problem is I hadn't enabled OEM unlock and developer options before. All the methods that I found so far requires bootloader unlock for that I also don't have MI account . What might be my next move? Thank you.
its hard to say what we can|t do with a still locked bootloader. if going to an authorized service center is out of reach, all we can do is try i guess. id still suggest going there if you can easily access your google account.
there are a few threads that say we can flash a still locked bl, but im not so sure.
Flash stock ROM/Recovery, lock bootloader?
Is there any guide on how I can complete return phone to stock and lock bootloader? Thank you.
forum.xda-developers.com
official stock roms can be hard to find on their site, heres an easier to navigate 1.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
gl
With EDL mode? I'm in a similar situation, a friend's mother forced a shutdown during a firmware update and destroyed the system that way. Of course the bootloader is blocked. I find it extremely stupid of Xiaomi to rely on a working system to give you the chance to unlock the bootoader but I guess that's how you sell some extra phones.
So far I've taken out the rear cover and the plastic that goes on top of the motherboard, unplugged the battery and with an arduino cable and some fiddeling shorted the "boot" pins while connecting the USB cable. Seems to be working given that MiFlash has changed the locked bootloader error for "indice fuera de limites" or in English "index out of limits error". I guess I don't have the right ROM so I'm downloading another one, but I'm struggilng to find the correct original fastboot ROM. The first one I've downloaded from Mi Community, the second one is from xiaomifirmwareupdater, but is gonna take forever to download. And I mean... F-O-R-E-V-E-R
Jaki1122 said:
With EDL mode?
...
Click to expand...
Click to collapse
gl with that, as only authorized people can properly flash from there. while i havent used EDL, there are some trusty people who can help us out (ive seen it in tg groups)
a site did say maybe using another version can help, who knows it might do the trick
https://c.mi.com/thread-2027947-1-0.html
also seems weird how goolag hasnt fixed half flashing from destroying, last time i had that happen was '12
I own a Rog Phone 5s (ZS676KS) since one week and tried to install TWRP without success. The result was a bricked phone and stressful days with no prospect of a solution. In this forum I found the following tutorial and completed it successfully
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
The update via the settings does not work, no update is found. So I downloaded the latest firmware from Asus and saved it in the internal memory. After restarting the phone I get a message that a system update is available, but it ends in an error message. I have tried the same with the previous firmware versions, but without success.
I would be very happy if someone has a solution to this problem.
RT3K said:
I own a Rog Phone 5s (ZS676KS) since one week and tried to install TWRP without success. The result was a bricked phone and stressful days with no prospect of a solution. In this forum I found the following tutorial and completed it successfully
Repair ROG Phone 5S through edl firmware, no need to unlock Bootloader to modify COUNTRY CN to WW
Success is disgusted by some people, and will not share any files for free in the future.
forum.xda-developers.com
The update via the settings does not work, no update is found. So I downloaded the latest firmware from Asus and saved it in the internal memory. After restarting the phone I get a message that a system update is available, but it ends in an error message. I have tried the same with the previous firmware versions, but without success.
I would be very happy if someone has a solution to this problem.
Click to expand...
Click to collapse
Hello and welcome to XDA,
This is intros section, you might have better chances on your devices section.
Good luck.
Hi all,
Quick backstory: I bought a Google Pixel 5a (from the USA) for my cousin who lives in India. The phone was working fine for him until about a few weeks ago when the phone was stuck in a boot loop. Unfortunately, my cousin did not have USB Debugging on and the OEM is locked.
I was able to help my cousin adb sideload the latest Full OTA update. The install completed successfully but when we try to restart the device, the phone bootloops once again. If we leave the phone to continue bootlooping, it gets very hot (which seems obvious but wanted to share this as well).
I cannot think of any other steps to take and it feels like this is a hardware driven issue. Worse yet, since my cousin is in India, we cannot service the phone. Posting here to see if anyone else has had a similar issue and was able to figure out what it was. Any advice helps, thanks!
did you try to extract the payload.bin to get the boot.img file and flash it to slots a & b .i think you can do that with twrp. with the bootloader you might not be able to do that.