[Q] Mango update issues (omnia 7) - Windows Phone 7 Q&A, Help & Troubleshooting

I was pretty excited to see the Mango update is now available for the masses.. I mean those of us who don't have our devices unlocked as a developer phone so I decided to try my hands on it. But now I have some issues. When I open ZUNE I see update is available.
It tries to update but than after rebooting and finishing step 2/2: ERROR Code 80180048. apppers
I tried this several times on Win7 X64 and x86 but I still have the same problem.
Any ideas? maybe am getting something wrong

you need to download a beta copy of zune (4.8) google it my friend

rlatarche said:
you need to download a beta copy of zune (4.8) google it my friend
Click to expand...
Click to collapse
I tried but didn't help

This could be happening for 2 reasons... Apparently your phone is getting confused by which update to download.
1) Did you unlock at any point with Chevron? If so you probably didn't check off all the languages. If this is the problem just look for the Microsoft approved walsh fix, very easy to find.
Then restore your phone to the version before it was provisioned for mango and apply the walsh fix. VERY IMPORTANT CHECK OFF EVERY LANGUAGE. Then restart the mango process and people have posted that this should work.
2) If, like me, your a registered developer and still getting this error then unfortunately I've only been able to find 1 fix. Microsoft is working on correcting the problem but has said it will take a couple weeks. So on to the fun part. You need to flash your phone back to factory form. Flash not reset. You lose everything. Good this is your purchase history, contacts and calendar should be attached to your live id, if not you might want to sync them.
To flash your rom just search these wonderful forums to find it. All I searched for was "flash focus rom" and found a thread with the files and instructions were in the files. Once your phone has been flash you should have no problem updating to mango although you have to go through all the original updates and re install and set up your phone.
Hope this helps... it worked for me.

mrcrazy11 said:
This could be happening for 2 reasons... Apparently your phone is getting confused by which update to download.
1) Did you unlock at any point with Chevron? If so you probably didn't check off all the languages. If this is the problem just look for the Microsoft approved walsh fix, very easy to find.
Then restore your phone to the version before it was provisioned for mango and apply the walsh fix. VERY IMPORTANT CHECK OFF EVERY LANGUAGE. Then restart the mango process and people have posted that this should work.
2) If, like me, your a registered developer and still getting this error then unfortunately I've only been able to find 1 fix. Microsoft is working on correcting the problem but has said it will take a couple weeks. So on to the fun part. You need to flash your phone back to factory form. Flash not reset. You lose everything. Good this is your purchase history, contacts and calendar should be attached to your live id, if not you might want to sync them.
To flash your rom just search these wonderful forums to find it. All I searched for was "flash focus rom" and found a thread with the files and instructions were in the files. Once your phone has been flash you should have no problem updating to mango although you have to go through all the original updates and re install and set up your phone.
Hope this helps... it worked for me.
Click to expand...
Click to collapse
Thanks for reaching out to help me but I think I will give up now. I did all what you told me.. I read from other places even before you responded but it still didn't work. Am thinking its a problem with my Samsung Omnia phone so I guess I have to wait till the Final release of mango comes out. I had also the same issue with NoDo, I had to wait till the official Samsung fix came before I could finally get it.. guess this is like that too.

Sorry I couldn't help more. I have an unlocked ATT Focus running on Rogers... I was able to flash an Omnia 7 ROM on it but that was horrible because the phone literally began to mix the up and down and the portrait and landscape modes.
Did you try and flash your omnia back to stock?

I couldn't return back to the the stock ROM. My boot-loader is probably damaged . When I press the the volume up + and camera button to enter into download mode all I see is the black and white screen ..

Related

[Q] samsung fasinate - bricked my phone - verizon tecs clueless

