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)
Related
hello guys
my bro come back and bought me a new Mobile (Huawei Ascend Ascend Y320-U30) and from first open at 30 mints it was fine and fo a phone call on it last for 12 mints .... when i try setup gmail acc and register it ... got froze and not respond to commands :\
at first there is a message said ( Google+ service stopped work) then i realize maybe cuz this cuz the problem and stopped this program , but the problem still exist and try do factory rest and Hard reset ( press power on with volume up) still froze and much more and when froze , Hauwei welcome screen logo showed to try takeover frozing , and now show UI system stopped working ( show sometimes)
my device support Dual SIM , and Android V4.2.2
the grantee outside my resident country and there is a chance to test and try fix it without broke warranty for a month and then i will send back with my bro , anybody have any tool or method to fix that
i am damn frustrated and sad
thx
and now i try connect my device to my computer with USB and now go on and off continues as u see on this pic .... i think internal memory got problem (like there is bad blocks there)
{
"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"
}
help guys
i found this site do much support for this phone but in Russian ,
http://translate.google.com.eg/tran...da.ru/forum/index.php?showtopic=545804&anno=2
i take a look and try to re flash my stock rom , anybody have tried before + any one got the right instructions??!!
i got a site have firmwares for u30
http://www.huawei-file.com/index.php?dir=/Y_Series/Y320-U30
but i couldnt find my version y320-u30v100r001c328b906
thx
anybody know how to repair internal memory from bad sector??!!
i think i got bad sectors in my device
up
G’day Xda
As per a previous post of mine (https://forum.xda-developers.com/huawei-p20-lite/help/help-error-mode-boot-loop-access-to-t3831058) I am attempting to revive my P20 lite.
This has turned into a bit of personal project for me so with that I’ll point out I am not interested in paying for any proprietary software or hardware that seems readily available. I am only making use of open source software and putting together my own hardware where I can.
Is there anyone who is able to advise me where on the main board (Pics attached) I can find the Test Point and if possible knows where I can get hold of a copy of the Board software/firmware (apparently this is different to the normal phone software which is readily available???)
Any help/clues/advice would be greatly appreciated.
{
"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"
}
Sent from my iPhone using Tapatalk
It Is too late now I guess, but did you try to send the unopened phone to Huawei for a warranty replacement?
I am aware they don't replace phones that have been modded. But by the time you were receiving the upgrade system error I am sure there was no possible way to see if you caused the error or the phone did itself through some freak accident software bug.
do you still have phone with you?
mutahharbashir said:
do you still have phone with you?
Click to expand...
Click to collapse
Almost a full year later and yes i still have it. HaHa
Selfi kamera not working after new apdate 9.1 front camera is of plis help me tenk you
https://prnt.sc/q8x4u7
https://mega.nz/#!XRpmUQiZ!-KfnY2ycR_jRO64Qqgf_dyKMuje2QxKYwydlb-eQUp8
uhm... I think it worked? I booted into a rom and it says huawei ascend now... wtf is going on
i have a p20 lite stuck at bootloop. (shows Huawei logo with "powered by android" at bottom. no boot animation or loading animation.
can not enter recovery or download mode.
can not power off. Will test point method work for my p20 lite?
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?
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.