[Release] VKWorld VK6735X - A working TWRP image - Android Q&A, Help & Troubleshooting

The problem that I've put into quotation below has been solved and here's what happened: I've basically been an idiot.
After I had gotten TWRP ported I did a reboot from TWRP into the system. But little did I knew that when I swiped for the reboot into the system, I had accepted to let the TWRP flash a SuperSU that wasn't compatible with the phone (some SuperSU were for whatever phone my TWRP originally intended to be for), hence breaking it.
First of all the exact phone we're talking about is this one.
The important thing to notice is that VK6735X is not the same as VK6735, which has got its own thread over here. According to that thread the so-called TWRP image (by the way it's not TWRP, but some Russian trash) over there could be flashed flawlessly whereas with my phone it didn't work that way.
Which brings us to the topic: Through my journey of Google searching for a TWRP image that actually works with my phone I've stumbled across a lot of things which I'll be summing up.
I've found an actually working stock ROM for this phone. You can download it along with the handy flash tool from the original source since it's probably a little big to be uploaded as attachment.
I've found a TWRP 3.0 image from another random website which I've successfully managed to port to this phone, or in the attachment.
I've discovered the tool called Carliv Image Kitchen, which made extracting and repacking boot.img and recovery.img extremely easy.
With that said I've basically ported and flashed TWRP as my recovery, though here's the problem: Booting up the system results in a bootloop...
So according to what I'm understanding it's due to some dm-verity garbage (yes, I'm just the kind of guy who hates it when a piece of human invention dares to defy the wish of its master) is preventing the system from loading because the inferior recovery that came out of the closet suddenly became straight, *cough *cough I mean because I've replaced the useless stock recovery with TWRP. Now this can apparently be fixed through porting or modifying the boot.img, right?
So here are my questions: What do I have to modify about the boot.img (or any other image) in order to stop the system from bootlooping over the fact that I've replaced the inferior recovery with TWRP?
Don't worry about me though, I can re-flash it anyway and plus it's not my main phone.
Click to expand...
Click to collapse
Either way, you came here for the TWRP image that's working for your VKWorld VK6735X so you can find that, as well as the flashing tool I used from my Google Drive folder.
But before all of that I obviously have to tell the same boring warning: I'm not responsible if you lose your data or brick your phone! Make sure to have backup for whatever you don't want to lose!
Head to the Google Drive folder, download the two zip files to your pc (lol not your phone), extract them anywhere you like and follow the steps below:
From the extraction of "Flash VK6735X.zip", install the drivers from the "Driver" folder. Windows might be acting stupid because it's Windows.
After installing the drivers, run "flash_tool.exe" which is located in the folder called "SP Flash Tool v5.1708"
(Optional) Go to your phone settings, go to "About phone" and tap the "Build Number" until you've unlocked the Developer options.
(Optional) Then go to the Developer options and enable "OEM unlocking" as well as "USB debugging", honestly you don't have to but why not...
Power off your phone and take out the battery
Back to the flashing tool you've opened in step 2: Load a so-called "Scatter-loading File" and select the file "MT6735M_Android_scatter.txt" which you've extracted from the "TWRP port for VK6735X.zip" file. The "recovery.img" file must be located in the same directory so do not separate those!!
Leave your phone battery removed and do not connect your phone to your pc yet: Press the download button
After pressing the download button you can connect your battery'less phone to your pc, no need to hurry since the flashing tool will only start once your phone's connected.
Wait 'till the flashing tool pops up a small green window saying it's done.
At this point you can place the battery back into your phone and unplug it from your pc.
Congratulations, you've installed TWRP.
Step 6:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And this is step 7:
How to get into TWRP:
Hold down the volume up button, then press and hold down the power button whilst still holding the volume+ button and wait.
In a few seconds you'll see three tiny options on your screen, with the volume up button you'll select between the three options and with volume down button you'll enter them.
Choose Recovery.
Be cautious: DO NOT swipe in any situation inside TWRP before you've read what it says, otherwise you may accidentally flash a SuperSU that isn't compatible with your phone and get the exact same problem that I've described in the quotation section of this post xD
Lastly you can find the Stock ROM inside the "Firmware" folder, if you select the scatter file inside this firmware folder with your flashing tool you can basically flash your phone back to stock.

Root + Viper4Android
Once you've successfully installed TWRP rooting this phone becomes amazingly simple!! Download the latest Magisk zip file and apk from the official thread and follow their instructions: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk v16 works for this phone, although mine does crash quite often when I'm scrolling through the module list.
Next up is Viper4Android: Installing this is as simple as going through the Magisk modules and finding the right one to install. There are multiple Viper4Android modules whereas I've picked the one made by Viper520, ZhuHang, Team_Dewitt, Ahrion and Zackptg5.
So here are the Magisk Modules I've got working for this phone so far:
Viper4Android FX Materialized
Magisk Manager for Recovery Mode
ADB & Fastboot for Android NDK
For some reason "Xposed Framework (SDK 22)" gave me a boot loop so that's a pity.
Luckily I've got Xposed Framework v89 working through using an apk from this thread and flashing the zip from the original with TWRP.
Here are Xposed Modules I've verified working so far:
GravityBox LP
Flat Style Bar Indicators
AFWall+ (some kind of fixes and such)
Youtube AdAway
Then lastly I've got F-Droid installed without any trouble so I've got myself Adaway and some other handy stuff from there as well.

Request move
Since this thread is no longer a request for help: Could a moderator move this thread over to the right forum for me?

Related

Reinstall/Install MM/N on WiFi/LTE YOGA BOOK

This is the stock Rom of N & M for Yoga Book LTE & WIFI for the needers
if any dev want to help me developing a dual boot for Yoga Book, just PM me or join Telegram Group for Yoga Book devs and users:
MOD EDIT: LINK REMOVED
Prees the Thanks button if that helps you​
How to install it:
Be careful, these steps will erase all your data on tablet and will downgrade rom (stock marshmallow)
First of all: read and understand all of the instructions.
1. Download the stock ROM
https://cloud.kolyandex.su/index.php/s/4WDt6ghOzHAyP4s (Nougat WiFi version)
https://easy-firmware.com/home/browse/category/id/19521/ (Marshmallo LTE version)
https://androidfilehost.com/?fid=817550096634799507 (Marshmallo WiFi version)
2. Extract it to some folder
3. Download Intel Platform Tool Lite from here: https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
4. Install Intel Platform Tool Lite
4. Boot into fastboot mode
5. Run Intel Platform Tool Lite
6. Make sure your tablet is recognized by the tool (otherwise you need to enable USB-debug in Developer settings)
7. Select "flash_update_from_eng.json" from folder in (2)
8. Push "start to flash"
9. Wait... (You should check tablet's screen in order to lock/unlock bootloader (it should be locked after flash in order to install OTA updates))
10. Reboot tablet
11. Your keyboard might not work: that is normal (just use on-screen keyboard for now)
12. After initial setup: open Contacts app, create new one (if there are no contacts yet), tap search and enter ####6020#
13. Choose your region
14. Reboot
15. Setup again (now halo should work)
16. Go into settings -> about -> updates and update till the last version (may take several hours)
17. Say thanks for alexjustes for his Amazing Steps
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
beltani said:
Thank you so much for posting this!
Have you tried flashing this through @danjac's TWRP build? I know trying to restore any nandroid backup made after the OTA upgrade to Nougat results in a boot loop.
Click to expand...
Click to collapse
Unfort. no, because i dont have a YB Android Version, i have win ver.
THE MAXIMUM POWER said:
Unfort. no, because i dont have a YB Android Version, i have win ver.
Click to expand...
Click to collapse
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
beltani said:
I'm 99% sure this isn't flashable in custom recovery, at least without some modification and repackaging. It's a package designed for Intel Phone Flash Tools.
Still a huge asset, though, so thanks again!
Click to expand...
Click to collapse
Same, it can only flashed through fastboot mode
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
@MarkAllen, thank you for your valuable information. This will help people unbrick their devices.
MarkAllen said:
I got myself into quite the pickle today. I've been considering selling my Yogabook to switch to a Chromebook 2-in-1. I wanted to get the device back to as full vanilla as possible. I "thought" the first step was to lock the bootloader again and then do a full factory reset, apparently not... After booting back up from locking the bootloader I kept getting an Intel "bootloader error code 01" and Android would not start. It would take me to fastboot mode on it's own but I was unable to use the power button to make a selection and the device would just power off after 5 minutes. Thankfully from there or fore powering off I could hold Volume up on startup and get to fastboot manually or recovery. It being in a locked state now though I couldn't do much of anything else, no flashing anything other than loader, no format, no erase, and TWRP was not able to be booted.
Anyway I finally read a post about DNX mode and how to get to it, but nothing on how to really use it or any decent information imho. After finally finding some users on another part of the forum discussing a DNX flashing tool made for their devices HTC I went searching for a tool for the Lenovo. Lenovo has nothing for this (shame on you Lenovo!) but Intel does have it and it can be used with the recovery image posted above in this thread (and I assume all the others running around). And here is the URL for the tool
https://01.org/android-ia/downloads/intel-platform-flash-tool-lite
You just have to load a valid JSON file containing the proper config information for the ROM you are flashing iwithin the Intel tool. For this particular version of the ROM I did have to modify the "flash_recover_dnx.json" file to remove this section
Code:
{
"duration" : 5000,
"restrict" : null,
"tool" : "sleep"
},
Otherwise the flash tool would not load it due to the a bad tool from this JSON config named "tool". No other changes to the settings of the Intel flashing tool were needed.
Just click "Start to Flash" and once it was done all was well. Took a little over five minutes, it unlocked, flashed, and locked the device again itself.
No more Intel error stating the device isn't secure every reboot. I did lose all my data that was on it doing this but I wasn't worried about that going into it.
After initial setup in Android I did have to do the trick noted here to get the Halo keyboard working again which then required initial setup once more.
Hope this helps others.
Click to expand...
Click to collapse
Thank You for the INFOS
The tool does not recognized my device
Please help to flash my yoga book.
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
jeitana said:
Please help to flash my yoga book.
Click to expand...
Click to collapse
Try installing Android SDK drivers in you PC
Guys, if anyone faced a Probleme during his way to flash the ROM, PLZ tell me the problems with More Details
_Deeb0_ said:
Got these with the stock .json file as described above:
06/18/18 12:00:01.188 ERROR : No description value in command sleep
06/18/18 12:00:01.188 ERROR : Cannot create command with tool "sleep"
06/18/18 12:00:01.188 ERROR : Tool sleep not found or invalid tool configuration
Opened that file in notepad and deleted the sleep section - started flashing.
The usb drivers are definitely required, I lost the connection because they weren't loaded. I installed them and refreshed device manager and she started receiving the flash.
Used Win7 to flash also, the intel page says its not supported.
Flash success and locked bootloader after entering the country code - thanks very much all!
Click to expand...
Click to collapse
Is this compatible with the Yoga Book A12?
I have been away for a while. Why should I want to install this rom?
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Shawnki91 said:
Is this compatible with the Yoga Book A12?
Click to expand...
Click to collapse
Sorry but no
hajkan said:
I have been away for a while. Why should I want to install this rom?
Click to expand...
Click to collapse
No Need to reinstall this Rom if you have already your System, both are 100 % same
hajkan said:
Ok I wanted to reset this tablet because the SystemUI ap was using %25 of the cpu constantly, I do not know when and hopw this piece of **** got to that level of crappy update, must be some google crap
- Can I unlock the OEM bootloader?
- Can I still use the twrp->Magisk method to root this?
thanks
Click to expand...
Click to collapse
Reinstall the Rom will fix this, but doing factory reset will fix this too
In case anyone wants the wifi only M firmware here it is https://androidfilehost.com/?fid=817550096634799507

Android POS machine H10-1 made by Citaq? Can I reuse it for personal touch tablet?

Hey All
Its been a while since I got to play with anything these days but I recently found one of these POS 10in touchscreen units in the dumpster and it fires up into a menu running android. So I was hoping I could reflash this and use it like a tablet given it's also got a small thermal printer in it, so maybe try and save it from e-waste
I searched online for more details and came across this HERE which is identical to what I have so hoping I can root it and flash it with a clean android?
I would love to repurposed this to use as a touch screen tablet or similar, since it's got a GSM module and can take an SDCard too as I opened it up and took some pictures and I managed to get it in a recovery mode as well - from the PIX its using a rockchip RK3368
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not sure if the mini usb port is a OTG port to try and use ADB but I have not been able to do much with it and hoping someone can guide me through to possibly a reflash or ways to unlook root and add in another bootloader/rom
I've downloaded the files from citaq website but so far not been successful to do much with it, has anyone played with these and turned them into something more practical for the home?
Here's hoping for some tips - Apology if this is in the wrong section, move as needed :good:
Cheers
Kosti
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
jwoegerbauer said:
@Kostiz
Device actually is running Android 5.1.1. It seems it has only 1GB RAM what is far too little to run a full fledged Android.
As long as you don't replace device's Stock Recovery by TWRP or similar recoveries, after a successful rooting don't install Magisk and/or Xposed Framework, you're on the safe side to play with, IMHO.
As 1st step check whether device is accessable by means of both ADB and Fastboot.
Click to expand...
Click to collapse
Hey, Thanks for chiming in!
So in order to get ADB and or Fastboot its suggested to enable USB debugging in the device system settings, but I am not sure on how to do this, would it be safe to assume this is already USB debug is already enabled?
Could I back up the original stock recovery
I'm a little green on the whole process hence looking thought I'd ask here, I don't think I even have an OTG cable handy
I will see if I can load ADB on a windows box and try and talk to this unit
Cheers
Kosti
@Kostiz
An OTG-cable isn't needed, because the recovery menu
doesn't give you the opportunity to load something from an USB-device
OK, some success!
I went back and connected a mini USB straight to the PC and ADB driver installed detected the android device.
Ran ADB in windows powershell
So whats the best method to backup the entire ROM, and recovery files in the event I stuff this up?
Do I use just ADB for this or someother tools?
I did try one tool here from the vendors website but stuck as not sure what the Chinese characters mean..
Is the fact that this is only 1G i couldn't run Android at all and needs to be stripped down?
Cheers
Kosti
@Kostiz
Android Oreo Go Edition is a lightweight distribution of Android that runs better than normal Android on devices with <= 1 GB of RAM
How to backup device's Stock ROM is eplained here.
Thanks again mate!
Seem I have to do a lot of reading and thankfully everything is here, just got to spend time to read and have a go!
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
BTW, the current ROM installed boots into a special menu, all other settings are hidden, would there be a way to enable seeing all the items and when getting the the settings (gear icon) that pops up in the corner, only takes me to the standard wifi menu to choose a wifi, so it seems everything else is hidden, if by enabling these I could potentially not need to do anything other than stop the default application from starting up - if that makes any sense
Could I just get back into a adb shell and try
adb shell
su
pm enable applicationname
I have to read up on rooting first I assume before I do much more, this is getting exciting, LOL :good:
Kostiz said:
BTW how do I go about using volume rockers and power button to move around the menu in recovery when there is none but only the two buttons as shown the reset and recovery buttons on the main board?
Click to expand...
Click to collapse
You use Android's HOME button to navigate within the Recovery menu, use POWER button to select option.
Hi, fellas! Please help me with one of these Citaq H10 POS. All we have is bootloop with some custom ROM showing vendor's logo.
Forcing it into recovery gives me some dead android screen with "No command" text.
Please guide me through this challenge, cause I have no other option but to ressurect it somehow.
Good news is that I have another one that is working fine, so we could try cloning it or something. Please help!
Yet I can't attach pics, cause of few posts, but if needed I can PM some.
citaq h10-2
I am also stuck with this machine citaq h10-2 , i did use a wireless kb to move up/down and not the 2 buttons on the motherboard , i can talk with it with ADB but all you can do is put it in sideload to upload new firmware and put it in fastboot but in fastboot you only get a black screen , what I have don is > opened up developer mode but you have no OEM UNLOCK tick box in side so running any bootloader unlock dose not work and i have run them all, if you google this machine for flashing new firmware you only get XDA this forum, unless any body knows another place to get the info from please let us know as i do think this would make a nice tablet with printer, the firmware is 5.1.1 and would love to put 6.0 or above on it but. i did download some firmware and used sideload to install it but it come up with error , i did try and make a backup but cannot do it ?, I think the firmware was from a galaxy s5 , I am not into all this firmware flashing so I am learning as I go along and if I brick it up well it was for free any way as the takeaway was shutting down and he gave it to me so no loss, if any body knows how we can get 6.0 or above on this machine please let us know.
A big thank you to all that can help put android 6.0 or above on this tablet.
Did you guys take a look at the solution here ? It worked for me ! All with a 2k ohm resistor...
Hola, alguien tiene la Rom de este dispositivo?

[Guide][root][unlockloader][roms][twrp][tutorial] for huawei devices

Disclaimer: Im new and i'm not that good at english,im not responsible for bricked devices.
So for the past month i've been through a journey of tryng to break through huawei's draconian security and i can proudly say that i finally did it, i installed a custom rom on my FIG-LX1
I've read a lot of sources and it all seems to be all over the place so i'm going to try and make this as easy as i can for you.
1.First of all ,if you want a custom rom go to OpenKirin ( https://openkirin.net/devices/) and choose your rom and see if you need to upgrade/downgrade your emui and also if your device is supported.
2.For the bootloader you have two options
a) The paid one, use sigma key or dc unlocker
b) The free and geeky one. Attention you'll need to open up your phone, which is honestly not that hard and you can pay a pro to do this for you for like 5 bucks .This method is pretty straight forward:\
1.Go to Potato NV (https://github.com/mashed-potatoes/PotatoNV) , see if your device is supported and download the software
2. Now comes the hard part, you need to take off the back cover of your device. Shut down your phone, then take your phone cover off, then you need to search google for your test point. For example for me it was Fig lx1 test point (device model+ test point)
3. When you located the test point youll need to short it with the motherboard shield. In their tutorial they said that youll need to solder it ,but it can be done easier. You need just a very small piece of wire and someone to plug the device
Here's how the process looks:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4.Open potato nv software. Now you need another person to help you. Hold the phone , touch the test point and the motherboard shield and keep them shorted while the other person plugs the usb cable from pc to phone. U should hear the connection sound from windows and the CHARGING LOGO SHOULDN'T APPEAR.
5. Now you can stop shorting the test point and the shield, but keep the phone connected to PC.
6. In potato Nv choose your cpu and unlock bootloader
7.Now your bootloader is unlocked ,if any problems you still have the bootloader unlock code
Back to roms and twrp .
Now you should see this messagge appear:
This menu is very important for changing the rom ,cause every rom needs emui 9 or 8 to be installed and from here you can reinstall the stock emui after flashing custom rom but we'll talk about it later.
Now for flashing twrp.
Boot the device into bootloader mode(shut down ,then hold power+ volume down until huawei appears on screen or Better and easier and useful for later download android platform tools from SDK Platform Tools release notes | Android Developers (developer.android.com/studio/releases/platform-tools).Plug the device into pc,enable usb debugging . Open a cmd and open the folder location .Example
Code:
cd C:\Users\USerName\Desktop\platform-tools
and type
Code:
adb reboot bootloader
. You should see that your bootloader is unlocked
Download android platform tools (developer.android.com/studio/releases/platform-tools)
Now find your twrp img for your phone , rename it to recovery.img and put it in in the platform-tools folder
Now in terminal open cmd in platform tools folder and type
Code:
fastboot flash recovery_ramdisk recovery.img
Now you have twrp installed
Note that you wont use it neither for rooting with magisk neither with installing custom rom.
Installing custom rom:
Open kirin has a very good user guide and i suggest you to follow it: OpenKirin (openkirin.net/user_guide/openkirin-rom-installation-instructions/)
Btw their rom works with twrp
But it doesn't say how to switch your rom or go back to stock for switching you need to be on stock)
1.Go to Android File Host - Free file hosting for Android developers ( androidfilehost.com) and search for your build number (eg: FIG-LX1) and download a firmware emui 8 or 9.
2.Open the zip ,go to software and from here youll see a folder called dload, extract it somewhere
3.Now youll need a sdcard in your phone,plug your phone into pc and put the dload folder on your sdcard (it should bee on the root directory ,basically dont put it in another folder in sdcard)
3.You should've noticed already that every time you restart your phone there is a warning message sayng that your phone is unlocked( image above)
4.Press volume up for 3 seconds and it should take you to huawei recovery ,from here press wipe data and factory reset to kinda reinstall huawei recovery which youll use for dload
5.After wipe restart your phone ,press vol up + vol down + power until huawei logo to enter force update
6.Now wait for it to do its job and install emui.
*If it doesnt do anything , take the sd card out ,put it in another device ,open dload folder,find update.zip and put it on the sdcard instead of dload folder
7. To switch the rom repeat the steps from open kirin,note that if u had twrp youll need to install it again
Now the hardest part ,rooting...NOte that i tested root only on stock so your process can be diffrent but im not sure ,you cand try for other rom this process
For stock and no twrp:
1.Force update emui with dload method , needed for a recovery img.
2.On pc open dload folder ,open update.zip and extract UPDATE.APP
3.Now download huawei app extractor from here [TOOL] Huawei Update Extractor [UPDATED: v0.9.9.5] | OPEN-SOURCE LIBRARY | XDA Developers Forums (xda-developers.com) (forum.xda-developers.com/t/tool-huawei-update-extractor-updated-v0-9-9-5-open-source-library.2433454/)
4.Open the app and go to settings and untick every box you see
5.Now go to extract and extract the UPDATE.APP file
6.Now you should see a lot of nonsense,find recovery_ramdis.img ,left click it once, then right click for options and select extract selected
7. Now u should have a recovery_ramdis.img file.Move this file on your phone and install magisk manager.
8.Open magisk and press install in the tab with the mask(the first install button) tick the box with recovery mode, then select patch a file and select the recovery_ramdis.img file .Now it patches it. Then move the patched file to the pc again, to the platform tools folder
9.Enable usb debugging on the device and plug device to pc
10.Open cmd on pc and type
Code:
adb reboot bootloader
, or simply reboot to bootloader(shut down phone,then hold power + vol down until huawei logo appears)
11. In cmd type
Code:
fastboot flash recovery_ramdisk magisk_patched_yourfile.img
Dont forget to change the yourfile into your file name mine had something like this : jhfdU
12.Reboot your phone and voila u have root, if doesn't work go back to magisk press again install,tick recovery mode, but this time select direct install and this should resolve problems
Magisk official guide(kinda hard to understand) : Installation | Magisk (topjohnwu.github.io) (topjohnwu.github.io/Magisk/install.html#huawei)
Note that by this you'll remove your custom recovery .
IF U WANT TWRP i assume that you patch the twrp img file with magisk and flash i,t you can try it out and post your results or u can try to just flash twrp as is.
Hope i helped you !!

Moto E6S XT-2053-1 Unlock Bootloader, Disable Verity, ROOT Magisk, TWRP

I am perfom this Sorry for my english, I am from Ukraine
Download archive!
We unpack. Install the adb and mtk preloader drivers, if they are not installed, restart the computer.
In the smart, turn on the developers menu, in it - "Allow OEM unlock" and "USB debugging" and connect the smart to the computer.
We drop valuable photo data from the smart to the computer for any, and, without disconnecting the smart from the PC, run the script (with the phone connected to the PC and loaded into the android phone. Reboot_to_fastboot_getvar current-slot.bat (not from the admin, just click twice).
Smart will look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
we allow - put a daw, ok. We are waiting for the smart to reboot into fastboot, when the barcode appears on the smart screen, before that we do not press anything in the script
I did the scripts step by step, after each operation in the script window, press enter to continue, and so on until each script is closed
We look at our current slot in the window and remember the letter - a or b:
In the script, press enter so that the smart reboots and the script closes.
Run flash_tool.exe, go to this tab and check the boxes, as in the screenshot:
So we consider the necessary versions of orig. files, so as not to download and sew a specific firmware version for this instruction.
(And best of all, all the checkboxes, except for system, vendor, userdata - they are not critical, if they are not removed, it will take up a lot of space on the computer up to +74 gb, but I did not put these checkboxes, there must be some risk and passion )
We press "Read Back" and only then we connect the switched off smart to the PC, we wait, at the end we disconnect the bodies, do not touch it: sveta:
Go to this tab, remove all checkboxes! And we only put on lk_ with the letter of a non-your slot that we looked at, for example, you had slot "a" - so we put a check on lk_b and vice versa :
Click "Download" and connect the switched off smart to the PC (it was already turned off: sveta
As it flashes, we close the USB flash drive window, disconnect and turn on the smart, after loading, we connect it to the PC again, we already run the script
Unlock_Moto_E6S.bat, wait until the body reboots into a fastboot (to the barcode on the screen) and only then press the input step by step to continue in the script until it is completely closed.
Everything, the bodies are unlocked. Now you can get an excellent and fast root from Magisk, try other firmware, unsubscribe which one is buggy, which one flies. I haven't tried yet. Now I will write how to flash orig. kernel with magisk root (attached magisk boot for xt2053-1 4/64 fw RETEU 288-60-6-29 https://mirrors.lolinet.com/firmware/moto/fiji/official/RETEU/
Additionally, there is a script in the folder to delete the message when loading that the bootloader is unlocked, it does not interfere much, but I deleted it. Since this is not important, I separated it from the main script, since I did not test it on different versions of the firmware, in theory it should work on all versions, you can try after unlock. Or throw off ROM_45 from your firmware, I'll remove it from it. I now have the latest firmware flashed, it is on the server, but for some reason it did not fly through the air. If you flash it, then you can safely delete the message from the bootloader with my script, there is a file from it)
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
severagent007 said:
I am flash in slot_b Android 12 GSI, work. And i have in slot_a original system
Click to expand...
Click to collapse
dude!! followed all your steps and i now have a bootloader unlocked and rooted device. how did you figure out the lk and signature to unlock that??
proof attached below
Слава Украине!!!
can the mods move this to the moto e6s forum so we can spread the news?
luridphantom said:
can the mods move this to the moto e6s forum so we can spread the news?
Click to expand...
Click to collapse
I took the first firmware I got to try from here: https://4pda.to/forum/index.php?showtopic=892755
but the firmware itself is everywhere, for example here:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
DeveloperLuke Roms - Browse /GSIs at SourceForge.net
sourceforge.net
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
You can try to sew any GSI arm64 a/b from anywhere you find and choose the one you like, because smart supports Project Treble.
If you like one and will look cool and work firmware, post links here!
Tested it and it worked! Thanks a lot!
Now looking for delevoping some roms to this device
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
refrigerador67 said:
Im having a little problem, i tried to flash a GSI with "fastboot -u flash system gsi.img", the device didn't boot. Then i tried to flash the stock with the SP Flash Tool, and i throws an error (status_sec_dl_ forbidden), then i flashed it with Lenovo Rescue and Smart Assistant. I tried to flash via fastboot the patched magisk image but it throws an signature error.
Any help? Tha device still says that is unlocked
Click to expand...
Click to collapse
did you use the auth file that comes with sp flash tool? without that your device wont boot properly
Yes, i used the correct download agent and auth file
interesting, i followed all his steps and had no problem rooting it. try backtracking with his scripts again?
Solved it, also me and a developer are working on a new, more simple and automated script. Still haven't figured out how to flash the lk via script.
When is done i will post a complete guide in the moto e6s forums on how to do it, i think it might work well, but i would have to test in a non-unlocked device
Can someone please make a video with explanation, I didn't understand very well what is done, so I won't touch anything, but I thank those who record a video explaining it to me (I'm Brazilian)
Here you have a more straight forward guide, note that is still in testing
[GUIDE] How to unlock bootloader on E6s
Hello, in this guide i will show you how to unlock the bootloader on Moto E6s ;) (Sadly for now this guide is Windows only) CAUTION You are doing this AT YOUR OWN RISK! I will NOT take responsibility if you brick your device! Also, remember to...
forum.xda-developers.com
Excuse my ignorance, do you think it is compatible for the XT2053-5 model?
cannot use fastboot flash boot magiskboot.img
sign failed
partition flash is not allowed
hey is the moto e6+ twrp work on e6s

[Hisense A5] Install stock android ROM [GSI][Android 9/10]

Disclaimer
I am not responsible for any damage you made to your device and responsibe for anything else. Do this only if you know what are you doing.
You have been warned
Click to expand...
Click to collapse
​​​Screenshots/Video:​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't be afraid: The latency you see is caused by the non optimization of the refresh rate of the e-ink panel, which I'd like to port from stock cinese rom. (here if you'd like to help to make the e-ink works on android even faster than stock!!).
System UI is very much smoother than on stock rom (try with scrcpy).
Files:​
Spoiler
Main Folder https://mega.nz/folder/QkVXUDLS#LWYIHVvuiOFxxeZpWruTlg
Download those files:
- https://mega.nz/file/bR5g0I5I#2kwOj8vpsrOUfu-Fpdj1Yboppx9-ZzTk7t3IS-dpT5E
- https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view
- Hisense_A5_LA592C(HLTE202N)_L1657.6.09.06.00_TFDownload_202004090105_user.zip
- https://drive.google.com/file/d/1WKhek-8iDULzjXKxBtVivhnbUeh8Fw89/view
- https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/system_arm64_ab.zip/download
- https://github.com/topjohnwu/Magisk/releases/download/v22.1/Magisk-v22.1.apk
- https://github.com/KinglyWayne/simg2img_win/archive/refs/heads/master.zip
Instructions:​
Spoiler
Bootloader still locked (unfortunately). (or tell me if you managed to unlock )
Android 9 works good.
Android 10 lags.
Before starting: Backup all the data, partitions and most importantly the EFS/QCN file! (Read BACKUP QCN section.)
If you'd like to share a vanilla EFS/QCN file, erasing your IMEI with a blank one before doing it, that would be useful in case someone corrupted his one. You can read more about on the guide.
Make sure to read the Disclaimer above.
- Install QPST and Qualcomm Drivers from Hisense_a5_Flashpaket_6.10.04.00.zip
- Format a microSD into FAT32, then unzip Hisense_A5_LA592C(HLTE202N)_L1657.6.09.06.00_TFDownload_202004090105_user.zip to a folder named HLTE202N_TF and copy it to the microSD. Insert the microSD inside the smartphone.
- Unzip HLTE202N_HLTE202N.R1_L1657.6.03.02.00.7z and replace recovery.img, vbmeta.img, boot.img with those you find inside zip file boot_recovery_vbmeta_6.03.02.zip.
- Enter in EDL MODE by [/I]adb reboot edl[I] or this and connect the device with usb cable to PC.
- open QFIL and select Flat Build, then select Programmer and choose prog_emmc_firehose_8937_ddr_000bf0e1, load XML rawprogram_000bf0e1 and patch patch patch0 from HLTE202N folder.
- Click Download to flash stock ROM 6.03
- Once finished, detach usb cable and reboot the smartphone this way: hold vol up and vol down and power at the same time and as soon as it boot, release only power button until you see vision logo flashing TF
- Wait the smartphone to boot the 6.09 firmware, and once booted, enable USB debugging and OEM unlocking.
- You should see developer options inside the submenu other settings after tapping 7 times on kernel version inside about phone.
- Now check system updates, and OTA update to 6.10.04.00 and no more, just only to build 6.10.04.00.
- After update complete, unzip Hisense_a5_Flashpaket_6.10.04.00.zip
- Open QFIL and select flat build, then select programmer prog_emmc_firehose_8937_ddr_000bf0e1, load XML rawprogram_000bf0e1_joygram and patch patch0 from Hisense_a5_Flashpaket_6.10.04.00/rootkit_6.10.04 folder.
- Enter in EDL MODE and click Download to flash root for ROM 6.10.04.
- Once finished, detach usb cable and to reboot, press power button for at least 20 seconds, or more, to exit EDL mode.
- Once booted up, install Magisk 22.1 and give all permissions, then open it, and click ok if it asks to install additional setup. Phone will reboot.
- Once rebooted, connect the phone via adb to pc and type adb shell
- Once in the adb shell, type su and a popup should appear on the smartphone. Grant permission from smartphone.
Checkpoint ​
- Once here, you could be ready to flash your desired GSI ROM (I've tested many, and look like only compatibility is with Android 9 and 10. 11/12/13 didn't work on my tests, and android 9 is the smoothest performance wise, while android 10 is not really supported and it lags on system.)
At this point, if you'd like to try out different roms, You need to return to Checkpoint, and follow again the steps below.
Your GSI rom should be arm64 and ab partion. Here you can find a list https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list (look for android 9 and 10 roms)
- Unzip your GSI rom, then rename the unzipped .img file to system.img
- copy system.img file to simg2img directory and double click convert.bat to start the unparsing process. It should make another system file inside same folder, but with .ext4 extension.
- copy the system.ext4 file to another directory.
- Open QFIL and select flat build, then select programmer prog_emmc_firehose_8937_ddr_000bf0e1 from Hisense_a5_Flashpaket_6.10.04.00/rootkit_6.10.04 folder.
- Enter in EDL MODE
- Now go on Tools and Partition Manager
- Popup will open, now right click system partition and select manage partition, then erase, then load image.
- Select the system.ext4 file, and it will start flashing.
- Once done, click close, then close again, and then ok.
- wait 10s and detach cable usb from the pc.
- press power button + volume down for 20s to enter recovery. You might want to try some times. Mine worked like this: as soon you feel the reboot vibration, release the power button but keep holding the volume down button until you see recovery logo. or. if it's still stuck on hisense logo (power on), press power and volume down button for 5 seconds, then release power button while still holding volume down, it should enter recovery.
- Inside recovery, erase all the data.
- Reboot, and wait at least 20 minutes, the phone should boot your GSI rom!
Possible error: If you still see Hisense logo with backlight on, probably your ROM has booted, but somehow it won't show you the main display.
Fix: with https://github.com/Genymobile/scrcpy by pressing the screen, after cable is connected and adb devices command launched, where the adb authorization popup would appear, just try to click "ok", and then scrcpy would allow you to see what's happening. Finish the wizard and you should be able to continue on the smartphone now. Keep in mind you may need to use scrcpy at each reboot, because for some ways, the smartphone boots up showing only Hisense logo, but underlying the system is working.
Projects:​- Hisense A5 Port eink display refresh rate modes from chinese to AOSP rom https://forum.xda-developers.com/t/hisense-a5-e-ink-display-modes-port-for-aosp.4497903/
- Hisense A5 adjustable backlight color temperature (Warm to Cold) https://forum.xda-developers.com/t/...lor-temperature-backlight-frontlight.4495045/
- Hisense A5 original EFS/QNC vanilla backup file
https://forum.xda-developers.com/t/hisense-a5-efs-qcn-original-file-backup.4497447/#post-87484995
Hey thanks for getting this far! I wonder if you got any further along? I have an a5 and I would very much like to put a stock rom on
which one recovery do you use ~~where can download it
THANKs
can be taught step by step

Categories

Resources