Hi, I am new to all of this, but Im a quick learner. I rooted my phone and have superuser permission. I have installed multiple applications that will help me to perform ROM installs all of which still do not help. I even tried the three button solution, however I am still getting the same message when I go into recovery mode. It is as follows: E: failed to varify whole-file signature then under that I get: E: signature verification failed, instalation aborted.
I tried applying sdcard update. zip, wiped out cache partition, factory reset, etc...
I have tried everything. I tried using Mod Manager, I get the downloads but then when i try to install after I make sure to click backup rom and clear cache, it boots to the rom screen, (not really sure what you guys call it, sorry) and I get that same message, the signature failed, et...
my phone info is as follows: SCH-I500, I500 Commercial Package_DL9 To EA28 (I think verizon automaticly updated for the emergency dial) code 200
hardware version i500.04 firmware version 2.1update.1, baseband version S:i500.04 V.EA28, kernel version 2.6.29 and last but not least build number SCH-I500.EA28
Now saying all of that, I tried all of the above steps prior to this automatic update and it still did not work. I still received the signature message.
I even tried Voodoo, as well as DL30, Superclean, none of which will pass the signature autentacation. I want to try to get past this as I am having my phone replaced due to burn in and want to get the steps right so I do not BRICK my phone after it has been replaced. If this one bricks, it wont matter to much because I will have the new one on Monday.
Any help would be greatly appreciated. I love this tecky stuff and want to be knowagable on how to get past this message so I can go full force on Monday.
Thanks,
EssyG
Also I checked the site and tried everything but still won't work.
Sent from my SCH-I500 using XDA App
You will need to flash a new Recovery via ODIN which you can find below for your Samsung Fascinate:
http://forum.xda-developers.com/showthread.php?t=782204
&
Also read this http://forum.xda-developers.com/showthread.php?t=790004
Thank you, up and running 2.2, will post screen latter! Now I need to get my old phone back to stock so I can send it back to veriazon. YOU ARE THE BEST!!
P.S. I love your idea about the 10 post allowence to post on other forums.
Essy G
If o.k. I will post what I did and that way new users will be able to follow directions. I am a newbe but have become addicted to this stuff. THANKS!!
now I bricked my phone... lol
Now let me start by saying I loved 2.2, no problems with it at all. but when battery ran out I wanted to clean stats in cwm green and the screen would not come up, sd would not mount any how I tried to start over, flashing oden, all the steps, but my drivers will not stay for some reason after flashing I need to uninstall the reinstall drivers or they are not recognized, really sucks, any how I got frustrated so while in odin I pulled the plug, lol literally, and now have a pic of a "phone" then ".." then triangle with (like my icon here)"!" then ".." picture of "computer". I called verizon and there sending me yet another phone. lol my question is, will they be able to unlock it and see that I had 2.2 on it? does anyone know what they do with the phones we send back? Basicly I want to know if they can unlock that being I can't. and if so, will they see the 2.2? Any sugestions?
Anyone there?
Any one there? Also I am debating, do I wait for official release. I heard it was coming out 2/22/11. If I put dl30 on new phone again and they release the update, will I still get the automatic update via verizon? If so will I lose root? Any comments on post #5? I can't believe I had it running I totally messed it up. Thank goodness when I called verizon I got two girls at tec support, lol while I am a girl, I am a tech lover, I acted like I had no idea what happened, well they didn't either, lol So just waiting on new phone to come in, yet again so I am getting everything ready to quickly install dl30 to new phone again. Hopefully I do not lose drivers again, as it seems that once I flash in odin, the hardware icon disappers as if drivers are not installed. any how, I was just wondering if anyone had an answer to post #5 so that when I return the phone, I am not caught, lol that would really stink! Plus I am board, took off of work because my kids are sick and now I have a bad cold also, so any comments would be great!! Besides I need to be here to sign for new phone.
Thanks,
Essy g

Focus i917 AT&T USA UCKC3 ROM

