Related
I believe (but can't swear to it) that I've managed to change my build number with flashing various roms. My number now is NXT-C900xxxx where xxx= software version. Before it had a more random set of numbers. I'm beginning to think this change has stopped my ability to apply standard ota updates.
I've downloaded the full B133 Rom, flashed the four partitions as stated on the unlock / unbrick tool. I also flashed the userdata.img file so I'd have my themes.
I then re-locked the boot loader using the method where your phone stated its locked, not relocked.
I thought as this point I should be able to apply the full b133 update.app file yet I get an error saying incompatible device. I've tried other update.app versions and I get the same issues. Also tried the ota update check and that states no updates available.
Does anyone have any ideas to get me back to a valid build number?
Thank you.
for that, ull first have to check which regional firmware u had in the first place unfortunately, we are not at a stage yet, where we can fully convert a phone as to be able to receive OTA updates, thus fool the update servers that this is the actual phone. were only capable of crossflashing firmwares, but this still makes it a modified phone, more or less...
this is why were tinkering with oeminfo backup and flash in others thread atm, this is a step towards enabling a user to fully change a phone model!
Is there any way (it's not printed on the box or anywhere else that I can see) I can find out my original region?
This may be help.
hw/eu for Europe and...
Model: Samsung J500F
Baseband: J500FXXU1BPF2 (Portugal)
Greetings to everyone.
My samsung j5 has a bug with the lock screen, which seems never ocurred with someone else.
It started when after i updated to Android Marshmallow after OTA updates and then i made a factory reset. After that i tried to put a Pin in lockscreen and after the pin was confirmed i locked the phone. When after a while i hit the button to turn the screen on it didnt asked the pin. In fact when i tried to change the pin in security settings it asked me a pin which wasn't the same that i put before.
To trying to solve this i though of doing a new factory reset, so i had to go to mysamsung.com to unlock the phone via remote controls and then i succefully reseted the phone.
The problem is that in the middle i forgot that and tried to do root but something went bad and i did lost the warranty but root didn't work. So a days after I tried to put a pass code and again the same error, this time asking for a password that didn't match mine.
I did some troubleshot:
-after Putting another pin the phone sends me to the previous page (security page) and instead of "pin" method to unlock screen it says "swip finger"
-it happens with passcode and pattern code too but when pattern code is choosed if i go to change it it firstly shows a pattern change screens but in a sec it dissapear being possible to put a new one and have the same bug
-I downloaded and installed a stock rom to my baseband and model (android 6.0 but my phone came with 5.1) and the error still exist.
-samsung support said to use smart switch initialization service but it says that my device doesn't support.
Notes: I didn't want to install a custom rom cause i like the samsung style.
Like i said: warranty is now voided (knox 0x1 (2)).
Any help would be apreciated.
Ps: I will provide screenshots and more info if needed.
Solved
Joylopes25 said:
Model: Samsung J500F
Baseband: J500FXXU1BPF2 (Portugal)
Greetings to everyone.
My samsung j5 has a bug with the lock screen, which seems never ocurred with someone else.
It started when after i updated to Android Marshmallow after OTA updates and then i made a factory reset. After that i tried to put a Pin in lockscreen and after the pin was confirmed i locked the phone. When after a while i hit the button to turn the screen on it didnt asked the pin. In fact when i tried to change the pin in security settings it asked me a pin which wasn't the same that i put before.
To trying to solve this i though of doing a new factory reset, so i had to go to mysamsung.com to unlock the phone via remote controls and then i succefully reseted the phone.
The problem is that in the middle i forgot that and tried to do root but something went bad and i did lost the warranty but root didn't work. So a days after I tried to put a pass code and again the same error, this time asking for a password that didn't match mine.
I did some troubleshot:
-after Putting another pin the phone sends me to the previous page (security page) and instead of "pin" method to unlock screen it says "swip finger"
-it happens with passcode and pattern code too but when pattern code is choosed if i go to change it it firstly shows a pattern change screens but in a sec it dissapear being possible to put a new one and have the same bug
-I downloaded and installed a stock rom to my baseband and model (android 6.0 but my phone came with 5.1) and the error still exist.
-samsung support said to use smart switch initialization service but it says that my device doesn't support.
Notes: I didn't want to install a custom rom cause i like the samsung style.
Like i said: warranty is now voided (knox 0x1 (2)).
Any help would be apreciated.
Ps: I will provide screenshots and more info if needed.
Click to expand...
Click to collapse
Hey everyone.
Turns out that after almost two months Samsung relased an updated that fixed this error.
Joylopes25 said:
Hey everyone.
Turns out that after almost two months Samsung relased an updated that fixed this error.
Click to expand...
Click to collapse
With installing the new update your phone baseband is still J500FXXU1BPF2 or something else?
saeid.1980 said:
With installing the new update your phone baseband is still J500FXXU1BPF2 or something else?
Click to expand...
Click to collapse
Actually with this new update the baseband still the same but when I updated the Android 5.1 to 6.0 the baseband changed.
I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
My phones info;
Software status: Modified
Android Security patch level: May 1 2016
Baseband version: M8992_1253331 .29.01.88.02R SUPER_NA
Kernal Version: 3.10.84-perf-g329ac5f
[email protected] #1
Thu Apr 21 00:11:23 CDT 2016
System Version: 24.221.4.clark_retus.retus.en.US.retus
Build Number: MPHS24.49-18-4
The pending update: New version:24.221.8.en.US
Thank you.
u need to flash official factory image inorder to get the updates
i hardly recommend you to use fastboot and install stock firmware from this site
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick...
install the latest firmware and then check for updates
if u have any queries then go through this.... make sure that u don't mess up
https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
Cjet said:
I have a non-rooted XT 1575, that had a sim card issue that gives me the 'No Command' message after trying to install the System Update (24.221.8.en.US). I had a friends son restore it by reloading 24.49-18-4. It seemed to work ok, then I received a notice to do the system update again (24.221.8.en.US).
Before doing this, I spoke with his son who assured me that it should be ok to do and go ahead and do it, even though the software says "modified". I tried installing the update and it did the same 'No Command' b.s. as before. I was able to get it to reload the 24.49.18-4, but the software status still says modified, and I am getting this dang update notice again. I also unlocked the bootloader at this point.
It is my understanding from what I have read on this forum that as long as the software status says "modified", that I will be unable to accept any updates. Is this correct? And the bootloader status is irrelevant as far as updates?
All I want is to restore this thing back to stock so it can accept updates. I am not interested in rooting. After reading the forum I am not sure how to proceed, and any help would be greatly appreciated.
Click to expand...
Click to collapse
If I understand your post correctly, and the COMPLETE firmware image was flashed, then you should have no issues taking an OTA update... the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt.
Try this, before you accept and download the update, boot into stock recovery and wipe cache. Or better yet, do a full factory reset and accept the update and apply it, then let it boot fully, do another factory reset and then set it up clean.
I don't know why this happens... it just seems like a few every update won't take it no matter what we do, and for we do not have the latest full factory image yet so there isn't much we can do to find another way.
Thank you both for your reply. However, I am still not clear on something.... there seems to be confusing/conflicting advice regarding the Software "Modified" status and it's role in accepting updates.
1. "if your system is modified then you might get updates but if u install them then you will end up in a bootloop or we can called it as softbrick..."
2. " the status of modified and bootloader lock/unlock is not relevant. The update should just work, the fact it doesn't means something is still modified or the cache is corrupt."....... If the Software status says "modified" doesn't that mean that the system is indeed modified, and that trying to load the OTA in this state will result in a bootloop? .
u neee to flash official firmware.... the only way to remove modified and change it to official....
it actually doesn't matter that if bootloader is unlock u can install the updates...... i was on may patch and i also wanted to change the software status from modified to official in order to get sept patch... but in moto firmware center the latest was feb 2016.... so i had to downgrade... i tried and it worked... then i was eligible for ota and yes im on sept patch
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Prazaar said:
Software status "modified" cant cange to official.. After factory img flashing is status still modified! Its no problem for OTA is the system stock will it work
OTA work with 100% Stock System incl recovery
(bootloader say still modified)
OTA work with unlock bootloader
Here is the new factory img
http://www.filefactory.com/file/5ea...HS24.49-18-8_cid9_subsidy-DEFAULT_CFC.xml.zip
Or
https://androidfilehost.com/?fid=745425885120703327
Gesendet von meinem XT1572 mit Tapatalk
Click to expand...
Click to collapse
I disagree... it CAN go back to Official, I had several ROMs on my device, then flashed stock image and somehow mine went back to Official. Was mine a fluke? I don't know, but it is clearly Official now. Note the picture clearly shows the bootloader was unlocked (Status 2) and I had at least dozen different ROMs flashed over time before going back to stock using the May 2016 security image and then successfully OTAing up to October security update.
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.
I know what you mean. My Software status is with LineageOS "official" i can flash every rom an the status stuck in official.
Factory img is no warranty for official status but also makes no difference for ota
Getapatalkt vom meinem Moto X Style
thebaconbox said:
Why don't you just flash a custom rom? I mean if your bootloader is already unlocked....
Click to expand...
Click to collapse
Because I am new to all of this and don't know anything about custom Roms. All I want to do is get this thing back to stock.
[/QUOTE
OP, I think we are getting caught up in the software status saying "Modified" which is of no consequence, and the device actually being modified meaning something is not stock... it's a semantics thing that I believe is confusing. The software status isn't relevant, it could say HACKED for all we care (and no, I don't think there is such a thing), but it's whether the device is REALLY stock or not.[/QUOTE]
Wow, thanks everyone for the suggestions and patience!
OK, so the software status does not affect OTA update installation. Software status being modified does not necessarily mean that the SYSTEM is modified. Yet if the SYSTEM is modified then taking the OTA update will cause a softbrick.
How can I tell if my SYSTEM is modified before deciding on taking the OTA update?
I have had the official Motorola firmware flashed/reinstalled previously by friend's son, and that didn't take the OTA update. It caused soft brick (No Command error bootloop)
I then went to the Motorola site myself, downloaded the firmware and flashed/reinstalled it. This is where I am currently, trying to decide if I should take the update or put it off until I have a couple of hours free to troubleshoot in case the OTA softbricks this thing again (it takes me much, much longer to figure this stuff out than it does for you guys. )
And if that does soft brick it again, then I am not sure what I am doing wrong with the flashing. So, is there any way for me to check to see if the SYSTEM is modified before I try the update.? Thank you!
Sagar_1401 said:
u neee to flash official firmware.... the only way to remove modified and change it to official....QUOTE
This was done twice and still says modified
Click to expand...
Click to collapse
Status modified will change to official after an OTA update.
Sent from my XT1572 using Tapatalk
Anyone? No one knows if there is any way for me to check to see if the SYSTEM is modified before I try the update.?
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Prazaar said:
Update will check system bevor it start, Is your system not 100% original will update cancel automatically.
You can not see if it is modified
Getapatalkt vom meinem Moto X Style
Click to expand...
Click to collapse
I don't understand what you are saying. I cannot see "what" if it is modified? Edited - removed earlier rant.
(Sorry)
SOLVED.....
Today I backed everything up, bit my lip and hit "install update". It did update the phone and it did change the software status to "Official". I did this with the bootloader unlocked, and it worked . It does say Status Code 3, and the bootloader unlocked warning screen on startup appears, both of these I am guessing is normal. Everything seems good.
I just ordered a Mediapad M3 8.4 and I should receive it in a couple of days. I plan to update it to whatever is the latest firmware, add TWRP and also root it. Are there any first steps or gotcha's I should be aware of? For example, should I root first or apply updates first? The reason I ask is that I've had some devices that could be rooted in one version but could not be rooted after updating the bootloader.
Any suggestions appreciated.
Firstly check what hardware oem location the tablet has as this effects it. To root or change that you need to get the bootloader unlocked. This is done via a code request website on the Huawei site. After that you can go TWRP, backup and so on.
Check the oeminfo/country ID and flash the appropriate rom for that if you want. If you want to change region, the partition oem files are online and can be done via twrp command line.
Thanks, that's what I needed to know!
Just for the sake of other people who may just be starting out with this tablet, it turns out that it does matter whether you update first or unlock first. You will not be able to get a bootloader unlock code from the Huawei website after you upgrade to EMUI 5.0, so if you plan to root your tablet, make sure you unlock the bootloader before you upgrade. Otherwise, you will have to downgrade to an earlier version.
woody1 said:
Just for the sake of other people who may just be starting out with this tablet, it turns out that it does matter whether you update first or unlock first. You will not be able to get a bootloader unlock code from the Huawei website after you upgrade to EMUI 5.0, so if you plan to root your tablet, make sure you unlock the bootloader before you upgrade. Otherwise, you will have to downgrade to an earlier version.
Click to expand...
Click to collapse
I upgraded first and still got a code. I have the LTE version. In order to get the code, I had to choose "phone" and not "tablet". It could be that with wifi-only version it won't work because you can't provide the IMEI.
Here are some notes from my experience with starting out on my new BTV-DL09 (4G version, bought in Europe):
1) I upgraded the brand new tablet to EMUI 5.0. At the end of the upgrade, I got an error message. But after reboot it seemed to work fine. Bluetooth does not work with EMUI 5.0 but I don't need Bluetooth on it.
2) I unlocked the bootloader. Had to choose "phone" on the Huawei site to get the code because there was no matching tablet with EMUI 5.
3) Installed Magisk 14 using twrp.
4) Systemless hosts doesn't work in Magisk because /system/etc/hosts is a symlink to /vendor/etc/hosts
5) remounted /system as rw, deleted /system/etc/hosts, copied /vendor/etc/hosts to /system/etc/hosts, remounted at ro
6) disabled magisk systemless hosts, re-enabled it, installed adblock hosts module, everything has worked since then.
7) changed dpi to 360 or so. 350 was nice because it made it look exactly like my Galaxy Tab S, but unfortunately the settings app didn't display the left side anymore. So I have larger icons now, but things still run in tablet mode.
If there is ever any update coming for this, I hope it will work if I undo my /system modification (put the symlink back)
I have to say, so far I'm very satisfied with this tablet! It runs super smooth, has great battery life, display, and the speakers sound great. Out of the box it's barely usable and very frustrating to use - I would not really recommend it to anyone if they don't plan on rooting it.
EDIT: just read I can get bluetooth working by upgrading first to B010 then B303, so I guess I gotta start all over again Thanks @30adi for that post: https://forum.xda-developers.com/showpost.php?p=73470572&postcount=380
adibadi said:
2) I unlocked the bootloader. Had to choose "phone" on the Huawei site to get the code because there was no matching tablet with EMUI 5.
Click to expand...
Click to collapse
It has been a while since i did unlocking. But is there a phone model to use when choosing "phone"?
fallen_13 said:
It has been a while since i did unlocking. But is there a phone model to use when choosing "phone"?
Click to expand...
Click to collapse
If you choose "Since EMUI 5.0" you have the following options:
Smartphone (not possible to change this)
Product Serial number
Product IMEI or MEID
Product ID
If you choose "Before EMUI 5.0" you have these options:
Smartphone (can change to Tablet 3G or to Tablet wifi)
Product Model
Product Serial number
Product IMEI or MEID
Product ID
So you don't need to provide the product model when choosing "since EMUI 5.0", but I'm not sure if they will accept one with no IMEI, as in the wifi-only tablet case.
adibadi said:
If you choose "Since EMUI 5.0" you have the following options:
Smartphone (not possible to change this)
Product Serial number
Product IMEI or MEID
Product ID
If you choose "Before EMUI 5.0" you have these options:
Smartphone (can change to Tablet 3G or to Tablet wifi)
Product Model
Product Serial number
Product IMEI or MEID
Product ID
So you don't need to provide the product model when choosing "since EMUI 5.0", but I'm not sure if they will accept one with no IMEI, as in the wifi-only tablet case.
Click to expand...
Click to collapse
Ah ok. I unlocked mine back before EMUI 5 was released. So i had to choose the "Product model" for Mediapad M3. Didn't know that the generic "smartphone" would just do for unlocking EMUI5. That's very helpful and does away with the need to do downgrading. Thank you.
adibadi said:
EDIT: just read I can get bluetooth working by upgrading first to B010 then B303, so I guess I gotta start all over again
Click to expand...
Click to collapse
So after downgrading back to Marshmallow, I got an update message which sent me back to B303 with an OTA, and bluetooth works now. I didn't have to go to B010 then to B303.
I'm not sure what was up with my original version which came preloaded on the tablet, but it didn't show this update - it told me that I was on on the latest version. The update screen appeared at first boot even before I could sign in to gmail. It's called OTA-BTV-DL09C100B009_B303
OK, I have the wifi only tablet, so maybe the unlock will work with the LTE version, but not with wifi-only after an upgrade to EMUI 5.0. Has anybody been successful in unlocking a wifi-only tablet which was already on EMUI 5.0? (BTW, Bluetooth works fine for me on Android 7.)
So your recommendation is to Unlock bootloader before upgrade? Does the OTA upgrade work afterward or can you do it through TWRP?
ScruffMcG said:
So your recommendation is to Unlock bootloader before upgrade? Does the OTA upgrade work afterward or can you do it through TWRP?
Click to expand...
Click to collapse
From what other people have said, the OTA will work while rooted, but I haven't tried it myself yet.
Didn't you say you upgrade to 7.0? Or did you re-lock bootloader to do that (or just stay on stock bootloader?). Just ordered so I have a couple days to figure the process out, but want to make sure I don't upgrade if I will be losing the ability to root afterward.
ScruffMcG said:
Didn't you say you upgrade to 7.0? Or did you re-lock bootloader to do that (or just stay on stock bootloader?). Just ordered so I have a couple days to figure the process out, but want to make sure I don't upgrade if I will be losing the ability to root afterward.
Click to expand...
Click to collapse
Ok, here's what happened to me:
I upgraded to EMUI 5.0/Android 7. Then, I went to the Huawei website to get the bootloader code. I was not able to get the bootloader code, because it appears that the website is not properly set up to give a bootloader unlock code for a tablet with EMUI 5.0 or greater, at least not for the wifi-only version. I'm guessing this is just a problem with the website not being updated to support the latest version.
So far, I'm trying to figure out if there's an option to get the bootloader code without downgrading first. If I can't find another way, I will downgrade, then get the bootloader code, then upgrade back to Android 7. As far as I know, there is not a problem upgrading after you've unlocked the bootloader, but I haven't personally gotten to that point.
woody1 said:
Ok, here's what happened to me:
I upgraded to EMUI 5.0/Android 7. Then, I went to the Huawei website to get the bootloader code. I was not able to get the bootloader code, because it appears that the website is not properly set up to give a bootloader unlock code for a tablet with EMUI 5.0 or greater, at least not for the wifi-only version. I'm guessing this is just a problem with the website not being updated to support the latest version.
So far, I'm trying to figure out if there's an option to get the bootloader code without downgrading first. If I can't find another way, I will downgrade, then get the bootloader code, then upgrade back to Android 7. As far as I know, there is not a problem upgrading after you've unlocked the bootloader, but I haven't personally gotten to that point.
Click to expand...
Click to collapse
I thought that the unlock code isn't tied to the emui version, but to the hardware, but I could be wrong. Is the requested data for 4.x wifi-only not available in your 5.0 emui?
adibadi said:
I thought that the unlock code isn't tied to the emui version, but to the hardware, but I could be wrong. Is the requested data for 4.x wifi-only not available in your 5.0 emui?
Click to expand...
Click to collapse
No the data is all available. The problem is that the Huawei website is not set up to provide a code for a wifi-only tablet that's on EMUI 5.0. It appears to be purely a problem with the website, not an issue with the code itself.
woody1 said:
No the data is all available. The problem is that the Huawei website is not set up to provide a code for a wifi-only tablet that's on EMUI 5.0. It appears to be purely a problem with the website, not an issue with the code itself.
Click to expand...
Click to collapse
What I meant was to just select emui 4 on the website.
Yes, it seems like that should work, but when I put in my data, I get a message saying that something is incorrect. Now that you mention it, I don't know how Huawei could know which version is installed. I wonder if the Product Number changes when you upgrade the EMUI version? Maybe that's the problem. Does anybody know about that?
woody1 said:
Yes, it seems like that should work, but when I put in my data, I get a message saying that something is incorrect. Now that you mention it, I don't know how Huawei could know which version is installed. I wonder if the Product Number changes when you upgrade the EMUI version? Maybe that's the problem. Does anybody know about that?
Click to expand...
Click to collapse
Not sure if it's the same thing, but I had to try a few times until the captcha worked, that thing was impossible to read. The error message said nothing about captcha, everything else was actually correct but it told me to check my serial numbers and stuff.
adibadi said:
Not sure if it's the same thing, but I had to try a few times until the captcha worked, that thing was impossible to read. The error message said nothing about captcha, everything else was actually correct but it told me to check my serial numbers and stuff.
Click to expand...
Click to collapse
If I put in a bad capcha, I get a message saying the capcha is wrong. If I put in the right capcha, I get a message saying "check your information" or something like that. Looks like the problem is not the capcha, but something else.
Hi all,
I'm on WAS-LX1AC432B184 and i can't update via OTA because "no update" and I think there's update as a friend of mine has the same phone but different build numbers as i needed to unlock my dual sim capability.
When i bought my phone i could only use 1 sim then i changed it to a dual sim. Can this be the reason why i can't get updates? The guy that did the dual sim conversion told me that i will be able to get updates as normal but i don't at all.
Please help me get the latest update so that i can enjoy the new Android – 8.0 Oreo
Hey there, by looking at your build number, you've got a 3GB RAM variant (LX1 instead of LX1A) Dual SIM (even build number) P10 lite on the global cust (C432).
The strange thing is the build number, stuck at 184 when Nougat arrived at B209/210 (Oreo is at B360/361).
Maybe you did some kind of modification (root, bad EMUI flash in the past) to the system so you can't receive official Huawei updates via OTA?
Have you tried clicking on the top right in System Update > Download latest full package?
Just some guesses here…
Probably, the you're huawei p10 lite dual is a branded? Usualy these models is the very slow for porting major release.
zYoshi said:
Hey there, by looking at your build number, you've got a 3GB RAM variant (LX1 instead of LX1A) Dual SIM (even build number) P10 lite on the global cust (C432).
The strange thing is the build number, stuck at 184 when Nougat arrived at B209/210 (Oreo is at B360/361).
Maybe you did some kind of modification (root, bad EMUI flash in the past) to the system so you can't receive official Huawei updates via OTA?
Have you tried clicking on the top right in System Update > Download latest full package?
Just some guesses here…
Click to expand...
Click to collapse
Hi zYoshi,
the download latest full package is greyed out... i have done a dual sim conversion in the past not sure if it was done correctly but i got it done... is there anyway i can fix this?
I want to get new updates for my phone to be honest.
sham_1 said:
Hi zYoshi,
the download latest full package is greyed out... i have done a dual sim conversion in the past not sure if it was done correctly but i got it done... is there anyway i can fix this?
I want to get new updates for my phone to be honest.
Click to expand...
Click to collapse
Hi sham_1
I sent you a guide wrote quickly in DM (for anyone who might need it, I left it here).
One quick question, now you have an even build number, right? That means that you are on a Dual-SIM firmware.
I suggest you to follow these steps and maybe wait some weeks because I did something similar too while Oreo was hitting Huawei's servers, but I received it only a month later, when the IMEI finally matched my firmware (the IMEI has to be approved in order to receive updates, suggest to "check firmware availability" on Firmware Finder).
"Hey,
I'm not so experienced in Huawei modding, but I managed to debrand my device from C55 to C432, so maybe it's worth a shot.
•
Anyways, try this:
- Download Firmware Finder from Play Store
- open it and click on WAS-LX1C432
- search for builds like B210 (must be an even number and not an Oreo B361, otherwise you can brick your device) choose a FullOTA
- click on update via proxy/DNS, follow the steps on screen
•
The important thing here is to know if the phone grants you into updating with that build, then failing in erecovery (detecting an error, no brick) so that you can reboot with not updated firmware and do a standard System Update from the settings, that update will contain the same build that you've got installed, but it will be used to basically overwrite everything without losing any data, even thought I suggest you to do a backup.
•
Before doing any of the steps I gave you, could you please describe me what you did, what method did you follow?
•
In this post, I am giving steps that worked for me when I had a corrupted firmware, but your problem may be different from this.
Check also the HWOTA method (to solve the same problem but with the warranty void, I suggest to use it only if the above method doesn't work), search "HWOTA P10 lite" on Google for more info.
•
Hope this helps
-zYoshi"