Database Info

[Q][A700] Post OTA Update Rooting.

After the recent update (AV043_A700_RV07RC06_PA_CUS1 / AV043_A700_1.029.00_PA_CUS1) which wiped unlocked bootloader and root.....
I've re-unlocked my bootloader. Had a few issues with system hanging, that I didn't have before, but it seems the unlock was a success as outlined in the thread by alx5962.
I'm not prepared to root again using method 2 (which worked just peachy, by the way) until I hear if the existing files/method will work with the new OTA firmware or if I would end up bricked.
Has anyone tried to root since the OTA?

ExtremeRyno said:
After the recent update (AV043_A700_RV07RC06_PA_CUS1 / AV043_A700_1.029.00_PA_CUS1) which wiped unlocked bootloader and root.....
I've re-unlocked my bootloader. Had a few issues with system hanging, that I didn't have before, but it seems the unlock was a success as outlined in the thread by alx5962.
I'm not prepared to root again using method 2 (which worked just peachy, by the way) until I hear if the existing files/method will work with the new OTA firmware or if I would end up bricked.
Has anyone tried to root since the OTA?
Click to expand...
Click to collapse
I was able to root the new update no problem with one of the scripts I downloaded here.
I can post it later after work if you want.
Its whichever one has the ICS Batch script in it that reboots your tablet into fast-boot, it worked.

Itchiee said:
I was able to root the new update no problem with one of the scripts I downloaded here.
I can post it later after work if you want.
Its whichever one has the ICS Batch script in it that reboots your tablet into fast-boot, it worked.
Click to expand...
Click to collapse
Yes, please. Post script if possible.
Please also let us know of any post rooting issues with the new update.

OK, I'll post it up when I get home.
I haven't noticed any issues, but then I haven't been really using it much since I got my Nexus 7 ♥
Edit - OK, I used the attached zip file, extract, right click the flash-ICS-patchedBoot.bat file and run as administrator.
Make sure USB debugging is checked on the tablet before running this file.

After you run the script it will boot the tablet into boot loader mode, it will copy over a few files, then the tablet will reboot with the script saying waiting for device, and will wait and wait... Once your tablet is up again it will have SuperUser installed, then you can install Busy box if you wish, or my fave Root Explorer, and the script will still be waiting for device... You can close it.

Yep, confirmed Method 2 still works. Hooray! Was a pain in the butt not having Button Savior.

TF700 - Lost OTAs

About the time JB was released I checked for an update not realising that it would go ahead without confirmation. As I didn't want to update just then I cancelled the download by clearing data in CM & DMclient (seemed to be the only way after turning wifi off).
Recently I just rooted (locked) using the debugfs method, after which checking for updates comes back with a zilch.
I tried clearing DM/CMclient data again and removing the update files :
fw_update_progress & isp_fw_progress
These had java errors in them presumably because I had aborted. After trying again they hold "0" and "100" in text format.
Finally on someone's recommendation I did a full factory reset (which worked for him) but I'm still without OTAs.
I'm hoping someone can shed some light on what may be the problem. AFAIK just rooting doesn't kill OTAs yet something has. Does Asus perhaps keep a database record as to what has been downloaded? I somehow doubt it but with a full factory reset I fail to see what's stopping these updates.
Any help , suggestions appreciated.

I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "

junrider said:
I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "
Click to expand...
Click to collapse
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.

louiscar said:
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.
Click to expand...
Click to collapse
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.

buhohitr said:
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.
Click to expand...
Click to collapse
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.

louiscar said:
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.
Click to expand...
Click to collapse
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.

buhohitr said:
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.
Click to expand...
Click to collapse
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.

louiscar said:
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.
Click to expand...
Click to collapse
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.

buhohitr said:
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.
Click to expand...
Click to collapse
Ok I will report here if I get anywhere with them. I somehow suspect that their support may not even realise or understand the issue but I will persist and see if I can get some kind of acknowledgment about their servers.

Well my OTA resumed after updating to JB so I think that it's as you state, the datebase on their servers. I don't know what the update was but your post in another thread would probably confirm this was JB .18. I guess once they have pushed an OTA, regardless of whether it was successful or not they don't seem to do it again. Which means I need to collect the dlpkgfile for each JB update given that I need to go back to ICS to do a proper factory reset and retain root.

Somewhat worried...

Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.

redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!

MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.

redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.

buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.

redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.

buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.

redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)

MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.

Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2

Used RootKeep but still lost root