Hello,
so you was waiting so long for this? there it is - first ROM for Focus
March 2011 release!!
Enjoy it
Samsung-i917-Focus-firmware-UCKC3-ATT-USA
i did not test it personally, so you take your personal risk
Happy Flashing
is hardspl needed?
has anyone used this? is it working? I am about to do it right now and I will let you know with the results..
Please report back.
carmello1911 said:
has anyone used this? is it working? I am about to do it right now and I will let you know with the results..
Click to expand...
Click to collapse
I tried this in my Focus but it doesn't work. I got the following message on the attached screenshot.. any ideas on this? it seems that the installer doesn't recognise my device as a Samsung Focus therefore it doesn't continue with the flashing procedure..
PavelX1 said:
Hello,
so you was waiting so long for this? there it is - first ROM for Focus
March 2011 release!!
Enjoy it
Samsung-i917-Focus-firmware-UCKC3-ATT-USA
i did not test it personally, so you take your personal risk
Happy Flashing
Click to expand...
Click to collapse
March 2011 so that means nodo?
carmello1911 said:
I tried this in my Focus but it doesn't work. I got the following message on the attached screenshot.. any ideas on this? it seems that the installer doesn't recognise my device as a Samsung Focus therefore it doesn't continue with the flashing procedure..
Click to expand...
Click to collapse
There are two versions of I8700 (Omnia 7) firmwares
one for Retail Devices that are signed by "WP7_PRODUCT" and one for Developer Devices - signed by "WP7_ENGINEER"
For Focus me dont have any "WP7_PRODUCT" signed firmwares, so i am not sure if that one me put online today (signed by "WP7_ENGINEER") are suitable for Retail Phones that AT&T sells.
So its about to check all and get the best from this....its better to have something that nothing (some people will be VERY happy to see even maybe not flashable ROM)...
where did you find this ROM? do you have the other one also?!
He already said he doesn't have the WP7_PRODUCT release.
BTW, thanks, if this is the real thing it will make a lot of people happy!
you are right.. excuse me.. do you think is possible to alter or tweak few things on this one and make it workable to the retail devices as well?
The rom loader appears to be for a different phone. I tried using the demo mode rom loader to load these rom files, as each tmp file corresponded with one of these rom files, but when i replaced the demo rom files with the legitimate rom files it would not move forward with the flash. Perhaps someone will figure it out.
cmmsex1i said:
Thanks but did not work, Its not the Retail Rom wish if u could find one. Thanks again
Click to expand...
Click to collapse
How can you say the rom is not retail... the loader surely is not, as it is looking for an SPH-i350 when it should be looking for the focus (SPH-i917)
If I was a little better with ollydbg id already have a solution but I am not very good with disassembly.
the rom is clearly not retail, but it is for this phone, and i would not mind testing it, as i do not use my focus for service right now, just my epic 4g
so probably what we need is someone to change the loader? could be a good idea to post this thread in a less specific forum as maybe someone should be able to do that..
carmello1911 said:
I tried this in my Focus but it doesn't work. I got the following message on the attached screenshot.. any ideas on this? it seems that the installer doesn't recognise my device as a Samsung Focus therefore it doesn't continue with the flashing procedure..
Click to expand...
Click to collapse
the same error
M dying to get Samsung Focus ROm
Guys my problem is I have a samsung focus which was unlocked with a code. i was on 7004 and i used Chevron Updater to update it by mistake I chose UK instead of US and now though the Phone has got the NODO update and works well but I can't open few applications like Phone(call), Text, Email etc and those applications are just crashing the moment i click them.
and worst thing is I can't connect it to ZUNE because the initial setup can't be completed (the setup of accepting terms and opening LIVE ID) and the ZUNE says that "PHONE SETUP INCOMPLETE"
Plese let me know if there is any way to connect the phone to zune so that i can update it through zune
first of all please read the rules, secondly, do not double or cross post ( this is the same with most forum), and lastly post in the right thread.
back to the subject, apart from this rom, has there been a non branded rom available, the last time i was gonna buy a i917 from expansys hk, i did remember that the phone boot up without the at&t logo, does this mean the f/w is non branded or simply the logo was just removed.
No there is no Samsung FOcus Rom (Retail) available on net!!!!!!!!!!
I can confirm that this rom does in fact work. Not all devices are recognised (I suspect the update tool looks for a developer device). But on a recognised device that I tested, this worked flawlessly and successfully reflashed the device to 7.0.7390.0
For those that want to force the rom to your phone, you may want to try the command line "UpdateWP" found under Program Files\Zune. Note, I haven't tested this method.
what application did u use to flash the focus as the one with it reports error..
Anyway thanks for hopes
dvorak123 said:
I can confirm that this rom does in fact work. Not all devices are recognised (I suspect the update tool looks for a developer device). But on a recognised device that I tested, this worked flawlessly and successfully reflashed the device to 7.0.7390.0
For those that want to force the rom to your phone, you may want to try the command line "UpdateWP" found under Program Files\Zune. Note, I haven't tested this method.
Click to expand...
Click to collapse
Are you saying you used the attachment in the beginning of this thread to flash a samsung focus of yours? And if that is what I am to believe, was this phone to your knowledge a special model, or a model meant to be used as a dev device?

