So I have this phone Xiaomi Redmi 10X, and I wanted to put Pixel Experience 11.0 in it, after seeing this thread on GitHub.
To my surprise, following steps on that link was not that easy!
I flashed MIUI 22.1.19 manually (not in the correct way), and I ended up with a hard bricked phone.
Yesterday, while Googling about that, I managed to run into a tool called MTKClient v2.0
{
"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 it solved my problem, by flashing original firmware and got it correctly working with the default MIUI 13 system.
BUT, that wasnt enough for me, because I still wanted to put Pixel Experience in it since I like it so much and think it is so sexy!!! So I, without knowing what I was doing, erased all the partitions in my phone with that tool.
Now, I cant get it to connect to that tool to work or connect with my device. On the cmd behind though, I do get some hope after seeing that device is still recognized in some way, but that's all there is to it, it doesnt go further, only "Phone detected: Reading model info".
I've tried to wait and keep both volume buttons pressed at the same time, but to no avail.
Since this, I've tried several tools but none is working to reset my partition table to original state, since I think that's my problem.
Any idea how to fix it?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
No. What is that?
Jjflick said:
Did you try cross-patching it with a razor cable?
Click to expand...
Click to collapse
Even if it connects, it shows no partitions to write over.
What it needs, is to first restore the erased partitions, I think, and then writing (flashing) the firmware into it.
Related
I've bought this Coolpad 7295 phone for less than three days from China.
It seems that I couldn't flash my phone back to the state where I could get the service for calling the first day.
After the second rom flashing with my flash tool. I kind of formated the Yl-parames and NVRAM section of the phone.
I don't know these two mean! Could someone explain how they work? Are they related to the hardware or the motherboard of the phone?
After the wrong formatting action, my phone could not make any calls. (But everything works, and network works also. And later I flashed many roms, all of them work, just no signal)
So the third picture shows that this device has a different partition compared to the most smartphones in the hardware called "YL-parames".
My friend who is good at making custom roms in Taiwan said I might accidentally screw up with the hardware partition.
I just want to know with this problem appearing, is there any other way that I could get my signal back?
I've tried several methods like rewriting IMEIs, reinstalling the official roms, but none of them work.
Or should I just send it back to the dealer to get it fixed? (I'm doing it right now...)
Just want to know in case the phone is back, how should I operate this flashing tool because I'm really a tech-savy
1) The first picture represents what i chose for the outcome of no signals later on.
2) The next one is its interface
3) The next one is the official flashing tool, but I still can not flash the CPB provided by the official since my hardware seems to be broken.
{
"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 would really like somebody to develop the custom rom in the English version for this device, this device is pretty good!
Or is there anybody using this phone as well? It's nice to have someone to exchange info with!!
please help me I have been trying solutions for 2 months but nothing works. I also tried to do
1 go to wipe
2 go to advanced wipe
3 select date
4 repair or change flie system
5 change flile system ext 2
6 then replace ext 4
but it does not work. when i try to boot in to the system it goes into an infinite loading screen. please HELP (I used google translator because my english sucks)
@Boyko99
Either boot-loader broken or Android system corrupted. Re-flash Stock ROM.
I don't know if my answer came to you so I'll rewrite it
jwoegerbauer said:
@Boyko99
Either boot-loader broken or Android system corrupted. Re-flash Stock ROM.
Click to expand...
Click to collapse
could you tell me how to find the Stock ROM. I need help because I'm not very practical in modding
Boyko99 said:
could you tell me how to find the Stock ROM.
Click to expand...
Click to collapse
GIYF ...
i downloaded this now what should i do? and with what program?
jwoegerbauer said:
GIYF ...
Click to expand...
Click to collapse
i downloaded this now what should i do? and with what program?
{
"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"
}
@Boyko99
Because you avoided to name phone's brand/model in this thread's title you can't really get advised.
Anyway:
Assumed these requirements
got fulfilled, the USB-driver suitable to your phone is installed on PC,
then the basic steps to perform are
1) Unlock phone's boot-loader, if not done yet
2) flash the ROM
@jwoegerbauer
I can't start the phone so I don't know how to do it I'm stuck in twrp because if I try to turn it on it goes into a loop
@Boyko99
My POV:
This is the price that people who think they must improve (?) phone's Android, will say put up a better (?) ROM / Recovery than that what gets pre-installed by OEM/Carrier ( in their R&D department there are certainly no idiots sitting around ), pay.
@jwoegerbauer
i have a note 3 its the worts rom of all
Hi there,
I'd really be grateful for any help anyone can give. Yesterday, my Honor 7C got stuck in a boot loop, restarting at the blue Honor screen continually until the battery runs out. It's impossible to boot it into recovery mode using any combination of key presses. It just keeps restarting.
Can someone please help? I don't really mind losing the phone, but ideally I would like to save some of the data on it, as it had been a while since I backed up.
I understand that the way to do this might be to flash the stock ROM, root the phone and then run a data recovery program like EaseUs. Is this correct?
Also, I have tried to flash the stock ROM but really have no idea how to do it. I got half way through using SP Flash Tool before I realised that the Honor 7C is not a Mediatek phone.
Also, I can't find the stock ROM (LND-L29) anywhere except on pretty dodgy looking websites. Is there a reliable source for stock ROMs anywhere?
Any help would be really gratefully received. Thanks!
B7C
@Bricky7C
Your Honor 7C has a Qualcomm chip-set hence you might use free-of-charge QPST ( read: Qualcomm Product Support Tool ) to re-flash device's Stock ROM.
{
"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"
}
Turns out my bootloop was caused by a hardware problem after all - ripping open the side of the phone solved it.
However, for anyone who stumbles across this thread with a similar problem, jwoegerbauer's suggestion of QPST was very helpful, but the tool on the site would not install for me on Windows 10. I kept getting an "installation was interrupted error". However, I found a working version of the tool at:
androidmtk dot com fslash download-qpst-flash-tool
[I'm a new user so XDA won't allow me to post a URL]
I scanned for viruses and the installation didn't cause me any issue, though I never ended up having to use it in the end.
Well, it's a bit of a long story, so I'll try to be as short as possible.
Last year, and after hours of searching on the internet, I found the solution for "Custom binary blocked by frp lock" on this forum (here and here). Both methods promised to fix the lock without erasing my data, but I decided to try the second one (it consists of reinstalling only the boot image with Odin).
Fortunately it worked for me on the first try, and since this method was not well known on the internet, I decided to make a video tutorial to help those who had the same problem and wanted to keep their data.
The fact is that, unfortunately, this method didn't work for everyone, and in many cases it generated bootloops or black screens of death.
And my question is: does anyone know what could be the cause of this?
I tested it on SM-J710MN and SM-G532M, both running Android Marshmallow, and the bootloops/black screens occurred on devices running Android 6, 7, 8 and (I guess) 9 and 10.
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
jwoegerbauer said:
Starting with Android 6 FRP on any such Android device is automatically enabled once a Google account is logged in to a device. The only way to get rid of it is by removing the account from the device into which it has been synced.
Click to expand...
Click to collapse
Thanks for answering.
Maybe I did not express myself in the correct way, but actually I was referring to the block that does not even allow to boot the device and only shows words in red, as seen in this 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"
}
But beyond that my question is about why does the bootloop or black screen happen after flashing the boot.img file? Does it have to do with a different/incompatible version of Android/binary/csc or something like that?
Ok, so i got this random Huawei P20Lite right?
Back isnt pealed off, works fine, no damages.
BUT WAIT... About Works Fine... It Wont really boot up into The OS!!!
Somethimes shows this really weired Image when pluged in and charging the phone, or randomly:
A green Screen with a Red Square on Top and a Blue one Down.
{
"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"
}
Not My Picture
It will then boot up and greed you with A:
Again, not my Picture.
Acording to Huawei, You have to Use HiSuite to recover it.
1. Put the Phone into Fast Boot. AND conect to PC
2. Open HiSuite on Your PC and click on Recovery mode or whatever its called.
3. i donk know i forgot.
anyways, i get this nice little message
(In translated, this means That: Your Device doesnt support System Recovery.
Bro wth
Anyways, our phone story doesnt end there...
I tried doing it without the Computer.
using eRecovery!!! not surprising i know...
Still, it was stuck on booting animation trying to enter eRecovery.
According to Huawei, "this message is displayed when a system file is replaced or modified, or the system is manually updated to an unofficial version". They were responding to another user with the same issue as mine.
I think that this is the Issue. Still, the instructions to fix it, dont work. (as tested above.)
Tutorials show the eRecovery method without the PC.
Here are some info i found:
Another Guy having the same issue:
i forgot the link but someone else on XDA Had the same issue.
please help!!!
hello sir did you have any luck resolving this issue (I've purity much looked every were but I had no chance)