Database Info

[Lenovo A10-70F] Unsecured boot.img / TWRP 2.8.7.x / Root

It's for A7600-F version! I didn't test it on other variants.
Also the boot.img is for ...150401_ROW firmware. (the latest one)
TWRP + unsecured boot.img
* You need to be rooted at least for the while to do it. The easiest way is to use KingRoot. You can uninstall it later and/or replace it with SuperSU.
1. Download the images and copy them to internal storage -> Google Drive
2. Turn on USB Debugging, then use Android Emulator or ADB shell to type those commands:
Code:
dd if=/sdcard/TWRP_2.8.7.x_a7600f.img of=/dev/recovery bs=16777216 count=1
dd if=/sdcard/unsecuredboot_a7600f.img of=/dev/bootimg bs=16777216 count=1
Root
1. Just flash SuperSU in TWRP.
Bugs
*Screen sometimes doesn't turn on after it goes to sleep (Workaround: Settings-->Screen->Uncheck screen timeout)
*Reboot doesn't work (Workaround: adb reboot or reboot in Terminal Command)
Also external storage isn't tested.
Source: github

Replaced TWRP image with new version with better interface and it should be more stable in overall.

Anyone tried this? Success?
Gesendet von meinem Lenovo A7600-F mit Tapatalk

smogan said:
Anyone tried this? Success?
Gesendet von meinem Lenovo A7600-F mit Tapatalk
Click to expand...
Click to collapse
I had this device and it works lol

Hello!
Is there a way back to stock revocery? because i need to reflash the whole tablet and smart phone tools dont recognize the tablet anymore.

Could we use flashify?
Sent from my LG-D850 using Tapatalk
---------- Post added at 05:13 PM ---------- Previous post was at 05:05 PM ----------
Also, this is for the regular a10-70f or a7600-f not the tab 2 version of the a10-70 correct?
Sent from my LG-D850 using Tapatalk

Bump
I too want to know if this works. Flashify or terminal dd command? Anyone?

I tried it with the dd command line. It works. But I don't know to get back to stock, because the flash tool for stock firmware now does not recognize my tablet anymore.
Maybe someone can make a backup of the system partition for me?
Gesendet von meinem Lenovo TAB S8-50F mit Tapatalk

smogan said:
I tried it with the dd command line. It works. But I don't know to get back to stock, because the flash tool for stock firmware now does not recognize my tablet anymore.
Maybe someone can make a backup of the system partition for me?
Gesendet von meinem Lenovo TAB S8-50F mit Tapatalk
Click to expand...
Click to collapse
Ouch Yeah I am rooted and have it the way I like and even have xposed running, but feel unsafe without a custom recovery installed yet.

Still no recovery solution
Have tried the guides that are around the net, but when I try them my tablet always wakes and boots when plugging it in to use flash tool. I have noticed that there is a flash boot option on tablet but flashtool did nothing in that mode. So I have been trying the apps like flashify to flash recovery directly and haven't been successful yet. Any suggestions are more than welcome at this point.
Lenovo A10-70F 4.4.4 KitKat Rooted

Installed recovery without a pc
Was finally able to install carliv (google it) up and running after trying every recovery image I could find.
First I backup up the stock recovery with rashr flashing tool then flashed the carliv img and boom a recovery solution. Tried many images from the internet and the non-touch version of carliv is the only one that would run.

spacenut said:
Was finally able to install carliv (google it) up and running after trying every recovery image I could find.
First I backup up the stock recovery with rashr flashing tool then flashed the carliv img and boom a recovery solution. Tried many images from the internet and the non-touch version of carliv is the only one that would run.
Click to expand...
Click to collapse
Would you care to tell us which version worked on your device? Nowhere do I see it compatible with the MTK 8165 that's running in this device. Also, the links I followed on xda only mention a touch version of the recovery. Am I missing something?
I'm hoping not to have to spend weeks experimenting to be able to get functionality that should never have been locked out in the first place. I can see the time in the near future where these software giants will finally be sued for willfully selling products that are essentially, deliberately crippled (like they are now). Unlocking my Galaxy Note 2 to gain full ownership was a piece of cake compared to this.
And if I may, as an old timer, rant a little - I've grown pretty sick and tired of the homeland security-esque computing environment of the last few years. When I get too depressed, I fire up my old Windows 98SE machine, tweaked to run like Windows 95, sit back and smile at how easy efficiently I could do everything with it...
Well, enough ranting for now. I'm sure a lot more people are going to start looking at ways to get this device to actually work for them after Christmas, as more people get it considering its great hardware features for the price and we'll get more input on these threads.
Keep up the good work folks, I'll keep looking on my end.