[Q] "Sorry I'm Having Trouble Communicating..."

So I've been trying to unlock my Samsung Focus with ChevronWP7. I have followed >>this<< guide, step by step, but after I click both boxes and click on "Unlock", I get "Sorry, I'm having trouble communicating with the phone. Please make sure it's connected using USB. Please start the Zune application." So then I tried another guide(can't find the link right now), which included disabling the network, using WPConnect.exe, etc, but that didn't work either. I am completely at a loss of why this damn error keeps popping up. I restarted both my PC and phone numerous times, I've tried different USB ports and cables, but nothing is working. Anyone have any tips?
My OS version is 7.0.7390.0, Firmware Revision is 2103.11.3.3 and Zune version is 4.7.1404.0 if that helps at all.
Thank you, maxx.
I had same problem and I used the guide below and it worked on the first try. Most importantly was STEP 2 for me. Uninstalling Zune and using the version from the link provided in the guide at step 2.
[Tutorial] Unlock your phone; prevent relock & prepare for updates!
Well damn, it says my firmware isn't compatible with CWP7. I guess that and my Zune version is why it doesn't work. Is it possible to revert back to a previous firmware version?
try to downgrade to previous version (if possible) from zune.
If your phone came with NoDo (7392 or 7390) installed the only way to unlock at the moment is to flash a previous firmware version. Check the forums if there is one for your provider and phone.
If i'm not wrong you can checkwith Ansar's rom.
Have you resolved the problem yet? It seems there is something wrong with the "hosts" file. Generally, this file is in folder "C:\windows\system32\drivers\etc". Open it, delete all lines like "192.168.1.101 developerservices.windowsphone.com". Then, save it, try ChevronWP7 again in admin permission, it should be OK. If still not works, please send email to me, [email protected].
maxxdout said:
So I've been trying to unlock my Samsung Focus with ChevronWP7. I have followed >>this<< guide, step by step, but after I click both boxes and click on "Unlock", I get "Sorry, I'm having trouble communicating with the phone. Please make sure it's connected using USB. Please start the Zune application." So then I tried another guide(can't find the link right now), which included disabling the network, using WPConnect.exe, etc, but that didn't work either. I am completely at a loss of why this damn error keeps popping up. I restarted both my PC and phone numerous times, I've tried different USB ports and cables, but nothing is working. Anyone have any tips?
My OS version is 7.0.7390.0, Firmware Revision is 2103.11.3.3 and Zune version is 4.7.1404.0 if that helps at all.
Thank you, maxx.
Click to expand...
Click to collapse
maxx,
Chevron WP7 DOES NOT work with 7390 and above. As you have found out, the only option is to downgrade the firmware to an older version and then unlocking it. I tried searching and was not able to find it ( or I did not know what the hell I was looking for, HTC HD7 user here )
If your Focus came with a older version and you updated using Zune, you can try restoring
Open Zune--> Settings-->Phone-->Updates-->Restore
Try posting in the Samsung Focus forum. You might get some help.Good luck...

cannot get to 7712 on my Samsung Focus

