Related
A long time ago I followed a guide showing the procedure to UNLOCK my P9 Lite as a way to allow me to root it.
As usual with this kind of stuff, the procedure only worked in half: the phone was unlocked, but I got no root access at all. Since then, every time I reboot my phone, I see a message saying my phone "was unlocked, and cannot be trusted", showing me a link to restore it (I'd gladly link it, but the forum doesn't let me). Anyway, that link simply takes me back to the Emui homepage.
Now I've received a new update (VNS-L31C113B364) for my phone, but everytime I try to install it, as soon as the phone reboots, the screen mentioned above appears, giving me two choices: rebooting my phone or opening Huawei eRecovery to restore it.
Rebooting the phone then shows an "update failed" notification, and allows me to keep using my phone as usual.
Opening Huawei eRecovery, instead, allows me to select "Download latest version and recovery". This option gets me a "Getting package info from server", but quickly turns into a "Getting package info failed".
At the same time, I can't Factory Reset my phone, because that procedure gives the same result.
Is there anything else I can try to solve this situation?
I'm extremely close to throwing my phone at sea and buy another one.
QuentinVance said:
A long time ago I followed a guide showing the procedure to UNLOCK my P9 Lite as a way to allow me to root it.
As usual with this kind of stuff, the procedure only worked in half: the phone was unlocked, but I got no root access at all. Since then, every time I reboot my phone, I see a message saying my phone "was unlocked, and cannot be trusted", showing me a link to restore it (I'd gladly link it, but the forum doesn't let me). Anyway, that link simply takes me back to the Emui homepage.
Now I've received a new update (VNS-L31C113B364) for my phone, but everytime I try to install it, as soon as the phone reboots, the screen mentioned above appears, giving me two choices: rebooting my phone or opening Huawei eRecovery to restore it.
Rebooting the phone then shows an "update failed" notification, and allows me to keep using my phone as usual.
Opening Huawei eRecovery, instead, allows me to select "Download latest version and recovery". This option gets me a "Getting package info from server", but quickly turns into a "Getting package info failed".
At the same time, I can't Factory Reset my phone, because that procedure gives the same result.
Is there anything else I can try to solve this situation?
I'm extremely close to throwing my phone at sea and buy another one.
Click to expand...
Click to collapse
same trouble here, can someone help ?
EDIT: Just to clarify, my phone is rooted and it does work, it just can't update to a newer version of the stock ROM, showing error number 7 in TWRP whenever I try to update it.
Try relocking the bootloader, if that doesn't work you need to preform a roolback to MM, this will lock the bootloader, then you can update it.
vidra said:
Try relocking the bootloader, if that doesn't work you need to preform a roolback to MM, this will lock the bootloader, then you can update it.
Click to expand...
Click to collapse
The problem is: how can I do that? I guess the link I'm seeing while booting is the one supposed to explain that, but it doesn't really show me anything.
QuentinVance said:
The problem is: how can I do that? I guess the link I'm seeing while booting is the one supposed to explain that, but it doesn't really show me anything.
Click to expand...
Click to collapse
no create a dload map on your MicroSD card and put the first rollbanc package in it, then reboot. Then remove the first UPDATE.APP AND REPLACE IT WITH UPDATE.APP htis is about 3gb. Just follow this
https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955
vidra said:
no create a dload map on your MicroSD card and put the first rollbanc package in it, then reboot. Then remove the first UPDATE.APP AND REPLACE IT WITH UPDATE.APP htis is about 3gb. Just follow this
https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955
Click to expand...
Click to collapse
The procedure you suggested specifically says NOT to try it on unlocked phones, so this doesn't really seem like a great idea to me...
I have done it two times on my unlocked p9 lite, it is fine. It will lock yout bootloader
This is quite strange: I'm following the guide you linked, but every time I copy the second file to my dload folder, it always fails after a few minutes. No explanations at all, I simply hear the "error" sound and the loading stops.
Update: I've managed to download and copy the correct version of the file (should be L31) but it doesn't work: it shows a message stating the file is incompatible and forces me to reboot my phone.
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Neskobar said:
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Click to expand...
Click to collapse
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Choose an username... said:
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Click to expand...
Click to collapse
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Neskobar said:
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Click to expand...
Click to collapse
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
raystef66 said:
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
Click to expand...
Click to collapse
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Neskobar said:
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Click to expand...
Click to collapse
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
raystef66 said:
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
Click to expand...
Click to collapse
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
edit - I renamed the zip to "update.up" and couldn't get that to work either. It's not detected in the update section of settings, and I still get the same "Sorry, you can't sdcard upgrade" message.
edit #2 - I tried naming it to "update.up.zip" and it detected it this time, trying to run the update now.
Neskobar said:
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up, when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
Click to expand...
Click to collapse
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
raystef66 said:
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
Click to expand...
Click to collapse
Ah, I should have mentioned that. This is the message I'm getting when I try that:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Neskobar said:
Ah, I should have mentioned that. This is the message I'm getting when I try that:
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Click to expand...
Click to collapse
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
raystef66 said:
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
Click to expand...
Click to collapse
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
raystef66 said:
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
Click to expand...
Click to collapse
Ok, I attached it to this post, hope it works.
Neskobar said:
Ok, I attached it to this post, hope it works.
Click to expand...
Click to collapse
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
raystef66 said:
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Click to expand...
Click to collapse
Yes, that's what I was concerned about. The very first update i tried to install was N-B09, and everything else has been an older update after that, so maybe it won't overwrite the newer files, or something? Or possibly something else went wrong in the first update, so everything else just wouldn't work because of that?
I'm putting N-B01 onto my SD card right now, so I'll test that, and if it doesn't work I'll wipe the phone and start again. If I do need to wipe the phone, however, which update would you recommend trying first? N-B09? That might confirm if it was just bad luck on the first try, or whatever.
RobboW said:
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Click to expand...
Click to collapse
Agreed, that sounds like a possibility to me. I'll probably end up wiping and starting over.
Choose an username... said:
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
Click to expand...
Click to collapse
Yes the tab autocomplete works on the "u" of update.zip and "o" of ota.zip, when I tried both. I have to admit, I was quite excited to see your suggestion there, as I thought that would be a really easy way to confirm if something isn't right with adb, but never mind.
I still don't understand why it gives me this error then, though: * cannot read 'update.zip' *.
ramnkc said:
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
Click to expand...
Click to collapse
Thanks for the suggestion, and yes, I did confirm that I renamed the right zip file. That would have been easy thing to fix though, sadly.
edit - I tried the same adb commands with windows powershell too, and got exactly the same error messages.
What ROM was on it before you flashed B09?
Updating to N-B01 worked! I've no idea why this happened the way it did, nor why adb didn't work for sideloading, but I'm really glad that it finally worked.
The order of events:
1) Installed N-B09 via transfer to SD using the android updater, no difference in android version, but appeared in update history.
2) Installed MM-B11, same as above.
3) Tried various methods of installing MM-B11, including:
- SD transfer
- recovery mode SD update (which the phone wouldn't let me do, saying, "Sorry, you can't sdcard upgrade").
- ADB sideload (which never worked even slightly. I always got the message, * cannot read 'update.zip'/'ota.zip'/'update.up.zip' *)
- Tried the above methods with variously named zip files, including "update, ota, and update.up".
- Tried the above methods, but wiping the cache in between processes.4) Installed N-B01 via transfer to SD using the android updater. This time the process took a lot longer and after rebooting the phone, went through the process of optimizing apps, which it had never done before.
Ok, I think that's everything.
The only theory I can come up with is that: Something (I have no idea what, though) went wrong with the first update attempt and every subsequent attempt to update to an older version didn't work because it didn't want to overwrite newer android version files? That doesn't seem quite right to me, though, as I would assume that whatever is in the update.zip would just overwrite everything as standard, because the assumption would always be that these files are newer than the existing ones.
What would you recommend that I do next? Should I try to push through the latest N update now, then? Has this outcome helped you figure out what the problem was/is?
Whatever the case, I'm happy to finally get an update working. Thanks very much for all your help and suggestions, guys. It was much appreciated!
Well here we are once again. Another ota update and was wondering if anyone has downloaded and packaged this update for our rooted / twrp phones?
The new ota update number and date:
BND-L34 8.0.0.332(C567)FULL
06/12/2018
madgoogler said:
Well here we are once again. Another ota update and was wondering if anyone has downloaded and packaged this update for our rooted / twrp phones?
The new ota update number and date:
BND-L34 8.0.0.332(C567)FULL
06/12/2018
Click to expand...
Click to collapse
Firmware finder shows Bond-L34CC567CUSTC567D1B332 (8.0.0.332) , and in file list it list "Bond-L34C 8.0.0.332(C567CUSTC567D1)" but in the filelist.xml it shows "BND-L34-hw-usa" . I'm unsure if its the same device but BOND-L34 doesnt seem to exist other than on fccid.io .
hicloud links
update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v138542/f1/full/update.zip
update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v138542/f1/full/public/update_data_full_public.zip
update.hicloud.com:8180/TDS/data/files/p3/s15/G2649/g1699/v138542/f1/full/BND-L34_hw_usa/update_full_BND-L34_hw_usa.zip
I'm downloading them now to see if its for the mate se, i can check against some of the partitions on my phone, i cant get the update off my phone because i messed up some of my partitions. Im alsu unsure how/which of these would be used to restore the phone to stock. I had seen some stuff on putting the files in a folder named dload, but my prior attempts to do that failed, the files i was using were for "BND-L34CC567B330 (8.0.0.330)" and im guessing it was failing because im on 8.0.0.332.
the file component_version.txt in VERSIONS.img lists "Version-BND-L34-000000 8.0.0.1(O.18051701)" , so it seems like its the correct file.
in case anyone stumbles on this trying to fix their phone i would avoid flashing the whole thing until there's better verification that its correct.
if you need a specific image download and extract the three files in my prior post and use "HuaweiUpdateExtractor" (uncheck verify header) to extract them from the UPDATE.APP
Let me know if any progress has been made on whether this firmware is correct and AOK.
THX
madgoogler said:
Let me know if any progress has been made on whether this firmware is correct and AOK.
THX
Click to expand...
Click to collapse
I flashed vendor, system and ramdisk from this then flash phh-treble and all seems well. the only issues i see seem to be from the treble rom. There is also a downgrade rom listed as "Bond-L34C567B130" in firmware finder, its description says "This HOTA will downgrade your system to N version."
files
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G2769/g1647/v139837/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...BND-L34_hw_usa/update_full_BND-L34_hw_usa.zip
Putting it in simplest terms possible. What 3xactly is the treble rom and what does it do? I hear a bunch of stuff but it gets a bit overwhelming to sift through all the incoherent posts that have nothing to do with the thread itself. lol.l
madgoogler said:
Putting it in simplest terms possible. What 3xactly is the treble rom and what does it do? I hear a bunch of stuff but it gets a bit overwhelming to sift through all the incoherent posts that have nothing to do with the thread itself. lol.l
Click to expand...
Click to collapse
project treble is available on Oreo compatible devices, it splits the system partition into separate system(operating system) and vendor(drivers) partitions, it also separates the kernel to its own partition and splits or renames recovery. That means that a rom developer can make a single image that works with any phone. unfortunately its not quite so simple since manufacturers do weird stuff that breaks things. huawei for example generates some files in the data partition that are necessary for everything to work.
That explains why twrp and flashing changed in 8.0
Thank you in advance to those who respond
will not long ago I want to root my smart phone is a Huawei P10 Lite released model WAS-LX3 with EMUI and Android version 8.0.0
When trying to root, I opened the bootloader without problem, and install a version of TWRP that apparently was for the P10 lite but when it had the version of android Nougat, in my country was just unlocked Oreo, I do not know if there was the problem but when wanting to install supersu or magiskV I got an error and in the end it was not possible
when I stop trying after a while I keep getting updates, but I have not installed them for fear they will not, find out if they try to root the phone, attached image of the update
by the way now every time I restart the mobile I get a black screen, image also below, with a link to try to enter but said that the page was not available
finally my question is
It will cause some problem if I install the updates, I want to do it, but I am afraid that I will wrap my cell phone or leave it unusable, I really do not know if it is serious or not, but I prefer to avoid problems if they can arise, The update is the WAS-LX3 8.0.0.364 (C605) says that they are google security patches.
my current version is WAS-LX3 8.0.0.360 (C605)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The black screen say something like "Your Phone is unlocked"?
If is that, you don't need to worry, is because you unlock the bootloader.
Fire Spirit said:
Thank you in advance to those who respond
will not long ago I want to root my smart phone is a Huawei P10 Lite released model WAS-LX3 with EMUI and Android version 8.0.0
When trying to root, I opened the bootloader without problem, and install a version of TWRP that apparently was for the P10 lite but when it had the version of android Nougat, in my country was just unlocked Oreo, I do not know if there was the problem but when wanting to install supersu or magiskV I got an error and in the end it was not possible
when I stop trying after a while I keep getting updates, but I have not installed them for fear they will not, find out if they try to root the phone, attached image of the update
by the way now every time I restart the mobile I get a black screen, image also below, with a link to try to enter but said that the page was not available
finally my question is
It will cause some problem if I install the updates, I want to do it, but I am afraid that I will wrap my cell phone or leave it unusable, I really do not know if it is serious or not, but I prefer to avoid problems if they can arise, The update is the WAS-LX3 8.0.0.364 (C605) says that they are google security patches.
my current version is WAS-LX3 8.0.0.360 (C605)
Click to expand...
Click to collapse
Sorry, but it's a little hard to understand you.
Anyway when you have a custom Recovery installed then you can't install OTA updates, but if you have a stock recovery then they should work without problems even when your bootloader is unlocked. And that screen appears when you have unlocked your bootloader as Ret-Zero said already.
Also your images don't work. Use the preview post option to see if they work or not before posting. I have personally used Imgur for inserting images and have never had a problem with it.
RE: about suggestion and correction
Thank you for helping me, and I'm sorry if it was for the grammar, I'm Spanish speaking so I use a translator, and if it was because I did not understand ... I'm sorry hehe
I just updated, thanks for the suggestion of imgur
that is the screen that appears when starting
does not have the factory recovery installed a modified TWRP, and that's the update that I get
I knew that technically, via OTA, they should not come to me because they opened the bootloader, but maybe I'm wrong
RE: Ret-Zero
and update the post by uploading the image of the screen that appears, thanks for answering
Fire Spirit said:
Thank you for helping me, and I'm sorry if it was for the grammar, I'm Spanish speaking so I use a translator, and if it was because I did not understand ... I'm sorry hehe
I just updated, thanks for the suggestion of imgur
that is the screen that appears when starting
does not have the factory recovery installed a modified TWRP, and that's the update that I get
I knew that technically, via OTA, they should not come to me because they opened the bootloader, but maybe I'm wrong
Click to expand...
Click to collapse
Yes that is the screen that you get when your bootloader is unlocked. When you press the power button it will boot you into android and when you press volume up then it should boot you into the stock eRecovery no matter what, even when you have a custom recovery installed. To boot into the custom recovery reboot the phone while holding volume up.
I don't think that unlocking the bootloader will prevent you from getting OTA updates, it will just give you the ability to flash custom images whether it be custom recovery, kernel or an entire OS.
Also your images are so big that they don't fit onto my laptop screen. When you choose an image in Imgur, in the same window that has all the different links, it also has options for changing the size of the image.
DeathBell said:
Yes that is the screen that you get when your bootloader is unlocked. When you press the power button it will boot you into android and when you press volume up then it should boot you into the stock eRecovery no matter what, even when you have a custom recovery installed. To boot into the custom recovery reboot the phone while holding volume up.
I don't think that unlocking the bootloader will prevent you from getting OTA updates, it will just give you the ability to flash custom images whether it be custom recovery, kernel or an entire OS.
Also your images are so big that they don't fit onto my laptop screen. When you choose an image in Imgur, in the same window that has all the different links, it also has options for changing the size of the image.
Click to expand...
Click to collapse
Thank you, good if I give you volume up if you start with the stock.
that was my doubt, is that I wanted to avoid any inconvenience if a bad installation arose because I was touching the cell haha
and with imgur, I will learn later hahaha thank you very much
DeathBell said:
Yes that is the screen that you get when your bootloader is unlocked. When you press the power button it will boot you into android and when you press volume up then it should boot you into the stock eRecovery no matter what, even when you have a custom recovery installed. To boot into the custom recovery reboot the phone while holding volume up.
I don't think that unlocking the bootloader will prevent you from getting OTA updates, it will just give you the ability to flash custom images whether it be custom recovery, kernel or an entire OS.
Also your images are so big that they don't fit onto my laptop screen. When you choose an image in Imgur, in the same window that has all the different links, it also has options for changing the size of the image.
Click to expand...
Click to collapse
help, I think the update has gone wrong or not
as no longer supposedly there were no problems of errors, I gave him to install the update
and I reboot the cell phone, normal, always does it when installing updates
but I started the custom TWRP, now that I give it a reboot and I want to reboot the system or just turn off the disositive
A message appears in blue saying: "No OS Installed! Are you sure you wish to power off?"
if I reboot the system, it puts me back into the TWRP
and if I turn off the phone and then turn it on normally
puts me in the system
what happened??
it could not be that I deleted the OS ... if it was just an update, and if it was, how to install the stock again
Fire Spirit said:
help, I think the update has gone wrong or not
as no longer supposedly there were no problems of errors, I gave him to install the update
and I reboot the cell phone, normal, always does it when installing updates
but I started the custom TWRP, now that I give it a reboot and I want to reboot the system or just turn off the disositive
A message appears in blue saying: "No OS Installed! Are you sure you wish to power off?"
if I reboot the system, it puts me back into the TWRP
and if I turn off the phone and then turn it on normally
puts me in the system
what happened??
it could not be that I deleted the OS ... if it was just an update, and if it was, how to install the stock again
Click to expand...
Click to collapse
You had a custom recovery installed while performing the update so it couldn't install it. To unbrick you phone use HuRUpdaterhttps://www.google.ee/amp/s/forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279/amp/. It may be a little difficult to set up especially since you use a translator.
I'll give you clearer instructions when I have more. time
Fire Spirit said:
help, I think the update has gone wrong or not
as no longer supposedly there were no problems of errors, I gave him to install the update
and I reboot the cell phone, normal, always does it when installing updates
but I started the custom TWRP, now that I give it a reboot and I want to reboot the system or just turn off the disositive
A message appears in blue saying: "No OS Installed! Are you sure you wish to power off?"
if I reboot the system, it puts me back into the TWRP
and if I turn off the phone and then turn it on normally
puts me in the system
what happened??
it could not be that I deleted the OS ... if it was just an update, and if it was, how to install the stock again
Click to expand...
Click to collapse
Ok, i'll give you step by step instructions. Hopefully your translator doesn't ruin the translation. Also I'm assuming your using Windows. When you are using linux then I'll probably have to give you the firmware files myself since Firmware Finder isn't for Linux.
1. Install Huawei Firmware Finder for Windows and open it.
2. Click on the tab that says "Common Base" and search for Was-LX3C605
3. Click filelist on the Was-LX3C605B364 firmware MAKE SURE THAT THE TYPE IS FULLOTA-MF
4. You should see 3 links. Copy them to your browser and download those 3 files. Their combined size is about 2.5 GB.
5. Put the 3 zip files that you downloaded into an empty folder.
6. Rename
"update_full_WAS-L23_hw_la.zip" to "update_all_hw.zip"
"update_data_full_public.zip" to "update_data_public.zip"
Don't rename "update.zip"
7. Download "HuRUpdater_0.4.zip" and put it also into the folder that you crated.
8. Boot to TWRP and move the folder into your phone's SD-Card.
9. Then flash only "HuRUpdater_0.4.zip". After flashing you'll have to press volume down otherwise it will abort the script.
Then you will need to wait a little. It will also show 3 unknown command errors written in red text. Ignore those because they don't mean anything.
When the installation failed then there is probably a problem with you Custom Recovery. When it worked then you should be able to boot into Android and also have the latest firmware.:fingers-crossed:
DeathBell said:
Ok, i'll give you step by step instructions. Hopefully your translator doesn't ruin the translation. Also I'm assuming your using Windows. When you are using linux then I'll probably have to give you the firmware files myself since Firmware Finder isn't for Linux.
1. Install Huawei Firmware Finder for Windows and open it.
2. Click on the tab that says "Common Base" and search for Was-LX3C605
3. Click filelist on the Was-LX3C605B364 firmware MAKE SURE THAT THE TYPE IS FULLOTA-MF
4. You should see 3 links. Copy them to your browser and download those 3 files. Their combined size is about 2.5 GB.
5. Put the 3 zip files that you downloaded into an empty folder.
6. Rename
"update_full_WAS-L23_hw_la.zip" to "update_all_hw.zip"
"update_data_full_public.zip" to "update_data_public.zip"
Don't rename "update.zip"
7. Download "HuRUpdater_0.4.zip" and put it also into the folder that you crated.
8. Boot to TWRP and move the folder into your phone's SD-Card.
9. Then flash only "HuRUpdater_0.4.zip". After flashing you'll have to press volume down otherwise it will abort the script.
Then you will need to wait a little. It will also show 3 unknown command errors written in red text. Ignore those because they don't mean anything.
When the installation failed then there is probably a problem with you Custom Recovery. When it worked then you should be able to boot into Android and also have the latest firmware.:fingers-crossed:
Click to expand...
Click to collapse
Thank you very much, yes, what I do is first translated and read it, and then see it in English hahaha, I can read English, what costs me too much is ecrbirilo
I have a question, I have seen how to install the custom ROMS that you are in XDA, it is very easy and I only need the TWRP
but, is there a problem if I install one of those? because it would take advantage and put one that already has root available
DeathBell said:
Ok, i'll give you step by step instructions. Hopefully your translator doesn't ruin the translation. Also I'm assuming your using Windows. When you are using linux then I'll probably have to give you the firmware files myself since Firmware Finder isn't for Linux.
1. Install Huawei Firmware Finder for Windows and open it.
2. Click on the tab that says "Common Base" and search for Was-LX3C605
3. Click filelist on the Was-LX3C605B364 firmware MAKE SURE THAT THE TYPE IS FULLOTA-MF
4. You should see 3 links. Copy them to your browser and download those 3 files. Their combined size is about 2.5 GB.
5. Put the 3 zip files that you downloaded into an empty folder.
6. Rename
"update_full_WAS-L23_hw_la.zip" to "update_all_hw.zip"
"update_data_full_public.zip" to "update_data_public.zip"
Don't rename "update.zip"
7. Download "HuRUpdater_0.4.zip" and put it also into the folder that you crated.
8. Boot to TWRP and move the folder into your phone's SD-Card.
9. Then flash only "HuRUpdater_0.4.zip". After flashing you'll have to press volume down otherwise it will abort the script.
Then you will need to wait a little. It will also show 3 unknown command errors written in red text. Ignore those because they don't mean anything.
When the installation failed then there is probably a problem with you Custom Recovery. When it worked then you should be able to boot into Android and also have the latest firmware.:fingers-crossed:
Click to expand...
Click to collapse
Thank you very much, yes, what I do is first translated and read it, and then see it in English hahaha, I can read English, what costs me too much is ecrbirilo
I have a question, I have seen how to install the custom ROMS that you are in XDA, it is very easy and I only need the TWRP
but, is there a problem if I install one of those? because it would take advantage and put one that already has root available
Fire Spirit said:
Thank you very much, yes, what I do is first translated and read it, and then see it in English hahaha, I can read English, what costs me too much is ecrbirilo
I have a question, I have seen how to install the custom ROMS that you are in XDA, it is very easy and I only need the TWRP
but, is there a problem if I install one of those? because it would take advantage and put one that already has root available
Click to expand...
Click to collapse
I would get the stock rom working first and have a way to always go back to stock on my sd-card in case something goes wrong or you just wish to go back to stock. Otherwise installing custom roms is easy as long as you follow the instructions, I have seen many times that newer members say that their phones are bricked because they wiped every single partition or something like that while trying to install a custom rom. Usually you only have to wipe data, system, cache and dalvik cache.
There's no point to installing pre-rooted roms if these even exist on huawei devices. When you wan't to root just install the latest version of magisk and you are good to go.
Also your device is C605 and not C432(European version). I am almost certain that you don't have to rebrand to C432 when installing custom roms especially treble roms but I am not entirely sure
Also you can find lots of treble roms that work for our devices in the p8 lite (2017) development forum
DeathBell said:
I would get the stock rom working first and have a way to always go back to stock on my sd-card in case something goes wrong or you just wish to go back to stock. Otherwise installing custom roms is easy as long as you follow the instructions, I have seen many times that newer members say that their phones are bricked because they wiped every single partition or something like that while trying to install a custom rom. Usually you only have to wipe data, system, cache and dalvik cache.
There's no point to installing pre-rooted roms if these even exist on huawei devices. When you wan't to root just install the latest version of magisk and you are good to go.
Also your device is C605 and not C432(European version). I am almost certain that you don't have to rebrand to C432 when installing custom roms especially treble roms but I am not entirely sure
Also you can find lots of treble roms that work for our devices in the p8 lite (2017) development forum
Click to expand...
Click to collapse
you're right, better keep the stock so you do not go unloading every time you ruin it hahaha
I only need to download the HuRUpdater tool
I'll see how it goes thanks:dedos cruzados:
DeathBell said:
Ok, i'll give you step by step instructions. Hopefully your translator doesn't ruin the translation. Also I'm assuming your using Windows. When you are using linux then I'll probably have to give you the firmware files myself since Firmware Finder isn't for Linux.
1. Install Huawei Firmware Finder for Windows and open it.
2. Click on the tab that says "Common Base" and search for Was-LX3C605
3. Click filelist on the Was-LX3C605B364 firmware MAKE SURE THAT THE TYPE IS FULLOTA-MF
4. You should see 3 links. Copy them to your browser and download those 3 files. Their combined size is about 2.5 GB.
5. Put the 3 zip files that you downloaded into an empty folder.
6. Rename
"update_full_WAS-L23_hw_la.zip" to "update_all_hw.zip"
"update_data_full_public.zip" to "update_data_public.zip"
Don't rename "update.zip"
7. Download "HuRUpdater_0.4.zip" and put it also into the folder that you crated.
8. Boot to TWRP and move the folder into your phone's SD-Card.
9. Then flash only "HuRUpdater_0.4.zip". After flashing you'll have to press volume down otherwise it will abort the script.
Then you will need to wait a little. It will also show 3 unknown command errors written in red text. Ignore those because they don't mean anything.
When the installation failed then there is probably a problem with you Custom Recovery. When it worked then you should be able to boot into Android and also have the latest firmware.:fingers-crossed:
Click to expand...
Click to collapse
friend did not work, gave error, right now attached images
I think it's because of the message that says, Inf no recorey.img
Now I will try to install one called CypheroOS
and if it does not work I will try with the method of this video;
https://www.youtube.com/watch?v=jRu7fz5GFdI
I do not know what to do :crying::crying: :crying::crying:
Fire Spirit said:
friend did not work, gave error, right now attached images
I think it's because of the message that says, Inf no recorey.img
Now I will try to install one called CypheroOS
and if it does not work I will try with the method of this video;
https://www.youtube.com/watch?v=jRu7fz5GFdI
I do not know what to do :crying::crying: :crying::crying:
Click to expand...
Click to collapse
That video wouldn't work because it's for EMUI 5 only.
Try to boot to TWRP then select mount and make sure that cache, cust, data, system, vendor are mounted(have checkmarks next to them.
When it still doesn't work then boot to fastboot and check if phone and frp are unlocked when they are install this TWRP(use the 0.2 test version) then try again
Edit: I would also like to know what recovery are you using. Can you give me the link please
DeathBell said:
That video wouldn't work because it's for EMUI 5 only.
Try to boot to TWRP then select mount and make sure that cache, cust, data, system, vendor are mounted(have checkmarks next to them.
When it still doesn't work then boot to fastboot and check if phone and frp are unlocked when they are install this TWRP(use the 0.2 test version) then try again
Edit: I would also like to know what recovery are you using. Can you give me the link please
Click to expand...
Click to collapse
A summary of what happened:
I turned off the cell because I needed the SD, and when I started it again
Instead of starting with TWRP, start with the stock recovery
And well there you only get 3 options, which is an Android start, turn off and I do not remember the last
I gave it to start system
And I start the phone all normal
Honestly I do not know what happened hahaha but I already have a cell phone
Now if I still have the custom recovery or the bootloader open I do not know it hahaha at the moment I do not want to keep touching more things
And about the version I had, I do not remember, at that time I think there was not for Android oreo, or for the p10 lite
I think I installed one of an honor 9
Is that in the official listings on the TWRP page did not appear p10 lite
Then lower the honor
I do not know if there is already TWRP that works well
I remember that I could not install supersu nor magisk before
And about the data, cache, no, those were demarcated.
I do not know why, nor did I know what it was for
Fire Spirit said:
A summary of what happened:
I turned off the cell because I needed the SD, and when I started it again
Instead of starting with TWRP, start with the stock recovery
And well there you only get 3 options, which is an Android start, turn off and I do not remember the last
I gave it to start system
And I start the phone all normal
Honestly I do not know what happened hahaha but I already have a cell phone
Now if I still have the custom recovery or the bootloader open I do not know it hahaha at the moment I do not want to keep touching more things
And about the version I had, I do not remember, at that time I think there was not for Android oreo, or for the p10 lite
I think I installed one of an honor 9
Is that in the official listings on the TWRP page did not appear p10 lite
Then lower the honor
I do not know if there is already TWRP that works well
I remember that I could not install supersu nor magisk before
And about the data, cache, no, those were demarcated.
I do not know why, nor did I know what it was for
Click to expand...
Click to collapse
I have no idea why your phone booted suddenly. The reason your installation failed is because the TWRP that you were using wasn't able to mount the required partions for some reason, the same probably happend when you were trying to install magisk.
Also yes that TWRP is for the honor 9 lite. But the honor 9 lite, p8 lite(2017), p10 lite, mate 10 lite just to name a few are all hi6250 devices so their recoveries, kernels and roms should work for all hi6250 devices. The good thing about this TWRP is that it works both in stock and custom roms but it has some minor bug.
Or you can also use this TWRP. This works perfectly for stock roms, but when you use custom roms then it doesn't even boot, it just hangs on the TWRP logo. One time It didn't even boot when I were on a stock rom but had wiped system, dalvik, data and internal storage and frp was also locked itself for some reason so I bricked my phone and payed 20€ for dc-phoenix to fix it. Back then I had no idea what I was doing anyway. You will also have to remove your screenlock password before using this TWRP because it checks for it when you boot into it, but even when you type the right password it still doesn't work and then it fails to unmount data.
I've used them both and they work really well, also I have no idea what I am writing about since I'm very tired. It's 00.40 AM for me.
DeathBell said:
I have no idea why your phone booted suddenly. The reason your installation failed is because the TWRP that you were using wasn't able to mount the required partions for some reason, the same probably happend when you were trying to install magisk.
Also yes that TWRP is for the honor 9 lite. But the honor 9 lite, p8 lite(2017), p10 lite, mate 10 lite just to name a few are all hi6250 devices so their recoveries, kernels and roms should work for all hi6250 devices. The good thing about this TWRP is that it works both in stock and custom roms but it has some minor bug.
Or you can also use this TWRP. This works perfectly for stock roms, but when you use custom roms then it doesn't even boot, it just hangs on the TWRP logo. One time It didn't even boot when I were on a stock rom but had wiped system, dalvik, data and internal storage and frp was also locked itself for some reason so I bricked my phone and payed 20€ for dc-phoenix to fix it. Back then I had no idea what I was doing anyway. You will also have to remove your screenlock password before using this TWRP because it checks for it when you boot into it, but even when you type the right password it still doesn't work and then it fails to unmount data.
I've used them both and they work really well, also I have no idea what I am writing about since I'm very tired. It's 00.40 AM for me.
Click to expand...
Click to collapse
do not worry, it's serious thank you for all your help, I still have a lot to learn
This is a last request, answer when you can
I would like you to give me a link or the post where the best TWRP is for the p10 lite, the one that works with both stock and personalized rooms, now I want to see if I can change rooms
and on the partitions, I remember that in a twrp area I said mount, and the partitions where I got an error, they were disassembled, they were not marked
It was not me, I guess that was the case since I installed the twrp,
That and how you installed the twrp, maybe that's why the one I have did not do things well, I installed the one I tell you of honor, with Huawei MultiTool, from the same channel of the video that I was going to follow
install the honor because it was the only one that worked, all others gave me error, I do not know if it was because the tool because in other forums I read that when it was updated to support EMUI 8, I made many errors when installing twrp, so it was with me
First of all, hello there community, all of you have already helped me so much and I really appreciate the effort that you put into this site to help guys like me out
Now onwards to my Problem:
I've had the P Smart for a couple of month when I considered using a Treble custom Rom (just to try it out and have some fun with it).
Since I didn't know how to flash GSI's I googled it and took the first step by step tutorial and followed it.
The Rom I flashed was the PixelExperience_arm64_a-8.1.0-20181015-0009-OFFICIAL.img.
Basically I flashed the rom via fastboot.
When I then realized that it wasn't quite what I expected I wanted to try out other roms.
So I went do dev-options and turned on ADB and OEM-Unlock but then... The OEM-Unlock option was greyed out.
f.
Since I came from stock I have had not yet installed TWRP.
I have searched the internet for hours and hours, day after day but I could not find a single option that could help me with my particular problem.
My current state:
- I have a rom that I do not longer want installed
- I do not have TWRP or any other custom-recovery installed
- In fastboot it says
"bootloader unlocked"
"FRP locked"
(My model is FIG-LX1 btw)
So, here I am and asking you guys for help.
Is there ANY possibility (aside from replacing the mainboard) to fix my phones current state?
Your help is really appeciated,
love y'all
kthxbye
the_darkest_knight said:
First of all, hello there community, all of you have already helped me so much and I really appreciate the effort that you put into this site to help guys like me out
Now onwards to my Problem:
I've had the P Smart for a couple of month when I considered using a Treble custom Rom (just to try it out and have some fun with it).
Since I didn't know how to flash GSI's I googled it and took the first step by step tutorial and followed it.
The Rom I flashed was the PixelExperience_arm64_a-8.1.0-20181015-0009-OFFICIAL.img.
Basically I flashed the rom via fastboot.
When I then realized that it wasn't quite what I expected I wanted to try out other roms.
So I went do dev-options and turned on ADB and OEM-Unlock but then... The OEM-Unlock option was greyed out.
f.
Since I came from stock I have had not yet installed TWRP.
I have searched the internet for hours and hours, day after day but I could not find a single option that could help me with my particular problem.
My current state:
- I have a rom that I do not longer want installed
- I do not have TWRP or any other custom-recovery installed
- In fastboot it says
"bootloader unlocked"
"FRP locked"
(My model is FIG-LX1 btw)
So, here I am and asking you guys for help.
Is there ANY possibility (aside from replacing the mainboard) to fix my phones current state?
Your help is really appeciated,
love y'all
kthxbye
Click to expand...
Click to collapse
You must sign in google account
leap_ahead said:
You must sign in google account
Click to expand...
Click to collapse
Did that already...
Erecovery, connects to wifi, reads the lastest rom from a server, installs it, wipes it all to stock
Hopefully that works
https://www.hardreset.info/devices/huawei/huawei-p-smart/recovery-mode/
redultra82 said:
Erecovery, connects to wifi, reads the lastest rom from a server, installs it, wipes it all to stock
Hopefully that works
https://www.hardreset.info/devices/huawei/huawei-p-smart/recovery-mode/
Click to expand...
Click to collapse
Tried that already, it can't connect to the update server. ("Getting package info failed").
Also I tried the dload method, but none of the update files that I tried seemed to work, it either goes to 5% or says "software install failed" (or both).
..
the_darkest_knight said:
Tried that already, it can't connect to the update server. ("Getting package info failed").
Also I tried the dload method, but none of the update files that I tried seemed to work, it either goes to 5% or says "software install failed" (or both).
Click to expand...
Click to collapse
I thought that was the be all of recovery, its never let me now
Hey dude i had ur same problem . All u need to do is use eRecovery and firmware finder through d's its easy
U this will guide you
https://www.google.tn/amp/s/forum.x...y-huawei-erecovery-solution-100-t3620165/amp/
let me know if you need further help
redultra82 said:
I thought that was the be all of recovery, its never let me now
Click to expand...
Click to collapse
I don't know why it doesn't work...
ilyes9999 said:
Hey dude i had ur same problem . All u need to do is use eRecovery and firmware finder through d's its easy
U this will guide you
https://www.google.tn/amp/s/forum.x...y-huawei-erecovery-solution-100-t3620165/amp/
let me know if you need further help
Click to expand...
Click to collapse
So I tried that out, but firstly I couldn't find a proper OEMINFO, and secondly I don't think I could flash it, since my OEM bootloader is still locked...
As I understood HWOTA doesn't support the P Smart (yet?), and it also needs the OEM to be unlocked
And without the OEMINFO it does not seem to work
the_darkest_knight said:
I don't know why it doesn't work...
So I tried that out, but firstly I couldn't find a proper OEMINFO, and secondly I don't think I could flash it, since my OEM bootloader is still locked...
As I understood HWOTA doesn't support the P Smart (yet?), and it also needs the OEM to be unlocked
And without the OEMINFO it does not seem to work
Click to expand...
Click to collapse
I don't know what you mean . All i know by my experience if you can access the eRecovery you can fix it even with locked bootloader
---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------
And by the way when looking for a firmware for your device . You should use older versions and it should be the full ota update