Hello:
I'm trying to root my JB (.25) TF700. Yesterday, I was able to downgrade to ICS, root, temp unroot and then install JB (.25). But - after installing JB, the TempRoot was gone. What's up with that?
Here's my method:
From JB (.25), downloaded ICS (.30), extracted it to MicroSD and downgraded without issue. I tried to do this through factory recovery (Volume Down, release and then Volume Up); however, I'd get the Android+red triangle error. Instead, I just inserted the card on the home screen and the system pushed the downgrade itself.
Once I installed ICS, I rooted without issue. Downloaded RootKeeper, created backup and temp unrooted.
Then, here's were I went wrong probably, used the same method as stated above to install the JB (.25) firmware. I downloaded .25 from ASUS, extracted onto MicroSD and then inserted the card at home screen. The OS prompted the firmware update and JB was installed. I did create a TempRoot (backup) before installing JB.
Like I said above, JB installed but TempRoot was gone. I'm assuming that I used the wrong technique for upgrading to JB. But I always seem to get the Android + red triangle when I go through recovery mode.
Any ideas? Thanks.

-lukin- said:
Hello:
I'm trying to root my JB (.25) TF700. Yesterday, I was able to downgrade to ICS, root, temp unroot and then install JB (.25). But - after installing JB, the TempRoot was gone. What's up with that?
Here's my method:
From JB (.25), downloaded ICS (.30), extracted it to MicroSD and downgraded without issue. I tried to do this through factory recovery (Volume Down, release and then Volume Up); however, I'd get the Android+red triangle error. Instead, I just inserted the card on the home screen and the system pushed the downgrade itself.
Once I installed ICS, I rooted without issue. Downloaded RootKeeper, created backup and temp unrooted.
Then, here's were I went wrong probably, used the same method as stated above to install the JB (.25) firmware. I downloaded .25 from ASUS, extracted onto MicroSD and then inserted the card at home screen. The OS prompted the firmware update and JB was installed. I did create a TempRoot (backup) before installing JB.
Like I said above, JB installed but TempRoot was gone. I'm assuming that I used the wrong technique for upgrading to JB. But I always seem to get the Android + red triangle when I go through recovery mode.
Any ideas? Thanks.
Click to expand...
Click to collapse
OK, what's going on here is you're using the Asus full firmware upgrade which will wipe your root. You need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
It's a pain since you need to go one upgrade at a time -.30 then .16 then .18 you got the idea!

buhohitr said:
OK, what's going on here is you're using the Asus full firmware upgrade which will wipe your root. You need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
It's a pain since you need to go one upgrade at a time -.30 then .16 then .18 you got the idea!
Click to expand...
Click to collapse
Thanks. Can't do one firmware upgrade, darn. How many increments are there?

-lukin- said:
Thanks. Can't do one firmware upgrade, darn. How many increments are there?
Click to expand...
Click to collapse
To do it right, .16,.18,.20,.23,.25 ...total of 5, (unless you unlock your device). You may get away with just .16,.18, then .25.(bootloader is the same after .18). Your auto OTA is not working??

buhohitr said:
To do it right, .16,.18,.20,.23,.25 ...total of 5, (unless you unlock your device). You may get away with just .16,.18, then .25.(bootloader is the same after .18). Your auto OTA is not working??
Click to expand...
Click to collapse
Well, at ICS .25, I checked for OTA and there was nothing. Not sure how long I should be waiting. I've had problems with OTA in the past and just assumed I screwed the pooch somehow. Should I be able to OTA at ICS .25?
Thanks.

-lukin- said:
Well, at ICS .25, I checked for OTA and there was nothing. Not sure how long I should be waiting. I've had problems with OTA in the past and just assumed I screwed the pooch somehow. Should I be able to OTA at ICS .25?
Thanks.
Click to expand...
Click to collapse
Well, I suggest at the least you should do .16, .18 then .25, since it's incremental change, one change depended on the previous change so some stuff may not working correctly if you decided to skip.

buhohitr said:
Well, I suggest at the least you should do .16, .18 then .25, since it's incremental change, one change depended on the previous change so some stuff may not working correctly if you decided to skip.
Click to expand...
Click to collapse
Okay - I have found all the firmwares here http://forum.xda-developers.com/showthread.php?t=1946456and here http://support.asus.com/download/options.aspx?SLanguage=en. I will try to do the incremental upgrades - but the step by step process isn't exactly clear from the link provided above. For example, what is the first step with "WW_epad-user-10.4.4.16.zip"? Do I extract the blob and if so so where to? How is "dlpkgfile" involved? Thanks.