Hi all,
I have tried following these two methods to try and get to 7220, but I always get stuck on firmware 7304->7112 (first, second). Thereby, never actually getting to 7112.
Every time I go through the update procedure to 7112, it progresses half way, then it stops and reboots my phone with the error 80004005. I have tried:
clean NoDo install, and re-trying
removing the SD card
doing a hard reset on the phone
No matter what I try, the same thing happens when trying to get to 7112. How did other Samsung Focus users get to 7112?
This could be related to your version of Zune. The support tools and Zune must be on the same version.
You may have to reinstall the beta version of Zune 4.8 to make this work.
I can't remember the error code I received, but this is how I sorted it.
There is a post somewhere else that explains how to do it.
hedpe said:
Hi all,
I have tried following these two methods to try and get to 7220, but I always get stuck on firmware 7304->7112 (first, second). Thereby, never actually getting to 7112.
Every time I go through the update procedure to 7112, it progresses half way, then it stops and reboots my phone with the error 80004005. I have tried:
clean NoDo install, and re-trying
removing the SD card
doing a hard reset on the phone
No matter what I try, the same thing happens when trying to get to 7112. How did other Samsung Focus users get to 7112?
Click to expand...
Click to collapse
Give the guide in this thread a go http://forum.xda-developers.com/showthread.php?t=1101344 also if you have any issues read through this thread as all issues encountered have been addressed with relevant resolutions http://forum.xda-developers.com/showthread.php?t=1215501
Hope this helps,
Creamy
creamy said:
Give the guide in this thread a go http://forum.xda-developers.com/showthread.php?t=1101344 also if you have any issues read through this thread as all issues encountered have been addressed with relevant resolutions http://forum.xda-developers.com/showthread.php?t=1215501
Hope this helps,
Creamy
Click to expand...
Click to collapse
thanks for your response. It seems like I need to unlock my phone first. What is the current defacto unlock method? Is it still Chevron?
Flash you Samsung Focus with this ROM and try the update again.
http://forum.xda-developers.com/showthread.php?t=1131022
day2die said:
Flash you Samsung Focus with this ROM and try the update again.
http://forum.xda-developers.com/showthread.php?t=1131022
Click to expand...
Click to collapse
thanks for the suggestion. I thought of doing this, but having trouble flashing the ROM:
http://forum.xda-developers.com/showpost.php?p=17315234&postcount=107

Bootloader Unlocking through Downgrade possible?

