I started out rooting my phone and installed TWRP and Cyanogenmod. Everything was working fine. I play Pokemon GO and I noticed it did not work after an update because my device was rooted. So I had the dumb idea to unroot my phone. No big deal right? Wrong. So now my phone is no longer rooted. Next I attempted to put the stock firmware back on my phone so I got a few images and zips and attempted to install them. They kept failing but at some point I must have accidentally deleted the boot or something because now when I turn on my phone it immediately goes to a green screen with a red rectangle at the top and a blue rectangle at the bottom. It stays there for maybe a second and then goes to a screen that is black and at the top in blue letters it says "Boot image verify failed!" and under that in white text it says "Please update to the authorized images." After about a minute it changes to the Huawei eRecovery screen where it says EMUI at the center and says "Download latest version and recovery" but every time I try that it fails. I have attempted to research how to fix this online but every potential solution requires I have a rooted device or be able to actually access my phone but I don't have a rooted device and I have no way of using my phone. I am able to get to the Android fastboot and rescue screen but again, it doesn't seem like it matters since my phone is locked and everything I've seen thus far that involves unlocking or resolving my issue, requires I either have access to the phone or have an unlocked device. Any advice would be greatly appreciated. I hope you guys can help me.
P.S. I literally just now made my xda account to inquire about my situation. I apologize in advance if I am breaking any kind of policy or posting this in the wrong section or something.
bcnguyen said:
I started out rooting my phone and installed TWRP and Cyanogenmod. Everything was working fine. I play Pokemon GO and I noticed it did not work after an update because my device was rooted. So I had the dumb idea to unroot my phone. No big deal right? Wrong. So now my phone is no longer rooted. Next I attempted to put the stock firmware back on my phone so I got a few images and zips and attempted to install them. They kept failing but at some point I must have accidentally deleted the boot or something because now when I turn on my phone it immediately goes to a green screen with a red rectangle at the top and a blue rectangle at the bottom. It stays there for maybe a second and then goes to a screen that is black and at the top in blue letters it says "Boot image verify failed!" and under that in white text it says "Please update to the authorized images." After about a minute it changes to the Huawei eRecovery screen where it says EMUI at the center and says "Download latest version and recovery" but every time I try that it fails. I have attempted to research how to fix this online but every potential solution requires I have a rooted device or be able to actually access my phone but I don't have a rooted device and I have no way of using my phone. I am able to get to the Android fastboot and rescue screen but again, it doesn't seem like it matters since my phone is locked and everything I've seen thus far that involves unlocking or resolving my issue, requires I either have access to the phone or have an unlocked device. Any advice would be greatly appreciated. I hope you guys can help me.
P.S. I literally just now made my xda account to inquire about my situation. I apologize in advance if I am breaking any kind of policy or posting this in the wrong section or something.
Click to expand...
Click to collapse
You need device serial, IMEI and device id to get an unlock code from Huawei.
IMEI and serial, should be on the side of the box and for device id, you can go to
http://forum.xda-developers.com/honor-7/general/bricked-honor-7-honor-6-id-t3468333/page1
But better still, download the latest firmware for your phone, extract to get dload folder containing UPDATE.APP . Copy dload folder to the root of an SD card.
Insert it on your phone. Hold power+vol up+ vol down until the phone reboots. Let go of power but keep other two pressed for 5 sec more. Your device should start a forced update. If it does not work, unlock bootloader as mentioned above and flash images manually.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You need device serial, IMEI and device id to get an unlock code from Huawei.
IMEI and serial, should be on the side of the box and for device id, you can go to
http://forum.xda-developers.com/honor-7/general/bricked-honor-7-honor-6-id-t3468333/page1
But better still, download the latest firmware for your phone, extract to get dload folder containing UPDATE.APP . Copy dload folder to the root of an SD card.
Insert it on your phone. Hold power+vol up+ vol down until the phone reboots. Let go of power but keep other two pressed for 5 sec more. Your device should start a forced update. If it does not work, unlock bootloader as mentioned above and flash images manually.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
Exactly what muradulislam said, is a good method I had a similar issue about a month ago. Get the appropriate download for your firmware, extract the UPDATE.APP, place UPDATE.APP in the root of a fat32 formatted SD card and force the update as he described. You will be back at stock with the unlocked bootloader. From there you should be able to use ADB to flash TWRP and subsequently SuperSU binaries to your stock.
muradulislam said:
You need device serial, IMEI and device id to get an unlock code from Huawei.
IMEI and serial, should be on the side of the box and for device id, you can go to
http://forum.xda-developers.com/honor-7/general/bricked-honor-7-honor-6-id-t3468333/page1
But better still, download the latest firmware for your phone, extract to get dload folder containing UPDATE.APP . Copy dload folder to the root of an SD card.
Insert it on your phone. Hold power+vol up+ vol down until the phone reboots. Let go of power but keep other two pressed for 5 sec more. Your device should start a forced update. If it does not work, unlock bootloader as mentioned above and flash images manually.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
I have already attempted to get the unlock code from Huawei. I have done it before, that is how I unlocked in the first place. However, the unlock code I got before did not work to unlock it this time so like I said, I tried going through that process again. It was asking for Model Number and Product ID, both of which are obtained from having the phone on and using the dial pad, which again, I cannot do because I cannot get past the boot stuff I mentioned. I can try the other idea you mentioned, I really hope it works.
muradulislam said:
You need device serial, IMEI and device id to get an unlock code from Huawei.
IMEI and serial, should be on the side of the box and for device id, you can go to
http://forum.xda-developers.com/honor-7/general/bricked-honor-7-honor-6-id-t3468333/page1
But better still, download the latest firmware for your phone, extract to get dload folder containing UPDATE.APP . Copy dload folder to the root of an SD card.
Insert it on your phone. Hold power+vol up+ vol down until the phone reboots. Let go of power but keep other two pressed for 5 sec more. Your device should start a forced update. If it does not work, unlock bootloader as mentioned above and flash images manually.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
I also clicked on that link and attempted to download the hacker toolkit but it did not work. After downloading and attempting to open I get this error: "Windows cannot open the folder."
"The Compressed (zipped) Folder 'C:\Users\BCNgu\Downloads\Huawei Hacker Toolkit v1.4.zip' is invalid."
bcnguyen said:
I have already attempted to get the unlock code from Huawei. I have done it before, that is how I unlocked in the first place. However, the unlock code I got before did not work to unlock it this time so like I said, I tried going through that process again. It was asking for Model Number and Product ID, both of which are obtained from having the phone on and using the dial pad, which again, I cannot do because I cannot get past the boot stuff I mentioned. I can try the other idea you mentioned, I really hope it works.
Click to expand...
Click to collapse
please post a photo of the bootloader screen that says your bootloader is locked
and explain what you did to get it that way. unrooting the phone will not relock the bootloader
bcnguyen said:
I also clicked on that link and attempted to download the hacker toolkit but it did not work. After downloading and attempting to open I get this error: "Windows cannot open the folder."
"The Compressed (zipped) Folder 'C:\Users\BCNgu\Downloads\Huawei Hacker Toolkit v1.4.zip' is invalid."
Click to expand...
Click to collapse
I will upload the unzipped file then in the evening... Check back again please...
(Uploaded the unzipped installer)
Sent from my PLK-L01 using XDA Labs
bcnguyen said:
I also clicked on that link and attempted to download the hacker toolkit but it did not work. After downloading and attempting to open I get this error: "Windows cannot open the folder."
"The Compressed (zipped) Folder 'C:\Users\BCNgu\Downloads\Huawei Hacker Toolkit v1.4.zip' is invalid."
Click to expand...
Click to collapse
I just attempted to download and open it again and got the same exact message.
clsA said:
please post a photo of the bootloader screen that says your bootloader is locked
and explain what you did to get it that way. unrooting the phone will not relock the bootloader
Click to expand...
Click to collapse
I did explain in the initial post.
bcnguyen said:
I did explain in the initial post.
Click to expand...
Click to collapse
There are two files there, one is zipped and one unzipped... Both are not working for you?
I double checked them myself and another user did the same.
I can't say what's the problem when you download it...
Sent from my PLK-L01 using XDA Labs
muradulislam said:
You need device serial, IMEI and device id to get an unlock code from Huawei.
IMEI and serial, should be on the side of the box and for device id, you can go to
http://forum.xda-developers.com/honor-7/general/bricked-honor-7-honor-6-id-t3468333/page1
But better still, download the latest firmware for your phone, extract to get dload folder containing UPDATE.APP . Copy dload folder to the root of an SD card.
Insert it on your phone. Hold power+vol up+ vol down until the phone reboots. Let go of power but keep other two pressed for 5 sec more. Your device should start a forced update. If it does not work, unlock bootloader as mentioned above and flash images manually.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
your google drive file is corrupt, you can attach it to your post here on xda
---------- Post added at 05:52 AM ---------- Previous post was at 05:49 AM ----------
bcnguyen said:
I did explain in the initial post.
Click to expand...
Click to collapse
your OP never states that you relocked the bootloader
Please post the photo of your phone in the bootloader
and the command screen where you tried to reflash TWRP
muradulislam said:
You need device serial, IMEI and device id to get an unlock code from Huawei.
IMEI and serial, should be on the side of the box and for device id, you can go to
http://forum.xda-developers.com/honor-7/general/bricked-honor-7-honor-6-id-t3468333/page1
But better still, download the latest firmware for your phone, extract to get dload folder containing UPDATE.APP . Copy dload folder to the root of an SD card.
Insert it on your phone. Hold power+vol up+ vol down until the phone reboots. Let go of power but keep other two pressed for 5 sec more. Your device should start a forced update. If it does not work, unlock bootloader as mentioned above and flash images manually.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
I just tried the dload folder method you explained and it worked. Thank you so much.
bcnguyen said:
I just tried the dload folder method you explained and it worked. Thank you so much.
Click to expand...
Click to collapse
My pleasure. Enjoy...
Sent from my PLK-L01 using XDA Labs
Since it's solved, can someone change the title of this thread?!
PalakMi said:
Since it's solved, can someone change the title of this thread?!
Click to expand...
Click to collapse
Well I solved my initial issue but another thing is still happening. I can now get into my phone but I still get that green screen with the red and blue rectangles initially on bootup. I'm not sure how to get that to go away
muradulislam said:
My pleasure. Enjoy...
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
well I spoke too soon. I was able to get back to using my phone using your method but I still get that green screen with the red and blue rectangles on boot up. I'm not sure how to get that to go away. It stays on that for a few seconds then goes to the honor splash screen and boots as normal but it's irritating seeing that every time. On another note, I was thinking if I unlock it that would solve it but I went to the huawei site to unlock and went through the whole process and when it told me to use the 357946 code to obtain the product ID it did nothing for me except pull up a blank white screen.
That's weird
bcnguyen said:
well I spoke too soon. I was able to get back to using my phone using your method but I still get that green screen with the red and blue rectangles on boot up. I'm not sure how to get that to go away. It stays on that for a few seconds then goes to the honor splash screen and boots as normal but it's irritating seeing that every time. On another note, I was thinking if I unlock it that would solve it but I went to the huawei site to unlock and went through the whole process and when it told me to use the 357946 code to obtain the product ID it did nothing for me except pull up a blank white screen.
Click to expand...
Click to collapse
Any other instances of the red and blue rectangles except boot up?
Do you think that screen splash is because of all the tinkering or may be, (someone may be able to confirm) the boot animation file is corrupt?
Try searching a method to change your boot animation without root? If it still stays, at least we can rule out this possibility...
(I am just Troubleshooting so I may be wrong)
And as for Huawei unlock code, many users reported captcha bugs (captcha did not show up) but never this problem?
Give it a try or two more and then contact Huawei customer service via email to get the unlock code (specifying that the website did not work for you).
Sent from my PLK-L01 using XDA Labs
---------- Post added at 07:50 PM ---------- Previous post was at 07:45 PM ----------
bcnguyen said:
I also clicked on that link and attempted to download the hacker toolkit but it did not work. After downloading and attempting to open I get this error: "Windows cannot open the folder."
"The Compressed (zipped) Folder 'C:\Users\BCNgu\Downloads\Huawei Hacker Toolkit v1.4.zip' is invalid."
Click to expand...
Click to collapse
That hacker tool is now working, I uploaded the wrong file by mistake but corrected it in both my posts now.
Sent from my PLK-L01 using XDA Labs
muradulislam said:
Any other instances of the red and blue rectangles except boot up?
Do you think that screen splash is because of all the tinkering or may be, (someone may be able to confirm) the boot animation file is corrupt?
Try searching a method to change your boot animation without root? If it still stays, at least we can rule out this possibility...
(I am just Troubleshooting so I may be wrong)
And as for Huawei unlock code, many users reported captcha bugs (captcha did not show up) but never this problem?
Give it a try or two more and then contact Huawei customer service via email to get the unlock code (specifying that the website did not work for you).
Sent from my PLK-L01 using XDA Labs
---------- Post added at 07:50 PM ---------- Previous post was at 07:45 PM ----------
That hacker tool is now working, I uploaded the wrong file by mistake but corrected it in both my posts now.
Sent from my PLK-L01 using XDA Labs
Click to expand...
Click to collapse
The hacker tool worked this time but I did the whole process and got my unlock code and did the adb fast boot unlock oem thing and it said invalid unlock key (I'm thinking maybe because I already unlocked once before? I also attempted to get the key a few more times to see if it changed but it did not. Same unlock key every time. Also, no the only time I see the rectangles and the green screen is immediately upon boot. The splash screen is normal, I didnt mean to imply there was anything wrong with that. It's just the honor logo. I did research and nothing that I saw helped with getting rid of the rectangles and the green screen.
bcnguyen said:
The hacker tool worked this time but I did the whole process and got my unlock code and did the adb fast boot unlock oem thing and it said invalid unlock key (I'm thinking maybe because I already unlocked once before? I also attempted to get the key a few more times to see if it changed but it did not. Same unlock key every time. Also, no the only time I see the rectangles and the green screen is immediately upon boot. The splash screen is normal, I didnt mean to imply there was anything wrong with that. It's just the honor logo. I did research and nothing that I saw helped with getting rid of the rectangles and the green screen.
Click to expand...
Click to collapse
That's why I was trying to troubleshoot coz could not find anything about this problem online.
If its the first honor logo then I am not sure how to proceed.
Sent from my PLK-L01 using XDA Labs
Related
Hey peeps, i also have this cricket version and I am currently trying to get some of the secure checks off, and I came across an apk that is normally only available to chinese customers, I guess they have to allow bootloader unlocks, so I ran across this file and installed it it opens and seems to have allowed for custom boot image, which if correct is good news, however I flashed an unofficial recovery just to see how that went and still got the secure check error but only on recovery this time, which i also discovered if you get this error while testing a recovery don't fret you have a couple of options the easiest for me i found that once you get that message reboot into download mode by holding power/vol down/home button once it starts to boot release power while still holding the other buttons then when prompted press volume up to enter download mode from here you can reflash the original recovery orrrrr their seems to be a loophole in the secure check here that i have found to be handy. you can just hold power from here as if you will reboot while having the phone plugged up to usb power mine was on pc usb. As soon as phone vibrates let go of power you should now be at the charging screen wait til you get the grahpic of the battery actually charging now hold power again to reboot seems to work. Now below I will post link to the apk i used for bootloader unlock, I am interested to see if other peeps have success with the cricket version, so we can move on to cracking the remaining checks to get a custom recovery on this device. This CROM does for sure work on some S6 devices and it looks like it does on ours too, but for whatever reason i still get checks for recovery anyhow a more experienced dev if you have this device please take a look and see for yourself.
I also wanted to know if this would possibly work if I was to unpack the recovery.img from a custom recovery then repack and sign using the releasekey.x509.pem contained in /etc/security/otacerts.zip? Would it show up as authorized then perhaps? From download mode currently my readout is current binary: custom
current status: custom
Reacvtivation lock: OFF
Qualcomm secureboot: Enable (CSB)
Secure Download : Enabled
so i guess the apk is not working afterall, but maybe someone can decompile it like im about to do just to see if their is another method hidden within.
toxinburn said:
i found that once you get that message reboot into download mode by holding power/vol down/home button once it starts to boot release power while still holding the other buttons then when prompted press volume up to enter download mode from here you can reflash the original recovery orrrrr their seems to be a loophole in the secure check here that i have found to be handy. you can just hold power from here as if you will reboot while having the phone plugged up to usb power mine was on pc usb. As soon as phone vibrates let go of power you should now be at the charging screen wait til you get the grahpic of the battery actually charging now hold power again to reboot seems to work.
Click to expand...
Click to collapse
YES - now THAT is handy... THANK YOU... best bit of "fool the machine" that I've come across... very helpful - not sure how you stumbled upon it but great find... thanks again...
Stumbled I did indeed lmao dumb luck really. I do however see this as a potential security hole which should be explored by someone more knowledgeable than myself.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
toxinburn said:
Stumbled I did indeed lmao dumb luck really. I do however see this as a potential security hole which should be explored by someone more knowledgeable than myself.
Click to expand...
Click to collapse
that's funny, however->> potential security hole = potential exploit...
I'll take it if it's a "get in anyway I can" - could prove very useful... dummy up about it, as you have to be physically local to run it (if it is) an exploit - not something that can be implemented remotely, as far as I can tell...
why do you the think they call it ROOT - ing... savvy?...
this is a good thing for us on this side of the phone...
Ya you can also just pull battery. Plug in charger wait for charging graphics then turn on I think as well....also another tidbit I zeroed my sec partition and it did not brick...all is well I did this to see what happened when entering download more but nothing was different I had viewed it in a hex editor and it had in plain text stuff about download mode and security checks I thought it may be the download mode partition however it is not I'm not sure what purpose it served if nothing else you can gain a small bit of space by doing so.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
I'm trying to get all apks from variants that allowed oem unlock from settings/developer settings I think of we can trash our settings and replace with those we may be in business without having to hex edit the aboot and/or boot. I was lookin through some database files as well and I think something I read may be telling the byte that controls security checks not completely sure just yet but it sure seems that way...also I think if we could change the csc app to a diferent variants it could be needed. Not sure but just a few ideas.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
I too have the SM-530A with 5.1.1 and have been looking for about a month now for ways to unlock the bootloader and root. I am far from a developer and know some about rooting as I have done several HTC phones , which are considerably easier than Samsung. I found a forum called GSM, there I found some links to the stock firmware , stock kernel and other firmwares. They are also available for a cost at another site but can't remember. I do have them on file on my computer .There is another system that is supposed to root and unlock the bootloader called , Samsung Octoplus which is a small box connected to the PC and software used. Possibly there is someone on this forum that knows of that system and might have it . I have semi rooted with KingRoot .apk and flashed the stock kernel with flashify following some instructions from a contributor at the GSM forum, but failed to get a custom recovery on. I still get the same thing in download mode or odin mode of the fastboot stops working there and get "waiting on any devices".
Now can any one here add to this? Seems most any of the variants of the SM-530 can be unlocked and rooted except this one .
Well I do have full root on mine but bootloader is locked up the octoplus is for numerous uses for multiple devices it can revive bricked devices and unlock some etc. Not sure about its use for unlocking the bootloader though.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
toxinburn said:
Well I do have full root on mine but bootloader is locked up the octoplus is for numerous uses for multiple devices it can revive bricked devices and unlock some etc. Not sure about its use for unlocking the bootloader though.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
Click to expand...
Click to collapse
I guess though if you brick it in process of trying to unlock then at least you can recover it
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
toxinburn said:
Well I do have full root on mine but bootloader is locked up the octoplus is for numerous uses for multiple devices it can revive bricked devices and unlock some etc. Not sure about its use for unlocking the bootloader though.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
Click to expand...
Click to collapse
toxinburn, would you please explain the process for the custom recovery and what did you use? I tried all of the TWRP's and CWM's that I could find none would flash, and too the process for superSU , that I could not get my phone would not allow any of the above and give all kinds of errors but would never lock up.
I just followed the root guide in forums but as far as a custom recovery we can't use until we get the bootloader unlocked
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
I may end up getting a octoplus box just so I can safely experiment more because it looks like we will require a dirty method of unlocking which requires hex editing the factory images like aboot and boot.
Sent from my SAMSUNG-SM-G530AZ using Tapatalk
Any updates or progress?
Okay so how are you supposed to make this work just download the APK open it press ok and then go straight to download mode I'm not sure exactly what you're supposed to do after opening the APK you provided explain
I have successfully rooted, unlocked bootloader and flashed stock kernel using Odin.
How did u manage that can u share what was done...
tomrockafellow said:
I have successfully rooted, unlocked bootloader and flashed stock kernel using Odin.
Click to expand...
Click to collapse
Share with us what was done...
still no sign of unlocking the bootloader?
Any updates
i hard brick my phone yesterday. trying to flash bootloader with flashfire. (the lazy way) thats what i get. anyways could not turn on n6p, tried charging it for a couple of hours, try holding power button for 30 seconds, try power + volume . tried holding all buttons. nothing work.. read some threads saying its done. look for new phone or send to get repair. then i found tenfar thread. long story short. i used some of tenfar info and rwj5279955.. so big thanks to these two users
here is what i did to get my N6p to turn back on.. brick by bootloader.. this is my first how to .. bear with me. please.
you will need the following https://drive.google.com/file/d/0By19rrbnQfVUVFZEVUZqQzY1RWs/view?usp=sharing
Qualcomm drivers
QFIL software
3 files, patch0, prog_emmc_firehose, rawprogram0 .. for this to work
1. install qualcomm drivers, Connect phone to pc, open Device Manager. if you see under com port Qualcomm USB loader or something along those lines. your good, go to step 2. if not disconnect phone hold power button for 10 seconds, wait for 5 seconds connect phone to pc. check if in com ports you see Qualcomm drives. if you can not get qualcom drivers on com port. just stop. its not going to work..
2. extract the three files. in a folder somewhere easy to remember.
3. install the QFIL software, . once install run QFIL.
4. in QFIL software
if qualcomm driver are found it will say on top of QFIL software Qualcom USB loader 9008
Select Build Type: click Meta Build
Select Build :: patch0 ... if for some reason patch0 doesnt work try rawprogram0
Select Programmer:: pro_emmc_firehose
hit download ...if the blue bar get to half way mark your golden. its going to always fail. the trick is to get the blue bar at least half ways. then you disconnect phone, hold power button, it should turn on.. then you ADB what ever you need to do.
for those that get the fail right away.. while phone connected to pc, hold power button until drivers disappear from device manager.. then disconnect phone, wait for 5 seconds, hold power button, for 10 second,.. wait for 5 seconds .. then connect phone back to pc, wait for device manager to see drivers.. then hit the download button . do this part over and over again ..until it works..
sorry for this horrible guide.. it work for me.. hope it works for you..
That's a lot to take in! Is this for windows only then not Linux? Bootloader and radio does have to be flashed via fastboot
DEVILOPS 007 said:
That's a lot to take in! Is this for windows only then not Linux? Bootloader and radio does have to be flashed via fastboot
Click to expand...
Click to collapse
Windows
Lw00d said:
Windows
Click to expand...
Click to collapse
Luckily there's already alternative for linux
Hello thank you so much for your guide, currently trying to unbrick my nexus 6P stuck in 9008 port, could you provide a link for your version of Qfil please? as I'm struggling to find your 2.0.0.2 version I either get 1.0.0 or 2.0.0.3 and they're not working
Update: I've found the version! However when I quick Meta build and attempt to locate XML there's nothing I can select? sorry if this is really simple just never done before thank you
Clarkeofcurtis said:
Hello thank you so much for your guide, currently trying to unbrick my nexus 6P stuck in 9008 port, could you provide a link for your version of Qfil please? as I'm struggling to find your 2.0.0.2 version I either get 1.0.0 or 2.0.0.3 and they're not working
Update: I've found the version! However when I quick Meta build and attempt to locate XML there's nothing I can select? sorry if this is really simple just never done before thank you
Click to expand...
Click to collapse
place the files in a folder.
then in QFIL brows to the folder
need to select build path first.
What type of brick does this fix? Is this for the big one " boot loop of death" that's been well covered?
I ask out of curiosity. My phone's unaffected (knock wood)
KLit75 said:
What type of brick does this fix? Is this for the big one " boot loop of death" that's been well covered?
I ask out of curiosity. My phone's unaffected (knock wood)
Click to expand...
Click to collapse
hard brick. phone does not turn on at all
Lw00d said:
place the files in a folder.
then in QFIL brows to the folder
need to select build path first.
Click to expand...
Click to collapse
I have done as stated, however when attempting to select build after clicking META BUILD, I have to change the browsing options to ALL FILES from META BUILD CONFIGURATIONS otherwise I can't find anything?
Once selected Patch0, I proceed to select programmer path, but then my download content isn't clickable please?
Select build type click flat build. See if u could click on download
Lw00d said:
Select build type click flat build. See if u could click on download
Click to expand...
Click to collapse
I can start it VIA flat build, however I get this error
Now try with meta build
Lw00d said:
Now try with meta build
Click to expand...
Click to collapse
When trying with meta build this is the problem I'm faced with.
Can't select anything, am i using wrong version of Qfil perhaps or isn't that an issue as it's the newst?
I click load content and I can't view the files I'm supposed to be selecting
Clarkeofcurtis said:
When trying with meta build this is the problem I'm faced with.
Can't select anything, am i using wrong version of Qfil perhaps or isn't that an issue as it's the newst?
I click load content and I can't view the files I'm supposed to be selecting
Click to expand...
Click to collapse
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Lw00d said:
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Click to expand...
Click to collapse
Thank you for your help and replies, no blue bar when I click download on flat build, just gives me that port error about it taking 10 seconds to open when it should only be 3? I'll try it on your version and let you know bare with me
---------- Post added at 07:44 AM ---------- Previous post was at 07:32 AM ----------
Lw00d said:
That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?
Click to expand...
Click to collapse
Could you send me a link to your version please?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Clarkeofcurtis said:
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Thank you for your help and replies, no blue bar when I click download on flat build, just gives me that port error about it taking 10 seconds to open when it should only be 3? I'll try it on your version and let you know bare with me
---------- Post added at 07:44 AM ---------- Previous post was at 07:32 AM ----------
Could you send me a link to your version please?
Sorry, I've found it again. But this time - different error... :/ Any ideas?
Click to expand...
Click to collapse
It's on first post
Lw00d said:
It's on first post
Click to expand...
Click to collapse
Getting this
Clarkeofcurtis said:
Getting this
Click to expand...
Click to collapse
did you do this..
for those that get the fail right away.. while phone connected to pc, hold power button until drivers disappear from device manager.. then disconnect phone, wait for 5 seconds, hold power button, for 10 second,.. wait for 5 seconds .. then connect phone back to pc, wait for device manager to see drivers.. then hit the download button . do this part over and over again ..until it works..
also try extracting all these files into the folder you made .. this includes the three files .. https://drive.google.com/open?id=0By19rrbnQfVUbFZSc3A3VXhGRzQ
Thank you so much! I messed up my 6P when I tried to flash a bootloader image via Flashfire. I hadn't been in a brick this bas since the good old days of Gingerbread and ROM Manager! For anyone else having similar issues, I got my dead 6P to be recognized as QHSUSB_bulk eventually in Windows 7. I then edited the rawprogram0.xml file (from OP's link) in a text editor. I removed the entries for all the other partitions I didn't want to overwrite (like system and vendor and userdata), leaving only the sbl1 (secondary bootloader, the part of the firmware that actually boots into the system/recovery/bootloader when the device is first powered on) partition entry - because that's what Flashfire said it had flashed the entire bootloader image to. Doing a bit of research, I found that our bootloader image is actually just many different small partitions all grouped together into a single image file. I couldn't figure out how to unpack the bootloader image, so I downloaded a full firmware OTA zip from Google, and lo and behold, there was a "bootloader.sbl1.img" (along with other small partitions) file in the OTA zip. I changed the sbl1.img entry in the rawprogram0.xml file so that it correlated with the filename "bootloader.sbl1.img", I moved the image file into the same folder as the rawprogram0.xml, and then I was able to restore my device to it's previous functionality using the "flat build" download configuration in QFil, though the whole process did take me like 3 hours. Lesson learned - screw using Flashfire for bootloader images.
ERROR: Could not access "C:\temp\vendor.img" with access mode 'rb'
When I'm finally lucky, rebooting, replugging the phone, it looks like it might flash...
...then I see this.
I've given all permissions to all users for full control, on the file, I've run time program as administrator, I don't know what else to do. If it can't open the file, I can't flash my phone. I'm not a Windows administrator so I don't really know what to do to get this to work and I can't find any hints on the forums.
Steps:
1. Turn Off Any Virus Protection Software
2. Download MP26010j_00_0316.kdz To Flash Your Phone Back To Stock
3. Install LGMobileDriver_WHQL_Ver_4.2.0.exe
4. Next Install LGUP_Store_Frame_Ver_1_14_3.msi
5. Make Sure That You Have Your Phone Connected (Take Battery Out Then Put It Back In Hold Volume Up And Connect With Micro USB) So LGUP Can Be Able To Recognize It
6. Then Double Click UPPERCUT.exe to open up LGUP Now But Only Thing Is That Uppercut will try to verify just ignore and if it doesn't open up just open lgup from desktop and its going to view phone as unknown
7. Unplug Phone But Keep LG Download Mode On And Exit LGUP
8. Open LGUP First And Then Connect Phone Which Should Recognize Phone As MP260
9. Click Upgrade, Make Sure That Bin Is Checked And Select File MP26010j_00_0316.kdz To Flash And Click Start
10. Your Done! Video Coming Soon
Links: https://mega.nz/#!EZcURRSD!NF_5MU4dJUpTknRcPMQWFVoYo4ePsGkoA0ndkkzVsmI https://mega.nz/#!dFNWFZZa!Rl3P7tJs7J51TtjcnaLwR3RHgGdRSco8NcJ9yog86J0 https://mega.nz/#!oVNSnYTB!3y9-P4t_8P-lj5sCXhFjO0R8J3j4Z_US-XCjVGysgEI https://mega.nz/#!pAUgGAwC!j5d3C8pUdQR5XMpqWBgLDu2O3tE99yWNa2nwXud3OSo
The Only Thing Im Disappointed Is That Every Time You Reboot Phone or Turn It On It Keeps Saying Lock Bootloader But Just Press The Power Button To Continue Repeating The Process Does Not Remove That Message
I Made This Tutorial For Some People That Have Trouble With Apps That Detect Root
Phone dont turn on at all
yesterday i rooted my k20 mp260 then this morning i wanted to revert back to stock and no root, i tried to unroot it but i didnt follow this cause i didnt find it til now,but i got rid of root and then i tried to update via ota and it went into twrp and then it was installing until it just went black, like it shut off now it doesnt power on. when i plug it in to pc it finds it but it cant install the driver. any help to try to Resurrect from the grave would be great
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
fyi u can get rid of the bootloader bootup annoyance by following the unlock bootloader instructions but instead of typing fastboot oem unlock type fastboot oem lock
shaneg79 said:
fyi u can get rid of the bootloader bootup annoyance by following the unlock bootloader instructions but instead of typing fastboot oem unlock type fastboot oem lock
Click to expand...
Click to collapse
If you lock the bootloader if you have custom recovery (twrp) and superuser you will not be able to boot
New Optimus said:
If you lock the bootloader if you have custom recovery (twrp) and superuser you will not be able to boot
Click to expand...
Click to collapse
Correct but this thread was about removing root
shaneg79 said:
Correct but this thread was about removing root
Click to expand...
Click to collapse
ah, I thought that was in the original post or implied if completely unrooting.
New Optimus said:
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
Click to expand...
Click to collapse
Any link for the T-mobile variant?
I looked all over and reached the end of internet but couldn't find , lol!
meazz1 said:
Any link for the T-mobile variant?
I looked all over and reached the end of internet but couldn't find , lol!
Click to expand...
Click to collapse
Here
kc6wke said:
Here
Click to expand...
Click to collapse
Thanks
meazz1 said:
Thanks
Click to expand...
Click to collapse
Looked and saw two links for the newest kdz. I'm in the USA so TMO =north america.
But I 'm curios what TMI stands for, no info on that page of region listings.
meazz1 said:
Looked and saw two links for the newest kdz. I'm in the USA so TMO =north america.
But I 'm curios what TMI stands for, no info on that page of region listings.
Click to expand...
Click to collapse
Not sure about TMI, use TMO North America
I figured I'd post this here to, because I am thinking about getting this phone. It's $99 at metro pcs right now, that's really hard to pass up.
In a twrp+root thread there are some that cannot get root, with the last LG firmware update, so I'm guessing this is a soft brick as apposed to a hard brick.
So, had a question.
If in the case of the like 10% of the people that do this root, the phone won't root or bricks, if I get this phone and and that happens, is it possible to flash the phone via the LG program, with a KDZ file and go back to stock like in this thread? If so I will probably buy this phone tomorrow (crosses fingers the kdz trick will work)
From looking at the videos, it looks as if the LG program is similar to the Samsung Odin program as far as flashing goes, am I correct in this?
...
Sent from my [device_name] using XDA-Developers Legacy app
I know this thread has not been active for a while. However I have a Metro LG K20 Plus phone and want to change the firmware to T-Mobile. I have not been successful doing this as I always get invalid firmware, because LG UP recognizes the phone as a metro phone. Is there a way to succeed in getting the T-Mobile firmware on the phone?
thanks in advance.
Stoner101 said:
yesterday i rooted my k20 mp260 then this morning i wanted to revert back to stock and no root, i tried to unroot it but i didnt follow this cause i didnt find it til now,but i got rid of root and then i tried to update via ota and it went into twrp and then it was installing until it just went black, like it shut off now it doesnt power on. when i plug it in to pc it finds it but it cant install the driver. any help to try to Resurrect from the grave would be great
Click to expand...
Click to collapse
Did you find any answers to this? I have one that is bricked. It will not show up when connected to a computer at all
Virus warning from Avira in Uppercut
lg k20 plus soft bricked?
So I've searched high and low and have tried suggestion after suggestion with no avail. To start things off, I have a soft bricked LG k20 plus. Everything was working fine until the other day when I went to flash a kernel, and when the phone restarted, the screen was a dark grey/black color. I rooted the devices using massis method, removed SU and then rooted using Magisk. Like I said everything was working fine and for whatever reason I decided to try a different kernel. That's when it all went downhill. So now when I turn the phone on, the screen is still blank but it vibrates. When I've connected it to a computer, on my Mac it doesn't show up with ADB or FASTBOOT but in my device tree it comes up as LGE Android device. I borrowed my friends laptop since it runs windows, and my Mac is a dinosaur. ADB doesn't pick it up either, but in a USB hub it says the same thing, LGE Android device and lower down it comes up as TP-LINK. Now tryin to use LG Flash tools doesn't work, LGUP doesn't see my device, and when I tried to extract the KZD file, when I go to select it from the list there is no file to choose. Since I can't see anything on my screen, I can't tell if I'm in download mode, bootloader, etc, but in my device tree sometimes my phone will pop up an bootloader interface and I can use fastboot commands. When I was last able to see my screen, yes, USB debugging was on, I had a recovery, but since I can't see anything on my screen I can't seem to boot into recovery. If I could I would wipe cache and all. I think I may have read too many article and suggestions as to what to do because nothing seems to be working, and don't seem to find anything else related closely enough to my issue. Anyone have a clue as to where I should start? I'll have to give my friend back her laptop soon, and since my mac is so old, and the whole PC vs Mac feud, my computer won't be of much help. Any advice my hair strands would greatly appreciate before they rest are pulled out lol
Hello.
I was trying to install a treble rom on my p20 lite and suddenly after flashing i needed to flash stock recovery to make the stock wipes.
I did.
The rom started but with no keyboard. I couldnt pass google part to get to the rom menu.
Ok.
I decided to flash it again.
I did. But this time, the rom never started and i was with stock erecovery, so couldnt flash again.
I went to flash twrp but FRP is LOCKed. Bootloader unlocked, obviously. And bc of that i cant flash ANYTHING.
Tried to flash system, twrp, anything. I cant. Says FRP lock.
Tried to lock bootloader and relock again: I cant. It says it needs to unlock FRP before.
Tried DC PHOENIX, didn't work on my p20.
Scrolled all google and xda for help, nothing.
Tried erecovery stock rom installation. It downloads the files but never installs, i've spent 5 hours waiting for it to go off the 0%. Nothing happens.
Already made erecovery wipe data/cache. Nothing.
Can someone please help me?
Hi there
Can you tell what's your build number if you already knew before this happened?
Also, right now your only hope is your Stock Recovery so let's focus on that:
Please try to download and install the official ROM via the eRecovery a couple of times and connect it to the best Wifi you have.
Do you have bootloader "unlocked" or "locked" right now?
FRP is locked so no changes possible yup.
If you have your bootloader "locked" not "relocked" you have warranty and you can send it to a customer repair center and they can solve it for you.
With the methods we know it's pretty much impossible, altough try this via fastboot command line:
fastboot erase config
then
fastboot reboot
If this does not do it then try with DC-Unlocker software via this link https://www.dc-unlocker.com/huawei-android-phone-frp-unlock
Sorry for insisting,
Best of hopes,
AS
ars_chelsea said:
Hi there
Can you tell what's your build number if you already knew before this happened?
Also, right now your only hope is your Stock Recovery so let's focus on that:
Please try to download and install the official ROM via the eRecovery a couple of times and connect it to the best Wifi you have.
Do you have bootloader "unlocked" or "locked" right now?
FRP is locked so no changes possible yup.
If you have your bootloader "locked" not "relocked" you have warranty and you can send it to a customer repair center and they can solve it for you.
With the methods we know it's pretty much impossible, altough try this via fastboot command line:
fastboot erase config
then
fastboot reboot
If this does not do it then try with DC-Unlocker software via this link https://www.dc-unlocker.com/huawei-android-phone-frp-unlock
Sorry for insisting,
Best of hopes,
AS
Click to expand...
Click to collapse
Hey, thanks for the answer.
My build number (ane-lx3 c605 b149)
I tried for like 10 times already to install the firmware from erecovery but it refuses to leave the 0% when installing... Ive waited more than 5 hours already.
When trying these fastboot command lines, i got this: https://imgur.com/a/hrSB8iK
Dc also didnt worked for me, i think it doesnt support my phone model?
Bc i can't find it in the list of phone model in the software also tried with similar and doesnt work.
My bootloader is unlocked, i guess warranty wont solve my problem bc of that :crying:
Thanks again for tryna help!
you need sd card
download this file: https://androidhost.ru/cBe
unzip this file, inside software folder are dload folder, coppy that to sd card
put sd card in phone
pres vol+ and vol- and power button (need atlest 50% batery)
give a try.
Arnys said:
you need sd card
download this file: https://androidhost.ru/cBe
unzip this file, inside software folder are dload folder, coppy that to sd card
put sd card in phone
pres vol+ and vol- and power button (need atlest 50% batery)
give a try.
Click to expand...
Click to collapse
He/She does need a micro sd card adapter for that to connect to the pc or use it on another phone and then copy the files.
Yeah I forgot about that I guess XD
Cheers,
AS
ars_chelsea said:
He/She does need a micro sd card adapter for that to connect to the pc or use it on another phone and then copy the files.
Yeah I forgot about that I guess XD
Cheers,
AS
Click to expand...
Click to collapse
Arnys said:
you need sd card
download this file: https://androidhost.ru/cBe
unzip this file, inside software folder are dload folder, coppy that to sd card
put sd card in phone
pres vol+ and vol- and power button (need atlest 50% batery)
give a try.
Click to expand...
Click to collapse
Thank you, guys.
I tried this method just now but after a time with EMUI logo in the screen it said software install failed!
I guess im really lost. :crying:
fcknumb said:
Thank you, guys.
I tried this method just now but after a time with EMUI logo in the screen it said software install failed!
I guess im really lost. :crying:
Click to expand...
Click to collapse
Hey
Did you try the official guide of @Merlin_99?
If not check his thread here: https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
That's the official way to do it
Cheers,
AS
ars_chelsea said:
Hey
Did you try the official guide of @Merlin_99?
If not check his thread here: https://forum.xda-developers.com/huawei-p20-lite/how-to/root-how-to-install-update-t3841557
That's the official way to do it
Cheers,
AS
Click to expand...
Click to collapse
Thanks for your reply and still tryna help me.
As i see, the only thing i didnt do from the official guide is this part:
"Finally, enter to the project menu from dialer typing *#*#2846579#*#* ==> Software Upgrade ==> SdCard Upgrade."
That i cant do cause my phone is systemless and i cant turn it on to use dialer :crying:
fcknumb said:
Thanks for your reply and still tryna help me.
As i see, the only thing i didnt do from the official guide is this part:
"Finally, enter to the project menu from dialer typing *#*#2846579#*#* ==> Software Upgrade ==> SdCard Upgrade."
That i cant do cause my phone is systemless and i cant turn it on to use dialer :crying:
Click to expand...
Click to collapse
Okay then.
It should work though did you put the dload folder into the root your sd card and then power on button + Volume buttons at the same time while powering on?
Cheers,
AS
ars_chelsea said:
Okay then.
It should work though did you put the dload folder into the root your sd card and then power on button + Volume buttons at the same time while powering on?
Cheers,
AS
Click to expand...
Click to collapse
Right bae, its like that into my sdcard: 1. http://prntscr.com/lx74xt 2. http://prntscr.com/lx7im7
And yes, i did pressed power and + - volume buttons at same time!
Thank you for not giving up.
fcknumb said:
Right bae, its like that into my sdcard: 1. http://prntscr.com/lx74xt 2. http://prntscr.com/lx7im7
And yes, i did pressed power and + - volume buttons at same time!
Thank you for not giving up.
Click to expand...
Click to collapse
Hi again
This is really weird... This one should work... Did you download the right version of your build? example: 8.0.0.162(C432)
And try to find the latest version of your build and via your model example: ANE-LX1 which is on the back of the phone with small letters or on the box
Cheers,
AS
ars_chelsea said:
Hi again
This is really weird... This one should work... Did you download the right version of your build? example: 8.0.0.162(C432)
And try to find the latest version of your build and via your model example: ANE-LX1 which is on the back of the phone with small letters or on the box
Cheers,
AS
Click to expand...
Click to collapse
Yeah, i did it all right.
So sad...
fcknumb said:
Yeah, i did it all right.
So sad...
Click to expand...
Click to collapse
Remote instructions are not the best for these problems, so try to get a person on your country which knows some stuff and can help you out there
Hi All. I'm afraid my Honor 10 is permanently dead but I'm looking for a solution to "exhume" it.
I had latest firmware installed, 9.0.0.219 (C636), but after I installed it, I observed some ghost touches and application lags so I wanted to install the Pixel Experience custom rom. To install this rom it needs not to be on Emui 9, so I used beta-downy_04 to rollback to latest oreo 8.1 fimware (COL-L29C636B153 8.1.0.153). All good until an error appears while flashing the firmware, "Software fimware failed"..Then a message appeared that suggested me to reboot or select eRecovery. I chose eRecovery but nothing. It won't to turn on. I tried to force reboot with Vol-Up and powe for more than 30 seconds, no responses. I tried to use Multi-tool because if I connect Honor 10 to pc it is recognised as fastboot device, so I tried to unbrick it flashing system, cust, kernel and recovery_ramdisk images, but nothing. So Am I finished? Can someone help me? Thanks :crying:
Sorry to hear that man. I noticed that after .219 update HiSuite doesn't get rollback firmwares from HiCloud anymore. Is that the reason why you tried the method above?
I tested rollback request with .212 in HiSuite and it successfully sent me the rollback data which is 219870 ID (not 206629 or 186881). Since Huawei device names change it's kinda tricky to force stuff into the phone.
{"status":"0","versionPackageCheckResults":[{"status":"0","autoPollingCycle":"1","components":[{"componentID":1,"createTime":"2019-04-25T07:08:45+0000","description":"219 - 153 fullback","name":"COL-L29 8.1.0.153(C636)","pointVersion":"1","reserveUrl":"updatessl.dbankcdn.com","ruleAttr":"","url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G3015/g1642/v219870/f1/","version":"COL-L29 8.1.0.153(C636)","versionID":"219870"}],"versionPackageType":1,"checkEnd":"1"}]}
If you didn't try the id 219870, can you try to flash it?
MagnoT said:
Sorry to hear that man. I noticed that after .219 update HiSuite doesn't get rollback firmwares from HiCloud anymore. Is that the reason why you tried the method above?
I tested rollback request with .212 in HiSuite and it successfully sent me the rollback data which is 219870 ID (not 206629 or 186881). Since Huawei device names change it's kinda tricky to force stuff into the phone.
{"status":"0","versionPackageCheckResults":[{"status":"0","autoPollingCycle":"1","components":[{"componentID":1,"createTime":"2019-04-25T07:08:45+0000","description":"219 - 153 fullback","name":"COL-L29 8.1.0.153(C636)","pointVersion":"1","reserveUrl":"updatessl.dbankcdn.com","ruleAttr":"","url":"http://update.dbankcdn.com/TDS/data/files/p3/s15/G3015/g1642/v219870/f1/","version":"COL-L29 8.1.0.153(C636)","versionID":"219870"}],"versionPackageType":1,"checkEnd":"1"}]}
If you didn't try the id 219870, can you try to flash it?
Click to expand...
Click to collapse
Hi. Thanks for your answer. Yes, I tried to rollback with beta-downy program because I wanted to flash a custom rom and I needed android 8.1 to do that.
Unfortunately I flashed a firmware COL-L29 8.1.0.153(C636) with ID 186881 because it has three files and beta-downy program works only if update.zip, update_all_hw.zip and update_data_public.zip files are present in ZIP-HERE folder and firmware with ID 219870 has only two files...
At this moment Honor 10 is fully dead. I can't access to bootloader mode but if I connect it to pc and I use adb, I seem to be able to use fastboot but I don't know if It really flashed something. So I can only use fastboot ( and I flashed all needed files of latest firmware installed, version .219) but it is useless at this time because Honor 10 appears dead, it won't charge. Sometimes seven red blinding appear when I try to force reboot pressing and holding power on and Vol-up buttons.... I tried to remove battery also, then to plugin the charge and holding power button for 30 seconds and then to insert the battery again but nothing. No charge and no power on... I have no idea what I must to do...
Someone alive???
Why you can't access bootloader?
Did you try to plug in charger while pressing vol down button?
empedocle86 said:
Hi All. I'm afraid my Honor 10 is permanently dead but I'm looking for a solution to "exhume" it.
I had latest firmware installed, 9.0.0.219 (C636), but after I installed it, I observed some ghost touches and application lags so I wanted to install the Pixel Experience custom rom. To install this rom it needs not to be on Emui 9, so I used beta-downy_04 to rollback to latest oreo 8.1 fimware (COL-L29C636B153 8.1.0.153). All good until an error appears while flashing the firmware, "Software fimware failed"..Then a message appeared that suggested me to reboot or select eRecovery. I chose eRecovery but nothing. It won't to turn on. I tried to force reboot with Vol-Up and powe for more than 30 seconds, no responses. I tried to use Multi-tool because if I connect Honor 10 to pc it is recognised as fastboot device, so I tried to unbrick it flashing system, cust, kernel and recovery_ramdisk images, but nothing. So Am I finished? Can someone help me? Thanks :crying:
Click to expand...
Click to collapse
Same happened to me so i bought new phone, luuckly i bought phone that broke with "found" money. Go to nearest repair center and say you left phone plugged overnight to update, tomorrow you came and it was dead. They will repair it for free if it had guarantee.
bestenderowner said:
Same happened to me so i bought new phone, luuckly i bought phone that broke with "found" money. Go to nearest repair center and say you left phone plugged overnight to update, tomorrow you came and it was dead. They will repair it for free if it had guarantee.
Click to expand...
Click to collapse
Same problem here...but i don't know if DC-Unlocker is compatible with this device. My concern is pay for service and not works. My device is in testpoint mode, but i can't find flash tool and board firmware for this version (COL-L29), variant C636 (spcseas) and bootloader lock for more help...
I appreciated any helps....
Thanks a lot
For all of you if you are willing to open back panel of your phone I can help you.
miststudent2011 said:
For all of you if you are willing to open back panel of your phone I can help you.
Click to expand...
Click to collapse
Panel back open....and now??
darks0ldier said:
Panel back open....and now??
Click to expand...
Click to collapse
There is a method known as test point method where you short two ports and flash service firmware. And later you flash full firmware.
Search Huawei p20 forums for details. Try to find them and share the links you got then I will guide you what next.
darks0ldier said:
Same problem here...but i don't know if DC-Unlocker is compatible with this device. My concern is pay for service and not works. My device is in testpoint mode, but i can't find flash tool and board firmware for this version (COL-L29), variant C636 (spcseas) and bootloader lock for more help...
I appreciated any helps....
Thanks a lot
Click to expand...
Click to collapse
I bought Chinese ****, i tried everything, i paid 30 bucks for code from one asshole, than i thought i hardbricked my device, i went to service, they said the motherboard was burnt, i lied that i left device update overnight xD, because bricking voids warranty. They said they dont support chineese guarante because we are Eu, so i sent my **** back to bang**** banggood. Com scammers. Than year i waited and they sent me refund 100 dolars, i paid 450 bucks, luckly i bought it with my grampa credit card so lol i got 100 bucks free xD ans i bought iFix it kit. So i recommend you to buy unlock code, and if you know what you are doing, you can successfully rebrand it, il send you one link, that helped me a lot. But it was t9o late, and i was stupid. I was curious and i flashed my phone with upgrade file, i didnt flash it with full ota., so basically idfk what did i do xD. So i probably wiped end to end and it removed power supply unit settings and full power from battery destroyed my cpu. Sooooo good luck and find something cheap or just try to get free code from funky huawei, they can help you rebrand, better pay 50bucks than loose 400 bucks
---------- Post added at 07:52 PM ---------- Previous post was at 07:49 PM ----------
darks0ldier said:
Same problem here...but i don't know if DC-Unlocker is compatible with this device. My concern is pay for service and not works. My device is in testpoint mode, but i can't find flash tool and board firmware for this version (COL-L29), variant C636 (spcseas) and bootloader lock for more help...
I appreciated any helps....
Thanks a lot
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-10/how-to/successfully-rebranding-chinese-col-t3823782
And i just noticed your device is dead. Okay idk are u familiar with those processes.
Extract boot.img file from firmware, (firmware extractor) by huawei. Than open adb, and do flash boot boot. Img, flash recovery recovery.img and thst