Related
Hi M3 users,
I'm a long time lurker and reader on XDA. Now it's time to give something back or at least participate
Following my recent M3 purchase a dugg a bit deeper into this topic and tried to get us the stock recovery for our devices.
I'm not really a dev. I just used the information I found here and in the russian forum where greatslon (thank you guy) is posting his work.
If you find an error in the process please let me know. The files have not been tested in any way. I have no idea if this would even work (encryption and so on).
So I managed to extract the recovery.img file from the chinese rom. This method will also work for the LTE variant.
Maybe @greatslon or @somboons can share their view on the topic or maybe @somboons can even use it in his tool.
Resources
http://4pda.ru/forum/index.php?showtopic=780572&st=120
http://forum.xda-developers.com/showthread.php?t=2433454
http://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146
https://play.google.com/store/apps/details?id=com.teammt.gmanrainy.huaweifirmwarefinder
Tools used
Huawei Firmware Finder (Team MT)
Huawei Update Extractor
Download
M3_BTV-W09C233B019_recovery.zip
Process
1. Start firmware finder (did use the android version)
2. Change device to BTV-W09C233
3. Downloaded the firmware B019 for BTV-W09C233 (no firmware for other variants present ATM)
4. Extracted and copied update.app to SD card
5. copy to PC
6. Extract recovery.img and recovery2.img using Huawei Update Extractor
Best regards,
Benjamin
Don't quite understand what's this for. First of all, recovery should be the same version as your ROM. I don't know if their mismatch will immediately lead to some malfunction, but some people on 4pda said they should match. Second - stock recovery's functions are limited to factory reset (wiping data, cache, etc.) and installing OTA updates. Without changing OEMINFO (and it's still unconfirmed), you won't be able to install any OTA except those, intented for your model and region, so again there's no need to install a higher version of recovery than your ROM is. But anyway, thank you for the extraction instruction.
P.S. I think there's no need to flash both recovery and recovery2. Recovery2 can be successfully replaced with TWRP and this combination is really great, cause you can launch TWRP by holding Volume Up button only.
And the only reason why you should keep recovery original is that it doesn't really wipe /data - it also creates some files there like custom.bin, containing your regional settings.
Hi Slavon,
Thanks for your highly appreciated comment. @somboons was looking for a stock recovery so I thought this might help.
Your given information are really helpful. I did not know that you could flash TWRP in recovery2 and replace erecovery Handy information.
I'm pretty new to the Huawei structure so always glad to learn something.
EDIT
A lot of good information can be found here: http://forum.xda-developers.com/honor-7/general/dual-recovery-honor-7-t3308398
Thank you very much,
sselpeelsxx
Giving Back
Benjamin,
I've also been a long time XDA lurker. Most of the devices I have owned were mainstream and thus already had a very active XDA developer community; Even if root had yet to be achieved, there would be hundreds of messages on the topic.
It seems the Mediapad M3 is just getting started. I am a developer of over 20 years, but very little android experience. However, I have recently spent a considerable amount of time (about 50-100 hours) working with the low level ADB protocol source code. And I have rooted and flashed no less than 50 devices, everything from cell phones to Android TV devices to routers.
I'm going to take this device on as my first real dev effort in this arena.
I have a few goals:
1. Get working backups for people that soft-brick or need to revert (including myself).
2. Recompile TWRP for the M3 to confirm greatslon's work, and better understand the process.
3. Release a stock rom that's pre-rooted and cleaned up (not that there was a lot of bloat on my device).
4. Release a custom rom that's not MIUI (perhaps based of CyanogenMod).
Since I have virtually no experience, I am sure these goals are quite lofty and will take some time. But hey, you got to have a plan, and I don't have anything else to work on right now.
Let me know if you want to work on anything together, or if you need any help with anything development related.
- 0D0A
Hey hey 0D0A,
I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work
Best regards,
Benjamin
can flash twrp via fastboot but get error saying and no recovery
hi, first thanks greatslon for doing the work on m3.
i seem to have succeeded in getting stuck and can't get it to boot into your custom twrp. adb on linux was working fine, but no longer. ditto for fastboot just get "waiting for devices" now. i switched to win10 and installed the hisuite app so i can use fastboot but still no adb. so i have tried to flash recovery and recovery2 but when i try to boot recovery i get error "Func NO: 11 (recovery image) ERROR NO: 2 (load failed)."
i then downloaded your custom rom and tried to flash the boot for that still no luck. i can't use adb so i am not sure how to just flash the custom rom with fastboot without being able to get into any recovery.
i did have this all rooted and working with your twrp but kept having issues with dpi and there was an ota update (b003) which wouldn't apply. so i tried to restore backup and it wen't south from there. basically now can't do much other than see the unlock "can't be trusted" page and bootloader.
any suggestions?
Desperately need stock recovery img, not sure exactly what when wrong, but it is stuck in a horrible boot loop. Tried Benjamin's recovery files and they seem to remove twrp and put it somewhat back to normal, but can only access the emui recovery and that fails to load the files. Put twrp back and tried greatslon's ROMs, they load but goes back to boot loop. Wipe and format everything, install my original backup through twrp recovery, it says it works, but again, back to boot loop... at this point I think I'm dead... any ideas, any word on the official recovery img? anything? Help!!
What device do you have? And what version were you on?
sselpeelsxx said:
What device do you have? And what version were you on?
Click to expand...
Click to collapse
I have the M3, BTV-W09, not sure what version, MM6.0 EMUI 4.1
Anyone have any other ideas on horrendous boot loop?
sselpeelsxx said:
Hey hey 0D0A,
I totally agree with you regarding the backups, I think once the first OTA update is pushed for the EU and US devices we have a good and safe way to go back.
Especially the US owners are struggling with greatslons TWRP version, that's the first thing we should tackle after the backup topic is cleared
I will contact you regarding possible work
Best regards,
Benjamin
Click to expand...
Click to collapse
Hello, I am unlocked, TWRPed, and rooted, but am trying to reverse all of that. My build number is BTV-W09C128B002. Is it safe to download the stock recovery from the OP for my device? Or do I really need the C128 version?
Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.
Regards
sselpeelsxx said:
Hello and sorry for the late response, you would need the matching version for your C128 device.
I may be able to extract recovery from an update, I have to look into this tomorrow.
Regards
Click to expand...
Click to collapse
Thanks! I have been able to use the Huawei Extractor to extract a recovery.img from OTA updates, but have been afraid to try flashing it. It has been recommended to hold off on trying that since that recovery.img is from an OTA and not a FULL update. Any thoughts?
Does anyone have or know where to get a stock recovery image for the BTV-W09?
When I flashed the US "003" update manually through the dload folder method, my TWRP was replaced by the stock recovery. I have left it there, and since flashed TWRP to recovery2. The update failed, but I ended up with stock recovery and the tablet no longer rooted. I would try that first. If that doesn't work for you and if you are on the US version "002" firmware let me know and I should be able to send you a backup of my recovery partition bit if you need the eRecovery from the recovery2 partition, I will be unable to help you.
I am on the US version “003”, I updated before flashing TWRP and rooting. TWRP was flashed recovery not recovery2. No worries though, Im sure someone will post a recovery as rooted people will be needing to flash OTA updates soon.
If you are on "003", try updating the unzipped "Update.Zip" from the dload file. I found a copy of the update.zip on my internal SD in directory called HwOUC. If you can't find it, I still have my file. The Update will most likely fail, but that should give you the standard recovery back. then I suggest you flash TWRP to Recovery2. TWRP actually is easier to access from Recovery2 becuase all you have to do is hold the volume up key down for a few seconds from the unlocked bootloader screen to boot into TWRP. Once you have TWRP re-installed you can then just flash the super user zip file to regain your root.
I am not sure if it is because I now have unlocked the bootloader, have recovery2 with TWRP or updated the file to enable the 5Ghz modem , but even with having the standard recovery partition back my system did not pass the altered system check and allow me to flash the OTA. I am not quite experienced enough to try and use Flashfire to force the update, since there is a warning about Huawei devices being easy to hard brick. Hopefully someone who has updated and then rooted will post an .img file of the updated system partition so it can be flashed with TWRP (at least I think that is what those of us who have already rooted will need to do).
I looked for the update.zip but it doesn’t exist anywhere. These updates are usually removed after the update completes successfully. Plus I’ve done a factory reset since updating, which may have deleted it. I wanted to see if enabling the 5GHz radio would stick after the reset (it did). The 5GHz radio hack was really my only reason to root. I didn’t alter my system partition with TWRP, so I may still be able to take an OTA update if I had the factory recovery. Ive stopped rooting all of my non Nexus devices. Since Google releases almost monthly security updates which usually unroots anyway it’s just too much hassle to keep root. If you want to post the update.zip somewhere I could give it a try, if not that’s cool. Im sure a factory image will be available at some point.
I have posted the Update.zip file to the following location:
http://www.mediafire.com/file/ug1pe2w38ddkxm9/update.zip
Let me know how things go.
Coming from a Nexus 7 I'm use to many of the img files you flash for restoring.
Using update extractor I now see many of those files (003 update) and some I have no idea about or how to flash them.
BOOT.img - OK
CRC.img - ?
CURVER.img - ?
EFI.img - I know what EFI is just never flashed it on an Android device.
FASTBOOT - OK
FW_HIFI.img - ?
FW_LPM3.img - ?
RECOVERY.img - OK
SENSORHUB.img - ?
SHA256RSA.img - No what it is normally but never flashed.
TEEOS.img - ?
TRUSTFIRMWARE.img - Interesting, but have no idea. - ?
VERLIST.img - ?
XLOADER.img - ?
Like many of us I'm in the same boat. Unlocked, Flashed recovery and rooted and cannot install update 003.
I've flashed the recovery.img from update 03. I've done a factory reset a few times. Odd enough it maintains 5Ghz wifi after doing a reset. I'm stumped and not sure of so many of the other .img files. Might one of them help me get the update to pass if I flash it. That or we wait for a full release and not an OTA to grab all the files we need. Really think I need system.img to make it work but the update doesn't include it.
Thanks johe for providing the 003 update.zip. I may try flashing the recovery.img this weekend. Ill let you know how it goes.
Jmjm003, I believe the issue with updating with the OTA is due to changes detected in the system partition after rooting/unlocking. Im not sure of a way around this other than flashing the full system partition, and we don’t have the factory ROM available yet. Im also new to Huawei devices and their partition structure so hopefully the development community will grow around this device and provide better solutions. I also can confirm the 5GHz stayed enabled after a factory reset, the question remains would it hold after an OTA update.
So, since once a month I find myself having to click a bunch of links and read how to do a bunch of commands, I wanted to create a thread that (rather generically) explains how to manually flash the OTA monthly updates if you're rooted with Magisk. So, minimally, here's a thread for me to review every month... if it helps you all out, all the better!
Pre-requisites:
Download Latest OTA zip file from Google.
Obtain the STOCK boot.img (required) and dtbo.img (optional) of the System ROM you are currently running. This can be done if you already have the full System Image file downloaded, downloading it currently, or just obtaining the stock boot and dtbo image files elsewhere. (NOTE: This can be skipped if you successfully uninstall Magisk BEFORE you start the process and choose to restore the Stock images in the uninstall process.)
Download Latest Magisk Zip file
Download latest TWRP recovery image
If applicable, have latest USB drivers, adb/fastboot/ files etc.
Preparation:
1) Extract or open the Full Image file and locate the boot.img and dtbo.img files. You will want these on your PC in the platform-tools folder (I usually put the Month name at the beginning, ex. - Jan_boot.img). Again, you can skip if you successfully uninstall Magisk prior to all of this.
2) Copy your OTA zip file to the platform-tools folder, again naming it after the month helps (ex. - Feb_Pixel2XL_OTA.zip)
3) Put your TWRP recovery in platform-tools folder.
4) Place the latest Magisk zip on your Pixel's internal storage (what used to be the SDCard on phones so equipped).
Commands:
1) From PC, open command prompt and change directory to your platform-tools folder.
2) If your phone is on, "adb reboot bootloader" If powered off, press power and Vol Down button to get to Bootloader. Plug your phone into your PC.
3) [If Magisk is not uninstalled first] Command: fastboot flash boot {Name_of_boot.img File}
4) [If Magisk is not uninstalled first] Command: fastboot flash dtbo {Name_of_dtbo.img File}
5) On your phone, hit Vol Down until you see Recovery, then press power button.
6) Once in recovery mode, press power and Vol Up to bring up menu
7) Scroll to item: "Apply update from ADB" and press power
8) Command: adb sideload {Name_of_OTA.zip file}
9) After the OTA finishes flashing, exit recovery back into the Bootloader
10) Command: fastboot boot {twrp_filename.img}
11) Install Magisk Zip file (and any other Zip files you want installed... Kernels, etc.) within TWRP
Then after flashing your zip files, reboot to system and you should be all set.
I believe everything above is correct, but if I've made a glaring mistake, please let me know. I also realize there may be other methods to this madness, but this is what works for me.
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
uofirob said:
With this method do you have to worry about removing your password from your phone before you try to go into twrp?
Click to expand...
Click to collapse
Yes. Mine is set to pin, which I had to put in and it let me finish.
Sweet. I'll give this method a try tonight!
WorldOfJohnboy said:
Yes. Mine is set to pin, which I had to put in and it let me finish.
Click to expand...
Click to collapse
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
So I did this, and now I'm bootlooping. I guess I'll re-flash the Jan factory image and wait a little longer... **UPDATE** I fixed the bootloop by re-trying the process again (after re-verifying the MD5 hash on the update.zip. I rebooted after installing the update,
but before the TWRP flash to install MAGISK. Maybe this allowed the "update"
to finish processing. I also had to remove the pin from my lock screen in order to allow me to get into twrp. After rebooting into the system and removing the pin, I adb reboot bootloader and then flashed twrp. Thanks for the guide!
---------- Post added at 07:58 AM ---------- Previous post was at 07:50 AM ----------
PuffDaddy_d said:
I believe you also need remove the -w from the end of the .bat file after you extract the OTA; otherwise, all of your data will be wiped.
But great job of getting all this info in one place!
Click to expand...
Click to collapse
You don't need to remove the -w from the .bat file since you aren't using it at all to do the update. That is only if you're flashing your factory image.
Fe Mike said:
Thank you for this. Just to be clear in step 2 under prerequisites you say more on this later. Then in step 1 for preparation you prefix your boot and dtbo with Jan xx.img. I get what your saying, but for the newer noobs they may get confused. Maybe reword to say, extract or open the factory image your currently using or the previous months image. Obviously you do this first so that you can sideload the ota. I don't mean any disrespect.
Click to expand...
Click to collapse
I changed some wording under prerequisite...
I agree with everything on this guide...
just teasing...
I'm actually glad you created this thread...I wanted to create one also and try and help out as much as I could, but I don't have the cahones and didn' t think I had experience enough to start a "guide" thread :silly:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
Well...I can't speak for the OP, but I wrote my extremely similar identical one because, for whatever reason, many users would choose OTAs over flashing full factory images. I/me & you understand the benefits of the factory images over the OTAs; especially understanding the process you must go through to install the OTAs as-of-current is almost the same as flashing the factory images anyways...
But if I were to give a possible explanation to their reasoning is that, like many of them, I come from a non-Google phone (S5 for me), and OTA's were simpler, takes less bandwidth (which still remains true today), they were significantly simpler to install vs. factory images, and with a lot of popular phones you only flash factory images to recover your phone; i.e. muniz_ri's OTA's for the S5 and FlashFire were loads simpler than flashing a whole factory image. But, again, understanding the difference for Pixel 2 and Oreo's OTA & factory images (or the small difference thereof), it's probably better to do a few extra steps and/or downloads to do the whole image than sideloading an OTA.
In the end, this is for people who insist for OTA updates most likely because that's how they are familiar (and therefore more comfortable) with; whether it being explained to them or not...
Cheers!:good:
Fair enough, thanks for the input!
CyberpodS2 said:
I mean no disrespect, but this seems awful complicated compared to just flashing the full image with the removed (-w). Especially since your downloading it anyway. I do that then boot the TWRP image and flash the TWRP zip. Reboot into recovery and flash kernel and magisk and reboot system. Again I'm asking for clarity, not dumping on you. Great write up btw!
Click to expand...
Click to collapse
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
WorldOfJohnboy said:
It may seem awful complicated, but to be honest, to me is less complicated than having to edit a script file (which if you forget to do, will lose all of your data). Also, though the steps I wrote out seem like a lot more if you were to write out a process using the full image, it actually works out to be almost the same number of steps.
Lastly, as someone else hinted at, the OTA file size is smaller. The only full image you need is what you are currently running (which in most cases I have on my phone in case the sh__ hits the fan with my phone), not the new full image. (To be even more precise, you only need the boot.img and dtbo.img from the full image file--there may be places to get just those two files out there.)
As I put in the last sentence, I realize there are other methods to this madness, this is basically what works for me. I wanted to get it in writing so I wouldn't forget this down the road, and if it helps anyone here, just icing on the cake. Clearly I'm no Dev and not forcing anyone to perform the updates this way!
Click to expand...
Click to collapse
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up ??
Badger50 said:
Hey bud, wonder I I could pick your brain just a little. When doing monthly Google updates, are most of their proprietary files located in the boot, dtbo, and vendor images?? Your posts have intrigued me a little, and are very well written BTW. My reasoning is this. On my old 6p, about all we needed to do was flash the new vendor, and of course the bootloader and radio if there were any worthwhile improvements. Would the same possibly apply to the P2XL?? I'm just wondering because, now that we're starting to see custom roms, if this would be a viable option, and simplify the updating process. Thank again for your great write up
Click to expand...
Click to collapse
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
WorldOfJohnboy said:
I'll be perfectly honest with you, I haven't taken a dive to see what is in the OTA files and would imagine that it varies depending on the monthly updates.... that said, the only reason why I have stated to re-flash the stock boot.img is because if you are rooted with Magisk, it takes the stock boot.img and modifies it. In order to take an OTA sideload, you need to be on stock boot.img and stock recovery. dtbo is only in my process because there was one time when I tried to sideload and my dtbo wasn't stock (or corrupt). You may not need to flash the stock dtbo.img, but it doesn't hurt to do so.
Click to expand...
Click to collapse
I'm really happy to see our device has graduated to this level of discussion, instead of the random guessing and 14 different "possible" routes to a solution. Lol
Custom roms abound, once TWRP gets squared away and someone master's the art of turning monthly updates into zip installs we'll pretty much be there!
Btw OP, great write up... Clear and precise!
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Brenneke said:
I do not understand the purpose for downloading the full system image and then flashing only the OTA zip - what am I missing? There is a widely distributed method for performing monthly OTA updates by uninstalling Magisk, updating OTA normally, then flashing Magisk again - seems much simpler, any reason why it would not work?
Click to expand...
Click to collapse
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
WorldOfJohnboy said:
Downloading the full system image is not required. You only need the Stock versions of boot.img (required) and dtbo.img (optional) of the ROM version your phone is currently running. I actually keep a full system image on my phone in case something goes awry.
I'm going to update the OP to more clearly state that you only need the stock boot.img file--how you obtain it is up to you. Uninstalling Magisk will do the same exact thing, however I tried to do that a couple of months ago and it created more issues for me than if I had just flashed the stock boot.img in the first place.
Click to expand...
Click to collapse
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Brenneke said:
I have not tried the uninstall Magisk method but plan to do so at next update. What kind of issues did it create for you?
Thanks.
Click to expand...
Click to collapse
For some reason, I don't think it restored the correct (or not corrupted) boot.img version. Then, there were remnants of the Magisk APK and other files so I ended up having to do a full TiBu of my apps and flashed (with wipe) a full System image. It may have been something I did or just my bad luck, but I prefer not to chance it and instead manually flash the Stock image as my "guide" here states.
Does anyone know about this ?
The last version of the firmware that got OTA'ed to my phone is POTTER_RETAIL_7.0_NPNS25.137-93-8.
The only twrp backup of the firmware I have is while it was on POTTER_RETAIL_7.0_NPNS25.137-93-4.
When I tried to flash the phone with v 93-4 using fastboot, I got denied because of the version being older than that of the bootloader. But the problem is that I was able to erase prior to attempting writing ...
I need to re-install a stock rom in the phone, but POTTER_RETAIL_7.0_NPNS25.137-93-8 cannbot be found anywhere yet.
I though about twrp-flashing the phone with my 93-4 backup, but I am hesitant, I fear bricking the phone.
Is there any alternative to patience while waiting for POTTER_RETAIL_7.0_NPNS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip eventually appearing somewhere ?
Or, in other words, knowing that the last OTA to my phone installed v 93-8, is there any way to flash POTTER_RETAIL_7.0_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip for instance ?
CanadianGixxerman said:
I though about twrp-flashing the phone with my 93-4 backup, but I am hesitant, I fear bricking the phone.
Click to expand...
Click to collapse
An older version (your twrp backup) will work with a newer bootloader, however you can't do any OTAs. An OTA will try to apply the same changes to the bootloader that were already made, resulting in a hard brick - though the OTA would fail anyway since you don't have an intact /oem partition. You will have a functional phone, and you can get back on track after 93-8 images or Oreo are released.
I know because I'm in a similar situation. I wanted to update from 93-4 to 93-8, and I had an intact /system image backup, but /oem was mounted before so I had to flash it via fastboot. Little did I know it was from the wrong channel (retus instead of reteu), resulting in the OTA updating everything except for oem and messing stuff up, so I just flashed a 93-4 twrp backup. Everything works, patiently waiting for Oreo.
bazinga137 said:
I just flashed a 93-4 twrp backup.
Click to expand...
Click to collapse
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
craigl14 said:
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
Click to expand...
Click to collapse
Honestly, I am not sure. I did a twrp back up with the default selected partitions. But it turned out that this backup is not reliable. The phone does boot up on it, but suffers from applications crashes all over. Last I discovered is that the phone itself was not working for a phone, meaning making receiving calls is not possible.
craigl14 said:
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
Click to expand...
Click to collapse
It needs to be an image backup for OTAs. Unlike a regular backup, image backups are block-by block pristine copies, and restoring them preserves dm-verity and all /system checks. On the other hand the /oem partition cannot be backed up as an image (I asked GtrCraft, the official maintainer of twrp for some moto devices), and since OTAs also check if /oem has been tampered with, the update fails.
Updates will only pass if /oem has never been mounted, and you have a system image backup.
bazinga137 said:
It needs to be an image backup for OTAs. Unlike a regular backup, image backups are block-by block pristine copies, and restoring them preserves dm-verity and all /system checks. On the other hand the /oem partition cannot be backed up as an image (I asked GtrCraft, the official maintainer of twrp for some moto devices), and since OTAs also check if /oem has been tampered with, the update fails.
Updates will only pass if /oem has never been mounted, and you have a system image backup.
Click to expand...
Click to collapse
Dumb question...How do I know if the oem partition is tampered with or has never been mounted? I am rooted with elementalx kernel and supersu. TWRP partition stock backup made immediately after taking 93-8 update and before flashing twrp, rooting, etc. I know I am hosed without the system IMAGE as far as ota's go, but I'm just trying to learn.
I'm in the same boat. Pretty much stuck on 93-8 forever until a new full image is released somewhere. I might just move onto a custom Oreo rom.
dunderball said:
I'm in the same boat. Pretty much stuck on 93-8 forever until a new full image is released somewhere. I might just move onto a custom Oreo rom.
Click to expand...
Click to collapse
Well, I did that. I have tried a few cutom roms : Pixel Exprerience, Resurection Remix, AOSP extended, AOSiP and Dirty Unicorns. The latter and AOSiP are those I find the most reliable. Avoid PE and RR, too buggy, AOSP-E has issues with SIM/SDcard here.
But I will want to go back to stock moto rom when I can (ie : full 93-8 load fastboot flashable is released).
If moto had been quicker to release Oreo AND fix the wifi bug, I would not have given up on retus.
I guess I have an even more fundamental dumb question than my twrp restore issue and maybe it belongs in another thread. Aside from advanced excel formulas, I have no programming experience of any kind, let alone android. However, it seems to me that if I have a full firmware package for 93-4 (which I do) and a "blur" ota update file that takes it to 93-8 (which I do), I should be able to create a full 93-8 firmware package file myself from those two files without waiting on the file hosting sites. Maybe this is way too advanced a process but it seems to me this is 1+2=3 variety.
craigl14 said:
I guess I have an even more fundamental dumb question than my twrp restore issue and maybe it belongs in another thread. Aside from advanced excel formulas, I have no programming experience of any kind, let alone android. However, it seems to me that if I have a full firmware package for 93-4 (which I do) and a "blur" ota update file that takes it to 93-8 (which I do), I should be able to create a full 93-8 firmware package file myself from those two files without waiting on the file hosting sites. Maybe this is way too advanced a process but it seems to me this is 1+2=3 variety.
Click to expand...
Click to collapse
Your device now being at 93-8 is what's in the way. It seems like you can restore your twrp 93-4 on it, but you won't be able to relock the BL, hence OTA will not work.
CanadianGixxerman said:
Your device now being at 93-8 is what's in the way. It seems like you can restore your twrp 93-4 on it, but you won't be able to relock the BL, hence OTA will not work.
Click to expand...
Click to collapse
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
I'm on a slightly same boat as OP, but I don't have my backup since I thought it was on my SD and wiped my phone, with the backup only there. I was on 93-8 when I wiped. Would getting a 93-4 backup work?
This question might of been answered but I did not see it when I read through this thread.
craigl14 said:
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
I took a full backup of my system image through twrp, and I was on 93-8. I'll upload it when I have time and you can give it a try.
CanadianGixxerman said:
[...] but you won't be able to relock the BL, hence OTA will not work.
Click to expand...
Click to collapse
Why would you need to relock the BL to take an OTA?
craigl14 said:
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
Sadly you can't apply an OTA to the firmware images, if that's what you're thinking. They need to be signed by moto to be flashable through fastboot. And if you'd want to provide someone with a twrp backup of a firmware higher than theirs, their bootloader would need to be updated too, via an OTA.
bazinga137 said:
if that's what you're thinking.
Click to expand...
Click to collapse
Thanks. That's exactly my question. So the answer is that Motorola controls the process. Makes sense. Any thoughts on my oem mounting question?
craigl14 said:
Thanks. That's exactly my question. So the answer is that Motorola controls the process. Makes sense. Any thoughts on my oem mounting question?
Click to expand...
Click to collapse
I really can't think of a way of checking the mount count of Android partitions, and I haven't found anything online.
I discovered the mount counter thingy when sweeping through logs of a failed OTA. I'm really not sure where the OTA script reads it from.
craigl14 said:
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
I made a full backup of 93-8, but still i can't lock bootloader. We need complete firmware, until then, Lineage OS is the answer.
---------- Post added at 11:55 PM ---------- Previous post was at 11:52 PM ----------
bazinga137 said:
Why would you need to relock the BL to take an OTA?
Click to expand...
Click to collapse
No idea, i saw this first time now on Motorola. On any other manufacturers i could lock bootloader, and even get OTA updates just by flashing stock recovery and having unlocked bootloader was not a problem.
If your device was formally updated to NPNS25.137-93-8 (March 2018 security patch), then you could try to flash the NPNS25.137-93-4 (Jan 2018 security patch) update again as you previously tried (link to the Jan 2018 stock firmware for EU/US and Asia devices: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ ). You may wish to ignore the security downgrade errors (you cannot downgrade bootloaders anyway, presumably to prevent you opening security vulnerabilities) when you flash, which should just be for GPT and bootloader. You may also see 'image signed with bad key' for recovery and boot as well, but verify those partitions, and the other partitions report [OKAY] after flashing. That way, you should have a NPNS25.137-93-4 system, with a NPNS25.137-93-8 bootloader, and when you boot you should have a device reporting with fully stock NPNS25.137-93-4. The next OTA you should receive is the NPNS25.137-93-8 OTA and then the NPNS25.137-93-10 April 2018 security patch OTA, which should bring you up to the latest stock firmware.
By reflashing the NPNS25.137-93-4 firmware, this should also restore your OEM partition to being untampered (read only status?), as should your system partition (which should be read only, I recall that swiping to allow modifications in TWRP sets your system partition to read-write, which causes the OTA to fail).
Normally, I would advise against downgrading and using OTA updates, as this is a prime way of hard bricking. However, in this case you are downgrading your device firmware to the firmware directly preceding the newest firmware you had (i.e. downgrading to NPNS25.137-93-4 from NPNS25.137-93-8), with the next OTA being NPNS25.137-93-8, which brings you back up to the build you had, this may be safe. To your device, you are flashing the same bootloader from the NPNS25.137-93-8 OTA as currently on your device, which should not hard brick.
If you previously had stock NPNS25.137-93-10, then I cannot recommend this procedure as you'll be downgrading two firmware versions (and you'll have to wait for newer stock firmware to be leaked), else if you try flashing NPNS25.137-93-4 onto the April 2018 firmware and try using OTA updates, you may hard brick and have a pricey paperweight. I also do not know if this will work by cross-flashing from the NPN25.137-92 series of updates either.
Of course, as the NPNS25.137-93-4 firmware is older than your bootloader, you will not be able to re-lock your bootloader (you'll need a newer firmware, probably the April 2018 or newer security patch stock firmware), but being back on full stock, you should be eligible for OTAs provided you only downgraded from NPNS25.137-93-8 (and that March 2018 security patch was the latest stock firmware on your device).
If you are truly concerned about hard bricking, then I would follow other member's suggestions in this thread and stay with TWRP flashables of the stock ROM, as they do not usually affect the bootloader.
Any questions or comments before you perform this procedure, please ask.
bazinga137 said:
I really can't think of a way of checking the mount count of Android partitions, and I haven't found anything online.
I discovered the mount counter thingy when sweeping through logs of a failed OTA. I'm really not sure where the OTA script reads it from.
Click to expand...
Click to collapse
Thanks. Weird. Sorry for hijacking this thread. But if my process were to take OTA after which it reboots, then IMMEDIATELY reboot into bootloader, fastboot BOOT into twrp (not flash it) and take a backup of boot, logo, oem, recovery and system (FULL IMAGE), how would that change oem?
CanadianGixxerman said:
Well, I did that. I have tried a few cutom roms : Pixel Exprerience, Resurection Remix, AOSP extended, AOSiP and Dirty Unicorns. The latter and AOSiP are those I find the most reliable. Avoid PE and RR, too buggy, AOSP-E has issues with SIM/SDcard here.
But I will want to go back to stock moto rom when I can (ie : full 93-8 load fastboot flashable is released).
If moto had been quicker to release Oreo AND fix the wifi bug, I would not have given up on retus.
Click to expand...
Click to collapse
What's buggy about PE? I was just about to try it...
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images.
I have access to a 10.1 with keyboard (ONA19TB007) and without (ONA19TB003) that I can pull updates and images from, but I do not have access to the 8" (ONA19TB002) or newer 7" tablet. Any assistance with those two would be welcomed :good:
Onn 10.1" without keyboard - ONA19TB003
OTA
20191015-1827
Stock Images
October 2019
Full (Thanks @CaffeinePizza!)
Boot
Recovery
VbMeta
Vendor
System
May 2019
Full (Thanks @CaffeinePizza!)
Onn 10.1" with keyboard - ONA19TB007
OTA
20191011-1212
20190516-1437
Stock Images
October 2019
Boot
Recovery
Vendor
VbMeta
System
May 2019
Boot
Recovery
Vendor
VbMeta
System
Onn 8" - ONA19TB002
OTA
November 2019 (Thanks @martyfender)
July 2019 (Thanks @tek3195)
Stock Images
November 2019
Full (Thanks @CaffeinePizza!)
May 2019
Full (Thanks @CaffeinePizza!)
Onn 7" Surf - 100005206
OTA
November 2019 (Thanks @tek3195)
Stock Images
October 2019
Full (Thanks @deadman96385!!)
June 2019
Full (Thanks @deadman96385!)
*Reserved
NFSP G35 said:
Since these tablets don't have an external online resource for downloading system updates, only a sketchy OTA app (com.adups.fota) I'm collecting a library of OTAs, as well as boot/recovery/system images.
Click to expand...
Click to collapse
I discovered that running the following command
Code:
pm uninstall -k --user 0 com.adups.fota.sysoper && pm uninstall -k --user 0 com.adups.fota
withing adb shell will disable the over the air updates.
I do not know if there is any truth to this, but Malwarebytes has an article on this, claiming that the software can be used to collect user data so I chose to disable it.
^ yep. I ran across a lot of worrysome information about that software. I figure I can 'take one for the team' and leave it enabled on mine, and collect updates here.
That way, if anyone wants to update while leaving com.adups.fota disabled or uninstalled, now they will have a way to do so
NFSP G35 said:
^ yep. I ran across a lot of worrysome information about that software. I figure I can 'take one for the team' and leave it enabled on mine, and collect updates here.
That way, if anyone wants to update while leaving com.adups.fota disabled or uninstalled, now they will have a way to do so
Click to expand...
Click to collapse
I am repeating some information I previously stated since we now have a section specifically for this:
I am sure @CaffeinePizza would not mind, he posted stock roms in this POST. Maybe a link to this information in the OP will help people looking for a STOCK rom for the 8' and 10' devices. The images he is hosting are patched to April 5, 2019. Anyone wishing to flash these images will need the SP Flash tools.
OTA for 8" ONA19TB002 https://drive.google.com/file/d/10vFETRunJEkyZXGUV05-rmJy60qrnSuy/view?usp=sharing
I can not remember date but somewhere around July 2019.
tek3195 said:
OTA for 8" ONA19TB002 https://drive.google.com/file/d/10vFETRunJEkyZXGUV05-rmJy60qrnSuy/view?usp=sharing
I can not remember date but somewhere around July 2019.
Click to expand...
Click to collapse
Thanks! Added to the OP
I guess this would be the place for the 7" SURF OTA's to reside for now ? Here is ota for Onn 7" Surf Model 100005206 downloaded 11/7/2019 have not installed yet so don't have security patch date.
https://drive.google.com/file/d/1U77dxYgO-ihbO1XP6c8AiEnEtUlJRcfI/view?usp=sharing
tek3195 said:
I guess this would be the place for the 7" SURF OTA's to reside for now ? Here is ota for Onn 7" Surf Model 100005206 downloaded 11/7/2019 have not installed yet so don't have security patch date.
https://drive.google.com/file/d/1U77dxYgO-ihbO1XP6c8AiEnEtUlJRcfI/view?usp=sharing
Click to expand...
Click to collapse
Thanks!
Added to the OP along with a couple of images from the 007.
More to come once I can get them uploaded.
Random OT... I just noticed you're in PC... Hi from Tallahassee!
Maybe we should have a thread on sptools too... I still need to read up on mtk told but there are so many...
You're welcome to reference my thread and post a link to my server with the x003 and x002 stock images. SP Flash Tools is needed.
https://forum.xda-developers.com/showpost.php?p=80574967&postcount=192
https://www.nathanbar.net/files/android
I plan on making a proper thread, perhaps this weekend, on how to backup with Wwr, and flash with SP Tools. I will try to upload updated images from the newest OTA.
I may even make a blog post with photos on my site.
Can the Onn 8 update.zip be flashed in TWRP, or must it only be flashed in spflashtool?
Thanks
UPDATE:
I tried both ways and neither works. How does one apply this update.zip? Do I need to reflash the stock recovery and apply it there?
I copied the update.zip to:
Code:
/storage/emulated/0/Android/data/com.adups.fota/files/fota
When I go to settings,system, about tablet, wireless Update, local updates, I navigate to where the update is and if I choose update.zip,: make sure the file is official, it states it may wipe your data and will reboot to recovery to install. (which I assume needs to be the stock recovery?)
I, of course do not want to do this until I hear from someone who can clarify all of this: @tek3195
Thanks
martyfender said:
Can the Onn 8 update.zip be flashed in TWRP, or must it only be flashed in spflashtool?
Thanks
UPDATE:
I tried both ways and neither works. How does one apply this update.zip? Do I need to reflash the stock recovery and apply it there?
Click to expand...
Click to collapse
To my knowledge, it has to be flashed with the stock recovery
NFSP G35 said:
To my knowledge, it has to be flashed with the stock recovery
Click to expand...
Click to collapse
Yeah, it has to be stock recovery and can be done with adb sideload or update from sdcard. I haven't tried yet but it may be able to be repacked and flashed with TWRP. I know as it sits now the compatibility.zip is of wrong format to be flashed. It's a possibility, but something that would have to be done at each update. Also, regardless of how installed will it re-lock bootloader or erase /data? Some brands do. I don't know mine was already wiped before the update.zip. Just installed it from sdcard and says success although two errors at end. loader1 & loader2 could not read misc-sd, unable to set boot part. Find out in a few if relocked.
Okay,cool. The ota when installed manually did not re-lock the bootloader.
tek3195 said:
Yeah, it has to be stock recovery and can be done with adb sideload or update from sdcard. I haven't tried yet but it may be able to be repacked and flashed with TWRP. I know as it sits now the compatibility.zip is of wrong format to be flashed. It's a possibility, but something that would have to be done at each update. Also, regardless of how installed will it re-lock bootloader or erase /data? Some brands do. I don't know mine was already wiped before the update.zip. Just installed it from sdcard and says success although two errors at end. loader1 & loader2 could not read misc-sd, unable to set boot part. Find out in a few if relocked.
Okay,cool. The ota when installed manually did not re-lock the bootloader.
Click to expand...
Click to collapse
Yes, I re-flashed the stock recovery and booted to it. I attempted to flash the update.zip from there, but there was some error that it was not and official verified file.
Keep in mind that is not what it stated, I am just relaying a very vague, poor memory version of what I saw then.
I tried to restore the just released, twrp version in fastboot in linux, but had errors, so I booted to Windows 7 and reflashed the just released version of twrp in fastboot in Windows 7 WTF? fastboot in Linux Mint Mate, has, until now, worked flawlessly.
To clarify, I could not install the ota with an unlocked bootloader and Magisk installed.
20191015 stock firmware for ONA19TB003 has been uploaded. https://www.nathanbar.net/files/android/ONA19TB003/
CaffeinePizza said:
You're welcome to reference my thread and post a link to my server with the x003 and x002 stock images. SP Flash Tools is needed.
https://forum.xda-developers.com/showpost.php?p=80574967&postcount=192
https://www.nathanbar.net/files/android
I plan on making a proper thread, perhaps this weekend, on how to backup with Wwr, and flash with SP Tools. I will try to upload updated images from the newest OTA.
I may even make a blog post with photos on my site.
Click to expand...
Click to collapse
Thanks a ton BTW, I tried to apply the October OTA on mine, and it failed because the system partition was modified (I'm sure I was doing some silly experiment)
Worse yet, the wifi stopped working for some reason... So I grabbed the backup from your server, dd'd the system image over mine, and the OTA was able to apply without a problem. Wifi started acting right again too.
I'm adding links to the OP now.
Thanks again!
NFSP G35 said:
Thanks a ton BTW, I tried to apply the October OTA on mine, and it failed because the system partition was modified (I'm sure I was doing some silly experiment)
Worse yet, the wifi stopped working for some reason... So I grabbed the backup from your server, dd'd the system image over mine, and the OTA was able to apply without a problem. Wifi started acting right again too.
I'm adding links to the OP now.
Thanks again!
Click to expand...
Click to collapse
MD5 hashes are also uploaded with DOS CRLF since I uploaded them from Windows (in the same directory as the zips on the server). Note: MD5SUM should be used only to verify that a file is not corrupt during transfer.
10"
af2e056b8b929540b3030f7dcbf07c1a stock_20190516_pie.zip
d5c6c4f8f1ea21bf18d2ee0fcb1e6335 stock_ONA19TB003_20191015.zip
8"
2244d235325b22a8a7225a736fbafaf6 stock_ONA19TB002_20190516.zip
Also, I know the 7" tablet exists now, and I have yet to purchase one. I do know, however, that it is not part of the same family. Technically (though I haven't tried it), the stock images between the 8" and 10" are exactly the same besides the ITEMS partition (items.ini).
Just got done adding boot, recovery, vbmeta, vendor and system images for the October updates on both the ONA19TB003 and ONA19TB007