Related
Hi all im just looking at a cheap phone for my mom that will pretty much just be used for phone calls and texts but I was wondering if anyone has got one of these phones and if you can root them so I can delete some rubbish off it so she has got some more room for apps as they only have 4g I believe if anyone could help id be really grateful
Jxt. said:
I didn't see any sites that talks about rooting, but you should check out the one click rooting application to see if your device is supported.
Click to expand...
Click to collapse
Thanks I'll give it a try when it comes through
Has anyone got a link to this app please and also is this the only way that may be possible thanks
Rooting DG100
galaxys3_newbie said:
Thanks I'll give it a try when it comes through
Click to expand...
Click to collapse
I'm also contemplating rooting one of these and would appreciate if you could comment on the success of One Click Rooting.
Thanks
I will do just waiting for it to come through what do you thonk of the phone
Sent from my GT-I9300 using xda app-developers app
galaxys3_newbie said:
I will do just waiting for it to come through what do you thonk of the phone
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Try Shuame
I've bought one of these Doogee DG100 smartphones, had it about a month now, and it's really excellent value for the price - I can't find anything I don't like about it. Well built, great phone and I'd highly recommend it. Well, Ok, the plastic fake leather cover's a bit naff, but hey.
I've rooted it using SRSRoot, flashed the latest firmware from the Doogee download site and I use MKTDroid for ADB access etc.
I removed all of the junk I didn't want, and removed the preloaded apps (twitter, whatsapp, skype etc) and reinstalled them from the Play Store - I didn't trust that some of them wouldn't update properly.
Managed to brick it too by doing dumb stuff, but the Doogee Flashtool just let me reflash the firmware and away it goes again.
Seems pretty bullet proof. Let me know if you get stuck and I'll try to help out.
Good luck!
the flash tool
serafis said:
I've bought one of these Doogee DG100 smartphones, had it about a month now, and it's really excellent value for the price - I can't find anything I don't like about it. Well built, great phone and I'd highly recommend it. Well, Ok, the plastic fake leather cover's a bit naff, but hey.
I've rooted it using SRSRoot, flashed the latest firmware from the Doogee download site and I use MKTDroid for ADB access etc.
I removed all of the junk I didn't want, and removed the preloaded apps (twitter, whatsapp, skype etc) and reinstalled them from the Play Store - I didn't trust that some of them wouldn't update properly.
Managed to brick it too by doing dumb stuff, but the Doogee Flashtool just let me reflash the firmware and away it goes again.
Seems pretty bullet proof. Let me know if you get stuck and I'll try to help out.
Good luck!
Click to expand...
Click to collapse
Hi,
I don't know if it's because it's all written in Chinese when I get to the page with the actual zip on it or if it's because I'm blind and am missing some important visual cue on the page, but I can't figure out how to download the firmware or how to get the tools. Any advice on this? I even tried looking at the source code to see if there is a direct link to the file, but it's all full of JavaScript.
Incidentally, is there any indication on the site as to whether we might expect a newer version of Android on this phone in the future?
problem with dg100
Hi, i need your help to fix my DG100, i tried to upgrade following the instructions in the website of Doogee and now the phone is not working at all. when i click in UPGRADE&FIRMWARE and connect the phone i got an error: SP FLASH TOOL ERROR: (8045) NO VALID PARTITION MANAGEMENT TABLE (PMT) FOR STORAGE DEVICE and when i click in DOWNLOAD and connect the phone i got : BROM ERROR: S_NOT_ENOUGH_STORAGE_SPACE (1011). Please, can you tell what i must do for fix this problem?. Thank you for your help.
Firmware 0926
tuxedo116 said:
Hi, i need your help to fix my DG100, i tried to upgrade following the instructions in the website of Doogee and now the phone is not working at all. when i click in UPGRADE&FIRMWARE and connect the phone i got an error: SP FLASH TOOL ERROR: (8045) NO VALID PARTITION MANAGEMENT TABLE (PMT) FOR STORAGE DEVICE and when i click in DOWNLOAD and connect the phone i got : BROM ERROR: S_NOT_ENOUGH_STORAGE_SPACE (1011). Please, can you tell what i must do for fix this problem?. Thank you for your help.
Click to expand...
Click to collapse
If you use the SP_Flash_Tool_v3.1320.0.174, you will manage to overcome that problem, but then you'll face the real one. The real problem is that your,phone like mine too, has a different version LCD display, that needs firmware 0926 to work right. If you use 0917, phone will flash, reboot, but show garbage on screen. I am asking Doogee to provide me the 0926 firmware (the one that my phone had installed when it arrived 5 days ago), but they don't reply to my mails. It also seems that the new display is not IPS as the earlier versions, as it greys while on angle and shows color shifting (obvious even with garbage on screen...).
I am waiting for a second DG100 within next week, so if anyone can share a way about extracting 0926 firmware from it, i would be obliged...
Asterisd said:
If you use the SP_Flash_Tool_v3.1320.0.174, you will manage to overcome that problem, but then you'll face the real one. The real problem is that your,phone like mine too, has a different version LCD display, that needs firmware 0926 to work right. If you use 0917, phone will flash, reboot, but show garbage on screen. I am asking Doogee to provide me the 0926 firmware (the one that my phone had installed when it arrived 5 days ago), but they don't reply to my mails. It also seems that the new display is not IPS as the earlier versions, as it greys while on angle and shows color shifting (obvious even with garbage on screen...).
I am waiting for a second DG100 within next week, so if anyone can share a way about extracting 0926 firmware from it, i would be obliged...
Click to expand...
Click to collapse
Hi, thank you for your answer, i am using SP_Flash_Tool_v3.1320.0.174 but nothing happen, could you please tell me, how can i do to overcome the problem?, thank you.
tuxedo116 said:
Hi, thank you for your answer, i am using SP_Flash_Tool_v3.1320.0.174 but nothing happen, could you please tell me, how can i do to overcome the problem?, thank you.
Click to expand...
Click to collapse
Ok, i managed to get my phone working again, by using an extracted rom from a phone with 0926 firmware.
h**ps://docs.google.com/file/d/0B2JMI3yL-RxZWHdYaFYycDhsdUE/edit?usp=sharing
Download this files, extract them in folder with firmware 0917 and then flash them to the phone. This will work until we get the firmware from the factory (if it ever publishes it). Doogee no more for me, by the way, their customer support sucks...
Files from 0926
Asterisd said:
Ok, i managed to get my phone working again, by using an extracted rom from a phone with 0926 firmware.
h**ps://docs.google.com/file/d/0B2JMI3yL-RxZWHdYaFYycDhsdUE/edit?usp=sharing
Download this files, extract them in folder with firmware 0917 and then flash them to the phone. This will work until we get the firmware from the factory (if it ever publishes it). Doogee no more for me, by the way, their customer support sucks...
Click to expand...
Click to collapse
Yo, i tried using the files you uploaded to flash. however, i am still faced with the BROM ERROR: S_NOT_ENOUGH_STORAGE_SPACE (1011). btw, i also used the SP_Flash_Tool_v3.1320.0.174
dealer12 said:
Yo, i tried using the files you uploaded to flash. however, i am still faced with the BROM ERROR: S_NOT_ENOUGH_STORAGE_SPACE (1011). btw, i also used the SP_Flash_Tool_v3.1320.0.174
Click to expand...
Click to collapse
Doogee announced new firmwares, 0926 and 1101 for DG100 at their site. Try 1101 first and then the 0926.
Solution
I solved the problem of the error 4032, steps:
1) i used windows xp, i don't know if it will work in windows 7.
2) i did use firmware 9_26 and flashtools v3.1328.
3) select the scatter of the firmware 9_26, leave marked only PRE-LOADER and click in DOWNLOAD.
4) Keep pushed (power) + (volume -) and connect the cable to the pc. You must see the red line, then purple and finally the green circle, then disconnect the cable.
5) Now unmark PRE-LOADER and mark the rest of the options and click in DOWNLOAD; then connect the cable keeping the buttons (power) + (volume -) pushed; now you must see the red line, then the yellow line and the green circle.
Thanks to Asterisd for your advice.
serafis said:
I've bought one of these Doogee DG100 smartphones, had it about a month now, and it's really excellent value for the price - I can't find anything I don't like about it. Well built, great phone and I'd highly recommend it. Well, Ok, the plastic fake leather cover's a bit naff, but hey.
I've rooted it using SRSRoot, flashed the latest firmware from the Doogee download site and I use MKTDroid for ADB access etc.
I removed all of the junk I didn't want, and removed the preloaded apps (twitter, whatsapp, skype etc) and reinstalled them from the Play Store - I didn't trust that some of them wouldn't update properly.
Managed to brick it too by doing dumb stuff, but the Doogee Flashtool just let me reflash the firmware and away it goes again.
Seems pretty bullet proof. Let me know if you get stuck and I'll try to help out.
Good luck!
Click to expand...
Click to collapse
I've done the extact same thing however I am not able to download twitter, whatsapp, skype or facebook after uninstalling and reinstalling in Play Store. The message I receive is the software is not digitally signed. The camera sucks really bad after doing the latest firmware upgrade. Is it me or am I missing something in the process ?
Doogee Collo Dg100 boot problem
I have a Doogee Collo DG100.
I have tried to flash a new ROM but at the middle of the process I got an error from SP Flash Tool "BROM ERROR:S_NOT_ENOUGH_STORAGE_SPACE(1011)". Now the phone does not start.
Can you please tell me what to do?
psild said:
I have a Doogee Collo DG100.
I have tried to flash a new ROM but at the middle of the process I got an error from SP Flash Tool "BROM ERROR:S_NOT_ENOUGH_STORAGE_SPACE(1011)". Now the phone does not start.
Can you please tell me what to do?
Click to expand...
Click to collapse
I get an error at wi-fi settings NVRAM WARNING: Err = 0x10.
Can anyone tell me what it is?
Tony Speaks said:
Hi,
I don't know if it's because it's all written in Chinese when I get to the page with the actual zip on it or if it's because I'm blind and am missing some important visual cue on the page, but I can't figure out how to download the firmware or how to get the tools. Any advice on this? I even tried looking at the source code to see if there is a direct link to the file, but it's all full of JavaScript.
Incidentally, is there any indication on the site as to whether we might expect a newer version of Android on this phone in the future?
Click to expand...
Click to collapse
I use Chrome which seems to auto-translate and gives me a Chinglish version of the screens, which makes it a lot easier.
I assume you got to the pan.baidu download site? If so, in the middle of the screen there is an icon that looks a bit like a suitcase. Above and to the right there are two rectangular buttons, one blue and the other unfilled. Click the unfilled one. A popup window will appear with another two rectangular buttons at the top, one blue and one unfilled. Again click the unfilled one. That should start the download.
This site has a list of the latest downloads: http://www.doogee.cc/en/gb/xiazai.asp - I'm currently running DG100-0917 and about to try DG100-1101
Hope that helps.
---------- Post added at 01:16 PM ---------- Previous post was at 01:03 PM ----------
rci_canada said:
I've done the extact same thing however I am not able to download twitter, whatsapp, skype or facebook after uninstalling and reinstalling in Play Store. The message I receive is the software is not digitally signed. The camera sucks really bad after doing the latest firmware upgrade. Is it me or am I missing something in the process ?
Click to expand...
Click to collapse
What's the exact wording of the message(s) you get? I recall I had some difficulty with this and googled how to overcome it, including deleting incorrect application IDs and certificates from one of the Android files - sorry, I can't now remember exactly what steps I followed but if you can post the exact message I'll try to help.
I don't think I was able to get Facebook to update from Play, no matter what I did. I think I read somewhere that this might be to do with one of the themes that Doogee / Mediatek use being incompatible with later versions of Facebook.
Anyway, please post the message(s) and I'll see what I can do.
Cheers.
DG100-1101 breaks WiFi
I installed the latest firmware, DG100-1101 but unfortunately Wi Fi and Bluetooth don't work, and when I reverted to DG100-0927 I get an odd entry in WiFi settings NVRAM WARNING Err = 0x10. Everything else seems OK though.
I would advise NOT upgrading to this version and if anyone finds a fix for the Wi Fi issue' please post here, thanks
Please help me. i got stuck my phone. My phone was runing on lillipop 324 and i have downloaded marshmallow 511, put that in dload and applied local update. i have made the mistake that i didn't notice at that time that this update is for 326. my phone restarted for applying marshmallow update. status of update was successful but during powering on phone got stuck on Huawei logo and this time continuosly restarting. i have tried so many thing. I have tried to flash back 324 but failed on 5%. I have tried again 511 update that may be some files got missed, the status of that comes successful every time. i have tried to roll back my phone using this 6 mb and 9mb files by three buttons methoud but failed on 5%. Pease guide me urgently phone does not even power off, continuosly attemting to restart and not go further as logo appears. either it is restarting or i can put it in hard reset mode screen. no other option. i am also scared that its battery would be drained. please help me. Please help me urgently
There's nothing you can do right now. There are plenty of mate 7 owners here who have bricked
their phones after installing marshmallow 511. Here's the thread that you may want to follow:
http://forum.xda-developers.com/mate-7/general/help-tl09-restarting-marshmallow-b511-t3304178/page3
Ali Faizan said:
Please help me. i got stuck my phone. My phone was runing on lillipop 324 and i have downloaded marshmallow 511, put that in dload and applied local update. i have made the mistake that i didn't notice at that time that this update is for 326. my phone restarted for applying marshmallow update. status of update was successful but during powering on phone got stuck on Huawei logo and this time continuosly restarting. i have tried so many thing. I have tried to flash back 324 but failed on 5%. I have tried again 511 update that may be some files got missed, the status of that comes successful every time. i have tried to roll back my phone using this 6 mb and 9mb files by three buttons methoud but failed on 5%. Pease guide me urgently phone does not even power off, continuosly attemting to restart and not go further as logo appears. either it is restarting or i can put it in hard reset mode screen. no other option. i am also scared that its battery would be drained. please help me. Please help me urgently
Click to expand...
Click to collapse
don brian said:
There's nothing you can do right now. There are plenty of mate 7 owners here who have bricked
their phones after installing marshmallow 511. Here's the thread that you may want to follow:
http://forum.xda-developers.com/mate-7/general/help-tl09-restarting-marshmallow-b511-t3304178/page3
Click to expand...
Click to collapse
Then what is the solution to it? I am follwoing the thread u mentioned.
Like the rest of those with bricked Mate 7 phones after failed update to B511,
you just have three options:
1) Wait for HUAWEI to release the official marshmallow to lollipop downgrade package for your region (you will use this to go back to lollipop),
2) Wait for the FINAL MARSHMALLOW (not beta) release from HUAWEI so you can install the final, full marshmallow release (not beta) or
3) Send your phone to a service center (assuming the service center personnel in your area are well versed with Huawei software).
Some service centers replace the internal memory assembly of the phone so you get can get back to kitkat. (They then send the bricked memory
assembly of your phone to more competent service centers.)
Sorry, it's really a waiting game for now unless option 3 works for you.
(Many Huawei service centers are really incapable/not competent enough to solve bricked software/firmware problems on the Mate 7.)
Ali Faizan said:
Then what is the solution to it? I am follwoing the thread u mentioned.
Click to expand...
Click to collapse
don brian said:
Like the rest of those with bricked Mate 7 phones after failed update to B511,
you just have three options:
1) Wait for HUAWEI to release the official marshmallow to lollipop downgrade package for your region (you will use this to go back to lollipop),
2) Wait for the FINAL MARSHMALLOW (not beta) release from HUAWEI so you can install the final, full marshmallow release (not beta) or
3) Send your phone to a service center (assuming the service center personnel in your area are well versed with Huawei software).
Some service centers replace the internal memory assembly of the phone so you get can get back to kitkat. (They then send the bricked memory
assembly of your phone to more competent service centers.)
Sorry, it's really a waiting game for now unless option 3 works for you.
(Many Huawei service centers are really incapable/not competent enough to solve bricked software/firmware problems on the Mate 7.)
Click to expand...
Click to collapse
What the **** is Huawei doing with customers. anyways thanks bro. If u come to know any solution please let me inform.
Ali Faizan said:
What the **** is Huawei doing with customers. anyways thanks bro. If u come to know any solution please let me inform.
Click to expand...
Click to collapse
It's not Huawei fault that you flashed BETA firmware that is for BETA testers and you find that firmaware on xda forum leaked by some of BETA testers.
And second thing you should read to know from which version you can update.
B329 - >B511
B331 - >B513
Sent from my HUAWEI MT7-L09 using Tapatalk
Pablo87 said:
It's not Huawei fault that you flashed BETA firmware that is for BETA testers and you find that firmaware on xda forum leaked by some of BETA testers.
And second thing you should read to know from which version you can update.
B329 - >B511
B331 - >B513
Sent from my HUAWEI MT7-L09 using Tapatalk
Click to expand...
Click to collapse
yupp i was careless about that i dont have any idea that this can be wiered. but please tell me now that what rights are available to me? what i can do now?
If you have unlocked bootloader and root there is hope to unbrick.
Sent from my JAZZ using XDA Free mobile app
tjoseph623 said:
If you have unlocked bootloader and root there is hope to unbrick.
Sent from my JAZZ using XDA Free mobile app
Click to expand...
Click to collapse
No i have not yet rotted but fon still rebotes in fast boot mode. can i try root at this stage? suggest me any useful links if it can be rooted?
http://forum.xda-developers.com/mate-7/general/tried-to-roll-b511-to-b326-fail-try-t3302479
Try this topic but first read more and more.
Welcome to the club of bricked mate 7's
Ali Faizan said:
yupp i was careless about that i dont have any idea that this can be wiered. but please tell me now that what rights are available to me? what i can do now?
Click to expand...
Click to collapse
Ali Faizan said:
Then what is the solution to it? I am follwoing the thread u mentioned.
Click to expand...
Click to collapse
Hi, every few days I come back here and I find new bricked mate 7 and a frustrated and desperate owner, but I also find defenders of Huawei , most probably those with their phones running well, trying to put the blame on us who chose to brick their phones !! Well, as far as I know if a respectable company have good numbers of customers sharing a major problem that disabled their phones, they will try to help them not to blame them and dump them. So for you, please get over it, I know it is hard but you have to get over it , buy a new phone , it will make you feel better and keep your phone till a solution surface. Don't waste your time , nothing ever will work now.
tmahmoud said:
Hi, every few days I come back here and I find new bricked mate 7 and a frustrated and desperate owner, but I also find defenders of Huawei , most probably those with their phones running well, trying to put the blame on us who chose to brick their phones !! Well, as far as I know if a respectable company have good numbers of customers sharing a major problem that disabled their phones, they will try to help them not to blame them and dump them. So for you, please get over it, I know it is hard but you have to get over it , buy a new phone , it will make you feel better and keep your phone till a solution surface. Don't waste your time , nothing ever will work now.
Click to expand...
Click to collapse
okay boss
Ali Faizan said:
Please help me. i got stuck my phone. My phone was runing on lillipop 324 and i have downloaded marshmallow 511, put that in dload and applied local update. i have made the mistake that i didn't notice at that time that this update is for 326. my phone restarted for applying marshmallow update. status of update was successful but during powering on phone got stuck on Huawei logo and this time continuosly restarting. i have tried so many thing. I have tried to flash back 324 but failed on 5%. I have tried again 511 update that may be some files got missed, the status of that comes successful every time. i have tried to roll back my phone using this 6 mb and 9mb files by three buttons methoud but failed on 5%. Pease guide me urgently phone does not even power off, continuosly attemting to restart and not go further as logo appears. either it is restarting or i can put it in hard reset mode screen. no other option. i am also scared that its battery would be drained. please help me. Please help me urgently
Click to expand...
Click to collapse
I was able to partially fix my phone by 1.) flashing TWRP 2.) advanced wiping the system 3.) restoring TWRP backup all with the help of Blue.Ember
Can it get to recovery so you can connect via adb and unlock it so it can be rooted? If so, you could then flash custom recovery and then flash a custom ROM. If that worked you could try to flash it back to standard and start again.
A lot of time and trouble though.
People need to STOP flashing their Mate 7 until something reliable is offered.
Kitkat is not so bad.....
Good news for those with bricked mate 7 phones!
(For those with unrooted, locked Mate 7 phones on boot loop.)
There are new OFFICIAL marshmallow to lollipop downgrade/rollback packages
uploaded by xda member albert-so758:
Check out his thread below:
http://forum.xda-developers.com/mate-7/development/finally-rollback-513-331-511-326-t3325803
Hopefully it will work for your bootlooping L09/TL10 phones.
So, ive been checking around here literally every 2 hours, trying to see if someone found a solution to force the update, rather than waiting and waiting.. Talking about the international version of the mate 9 of course..
Thought opening this might gather great minds here to find a solution.
So everyone, your help is much appreciated by all of us..
I've been testing all day with someone who has an affected phone. We have been successful in flashing B115 onto a European Mate 9 by hijacking eRecovery or using a trick to flash via USB in HiSuite, but B126 refuses to flash with either of these methods. There is something about the B126 package which the phones don't want to flash.
When a ROM is flashed on a Mate 9, it must have an internet connection. eRecovery (or HiSuite) sends a request for a code based on the serial number of the phone, its IMEI, an update token, and the version number of the update. Huawei's server returns an encrypted hash. This hash is then checked by the phone and for whatever reason, this check fails with the B126 package (it works fine with B115.) I have been looking into ways of getting around this, but the only way I can come up with (overwriting the hard disk area an update.app file is stored while Hisuite is doing the live flash) is extremely dangerous and could result in a brick. So it's better to wait for a new version to come out, which might be flashable via eRecovery or HiSuite.
So annoying! I'm also desperately waiting for the update because I really like the phone but some annoying bugs are just making the whole experience so annoying. It was quite silly of Huawei to actually release the phone with this half baked ROM.
Any way, now I'm not just going to check for update every hour but also this thread
Cheers,
Many thanks for your efforts @duraaraa, hopefully you'll find a way in the end.
I just found the exact reason why it doesn't work, and am working on a remedy. If it's successful, I will make it public tomorrow. Afterall, Huawei is not authenticating these versions for installation. OTA authentication is different so I can't say anything about that, but the authentication for eRecovery/HiSuite full version flash is not there.
duraaraa said:
I've been testing all day with someone who has an affected phone. We have been successful in flashing B115 onto a European Mate 9 by hijacking eRecovery or using a trick to flash via USB in HiSuite, but B126 refuses to flash with either of these methods. There is something about the B126 package which the phones don't want to flash.
When a ROM is flashed on a Mate 9, it must have an internet connection. eRecovery (or HiSuite) sends a request for a code based on the serial number of the phone, its IMEI, an update token, and the version number of the update. Huawei's server returns an encrypted hash. This hash is then checked by the phone and for whatever reason, this check fails with the B126 package (it works fine with B115.) I have been looking into ways of getting around this, but the only way I can come up with (overwriting the hard disk area an update.app file is stored while Hisuite is doing the live flash) is extremely dangerous and could result in a brick. So it's better to wait for a new version to come out, which might be flashable via eRecovery or HiSuite.
Click to expand...
Click to collapse
Thats tbe spirit i was looking for.. Mate9 gang around.. This way we all try to share updates
malikons said:
So annoying! I'm also desperately waiting for the update because I really like the phone but some annoying bugs are just making the whole experience so annoying. It was quite silly of Huawei to actually release the phone with this half baked ROM.
Any way, now I'm not just going to check for update every hour but also this thread
Cheers,
Click to expand...
Click to collapse
Join the club..
duraaraa said:
I just found the exact reason why it doesn't work, and am working on a remedy. If it's successful, I will make it public tomorrow. Afterall, Huawei is not authenticating these versions for installation. OTA authentication is different so I can't say anything about that, but the authentication for eRecovery/HiSuite full version flash is not there.
Click to expand...
Click to collapse
We all can't wait.. So keep us updated here..
I'm in....
Inviato dal mio MHA-L29 utilizzando Tapatalk
Ok, so. Here is what I have. I've been up all night, it's 7AM, and I'm tired, so I'm not going to be working on this any more until tomorrow. If any of you can find the solution to this, I can very likely let you flash whatever version you want onto your phone. This will be a long explanation, but if anyone is knowledgeable about openssl, they can help me hack at this.
Here is a response from a request to huawei's authorization server for B115, which can be flashed.
Code:
data=eyJ1cGRhdGVUb2tlbiI6Ijc1M0Q4QUYwMDAwNzFBQkMiLCJkZXZpY2VJZCI6IjU5OTg0RUJBQ0U5MkI3REJBQkQxMzUwQTk4NDgzQzlDM0U3MTYyRjMxMDExNDk0QjQ2REFFNkU4MjJEMkM0OEIiLCJhcHByb3ZlZFZlcnNpb25MaXN0IjpbeyJ2ZXJzaW9uSWQiOiI2NjcxMSIsInN0YXR1cyI6IjAiLCJ2ZXJzaW9uTnVtYmVyIjoiTUhBLUwyOUM5MDBCMTE1In1dfQ==&sign=MEUCIF1DGCXm0VPxuBa2qdBfGr98haEasb3yMcCVr+lYbHrBAiEAyZn3Wi1vlD9ZeWQDWeTt9kE7a9YJhFR2b01nG/FDlWI=&cert=MIIDJzCCAsygAwIBAgIJALWcScNmfs+NMAoGCCqGSM49BAMCMIHXMQswCQYDVQQGEwJDTjEQMA4GA1UECAwHSmlhbmdzdTEQMA4GA1UEBwwHTmFuamluZzEsMCoGA1UECgwjSHVhd2VpIFNvZnR3YXJlIFRlY2hub2xvZ2llcyBDTy5MdGQxQTA/BgNVBAsMOERldmllIFJlZ2lvbiBEZWxpdmVyeSAmIFNlcnZpY2UgUXVhbGl0eSAmIE9wZXJhdGlvbiBEZXB0MRQwEgYDVQQDDAtPVEEgUm9vdCBDQTEdMBsGCSqGSIb3DQEJARYOb3RhQGh1YXdlaS5jb20wHhcNMTYwNzEyMDgxOTU5WhcNMTcwNzEyMDgxOTU5WjCB2zELMAkGA1UEBhMCQ04xEDAOBgNVBAgMB0ppYW5nc3UxEDAOBgNVBAcMB05hbmppbmcxLDAqBgNVBAoMI0h1YXdlaSBTb2Z0d2FyZSBUZWNobm9sb2dpZXMgQ08uTHRkMUEwPwYDVQQLDDhEZXZpZSBSZWdpb24gRGVsaXZlcnkgJiBTZXJ2aWNlIFF1YWxpdHkgJiBPcGVyYXRpb24gRGVwdDEYMBYGA1UEAwwPT1RBIEF1dGggU2VydmVyMR0wGwYJKoZIhvcNAQkBFg5vdGFAaHVhd2VpLmNvbTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABGeDtAUO4uTY5yWwS54sk030WOdHYoaaO0dufn4jvul22Ytogvua1W0qY+ABblhA3eB49YXYPnpLvGhjr+73oZ6jezB5MAkGA1UdEwQCMAAwLAYJYIZIAYb4QgENBB8WHU9wZW5TU0wgR2VuZXJhdGVkIENlcnRpZmljYXRlMB0GA1UdDgQWBBTGCe/51LIS2ZT9nAj06RaAFcQa4jAfBgNVHSMEGDAWgBTH3T3aib5XZtlRccAInw7VjXJS0jAKBggqhkjOPQQDAgNJADBGAiEAjyic8z59ws8PvB2Q7apf69yFLM7ByICD8RBXxmz1WtUCIQChb2PYP5BzGRFxKV9ow9DesWt4bakIgdNFsUuT4NwMlQ==
We can split this up into three parts. All of them are base64. so the first part, from data= to &sign= can be translated to plain text, which gives us this json:
{"updateToken":"753D8AF000071ABC","deviceId":"59984EBACE92B7DBABD1350A98483C9C3E7162F31011494B46DAE6E822D2C48B","approvedVersionList":[{"versionId":"66711","status":"0","versionNumber":"MHA-L29C900B115"}]}
The sign= portion is a signature, and the cert= portion is an openssl certificate.
I have determined that all or part of the data= portion is signed with the certificate in the cert= portion. But I don't know in what shape the data is signed. If I convert everything and check with openssl, verification fails. I hope that someone can run some experiments and figure out exactly what it is in that data which is signed. If you can find this, I can help you get whatever version loaded you want.
By the way, here's what happens when we try to request B126:
Code:
data=eyJ1cGRhdGVUb2tlbiI6Ijc1M0Q4QUYwMDAwNzFBQkMiLCJkZXZpY2VJZCI6IjU5OTg0RUJBQ0U5MkI3REJBQkQxMzUwQTk4NDgzQzlDM0U3MTYyRjMxMDExNDk0QjQ2REFFNkU4MjJEMkM0OEIiLCJhcHByb3ZlZFZlcnNpb25MaXN0IjpbeyJ2ZXJzaW9uSWQiOiI2ODE2NSIsInN0YXR1cyI6IjEifV19&sign=MEUCIBrO1Y0ko3+fb12yXewessLbe3lfg5XPoPoqL30G5XMtAiEA9WniyB0vNRZWREk2vYT3Dfq9hPUJMNC8miAdlkULCe0=&cert=MIIDJzCCAsygAwIBAgIJALWcScNmfs+NMAoGCCqGSM49BAMCMIHXMQswCQYDVQQGEwJDTjEQMA4GA1UECAwHSmlhbmdzdTEQMA4GA1UEBwwHTmFuamluZzEsMCoGA1UECgwjSHVhd2VpIFNvZnR3YXJlIFRlY2hub2xvZ2llcyBDTy5MdGQxQTA/BgNVBAsMOERldmllIFJlZ2lvbiBEZWxpdmVyeSAmIFNlcnZpY2UgUXVhbGl0eSAmIE9wZXJhdGlvbiBEZXB0MRQwEgYDVQQDDAtPVEEgUm9vdCBDQTEdMBsGCSqGSIb3DQEJARYOb3RhQGh1YXdlaS5jb20wHhcNMTYwNzEyMDgxOTU5WhcNMTcwNzEyMDgxOTU5WjCB2zELMAkGA1UEBhMCQ04xEDAOBgNVBAgMB0ppYW5nc3UxEDAOBgNVBAcMB05hbmppbmcxLDAqBgNVBAoMI0h1YXdlaSBTb2Z0d2FyZSBUZWNobm9sb2dpZXMgQ08uTHRkMUEwPwYDVQQLDDhEZXZpZSBSZWdpb24gRGVsaXZlcnkgJiBTZXJ2aWNlIFF1YWxpdHkgJiBPcGVyYXRpb24gRGVwdDEYMBYGA1UEAwwPT1RBIEF1dGggU2VydmVyMR0wGwYJKoZIhvcNAQkBFg5vdGFAaHVhd2VpLmNvbTBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABGeDtAUO4uTY5yWwS54sk030WOdHYoaaO0dufn4jvul22Ytogvua1W0qY+ABblhA3eB49YXYPnpLvGhjr+73oZ6jezB5MAkGA1UdEwQCMAAwLAYJYIZIAYb4QgENBB8WHU9wZW5TU0wgR2VuZXJhdGVkIENlcnRpZmljYXRlMB0GA1UdDgQWBBTGCe/51LIS2ZT9nAj06RaAFcQa4jAfBgNVHSMEGDAWgBTH3T3aib5XZtlRccAInw7VjXJS0jAKBggqhkjOPQQDAgNJADBGAiEAjyic8z59ws8PvB2Q7apf69yFLM7ByICD8RBXxmz1WtUCIQChb2PYP5BzGRFxKV9ow9DesWt4bakIgdNFsUuT4NwMlQ==
The data portion translates to the following json:
{"updateToken":"753D8AF000071ABC","deviceId":"59984EBACE92B7DBABD1350A98483C9C3E7162F31011494B46DAE6E822D2C48B","approvedVersionList":[{"versionId":"68165","status":"1"}]}
You will notice that the status in the working update was 0. It also gave a version. In this case, we get status 1 and no version. Ergo, authentication fails and it will not install through eRecovery or HiSuite, while version B115 will.
So if you can find out what is signed and how, I might be able to re-sign this stuff and just provide/generate the certificate/key via my DNS server so that the installations no longer fail.
That is where I'm at. If anyone can crack the code, please post it here.
@duraaraa, just wanted to say you're a beast. Thanks for all your contribution and hard work thus far to the Mate 9 forum. I think I speak for everyone when I say we're lucky to have you here. I hope more developers start chiming in soon to help. I know it can be quite a task doing all of this by yourself, so we appreciate the time/effort you've spent for everyone. Cheers brother :highfive:
duraaraa said:
Ok, so. Here is what I have. I've been up all night, it's 7AM, and I'm tired, so I'm not going to be working on this any more until tomorrow. If any of you can find the solution to this, I can very likely let you flash whatever version you want onto your phone. This will be a long explanation, but if anyone is knowledgeable about openssl, they can help me hack at this.
Here is a response from a request to huawei's authorization server for B115, which can be flashed.
We can split this up into three parts. All of them are base64. so the first part, from data= to &sign= can be translated to plain text, which gives us this json:
{"updateToken":"753D8AF000071ABC","deviceId":"59984EBACE92B7DBABD1350A98483C9C3E7162F31011494B46DAE6E822D2C48B","approvedVersionList":[{"versionId":"66711","status":"0","versionNumber":"MHA-L29C900B115"}]}
The sign= portion is a signature, and the cert= portion is an openssl certificate.
I have determined that all or part of the data= portion is signed with the certificate in the cert= portion. But I don't know in what shape the data is signed. If I convert everything and check with openssl, verification fails. I hope that someone can run some experiments and figure out exactly what it is in that data which is signed. If you can find this, I can help you get whatever version loaded you want.
By the way, here's what happens when we try to request B126:
The data portion translates to the following json:
{"updateToken":"753D8AF000071ABC","deviceId":"59984EBACE92B7DBABD1350A98483C9C3E7162F31011494B46DAE6E822D2C48B","approvedVersionList":[{"versionId":"68165","status":"1"}]}
You will notice that the status in the working update was 0. It also gave a version. In this case, we get status 1 and no version. Ergo, authentication fails and it will not install through eRecovery or HiSuite, while version B115 will.
So if you can find out what is signed and how, I might be able to re-sign this stuff and just provide/generate the certificate/key via my DNS server so that the installations no longer fail.
That is where I'm at. If anyone can crack the code, please post it here.
Click to expand...
Click to collapse
Your help is much much appreciated.. I have friends expert in telecommunications security, will share this with them and see what they can do.. If they can..
Regardless, you are a big asset to all of us mate9 users.. Thank you again..
opasha said:
@duraaraa, just wanted to say you're a beast. Thanks for all your contribution and hard work thus far to the Mate 9 forum. I think I speak for everyone when I say we're lucky to have you here. I hope more developers start chiming in soon to help. I know it can be quite a task doing all of this by yourself, so we appreciate the time/effort you've spent for everyone. Cheers brother :highfive:
Click to expand...
Click to collapse
Thank you for that! I feel less like a beast and more like a slug right now to be honest!
duraaraa said:
Thank you for that! I feel less like a beast and more like a slug right now to be honest!
Click to expand...
Click to collapse
Haha, you're welcome, bro. To me, progress, no matter how slow, is still progress .
OK guys. Here is the final outcome.
Basically, updates are either approved by Huawei to be installed, or not approved.
B126 is actually a beta version, and it's only available to SOME IMEIs. I got a hold of someone who got the update and used his information to confirm.
Anyway, you will NOT be able to side load it. In order to install a regular update through eRecovery or HiSuite, the update must be authorized as an update which can be installed by Huawei. As of right now, the only non-Chinese update authorized to be installed by Huawei is B115. There are several Chinese updates which you could install on your phone, however, if modified correctly, but I don't think you would want to do this, as there are negative side effects.
So why do I declare it to be impossible? B126 is only installable as an OTA by people whose IMEIs are on Huawei's beta list. Here's how an OTA works.
1. The phone goes to query.hicloud.com to check for the version to get. (This step can be overridden by me, and I can make the phone find any version.)
2. The phone downloads the update and verifies that the files are correct. (This step also works fine.)
3. The phone then says it will restart to install in 10 seconds.
4. Right before the phone restarts to install, it connects over HTTPS to https://query.hicloud.com to confirm. Because it uses a certificate and I can't fudge the certificate, this is the step we cannot bypass. So the install stops here unless your IMEI is on Huawei's approved list, and the update is found to be invalid.
The only chance we will have at installing updates Huawei doesn't want us to install will be either unlocking the bootloader, rooting, or finding a way to install without any internet connectivity. I'm sorry to have to say this, but it's not going to happen this time
Below you will find a full list of the Mate 9 updates for which installs are allowed by Huawei.
65567 - MHA-AL00-all-cn:MHA-AL00C00B106;MHA-TL00-cmcc-cn:MHA-TL00C01B106;MHA-AL00-demo-cn:MHA-AL00C00B106
65569 - MHA-AL00-all-cn:MHA-AL00C00B109SP01;MHA-TL00-cmcc-cn:MHA-TL00C01B109SP01;MHA-AL00-demo-cn:MHA-AL00C00B109SP01
65571 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
65570 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
66546 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66549 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66711 - MHA-L29C900B115
67904 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
67986 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
duraaraa said:
OK guys. Here is the final outcome.
Basically, updates are either approved by Huawei to be installed, or not approved.
B126 is actually a beta version, and it's only available to SOME IMEIs. I got a hold of someone who got the update and used his information to confirm.
Anyway, you will NOT be able to side load it. In order to install a regular update through eRecovery or HiSuite, the update must be authorized as an update which can be installed by Huawei. As of right now, the only non-Chinese update authorized to be installed by Huawei is B115. There are several Chinese updates which you could install on your phone, however, if modified correctly, but I don't think you would want to do this, as there are negative side effects.
So why do I declare it to be impossible? B126 is only installable as an OTA by people whose IMEIs are on Huawei's beta list. Here's how an OTA works.
1. The phone goes to query.hicloud.com to check for the version to get. (This step can be overridden by me, and I can make the phone find any version.)
2. The phone downloads the update and verifies that the files are correct. (This step also works fine.)
3. The phone then says it will restart to install in 10 seconds.
4. Right before the phone restarts to install, it connects over HTTPS to https://query.hicloud.com to confirm. Because it uses a certificate and I can't fudge the certificate, this is the step we cannot bypass. So the install stops here unless your IMEI is on Huawei's approved list, and the update is found to be invalid.
The only chance we will have at installing updates Huawei doesn't want us to install will be either unlocking the bootloader, rooting, or finding a way to install without any internet connectivity. I'm sorry to have to say this, but it's not going to happen this time
Below you will find a full list of the Mate 9 updates for which installs are allowed by Huawei.
65567 - MHA-AL00-all-cn:MHA-AL00C00B106;MHA-TL00-cmcc-cn:MHA-TL00C01B106;MHA-AL00-demo-cn:MHA-AL00C00B106
65569 - MHA-AL00-all-cn:MHA-AL00C00B109SP01;MHA-TL00-cmcc-cn:MHA-TL00C01B109SP01;MHA-AL00-demo-cn:MHA-AL00C00B109SP01
65571 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
65570 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
66546 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66549 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66711 - MHA-L29C900B115
67904 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
67986 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
Click to expand...
Click to collapse
I agree with u about it being impossible, i even checked with my security experts friends, and they said " only by hacking Huawei servers Hahaha"..
But am so so so excited and waiting for this update, really the device needs the update badly to complete the experience, feels like i have the fastest horse ever, but am missing one of his legs..
I wonder how fast Huawei will roll out the final version.. Maybe those who have history with Huawei devices can tell, as am new to Huawei and ive always been a Samsung guy (not anymore with the impressive mate9)
duraaraa said:
...
Below you will find a full list of the Mate 9 updates for which installs are allowed by Huawei.
65567 - MHA-AL00-all-cn:MHA-AL00C00B106;MHA-TL00-cmcc-cn:MHA-TL00C01B106;MHA-AL00-demo-cn:MHA-AL00C00B106
65569 - MHA-AL00-all-cn:MHA-AL00C00B109SP01;MHA-TL00-cmcc-cn:MHA-TL00C01B109SP01;MHA-AL00-demo-cn:MHA-AL00C00B109SP01
65571 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
65570 - MHA-AL00-all-cn:MHA-AL00C00B115;MHA-TL00-cmcc-cn:MHA-TL00C01B115;MHA-AL00-demo-cn:MHA-AL00C00B115
66546 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66549 - MHA-AL00-all-cn:MHA-AL00C00B125;MHA-TL00-cmcc-cn:MHA-TL00C01B125;MHA-AL00-demo-cn:MHA-AL00C00B125
66711 - MHA-L29C900B115
67904 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
67986 - MHA-AL00-all-cn:MHA-AL00C00B135;MHA-TL00-cmcc-cn:MHA-TL00C01B135;MHA-AL00-demo-cn:MHA-AL00C00B135
Click to expand...
Click to collapse
Some people in the Netherlands that had MHA-L29C432B109SP2 also got the update to b126.
Not me unfortunately.
@duraaraa, did u changed the public key to any from an updated phone?
dkionline said:
@duraaraa, did u changed the public key to any from an updated phone?
Click to expand...
Click to collapse
Sorry, I don't understand your question.
I am on B110 with my C636 model. Nothing new yet
Sent from my FRD-L09 using Tapatalk
Hello,
As we know there are many H90021w firmware user found their phone is not working as it should be. There are some issues like fingerprint sensor is not working, cant uninstalling apps, etc. I found the only way to solve is by updating the firmware to 21z or 22b only. I've try to find in on the net throughly only to find after the v21w firmware, newer firmwares are stored in the AT&T server, not on the LG server anymore. And the only way to get the OTA is by using an AT&T simcard and in the US. This definitely a problem to those who live outside the US just like me.
And it's not possible to downgrade, trust me, maybe I've try everything that possible including taking out the emmc from the board, erasing everything and put the lollipop firmware in it. Simply not working. Mind you, when I put that emmc (lollipop) on another board (vs990 too) which were originally lollipop and never use the 21w firmware, it's working fine.
So basically updating to 21z or 22b is the only way. Also if there's any 21w user and the phone is normal, maybe you can help too.
All we need is to put the phone on qualcomm 9008 mode, copy some partitions, zip it and upload to somewhere. It's perfectly safe as I did it many many times to backup my phone and some friend's phones (v10 and G4). We'll exclude the imei partition and userdata, so it will be safe for you.
This method is also useful for other purposes. You can full backup your phone and restore it if theres anything happen. For those who have bootlooped phone, you can backup it and restore to another working phone and you'll have almost the same state of the phone. Of course the type of the phone should be identical and the arb is ok. If the arb is stil 0, you can even switch the carrier to Tmobile.
This could be used for many purposes, but let's get this one done first. If its working, I'll put it in a new "how to" thread so many will be helped. We can also arrange donations for those who help. We can discuss it by pm.
So hopefully someone can help and we can discuss on private message about the method in details.
Thank you
Nobody?
Hi all,
Probably my previous request were too much.
I found an easier and faster way to do it. No need to go to mode 9008 or modifying the cable.
All it need is LGup patched which can be found on https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 and a normal data cable.
If anybody willing to help, feel free to let me know.
Thank you
ardian1899 said:
Hi all,
Probably my previous request were too much.
I found an easier and faster way to do it. No need to go to mode 9008 or modifying the cable.
All it need is LGup patched which can be found on https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222 and a normal data cable.
If anybody willing to help, feel free to let me know.
Thank you
Click to expand...
Click to collapse
I hope you have news. I have the same problem without solution so far.
Nope. Although still hoping to find someone eager to help, I think this H900 section is practically dead.
ardian1899 said:
Nope. Although still hoping to find someone eager to help, I think this H900 section is practically dead.
Click to expand...
Click to collapse
Hey, sorry, didn't see this post, but if you still need the firmware, I'm willing to help you out Im pretty sure I got 22b running
Theamerix said:
Hey, sorry, didn't see this post, but if you still need the firmware, I'm willing to help you out Im pretty sure I got 22b running
Click to expand...
Click to collapse
Wow awesome, thank you!
I already got 21z by myself and planning to ask a few $$ from others since no one helping since months ago. But with your help we can help others too. I'll send a pm later today with some instruction, need to back home first and recheck the method.
Thanks again.
ardian1899 said:
Wow awesome, thank you!
I already got 21z by myself and planning to ask a few $$ from others since no one helping since months ago. But with your help we can help others too. I'll send a pm later today with some instruction, need to back home first and recheck the method.
Thanks again.
Click to expand...
Click to collapse
Yeah I'll need some instructions, its been a long time since I last used LGUP or anything similar... ^^
Now, I just checked, I am running H90022b, but I'm not entirely sure whether this would solve your problem.
I have an LG V10, AT&T locked, but with a verizon motherboard... This means that in my case, some security options don't work, I can't update, can't use a fingerprint sensor and worst of all, I can't deinstall apps. (I'm never buying refurbished devices again ^^)
However, if you have a normal V10 (H900), this should be no problem. The software is still the same, its flashed as a H900, whilst it should be a H901 I think.
Theamerix said:
Yeah I'll need some instructions, its been a long time since I last used LGUP or anything similar... ^^
Now, I just checked, I am running H90022b, but I'm not entirely sure whether this would solve your problem.
I have an LG V10, AT&T locked, but with a verizon motherboard... This means that in my case, some security options don't work, I can't update, can't use a fingerprint sensor and worst of all, I can't deinstall apps. (I'm never buying refurbished devices again ^^)
However, if you have a normal V10 (H900), this should be no problem. The software is still the same, its flashed as a H900, whilst it should be a H901 I think.
Click to expand...
Click to collapse
Hello,
Sorry I just be able to reply.
So basically you cant uninstall app too?
lv v10 h90022b issues
I have 2 identical lg v10 h90022b phones. One works perfectly without any issues but the other one had issues exactly the same issues your phone have.
I'm not a android geek. Can you guide me step by step how to put the good phone into Qualcomm 9008 mode then copy its patition to fix the phone that had issues.
Thanks
[email protected] said:
I have 2 identical lg v10 h90022b phones. One works perfectly without any issues but the other one had issues exactly the same issues your phone have.
I'm not a android geek. Can you guide me step by step how to put the good phone into Qualcomm 9008 mode then copy its patition to fix the phone that had issues.
Thanks
Click to expand...
Click to collapse
were you able to solve your problem, I had a bricked h901 tmobile, which i flashe to at&t h900 , now fingerprint , uninstalling apps doesnt work, so looking for a way out of this mess, I didnt know before buying from some other guy that it was arefurb aliexpress mobile with korean boartd, after flashing i cant even make a call, says radio off, can anyone help?
Hi everyone, I need some help if possible!
The situation : I have a huawei P40 ANA-NX9. I successfully install gms, makes updates, then have a problem with my google account wich force my to change my password. GMS was not working and see that I have to downgrade firmware to reinstall gms.
I follow this good tutorial : https://www.youtube.com/watch?v=c1M4amoGvtA&t=74s&ab_channel=SystemHacks
I can't find any "approuved" firmware as I have this one : ANA-LGRP4-OVS 10.1.0.182
So I try to install ANA-LGRP4-OVS1B116-log (11.0.0.116) and now my phone don't boot, it show EMUI recovery. :crying:
I try to full reset, wipe cache, nothing work.
I try to re-install via usb-otg firmwares from here : https://androidhost.ru/search.html searching for "ANA-n29" none of the 3 work
I try to recover with hisuite, don't work.
Maybe someone know better how to restore the phone, with or without gms just make it work.
Maybe someone know that the phone is bricked forever so I can stop trying and trying...
thanks a lot !
JB
Hi i ever read somewhere before about this happening to one of the p40 pro user, something when wrong after he downgraded his phone, his imei shows null making the phone hangs at recovery page or keeps on bootlooping every 30sec to 2mins. (there's no other way to fix this ATM, only to try luck by bringing it to service center to fix it, if your phone is still covered by warranty)
jb_82 said:
Hi everyone, I need some help if possible!
The situation : I have a huawei P40 ANA-NX9. I successfully install gms, makes updates, then have a problem with my google account wich force my to change my password. GMS was not working and see that I have to downgrade firmware to reinstall gms.
I follow this good tutorial : https://www.youtube.com/watch?v=c1M4amoGvtA&t=74s&ab_channel=SystemHacks
I can't find any "approuved" firmware as I have this one : ANA-LGRP4-OVS 10.1.0.182
So I try to install ANA-LGRP4-OVS1B116-log (11.0.0.116) and now my phone don't boot, it show EMUI recovery. :crying:
I try to full reset, wipe cache, nothing work.
I try to re-install via usb-otg firmwares from here : https://androidhost.ru/search.html searching for "ANA-n29" none of the 3 work
I try to recover with hisuite, don't work.
Maybe someone know better how to restore the phone, with or without gms just make it work.
Maybe someone know that the phone is bricked forever so I can stop trying and trying...
thanks a lot !
JB
Click to expand...
Click to collapse
Did you find a solution to this? I`m trying to downgrade my ANA-LGRP4 aswell
mrteyssere said:
Did you find a solution to this? I`m trying to downgrade my ANA-LGRP4 aswell
Click to expand...
Click to collapse
Hi,
No, still bricked.
I think the problem is I update with emui 11 and it don't want to downgrade to 10.
My only hope for now, is the release of emui 11 on the huawei P40 so maybe I will be abble to use the hisuite recovery.
https://www.huaweiupdate.com/huawei-emui-11-official-roadmap-released-for-all-countries/
Seems like it will be released on December...
jb_82 said:
Hi,
No, still bricked.
I think the problem is I update with emui 11 and it don't want to downgrade to 10.
My only hope for now, is the release of emui 11 on the huawei P40 so maybe I will be abble to use the hisuite recovery.
https://www.huaweiupdate.com/huawei-emui-11-official-roadmap-released-for-all-countries/
Seems like it will be released on December...
Click to expand...
Click to collapse
how did you even get that firmware to flash? i have literally the same model and my phone tells me that its incompatible .
ooh and to fix your phone is easy, just use the eRecovery option (done by holding up and power until the huawei boot sign comes on, then select update mode, followed be eRecovery.)
Lizzo said:
how did you even get that firmware to flash? i have literally the same model and my phone tells me that its incompatible .
ooh and to fix your phone is easy, just use the eRecovery option (done by holding up and power until the huawei boot sign comes on, then select update mode, followed be eRecovery.)
Click to expand...
Click to collapse
Hi,
I flash it with Hisuite & a proxy. It show an alert like "are you sure?" and I click "yes" ...
Thanks for helping, I already try the erecovery but It does not work.
I try "update & recover system" with wifi, it show : "retrieving package information..." > Get package info failed
And I try Factory reset, it goes from 0 to 100 % , then I click wipe cache, it restart, show huawei logo and show erecovery again, i click restart > show huawei logo > ... > erecovery again ...
I'm stuck on erecovery, it never start..
Do you test the dload method?
i think dload will work , but we need to have god firmware , im the same situation. ;(
Hi guys, anyone found any solution? I f..ed my phone today. I dont know where to download fw from, nothing worked, flash from USB didnt work, nothing works. Unbelievable,even Sony offers a recovery option.
I have the same problem.
Spend already a week and haven't found a solution.
I believe that SigmaKey or Chimera software can help with it but it needs to be checked.
i installed the wrong version (els-lgrp4-ovs) instead of (els-lgrp6-ovs)..FFFuu.. its bricked. keeps on restarting. if anyone knows how to fix it, let me know.
Now it seems i have to call the after sales...
grand_deluxe said:
i installed the wrong version (els-lgrp4-ovs) instead of (els-lgrp6-ovs)..FFFuu.. its bricked. keeps on restarting. if anyone knows how to fix it, let me know.
Now it seems i have to call the after sales...
Click to expand...
Click to collapse
Me too, I'm waiting for Solutions.
jb_82 said:
Hi,
I flash it with Hisuite & a proxy. It show an alert like "are you sure?" and I click "yes" ...
Thanks for helping, I already try the erecovery but It does not work.
I try "update & recover system" with wifi, it show : "retrieving package information..." > Get package info failed
And I try Factory reset, it goes from 0 to 100 % , then I click wipe cache, it restart, show huawei logo and show erecovery again, i click restart > show huawei logo > ... > erecovery again ...
I'm stuck on erecovery, it never start..
Click to expand...
Click to collapse
My Situation. Waiting for Solutions
Try this original rom. I have made my downgrade with this rom.
It's for ANA-NX9 like yours.
Huawei P40 ANA-NX9 ANA-N29 hw eu HLRCF Anna-N29CB 10.1.0.114(C432E6R5P2) Firmware EMUI10.1.0 05016PSQ_By(www.dztechphone.com).zip | by DzTechphone for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Put dload on a pen and try to recovery update with it.
Guys I failed my downgrade and now my phone is dead as in muerto! It cannot even go to Bootloader nor Fastboot. Only Someone with Sigmakey or simillar and a lot of experience can help now, if its possible to help me in general
Did you all find a solution for this? Also, just curious, why would you want to try to downgrade the software?
I have the same problem with a p40 lite JNY-LX1 after I used OTG to downgrade phone went into bricked mode, any useful tips will be much appreciated to help remedy this situation
Phone firmware was on 10.1.0.338 or 335 not sure but that version I'm reading multiple posts about test point mode not working after July patch I'm hoping someone smart out there will have the skills to bring this dead junk back to life at some point in time
Exactly the same problem here. Today my p40 lite JNY-LX1 bricked after I tried to downgrade from 10.1.0.336 to an earliest version.Let's hope a solution will be available any time soon
​
I took my device back to store and lied to them about having wifi problems when I was updating it so they gave me a new device after a week