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
Related
Hello,
I just jumped on a good deal for Xperia Z5 (E5823) with software issue. Device boots up to the Xperia logo screen and hags there. I am preparing myself for flashing but hoping a simple hard reset might solve the problem. What should my steps be? I already downloaded Flashtool and did some reading on the forum to get myself familiar with the process. Looks like I will need to download FTF file (I am in US, prefer to have unbranded with minimal carrier bloat) and can use your advice on which version/file to start with. Ideally I would want to root as well, but for now more concerned about restoring back to stock. I did read that Lollipop has a better performance, but open to suggestions for whatever is easier/stable. Any guidance/advice is appreciated (with links to tools or downloads if avail). Is there a way to tell what version # along with region/customization I have installed now?! Should I try the Sony Companion software?
For the record, I have successfully flashed custom ROMS on various Samsung/LG devices, as well as Nexus 4/5. Therefore, feel pretty confident this should not be impossible or any harder. Thanks A LOT.
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
coolmen777 said:
An update after spending few hours yesterday. PC Companion doesn't recognize the phone when attempting to repair (Vol down + insert USB). It did install few drivers when connected to PC, and it looks like the phone does go into flashmode (as indicated by LED staying green). Then tried the Flashtool, created FTF file (based on tutorial at XperiaBlog) and again the same thing, can't get the phone to be recognized in flashmode. It does respond in fastboot mode and able to get some identifying information. I couldn't find any information on how to flash system, kernel, etc through fastboot (was hoping to use the Flashtool FastBoot mode option, but picking corresponding SIN files resulted is fail errors). I am afraid that flashmode might not work for me as the phone might not have USB debugging enabled (not sure what was done to it and who had it prior).
Are the other alternatives/methods I should try? I wish there was a way to send flash commands from ADB command prompt (like with Nexus phones) and from fastboot mode. Any ideas? Really love the phone, though and want to get it repaired to replace my huge LG! Thanks everyone.
Click to expand...
Click to collapse
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
I gladly would, except that I am not very comfortable using it due to lack of experience and available zips for my Z5 compact. Can you point me to that info and how to make zips to flash and what to start with? I am willing to try it.
Also, how can I check if my boot loader is unlocked? Can't seemed to find a command to use. Thanks again.
Any pointers for zips or how to flash a rom through fastboot? Thanks.
coolmen777 said:
Any pointers for zips or how to flash a rom through fastboot? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
civicsr2cool said:
Why couldn't you use adb? I use it to flash the recovery every once in a while, I hate flash tool. It took me a good 4 different PCs before I found one it would work on
Click to expand...
Click to collapse
civicsr2cool said:
http://forum.xda-developers.com/showthread.php?t=2277112
We have a couple aosp Roms available to flash, I'd try cm13. I don't know if you've tried to unlock your bootloader yet or not but you should try that. You could also try flashing zombie kernal and see if that'd boot up.
Click to expand...
Click to collapse
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
coolmen777 said:
Thanks for the reply and guidance. I would prefer to stick with Stock Xperia software and launcher. From my experience, CM tends to be buggy and I need full stable functionality with max battery (hoping to give Stamina a test). I am not sure if the bootloader is unlocked and don't want to mess with it unless I absolutely have to (does unlocking BL still messes with DRM keys for camera processing?) Wish I could see if it is unlocked somehow, maybe someone tried to flash/root it and messed up the bootloader somehow.
I will look at zombie kernel (does it need unlocked bootloader or recovery to flash, will it work with stock ROM?) Thanks again for your help.
Click to expand...
Click to collapse
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
civicsr2cool said:
I'm only trying to suggest things that could get the phone working again not permanent solutions lol I don't run cm13 yet as it's definitely not refined. Flashing a stock ftf should be able to bring you to complete original specs without unlocking bootloader or anything.
Click to expand...
Click to collapse
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
coolmen777 said:
Lol, I understand now. It looks like the bootloader might still be locked as I am unable to flash zombie kernel (command: "fastboot flash boot boot.img" results in sending OK, but Failed: remote command not allowed). Looks like I am stuck to trying to unlock a bootloader to keep trying to revive the phone. Just bothers me that I can't get into Flashmode (even after installing drivers that come with Flashtool). Could this be because the phone might not have USB debugging enabled? Is there a way to try to flash the stock through fastboot (as zip) instead of ftf?
My big concern is loosing TA partition and associated DRM keys (any way to back it up from fastboot or toolkit?). Or is that not a factor with the hack available now? Sorry for all these questions, just getting more and more frustrated with this.
Click to expand...
Click to collapse
Come to think of it without getting into the phone to enable unlocking the bootloader I don't think you would even be able to do that. Even if the drivers weren't installed the phone should go into flash mode. I had a hard time with my first attempt with flash tool at getting into flash mode. If you hold power and volume up you should be able to power down the phone completely then hold volume up while plugging in. The problem I had was my PC has a few different USB ports and I was using one that was meant for charging and it wouldn't go into flash mode, tried a different port and it went well after that.
Failed: remote command not allowed ???
This error is because you have not enabled OEM Unlocking from the Developer Option.
If you have enabled it but still receiving the error then you have not unlocked bootloader properly.
There is no need to unlock bootloader for flashing official sony firmwares. It is pretty simple. If you are facing any problems then please feel free to message me.
my email : [email protected]
#coolmen777
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
coolmen777 said:
Looks like this phone got the dreaded sleep of death bug (won't turn on at all, no matter which combination of buttons I press). Had it on the charger for last 3 days (no led indicators at all and no vibrations), so I got a brick now. Any ideas? This phone should still be under warranty (manufactored week 9 of 2016), but Sony USA refuses to service International phones in their facility. Learned that based on IMEI, this is a Hong Kong version and they want an invoice from authorized dealer for warranty work. Are there are other countries that honor warranty without checking invoice (go by date of manufactoring?) I had Moto and LG repaired before just based on age of phone, no invoice needed. This is my last resort option (to attempt sending in for service).
Click to expand...
Click to collapse
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
civicsr2cool said:
search on here for a thread about flashing the wrong ftf onto the phone, I think op used a tablet ftf and had teh same results and had to send to sony
edit:
http://forum.xda-developers.com/z5-compact/help/flashed-wrong-mm-rom-phone-dead-help-t3330929
Click to expand...
Click to collapse
Thanks, not very encouraging given the fact that Sony USA supposedly doesn't currently have a service center to repair international phones (closed their TX center). Are there other countries (Canada or UK) which have less stringent policies of needing invoice (for proof of purchase) and can simply go off of manufacture date from the IMEI or device info? Thanks again.
Hi Folks
I just bought my girlfriend a Redmi Note 3 SE (Kate) quick back story, she received it turned it on added a pin to it got called away, when she got back to it she couldn't remember the pin, bad news is she hadn't yet turned on Developer Mode or USB Debugging.
Original SW - MIUI 7.5 android 6.0.1, at least that's what the Ali product page says (Sorry it seems I can't post a link to the actual product)
This began last Friday, since then she has tried the following:-
Installed MI Suite and registered a gmail account - so far "device not recognised"
Applied for an Unlock code.
Unlocked the boot loader which seems to have been successful.
Flashed two different (stock) ROM's which completed successfully but both stuck while booting the phone.
One was:-
"kate_global_images_6.12.29_20161228.0000.00_6.0_global" not sure what the other was.
On trying a different ROM today she's now getting the following error:-
"Can't Flash in miflash. Not enough storage is available to process this command"
Tried different versions of the Flash tool including the Beta version but still getting the same error on each of them.
Ticked the "Clear Data" box in the Mi Flash tool but that doesn't help.
A bit stuck on what to try from here and any help would be greatly appreciated if you need any more info please let me know.
I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.
What versions of miflash have you tried and which firmware did you download from xiaomi?
theoneofgod said:
I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.
What versions of miflash have you tried and which firmware did you download from xiaomi?
Click to expand...
Click to collapse
Hi thanks for the reply, unfortunately I need to wait for an answer on that as she's not around at the moment, but from what I can gather she has tried miuiflash 1, 2 and beta and i know she tried this which I'm assuming is a firmware - kate_global_images_6.12.29_20161228.0000.00_6.0_global (if it's not please let me know what we should be using) *edit, mind you that's one of the files that got stuck showing the out of space error.
I also forgot to mention the PC is a win 10 64bit..
Soon as I can get you a better answer on the above I'll post it.
I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.
Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.
theoneofgod said:
I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.
Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.
Click to expand...
Click to collapse
Ah so it wasn't a firmware, alright I've passed this on as soon as I hear back I'll post here, many thanks.
I just checked the link for the 8.1.1.0 Firmware but it gives a 404 error on the page, I'll look on their site for an alternative, but if you do know of an alternative please let me know.
**edit Never mind a right click and copy link location got it.
So the issue looks to be solved, so firstly many thanks "theoneofgod" for your input.
Unfortunately due to a rather dodgy internet connection I haven't managed to get further into it, but here is what I received:-
"I used the same Kate and used miflash beta version.. i did the same as i did on first attempt.. after succesfully flashing it, i turned it on (result:same stuck on booting)
i switch it back to fastboot mode.
flash it.
result error.
i then press power on for about 5 seconds or till the mi logo appeared.
unplugged the USB cable and plugged it in again.
then phone booted.
and
When miflash beta version recognized my phone as just a device not com port. i flashed it. (it was just flashing endlessly)
So i tried to refresh the page, it then showed my device with an id as com10 (I have a feeling this might be the important part)
i flashed that too, and then it worked didn't get that error " no storage" anymore.
I'm not sure though if that helped
Basically I'm saying that i was flashing 1 device with two different id.
So I'm thinking simply the device refresh actually did the trick, anyway it looks to be solved, that was 3 days of no fun, and that whole thing about hey submit an application for a bootloader unlock and then wait 2 or 3 weeks and we might even refuse it lol.
Thanks again for your help "theoneofgod" thanks meter pressed.
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 have flashed my Lenovo Vibe K5, former build A6020a40_S004 to A6020a40_105, hoping for that VoLTE update. Following the proper steps and downloading the Stock ROM Firmware from trusted supplier, my phone won't boot into anything: recovery, or normal. Though the LED lights up when connected to a computer. However, it doesn't appear on my computer or hear that USB chime. I'm using a Windows 10 (which I've seen many have issues with Windows 10 and drivers) running on Bootcamp 6. I appreciate it if you guys could help me. Thank you very much.
By the way, I have no custom recovery installed. Just the basic Android System Recovery <3e> and I'm not that familiar with Android systems.
justinfinity09 said:
Hello. I have flashed my Lenovo Vibe K5, former build A6020a40_S004 to A6020a40_105, hoping for that VoLTE update. Following the proper steps and downloading the Stock ROM Firmware from trusted supplier, my phone won't boot into anything: recovery, or normal. Though the LED lights up when connected to a computer. However, it doesn't appear on my computer or hear that USB chime. I'm using a Windows 10 (which I've seen many have issues with Windows 10 and drivers) running on Bootcamp 6. I appreciate it if you guys could help me. Thank you very much.
By the way, I have no custom recovery installed. Just the basic Android System Recovery <3e> and I'm not that familiar with Android systems.[/Q
Click to expand...
Click to collapse
Well sorry to hear about that but I know very well how to recover from such situation. You'll need to flash the recovery IMG again so that it boots into recovery mode
Brawler leon said:
Well sorry to hear about that but I know very well how to recover from such situation. You'll need to flash the recovery IMG again so that it boots into recovery mode
Click to expand...
Click to collapse
Thanks! Can you tell me how? I've been researching about this as well for a long time now. Any help is appreciated.
Yes my bud. I will provide you the link shortly to some SDK tools so that you can flash your recovery IMG again and et access to recovery mode. I know that situation is chaotic and sucks but I am assuming that you aren't able to access twrp or anything.when you turn the phone on it gets stuck at lenovo and after few minutes it gets restarted on its own. And on connection g it to computer, it just doesn't get connected and nothing appears to be connected. I want you to take the battery out and place it again after few minutes and press the "vol down" button and "power button at the same time. You'll see the same lenovo icon but there will be something written in Chinese or something like that. Now connect your phone to your computer and I advise you to use a very good quality data sharing cable or original lenovo cable. Now your computer will recognise your phone as a hard drive or a storage device.i I'll try to upload a video on that too. Till then try these steps and lemme know if they work and your computer recognises your dead phone.if it does then there is still a hope left. BTW I was stuck in the same situation twice but thank god I saved myself and I am using my device. Note:- this method doesn't uses any software like " QFIL" or "QCOM" loader to flash stock firmware. Hope it works
---------- Post added at 05:30 PM ---------- Previous post was at 05:22 PM ----------
Just keep replying if it works and within a week you'll get your phone fully functional.
Here I have uploaded the platform tools needs d to flash recovery
Brawler leon said:
Here I have uploaded the platform tools needs d to flash recovery
Click to expand...
Click to collapse
Thanks a lot, man. Where the hell have you been all my life? Lol.
So my phone doesn't boot. It doesn't even show the Lenovo logo on it. Just mere darkness. :'(
I am going to Hong Kong later this week (this is where I bought the phone) and I don't know, maybe have someone fix it.
PS. Can you please DM me the links or if it isn't a loss for you you may just reply it here.
Thanks in advance and more power. The world needs more people like you.
Sincerely,
Justin
Sorry for responding late bud.but I am not able to post the link on this thread. If you have any e mail address then tell me so that I can mail you the links. And as you said your phone doesn't boot I want to ask you whether your phone charges when you connect it to the power and charging bar is shown or not. If yes then pls remove your phone battery and put it back and press the power button and the vol. down button hardly .if you see lenovo logo and something written in Chinese or something like that then you're on the way to get your phone back.just reply me the results soon bud
Brawler leon said:
Sorry for responding late bud.but I am not able to post the link on this thread. If you have any e mail address then tell me so that I can mail you the links. And as you said your phone doesn't boot I want to ask you whether your phone charges when you connect it to the power and charging bar is shown or not. If yes then pls remove your phone battery and put it back and press the power button and the vol. down button hardly .if you see lenovo logo and something written in Chinese or something like that then you're on the way to get your phone back.just reply me the results soon bud
Click to expand...
Click to collapse
Hey man. Justin here, again.
You may reach me through "[email protected]".
It doesn't show anything. Though, the LED light illuminates when connected to a power source or laptop. I'm starting to think it's absolutely hopeless. But please do message me anyway.
Fondly,
Justin
I think you have hard bricked your phone but still let's try
Brawler leon said:
I think you have hard bricked your phone but still let's try
Click to expand...
Click to collapse
Sure. I will wait for you in my e-mail. Thanks!
Brawler leon said:
Yes my bud. I will provide you the link shortly to some SDK tools so that you can flash your recovery IMG again and et access to recovery mode. I know that situation is chaotic and sucks but I am assuming that you aren't able to access twrp or anything.when you turn the phone on it gets stuck at lenovo and after few minutes it gets restarted on its own. And on connection g it to computer, it just doesn't get connected and nothing appears to be connected. I want you to take the battery out and place it again after few minutes and press the "vol down" button and "power button at the same time. You'll see the same lenovo icon but there will be something written in Chinese or something like that. Now connect your phone to your computer and I advise you to use a very good quality data sharing cable or original lenovo cable. Now your computer will recognise your phone as a hard drive or a storage device.i I'll try to upload a video on that too. Till then try these steps and lemme know if they work and your computer recognises your dead phone.if it does then there is still a hope left. BTW I was stuck in the same situation twice but thank god I saved myself and I am using my device. Note:- this method doesn't uses any software like " QFIL" or "QCOM" loader to flash stock firmware. Hope it works
Tried removing battery, its still in bootloop.
Click to expand...
Click to collapse
So, there's a lot of people sending me PM, most asking how to unbrick the GT2Pro. To make things easy I'll try to explain the basics here...
The good news is that the GT2Pro is pretty much unbrickble, unless you mod the hardware you can always bring the phone back to normal thanks to the EDL mode. The EDL mode connect direct to the chipset, even if the battery runs out completely.
The bad news is that you'll probably have to spend some money.
There's two ways to flash the phone via EDL mode, with QFIL or MSM Download Tool.
The QFIL is free, but it is very buggy, you can try it, but it probably won't work. I don't remember very much how to use QFIL, but I do remember that you'll need to extract the files of .ofp, select the right ones in the QFIL, change some settings and try to flash... And you'll probably get some error... Mine most of the time was "Firehose error" and "Sahara error"... I tried diferent versions of QFIL, diferent configs, tons of tweaking.. Didn't work.
The MSM Download Tool is flawless, but you have to login to access the software and only developers, official repair or resellers have access, luckly there are a lot of people who sell the login. Well, you'll need to get the login at leat untill the realme release a patched version of MSM for GT2Pro.
To login into MSM there's two ways, the login itself or using a Loader, most of the time you'll get the code to use the Loader, you can use the code only once.
So...
-Get the Realme Login Tool 2.0, MSM Download Tool 2.0.67 and the .ofp of your phone region and put all in the same folder..
-Turn off your antivirus or allow the MSM to transpassing it..
-Run the Login Tool as a admin, put the OTP code..
-In the MSM select the .otp file..
-Connect the phone to the PC and turn on the EDL mode..
-To enter the EDL mode Hold Volume Up + Down at same time, if the phone battery is completely dried out connect the phone to PC, hold the Power button for a long time and wait about 4 or 5 minutes to get a minimum charge to enter EDL mode..
-Then just click Start, if you get some error select the option in the top right corner "Standard something" or "Default something" I think... I don't remember..
Don't forget that for the PC to recognize the phone in EDL mode you'll need the right Windows driver, the Windows recognize as "Qualcomm HS-USB QDLoader 9008" most of the time. You find the driver easily on the internet.
I have all the files needed, but it's not here right now with me.. When I get it I'll upload here.
If the Admin allows (so you guys ask him) I'll put here the number of the cheapest guy to get the OTP code, I got the code for $2 and he accepts PayPal. There's people who do all the job via TeamViewer too, but generally it's more expensive and you can't get access to MSM. If you are messing up with the GT2Pro, flashing, tweaking, changing configs, etc, just get access to MSM and don't close the app, then if you brick the phone just flash again... And again... And again...
You guys can also pressure realme to release a patched version of MSM Download Tool for GT2Pro...
Good luck
Cheers
----------------
So these are the files... I think that's all... If I remember others I'll upload them...
Maybe it's a silly question, but have you tried loading prog_firehose_ddr.elf in QFIL?
Rapper_skull said:
Maybe it's a silly question, but have you tried loading prog_firehose_ddr.elf in QFIL?
Click to expand...
Click to collapse
Yeah.. The .elf and .mbn ... It didn't work.
Though trading is not permitted on XDA, but OP wants to help Realme GT 2 Pro users, as many users are even paying upto 10 USD for fixing their device due to absence of official download tool . So He should be permitted to share contact info of cheap code provider.
I had to pay $25 a couple weeks ago to get mine fixed, it would be much better if we can have a cheaper or free alternative.
zorbakun said:
I had to pay $25 a couple weeks ago to get mine fixed, it would be much better if we can have a cheaper or free alternative.
Click to expand...
Click to collapse
Yeah... The best shot is to pressure realme to release a patched version of MSM like they have for other phones or pressure them to update their Flash Tool for GT2Pro.
When using the MSM tool to flash will it recognize the nv-id of my phone and automatically pull and merge the correct super images from the firmware ofp or does that need to be done manually before flashing?
Ok idk what I am doing wrong here. Everytime I try to flash with MSM Tool I get an error that says "Failed to get NV Code:"
Could this be because the realme server is offline?
What will happen if I select the "Use Default NV" box?
When I click it a popup comes up and says "Default NV (MEA) will be used if this tool cannot get NV from server. Continue?"
How did you get access to MSM tool?
By using the realme login tool and an OTP
edit: Yeah alright I don't get it. I flashed the phone with the MSM tool back to A.17 and the bootloader is still unlocked and still will not boot and I am not getting the A18 update either. Is this just impossible to fix?
can you please elaborate regarding "By using the realme login tool and an OTP"
kkffiirr said:
can you please elaborate regarding "By using the realme login tool and an OTP"
Click to expand...
Click to collapse
The OP posted the realme login tool that can be used to gain access to the MSM tool. Download your firmware and extract the zip file and move the realme login tool into the folder containing the MSM and ofp files then open the tool and type the OTP/one-time password (there are plenty of people who sell them but XDA only allows sharing free and open source solutions). This will open the MSM tool and allow you to flash.
I was in total shock, I didn't find a solution, even the support didn't help me, they ignored my emails.......
Until I found a guy who helped me on Telegram @Fixteambd for a nominal sum of only $10 I'll confirm he deserves the money!!
managed to get out of the RMX3300 brick in less than 20 minutes
My 3300 bricked flashing global rom, it does not respond to any buttons or USB. Nothing happens at all. Any ideas on how to revive it?
Hello, so you say you can use MSM Download Tool even with a dead battery but even when you open the program it says to ensure you have enough battery. Now, I have paid a guy to try and fix my soft bricked GT 2 pro with this program but cmd is not letting him do anything due to the battery levels and MSM keeps getting an error and I'm assuming it's also because of battery levels.. is there hope for me? Would anyone be able to help please?? I'm getting desperate at this point
anika_kirana said:
Hello, so you say you can use MSM Download Tool even with a dead battery but even when you open the program it says to ensure you have enough battery. Now, I have paid a guy to try and fix my soft bricked GT 2 pro with this program but cmd is not letting him do anything due to the battery levels and MSM keeps getting an error and I'm assuming it's also because of battery levels.. is there hope for me? Would anyone be able to help please?? I'm getting desperate at this point
Click to expand...
Click to collapse
I believe you gonna have to open the device and unplug the battery for it to work, not 100% sure if it's the only way to do it but if you left if changing for an hour or 2 and still can't flash with MSM I'm guessing the only way is to open the device and unplug the battery, were you able to put it in EDL mode without opening it?
I left it charging overnight the problem is that it doesn't recognise it as being plugged so it's actually not charging at all. I was thinking of opening it up and "manually" charging the battery and I've seen a charging board on eBay to charge batteries connecting the flex directly to it but 1) I wasn't sure if that would make it work and 2) I wanted to make sure there were no other options before opening the phone up. I've seen you can potentially charge if you're able to boot twrp and using that recovery but I can't find anywhere how to do that with a GT 2 pro so I don't even know if that's an option... Thank you for your reply by the way
anika_kirana said:
I left it charging overnight the problem is that it doesn't recognise it as being plugged so it's actually not charging at all. I was thinking of opening it up and "manually" charging the battery and I've seen a charging board on eBay to charge batteries connecting the flex directly to it but 1) I wasn't sure if that would make it work and 2) I wanted to make sure there were no other options before opening the phone up. I've seen you can potentially charge if you're able to boot twrp and using that recovery but I can't find anywhere how to do that with a GT 2 pro so I don't even know if that's an option... Thank you for your reply by the way
Click to expand...
Click to collapse
dude, it's hard brick, you have to short test Point to access EDL Mode, after that MSM Flash
Yep, that's what I had to do in the end, but the good news is that it worked and I have a working phone again, the bad news is that I damaged the power flex cable opening it up so next project is to replace it, although I'm still using it every day and I don't seem to miss the button. I can lock it with double tap and take screen shots with the three fingers gesture. Wish me luck with the replacement when it finally arrives from AliExpress!
Somebody let me know where I can get cheap OTP code for Realme Login Tool 2.0 (RLT2) for flash Realme GT2 Pro RMX3300, RMX3301.