Requirementsinstall ubuntu on your pc
Download This lineage image, if you want google apps download BVG if you dont want google apps download BVS Make sure to download arm64 not a64 note if you want a pre-rooted lineage OS choose lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz
Download This GSI make sure to download system-roar-arm64-ab-vndklite-gapps.img.xz or system-roar-arm64-ab-vndklite-vanilla.img.xz These are pre-rooted GSI'S
And Download This FILE We will need it later
==============================================================================================================================
BEFORE WE PROCEED IM NOT RESPONSIBLE FOR BRICKING YOUR DEVICE
extract everything in the same folder right click open in terminal
reboot into download mode voulme up + power
Ok now we"ll need to install heimdall on your ubuntu machine by opening the termanil and typing sudo apt install heimdall-flash
type in the terminal heimdall flash --SYSTEM sysnull.img
system will reboot, go into download mode again
now write heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-gapps.img --VBMETA avbnull.img
or if you downloaded the one without GAPPS Write heimdall flash --SYSTEM system-roar-arm64-ab-vndklite-vanilla.img --VBMETA avbnull.img
Boot into stock recovery and do a factory reset
install Termux and download this TWRP image and rename it to r.img
open Termux and type su
Now Write dd if=/sdcard/Download/r.img of=/dev/block/bootdevice/by-name/recovery
if you saved the TWRP image to your internal storage type dd if=/storage/emulated/0/Download/r.img of=/dev/block/bootdevice/by-name/recovery
ok now reboot into TWRP (power + vol up)
wipe dalvik art, cache, system, data, cache
and move the LineageOS image from your pc to your INTERNAL STORAGE THERE WILL BE A FILE NAMED TWRP PUT IT THERE SD CARD WILL NOT WORK IF YOU FLASH IT FROM AN SD CARD THERE WILL BE A STORAGE PROBLEM AND YOU WONT BE ABLE TO INSTALL ANY APPS
Click select storage (click on internal storage)
Click on install image
and now just flash LineageOS and make sure to choose system image
Thanks to @Hex_101 For the rooting tutorial !!
Edit: I Stopped Using The Phone and Switched To An Iphone 14 Pro Max
works fine
Hello, I've been trying to install LineageOS on my device (SM-A207F), and I've followed every instruction so far, but I'm stuck while trying to flash heimdall sysnull.img
After I typed in heimdall flash --SYSTEM sysnull.img in the terminal, I've persistently got this error:
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive end PIT file transfer verification!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've unlocked the bootloader and enabled USB debugging.
I'm using Ubuntu 22.04 LTS (on VirtualBox, Windows 11), also very new to custom ROM, I've only successfully installed LineageOS on an S5 (SM-G900H).
Edit: Solved
I entered the wrong Download Mode (step #2), I thought the Download Mode was the one when I'm supposed to press Volume Up on the same recovery mode to unlock the bootloader (pressing volume up & down together and connecting the cable), turns out I'm supposed to enter Download Mode from the Stock Recovery (pressing volume up & power button)
And probably because I used Ubuntu on a VM
Wurd4Wurd said:
works fine
Click to expand...
Click to collapse
Hi, may I know which version of LineageOS did you install?
I've managed to successfully flashed LineageOS ( lineage-19.1-20221122-UNOFFICIAL-arm64_bgN-secure.img.xz ) but my phone keeps rebooting while setting up.
jfr07 said:
Hi, may I know which version of LineageOS did you install?
I've managed to successfully flashed LineageOS ( lineage-19.1-20221122-UNOFFICIAL-arm64_bgN-secure.img.xz ) but my phone keeps rebooting while setting up.
Click to expand...
Click to collapse
you downloaded the wrong version. you can find it at https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/ and make sure to download lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz use ctrl + f to find it faster. and then flash it again, and it should work perfectly fine.
also if you want root permissions make sure to install phh superuser, flashing Magisk will brick your device.
jfr07 said:
Hello, I've been trying to install LineageOS on my device (SM-A207F), and I've followed every instruction so far, but I'm stuck while trying to flash heimdall sysnull.img
After I typed in heimdall flash --SYSTEM sysnull.img in the terminal, I've persistently got this error:
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive end PIT file transfer verification!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I've unlocked the bootloader and enabled USB debugging.
I'm using Ubuntu 22.04 LTS (on VirtualBox, Windows 11), also very new to custom ROM, I've only successfully installed LineageOS on an S5 (SM-G900H).
Click to expand...
Click to collapse
Use Dualboot instead of VirtualBox, you can find tutorials on youtube but you'll need a spare USB drive
Wurd4Wurd said:
Use Dualboot instead of VirtualBox, you can find tutorials on youtube but you'll need a spare USB drive
Click to expand...
Click to collapse
Yes I've overcome this problem since my second post where my phone keeps rebooting
Wurd4Wurd said:
you downloaded the wrong version. you can find it at https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/ and make sure to download lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz use ctrl + f to find it faster. and then flash it again, and it should work perfectly fine.
also if you want root permissions make sure to install phh superuser, flashing Magisk will brick your device.
Click to expand...
Click to collapse
Okay this version works, but I seem to encounter a problem. Everytime I try to open Storage in Settings, the Settings App crashed, and whenever I try to install an App from Play Store, it says that I don't have enough storage. Does it have something to do with this on the original thread?
Sinshro said:
and move the LineageOS image from your pc to your INTERNAL STORAGE THERE WILL BE A FILE NAMED TWRP PUT IT THERE SD CARD WILL NOT WORK IF YOU FLASH IT FROM AN SD CARD THERE WILL BE A STORAGE PROBLEM AND YOU WONT BE ABLE TO INSTALL ANY APPS
Click to expand...
Click to collapse
jfr07 said:
Okay this version works, but I seem to encounter a problem. Everytime I try to open Storage in Settings, the Settings App crashed, and whenever I try to install an App from Play Store, it says that I don't have enough storage. Does it have something to do with this on the original thread?
Click to expand...
Click to collapse
It's a common issue. Try following these steps:
1. Boot into TWRP
2. Go to Advanced
3. Click on Fix Contents and confirm
4. Reboot
Wurd4Wurd said:
It's a common issue. Try following these steps:
1. Boot into TWRP
2. Go to Advanced
3. Click on Fix Contents and confirm
4. Reboot
Click to expand...
Click to collapse
I thought I made mistakes throughout the process so I tried re-doing everything from the beginning and it finally works without storage issues. Thank you so much for your help, especially pointing out the correct OS image, such a lifesaver
Okay so I've encountered another problem and it looks like a critical one
- My phone's battery was drained, I only realized after trying to boot it up without realizing the battery's at 0 capacity
- It went through the Lineage OS boot animation and went back off
- I charged it and tried to boot it up, then the charging animation comes on
- When I long-pressed the power button, it only showed the charging animation without any other responses.
- The animation keeps going during the charging process, but even after I ejected the charger and tried to boot it up, it still only showed the battery capacity (without the charging animation) and no other responses
- So now I'm stuck with the phone in a battery showing state, pressing Volume Up + Power Button & Volume Down + Power Button does nothing
- I'm currently trying to charge it to full capacity to see if it will actually respond with something after being completely charged
Has anyone ever come across similar situation?
UPDATE: Pressing Volume Up, Volume Down, and Press Button altogether works while in the battery charging state and it booted up normally, so it doesn't look like an actual problem for now
jfr07 said:
Okay so I've encountered another problem and it looks like a critical one
- My phone's battery was drained, I only realized after trying to boot it up without realizing the battery's at 0 capacity
- It went through the Lineage OS boot animation and went back off
- I charged it and tried to boot it up, then the charging animation comes on
- When I long-pressed the power button, it only showed the charging animation without any other responses.
- The animation keeps going during the charging process, but even after I ejected the charger and tried to boot it up, it still only showed the battery capacity (without the charging animation) and no other responses
- So now I'm stuck with the phone in a battery showing state, pressing Volume Up + Power Button & Volume Down + Power Button does nothing
- I'm currently trying to charge it to full capacity to see if it will actually respond with something after being completely charged
Has anyone ever come across similar situation?
UPDATE: Pressing Volume Up, Volume Down, and Press Button altogether works while in the battery charging state and it booted up normally, so it doesn't look like an actual problem for now
Click to expand...
Click to collapse
Good to hear, I was so worried that it will also happen to my a20s.
Wurd4Wurd said:
Good to hear, I was so worried that it will also happen to my a20s.
Click to expand...
Click to collapse
There's another bug on my phone that I haven't found any solutions yet, on phone calls the phone doesn't have any audio input or output (microphone & handset/speakerphone). But WhatsApp calls work just fine. Does this also happen to your device?
I've tried fixing contents through TWRP but it didn't fix the problem
Does it work on the SM-A207M/DS? I have seen the hardware of both phones and they are identical, the only diference being a letter in the model number, which says the region in which was sold in.
jfr07 said:
There's another bug on my phone that I haven't found any solutions yet, on phone calls the phone doesn't have any audio input or output (microphone & handset/speakerphone). But WhatsApp calls work just fine. Does this also happen to your device?
I've tried fixing contents through TWRP but it didn't fix the problem
Click to expand...
Click to collapse
I haven't found a solution to this.
try disabling Disable audio effects, and enable Use alternate way to detect headsets, Force headset switch, and Force-disable A2Dpp offload and then restart your phone.
aerglass said:
Does it work on the SM-A207M/DS? I have seen the hardware of both phones and they are identical, the only diference being a letter in the model number, which says the region in which was sold in.
Click to expand...
Click to collapse
I don't know much about this phone. Add me on discord maybe I can help you. lib#0520
Wurd4Wurd said:
I haven't found a solution to this.
try disabling Disable audio effects, and enable Use alternate way to detect headsets, Force headset switch, and Force-disable A2Dpp offload and then restart your phone.
I don't know much about this phone. Add me on discord maybe I can help you. lib#0520
Click to expand...
Click to collapse
sorry if itype bad (i am typing one handed because my right hand broke)
i installed it on to a broken (that has no wifi or bluetooth, idk why) samsung galaxy a20s from latin america (SM-A207M/DS) which seemed that it was going to no work but it worked perfectly, i have some problems with lineage though, i could fix the phone but i do not care so whatever. I have another samsung galaxy a20s that works fine.
Using this method i flash twrp and repack stock system.img by deleting install-recovery.sh and recovery-from-boot.p
Now i'm have stock rom with twrp
Maybe have methods install system root to stock rom without modify boot.img?
I'm add phh-su to bin and su to xbin and add su.rc to init but phh su can't work with stock rom
minakriss said:
Using this method i flash twrp and repack stock system.img by deleting install-recovery.sh and recovery-from-boot.p
Now i'm have stock rom with twrp
Maybe have methods install system root to stock rom without modify boot.img?
I'm add phh-su to bin and su to xbin and add su.rc to init but phh su can't work with stock rom
Click to expand...
Click to collapse
Did you flash the stock system.img via TWRP? I can't seem to do the same. If you have the zip that you flashed, can you upload it here? It means a lot to me. Thanks
I can send u patched system.img for flash via TWRP if u can send me version of previous installed stock Samsung rom
minakriss said:
I can send u patched system.img for flash via TWRP if u can send me version of previous installed stock Samsung rom
Click to expand...
Click to collapse
A207FXXU2BTH2 Binary 2, Android 10 and region is the Philippines SMA
i need the non-superuser lineage 19.0 and it does not exist on https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/History/
Related
SPECIAL KNO'DIS: This Guide has been changed to refelct proper installation for both types of Maven Pro tablets, be Sure to follow the appropriate guide.
For the purpose of this guide, I'll assume you already have working ADB and Fastboot on your PC, if not, you'll need to set that up first. This guide doesn't cover installation of ether of those. If you're looking for the guide to the Viking Pro (RCT6303W87DK), go here.
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR TABLET!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!! (Or ask for help, there's a lot of friendly people around here)
So, without further ado, lets get started. First, you'll need to know which version of firmware your device is running, this can be found in 2 different ways. From a running device go to: Settings/About tablet and look at the Build number. Or you can boot into stock recovery and the firmware version will be at the top left of the screen.
You should see something like the following, and note the 2nd number after the 2nd "V":
Code:
RCT6213W87DK-ANDROID5.0-V37-V1.9.30 <-- This is x.9.x version of firmware
or
RCT6213W87DK-ANDROID5.0-V68-V1.12.30-B <-- This is x.12.x version of firmware
Now that you know which firmware you have, follow the approriate guide below. I've broken this post into 2 different sections, as each tablet is just a little bit different.
About the Bootloader
This applies to both versions of firmware and tablet users. Turns out, the booloader doesn't have to be unlocked in order to install a custom recovery or root the device. So there's really no reason to unlock it, and I have removed that portion of this guide.
Installing MTK Preloader Signed Drivers
Drivers located Here
x.9.x Versions
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the micro USB on the tablet, the other to the USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
3- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
4- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
5- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug the usb cable from the pc (I find it easier to just keep the micro in the tablet).
x.12.x Versions (Requires Full size Male-to-Male USB Cable)
Steps (Windows 8/8.1/10): For step 2 you will have less than five seconds. Preloader mode is only active for a few seconds. So read first!
1- Extract the drivers to the Desktop and open the Device Manager ("right click" on the Start button, select "Device Manager")
2- Plug your tablet in as such: turn off the tablet. Plug in the full size USB cable to both the tablet and the PC.
3- Plug the micro USB into the tablet, the other to another USB port on the PC, now very quickly in the device manager locate the new device and right click on it. For me, it showed up under "Other devices" and read MT65XX.
4- Select "update driver software" then select "browse my computer for driver software" (make sure "Include subfolders" is selected.
5- Click "Browse..." and navigate to where you extracted the driver zip. You "should" be at the following path: Desktop/MTK Preloader Signed Drivers
6- Click on "OK" then "Next". The driver should install at this point. Once that is done, unplug both USB cables from the PC (I find it easier to just keep them in the tablet).
Installing TWRP
Firmware/TWRP Downloads
Maven x.9.x (Currently Contains: V37-1.9.30 and TWRP)
Maven x.12.x (Currently Contains: V63-V1.12.0-20150802 and V66-1.12.20-B-20150831 Firmware and TWRP)
Special Thanks to: @ShadowCX11 for testing for me.
Be sure you are using the appropriate TWRP for your version of firmware, and do the following:
1- Extract the firmware and the SP Flash Tool to your desktop.
2- Start the SP Flash Tool, and where it says "scatter file loading" click and navigate to the folder where you have the firmware and load the scatter file (depending on device, it could be in the "Images" folder).
3- Once that is done, uncheck everything, and select "recovery" only, from the list, navigate to the TWRP image file and click "Open", then click on the download button.
4- Plug the USB cable(s)* back into your PC. At this point the flash tool will load the recovery to the tablet. DO NOT UNPLUG ANYTHING UNTIL THE FLASH TOOL SHOWS YOU A GREEN CHECK MARK TO INDICATE THAT IT IS DONE, OR YOUR TABLET COULD BE HARD BRICKED AND IRREPARABLE.
5- After you get your check mark, unplug and boot into recovery, hold the Volume + and Power button. When splash screen comes up (the 2 dogs) release the power button.
6- Welcome to TWRP
*Remember, x.12.x requires 2 USB cables to work
ROOT
You can get root by flashing the latest SuperSu zip file located here, be sure to download the flashable zip.
Otherwise, for root, you can use the KingRoot app located here, (get the apk, or "Download for Android") and if you don't want a Chinesse Super User app, you can replace it with the ChainFire SuperSu by going here.
NOTE: This method of replacing KingRoot with SuperSu no longer works properly, and results in a bricked device.
Device Tree
GitHub
CREDITS
@vampirefo (for the CWM Recovery and teaching me about TWRP, there would be no recoveries if it wasn't for him!)
@Bogram (for the lk.bin patch trick)
@smartmanvartan (for the flashing guide)
Reserved
Reserved #2
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
equinox13 said:
Hello! I've had my Maven Pro for a couple months now and I still haven't rooted it like I have with the rest of my devices. I'd love to do it too, but reviewing your instructions, I found that my version number is way different. V66-V1.12.20-B. will that version patch tool still work for it? is there an update that it's refusing to download? Thanks!
Edit: on top of this, i can't get it to even connect (step 2) with any of my microUSB cables. (they work with my other devices)
Click to expand...
Click to collapse
Ooh, a v12, sorry friend, lol. Make sure the tablet is off, and be ready with "Device Manager" open, the preloader only shows up for a bit, then it disappears. The patch tool should still work for you, but the TWRP recovery may not. If it doesn't, the CWM recovery will after I modify it, because it's non-touch.
If neither recovery works for you, you can give me a copy of your "boot.img" file, and I can convert TWRP or CWM to work on your tablet. Also, I've changed the guide up top to include other root methods.
If you have any trouble, by all mean, post, and I'll try to help you through it
Regards,
Nepo
EDIT:
A friend found some V12 firmware, and I'll be uploading it soon. I can get a boot.img file from it to make a recovery.
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
GartimusPrime said:
My maven pro is stuck in a bootloop after I rooted now I don't know what to do. I can't even shut it down
Click to expand...
Click to collapse
You can reflash firmware while it is in a bootloop, I've done this many times. If you have everything set up, drivers, SP Flash Tool, firmware, etc..
Do the following:
1) Startup the Flash Tool and Load your firmware, as described in the OP (be sure to "uncheck" the Preloader)
2) Plug in your micro USB cable to both the PC and the tablet
3) Press and hold the "Reset" button located on the back
4) Click the Download button, then let go of the reset button, it should start flashing the firmware.
If it doesn't the first time, retry steps 3 and 4. I've had it fail the first time before, but work on the second.
Good Luck and let me know how it goes. Also, if the battery is completely drained by the time you read this, just flash firmware normally (again, uncheck the preloader). The tablet has to be powered off to flash it anyway.
Regards
Nepo
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
ShadowCX11 said:
So after reflashing my tablet (a Canadian V12 that had V68, and flashed to V66 trying to unlock the boot loader and install CWM), USB doesn't work. The port doesn't output any voltage, and neither does the keyboard connector. The tablet acts like nothing is there, as does the PS3 controller I tried. Also, before, Firmware Update would say there's no updated firmware. Now, it doesn't seem to do anything. I flashed every partition except preloader, MBR and ebr, and the sec partitions. Do I have to reflash again, or is there something else I can do?
On a completely different note, I tried flashing a patched lk.bin, and it failed with an error I don't remember (I had temporary access to a PC).
One more thing that was quite interesting to me. It seems if you reboot into recovery or bootloader from Android (APM+ or root), you're then able to access the recovery with Power + Vol. Up. Is this known, or was it a fluke?
Click to expand...
Click to collapse
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
NepoRood said:
No USB is a new one on me, I wish I had a x.12 version of this tablet to test on (mine's x.9) I'd try a re-flash, this time, do everything but the preloader, the reason for not flashing a preloader is because it sometimes semi-bricks one of these tablets.
Interesting note, there was a guy on the Viking thread (RCT6303W87DK) that flashed CWM without unlocking his bootloader, and everything is working fine for him...
Regards,
Nepo
PS, Power + Vol Up is the standard way to enter recovery on this device (I have the Xposed APM+ apk installed too)
Click to expand...
Click to collapse
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
ShadowCX11 said:
So just a quick question: Is the device /dev/recovery for sure recovery? I want to see if I can just use dd to flash recovery.
Click to expand...
Click to collapse
Yes, to pull a copy from a running tablet you use dd, and the path is: /dev/recovery
So, I'd do it this way, using adb:
Code:
adb push NAME_OF_RECOVERY.img /data/local/tmp
# Wait for it, then type:
adb shell
#Followed by:
dd if=/data/local/tmp/NAME_OF_RECOVERY.img of=/dev/recovery
#After it finishes:
reboot recovery
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
ShadowCX11 said:
Okay, I got CWM installed! Now to see if I can find a way to build TWRP...
Click to expand...
Click to collapse
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
NepoRood said:
Great! Is the CWM in portrait or landscape? You can always try to port the one I built for the x.9's, just unpack stock recovery, unpack TWRP, swap out the prebuilt kernel and repack.
Click to expand...
Click to collapse
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
ShadowCX11 said:
It's in landscape, and works quite well! I just like the touch interface a bit more. I'll try the kernel replacement.
Click to expand...
Click to collapse
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
NepoRood said:
I prefer TWRP as well, that's why I built it
The only reason I don't have one posted for x.12 users is I can't test it. If you get it to work properly, let me know and I'll add it to the OP so others can benefit. :good:
If not, I can do some builds for you to test, if you don't mind. I have the x.12 kernel in my repo
Click to expand...
Click to collapse
Yeah, I can't figure out how to extract the kernel, because I don't usually have access to a PC. However, I'll take some testing builds if you can make them.
Also, back to the USB issue, a reflash of everything except preloader didn't fix it. However, checking the firmware update now tells me that this is the latest version (which is definitely wrong, since I had v68). It must be an incompatibility between the USA and Canadian variants. If you find a Canadian firm dump, can you send me a link?
---
Hmm, okay.
So I just took a look at the model number on my box, and it's RCT5213W87DKF. That extra letter is what changes this a bit. I'll try seeing what I can dig up in terms of OTA updates, and I'll keep posting about what I find.
---
Okay, so after a few packet captures, I found the tablet makes a GET request to http://tablet12.gyrodock.com:2300/OtaUpdater/android?device=RCT6213W87DK with the User-Agent rk29sdk/4.0, but the server returns a 404 page. When I do this in the browser, however, I get something quite peculiar happen, which interests me. Most of the other places on the site return a Tomcat 404 that has the path in the parenthesis. However, for the OTA URL, it just has empty parenthesis. POST requests to that URL return a 200 OK with no return data, which is also interesting. I'll keep hunting around.
Some people might not have a PC to run flash_tool on, so here's how you can flash recovery/uboot/mbr/ebr2/logo/sec_ro from within Android
I'll use recovery as an example. I'm using a V12 tablet, so steps might be different if you have a V9. I tried to make this guide as revision-agnostic as possible, so correct me if I mess something up.
Root your device. The method I use is KingRoot, because it doesn't require any weird things. You can uninstall KingRoot and flash SuperSU later.
Download a recovery image. Make sure if you have a V12 tablet, you download a recovery image for V12, and a V9 recovery for a V9 tablet, or you'll brick your recovery. I personally prefer TWRP, because it has more features and a nicer UI, but CWM works too.
Get shell access. You can use a terminal emulator.
Type in su, and give the terminal superuser access on your device.
Type in dd if=/sdcard/Download/mavenVY_XXX.img of=/dev/recovery, where Y is 9 or 12, and XXX is CWM or twrp3.0.2. This will flash the recovery image.
Finally, type in reboot recovery. This should reboot into your custom recovery! It might also enable Power + Vol Up access to recovery, however, this hasn't been confirmed.
All the other partitions are similar, just replace the references to recovery images with the respective file names for the raw partition, and /dev/recovery with /dev/[PARTITION]. You can NOT flash the android or usrdata partition while in Android or you'll most likely soft-brick your tablet, however, you can boot into TWRP and go to the terminal and do the flash. You must copy your disk images to /tmp when doing so however, or you'll probably lose the disk image during the flash, effectively causing a brick.
Hope this helps people out!
ShadowCX11 said:
I've found out that it seems the v12 tablets strictly enforce the checksums of partition images, so flashing a custom recovery or uboot does not work with flashtool.
Click to expand...
Click to collapse
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
NepoRood said:
Nice addition, but all you have to do is disable it in the Checksum.ini file (change the 1 to 0):
Code:
[IsEnableChecksum]
CHECKSUM_SWITCH=0
I did that for the v9 versions, but only uploaded the v12 firmware...
Click to expand...
Click to collapse
Oh... makes sense...
ShadowCX11 said:
Oh... makes sense...
Click to expand...
Click to collapse
I'm glad you posted that info, it'll be super handy for folks that may not have access to a PC, or would rather use their device instead of a PC :good:
This procedure has been tested on LENOVO K4 NOTE MARSHMALLOW (S219) and it worked perfectly fine.
i posted this thread since the previous procedures only covers rooting prior to S218.
verified working on s219
DISCLAIMER:
I JUST FOLLOWED THE PROCEDURE PROVIDED BY "AYAN CHOUDHURY" ON YOUTUBE CHANNEL SO CREDIT GOES TO HIM.
IF SO HAPPENED THE PROCEDURE WAS MADE BY ANOTHER DEV AND WASN'T QUOTED PROPERLY BY MR. AYAN COUDHURY. MY APOLOGIES AND GIVE CREDIT TO THE ORIGINAL OWNER OF THE PROCEDURE
I WON'T BE RESPONSIBLE FOR ANY DAMAGE, SOFT BRICK, HARD BRICK, AND OTHER INSTANCES FOR YOUR DEVICES AS IT WORKED PERFECTLY FOR ME 3-4X BEFORE POSTING THIS THREAD.
original vid: https://www.youtube.com/watch?v=fPx8QWnYLNo
Before we start:
Here is the details of my handset
Model: Lenovo K4 note (PH) [MTK MT6753 8CORE 1.3GHZ 3.00GB RAM]
Model #: A7010a48
OSv: marshmallow 6.0
Android security patch level: April 1, 2016
Kernel ver: 3.18.19+ [email protected] #1, su jun12 18:27:10 CST 2016
Build number: A7010a48_S218_160612_ROW
Step 1:
download all necessary files.
all files and links are not mine and credit goes to the owner of the files
adb tools : https://drive.google.com/open?id=0B16daNyhWTx1djhqSkJ6QkFKaUk...
recovery(i.e TWRP) : https://drive.google.com/open?id=0B16daNyhWTx1RlB0U01sUkVHMjg...
aroma file manager: https://drive.google.com/open?id=0B16daNyhWTx1TmJqRmxIUUI3YUU...
Super Su : https://drive.google.com/open?id=0B16daNyhWTx1V2ZobTI0RVpKQ1E...
xposed installer : https://drive.google.com/open?id=0B16daNyhWTx1N2RDc2Y4TzlWaWM...
xposed framework : https://drive.google.com/open?id=0B16daNyhWTx1QmlRTHhXOUMydDQ...
step 2:
a. back up any necessary files from your handset.
b. since some computers doesn't show your lenovo k4 note while on recovery mode, it is imperative to put aroma file manager and supersu on your sd card. "do not extract. just copy them as it is"
take note that the next step will definitely hard reset your device.
step 3:
a. enable developer option on your handset. go to system settings/about and click build 7x or as it says "you are now a developer"
b. go to developer option do this two things
enable oem unlock
allow usb debugging
c. once you are done please connect your device to your laptop
step 4:
a. run adb server (go to adb folder, shift+right mouse click and choose open command window here.
b. it will prompt you to allow your pc to connect/control your devices just click YES
c. on your command window, type ADB DEVICES (it will detect your lenovo k4 note)
d. once detected type ADB REBOOT-BOOTLOADER (your device will reboot)
e. once rebooted, type FASTBOOT DEVICES to verify if you are already in fastboot mode
f. if connected proceed to step 5. if not please repeat procedure
step 5:
a. once connected go to adb folder on your computer. you will see a file named unlock recovery.bat
if not, copy this text
call adb.exe devices
call adb.exe reboot bootloader
call fastboot.exe getvar all
call fastboot.exe oem unlock
call fastboot.exe format userdata
call fastboot.exe erase recovery
call fastboot.exe flash recovery recovery/recovery.by.gursewak.img
call fastboot.exe getvar all
call fastboot.exe reboot
echo done successful please press any key to continue
echo disconnect your phone and press power button untill phone reboots
pause
Click to expand...
Click to collapse
to notepad and save as batch file, name it as UNLOCK_RECOVERY.bat
b. click the UNLOCK_RECOVERY.BAT then it will ask you on your device to confirm, (will add screen shot later on) just press volume up button
c. once the process has been done, (will take few seconds) extract recovery.img to adb folder
d. go to your previously opened command window and type
FASTBOOT FLASH RECOVERY RECOVERY.IMG (the one you extracted)
step 6:
a. once flashed, disconnect your device (it will show a tiny text telling you transmission ok)
b. press and hold the power button for few seconds to turn off the device
IT IS IMPERATIVE THAT YOU WON'T TURN ON THE DEVICE UNLESS THE NEXT STEPS ARE DONE. IF YOU ACCIDENTALLY TURNED ON YOUR DEVICE REPEAT TO STEP 1.
c. press and hold vol up+vol down+ powerbutton simultaneously for few seconds, once you felt a vibration, release power button whilst still holding the vol up and down button
it will show the lenovo screen then go black. (don't worry it means you successfully flashed recovery.img)
d. connect the device to your computer
if lenovo shows on your device, now is the time to recopy aroma file manager and supersu. if not just wait for the screen to turn back on.
e. once twrp recovery is on, go to mount and check SYSTEM. (do not touch anything aside what i unstructed)
d. go back to previous menu and go to install
install aroma file manager and wait for it to finish
f. once installed it will go directly to aroma file manager, go to system folder and scroll down. look for recovery-from-boot.p and delet it
g. once deleted exit aroma file manager (button can be found on right corner)
h. go back and install beta supersu which you copied. (browse sd card)
i. once flashed, reboot system,
step 7:
a. if you made it this far, then you are almost done.
b. just finish the lenovo start up.
c. once done, connect your device again on your computer and copy xposed apk and xposed arm to internal or sdcard
d. install xposed apk
e. turn off your device
step8:
a. reboot to recovery (press vol up and down and power button simultaneously, once you felt a vibration release power button whilst holding vol up and down button. lenovo screen will show and it will eventually go to twrp recovery)
b. click install and install xposed arm
c. onced install. reboot system.
THERE YOU GO... YOU ARE DONE. YOU CAN VERIFY ROOT BY DOWNLOADING ROOT CHECKER FROM GOOGLE PLAY STORE.
WELL I WAS FORCED TO ROOT MY K4 NOTE JUST TO PLAY POKEMON GO.
I WILL UPLOAD SCREEN SHOT ONCE I ALREADY COMPILED THEM. THANK YOU
IF YOU LIKE AND HELPED YOU A LOT PLEASE HIT THANKS AND LEAVE A MSG.
IF YOU HAVE QUESTIONS, JUST COMMENT IT HERE.
Thanks it worked. I was about to complain when twrp recovery does not show up. BUT IT WORKED THANKS
xposed isn't necessary to root the phone. Am I right? Maybe you should explain that in the OP. You'll get people confused down the road if they don't already know what they're flashing.
Sent from my f320 using XDA Labs
Will it work on s219?
I just badly wanna root amd this is the easiest way i found..
Thanks:cyclops:
And yes,one more question,
During unlocking the bootloader, will it only format my phone or both phone and sd card?
infected_162k said:
Will it work on s219?
I just badly wanna root amd this is the easiest way i found..
Thanks:cyclops:
And yes,one more question,
During unlocking the bootloader, will it only format my phone or both phone and sd card?
Click to expand...
Click to collapse
yup....and yuhooooo.
it worked like a charm.thank you very very much:fingers-crossed:
infected_162k said:
yup....and yuhooooo.
it worked like a charm.thank you very very much:fingers-crossed:
Click to expand...
Click to collapse
hi
will it erase internal phone memory (i mean after flushing ROM can i get my data using any recovery software)
i am also using same s219 Rom model lenovo k4 note phone.
Actually i deleted some files unexpectedly from internal memory but i want them back, so i tried many ways but no software is identifying internal memory as a drive. I tried to root using root apps but marshmallow not allowing.
i found this topic, but i have only doubt is after flushing the rom can i recover my data using any recovery software?
Thanks in advance
thank you so much!
now to answer some queries and give thanks...
@Duffy144: glad you like it.
@Bdwilk: thank you for the input, i will do that.
@infected_162k: i haven't tried yet since i haven't been able to check latest OTA, but i will try it now since s218 causes lag and memory leak when using facebook messenger. and as you've said. thanks for the confirmation for s219, at least i am more confident. btw, does this really solve the memory leak of the s218?
@anvesh.k yes it will delete all files as the procedure requires you to factory reset your handset.
Rooted K4 Marshmallow
Damn. Finally. I got root. Can finally get rid of that Cell Broadcast. Thanks Sir ansei. The unlocking of bootloader, flashing of twrp and supersu process is pretty much straight forward and will only take you about less than 10 minutes.
Am not sure if this is a systemless root i have. If so, it's great. I am on S_219. Zero performance or stability issues.
I feel my K4 Note runs smoother and snappier compared to S150 row. Still getting the hang of the revamped user interface though.
Overall, Marshmallow 6.0 S_219 runs great with unlocked bootloader, twrp and supersu.
Can someone confirm if this works with 2 gb / 32 variant?
RK_D2502 said:
Damn. Finally. I got root. Can finally get rid of that Cell Broadcast. Thanks Sir ansei. The unlocking of bootloader, flashing of twrp and supersu process is pretty much straight forward and will only take you about less than 10 minutes.
Am not sure if this is a systemless root i have. If so, it's great. I am on S_219. Zero performance or stability issues.
I feel my K4 Note runs smoother and snappier compared to S150 row. Still getting the hang of the revamped user interface though.
Overall, Marshmallow 6.0 S_219 runs great with unlocked bootloader, twrp and supersu.
Click to expand...
Click to collapse
Can you recovered old data after rooting the device?
anzei19 said:
@infected_162k: i haven't tried yet since i haven't been able to check latest OTA, but i will try it now since s218 causes lag and memory leak when using facebook messenger. and as you've said. thanks for the confirmation for s219, at least i am more confident. btw, does this really solve the memory leak of the s218?
Click to expand...
Click to collapse
Amm, about that memory leak thing, i basically know what that is cause it was a huge problem in my father's phone(gionee m3). But i exactly don't know how to know if it's still there or not as I use messenger hardly 2-3 times a week. guide me about this so I can tell you exactly.
Another thing that will help other users: I have to factory reset my phone due to a google error ( unable to communicate with Google server). I was not sure about root and xposed will be gone or not. But here is the result : lost both, root and xposed. Just flashed both again, super su and xposed framwork, worked
anvesh.k said:
Can you recovered old data after rooting the device?
Click to expand...
Click to collapse
Old data? Not sure what you are referring to. After the unlocking of bootloader, flashing or twrp and root, restarted the phone in normal mode. Went through the setup wizard and all. Reinstalled my usual stuff. Back to where I left in Lollipop. Zero issues with Marshmallow 6.0 S_219.
Sir Ansei, everything is fine except 1 minor issue, when rebooting to TWRP, I often get the black screen. Power cycling the phone works. Any ideas?
RK_D2502 said:
Old data? Not sure what you are referring to. After the unlocking of bootloader, flashing or twrp and root, restarted the phone in normal mode. Went through the setup wizard and all. Reinstalled my usual stuff. Back to where I left in Lollipop. Zero issues with Marshmallow 6.0 S_219.
Click to expand...
Click to collapse
May be what he trying to tell is he accidentally deleted some of his important stuff and now he wants to get it back with the apps that use root to dig around. But as per my experience, it only work if that portion of sd card of internal storage is stayed untouched not if overwritten by something else. But if you already rooted, just give it a try...maybe you'll be lucky...
infected_162k said:
May be what he trying to tell is he accidentally deleted some of his important stuff and now he wants to get it back with the apps that use root to dig around. But as per my experience, it only work if that portion of sd card of internal storage is stayed untouched not if overwritten by something else. But if you already rooted, just give it a try...maybe you'll be lucky...
Click to expand...
Click to collapse
Thanks for understanding my problem
call fastboot.exe flash recovery recovery/recovery.by.gursewak.img - needs to be edited? make sure path is correct and image name.
call fastboot.exe flash recovery recovery.img
Just put recovery.img in the same folder
I cannot get fastboot to recognize my device & perform the bootloader unlock. Whenever I type in " adb reboot bootloader" or click on that "unlock_recovery.bat" file, I get booted into a dark screen where "fastboot" is written at the bottom & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Please tell how to get past this!
sujitmohanty2012 said:
I cannot get fastboot to recognize my device & perform the bootloader unlock. Whenever I type in " adb reboot bootloader" or click on that "unlock_recovery.bat" file, I get booted into a dark screen where "fastboot" is written at the bottom & the command prompt window says < waiting for device> & I am stuck there until I reboot my phone.
Please tell how to get past this!
Click to expand...
Click to collapse
you should install fastboot driver
setpam25 said:
you should install fastboot driver
Click to expand...
Click to collapse
@setpam25 Is there a specific driver for that.? If yes, could you please share the link to download that?
My system currently has the lenovo usb driver 1.16, windows 10 mtk vcom preloader & ADB interface driver (by google) properly installed!
Does this work on s230 update marshmallow
Please help me,
I am stuck there until I reboot system
Guide for rooting and Twrp installation for Zenfone max ZC550KL 615 MSM 8939 :
Warning: Rooting a device automatically voids the warranty. We assume you know what you are doing and we shall not take any responsibility if your device blows up in your face. Be warned.
FILES NEEDED
DRIVERS\TOOLS
a. adb setup; http://www.mediafire.com/file/jsbx6isfpgle319/adb-setup-1.4.3.exe
b. Android usb drivers ;http://www.mediafire.com/file/57fzehmcfqk0y7t/ASUS_Android_USB_drivers_for_Windows_20150212.zip
c.minimal adb and fastboot : http://www.mediafire.com/file/0h36wb7e8aoimvb/minimal_adb_fastboot_v1.3.1_setup.exe
d. Asus bootloader unlock tool for 8939 device : http://dlcdnet.asus.com/pub/ASUS/Ze...513.74708998.1502054577-2083321676.1502054577
TWRP\ROOT FILES
e. custom recovery image file (Twrp) :
https://www.mediafire.com/file/1kyk0q3b99kcrue/Twrp_3.0.2.img
f. SuperSU file (root) : http://www.mediafire.com/file/dchiph3qkml3u8g/PRO-SuperSU-v2.67.zip
STEP BY STEP GUIDE
1. Download and install adb and Android usb drivers if you don't have them already installed, otherwise, you can skip
2. Download and install minimal adb and fastboot and put icon on desktop
3. Download the Asus bootloader unlock tool .apk file to your device and install like an application in order to unlock bootloader(follow on-screen messages)
4. Boot device into CSC MODE(fastboot\bootloader) and connect to PC via usb cable. (To boot into CSC MODE , press and HOLD "volume up key+power key")
5. open minmal adb and fastboot and enter the following commands:
Code:
[COLOR="Red"]fastboot devices[/COLOR]
hit enter on keyboard and the serial number of your device SHOULD show in minimal adb window, if it does'nt then you've not installed your Android usb drivers correctly !
Code:
[COLOR="Red"]fastboot flash recovery[/COLOR]
after this command press the SPACE KEY ON KEYBOARD AND DRAG THE "CUSTOM RECOVERY IMAGE FILE TO THE MINIMAL ADB WINDOW then hit the enter key on your keyboard and Twrp will be flashed .
IMPORTANT !!
After flashing the TWRP file, you should boot directly into recovery by holding VOLUME DOWN+POWER BUTTON do not allow device to boot into home screen at first boot, otherwise stock recovery will be restored !!!
6. After booting into TWRP , FLASH THE ROOT FILE IMMEDIATELY !
WARNING !
if you don't flash the root file once in twrp, you might encounter a bootloop!
some users report a password prompt while in Twrp, just press "cancel" then go to twrp home screen , WIPE-FORMAT DATA, after formatting data , go back to twrp home screen -REBOOT-RECOVERY , after that flash the root file (make sure your root file is on an external sd card .
Just followed instructions word by word and successfully rooted my Asus Max SD 615 !
Thanks !:good:
Plez upload video..
Please upload video for how to root,twrp and adb installing..because i m a android beginner.
Nandha2335 said:
Please upload video for how to root,twrp and adb installing..because i m a android beginner.
Click to expand...
Click to collapse
Well i guess if you follow it step by step there won't be any problem.If you get stuck at some point just comment here.And installing adb is just like the normal installation of any setup files in windows.Regarding the flashing of twrp there is nothing much to do than the steps mentioned above.If you still need a video go for this.https://youtu.be/kmq2Eyzl3wA NOTE:This video makes use of files for the sd410 model,so don't use the files in that video.Get the files from this post.This video can make you familiarize the process,but steps mentioned here is slightly different.
Nandha
Any problem doing this method????
Plez upload custom rom for ZenFone max sd615 model..
Nandha
Thank u so much bro ..i m following as per u r procedure now my mobile was rooted ...
Nandha2335 said:
Any problem doing this method????
Plez upload custom rom for ZenFone max sd615 model..
Click to expand...
Click to collapse
There aren't any custom roms available till now.Try using xposed modules for improved functionality(serves the purpose of custom rom to great extent).
Abhishek P G said:
There aren't any custom roms available till now.Try using xposed modules for improved functionality(serves the purpose of custom rom to great extent).
Click to expand...
Click to collapse
Actually, there's MIUI 8 available, but its in this Russian thread http://4pda.ru/forum/index.php?showtopic=726975&st=9000#entry62639193
jide1 said:
Actually, there's MIUI 8 available, but its in this Russian thread http://4pda.ru/forum/index.php?showtopic=726975&st=9000#entry62639193
Click to expand...
Click to collapse
Miui 8 rom properly working or not
---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------
Abhishek P G said:
There aren't any custom roms available till now.Try using xposed modules for improved functionality(serves the purpose of custom rom to great extent).
Click to expand...
Click to collapse
Bro how to change notification panel ..and status bar
Nandha2335 said:
Miui 8 rom properly working or not
don't ask me, i didn't post any rom here, ask him https://forum.xda-developers.com/showthread.php?p=73339833
Click to expand...
Click to collapse
Nandha2335 said:
Miui 8 rom properly working or not
---------- Post added at 04:29 PM ---------- Previous post was at 04:27 PM ----------
Bro how to change notification panel ..and status bar
Click to expand...
Click to collapse
Try using gravity box after installing xposed framework.There a lot of graphical tweaks in gravity box.
Internal Storage Files Missing
After I flashed TWRP and then entered it, it asked for a password to decrypt my storage. I didnt set any password for my phone so I pressed cancel after which came the TWRP menu. But once I selected the install option so as to flash the supersu file, I was unable to find my zip file in it. When I searched for solution, they said it was because my storage is encryted that I was'nt able to acces the data. They adviced to format data through wipe option in TWRP. But still no use. And to add to the problem, when I tried to reboot into system, I was left with a black screen and couln't get to the homescreen.
Please consider my problem and hoping for your fast reply.
kiranrajr said:
After I flashed TWRP and then entered it, it asked for a password to decrypt my storage. I didnt set any password for my phone so I pressed cancel after which came the TWRP menu. But once I selected the install option so as to flash the supersu file, I was unable to find my zip file in it. When I searched for solution, they said it was because my storage is encryted that I was'nt able to acces the data. They adviced to format data through wipe option in TWRP. But still no use. And to add to the problem, when I tried to reboot into system, I was left with a black screen and couln't get to the homescreen.
Please consider my problem and hoping for your fast reply.
Click to expand...
Click to collapse
Boot back into twrp home screen - WIPE- FORMAT DATA , after that, also from twrp , REBOOT-RECOVERY, after that, go ahead and flash the root file and then try to boot into home screen.
Place the root file on an external sd card.
jide1 said:
Boot back into twrp home screen - WIPE- FORMAT DATA , after that, also from twrp , REBOOT-RECOVERY, after that, go ahead and flash the root file and then try to boot into home screen.
Click to expand...
Click to collapse
Thank for your fast reply. By following your steps, I was successful in rooting the phone but when rebooting back to home screen, the black screen's still there.
kiranrajr said:
After I flashed TWRP and then entered it, it asked for a password to decrypt my storage. I didnt set any password for my phone so I pressed cancel after which came the TWRP menu. But once I selected the install option so as to flash the supersu file, I was unable to find my zip file in it. When I searched for solution, they said it was because my storage is encryted that I was'nt able to acces the data. They adviced to format data through wipe option in TWRP. But still no use. And to add to the problem, when I tried to reboot into system, I was left with a black screen and couln't get to the homescreen.
Please consider my problem and hoping for your fast reply.
Click to expand...
Click to collapse
I guess you have copied the super su file to external sd card.Formatting data as mentioned by jide1 did remove the encryption for me.If it doesn't work do advanced wipe with only the data,cache and dalvik cache boxes checked.Note:don't check any other box.Then reboot into twrp.Go to mount in twrp and see that your external sd is mounted.Now access the external sd card in install option and you will find the files of super su.
How to get into twrp recovery?
There is problem after flashing when i press volume down+power button its restarts twrp recovery got lost
6goyal said:
There is problem after flashing when i press volume down+power button its restarts twrp recovery got lost
Click to expand...
Click to collapse
Flash twrp again ,disconnect usb cable from pc, then press and HOLD "volume down" AND "power button" when device vibrates, RELEASE "power button" WHILE still holding "volume down" , that should do the job.
Need stock boot.img
I require the stock boot.img so if anyone is kind enough to upload it, ill be greatful. Or if anyone knows how to extract it from the raw image, that'd also be appreciated.
Volker802 said:
I require the stock boot.img so if anyone is kind enough to upload it, ill be greatful. Or if anyone knows how to extract it from the raw image, that'd also be appreciated.
Click to expand...
Click to collapse
Download the official firmware from Asus website and unpack the zip file, and you'll see the boot.img file there.
STEP BY STEP GUIDE FOR LG V20 H918 UNLOCKING BOOTLOADER, DOWNGRADING, ROOTING AND INSTALLING CUSTOM ROMS (NOOB FRIENDLY)
DISCLAIMER: I'M NOT THE DEVELOPER OF ANY OF THE BELOW SOFTWARE'S AND YOU PROCEED WITH YOUR OWN RISK AS THIS INVOLVES BRICKING OR DAMAGING YOUR MOBILE IF THE PROCEDURE IS NOT FOLLOWED CORRECTLY. I'M JUST SHARING THE WHOLE PROCESS WHICH I HAVE FOLLOWED TO ROOT AND INSTALL TWRP IN MY LGV20 H918 UNLOCKED T MOBILE.
AND I HAVE TESTED THIS IN MY OWN DEVICE AND WAS ABLE TO ROOT AND ACHIEVE TWRP.
THIS IS ONLY FOR LGV20 H918 VERSION
ENSURE INTERNET IS UP AND RUNNING IN YOUR PC
EDIT: THE WHOLE PROCESS HAS NOW BEEN AUTOMATED IN TWO SIMPLE STEPS TO PREVENT ANY POTENTIAL DAMAGE TO YOUR DEVICE. THANKS TO THE LAFSPLOIT CREATOR BRIAN @runningnak3d.
JUST FOLLOW THE PROCEDURE BELOW AND YOU SHOULD HAVE YOUR DEVICE ROOTED IN NO TIME
1. BACKUP ALL YOUR IMPORTANT DATA BEFORE PROCEEDING.
2.MAKE SURE YOU HAVE CHARGED YOUR PHONE TO AT LEAST 90 PERCENT
CHECK YOUR PHONE SOFTWARE VERSION IN SETTINGS---ABOUT PHONE----SOFTWARE INFO
IF IT IS ANYTHING BETWEEN H91810P TO H91810U MEANS IT IS ARB1 (ANTI ROLL BACK 1) AND YOU NEED TO USE LAFSPLOIT METHOD TO ROOT AND INSTALL TWRP,
IF YOUR VERSION IS H91810O OR BELOW (ARB0), YOU CAN EITHER USE DIRTYCOW OR LAFSPLOIT METHOD FOR THE SAME.
IF YOU ARE ON ARB1, PLEASE FOLLOW THE METHOD BELOW,
PART 1: DOWNGRADING
IF YOUR VERSION IS H91810 (Q, R, S, T, U) YOU NEED TO DOWNGRADE TO A LOWER VERSION ( H91810P) TO EXECUTE LAFSPLOIT.
IF YOU ARE ALREADY ON H91810P, YOU STILL NEED TO RE FLASH THE H91810P KDZ AGAIN FOR THE LAFSPLOIT SCRIPT TO WORK CORRECTLY.
DOWNLOAD H91810P KDZ FILE FROM BELOW
https://androidfilehost.com/?w=files&flid=282709
DOWNLOAD AND INSTALL ALL THE FILES BELOW IN YOUR PC
UPPERCUT AND LGUP----
http://downloads.codefi.re/autoprime/LG/Flash_Tools/LGUP/
LG DRIVERS---
http://tool.cdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
CONNECT YOUR MOBILE TO YOUR PC IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
RUN UPPERCUT.EXE WHICH WOULD OPEN LG'S UPDATER TOOL AUTOMATICALLY.
INSIDE THE LG UPDATER TOOL, CLICK ON BIN AND SELECT THE H91810P KDZ FILE DOWNLOADED EARLIER.
NOW SELECT UPGRADE AND FLASH
ENSURE THE USB CABLE IS CONNECTED THROUGH THE FLASHING PROCESS AND WAIT FOR YOUR PHONE TO REBOOT AND THEN REMOVE THE USB CABLE.
CHECK THE SOFTWARE VERSION AND ENSURE IT IS H91810P
PART 2: UNLOCKING BOOTLOADER
HEAD TO SETTINGS---ABOUT PHONE----SOFTWARE INFO (ENSURE IT IS H91810P)
ENABLE DEVELOPER OPTION IN YOUR PHONE BY CLICKING ON THE BUILD NUMBER MULTIPLE TIMES
NOW HEAD TO SETTINGS---DEVELOPER OPTIONS
TURN ON OEM UNLOCKING, ENABLE USB DEBUGGING AND DISABLE 'VERIFY APPS OVER USB'
NOW CONNECT YOUR PHONE TO PC AND OPEN ADB COMMAND CENTER PROMPT IN YOUR PC
adb devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN ADB
adb reboot bootloader--->THIS REBOOTS YOUR DEVICE IN FASTBOOT MODE
fastboot devices---->CHECK IF YOUR MOBILE IS CORRECTLY RECOGNIZED IN FASTBOOT
fastboot oem unlock---->THIS COMMAND WOULD UNLOCK YOUR BOOTLOADER AND RESET's YOUR DEVICE.
fastboot oem device-info OR fastboot getvar unlocked ----->THIS WOULD CONFIRM IF YOUR BOOTLOADER HAS BEEN UNLOCKED OR NOT.
fastboot reboot-----> THIS WOULD REBOOT YOUR DEVICE
IF THE BOOTLOADER HAS BEEN SUCCESSFULLY UNLOCKED, THE DEVICE WILL SHOW AN UNLOCKED BOOTLOADER WARNING MESSAGE WHILE BOOTING (THIS CAN BE IGNORED OF COURSE)
PART 3: CREATING A BOOTABLE LINUX USB USING FWUL
DOWNLOAD FWUL_v2.7_x86_64_15GB.zip FROM THE LINK BELOW AND EXTRACT THE IMAGE FILE SOMEWHERE IN YOUR PC.
https://androidfilehost.com/?w=files&flid=214529
DOWNLOAD RUFUS FROM BELOW AND INSTALL
https://rufus.akeo.ie/
INSERT A PEN DRIVE IN YOUR PC AND RUN RUFUS.
INSIDE RUFUS SELECT THE IMAGE FILE AND SELECT START (AFTER SELECTING START SELECT DD MODE IN THE DIALOGUE BOX) TO CREATE A BOOTABLE PEN DRIVE (WARNING: THIS WOULD FORMAT YOUR PEN DRIVE)
NOW YOU SHOULD BOOT YOUR PC FROM THE BOOTABLE USB STICK WHICH YOU HAVE JUST CREATED
THIS WOULD MAKE YOUR PC RUN LINUX OS
TYPE PASSWORD AS linux AND ENTER
PART 4: INSTALLING TWRP AND ROOTING USING LAFSPLOIT
BEFORE PROCEEDING ENSURE YOU BOOT YOUR PHONE AND DONE ALL THE BASIC SETTINGS
NOW HEAD TO THE DEVELOPER OPTIONS IN YOUR DEVICE AND ENSURE OEM UNLOCKING AND USB DEBUGGING ARE SWITCHED ON.
NOW CONNECT YOUR DEVICE TO THE PC (RUNNING LINUX OS FROM PENDRIVE) IN DOWNLOAD MODE (SWITCH OFF YOUR MOBILE AND CONNECT THE USB FROM PC WHILE HOLDING THE VOLUME UP BUTTON SIMULTANEOUSLY)
DOUBLE CLICK ON THE LG FOLDER INSIDE FWUL DESKTOP
INSIDE THAT, DOUBLE CLICK ON LGLAF(RUNNINGNAK3D) ICON WHICH WILL OPEN A TERMINAL
ENTER THE BELOW COMMANDS
git pull
git checkout h918-miscwrte
./step1.sh
THE ABOVE COMMAND FLASHES TWRP RECOVERY ONTO YOUR DEVICE.
WAIT AND PULL OUT YOUR DEVICE WHEN IT ASKS TO.
RECOMMENDED: NOW THAT TWRP HAS SUCCESSFULLY INSTALLED, YOU CAN MANUALLY FORMAT,FLASH LATEST TWRP RECOVERY AND USE ANY METHOD LIKE MAGISK OR SU FOR ROOTING.
INSIDE TWRP RECOVERY. FIRST FORMAT USING WIPE--ADVANCED FORMAT--TYPE yes AND FULL DO A FULL FORMAT, THEN FLASH MAGISK AND THE LATEST TWRP RECOVERY BELOW.
MAGISK ZIP DOWNLOAD:
https://github.com/topjohnwu/Magisk/releases/download/v16.0/Magisk-v16.0.zip
LATEST TWRP BY PHOENIX(H918):
https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
OR
IF YOU ARE UNSURE ABOUT FORMATTING AND FLASHING, JUST USE THE BELOW COMMAND TO DO ALL THE WORK AUTOMATICALLY
CONNECT YOUR DEVICE AGAIN IN DOWNLOAD MODE AND ENTER THE FOLLOWING COMMAND
./step2.sh
THE ABOVE COMMAND FORMATS YOUR DEVICE AND FLASHES MAGISK TO ACQUIRE ROOT.
TIP : IF YOU FACE ANY ENCRYPTION ERROR AFTER USING STEP2. SH, DO A ADVANCED FORMAT WITHIN TWRP AND FLASH MAGISK AND LATEST TWRP BY PHOENIX MANUALLY.
YOU ARE NOW ROOTED WITH TWRP RECOVERY INSTALLED.
REMEMBER TO BACK UP THE CURRENT ROM BEFORE FLASHING ANYTHING..... DO CHECK POST #2 FOR OTHER TWEAKS
IF YOU WISH TO UPDATE TO LATEST STOCK (10U) AND KEEP ROOT AND TWRP, JUST FOLLOW THIS LINK AND DO REMEMBER TO ROOT USING MAGISK AFTER FLASHING THE ROM BEFORE YOU BOOT.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
I WOULD LIKE TO THANK ALL THE DEVOLEPERS WHO HAVE CREATED THE ABOVE SOFTWARES WITHOUT WHICH THIS ISNT POSSIBLE.
CREDITS:
@autoprime FOR HIS UPPERCUT TOOL
@steadfasterX FOR HIS FWUL TOOL
@Phoenix591 FOR HIS WORKS ON TWRP RECOVERY
AND FINALLY, @runningnak3d FOR HIS EXCELLENT WORK IN ROOTING OUR DEVICE :good:
WHAT NEXT?
NOW THAT YOU HAVE ROOTED YOUR MOBILE, I WOULD RECOMMEND DOING THE BELOW TWEAKS FOR FURTHER ENHANCED EXPERIENCE....
1.THERMAL THROTTLING
IF YOUR ARE STILL ON A STOCK BASED ROM , I WOULD STRONGLY RECOMMEND TO RECONFIGURE YOUR THERMAL FILE TO PREVENT ANY POSSIBLE LAG WHEN USING EXTENSIVELY...
FIRST DOWNLOAD THE FILE BELOW:
https://drive.google.com/file/d/0B0W3xXHgfOxvLUpKNWhrWDE0TDg/view
USE A ROOT EXPLORER (PREFERABLY ES EXPLORER) AND GO TO ROOT/SYSTEM/ETC.
YOU SHOULD HAVE A FILE NAMED thermal-engine-8996.conf
RENAME IT TO thermal-engine-8996.conf.bak (JUST FOR A BACKUP IF ANYTHING GOES WRONG)
ENSURE THE ABOVE DOWNLOADED FILE IS IN .conf FORMAT
IF IT ISN'T , RENAME TO thermal-engine-8996.conf
NOW SAVE THE FILE TO THE SAME DIRECTORY VIZ ROOT/SYSTEM/ETC
GIVE PERMISSION TO THIS FILE TO rw-r--r-- USING THE ROOT EXPLORER ( SELECT FILE--->PERMISSION--->READ WRITE, READ, READ)
FINALLY SAVE AND REBOOT.
THIS WOULD OVERWRITE THE THERMAL LINKED PERFORMANCE OF THE CPU TO AVOID ANY LAG WHEN USING EXTENSIVELY.
2. RCTD REMOVER
ALSO I WOULD STRONGLY RECOMMEND TO REMOVE THE LG'S RCTD CCMD AND TRITON MONITORS AS THESE WOULD RUN CONTINUOUSLY IN A ROOTED LG PHONE AND CONSUME LOT OF RESOURCES...
JUST INSTALL THE RCTD REMOVER APP FROM BELOW LINK:
https://labs.xda-developers.com/store/app/com.zacharee1.rctdremoverforlg
GRANT SU PERMISSION AND CHECK THE DESIRED FILES (I CHOSE ALL THREE FILES) AND CLICK ON PATCH, FLASH IMAGE AND REBOOT (THIS WOULD PATCH THE BOOT FILE, SO AGAIN IT IS ADVISABLE TO CREATE A BACKUP OF THE CURRENT BOOT IMAGE USING TWRP OR WITHIN THIS APP ITSELF)
3. SCREEN CALIBRATION:
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
INSTALL KERNAL AUDITOR APP FROM PLAY STORE AND GRANT SU ACCESS
CHANGE THE BELOW VALUES WITHIN THIS APP (SCREEN SETTINGS)
Minimum RGB value = 35
Saturation Intensity = 27
Screen Hue = 1520
Screen Value = 112
Screen Contrast = 132
THIS WOULD SOMEWHAT REDUCE THE BLUE TINGE AND GHOST APPEARANCES OF THE SCREEN
CREDITS: @Holyman007 for his thermal tweak @Zacharee1 for his rctd remover app
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
turdbait said:
I was just about to create a post asking for a step by step for dummies so thank you very much for this! Going to do this sometime tomorrow or Tuesday and will update if I succeed or not. :good:
Got a question. Does this method stop the second screen from working?
Click to expand...
Click to collapse
this would end up with a stock rooted phone with twrp recovery if all the methods are correctly followed..
......final result would be.... you would end up with a rooted stock rom with a twrp recovery....
your second screen will work perfectly.....
please let me know if you need a different thread for installing custom rom, and to reduce the lag., install sound mod to get maximum sound output and customize second screen... i will create a noob friendly thread for these as well......
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
kish9046 said:
Also check the original lafsploit thread @
https://forum.xda-developers.com/v20/how-to/root-lafsploit-h918-version-t3773443
Click to expand...
Click to collapse
Thank you, I've been reading up on the main lafsploit thread for awhile but I was still not sure about the whole flashing KDZ file and stuff so when you posted this thread it was a motivator to try it out. Got a day off from work tomorrow so gonna try it then so I don't got to worry about the time.
I'm interested in the max sound output and second screen customization if you got the time and its not to much to ask. If you want to wait till either someone else comes along thats interested or till I root just so you don't waste your time I shall update hopefully sometime tomorrow. Thanks again.
kish9046 said:
sha256sum h918-twrp.img ----> THIS WOULD AGAIN THROW A HASH, CHECK IF BOTH THE HASHES ARE ABSOLUTELY SIMILAR
Click to expand...
Click to collapse
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
onlineaces said:
Excellent. Just a friendly suggestion, however. I would change the instruction above to use the word EXACT instead of SIMILAR, otherwise people may continue erroneously. The hash numbers must be exact.
Click to expand...
Click to collapse
Thanks for the heads up.... Changed to EXACT...
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
turdbait said:
I successfully have root now, thank you! If you're still interested in doing a guide on how to do the second screen customization I'd be grateful.
Click to expand...
Click to collapse
great to hear that u have root now.... will post soon on other mods including a step-by-step process on removing rct soon....
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
cnjax said:
All this stuff can be found already in the forums so you posting guides is redundant js
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Glad someone actually laid it out step by step.
kish9046 said:
Thanks for the suggestion... but i thought this would help noobs like me to explore more about our device without doing any harm to it.....
Click to expand...
Click to collapse
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
BROKEN1981 said:
so i just wanted to say thank for for the very noobie step by step guide. im soooo use to odion and adb flash commands.
just 1 thing i had trouble with was trying to push magisk and twrp over. I rooted by pushing magisk over with otg but no twrp on recovery. then i saw it said it was on download mode. from dl mode i just flashed twrp to recovery.
Click to expand...
Click to collapse
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
kish9046 said:
So i assume you have both TWRP and root now?..... And can i ask which version r u in now....ARB0 or 1
Click to expand...
Click to collapse
Abr1 yes I am rooted with twrp.
As I said, the commands to push magisk and twrp to sd did not work. I used usb otg in twrp to push magisk, but forgot to put twrp to flash as well.
I forgot that twrp had replaced download mode, so I was going a bit nuts trying to figure out how to get twrp to recovery. Lolol
Now I'm on latest update with rtcd removed thanks to the op who hosted it on xda as a flashable zip.
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
As you are in twrp, you can manually flash magisk zip and twrp recovery.....
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.
tenkensword said:
Hi guys, sadly I'm at the last step and got stuck.
I did everything, and managed to get to the part where you WIPE de data using TWRP, Mount, but when I go and type
adb push Magisk...
adb push h18...
I get an error saying that Cannot stat : No such file or directory
I'm unable to figure out what I'm doing wrong
Any idea?
Click to expand...
Click to collapse
Download magisk and twrp here https://androidfilehost.com/?fid=746010030569963731
While you are in the last step, in mount, select otg USB. You can push it to SD card and manual flash.
If you booted to system without magisk and flashing twrp, power off the phone, hold volume up, put in the USB, connect to PC. This will put you in twrp since download mode is replaced by twrp.
Now you can flash both files.
Below you will find a download for my modification of a ported Team Hovatek TWRP file as their TWRP did not support OTG. Thanks to Team Hovatek for making a nice porting tool. Unfortunately it took some days and late nights of work to get the ported TWRP to actually be useful as this phone needs OTG support to use TWRP.
When I recently got the Unihertz Atom I didn't realize that it had no micro SD card slot for an external SD card like the Unihertz Jelly Pro had. However it does have OTG support unlike the Jelly Pro but I could not find any TWRP versions for the Atom. So I found a TWRP porting tool from Hovatek and I was able to create a TWRP version but USELESS unfortunately as that version of TWRP did not have OTG support for the Atom.
To make matters worse that TWRP can't deal with the encrypted internal storage of the Atom so there was no way to do a backup of your system. It was possible to format data in TWRP and do a backup to it but upon reboot all that data was gone and reset by the Atom as an essentially new phone being setup for the first time.
I needed a way to modify the ported TWRP so it would recognize an OTG flash drive or USB flash with an OTG cable. I used Image Kitchen to disassemble the original Atom Recovery image and also the modded TWRP recovery image so I could find what was missing from TWRP that was there in the original setup. After a whole lot of reassembling and reflashing various attempts to fix the OTG problem I finally got it. Had to add different lines of code to 3 different files within the unpacked TWRP recovery for it to finally recognize an OTG attached flash drive.
A couple notes on using your external flash drive with TWRP. First you want to insert the flash drive with an appropriate USB type C OTG adapter or cable. Or I see Sandisk (and possibly other brands) are now making a flash drive with USB and Type C dual setup for OTG use.
Bootup your regular phones Android system and look in the pull down notifications - it will ask if you want to use the flash drive as storage. Answer yes and it will then Format it to FAT32 0x0C type which is different than what it was fresh out of the package as most will be FAT32 0x0B type. Once formatted the way the Atom wants it you can use it. However if you put the drive back in your Windows computer it may not see the drive at all. The solution is to open Windows Disk Management and Assign it a drive letter. Once that is done you can read and write to it from both Android and Windows or Linux.
Once that is done you can turn off your phone (IMPORTANT). Do not use any apps that reboot into recovery after installing this TWRP or you will likely just get a black screen and it won't boot up until you reflash the preloader, boot and recovery.
To get into recovery hold down the Volume UP button and the Power button at the same time until you see Unihertz then release both. This is of course after you have flashed TWRP. More on that below. Once your are in TWRP you may have to remove your Flash drive if you had it plugged in during recovery boot up - then reinsert it for TWRP to see it. You can then see it when you mount storage or select storage and it should show the size of your flash drive.
You can then backup your Boot, Recovery, EMMC, System and cache. However the data on the Atom seems to be encrypted in a way that this TWRP does not see it so it will be best to use something like Titanium backup for your Apps and their data. The TWRP though will ensure a complete backup of your system and it's settings as well as the other items mentioned above. I am still looking into why it can't see the encrypted data part of the phone but for now it's nice to have an image of all the rest of the phone. If anyone can help with that I would appreciate it. So far I've tried several 'no encrypt scripts' and ones to turn off DM verity I found on XDA but none of them worked on this phone.
Here is the download of my modded TWRP and also a link for the SHA-256 of it:
TWRP mod: TWRP mod by droidzer1
SHA-256 for file above: SHA-256 for TWRP mod Love the Atom - fast Octacore 4GB Ram - 64GB Internal storage, rugged and tiny as an underfed mouse. :silly: Enjoy !
Notes on Installing this TWRP on your Atom
There are two ways I have used to install this TWRP onto the Atom. One way (and the best way IMO) is to use the SP Flash tool version 5.1828. The other is to use Fastboot. I believe for both methods you need to enable developer options on your phone and turn on OEM unlocking. But if you use Fastboot you also have run the line: "fastboot oem unlock" to install TWRP and that will wipe your phone to a new reset condition plus you will see the 5 second "Orange State" pause screen every time you turn on the phone. To eliminate the "Orange State you can run : "fastboot oem lock" but that will once again totally reset your phone wiping everything including apps and settings. So I prefer using SP Flash tool to avoid all that.
When installing with SP Flash tool I always flash the preloader, boot and recovery (the TWRP modded one) and of course the scatter file. It seems if you don't flash all of those it sometimes doesn't want to boot up.
Also this mod is for the official Unihertz 11-30-2018 ROM version which is the latest update I've seen as of a week ago. I don't know if it will work for other versions. You will want to download that ROM to get the scatter file that is needed by SP Flash tool and it's always good to have an original ROM just in case. Link for the new 11-30-2018 Atom ROM here: 11-30-2018 Atom ROM If you are not on that version you could backup your apps and data with Titanium backup and then install the new ROM while flashing my modded TWRP all at the same time. Just make sure the TWRP you download is named "recovery-verified.img" when you replace the stock one in the SP Flash tool list on the Download page. Also make sure on the tools 'Connections' setting that you check 'Battery installed'.
IMPORTANT!!! - Every version of SP Flash tool I've used shows up as having a virus or trojan and although it may probably be a False positive to be safe I always run Shadow Defender before starting the SP Flash tool. There may be other similar programs but I found this to be one of the best as it totally freezes your computer and hard drive(s) so nothing can be changed or written permanently to them while in Shadow mode. Once you reboot everything is back to a normal state and any changes that may have been made are gone. SP Flash tool available here: SP Flash tool v5.1828 I strongly suggest you use this latest version as previous ones had some issues in completing this project.
A couple quick notes on using the SP Flash tool: It is best to start the tool, have all your items in the check boxes loaded (select scatter file location first) check and locate preloader, boot and recovery - the preloader and boot are from the original ROM you downloaded from the above link. Unzip it and you'll see the needed files inside along with the scatter file.
Once that is ready turn OFF your phone and hook it up with the original USB-C cable to your computer. Wait for it to show the battery charging screen and wait till all that disappears and you have nothing but the black screen. (Or per user SepticFuddy you can hold the Volume Up key while inserting the USB cable and it will connect quickly - I have not tested it this way). Then click on the Flash tool download button. After that you need to push the Atom Power button once briefly - not long enough to turn it on - just a brief click. After that you should see the Flash process going on - it only takes a few seconds to load the preloader, boot and recovery and then you will see a "done" with a big check mark. Remove your phone then and boot into your regular Android OS or use Volume Up and the Power key to boot into your TWRP. :highfive:
Why TWRP doesn't work with Encryption - from TeamWin
I guess this may explain why it is unlikely to get TWRP to work with the encrypted data partition - straight from Teamwin's TWRP website:
"Why doesn't TWRP support encryption on my device?
TWRP encryption is supported in 2 phases. The first item is keeping up with the newest support from AOSP, which can require lot of changes and integration with the new AOSP release. This can take time especially if we have to wait for reference devices to test with. The second item is custom blob support and integration with device OEM firmware.
Even if your device supports AOSP encryption and decryption, it usually requires custom blob support. The process of figuring this out may take time and may never be done. Some vendors such as Samsung use their own encryption techniques. Without heavy deconstruction/decompiling of custom library blobs, and successful ports by an active maintainer, this may never be done. Encryption support is a nice thing to have in TWRP, and not a must have support option. We feel that the ability to backup system and install custom firmware can outweigh having no TWRP support at all."
From: TWRP Website FAQ on Encryption
How I fixed TWRP
For anyone who wants to try the mods their self if you don't trust using the recovery I uploaded I believe these are the changes I made to the ported TWRP. You need of course the porting tool from Hovatek and after you have ported your original recovery you will want to use Image Kitchen to make these mods to the ported image:
Use Image Kitchen to unpack the ported TWRP recovery. In the Ramdisk folder this line "ro.agui.otg_usbdisk=yes" orginally found in the prop.default of the original recovery needs to be put into the file "default.prop" which is a different file name than the original but I am sure is the same purpose and was referenced in the original by a small file with that name.
Then this line "/dev/mt_otg_test(/.*)? ubject_r:mt_otg_test_device0" from the original recovery image in the file "nonplat_file_contexts" I believe I copied into the file "file_contexts" in the TWRP image in the Ramdisk folder.
Note - the above code line that has a smiley in it is because there is the letter "o" followed by a colon. Replace the smiley with "o" and : no spaces between it and the letter 'u' before it or between 'o' and :
I think the third file I modified was found in the unpacked folder /ramdisk/etc in the file 'recovery.fstab' and I took this line "/devices/platform/mt_usb* auto vfat defaults voldmanaged=usbotg:auto " from it to add to the same file in the ported TWRP. Then just repack everything in Image Kitchen and you should have a TWRP recovery that works with OTG.
If you aren't familiar with how to use Image Kitchen it would be best to google how to use it. I have left out some of the basics such as needing to Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the unpacked stock recovery and overwrite those two files in ported TWRP folder. Best to look for an instruction article on techora.net about porting TWRP on mediatek devices.
Thank you, it's awesome! But how did you manage to flash Magisk? I can't flash it as /data and /storage can't be mounted.
You should be able to flash it with Fastboot by using command:
fastboot flash boot /path/to/patched_boot.img OR simply put it in the fastboot folder and type:
fastboot flash boot boot.img (the patched boot image)
You may want to review info on the Magisk thread here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This method of course is done with you computer and USB cable attached to the Atom. Make sure you have correct drivers for it to fully recognize your phone.
A bit more info from topjohnwu's Magisk thread mentioned above:
Via Magisk Manager:
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/Download/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
If the above method fails for some reason you should also be able to flash to patched boot image with SP flash tools as long as you have the scatter file for the ROM you have installed on your phone. As I mentioned if you flash the patched boot image that way I found it best to also flash the preloader and recovery at the same time.
Cannot mount /data
What you did here was remarkable. I love the Atom so I never tried to tinker with recovery since I might end up with a bootloop. I hope we find a solution soon on how to mount /data.
post-root network failure
First off thank you for doing the research and posting in the thread to help us root this awesome little device.
I followed your steps to the "T" and I was able to successfully patch magisk and re-download it back onto my atom and it was rooted BUT, there seems to be some sort of network issue that I'm stuck on, I'm unable to turn on the wi-fi and bluetooth and every few seconds I keep getting an error message that says "bluetooth keeps stopping" consistently whenever I have the phone on.
I was wondering If you had any idea on what might be causing this, or if you had this problem.
thank you, and I look forward to hearing back from you
droidzer1, Finally got to post now and wanted to thank you for your work on the Atom. I got it rooted and got TWRP working too with only some frustrations because I got in a hurry and missed a detail the first try. I haven't found any problems and have had it running about 2 weeks now with root and TWRP. Nice to have root and of course great to be able to do a whole system backup now!
---------- Post added at 03:08 AM ---------- Previous post was at 03:02 AM ----------
hayestak said:
First off thank you for doing the research and posting in the thread to help us root this awesome little device.
I followed your steps to the "T" and I was able to successfully patch magisk and re-download it back onto my atom and it was rooted BUT, there seems to be some sort of network issue that I'm stuck on, I'm unable to turn on the wi-fi and bluetooth and every few seconds I keep getting an error message that says "bluetooth keeps stopping" consistently whenever I have the phone on.
I was wondering If you had any idea on what might be causing this, or if you had this problem.
thank you, and I look forward to hearing back from you
Click to expand...
Click to collapse
Were you able to get this fixed? Doesn't look like droizer1 has been on here recently. Mine didn't have either of those issues. Have you tried doing a factory reset and doing the whole process over? I think sometimes just a computer PC might glitch something on your phone so doing it over might skip the hiccup.
---------- Post added at 03:48 AM ---------- Previous post was at 03:08 AM ----------
Since droidzer1 first posted this in early January you might try using the version of Magisk that was available at that time as I think by later March when you posted there was a newer version out and I've found some versions of Magisk to not work a hundred percent and had to use an older version on some phones.
The latest Magisk (19100) + Xposed (v90 beta 3) work fine for me using the TWRP posted above, in case people were wondering about it.
R
Lost in reboot ...
Hi
I urgently need some help. I seem to be lost...
I have successfully installed TWRP on my Unihertz atom. And I can manage to go into either TWRP mode or into fastboot mode.
I can also successfully unlock the Unihertz atom with:
fastboot oem unlock-go
But what is next?
If I reboot, my phone constantly reboots. It cycles into reboot without Android coming up.
(perhaps I made something wrong).
What I actually want is: The phone should boot including Magisk.
Can anyone please help me what commands I have to issue (with the phone connected to my linux computer via USB) in order
to recover to a normal reboot? Which image-file should I use (please provide URL)?
Can anyone please help me what commands I have to issue to flash Magisk?
Which image-files I should use (please provide URL)?
If somebody has a custom rom or lineageOS rom I would be even happier ...
Thanks a lot.
Thank you
Confirmed working with the Android 9 Pie 2019082617 ROM, latest Magisk 19.3 (19300), latest Riru core v19.5, latest Riru- EdXposed v0.4.5.1b (4463) (SandHook). EdXposed seems hit or miss after a reboot though, getting it to stick may take a few installations.
To get SP Flashtool to work, I had to hold the Volume Up key while inserting the USB cable and it would instantly connect, rather than following the OP's instructions of just inserting the cable and waiting for a black screen.
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
SepticFuddy said:
Confirmed working with the Android 9 Pie 2019082617 ROM, latest Magisk 19.3 (19300), latest Riru core v19.5, latest Riru- EdXposed v0.4.5.1b (4463) (SandHook). EdXposed seems hit or miss after a reboot though, getting it to stick may take a few installations.
To get SP Flashtool to work, I had to hold the Volume Up key while inserting the USB cable and it would instantly connect, rather than following the OP's instructions of just inserting the cable and waiting for a black screen.
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
Thanks for the mention of a quicker method. I've updated my post to include your info.
LineageOS for Uniherz Atom?
SepticFuddy said:
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
Me too!! LineageOS for the Unihertz Atom would be great!
The hadrware of the Uniherz Atom is just great, is is small and it is dual-sim. This is unique in the market.
I would be even willing to contribute with 100,- EUR if somebody delivers a working LineageOS ROM.
Any body interested? :highfive:
SepticFuddy said:
I'd love to see a custom ROM like LineageOS or something, but this is will have to do for now.
Click to expand...
Click to collapse
The main problem is that unihertz never released their source code (despite being obliged to do so according to the android licensing contract).
There are some bits in the official mediatek kernel source tree (https://android.googlesource.com/kernel/mediatek/) but I doubt that this would be enough to build something stable out of it.
@droidzer1 Hey there, what is the difference between your modded TWRP and this test release by the TWRP Builder Project asside from the TWRP version?
J-Kos said:
@droidzer1 Hey there, what is the difference between your modded TWRP and this test release by the TWRP Builder Project asside from the TWRP version?
Click to expand...
Click to collapse
I'm not sure what the difference is except I came out with mine in January and theirs came out in March. Theirs is about 4 Megabytes bigger - maybe a newer version (mine is 3.2.1-0). I contacted 'bigbiff' at TWRP about mine when I had it working but they were not interested unless I had a device tree which I didn't so they didn't want to post it on their site.
Great, thanks for your reply. I am satisfied with you version, so I will just keep using it.