Well, after reading a lot and trying a few things here's what I discovered, for those who have this tablet:
Fist of all, thank you Lenovo for making a tablet that is designed for productive work! I got an external SD Card and was able to easily enable USB Mass storage mode directly without rooting, scripting or any other shenanigans
Furthermore, although this thing is running Kitkat 4.4.4 and although I wasn't sable to directly write to the SD Card, I was able to copy created content from the internal to the external SD Card without any issues. It's just that one cannot write from an installed app to the external card (at least that's what it seems to be from early testing with the tablet in unrooted, original OEM configuration).
I've been collecting files and information and as soon as I get this tablet fully under my control with root and a custom recovery I'll make a write up on it here if there is any interest.
Now if I could only find a way to turn down those impossibly garish colors in my pictures... For now it will have to wait, got stuff to take care at the house now, mess has been accumulating since I got the tablet a few days ago

Sorry I don't recall where I got the recover from it was some German sight. The non-touch version was all I was able to get to work.Play store has apps to fix the read only external sdcard.
Sent from my Lenovo TAB 2 A10-70F using XDA Free mobile app

spacenut said:
Sorry I don't recall where I got the recover from it was some German sight. The non-touch version was all I was able to get to work.Play store has apps to fix the read only external sdcard.
Sent from my Lenovo TAB 2 A10-70F using XDA Free mobile app
Click to expand...
Click to collapse
No problemo, I found it on the Russian Lenovo Forum, after reading this thread on xda-developers in its entirety (a MUST READ IMO) and a couple of other online postings elsewhere.
Basically, the recovery for kitkat (4.4.4) is here, for Lollipop 5.0.2 you need to use the one in that thread. Use Google Translate if you must, it's in the Russian.
I'm not sure why you couldn't get touch to work, and if you're worried because it's for the L version of the tablet originally (the tablet version with cellular data), although posted for the A10-70L (WiFi and Cellular version), it's been tested to work on the A10-70F by this new guy in this post, who succeded in rooting his Lollipop updated tablet, he's written a very nice summary of the whole procedure, so that's good enough for me.
I'll see how it goes as soon as I get my SD Card, which should be in a few days.
For those who wonder about this recovery, I've checked a few youtube videos, it's based it's based on ClockWorkMod, so if you're familiar with it you'll feel right at home. Just make sure you get the right recovery version for your tablet's android version

Old faithful said:
No problemo, I found it on the Russian Lenovo Forum, after reading this thread on xda-developers in its entirety (a MUST READ IMO) and a couple of other online postings elsewhere.
Basically, the recovery for kitkat (4.4.4) is here, for Lollipop 5.0.2 you need to use the one in that thread. Use Google Translate if you must, it's in the Russian.
I'm not sure why you couldn't get touch to work, and if you're worried because it's for the L version of the tablet originally (the tablet version with cellular data), although posted for the A10-70L (WiFi and Cellular version), it's been tested to work on the A10-70F by this new guy in this post, who succeded in rooting his Lollipop updated tablet, he's written a very nice summary of the whole procedure, so that's good enough for me.
I'll see how it goes as soon as I get my SD Card, which should be in a few days.
For those who wonder about this recovery, I've checked a few youtube videos, it's based it's based on ClockWorkMod, so if you're familiar with it you'll feel right at home. Just make sure you get the right recovery version for your tablet's android version
Click to expand...
Click to collapse
Not sure why the touch won't go. I was aware that the "f" and the "l" are the same with the latter just having data. Thanks for "cleaning up" the thread for us. Merry Christmas.

spacenut said:
Not sure why the touch won't go. I was aware that the "f" and the "l" are the same with the latter just having data. Thanks for "cleaning up" the thread for us. Merry Christmas.
Click to expand...
Click to collapse
Thank you for the good wishes
I found a great video online for backing up your own ROM http://bit.ly/1J6x6ruhere and am doing that next while the turkey is cooking and report back afterwards
Since my ROM is a slightly different version from the one posted before I thought it would ne best to make my own to make sure I don't run into problems should I need to get warranty service.
The instructions make it a very simple process, the only thing that isn't clear is what to do to make the tablet read and writable, since in that video you're supposed to remove the battery, which can't be done on our machines. I presume a simple power off should do. I'll be back when it's done.
Sent from my Note 2 using Tapatalk

Backing up
I just back up in Carlviv. The only issue is it does not see my external sdcard. So it takes up lots of room on the device.

spacenut said:
I just back up in Carlviv. The only issue is it does not see my external sdcard. So it takes up lots of room on the device.
Click to expand...
Click to collapse
Indeed - and it's difficult to understand why considering the SDCard can easily made writable - But you can move the backup later if you so wish. I just don't like the idea having to shuffle everything all the time. It's a huge annoyance.
I guess the only solution for now is to move on to lollipop...
Sent from my Note 2 using Tapatalk

I have this problem too but in a more complex version, I need to install TWRP whilst in a bootloop to gain ADB access because then I can push the stock ROM and fix the problem so I was wondering if you could do this without ADB?

BLN-L21C432B368/B369 build.prop file request

Hi guys, i just ask to some who like me owns the European variant of Honor 6X a clean build.prop file for the model variant and build listed in thread's title, since that I'm trying to figure out a way to fix once and for all the "generic_a15" issue encountered while updating to Magisk V15.0 (i know that there is already V15.1, I'm on it), that was messing up build and model names as you can see in the screenshots attached.
The build.prop in question is located in root/system, and it is only 2KB weight. Attach it here as a file, screenshot it or post it as a .txt log on sites like pastebin, please.
@Nollie8969 @Martin213 i call you guys because i know that we're on the same boat

Although I'm a Ubuntu user, I don't how to become root on android. Show "system files" and ?
Or do I need a terminal app ? If yes, what's the code

Nollie8969 said:
Although I'm a Ubuntu user, I don't how to become root on android. Show "system files" and ?
Or do I need a terminal app ? If yes, what's the code
Click to expand...
Click to collapse
To root on Android usually you just need to flash a SuperSU app like Magisk through a custom recovery l, like TWRP. In order to have a custom recovery, you must have an unlocked bootloader first. The bootloader is unlockable through a code sent by Huawei, wrote in a fastboot string of command by terminal emulator on PC. To be able to see and modify system files, you have to use a root explorer like MiX, ES file explorer, Total Commander, ecc. and browse to the root folder, hidden if not rooted.
I thought you were rooted man, if not don't bother, I'll ask someone else. Thanks anyway for the fast reply

No I have not rooted this phone. Too many strange stories on xda. There is no perfect custom rom yet.

Yeah I'm still on stock too, but i rooted it to take advantage of apps like AdAway, Battery Charge Limit, MiXplorer, Greenify, Xposed and TWRP overall.

I tried the build.prop file for BLN-L21 available in the repository thread, but it contains references to the general model hi6250, and not BLN-L21. I'll update the thread with a correct one as I'll have it

.

Martin213 said:
Hello @RedSkull23 sorry i didn't saw you post If you still need it here you go. Screenshot from my device of needed file.
Click to expand...
Click to collapse
Hi @Martin213 no worries, thanks first of all. I saw that even your build.prop file is the same as mine, and i refer to the fact that it reports in various voices the "generic_a15" as model name, instead of BLN-L21 (as i thought it should be, but I'm still unsure about). Did you messed up with Magisk V15.0 too when it was released? I thought i read that in another thread.. Because that's a thing that makes me think to have a corrupt build.prop file running after that. Even flashing a version.img extracted from official firmware didn't change that, and so i don't know if it had always reported generic_a15 or not... And i notice that even yours contains NRD90M test-keys in various points, so i guess that when you take a TWRP backup, the default name of it is something like "NRD90M_test-keys-xx-xx-xxxx", can you confirm this?

.

I have seen this generic stuff even on some pure stock, rooted phone...my Honor 6X but that was not causing anything in about phone section. I had the NRD tesy key issue yesterday while I restored the TWRP backup while moving from Elite to stock but then eventually gone for the dload to recover it.
Flashed stock and now I am pure stock, non rooted as started using Honor 8 now

Martin213 said:
I didn't play with magisk or testing something,just got notification in status bar and updated. After restart phone went i to a bootloop. Tried flash stock boot.img and M 15.0 zip on top with no success all was the same. After all tryings i flashed boot.img and magisk 14.0 on the top ? Then all went good. This means if i want to update Magisk i have to update my all Rom/firm or at least re-flash same firm ???
P.S one more thing for those who have OEM bootloader option grayed in developer options. Its back to normal(you can turn on/off) when i flashed Magisk and universal safetynet fix 2v beta 5 module. That was really strange for me.
@RedSkull23 if you need any help or collaboration just ask, I'm ready to help you if i can.
Click to expand...
Click to collapse
Kinda weird how OEM unlock came back by Magisk and Safetynet module never got OEM grayed out, but maybe it could help other users..? Anyway, i had understood that build.prop reports generic_a15 since the beginning, so i obtained the answer i was looking for. Thanks for your help!
shashank1320 said:
I have seen this generic stuff even on some pure stock, rooted phone...my Honor 6X but that was not causing anything in about phone section. I had the NRD tesy key issue yesterday while I restored the TWRP backup while moving from Elite to stock but then eventually gone for the dload to recover it.
Flashed stock and now I am pure stock, non rooted as started using Honor 8 now
Click to expand...
Click to collapse
Yeah it must be a general flag that is more specified in others local.prop/componentversion.txt/build.prop files in other root folders, like hw_init or cust... I have my model name correct in phone info and other files, i get NRD90M test-key name only when launch a backup by TWRP, and I'd like to know if other users get that too or they get instead the wrong build name like BLN-L21

RedSkull23 said:
Kinda weird how OEM unlock came back by Magisk and Safetynet module never got OEM grayed out, but maybe it could help other users..? Anyway, i had understood that build.prop reports generic_a15 since the beginning, so i obtained the answer i was looking for. Thanks for your help!
Yeah it must be a general flag that is more specified in others local.prop/componentversion.txt/build.prop files in other root folders, like hw_init or cust... I have my model name correct in phone info and other files, i get NRD90M test-key name only when launch a backup by TWRP, and I'd like to know if other users get that too or they get instead the wrong build name like BLN-L21
Click to expand...
Click to collapse
I am in the same boat. You will fet NRd test in twrp back-up name.
If you like change in model name then there are few changes needs to be done in build.prop file. As long as its appearing correctly in about phone, no need to worry as thats with Kirin phone i guess, had same on 5C, 6X. Dont worry thats nrd stuff jn twrp name is normal. I change it manually there for every backup name

shashank1320 said:
I am in the same boat. You will fet NRd test in twrp back-up name.
If you like change in model name then there are few changes needs to be done in build.prop file. As long as its appearing correctly in about phone, no need to worry as thats with Kirin phone i guess, had same on 5C, 6X. Dont worry thats nrd stuff jn twrp name is normal. I change it manually there for every backup name
Click to expand...
Click to collapse
Ok, I'm not the only one so :victory: yeah i saw but i wanted to know if even others was getting that as default backup name or not. In fact i do the same and i was sure that it was due to the build.prop file located in /system, but i waited to modify that because i thought that if it is was already like that, maybe there was a reason... But maybe there isn't one, just Huawei :silly:

Honor 6x OTA update bln24 B365 to B376-Full

What I don't understand is there are all these talented people out there, finding ways to do virtually anything to their phones, but there doesn't seem to be any normal solution to receiving an OTA update on a phone that has twrp and rooted and just install the update. The phone is obviously getting the right update, it restarts to install and twrp fails with error 7. There are all kinds of people saying "unpack the zip, remove the asserts line, which doesn't work, at least for this update. Also try using the dload method, but really the ultimate question is, why hasn't a simple solution to just installing this ever have been found? Is the way that all this stuff works in the background just so difficult that a legit update cannot be installed because the stock recovery isn't present? and if so, why can't a way around this obstacle be found.
I would just like to install updates as they come down (i assume by now this phone is trying to work its way up to android 8, or oreo) but i am stuck just ignoring it. I don't mind a little messing around to get things to work, i just haven't found any that actually do and don't involve wiping out the phone and installing everything again. Any answers are appreciated.

Dude. There is a way. I had the same thought before I pressed search on XDA and spent the next 3 hours digging in every Honor Forum and XDA and here is my tried and tested solution.
Make sure you have TWRP installed.
Download Firmware Finder from the Play store, enter your Model Number and download latest FULL-OTA for it. Only Full OTA will work.
Search for and Download Hurupdater from thread. Specifically Hurupdater 0.4
Rename files as specified in Hurupdater thread. Transfer them and Hurupdater to same folder on SD card. i.e all 4 files need to be in same folder. Now boot into TWRP and select Only Hurupdater to flash. Press Volume down when promoted and sit back for a few minutes. Once it completes wipe Dalvik Cache and Reboot.
Now you are on the firmware you wanted without factory reset.
A few things to note.
Your device shouldn't be Rooted. Unrooted first.
First boot will take some time approx. 10 mins. Don't Panic
After update TWRP will be overwritten. Reflash TWRP.
Don't use this to go from EMUI 5 to 8. You will brick your phone
In Firmware Finder there will be three Zips. Rename them as follows:
Update.zip -> don't rename
Update_data_full_public.zip -> update_data_public.zip
Last one will be region specific with your model number. Rename it to update_all_hw.zip
Good Luck.

Mannan Qamar said:
Dude. There is a way. I had the same thought before I pressed search on XDA and spent the next 3 hours digging in every Honor Forum and XDA and here is my tried and tested solution.
Make sure you have TWRP installed.
Download Firmware Finder from the Play store, enter your Model Number and download latest FULL-OTA for it. Only Full OTA will work.
Search for and Download Hurupdater from thread. Specifically Hurupdater 0.4
Rename files as specified in Hurupdater thread. Transfer them and Hurupdater to same folder on SD card. i.e all 4 files need to be in same folder. Now boot into TWRP and select Only Hurupdater to flash. Press Volume down when promoted and sit back for a few minutes. Once it completes wipe Dalvik Cache and Reboot.
Now you are on the firmware you wanted without factory reset.
A few things to note.
Your device shouldn't be Rooted. Unrooted first.
First boot will take some time approx. 10 mins. Don't Panic
After update TWRP will be overwritten. Reflash TWRP.
Don't use this to go from EMUI 5 to 8. You will brick your phone
In Firmware Finder there will be three Zips. Rename them as follows:
Update.zip -> don't rename
Update_data_full_public.zip -> update_data_public.zip
Last one will be region specific with your model number. Rename it to update_all_hw.zip
Good Luck.
Click to expand...
Click to collapse
Ok, I'll give it a shot and respond later. Like I said, I don't mind jumping through a few hoops. One question, how can I make sure whatever latest full OTA is doesn't have emui 8 in it? will that firmware finder point out what is in it?

If it has EMUI 8 it will be mentioned in the title of the firmware like 8.0.0.536 or something. Currently only India and China have EMUI 8. However to be safe I advise you to go to system update and Download & install. It will Download firmware and ask you to install. Hit cancel and using file explorer go to internal storage. There will be a folder named HwOUC. You will find three firmwares archives there. Use them. Make sure they are Full OTA by checking the size of archives. Update.zip should be at least greater than 1 GB

Mannan Qamar said:
If it has EMUI 8 it will be mentioned in the title of the firmware like 8.0.0.536 or something. Currently only India and China have EMUI 8. However to be safe I advise you to go to system update and Download & install. It will Download firmware and ask you to install. Hit cancel and using file explorer go to internal storage. There will be a folder named HwOUC. You will find three firmwares archives there. Use them. Make sure they are Full OTA by checking the size of archives. Update.zip should be at least greater than 1 GB
Click to expand...
Click to collapse
Yeah, I looked in the changelog, and it isn't emui 8. Plus it not being available in the USA kinda answers that as well I was going to ask if i could just use the files that are sitting in my HWOUC folder already, but you beat me to that question. so i should just move that over to my sd card into a temp folder along with that hurupdater app?

jackmeat said:
Yeah, I looked in the changelog, and it isn't emui 8. Plus it not being available in the USA kinda answers that as well I was going to ask if i could just use the files that are sitting in my HWOUC folder already, but you beat me to that question. so i should just move that over to my sd card into a temp folder along with that hurupdater app?
Click to expand...
Click to collapse
Ouch...this locks the bootloader....so can't get twrp or SU back on without losing my data (well, i have a backup, but would have to restore everything, at least i assume) if i unlock the bootloader

If it's stock firmware it will. Forget that download from firmware Finder

Mannan Qamar said:
If it's stock firmware it will. Forget that download from firmware Finder
Click to expand...
Click to collapse
Well, it was too late anyway, so the OTA files that were existing on my phone for B376 did flash fine, but now I lost TWRP and root. Beyond that, B377 tried to install today, and even though now my phone is back to factory (i assume, since those changes had been made) Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
Am I stuck now using your method above for each and every OTA update that comes through? If so, how would that be possible since I am unable to get TWRP back onto my phone.

jackmeat said:
Well, it was too late anyway, so the OTA files that were existing on my phone for B376 did flash fine, but now I lost TWRP and root. Beyond that, B377 tried to install today, and even though now my phone is back to factory (i assume, since those changes had been made) Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
Am I stuck now using your method above for each and every OTA update that comes through? If so, how would that be possible since I am unable to get TWRP back onto my phone.
Click to expand...
Click to collapse
Just reflash TWRP. It should flash fine. And yes, if you plan on using EMUI 8 the above mentioned method is the only way to update. Normally I would recommend you to Ditch EMUI and install a custom ROM. There are a lot of great ROM available for our device. If you want to flash one I will be more than happy to guide you.

Mannan Qamar said:
Just reflash TWRP. It should flash fine. And yes, if you plan on using EMUI 8 the above mentioned method is the only way to update. Normally I would recommend you to Ditch EMUI and install a custom ROM. There are a lot of great ROM available for our device. If you want to flash one I will be more than happy to guide you.
Click to expand...
Click to collapse
Well, I am still on EMUI 5 right now. I was kind of hoping not to go through flashing a custom ROM since I went through doing that on my LG nexus 5, and yes, it was great once it worked, it was a real pain to get to that working part. I was hoping the standard OTAs were going to get me up to android 8, and then just be happy with that. So I am unsure how I can flash TWRP again since my bootloader is locked again. Basically if I am going to be stuck wiping my phone out again, then I suppose I would be inclined to going the route of a custom ROM. So I guess it is just a matter of if I can get twrp on here again without wiping my phone again (unlocking the bootloader)

Um, no. You can't get TWRP with a locked bootloader. And also you can't go from EMUI 5 to 8 via Hurupdater. In Oreo partition table changes and Hurupdater can't flash that. So you will have to upgrade to Oreo manually. You can easily do that. It will take an hour to get to Oreo as well as flashing a ROM.

Mannan Qamar said:
Um, no. You can't get TWRP with a locked bootloader. And also you can't go from EMUI 5 to 8 via Hurupdater. In Oreo partition table changes and Hurupdater can't flash that. So you will have to upgrade to Oreo manually. You can easily do that. It will take an hour to get to Oreo as well as flashing a ROM.
Click to expand...
Click to collapse
so in essence what you are saying is that I can't go any further at all right now without wiping my phone again so i can unlock the bootloader? As of right now, I don't even know Huawei is going to release Oreo for this phone OTA, and even if it does, right now I can't get it. So since you have been so helpful (and very much appreciate it btw) what do you think is my best course? I don't think unlocking the bootloader will be an issue. i have the code saved somewhere around here. I wasn't all dead set on EMUI, it was just kind of nice staying somewhat in the realm of legit. And no, I have no qualms about straying outside of that. I just didn't want the nightmare I had with my nexus occurring again and not having use of my phone as a phone for the longest time. I'll await to see what you think I should do. Thanx again

Well. Flashing is easy. I'd recommend you to unlock your bootloader. And after that download HWOTA from thread. I will provide link. Next I want you to decide that wether you want stock EMUI 8 or want to flash a custom ROM. Depending on that I would advise you to either get Indian or Chinese EMUI 8. Indian is good for daily driver. Chinese for flashing custom ROM
Edit: heres the link
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page15

Mannan Qamar said:
Well. Flashing is easy. I'd recommend you to unlock your bootloader. And after that download HWOTA from thread. I will provide link. Next I want you to decide that wether you want stock EMUI 8 or want to flash a custom ROM. Depending on that I would advise you to either get Indian or Chinese EMUI 8. Indian is good for daily driver. Chinese for flashing custom ROM
Edit: heres the link
https://forum.xda-developers.com/honor-6x/development/hwota7-hwota8-honor-6x-t3792601/page15
Click to expand...
Click to collapse
Looks like I will be stuck either way with wiping the phone, so I may as well go the custom ROM road. Don't really need to bother with the HwOTA then I wouldn't think. Unless I am missing something here. So who are the players for custom these days? still cyanogen? I saw on a search thay had android oreo 8.1. I used their custom ROM on my nexus as well. I most likely won't be getting to this now until tomorrow. I'll backup my phone...oh ****, titanium isn't gonna work. no more root....ok, i'll unlock bootloader, get twrp and root back on my phone and backup so definitely not until tomorrow. Only question for tonight is do I still need that HwOTA? I think I am a bit confused on what exactly I am trying to achieve. is it EMUI 8 with custom ROM of android 8? or nixing EMUI completely. Pardon my ignorance, but I really am just a bit hazy here on how this all works. all this for some stupid security update only because I thought it would open my phone back up to getting the OTAs and Huawei would release 8.....

Well. Since you are on EMUI 5 you will have to use HWOTA once you get to EMUI 8 as all custom ROMs require that. It also adds Project Treble support. So you will be flashing EMUI 8 once. After that, it's your choice. Either stay in stock or take the custom road. In terms of stock, there are currently 3 Android 8.1 ROMs available by OpenKirin and one Pie ROM available by Askuccio Droid. OpenKirin ROMs have stock camera in built while Pie ROM is.... Well Android Pie. All of them are smooth, have tweaks and great battery life and are infinitely better than stock EMUI 8. If you want the stock road, upgrade to BLN-AL20. That's the Chinese EMUI 8 and better for custom ROM. If you want stock EMUI 8 then go for BLN-L22.

Mannan Qamar said:
Well. Since you are on EMUI 5 you will have to use HWOTA once you get to EMUI 8 as all custom ROMs require that. It also adds Project Treble support. So you will be flashing EMUI 8 once. After that, it's your choice. Either stay in stock or take the custom road. In terms of stock, there are currently 3 Android 8.1 ROMs available by OpenKirin and one Pie ROM available by Askuccio Droid. OpenKirin ROMs have stock camera in built while Pie ROM is.... Well Android Pie. All of them are smooth, have tweaks and great battery life and are infinitely better than stock EMUI 8. If you want the stock road, upgrade to BLN-AL20. That's the Chinese EMUI 8 and better for custom ROM. If you want stock EMUI 8 then go for BLN-L22.
Click to expand...
Click to collapse
Ok, I must just be really tired. Is there not some way for me to just get back to whatever is causing this next OTA to stop? Meaning even though it is just some stupid piddly update, just get my phone to accept that without going totally overboard and what seems to be a bit above what I know how to do. That way the OTAs will just come at their own pace and I'll live with not having all the bells and whistles. Just going back to stock sort of thing. That is kind of what I thought was going to happen when you so very graciously and successfully got that last update to work. That way I can try something new and just be patient until Huawei forces out android 8 on their own.

jackmeat said:
Ok, I must just be really tired. Is there not some way for me to just get back to whatever is causing this next OTA to stop? Meaning even though it is just some stupid piddly update, just get my phone to accept that without going totally overboard and what seems to be a bit above what I know how to do. That way the OTAs will just come at their own pace and I'll live with not having all the bells and whistles. Just going back to stock sort of thing. That is kind of what I thought was going to happen when you so very graciously and successfully got that last update to work. That way I can try something new and just be patient until Huawei forces out android 8 on their own.
Click to expand...
Click to collapse
So you want to remain on stock EMUI 5? Well it's your choice. Anyway check a few things.
1. Is your bootloader locked? Do you get a warning screen when phone turns on?
2. Do you have TWRP recovery? Or stock?
3. Lastly is your phone rooted?
If your bootloader is locked, you have stock recovery and your phone isn't rooted, then congratulations. You are on stock EMUI 5 and you should receive OTA normally. Or at least I hope so.

Mannan Qamar said:
So you want to remain on stock EMUI 5? Well it's your choice. Anyway check a few things.
1. Is your bootloader locked? Do you get a warning screen when phone turns on? Yes the bootloader is locked now. And no, I do NOT get that warning screen anymore
2. Do you have TWRP recovery? Or stock? NO, I don't have TWRP anymore
3. Lastly is your phone rooted? No, I removed root to perform theinstall of B376-FULL and was obviously not able to root it after due to the previous
If your bootloader is locked, you have stock recovery and your phone isn't rooted, then congratulations. You are on stock EMUI 5 and you should receive OTA normally. Or at least I hope so.
Click to expand...
Click to collapse
Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
This shows the EMUI 5.0 screen

jackmeat said:
Now it fails on the next update of B377 on the EMUI recovery screen and tells me "software install failed get help from http://www.emui.com/emotiondownload.......
This shows the EMUI 5.0 screen
Click to expand...
Click to collapse
Can you tell me what is it that you're trying to do and what's failing. I can't tell much from this.

Mannan Qamar said:
Can you tell me what is it that you're trying to do and what's failing. I can't tell much from this.
Click to expand...
Click to collapse
I am not trying to do anything. The phone has received an OTA update, B377, and after it downloads, it says install. click to restart now. After restarting to do the install (the everyday, normal OTA update method, nothing fancy) then it goes to that error. Only option from that black EMUI screen is "reboot now"

[Huawei P20] getting root on AOSP 10 Preview 2

After several days reading into topic, many tries, (including bricking and unbricking my P20 two times down to fastboot access only..), I still not at my goal: Taking full ownership aka. get root of slick & clean device.
Thanks to @OldDroid and his crew (THX!) now I have a working AOSP 10 Preview 2. It was flashed over a fully working EML-L29 9.0.0.293 (C432E7R1P11), bootloader & FRP unlocked, installed from eRecovery internal download(after second brick..) Thankfully I refused to update to 9.1 before due to /system read-only problems i red about. So everything, including recovery should be genuine. I will try to keep all the Google inside an Island and restrict it as far as possible with firewall.
Now I question myself how I can obtain root without bricking this wonderful machine again. I guess I will need Canary Magisk Manager from this link:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Switching channel to canary too, going the recovery_ramdisk patching route. (TWRP I already miss you!!)
I already downloaded EML-LGRP2-OVS 9.0.0.293 (FullOTA-MF) via Firmwarefinder to extract recovery_ramdisk from it. As I only flashed system I guess this should be the version I need to patch with Magisk?
I know, this is pretty unknown territory, but on OmniROM 5 beta I the non working touchscreen bug. Would give it a second try if there is no other way, maybe starting from a lower EMUI 9 version? If anybody could confirm my plan, or tell me its rubbish, I would be thankful.
@mods: This whole Treble thing makes it quite confusing, if you believe this post would get more attention in another place, feel free to move it. thx!

Question TWRP coming?

Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup.
That said, does anyone know how long it typically takes for TWRP to be supported on a new device (i.e. G-Stylus 2021)? Just curious what the norm is. Thanks!

That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.

DM.IDOL said:
That's a good question. I don't know how long it should take, but after reading the article you linked it seems that successfully porting TWRP to these newer phones will take a lot longer than on the older ones. Hopefully someone's already started working on TWRP 3.5 for the 2021 models, but I haven't heard any actual news on that yet.
I would love to be able to get a full backup of my device in case I really screw something up later on. If I had any level of programming skills I would certainly make an attempt at it myself.
Click to expand...
Click to collapse
I'd look around on github

THIS is a TEST build for the Moto G stylus XT2115-1 minsk_t
(please mind that i have never done this before and i am at least trying to figure out how to create custom recoveries. i just need a good teacher with a little time. .)​
*Touch Screen does not work. OTG mouse necessary.*
(not too sure how to fix this error)
*Mount points were for testing*
(modied fstab files in ramdisk to fix mount points)
*modified ramdisk and split_image from Moto G 9 plus unofficial 3.5.1 twrp*
https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-g9-plus-odessa.4195729/
i tried to put a recovery together for this device but im not sure where i went wrong or what to do next. booting into this recovery works but /vendor and /system_root have denied permissions. when it is flashed within twrp and rebooted to recovery or system the screen says no OS installed press power to power off. If anyone can help me figure this one out i would be greatly appreciative. If you need anything i can pull from my device just let me know. Anyone willing to help work on this recovery and figure out what needed to be fixed i would greatly appreciate it!
*EDIT*
i got /data to back without digest verification. Was not able to try to restore the backup as i got NO OS error when i rebooted to restore.
*EDIT*
i was able to figure out pretty much everything except the touch part of the recovery. it has a novatek_ts (NVT-ts)
not sure what to do to enable the drivers for twrp. any feed back would be great.
*EDIT*
Found the driver. I'll post it here and see what you can do. I'll also work on it as I'm still learning where stuff should go in the recovery. And also seems to b that i cannot access external sd from twrp either.
*EDIT*
resolved sd card issues. mountpoint was incorrect. only thing left to get working is touchscreen and not have to use otg mouse.
updated twrp for minsk_t is in files now.
*EDIT*
I found the proper elements to configure the recovery's touchscreen capabilities. Will be recompiling later on today. After I have tested it I will post the new working TWRP recovery. Thanks everybody.

*deleted*

sosthenisRR said:
*deleted*
Click to expand...
Click to collapse
So this is fully functioning now right? Is there any reason to use this over the OrangeFox recovery that has been posted?
Also, if I did install OrangeFox, and decided I wanted to install this later, would it be as simple as flashing using fastboot from ADB, overtop of OrangeFox? Or would the procedure be a little more complex?