-lukin- said:
Okay - I have found all the firmwares here http://forum.xda-developers.com/showthread.php?t=1946456and here http://support.asus.com/download/options.aspx?SLanguage=en. I will try to do the incremental upgrades - but the step by step process isn't exactly clear from the link provided above. For example, what is the first step with "WW_epad-user-10.4.4.16.zip"? Do I extract the blob and if so so where to? How is "dlpkgfile" involved? Thanks.
Click to expand...
Click to collapse
Both links you provide are full stock firmware, not going to work. You need dlpkgfile only, can be found here http://forum.xda-developers.com/showthread.php?t=1926147
Just download them and make sure the final name is dlpkgfile (no extention, exactly like that).
also download command file and the name is command (exactly like that, no extention)
copy them these directories:
command goes to /cache/recovery
dlpkgfile goes to /cache
Make sure the files are named exactly as shown above. No capitals, no file extensions, etc.
Make sure the permissions for both files are changed to RW-RW-R for both.
This is how it should be after copied:
/cache/recovery/command
/cache/dlpkgfile
power off, then boot into recovery and wait a 10sec it should update. Remember if it failed or boot back into the OS, you need to verify if the two files still there, one of them will be erase and you have to recopy then do it again.

buhohitr said:
Both links you provide are full stock firmware, not going to work. You need dlpkgfile only, can be found here http://forum.xda-developers.com/showthread.php?t=1926147
Click to expand...
Click to collapse
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?

-lukin- said:
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
Click to expand...
Click to collapse
Yes, depend on how much upgrade, but they are much smaller around 14meg. Full firmware is around 455-485meg.

-lukin- said:
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
Click to expand...
Click to collapse
The dlpkgfile that updates from ICS to JB is almost 200 MB, the others are around 15 MB each.

buhohitr said:
Yes, depend on how much upgrade, but they are much smaller around 14meg. Full firmware is around 455-485meg.
Click to expand...
Click to collapse
We're in business. I've got ICS, rooted and JB .16 - now working on .18
Thanks for taking the time to help today
P.S. Never forget to unroot! That's how I got here in the first place. Cheers.

Not bad, you're a pretty smart guy after all.
Sent from my ASUS Transformer Pad TF700T using xda premium

Locking bootloader removes root? Also more Questions. [Phone Gone Now]

I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.

Superorb said:
I'm gifting my father in law an Honor 6X. I already unlocked the bootloader and rooted, but I'd like for him to be able to install updates when they're released. If I uninstall all the bloatware while rooted and then relock the bootloader, will root be retained? Will TWRP be removed? Will OTA updates be allowed? This is all on the stock ROM.
Click to expand...
Click to collapse
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.

BakedOnSomeSour said:
I believe you should be able to receive updates with the bootloader unlocked. The OTA might relock the bootloader and will most likely remove root. In order to update you will need to also have stock recovery installed so there would be no way for him to root again without unlocking the bootloader and flashing twrp.
Click to expand...
Click to collapse
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?

Superorb said:
Ok. He's clueless when it comes to even using stock phones, so I'll probably completely return the phone to stock and call it a day. Is there a thread floating around here to do relock, unroot, and completely return to stock?
Click to expand...
Click to collapse
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985

BakedOnSomeSour said:
https://forum.xda-developers.com/honor-6x/how-to/how-to-to-stock-emui-5-0-flashing-twrp-t3679985
Click to expand...
Click to collapse
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?

Superorb said:
That says it's for after you've flashed custom ROMs. I've never flashed a ROM on mine, only unlocked and rooted. Haven't even uninstalled any apps yet. Is there a quick way to relock and unroot?
Click to expand...
Click to collapse
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.

BakedOnSomeSour said:
Its also if you flashed twrp not only custom roms. You can uninstall root in the superSU app when selecting full unroot in the settings. I believe a factory reset can do it too. The next step would be to download the firmware for the phone and using fastboot to flash a boot and recovery image and then to lock the bootloader. Those steps are all in the link. That is the quickest way.
Click to expand...
Click to collapse
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.

Superorb said:
Damn, I was hoping it would be as easy as "fastbook oem lock" and be done with it.
Click to expand...
Click to collapse
Same. if you need any additional help with the process just let me know.

BakedOnSomeSour said:
Same. if you need any additional help with the process just let me know.
Click to expand...
Click to collapse
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.

