Related
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
Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.
ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse
rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse
TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?
dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.
nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM
back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...
nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?
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.
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
electrogiz said:
FINALLY! Still waiting for the Ota to hit my phone... Anyone gotten it yet? And I'm betting March's security update is going to be included too.
Click to expand...
Click to collapse
Just got the OTA notification!
electrogiz said:
Just got the OTA notification!
Click to expand...
Click to collapse
I'll wait until I can manually flash.
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Updating now!!!
dhorgas said:
Downloading it now. I will be really interested to see if they managed to address the stand-by bug that was causing excess drain and upgrade the modem firmware to improve connectivity. Those are the two main remaining issues with this phone. Hopefully they also implemented a method to force applications into full-screen, but I'm not holding my breath on it.
Click to expand...
Click to collapse
Already disappointed on the modem firmware front. No upgrade there. Also, no ability to force full-screen. Going to pass judgement on stand-by bug after 48 hour or so, unless obviously an issue.
The fact that it was not released to beta first makes me think it may just be an official release of the beta
crixley said:
The fact that it was not released to beta first makes me think it may just be an official release of the beta
Click to expand...
Click to collapse
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
dhorgas said:
I sure as hell hope not because the deep-sleep issue is horrible. You lose an average of 1.5-2h of actual SoT and the drain is regularly >1% per hour in stand-by.
Click to expand...
Click to collapse
Hopefully. SoT and Deep-sleeps issues were horrendous!
epicbeardman911 said:
I just keep getting an installation error, now I have a permanent notification telling me that the installation failed.
Click to expand...
Click to collapse
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
tanker666 said:
you are probably on Rooted device, or activate usb debug mode. Try to unroot if you are
Click to expand...
Click to collapse
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
E: Package is for source build essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but expected essential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys
Installation aborted.
Click to expand...
Click to collapse
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
GospelNerd said:
I am on 8.1b1 rooted. I flashed the stock 8.1b1 boot img to remove root. Then tried to sideload the 8.1 official OTA zip, and I get this:
Not sure what else I can try short of the full flashable build image once Essential posts it to their website.
Click to expand...
Click to collapse
I was in the same boat as you. I was on 8.1B1 rooted so I fastboot flashed the boot.img, then rebooted , downloaded the OTA which wouldn't install.
Went back to boot-loader, flashed the boot.img to both slots, rebooted, took OTA, and it still won't work. I get "couldn't update installation problem"
I didn't have an issue getting the last OTA, the same way.
I dunno
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
NaterTots said:
Edit: Mine just did a factory data reset on boot up. I think I'll be able to install the OTA now.....
Click to expand...
Click to collapse
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Wonder if Essential pushed it since Pixel is now offering pre release of Android P?
My radio has noticeably improved, instead of VZW its finally showing Verizon wireless. And the new developer options are nice
GospelNerd said:
Yea..not looking to start over.
The OTA I downloaded was off the reddit announcement thread. I'm assuming that guy pulled it off the device. Essential said they were going to post "sideloading files" also. So, I'm hoping that those are somehow different. (Otherwise why wouldn't they just throw a link up there)
Click to expand...
Click to collapse
My install wasn't working either at first (same boat as you guys, Magisk rooted with custom kernel). At first I just did a Magisk uninstall and reboot but it wouldn't install. Thought maybe I still had a custom recovery installed, but there was no TWRP in recovery. So, I just did a sideload install of the 8.1 beta using adb and then rebooted. That put me back on stock 8.1b1 and retained all my settings/data. Then I made sure my settings were correct in developer options (USB debugging, etc.), and it's finally installing. Not sure, maybe I just didn't hold my mouth right the first couple times, but it's working now.
Can anyone tell me if stable has multitouch issues that were on beta?
Rooted 7.1.1 took the update just fine, lost root and twrp
Looking at META_INF\com\android\metadata, it's expecting essential/mata/mata:8.1.0/OPM1.180104.010/144:user/release-keys but, based on the text at the top of the screen when sideloading, the device is at ssential/mata/mata:8.1.0/OPM1.180104.010/144:user/test-keys. Changing it is pointless, since META_INF\MANIFEST.MF contains a SHA-256 hash of of the metadata file. I'm going to try recomputing the hash and updating the OTA zip.
Edit: Didn't work. But has someone on reddit confirm Jank4AUs situation.