I finally got my cubot pocket. I like my devices without GAPPS so I unlocked the bootloader and finally managed to flash a GSI.
This post contains: observations and general hints for this level of development, a guide to unlock the bootloader and what I did so far to flash a GSI.
Unlocking the bootloaderThis works similar to other Spreadtrum/Unisoc-based devices.
The crucial thing is to issue get_identifier_token from fastboot -> reboot to bootloader. If you issue it in adb reboot fastboot, it will say OKAY and may also print a four character string, but this is not the token you're looking for.
Also, when you flash the unlock_bootloader signature.bin, it will prompt you on the phone, but you have to react differently than described on the phone - see below.
enable Android developer mode (Settings -> About Phone -> tap "build number" >= 7x)
enable OEM unlocking (Settings -> System -> Developer Options -> OEM unlocking)
enable ADB (Settings -> System -> Developer Options -> USB debugging)
adb reboot fastboot
choose "reboot to bootloader"
Code:
$ fastboot oem get_identifier_token
proceed as described here
finally:
Code:
$ fastboot flashing unlock_bootloader signature.bin
this prompts you to press volume up to cancel, volume down to confirm.
But volume down and power don't have any effect, instead volume up starts wiping user.
wiping takes a bit longer than I'd expect, for me 433 s.
Congratulations, you now own your phone a bit more than before!
Flashing GSIs (probably applies to ROMs in general)It's a Treble-enabled arm64 A/B device. Flashing GSIs should be possible.
It looks to me like the A/B is crippled as all the _b partitions are 0-sized, probably to save space.
get and unpack necessary files as necessary: boot.img, vbmeta-sign.img, a ROM that you want, p.ex. AndyYan's Lineage GSI
fastboot resize-logical-partition product_a 38000
fastboot flash system [unpacked ROM file]
I also factory reset it afterwards
General/random notes
there are two different things reachable as "bootloader":
in fastboot switch to bootloader. The device displays the Cubot splash and from the display it looks stuck, but it exposes a fastboot interface -> useful
$ adb|fastboot reboot bootloader
shows the droid with open service door, saying "no command". It also exposes adb, but I don't see a way how to authorise it. Maybe via the debug UART? I didn't yet read the UART when I stumbled upon this. Currently it seems useless to me.
there are test points for the debug UART easily reachable once you disassemble it.
I didn't see anything with a 3.3V USB UART adapter, but a logic analyser with 1.4 V threshold works -> it probably uses 1.8 V logic level. UART-wise it's 115200 8n1.
I think I don't have anything to hook up to the TX currently.
UART log of boot
it's easy to softbrick this device, and I haven't found a nice way out of softbricked yet. Two not-so-nice-ways
- drain the battery, which obviously requires lots of patience
- disassemble the device and disconnect the battery
then flash the original ROM from the cubot site following the instructions there.
Once it bootloops, I didn't manage to power it off or get into fastboot / recovery using the device's keys.
the device reconfigures it's USB during boot and there's a limited time for the SPDFlashTool's mode that flashes complete firmwares. That means that it's not really feasible to run SPDFlashTool inside a VM.
the phone actually does something with the battery detached but USB power attached. For example, it's possible to flash it with the SPDFlashTool. However, it doesn't boot the linux kernel / Android, this seems to be inhibited.
This is in contrast to many other devices that are not laptops for which the PMIC does not provide power to the system when the battery is disconnected.
Old notes / how not to do it: Flashing GSIs (probably applies to ROMs in general)
it's a Treble-enabled arm64 A/B device. Flashing GSIs should be possible.
It looks to me like the A/B is crippled as all the _b partitions are 0-sized, probably to save space.
system_a is a bit below 1 GB ( 0x3CF5D000 B) which is likely smaller than any interesting GSI.
attempting to flash yields
Code:
Resizing 'system' FAILED (remote: 'Not enough space to resize partition')
There's the general hint to delete the product partition by running
fastboot delete-logical-partition product
then it's actually possible to flash a GSI, however:
the device bootloops -> log
From the log I realised I need to modify vbmeta, so:
it does android verified boot / AVB which from my understanding the easiest way forward is to disable it by:
creating a vbmeta.img with
Code:
$ avbtool make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
the padding necessary might be 16384 instead, according to the hovatek thread below.
it might be necessary to pad it additionally. There's a tutorial and a script here
when I flash both the hovatek-unpadded avbtool-4096-padded and hovatek-padded avbtool-16384-padded vbmeta, the device bootloops -> log
I guess the next step would be to unpack the vendor PAC ROM and check how the vbmeta image looks there.
Since with the original vbmeta it looks like it's restarting when it's already running linux / android, another way to go at this might be to change the kernel cmdline: instruct it to not do verity - Does anyone know how this is possible?
reserved for future use
dead ends (so far...)
didn't manage to find what image header magic number was wrong with the vbmeta.img (was already in the starting post)
the vbmeta actually doesn't chain to system, but there's a vbmeta_system partition (and vbmeta_vendor.img, vbmeta_system_ext.img, vbmeta_product.img) - I flashed the empty vbmeta disabling checking to vbmeta_system... and it bootloops again
this time the error is:
Code:
sprd_get_all_imgversion: ab_slot_flag is 0
read successed
sprd_get_all_imgversion: rpmb read blk 16382 successful
invalid sprd imgversion magic 0 exp a50000a5
uboot_vboot_verify_img() return error:param->a0=3
could be that it's just necessary to write the magic number to the correct offset, but I coulnd't figure out where this offset is - the images in the PAC don't have this number, so I guess it's embedded on-the-fly while flashing.
searching for imgversion+spreadtrum gets 0 relevant results - I guess it's very unusual that people hook up to the debug uart
I didn't manage to disassemble uboot.img - At least the disassemble doesn't look like a bootloader to me. Not an expert with disassemblies though!
modifying boot.img with magisk also results in invalid sprd imgversion, so no root or disabled verity through this route
I didn't manage to read back from flash through SPD ResearchDownload, I get the error "incompatible partition" for userdata - and I can't deselect it :/
(I thought it might be possible to get the sprd imgversion magic throught this route
Partial successI managed to boot a GSI by signed by google through Dynamic System Updates (DSU).
It kind of looks like it's running in emulation though: settings say "About emulated device" and it gets an own userdata.img
the DSU page also says it will only run GSIs signed by google or the vendor (not sure which key that would be, but I doubt there are any) - I haven't tried flashing anything this route
Open Ends:reverse engineering the imgversion thingIt should be possible to figure out how this imgversion business works, ultimatively from the u-boot.img / PAC content. Anyone has any idea how to proceed there? I tried:
binwalk: doesn't look useful to me, nothing got extracted -> here
arm-none-eabi-objdump -b binary -D u-boot-sign.bin -m armv8-a -Mforce-thumb
(also without -Mforce-thumb and with -m armv7)
I'm pretty sure it's actually U-boot: there is the U-boot version string matching the one printed to uart and also the printf-string for the imgversion
requested U-boot source code from CubotI requested source for all GPL'ed parts of the Pocket from Cubot, but especially U-Boot and the kernel. I'd be a pleasantly surprised if something comes out of this though
reading back the flashDoes anyone have an idea how to do that? without root no access to /dev/block/mmcblk* and I didn't get SPD ResearchDownload to read it.
It's nice that you could unlock the bootloader! I'll try to do it soon (maybe in some months, but ok lol)
Anyway, which GSI did you try? And about the vbmeta, I think it should be enough to flash the blank vbmeta.img from google. Maybe we could use the original vbmeta.img from stock ROM with the --disable-xxxxx flags.
This is the tutorial from phhusson's group (the man behind the treble project):
0. Get an up-to-date fastboot on your computer (fastboot —version should give version >= 29)
1. Get vbmeta.img from https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
2. Get A/B GSI (I'm guessing you need ARM64), don't forget to uncompress it
3. From running Android, do adb reboot bootloader
4. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. fastboot reboot fastboot
6. fastboot flash system system-xxxx.img
6bis. If fastboot tells you there isn't enough place, do fastboot delete-logical-partition product, fastboot delete-logical-partition product_a, fastboot delete-logical-partition product_b and run the fastboot flash command again
7. On your phone, the screen should have a button "go back to recovery", select it, then select "factory reset / wipe data"
8. Reboot and enjoy
Thanks for your work. I got my Cubot Pocket unlocked too. I have booted LineageOS 19 via DSU Sideloader. It runs like a charm but there is no way to flash the GSI permanent.
@changer86 with the DSU I have the navigation bar not showing, back-gesture not functioning and no automatic display brightness - do these work for you?
wori said:
@changer86 with the DSU I have the navigation bar not showing, back-gesture not functioning and no automatic display brightness - do these work for you?
Click to expand...
Click to collapse
I tried it. My Navigation Bar is showing and working normal.
Automatic Display Brightness is working too.
I dont use gestures, but if you tell me how to do it, i will check that too.
Image: lineage-19.1-20220719-UNOFFICIAL-arm64_bvS.img.xz
and DSU-Sideloader 1.03 from Github. Default Settings
thanks for trying!
You can change it in Settings->System->Navigation->System Navigation->check Gesture Navigation
So: interesting that you got a lineage build working, maybe that's the important difference! From google's doc I understand that there's some verifcation, but looks like it's not. Since I actually don't want the google build, I'll try with lineage next. Did you also try with the built-in DSU way, like described in googles doc?
wori said:
Did you also try with the built-in DSU way, like described in googles doc?
Click to expand...
Click to collapse
As I understood, the app is doing exactly the same like the Google Doc say. It seems like unlocking the Bootloader is enough to boot a custom-DSU.I have read something about signed Images that will boot without unlocking the Bootloader, but i didnt try it. I just want to get rid of all the Google-Stuff before using the Pocket Hope we can get it working.
btw: Gestures seem to work. swipe from right to middle closes Apps. from middle to up opens Menue
After a Weekend of fails i flashed Lineage 19 to my old KingKong mini and its working on the first try. Problem seems to be the Unisoc T310. The success-rate of flashing GSI to T310 seems to be really low. Does anybody know another Android 11 Device with Unisoc T310 that is working with GSI-Roms?
changer86 said:
Does anybody know another Android 11 Device with Unisoc T310 that is working with GSI-Roms?
Click to expand...
Click to collapse
GSI on Unisoc device
My tablet is unisoc t310 T803 with oem android 11 here is were im stuck I reflashed oem super.img and the system booted fine so i can start fresh i erased product and system, and flashed lineage 17.1
www.hovatek.com
seems this guy has succeeded and his device looks pretty similar to pocket in treble info
im unisoc tablet has oem stock A11 and no GSI A10 was to boot. my oem system is system as root AB arm64. so I have no choice but to use Arm64 AB GSI A11 because A10 will not boot
Click to expand...
Click to collapse
Hi, can you help me with this situation? I can't unlock bootloader on cubot pocket.
I tried to unlock on my ubuntu and windows devices.
FAILEN ( Flashing Lock Flag is locked. Please unlock it first)
I don't know that I will do for this problem
Spoiler: image
{
"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"
}
@raary did you enable OEM unlocking in the Android settings?
wori said:
@raary did you enable OEM unlocking in the Android settings?
Click to expand...
Click to collapse
Yes of course
raary said:
Yes of course
Click to expand...
Click to collapse
Did you use the modified fastboot ? Under Ubuntu start a Terminal from the extracted Folder and use ./fastboot instead of fastboot. Ensure that fastboot in the folder is executable. Check this guide: How to unlock Unisoc
Be warned: Unlocking the Bootloader ist working but flashing vbmeta like you tried leads to bootloop. I think the cubot pocket needs signed Images for flashing. there is a guide for custom signed Images but i did not get it to work for now.
changer86 said:
Did you use the modified fastboot ? Under Ubuntu start a Terminal from the extracted Folder and use ./fastboot instead of fastboot. Ensure that fastboot in the folder is executable. Check this guide: How to unlock Unisoc
Be warned: Unlocking the Bootloader ist working but flashing vbmeta like you tried leads to bootloop. I think the cubot pocket needs signed Images for flashing. there is a guide for custom signed Images but i did not get it to work for now.
Click to expand...
Click to collapse
Thank you, I will be try to unlock
@wori any updates on flashing gsi?
@badcodelab not from my side. I got frustrated and also had some other things to do. Hopefully find some time + energy to continue working on this.
I can't stay in stock OS, my GSI on cubot pocket have only 16 Gb via DSU sideload less for me, correct custom not exist for this, sad
@wori, @changer86 i didn't get clear from your posts if you tried to use signed vbmeta from the stock rom
also i haven't manage to make research tool to unpack boot.img nor super.img
by some reasons they stay listed as zero-sized .flag files in the target folder
Related
{
"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"
}
It has LINUX/UNIX and MAC support!
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.2 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
Download links: Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.
Known bugs/limitations: - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)
Changelog:
Check the changelog for each release here.
Tutorials/FAQ:
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload
Sources: The official and original repository can be found here.
Bug reports/Feature requests: If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.
Licensing: Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.
Tech and stuff: Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.
Donations: Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
Disclaimer:I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Getting an error
FAILED(remote: oem unlock is not allowed)
Skies/SANKE said:
Thanks!
I think there will be more people. Need to run a better window.
Windows7 64bit, part of the code.
Now, I have a simple editing of it.Make it look good.:laugh::laugh:
Download link:
https://mega.nz/#!nQBiDL7J!aDd9BhKtRw2tuYrpD7fImUXMn_Hl-qmUzwqKY13bYTc
Click to expand...
Click to collapse
Well, I've looked at your edit and I don't understand what looks better than mine... It might be subjective though...
Pikezer1337 said:
Getting an error
FAILED(remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Will investigate this problem and I hope I will get a solution fast
Edit: The information from this link might help with your problem.
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
paOol said:
I am running Arch Linux.
My shell is ZSH.
I downloaded and extracted, and ran zsh (filename).
I wanted to go with option 1 and got this
Code:
[= LG Nexus 5X - Multi Tool v0.1 - Linux =]
[1] Unlock bootloader. (via fastboot)
[2] Relock your bootloader. (via fastboot)
[3] Flash Recovery menu. (via fastboot)
[4] Backup and restore. (via adb)
[5] Recovery sideload. (via adb)
[r] Reboot menu.
[l] Logging menu.
[q] Quit.
Select your option:
1
menu:23: command not found: bootloader
127 [email protected] ~/Android/5XMultiTool.v0.1 % :(
any ideas?
Click to expand...
Click to collapse
The problem should be fixed in the V0.2, the Linux and MAC versions are not tested before posting, so bugs could still be around there...
added to index
Hi all, imusing linux and just tried to unlock my 5X. it worked but my question is, it is normal that it formated automatically?
after reboot, i have to start all over again with my account and setup.
Yes it's normal
Thanks mate, I'm new with nexus devices. One last thing, do I have to locked again or its OK leave it like that since on every reboot its showing me that I'm unlock. Sorry and thanks
Sent from my Nexus 5X using Tapatalk
You can leave it like that as long as you can deal with that message on every boot. If you lock it, you would have to unlock (and wipe) again if you ever want to flash anything again. Personally, unless you want to stick with the stock ROM OTAs, I'd leave it unlocked.
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Born<ICs said:
Would you confirm your Tools Re-Lock feature works with Custom Recovery (TWRP) without bricking device?
Click to expand...
Click to collapse
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Lexmazter said:
Usually, locking your device does not brick anything, if everything works fine before locking, everything will work fine after locking, you are only limited after locking.
Click to expand...
Click to collapse
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Born<ICs said:
.
Would you mind answering the question?
With custom recovery, TWRP, installed and unlocked what happens when you use your Tool to go back to Lock?
Have you tested?
Thanks
Click to expand...
Click to collapse
To be honest I never locked my bootloader, didn't found a reason to, so I didn't tested.
But technically speaking, the only thing that happens is that you cannot flash other custom recoveries (fastboot stuff basically) without unlocking again and wiping all the stuff on your device.
OK, thank you. ReLocking to flash factory image was what I was thinking. I read doing so can lead to bootloop. Just trying to make note of things to avoid doing.
Cheers
You can lock and unlock your bootloader as much as your heart desires without consequence
skulldreamz said:
You can lock and unlock your bootloader as much as your heart desires without consequence
Click to expand...
Click to collapse
Well, wiping your data partition can be a pretty big consequence...
-edit-
You used to be able to use BootUnlocker for Nexus Devices to lock and unlock the bootloader from within the OS, but it looks like that's a no-go on the 5X...
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
owenrg said:
I'm new to the nexus devices, but if I unlock the bootloader and root, will I loose both if I take an OTA update?
Click to expand...
Click to collapse
You will definitely lose root. I don't know about the bootloader since I've never taken an OTA, but I would guess that, unless there are bootloader changes in the update, your bootloader would stay unlocked. And to my knowledge the bootloaders are pretty much never updated for incremental OTAs.
Hey guys! Today is a big day for Alcatel 1 owners, since the root is possible. Follow my steps to root your device!
NOTE: This is using a treble gsi rom
[DISCLAIMER] . I am not responsible for dead phones, SD Cards, Alarm clocks failing, etc. You have been warned!
WARNING: Your data will be lost during the process!
=====================================================================================
[Unlocking The Bootloader]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Check OEM Unlocking
4 - Turn off your phone
5 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
6 - When the logo appears release the PWR button, while holding the VOL+ button
7 - In the recovery menu select reboot to bootloader
8 - In your pc with Minimal ADB and Fastboot installed type "fastboot oem unlock" (w/out the quotes)
9 - On the phone click the VOL+ button
10 - Reboot your phone and wait until the phone factory resets
=====================================================================================
[Installing LAge 16 (Android Pie)]
1 - Go to settings, and search factory
2 - Tap on Factory Reset
3 - When the factory reset is done, turn off the phone
4 - Hold down the PWR and VOL+ buttons until the alcatel logo appears
5 - When the logo appears release the PWR button, while holding the VOL+ button
6 - In the recovery menu select reboot to bootloader
7 - Download https://sourceforge.net/projects/an...910-UNOFFICIAL-treble_arm_avN.img.xz/download to your computer
8 - Open Minimal ADB and Fastboot and type "fastboot -u flash system filelocation.img" (w/out quotes and replace filelocation.img with your "lineage-16.0-20190910-UNOFFICIAL-treble_arm_avN.img" file location
=====================================================================================
[Rooting]
1 - Open Settings, go to About Device and tap Build Number 5 times
2 - Go back, tap on System, Advanced and Developer Options
3 - Tap in Root Access and select ADB and Apps
=====================================================================================
If you have reached this part, congrats! You have successfully rooted the Alcatel 1
{
"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"
}
Thanks dude, that worked perfectly.
Any idea how to get GAPPs working?
What if I only want to root the phone without installing Lineage OS? I just want to remove the bloat apps that came with the phone e.g. Youtube Go, Asistent Go, etc.
I bought a cheap Alcatel 5033D-2BALWE1 from amazon warehouse deals and did not expect to be able to install a custom rom, very nice. But I do have few questions:
Does the rom you linked have some adjustments for this hardware or should any other GSI image work just as well?
Does all the important hardware work (basically LTE, wifi, bluetooth, gps, microphone + speaker + headphone jack, camera)?
Any trusted source for a stock rom that can be flashed with fastboot? There's one on alcatelfirmware.com but not sure how legit it is...
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
ccxxx said:
Because amazon warehouse deals sold them so cheap I bought 2, so after trying it I can answer some of my questions. First, my fastboot here (linux) doesn't have a -u switch, but it worked fine without it.
I tried andy yan's build first. Rotation sensor, display brightness, wifi, gps, audio output + micrphone + audio jack switching, camera works. I have not tried bluetooth yet, but the bluetooth settings are there, so there shouldn't be much of an issue. I have not tried a sim card yet.
I wanted something more well known, so I flashed system-quack-arm-aonly-vanilla.img.xz from https://github.com/phhusson/treble_experimentations/releases/tag/v204 and so far everything still seems to work fine. treble version is 27, so I guess all treble roms with support for this version should work. You will need the "aonly" variant, and not the ab one, and it probably has to be the arm (= all arm32?) variant, not the arm32_binder64 one.
Click to expand...
Click to collapse
isnt the mediatek a 64bit cpu
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
ccxxx said:
Good question. /proc/cpuinfo says
Code:
Hardware: MT6739WA
which seems to be a Arm Cortex-A53, which seems to be a 64 bit cpu. I shall try the 64 bit variant of the rom.
Click to expand...
Click to collapse
right something going on after a few flashes, ive tried a few roms and my data in buggered cant get a mobile connection whatsoever ive tried getting into testing mode but no luck!
Any advice>?
---------- Post added at 05:48 PM ---------- Previous post was at 05:46 PM ----------
also getting this quite alot on lots of different roms -FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
With the arm64 build from https://github.com/phhusson/treble_experimentations/releases/tag/v204 I get this too:
Code:
$ fastboot flash system system-quack-arm64-aonly-vanilla.img
Sending sparse 'system' 1/13 (131068 KB) OKAY [ 38.967s]
Writing 'system' FAILED (remote: 'sparse image size span overflow.')
fastboot: error: Command failed
I guess the system partition is just too big:
1.7G system-quack-arm64-aonly-vanilla.img
1.1G system-quack-arm-aonly-vanilla.img
Are the arm64 binaries really 50% bigger, or is there more stuff in the 64 bit build, or is there empty space in the image?
Anyway, I put my sim card into slot 1 and immediately got a decent 4G connection, I didn't have to do any fiddling (O2/Eplus in germany). I only tried the AOSP image I linked, not the one from andy yan. It seems there are some issues with that image though, alarms and messaging notifications are two things that don't seem to work yet.
I keep getting this:
Code:
fastboot oem unlock
FAILED (remote: 'unknown cmd.')
fastboot: error: Command failed
FYI i have enabled oem unlock. Any clues?
hello
can i have the source for this because i want to optimize it.
my reason is the boot time is very long.
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
FNMONTEFALCONE said:
Hi Guys,
I've been trying since yesterday and get a boot loop on the lineage os boot.
I haven't got past the boot animation.
I've tried to flash to stock with spflash tool. NO success so far.
I need help, please.
I'm running Linux i3.
Thanks a lot!
Click to expand...
Click to collapse
Have you tried clearing the cache on the recovery menu and trying to boot again?
Sometimes the phone gets stuck on boot, any clues?
No success with rooting
Chinchila01 said:
Have you tried clearing the cache on the recovery menu and trying to boot again?
Click to expand...
Click to collapse
Dear Chinchila01,
Yes, and yes. I tried everything. The phone is now at my carriers tech support team. It's been more than a week and they can't fix it!!
I'm surprised, I must've really screwed it up somehow!
Well, I got a backup while they decide what to do and I've decided not to touch it.
I guess some phones are just not for fooling around with.
Hope this helps.
Best,
Facundo
I have much the same issues.
Lineage 16 works almost completely if it ever boots, sometimes you get lucky!
Lineage 17 usually boots but doesn't work really well, no gps, etc.
No GAPPS either way.
So close yet so far!
Solution
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Thanks, that worked. Even GAPPS!
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
I've tried a lot of different GSI images, All Pie ones take a long time to boot or don't boot and have to restart until it does.
I got this phone few days ago, Surprised me that it can run GSI's been having a good time testing different roms.
Thought there would be a TWRP but haven't found one. Makes it hard to have a rom with play store and root.
That's what i'm trying to find.
Chinchila01 said:
@caish5
@FNMONTEFALCONE
Hey guys, just to tell you:
Have been trying out this rom: https://github.com/phhusson/treble_experimentations/releases/tag/v32
And so far everything's good.
I installed system-arm-aonly-go-su.img.xz using the following method:
1. Extract it.
2. Reboot to fastboot.
3. fastboot flash system <file>
4. Reboot to recovery
5. Factory reset and cache clean.
6. Reboot.
Click to expand...
Click to collapse
Does that rom have SuperSU ? it say's SU at the end but installed it and no SU app ?
Hi,
So long i've dont active my account on XDA Developers because my studies. Finally i've found to update Oukitel K9 by using Treble Img
{
"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"
}
Video Review : https://youtu.be/EMbBpCc0R-Y
Please make sure you have download Generic GSI from Google and already unlocked bootloader.
Here the link ( Download Generic GSI )
Choose ARM64+GMS / ARM64, if you want to flash android Q treble rom, just download Android Q only.
Let's start it.
1. Flash to stock firmware using MTK Tools
2. Extract vbmeta.img from Generic GSI.
3. Connect to usb to device (enter fastboot mode) hold volume up and power button, choose fastboot mode.
4. Type this and make sure using generic vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5. Next erase file system
Code:
fastboot erase system
6. a) Flash file system
Code:
fastboot flash system ######.img
# = your file system name
or
6. b) Using TWRP > Flash> Click image> find img to flash> Select system>then swipe to flash
7.
Code:
fastboot -w
8.
Code:
fastboot reboot
PLEASE TAKE NOTE OUKITEL K9 IS A/B DEVICES
Test
Working GSI:
system-quack-arm64-ab-gapps.img.xz
Evolution X , Lineage 17.1 - All Working
Havoc 3.3 - RIL bugs, no simcard detect
All GSI Rom list you can find here : Phhusson GSI
Thanks @Levered
I've flashed stock Android 9 using SP Flash Tool, is that what you're talking about when you say 'MTK Tools'?
Step #3 - My PC doesn't recognize my device. (see #2 below)
A few other questions:
1) What build number are you coming from? I'm on OUKITEL_K9_V21_20190524
From what I've read there was some sort of 'lock' put in place at around that time so that only certain firmware could be flashed.
2) Fastboot? on a MTK device? I thought that was impossible too, even though it canbe put in to Fastboot mode by holding Vol+&PWR. I'm new to MTK devices so am very much a newb.
3) The link you provided correct? It takes me to the page for Android 11 GSI's, but the video shows Android 10
4) At bottom you have generic GSI linked—which one to flash, the one linked at top or bottom?
Also, perhaps worth mentioning, I've successfully temporary-rooted using this method from @diplomatic
https://forum.xda-developers.com/an...ing-temp-root-mediatek-armv8-t3922213/page101
Thanks again
TiTiB said:
Thanks @Levered
I've flashed stock Android 9 using SP Flash Tool, is that what you're talking about when you say 'MTK Tools'?
Step #3 - My PC doesn't recognize my device. (see #2 below)
A few other questions:
1) What build number are you coming from? I'm on OUKITEL_K9_V21_20190524
From what I've read there was some sort of 'lock' put in place at around that time so that only certain firmware could be flashed.
2) Fastboot? on a MTK device? I thought that was impossible too, even though it canbe put in to Fastboot mode by holding Vol+&PWR. I'm new to MTK devices so am very much a newb.
3) The link you provided correct? It takes me to the page for Android 11 GSI's, but the video shows Android 10
4) At bottom you have generic GSI linked—which one to flash, the one linked at top or bottom?
Also, perhaps worth mentioning, I've successfully temporary-rooted using this method from @diplomatic
https://forum.xda-developers.com/an...ing-temp-root-mediatek-armv8-t3922213/page101
Thanks again
Click to expand...
Click to collapse
Sorry for this.
Use fastboot mode on windows. You can find this on others thread using cmd.
I suggest you flash img using twrp for more faster.
3) Yes, i will check later.
4) All linked has work on our devices. I will update what rom has worked.
thanks
Levered said:
Sorry for this.
Use fastboot mode on windows. You can find this on others thread using cmd.
I suggest you flash img using twrp for more faster.
3) Yes, i will check later.
4) All linked has work on our devices. I will update what rom has worked.
thanks
Click to expand...
Click to collapse
Thanks for the reply, but the question remains,
Which firmware version did you start with?
I believe the bootloader is locked on my device, no fastboot.
TiTiB said:
Thanks for the reply, but the question remains,
Which firmware version did you start with?
I believe the bootloader is locked on my device, no fastboot.
Click to expand...
Click to collapse
Pixel experience, havoc 3.3, lineage 17.1 and EvolutionX
Please unlocked your bootloader, if that. Your device will get brick.
Levered said:
Pixel experience, havoc 3.3, lineage 17.1 and EvolutionX
Please unlocked your bootloader, if that. Your device will get brick.
Click to expand...
Click to collapse
nvm, you are obviously not going to share useful information
1) build# you were able to root
2) what you mean by 'MTK Tools'
3) and other important stuff
Additional information I have discovered
The vbmeta generic file is needed http://www.mediafire.com/file/lpdpocvn76n7cyo/vbmeta.img/file
The rom is https://www.mediafire.com/file/i9jo...20200413-UNOFFICIAL-treble_arm64_bvN.img/file
The Trebel test app stated the my Oukitel k9 was A only I found out it is A/B this rom works.
Also after flashing Lineage 17 there is not enough space for Gapps. Solution after flash reboot recovery again go to wipe select system select repair then adjust size of partition. Then reboot to recovery again then flash Gapps. I have successfully flashed Gapps stock and works great. Note I flashed Magisk last. So far this GSI works great, better than the phones original. Xposed works! Gravity box beta 6 works. Apps now auto start properly.
Thank you.
Thanks
hello, my name is bausette i'm italian, i'm sorry for my bad English i hope you cand understand me. First of all
thanks for your work, that's amazing my Oukitel k9 has new life :fingers-crossed::victory:, that's amazing Everything work better, than Stock Rom.
Can i Ask you some question please? i had Flash Vmeda generic files, Open Gapp, Orange State fix message, Lineage Rom project Treble, TWRP recovery, but i think i forgot something, because after install Magisk it say that the device is not Rooted, please can you tell my step by step Guide to Root the phone? thanks so much
Levered said:
PLEASE TAKE NOTE OUKITEL K9 IS A/B DEVICES
Click to expand...
Click to collapse
My Oukitel K9 is A-Only partition when I use Treble checker. Every guide seems to reference A/B for the Oukitel K9. Mine is not or at least it is being reported incorrectly.
How do I update to a custom rom when I have only A-Partition? The stock image is so buggy it's almost unusable.
Thanks!
Lannie
lschafroth2 said:
My Oukitel K9 is A-Only partition when I use Treble checker. Every guide seems to reference A/B for the Oukitel K9. Mine is not or at least it is being reported incorrectly.
How do I update to a custom rom when I have only A-Partition? The stock image is so buggy it's almost unusable.
Thanks!
Lannie
Click to expand...
Click to collapse
You can try A partition images.
Levered said:
You can try A partition images.
Click to expand...
Click to collapse
Is the process any different? I found the following list of files:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
It shows Treble A only image as an option. Mine supports Treble but not seamless updates due to the A-only partition.
Will the image listed above work with the normal guides? Do I need the vbmeta.img for the Oukitel K9?
I'm very new to this so I'm afraid to mess it up.
Lannie
lschafroth2 said:
Is the process any different? I found the following list of files:
https://sourceforge.net/projects/andyyan-gsi/files/lineage-17.x/
It shows Treble A only image as an option. Mine supports Treble but not seamless updates due to the A-only partition.
Will the image listed above work with the normal guides? Do I need the vbmeta.img for the Oukitel K9?
I'm very new to this so I'm afraid to mess it up.
Lannie
Click to expand...
Click to collapse
you can try both, but i think our k9 is A/B partition.
yes you need vbmeta.img
follow this guide:
https://forum.xda-developers.com/mi-9-se/how-to/guide-how-to-flash-twrp-gsi-roms-mi-9-se-t3939254
Levered said:
you can try both, but i think our k9 is A/B partition.
yes you need vbmeta.img
follow this guide:
https://forum.xda-developers.com/mi-9-se/how-to/guide-how-to-flash-twrp-gsi-roms-mi-9-se-t3939254
Click to expand...
Click to collapse
I have tried 4 different Treble checking apps and they all say Treble supported but seamless updates not supported because A-only partition exists.
This is a Oukitel K9 OUKITEL_K9_V21_20190524
Wonder why everyone else seems to have A/B and I only have A.
Lannie
---------- Post added at 07:35 PM ---------- Previous post was at 07:33 PM ----------
nation888888 said:
The vbmeta generic file is needed http://www.mediafire.com/file/lpdpocvn76n7cyo/vbmeta.img/file
The rom is https://www.mediafire.com/file/i9jo...20200413-UNOFFICIAL-treble_arm64_bvN.img/file
The Trebel test app stated the my Oukitel k9 was A only I found out it is A/B this rom works.
Also after flashing Lineage 17 there is not enough space for Gapps. Solution after flash reboot recovery again go to wipe select system select repair then adjust size of partition. Then reboot to recovery again then flash Gapps. I have successfully flashed Gapps stock and works great. Note I flashed Magisk last. So far this GSI works great, better than the phones original. Xposed works! Gravity box beta 6 works. Apps now auto start properly.
Thank you.
Click to expand...
Click to collapse
How do you verify you are A/B? Mine says A only on 4 different treble apps. Is there a way to verify for sure? I have a Oukitel K9.
Lannie
lschafroth2 said:
I have tried 4 different Treble checking apps and they all say Treble supported but seamless updates not supported because A-only partition exists.
This is a Oukitel K9 OUKITEL_K9_V21_20190524
Wonder why everyone else seems to have A/B and I only have A.
Lannie
Click to expand...
Click to collapse
You can try it first both partition. If not boot, try another partition. :fingers-crossed:
Everything seems to work except hotspot
The no verity, Lineage rom a/b, vbmeta, resizing system partition size, installing stock gapps all works making this one of the nicest roms I have worked with. The only issue I find so far I cannot get the mobile Hotspot to stay on. Mobile Hotspot works in safe mode. I did a fresh install and does the same. Modded buildprop, no results. Installed module tether enabler, no results.
Mobile Hotspot switches off right away. Any ideas?
---------- Post added at 06:01 AM ---------- Previous post was at 05:57 AM ----------
It is this one a/b I have not seen any other variants. Both Global and Chinese have same partition setup. Yes I have tried a only and doesn't boot.
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
lschafroth2 said:
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
Click to expand...
Click to collapse
If recovering to stock is easy, I guess I can dive in and try the A/B image and see if it works.
Lannie
use the lineage ab... it is ab. Make sure to do the no verity first with vbmeta line. Then flash lineage ab the file is not clear it states b. I tried them all see my post for direct download.
Same result
lschafroth2 said:
How do I check? I've tried the ADB SHELL commands and it returns an empty line. The article said it would show TRUE if it did. All it returns is an empty line. I have yet to find any app that shows my Oukitel K9 is A/B. All of them say it is not.
Click to expand...
Click to collapse
I have same firmware, K9 OUKITEL_K9_V21_20190524, and same results for Treble check (see screenshots for info).
Also, device not recognized using fastboot.
Code:
adb devices
OUKITELK90007961
Code:
adb reboot bootloader
success; 'FASTBOOT mode. . .' on phone
Code:
fastboot devices
blank line
From what I understand, this is because our devices' bootloaders are locked; and there is nothing we can do to change that, period. So, no flashing anything but stock. I hope I'm wrong, and someone more knowledgeable corrects me, but I'm pretty sure this is correct.
For now I'm just stuck, and using temporary root as mentioned in previous post.
{
"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"
}
TWRP FOR Ulefone Armor X5DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the phone and boot to fastboot mode (power and volume +)
- Open a comand prompt and type:
Code:
fastboot flashing unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot reboot
- When the phone is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the phone, type the following command:
Code:
fastboot flash recovery recovery.img
- Now Boot into TWRP, and format data, and reboot to system
If you wanna root it:
- When you are at TWRP and you have formatted data, flash Magisk by sideload
- And reboot to system
Sources:
Device Tree
Download:
TWRP v1
TWRP v2
TWRP v3
Thanks to [Alphabetical Order]:
* Hadenix
* Maanush
* R0rt1z2
* SebaUbuntu
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Pachacouti said:
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Click to expand...
Click to collapse
Hi
How are you?
My variant is MT6763 one, if you want open pm and we will work for make TWRP for MT6765 variant.
Thanks!
A Only
Thanks dude, but my phone is an 'A' only partition, and as far as I'm aware, only johnwu's phone has actually been done, his being 'A' Only... He made a magisk for his 'A' only phone, but it dont work on mine. To see my firmware, just look at the ulefone stock firmware for android 10_Q, you'll find all you need there... ? It's an armour x5, aarch64, meaning 64bit only I think...
Tried everything I know of, and I do know a bit so not shy in testing any files, I am a competant programmer electronics style, flashing chips etc, so no prob re-flashing errors etc
Edit google johnwu 'A' only and you'll see why its not been done yet... whoever does it will create root for what is coming for all fones...!
X5 pro variant
FYI, this method isn't working on Ulefone Armor x5 Pro variant. (MT6765 - Android 10) Dont know why, but it causes bootlop. Reflashing stock boot img restores the phone functionality (without TWRP obviously). As i'm a new user, i can't post the link to the stock Boot and Recovery images, but if anyone needs them for porting, feel free to PM me.
It wont work because android 9 is the old version of 64bit capable of running 32bit apps, android 10 is pure x64bit. The bootloader is NOT the bootloader anymore, but a preloader, loading BEFORE the bootloader. so flashing bootloader over preloader causes bootloop, makes sense dunnit?
All fones will soon adopt this, and it has already started, since johnwu was bought by apple, and will be made too busy to produce anything anymore, by design of course, and since this new version of a only partitioning has been succesfull in thwarting him, no more root for you. Now you get another file system running on top of your unrootable fone to make you think you have root, pretty much sums it up, this overlayfs...
Shows how good the devs really are nowadays, when nomoretech (hovatek) found out his work dont work on android 10, he ignored my thread, too busy with old android 9 for old fones. upgrade, update, move on, say 'tata root'....
thanks good job on android 9
jmpf_bmx said:
TWRP FOR Ulefone Armor X5DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
INSTALLATION
- Go to developer settings and turn on OEM unlock
- Power off the phone and boot to fastboot mode (power and volume +)
- Open a comand prompt and type:
Code:
fastboot flashing unlock
All the data will be loss
- Confirm the oem unlock by pressing the volume + button
- And now type:
Code:
fastboot reboot
- When the phone is turned on, and you complete the setup wizard, type:
Code:
adb reboot bootloader
- When fastboot mode appears in a corner of the phone, type the following command:
Code:
fastboot flash recovery recovery.img
- Now Boot into TWRP, and format data, and reboot to system
If you wanna root it:
- When you are at TWRP and you have formatted data, flash Magisk by sideload
- And reboot to system
Sources:
Device Tree
Download:
https://github.com/jmpfbmx/android_...eleases/download/twrp_bretzel_v1/recovery.img
Thanks to [Alphabetical Order]:
* Hadenix
* Maanush
* R0rt1z2
* SebaUbuntu
Click to expand...
Click to collapse
Hi,
We try to install it on a Armor X5 with android 9, build Armor_X5_MH1_EEA_V01 and all we have is a green line in the top of the screen then the phone reboot...
Is it many hardwares for the same phone ?
Thank you
wargreen said:
Hi,
We try to install it on a Armor X5 with android 9, build Armor_X5_MH1_EEA_V01 and all we have is a green line in the top of the screen then the phone reboot...
Is it many hardwares for the same phone ?
Thank you
Click to expand...
Click to collapse
Hi,
Can you share a pic of the screen?
Can you try to use adb? (Try adb shell, if works make this, adb shell cat /tmp/recovery.log, and send me the file by here)
Thanks
Regards
Jose
Tomorrow you will have a huge update of TWRP and some news about A11 hehe
"- Now Boot into TWRP, and format data, and reboot to system"
Could you explain exactly How to do this, please
bootloader activated, do I hard reboot pressing power and vol+, and when do I stop pressing ?
thanks
ulysse
"- Now Boot into TWRP, and format data, and reboot to system"
Could you please explain exactly how to do this ?
Bootloader activated, Do I press power and vol+ and keep then pressed ? until what ?
thanks a lot
ulysse
ulysse_21 said:
"- Now Boot into TWRP, and format data, and reboot to system"
Could you explain exactly How to do this, please
bootloader activated, do I hard reboot pressing power and vol+, and when do I stop pressing ?
thanks
ulysse
Click to expand...
Click to collapse
Hi
How are you?
Have you got Bootloader unlocked? (Idk wdym with bootloader activated)
For do that you just need to flash TWRP, reboot phone pressing vol+ and power as you say and when TWRP boots, just go to Wipe -> Format Data (Type yes) and then when the format data has finished, clic on reboot to system
TWRP Updated!
Now MTP and ADB are working better!!
thanks, i try
ulysse
jmpf_bmx said:
- When the phone is turned on, and you complete the setup wizard, type:
Click to expand...
Click to collapse
I start in Engish , skip connect to mobile network (no sim), skip WI-Fi, adjust good date and time, without "use location" and without "send usage and diagnostic data"; acept; "not now" for "protect your phone"
Then I activate the developper mode and in "system/ options for developers" I turn on USB debogage.
Did i miss sommething at this stage ?
jmpf_bmx said:
Can you try to use adb? (Try adb shell, if works make this, adb shell cat /tmp/recovery.log, and send me the file by here)
Click to expand...
Click to collapse
Hello thanks for your help.
Phone powered on, I can go on "Armor_X5:/ $ " if I type "adb shell".
but I don't understand "adb shell cat /tmp/recovery.log,"
I have "cat: tmp/recovery.log: No such file or directory"
appologize for my low level in English and in computering, I write code more on ImageJ and Rstudio.
ulysse_21 said:
I start in Engish , skip connect to mobile network (no sim), skip WI-Fi, adjust good date and time, without "use location" and without "send usage and diagnostic data"; acept; "not now" for "protect your phone"
Then I activate the developper mode and in "system/ options for developers" I turn on USB debogage.
Did i miss sommething at this stage ?
Click to expand...
Click to collapse
Did you opened bootloader?
ulysse_21 said:
Hello thanks for your help.
Phone powered on, I can go on "Armor_X5:/ $ " if I type "adb shell".
but I don't understand "adb shell cat /tmp/recovery.log,"
I have "cat: tmp/recovery.log: No such file or directory"
appologize for my low level in English and in computering, I write code more on ImageJ and Rstudio.
Click to expand...
Click to collapse
I guess that you aren't at recovery, or you didn't disable and enable MTP
Pachacouti said:
Just a note: This is NOT for the newer mt6765 Android 10 Q phone, If your fone is android 10 Q it will NOT work.
Click to expand...
Click to collapse
It works in mt6762 Android 10 version? model Armor_X5_Q_EEA
Android 11 (Go Edition)
Modified Stock ROM
{
"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"
}
Assurance Wireless
KonnectONE Moxee m2160
4G-LTE Smartphone
Model No. MH-T6000
OVERVIEW:
This is a heavily modified build of the stock Android 11 (Go Edition) ROM which comes preinstalled on the KonnectONE Moxee m2160 smartphone. Please note that, while flashing this ROM will not network unlock your device, the ROM does include added support for most GSM based providers on devices which have previously been network unlocked.
In a nutshell, this modified build focuses on the removal of bloatware and a slimmed-down, more responsive stock OS experience. In addition, once installed, the ROM supports full R/W mounting of all logical partitions encompassed within /super. (The unmodified stock ROM, notwithstanding Magisk systemless root, restricts proper R)W mounting of these partitions due to the stringent codebase changes which implemented the dynamic partition scheme back with the release of Android 10.) This ROM also disables force encryption to /userdata (DFE), disables AVB/dm-verity, and includes several mods for improved performance and responsiveness. While certainly nothing special in terms of custom development for the Moxee m2160, this ROM should provide users with a sufficient daily driver ROM with an optimized stock feel.
FEATURES & BUILD INFO:
• Based on firmware build MH-T6000V1.0.0B010
• Kernel version: 4.19.157-perf
• Security patch level: March 5, 2023
• GMS version: 11_202111.go
• VNDK version: 30
• Quick boot sequence
• Systemless root via Magisk v26.1
• Enabled Power Stamina mode for better battery life
• /system mounts R/W
• /system_ext mounts R/W
• /product mounts R/W
• /vendor mounts R/W
• Force encryption of /userdata disabled (DFE)
• OTA notifications & persists disables
• AVB/dm-verity disabled
• Stock launcher locked in memory
• Zipaligned /system/app & /system/priv-app
•Zipaligned /system_ext/app & /system_ext/priv-app
• Zipaligned /product/app & /product/priv-app
• Custom TCP congestion algorithm presets
• Heavily debloated w/minimal Google framework
• Kernel level performance optimizations
• Google Pixel 2 dark bootanimation
• Optimized RAM management
• Schedutil tuned CPU governor parameters
• Enabled fast charging (1100 mAh stable)
• GSM support for network unlocked devices
PREREQUISITES:
An unlocked bootloader
A PC or laptop running on Windows 7, 8.1, 10 or 11
Smartphone must be running Firmware Build No. MH-T6000V1.0.0B010
The SDK Platform Tools on your Windows computer (link provided below)
Installation of the proper ADB & Fastboot device drivers on your Windows computer
The factory supplied, or a quality sufficient, USB-A to USB-C syncing/charging cable
A reliable internet connection for downloading the required files
NOTE: We will not be using a custom recovery for installation of this ROM, but rather the dynamic user space implementation of fastboot mode, formally called FastbootD. This fastboot protocol was first introduced with the release of Android 10, and is primarily utilized for the management of dynamic partitions (devices with a /super partition).
DISCLAIMER:
This guide involves the invasive procedure of flashing the partitions of your device, thus modifying the configuration of the device from its factory stock state. This is always inherently risky to the integrity and operability of your mobile device. By proceeding further, you are assuming sole responsibility for the functionality and physical wellbeing of your mobile phone, thus absolving me of any liability in the event things go badly. This ROM has, however, been tested thoroughly on my own device with no negative issues. Moreover, in the unfortunate event your device becomes bricked or otherwise inoperable by way of a botched adherence to this guide, my firmware restoration guide for this device can restore both soft and hard bricked phones. Moxee m2160 Unbricking Guide
INSTRUCTIONS:
WARNING:
These instructions include steps for initiating a factory data reset, a procedure which will effectively erase all saved user data, app data, app preferences, photos, videos, music, documents and other media files from your smartphone. Make a backup at this point of all data, files and media that you wish to preserve.
Download the SDK Platform Tools from the link below and extract the contents of the archive to an empty folder on the desktop of your Windows computer
Download the ROM from the link below and extract the contents of the archive to your platform tools directory created in the previous step
Because this ROM has been modified to disable DFE force encryption, it is first necessary to format the /userdata partition. With your phone in a powered off state, press the Volume Up & Power keys simultaneously until the Moxee logo appears on your display, at which time you should release the Power key, but continue holding Volume Up until an Android logo and a corresponding No Command notification appears on your phone display. Now quickly press and hold Power, tap Volume Down and then Volume Up to enter stock recovery mode.
Use the Volume Down key to navigate to the Wipe data/factory reset option, then press Power to select. Confirm this selection on the next screen to initiate the factory data reset.
Once the factory reset is complete, navigate to the option to Enter Fastboot, then press Power to select. Your phone should now boot to FastbootD mode.
In the platform tools folder created in the first step, click on cmd-here.exe, then right click and opt to run it as an administrator. A command window will be launched. Now connect your Moxee m2160 to your Windows computer using a sufficient USB-A to USB-C data syncing/charging cable.
In order to verify proper fastboot communication between your phone and PC, execute the following command:
Code:
fastboot devices
If properly connected, the command window will yield an alphanumeric value consistent with your mobile phone serial number.
Execute the following commands once a proper fastboot connection has been verified. Note, the user may copy these commands and paste the full text to the fastboot command window for systematic execution:
Code:
fastboot flash boot boot.img
fastboot flash vbmeta vbmeta.patched.img
fastboot flash vbmeta_system vbmeta_system.patched.img
fastboot flash vbmetabak vbmetabak.patched.img
fastboot flash vbmeta_systembak vbmeta_systembak.patched.img
fastboot erase super
fastboot flash super super_rw.img
fastboot erase metadata
fastboot erase cache
fastboot erase DDR
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
** Please note that the super_rw.img file is large in size. Fastboot may initially give a header magic notification error. However, the super_rw.img will then be allocated into a number of smaller sparsechunk files, which will subsequently be flashed to your device one at a time, until complete. Just remain patient during this process. This can take five minutes or more, but the process will not require any user action.
Upon first reboot following installation, and after completing initial device setup, open your app drawer and search for the Magisk app or its stub placeholder. Open Magisk, grant any requested permissions, and follow any prompts by Magisk to update the version or complete setting up the root environment. If you do not see the Magisk app or stub, download the Magisk v26.1 APK from the link provided below and install the app on your phone. Be sure to then open Magisk and follow all prompts.
DOWNLOADS:
• SDK Platform Tools r34.0.3
• Modified Stock ROM Package
• Official Magisk Releases / GitHub Repo
BUGS:
Please report any bugs or instabilities you may encounter using this modified stock ROM. Those who know how to submit an official bug report are urged to do so. Otherwise, please give a concise and detailed description of the issue, including photos or screenshots if possible. I will work diligently to patch any reported bugs or instabilities.Moxee m2160 Firmware Restoration & Unbricking Guide
Instructions were great and I had no problems following them. I did have an error when I first entered the command "fastboot erase DDR" but only because I did not capitalize DDR. My only issue is I cannot get past the phone set up when first booting because it says there is an update and can not pass verification and there is no option to skip. And in my case I don't have a computer still so cannot use qfil to return to full stock to update. Any suggestions?
scottfan81 said:
Instructions were great and I had no problems following them. I did have an error when I first entered the command "fastboot erase DDR" but only because I did not capitalize DDR. My only issue is I cannot get past the phone set up when first booting because it says there is an update and can not pass verification and there is no option to skip. And in my case I don't have a computer still so cannot use qfil to return to full stock to update. Any suggestions?
Click to expand...
Click to collapse
Okay. At the time I completed modifications on the ROM, the latest OTA had not yet rolled out. What I'll do is add another mod to kill the OTA service entirely. That should prevent any issues like you're facing. I'll expedite this task and will let you know just as soon as I've made the fix and changed out the ROM file with the new one. Thanks for your feedback. By the way you won't have to repeat the process, but will only need to flash the super_rw.img file.
Update: I have disabled system updates and OTA notifications. Proved trickier than I thought, since system updates on Android Go Edition are governed by Google Play Services. I had to decompile the Google Services apk, manually disable the individual system update service and listeners, then recompile and reinstall the Google Services core app. I am presently uploading the new super_rw.img.
One thing that should work for you in the meantime, while I get these new files uploaded, is to perform another factory data reset. During initial boot and setup, opt to complete setup offline, without connecting to WiFi or a mobile data network. Accordingly, your device will not be able to check for pending system updates and you should, therefore, be able to complete setup.
Viva La Android said:
Okay. At the time I completed modifications on the ROM, the latest OTA had not yet rolled out. What I'll do is add another mod to kill the OTA service entirely. That should prevent any issues like you're facing. I'll expedite this task and will let you know just as soon as I've made the fix and changed out the ROM file with the new one. Thanks for your feedback. By the way you won't have to repeat the process, but will only need to flash the super_rw.img file.
Click to expand...
Click to collapse
That would be awesome. I really appreciate your help.
scottfan81 said:
That would be awesome. I really appreciate your help.
Click to expand...
Click to collapse
The files should be finished uploading within the next 15 minutes or so. I will then update the download link and will inform you here when that's done.
@scottfan81, the latest files are uploaded and the download link has been updated accordingly.
Viva La Android said:
@scottfan81, the latest files are uploaded and the download link has been updated accordingly.
Click to expand...
Click to collapse
That's great! I just got done with my dinner and going to download it now. I will let you know how it goes. And I did see that I only need to flash the super_rw.img file. So I should know shortly.
scottfan81 said:
That's great! I just got done with my dinner and going to download it now. I will let you know how it goes. And I did see that I only need to flash the super_rw.img file. So I should know shortly.
Click to expand...
Click to collapse
Do a factory reset beforehand. Then flash the super_rw.img
@Viva La Android
I haven't had any luck since my last post. Before I posted about the verification issue I had when setting up my phone I made sure I double checked that I did not have the option to skip the update as you suggested. That was not an option for some reason and that is when I came here. I have followed your steps with the new super.rw.img you updated but I am worse off than I was before. Now I cannot do anything as the phone is not recognizing any network or available WiFi connections. I have tried a factory reset and started over from your first step with no success. I should also include that since flashing the updated super.rw.img file, when the phone first boots the screen quickly flashes black and blue for about 10 seconds before finally starting the set up process then I get 2 error messages. The first being "system UI isn't responding" and second "Android setup keeps stopping" After all of that the setup starts and that's as far as I can go because I can't connect to anything. Trying to give you as many details I can think of. Before the screen flashing when powering on the phone, the boot animation just function properly. Only between the boot animation and setup process do I experience the rapid black and blue screen for roughly 10-15 seconds. I am including some screenshots of the error messages and setup screens showing no connections available. I almost forgot. I also tried manually adding my network and scan qr code with no success.
Unfortunately I have physically damaged my device beyond any hope of restoring it, so I won't be able to support this device any longer -- until & unless I can get a replacement display. But before my device went kaplut, I did test this ROM and had no issues. I wish I could be more help.
I would recommend performing all steps over again from the top -- formatting /userdata before doing anything. Have you tried by completing all the steps over?