Superorb said:
Thanks! Where can I find the EMUI 5.0.1 image? Mine is BLN-L24.
Click to expand...
Click to collapse
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.

BakedOnSomeSour said:
There's a PC application called firmware finder. https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
You can download firmware finder on your phone too and download the files from there. It's on the play store.
Click to expand...
Click to collapse
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.

Superorb said:
Ok, downloaded the Firmware finder and I have no idea how to use it. Directions don't make any sense and I have no idea what I'm doing after entering in my phone model.
I'm trying, but this phone is so different from my old LG G2 to play around with.
Click to expand...
Click to collapse
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.

BakedOnSomeSour said:
When you get into the Firmware Finder(PC) app youll notice your on a tab labeled "Main Page". Click on the tab labeled "common base" and type BLN-L24 into the search bar at the top right and then click on FIND. A list of firmware will pop up. Find the one that matches your build number and then click on the link under the "filelist" section. There will be two or three different zips you need to download. When you have the three downloaded let me know.
Click to expand...
Click to collapse
Ok, I've downloaded all 3 zip files from my build at over 2gigs.

Superorb said:
Ok, I've downloaded all 3 zip files from my build at over 2gigs.
Click to expand...
Click to collapse
Ok now extract the files from the update.zip folder. Then take the UPDATE.app from the extracted files and open it with update extractor: https://forum.xda-developers.com/showthread.php?t=2433454
After that your ready to follow the steps on the other guide.

So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?

Superorb said:
So I screwed up. Before you posted I unrooted via unSU flashable zip. Then I fastboot flashed boot and recovery to the stock one from the update.app file. Now it's got some verification error on power on and OTA updates fail. I tried moving the update.app to a dload folder on sdcard, but when it starts up it fails at 5% when restoring from the sdcard.
ETA: Tried the 360 FW which updated successfully. Booted and asked for password. After panicking shutdown and copied the HW contents to Sdcard and did the update again which succeeded. Booted and asked for password again and I panicked again. Pulled the Sdcard and booted into stock recovery. Wiped everything and then restarted crossing fingers. Started up like normal, no password request! So it looks like the phone is back on totally stock EMUI 5.0. I'll hope for the update and will try with fingers and toes crossed. Thanks for your help. I may be back, but hopefully not.
ETA2: There's no update option above the last About option in settings... How do I get the update option?
Click to expand...
Click to collapse
Edit: Before trying below steps. Just put the files from "BLN-L24_hw_usa"(b360) into dload folder and flash with dload. It might update the version.img without the needs for the steps below. if that brings the build number back to b360 use the hisui(PC) application to connect to the phone and update
Ok i forgot to mention something. The reason you dont have a update option is because you are on b360 which never had a button. Your build number on your phone will say b366 but thats incorrect. You cant receive an ota automatically because the phone thinks its already on the latest version. You need to take the UPDATE.APP from the "BLN-L24_hw_usa" (b360) folder and extract the VERSION.IMG file. It needs to be flashed with TWRP because fastboot wont work for some reason. That file will fix the build number and change it back to b360 so you can receive the OTA which will also restore the missing apps and features. That means you have to unlock the bootloader. Flash twrp. Flash the vendor.img with twrp and then do the dload method.
You have all the files and have done it already so this time will be easier. Ive done this way too many times with this phone. Sorry i forgot the mention the one step

Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.

Superorb said:
Build number on my phone is already 360, and it has never been 366. Tried flashing the 360 like you said via dload and nothing seems to have changed.
Also the SIMtray eject tool seems to just go into the phone without ejecting the tray. A paperclip worked, but man this phone is really frustrating.
Click to expand...
Click to collapse
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.

BakedOnSomeSour said:
Oh ok my build number always got stuck at b366. Try connecting with the HiSuite program and getting an OTA. And yes this is the strangest, most difficult phone to work with that ive ever owned.
Click to expand...
Click to collapse
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.

Superorb said:
Wife made me box it up and ship to her dad, so I no longer have the phone. I did install the HiSuite when I first powered on the phone and it was never able to connect and see the phone, so who knows what's going on.
Thanks for all your help. I have another one, but I'm just going to sell it and be done with it. No idea what other phone I can get with the same specs for the same price that's not so difficult to flash, but I'll keep looking I guess.
Click to expand...
Click to collapse
Its not difficult. In order to connect to hisuite you need to enable developer settings and allow usb debugging or type hisuite in the settings search bar and click "allow HiSuite to use HDB". I got this phone for christmas and i already know a ton about it. It may seem complicated now but its really nothing.