Hello Guys,
i had bought an Huawei P20 about an year ago. Now you know with all of this "USA-Huawei" Trouble going on, the thought came to my mind that i better start unlocking bootloader and be prepared to flash custom rom if worst come to worst. so far, so good.
now i started looking around if there is an easy method of getting the bootloader unlocked. but oh my, the huawei company is very friendly to us users and say "no, you wont get any unlock code from us anymore". so screw that.
now i want to try some experimental stuff. it looks like this:
my Smartphone has currently the version EML-L29 8.1.0.168(C432). I bought some Credits (i think it is that thing for $4) from DC-Unlocker. Yeah yeah i know, there they say "no support for Huawei P20!!!". But i still want to try. Well i tried, but it doesnt work - what you should expect.
now i read from some other website that there is another way of unlocking it. i only read it diagonal but the one thing i read was the information "unlocking bootloader is only possible till firmware version june 2018". so i jumped to an maaybe interesting conclusion about unlocking the phone with DC-Unlocker or HCU (whatever, i guess maybe both use the same method anyway).
if i do an rollback to the old firmware version *before* June 2018 on the device, wouldnt it be possible to do the unlock? Because the security patches that preventing it unlocked arent on the device then.
So what i have done so far is loading the old firmware version 8.1.0.128(C432). But the source is saying that it is coming from "Asia" but in the next line it reads "Asia, Europe" etc. - do they mean that this version is universal or do i run in trouble if i install one that is having the wrong area?
the next thing that kinda baffles me... all guides are sayin "copy the extracted dload folder to your sd-card". even the p20 guides do that. but.. well you know, the p20 device doesnt even have sd-card support. so how are you intended to use it then? i wonder about that a bit.
i dont think that without unlocked bootloader, flashing an original OTA full update would be impossible. but im not really sure how. there is this shady menu you can reach if you call this strange numbercode. but im very unsure if that will really work out. the phone (it is still a phone without SD-Card-Support) even has the option "apply update from sd-card". so im wondering how this feature they implemented in the original software is intended to use at all. maybe i should push the dload folder on the internal storage? i dunno.
i read about another possibilty of flashing stock roms. they say you can do it per adb command. so no problems would be here, i have adb and the hisuite and all already set. but i have absolutely no idea if that is possible without unlocked bootloader. so the questions arose from my mind are those:
- does an stock rom image from possibly/maybe asia would do any harm to my device like it is getting unbootable or anything like that?
- is it possible to flash an image older android stock rom with methods like this special menu on the device or the adb load?
- do you all think that my plan of downgrading the phone in order to get the bootloader code would work?
i'm looking very forward to your answers )
no_monday said:
Bootloader Unlocking through Downgrade possible?
Click to expand...
Click to collapse
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Jan Philipp said:
No. Sorry. There's no solution. Reason: It would appear in this forum within minutes and thousands of people would be happy to unlock their bootloaders. Many Huawei-Owners here on XDA invested a lot of brain power to find a way. Noone succeeded. No bootloader code, no unlock.
If you still want to play around with firmwares, please inform us about any progress.
Click to expand...
Click to collapse
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
no_monday said:
okay so there are basically no real information. look, i dont expect anyone to say like "oh there is an easy method xy" because i know it doesnt exist on this moment in time.
however i made an percent of an progress, it is more a thing for other interested custom rom modders out there.
i downloaded this update.zip and there are all kinds of howtos on the internet about it. the one thing i did is basically create the dload folder. then i put the extracted update.app in there. i rebooted the phone with power, vol down + vol up. i released the power button after the vibrating. the flashing screen indeed appeared! but something very strange has happened and i have no explanation what have happend.
so the emui updater appeared. there was this emui logo in the middle, the circle building up around it. but then it stopped at 5%. i really got panicked that im about to brick my device. so in an mad attempt i wanted to stop the update and power off the phone. glad i didnt do it. the phone always said if i tried to press the power button long enough "the system will crash if it is powered down". i stopped - but i tried it serveral times to stop.
now the strange thing is.. it stuck relatively long on this screen. but after a while (i guess it was 5-6 minutes) it suddenly got dark. and the battery was at 100%, so it wasnt a faulty battery. i just wondered. the phone - other than i would expect - rebooted. after a short while of the logo flashing (for about an half minute) it finally started. first i didnt have any connect to GSM Network. but after a short while that was okay too. all apps are still there. i looked at "about" and the version is still the same as before.
do someone have any imagination what has happened there? so apparently the phone *does* try to install something on this method, but the method seemed to fail. or is there any knowledge out yet for update logs that are getting generated by this process? i try to find any hint in order to tackle this problem atm.
and one thing is still on my mind.. could it be that the update is already through and i just didnt realized it yet because these other custom files werent changed? i mean that could be an possibility to say the least. anyway, i will try to use hcu now if maybe sth has changed. and i give kingoroot as well a shot if this buddy finds everything about rooting the device. maybe with root rights through exploit i can get further.
Click to expand...
Click to collapse
It seems you have a couple of questions, pal, I answered to the first one (Bootloader Unlocking through Downgrade possible?). All I said is that it's impossible to unlock the bootloader through a downgrade. If you read all the how-to's you should have noticed that FirmwareFinder doesn'st work anymore since EMUI 9.0. This Information simply means Huawei doesn't allow us to flash updates on our own anymore like we did before. For sure there are some guides how to rollback to Android 8 but even this changes nothing to the bootloader.
Sadly I have no answer to the other questions about the strange behavior, it sounds pretty odd. Never heared something like this. But good luck fixing your phone anyway.
well i found out a couple of things now.
first thing: you know the service menu when you try to apply a zip archive from sd card? well you wont be able to use it UNTIL you use an usb-otg cable and an exFat formatted USB-Stick. Next thing to know is, you have to use the right images. there seem to be an kind of rule how this images are supposed to be and the image i found was from an russian firmware download site it was linked here in the forum in a thread. so i did choose "apply zip from sdcard" and .. IT DOES! the device rebooted, the stick flashed and the flashing process occured! and guys, im back to Version EML-L29 8.1.0.128(C432)! it is clearly stated in the build version view in settings. so.. i guess you *can* roll back even without firmware updater.
so far so good. but lets get back to the problem with the Bootloader. sadly Jan Philipp was totally right.. the bootloader cant be unlocked even in this version with the security patch of 5. may 2018. that is kinda sad. even kingoroot is still no different from before. i guess i have to search now for an way to get the system rooted. however, it must be easier on an earlier security update stage like now instead of the future versions of emui 8.1.
edit: another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
"unlocking bootloader with exploit is only possible till firmware version june/july 2018" does not apply to 2018's devices with kirin970, kirin980 & kirin710.
You are with kirin970.
So to unlock your kirin970, the only way for now is to wait for 3rd party seller to hypotheticaly start back their dervice:
- In the last 6 months there was only 2 'windows' which lasted 3 or 4 days where you could order your bootloader's unlock code by imei (from 5 to 124 us$).
GuestD0711 said:
another strange thing i discovered so far is that after this restore.. the play store wasnt able to connect to the google server until i gave permission to a few google processes to calendar and file access (i wonder what that is all about). maybe it has something to do with incompatibilities in the rom versions but now it works just fine as it should).
Click to expand...
Click to collapse
Google Play services require all permissions, otherwise won't work.
I also been searching on how to unlock the bootloader and found no solution or hope. I guess we are stuck with EMUI forever.
Reply from Huawei:
You can roll back to earlier versions of EMUI software, but you have to roll back one version at a time. However, our earlier phones operate exclusively on Google Mobile Services so removing it would limit the functionality extremely, however, we do have a range of new devices that no longer rely on Google Mobile Services and use Huawei Mobile Services instead - such as our P40 series.
Here are the instructions for rolling back software:
[Rollback Guideline] EMUI 9.1 (Android 9) Rollback to EMUI 9.0 (Android 9) Operation Instruction
EMUI 9.1 (Android 9) can now be rolled back to the official version of EMUI 9.0 (Android 9) using HiSuite, without downloading any intermediate packages. To ensure that the rollback succeeds, read the instructions carefully and perform the steps as instructed.
1. The following are precautions for roll-back.
a. Rolling back to an earlier version will erase all data on your device. Use an SD card, computer, or Cloud storage to back up all important data before rolling back your phone, and make sure all backed up content is complete and effective.
b. Use a computer running a Windows operating system to visit http://consumer.huawei.com/minisite/HiSuite_en/index.html and download the latest version of HiSuite. If HiSuite is installed on your computer, click the version number in the lower left corner of the page to check if it is the latest version. Make sure HiSuite version is 9.1.0.303 _OVE or above.
c. Before rolling back the phone, make sure your phone has not been upgraded using non-official updates. Otherwise, the roll-back may fail and unknown issues may be introduced. If you have used non-official packages to upgrade your phone, it is recommended that you go to an after-sales service center to roll back your phone.
d. Before rolling back your phone, make sure that your phone system has not been unlocked or rooted. If the system has been unlocked or rooted, it is recommended that you go to an after-sales service center to roll back your phone.
e. Before the roll-back, restore the phone to factory settings to make sure there is enough storage space.
f. Make sure the battery level is more than 50%.
Hi All,
I need assistance to update my EML L29 Huawei P20 phone.
The phone is Locked and FRP Lock
Issue the phone is always booting into recovery mode and not into the main screen.
I tired flashing via CMD using twrp.img file but its not writing.
Need help

Categories

Resources