Related
this was a work-in-progress development project for porting CyanogenMod 9 (ICS/4.0.4) and ClockworkMod Recovery 5 to Allwinner A10 devices.
but my CM9 is obsolete now. if you want to get CM9, please refer other active projects.
currently here is only for my miscellaneous work for Allwinner A10 devices. if you have a question about development work for A10, you may post it on here. but I can't guarantee any answer.
* links to other active CM9/CM10 projects
http://forum.xda-developers.com/showthread.php?t=1821398 CM10 for many A10 tablets by Christian Troy
http://forum.xda-developers.com/showthread.php?t=1760929 CM9 for many A10 tablets by Christian Troy
http://www.slatedroid.com/topic/33820-ics-404-ivi-cm9-firmware-for-novo7-advanced-btgpsusb-audio/ for NOVO7 Advanced(1) by tsynik
* links to other active AOKP projects
http://forum.xda-developers.com/showthread.php?t=1760931 for many A10 tablets by Christian Troy
* How to install ClockworkMod Recovery 5
1. (if you don't have official ROM and flash tool,) make backup of recovery partition
2. download recovery.zip and unzip it
3. put install-recovery.sh and recovery.img(recovery.cpio for GB ROM) on /sdcard/ *1 *2
4. run install-recovery.sh from root shell or any apps which can run a script (terminal, gscript, etc)
e.g.
Code:
> adb shell
$ su
# sh /sdcard/install-recovery.sh
* How to boot recovery
1. put reboot-recovery.sh on /sdcard/ *1 *2
2. run reboot-recovery.sh from root shell or any apps which can run a script (terminal, gscript, etc)
e.g.
Code:
> adb shell
$ su
# sh /sdcard/reboot-recovery.sh
*1 if you are using CM9, install-recovery.sh and reboot-recovery.sh are already installed on /system/bin/. if you are not using CM9, you can put these scripts on your ROM.
*2 /sdcard/ is referred as "SD card" on Android, but it may not be physical/external "SD Card". please make sure files are placed on /sdcard/.
* How to boot recovery (alternative)
for ainol NOVO7 AdvancedII/Aurora/Elf
BACK + POWER
for other tablets, please find the way to boot recovery.
* How to control ClockworkMod Recovery 5
for ainol NOVO7 Advanced
VOL-: down, VOL+: up, POWER/MENU: select, BACK: back
for ainol NOVO7 AdvancedII/Aurora/Elf
VOL-/MENU: down, VOL+/HOME: up, POWER: select, BACK: back
* How to install CyanogenMod 9
1. download update.zip and put it on internal NAND flash or SD card (don't unzip it)
2. install ClockworkMod Recovery 5
3. reboot recovery
4. install update.zip
5. wipe data/factory reset *3
6. reboot
*3 only if you are upgrading from non-CM9 ROM (CM9 1st install)
reserved
reserved
Hi,
I was not shure if I should by the NOVO7 Advanced, but now as I see that there is (or will be) CM avaidable for it , I will buy it.
Thanks for porting
T
saulmrt said:
I was not shure if I should by the NOVO7 Advanced, but now as I see that there is (or will be) CM avaidable for it , I will buy it.
Thanks for porting
Click to expand...
Click to collapse
thank you for your message.
but I don't recommend to buy it because of my CM, unless you like/want to do porting work. my CM is not perfect at all.
I ordered it because I thin it is a good piece of hardware, you don't have to be afraid that it was only because of this port.
Well as soon as I have this tablet I will try to help with porting as good as I can.
Great work so far OP!
I have the Ainol Advanced waiting for me at the post office. There's already a healthy community over on slatedroid but it's always good to see CM getting ported!
thank you for your comments.
I wish I'll re-upload my files in this weekend...(it's not technical reason at all)
FILES! FILES!! My Kingdom for FILES!!!
i have been longing for it and i suggest to launch a new board for it. it's been a popular device in PRC, taiwan & hong kong already! please note that the 2.0.3 & 2.0.4 firmwares are quite buggy, and i would advise all to flash 1.8 modified version which is stable and can score 18XX at quadrant.
I've been trying to do this for my A10-based tablet too. Can you up the download links again? Maybe I can improve some things.
Edit: I'll upload a dump of the stock ROM soon. I also found a tool to (partially) extract the LiveSuite *.img files.
Edit 2: WiFi chipset of the tablet is a Realtek 8192CU, Freescale MMA7660 accelerometer & Goodix touchscreen.
FezzFest said:
I've been trying to do this for my A10-based tablet too. Can you up the download links again? Maybe I can improve some things.
Edit: I'll upload a dump of the stock ROM soon. I also found a tool to (partially) extract the LiveSuite *.img files.
Edit 2: WiFi chipset of the tablet is a Realtek 8192CU, Freescale MMA7660 accelerometer & Goodix touchscreen.
Click to expand...
Click to collapse
sorry, I need some time to prepare my site. it seems I don't have enough time on this weekend but I hope I'll get some time on next week.
I guess you are talking about this tool: http://www.mp4nation.net/forum/viewtopic.php?f=24&t=20476
I'll try it when I get enough time
and thank you for your information. if you want to add your tablet to my support list, I need more detail info (please see post#4). if you can do it yourself, please just wait for some day... I'll uploaded my git repo too.
(nothing is secret, just I need my free time!)
I found it on a different website, but I think it's the same tool.
This is a dump I made of the original partitions with dd:
boot.img: http://dl.dropbox.com/u/28680222/XDA/tablet/boot.img
misc.img: http://dl.dropbox.com/u/28680222/XDA/tablet/misc.img
rootfs.img: http://dl.dropbox.com/u/28680222/XDA/tablet/rootfs.img
recovery.img: http://dl.dropbox.com/u/28680222/XDA/tablet/recovery.img
system.img: http://dl.dropbox.com/u/28680222/XDA/tablet/system.img
I haven't included cache, data and internal sdcard because I don't think they are of any use for ROM development.
Edit: attached required output from commands in post #4. Find /sys doesn't work because adb can't find find
Hi fun thanks for the pm found my way here at last
i have not managed to get into stock recovery on the Excel so far so i have not made any kind of file dump or backup i will see how it goes and keep my eye on this thread i have root and terminal emulator i have installed superuser as an app from market
can i type a command to get into stock recovery or would you think there is no stock recovery
cheers
Recovery is also a mistery to me. I tried 'adb reboot recovery' but I guess that was too simple. There is a recovery partition (I created an image with dd above) but haven't found a way to boot into it. I'd love to know how the topic starter got clockworkmod working
Mitred said:
i have not managed to get into stock recovery on the Excel so far so i have not made any kind of file dump or backup i will see how it goes and keep my eye on this thread i have root and terminal emulator i have installed superuser as an app from market
can i type a command to get into stock recovery or would you think there is no stock recovery
Click to expand...
Click to collapse
hi.
stock recovery should work because it's necessary to run "factory reset" from setting menu on stock rom. (it's done automatically so we can't use it to enter recovery mode. I just explained about functionality)
and recovery is not necessary for now. what I need is not complete dump image. I just want to know hardware related things so tar archive is enough.
permanent root is not necessary too. sometimes rooting app makes brick, so I don't recommend it. I don't recommend to modify stock rom unless you have official rom and flash tool.
if adb shell is root shell, then rooting is not necessary at all. if adb shell is not running, or non-root user shell, temporary root is necessary to get root shell.
then, you already got root shell, right?
then, please check following commands are available in your rom, "tar" and/or "busybox".
FezzFest said:
Recovery is also a mistery to me. I tried 'adb reboot recovery' but I guess that was too simple. There is a recovery partition (I created an image with dd above) but haven't found a way to boot into it. I'd love to know how the topic starter got clockworkmod working
Click to expand...
Click to collapse
"adb recovery" doesn't work. I'll post how to enter recovery. please wait for a moment.
anyway, please tell me name of your tablet, or link to web, or photo.
if busybox is in your rom, "busybox find /sys" will work.
It's a Bmorn V11. The 'busybox find /sys' command indeed works, I have attached the output files to the zip file in this post.
FezzFest said:
It's a Bmorn V11. The 'busybox find /sys' command indeed works, I have attached the output files to the zip file in this post.
Click to expand...
Click to collapse
i'm guessing you are referring to the Bmorn V11 rebranded for Promedia ?
If so, keep in mind that there are 2 versions of this tablet, one with 3600 battery and one with 3200 battery, the 3200 version has the goodix_touch drivers.
hey guys... all the root packages I have seen so far have a survey to download ... I cant do surveys because .. well its a long story .
in a short version .. I am looking for a direct root package download without being troubled in doing a survey .
I would be grateful if some one can help me out
Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita
timmaaa said:
Please don't duplicate posts, it's against the rules. I was already helping you in the other thread you posted in but I'll continue here. The root package you were looking at is most likely not compatible with your current firmware version. What are your bootloader details? I need to see the first five lines.
Sent from my Evita
Click to expand...
Click to collapse
*** UNLOCKED ***
evita pvt ship s off RL
CID-HTC__622
hboot-2.15.0000
radio-1.30a.32.45.18
opendsp-v33.1.0.45.1128
What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita
timmaaa said:
What's your ultimate goal? Do you want to root your current stock ROM or install a custom ROM? Either way you need to install TWRP recovery first. I'm assuming you already have adb/fastboot installed on your PC.
Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you have TWRP recovery on your phone.
If you want to root your current stock ROM you can just flash SuperSU through the install menu in TWRP recovery. You'll find a download link here:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
If you want to install a custom ROM, just find one you like, download it, read the install instructions on the ROM thread, perform a full wipe (cache/dalvik cache/factory reset/system) through the wipe menu in TWRP, then install the ROM through the install menu in TWRP.
Before doing either of these options you should make a backup of your current setup in the backup menu in TWRP. Select system, data, and boot, then swipe to backup.
Sent from my Evita
Click to expand...
Click to collapse
tried to flash recovery ...
"error : cannot load "recovery file name" (openrecovery-twrp-2.6.0.0-evita)
though it is in the same folder of android where I put fastboot and all that stuff..
The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita
timmaaa said:
The command should be:
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
Sent from my Evita
Click to expand...
Click to collapse
oh I forgot the img thing haha
thanks a lot
though now I wanna flash the venom rom (sense 5 , 4.2) and step 3 says : "Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)" what does that mean ?
If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita
timmaaa said:
If you're downloading the file directly to your phone, use an app called AFV (Android File Verifier) to check the md5. After you've downloaded the ROM just copy the md5 listed on the download site, open AFV, paste the md5 into the box, click the select file button, navigate to the file then long press it and select calculate md5, hopefully it'll say success. If it says anything other than success the download is corrupt.
Sent from my Evita
Click to expand...
Click to collapse
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread
madshark2009 said:
oh ok thanks alot you are smart you know ?? extremely helpful and nice to have you around the thread
Click to expand...
Click to collapse
Thanks, I've just been doing this for a while. Give yourself some time and try to keep up with things and you'll gain a whole lot of knowledge too.
Sent from my Evita
ClockWorkMod recovery version 6.0.5.0*, using Cyanogenmod 11 source, ported for Cherry Mobile Omega Icon (aka Micromax A121).
DOWNLOAD:
recovery_CWM_h700.img
SOURCES:
Device tree: https://github.com/arvinquilao/android_device_cti_h700/tree/cm-11.0
Flashable via fastboot or adb (dd command). Make sure you have a backup stock recovery in case CWM fails to work. You can also use Flashify to install the img file, it's available at the Play Store. Another alternative is Universal AIO flasher.
To test via fastboot: "fastboot boot recovery_CWM_h700.img"
To install via fastboot: "fastboot flash recovery recovery_CWM_h700.img"
Feel free to comment if you encounter issues with this CWM port.
*This is the classic, non-touch version.
arvinquilao said:
ClockWorkMod recovery version 6.0.5.0, using Cyanogenmod cm11 source, ported for Cherry Mobile Omega Icon (aka Micromax A121).
DOWNLOAD:
recovery_CWM_h700.img
SOURCES:
Device tree: https://github.com/arvinquilao/android_device_cti_h700/tree/cm-11.0
Flashable via fastboot or adb (dd command). Make sure you have a backup stock recovery in case CWM fails to work. You can also use Flashify to install the img file, it's available at the Play Store. Another alternative is Universal AIO flasher.
To test via fastboot: "fastboot boot recovery_CWM_h700.img"
To install via fastboot: "fastboot flash recovery recovery_CWM_h700.img"
Feel free to comment if you encounter issues with this CWM port.
Click to expand...
Click to collapse
Good Work Bro Keep it up
Notice: Improvements to 10 Post Rule
A New Q & A thread , for This Topic has been created in the Q&A, Help & Troubleshooting Sub-Forum.
New Discussion and Q & A Tabs have also been created, located just under threads Title when viewing in a Browser.
Posts from members with less than 10 posts will automatically be posted in the new Q & A thread.
Please check it out, and see if you can help out someone with a question about this Topic.
For more about this new feature see: Improvements to 10 Post Rule
Thanks so much, buddy. Awesome work, these recoveries (TWRP and CWM) of yours.
Now digging through your device tree, trying to get a grab on how to compile this stuff by myself.
Too bad ROMs for this are few and far behind; it would've been golden if someone's up to the task of porting CM10.1 or 11 for this. Thanks for the CWM though, that'll be much appreciated.
Alcatel Tetra (5041C) All In One Thread
##############################################################################
UPDATE: 4-20 2020 added direct link to folder with free tools for linux and windows
new Url for our site with the tools and roms:
https://a-team-solutions-downloads.myddns.rocks/Site/ UPDATED 4-20 2020
this is active as of 2/26/20
OUR TG Chat Group for all our best advice and where our book of development Notes live,
Check it out.
https://t.me/Android_General_Chat UPDATE: still live on 4-20 2020
UPDATE:
direct shortcut to free version of our AIOtoolkit tools
Live on 4-20 2020
https://a-team-solutions-downloads.myddns.rocks/Free/AIO-ToolKit/
###############################################################################
This is where you want to start for the Alcatel tetra,
Here you will get root ,
You will get the latest fastboot fix to get a custom recovery and bootloader unlock,
Learn how to flash a gsi on the tetra and get it working correctly.
You will see our tool to get magisk working correctly on a pie gsi 's
You may find gsi images here that are modded to be device specific for the tetra.
You will find links to a device support group where u can get help with trouble shooting if you get into a jam.
And you will find access to a factory tool to unbrick a tetra in the last resort.
There will be no disrespectful language in this thread.
It will not be tolerated here you will be reported to the moderation team if you post
disrespectful/flame-war comments here.
This is not a general discussion thread.
This is The place to find everything you need for your tetra :
ROMs
Recovery
Mods/flashable zips
And precise correct instructions for the use of these.
Disclaimer :
I nor anyone at XDA nor any of the devs who's work you find here are responsible for your actions in choosing to use the tools and methods laid out in this thread.
If you follow the instructions here ,
you do so at
You're Own Risk.....
Bricks and loss of data may happen to your device as a result
You have been warned.
This thread is a work in progress please be patient.
Credits go to :
@diplomatic for mtk-su and his awesome kernel exploitation work which allowed me write access to the device partitions ! Thanks Man!
@clcombs262 for opening the old root question thread that got my associates and I together to work on this device!
@PizzaG for his work on this device, his trick for SugarMTK to get lk downgrade in the beginning. and giving us Sugar MTK login so we can use it to restore the countless times we bricked developing all of this stuff. You're Awesome Bro !
@Spades99 for tinkering and getting hotspot working without a plan on oreo roms , good Idea Bro!
@topjohnwu for magisk and all the wonderful things we get from that!
@AndyYan for the LOS 16 build I modified to be my daily driver rom.
@phhusson For his excellent work on the treble-project and for giving us gsi's to play with. Thanks Man You Rule!
@LgPWN'd For Fastboot-fix, Magisk-Gsi-Helper.zip, porting P.B.R.P and Red-wolf custom recoveries, fixing adb (kinda) in twrp.
and just about everything else...
Special thanks to a lady called Alexandria and @clcombs262 for getting me access to a server to build roms/recoveries for these devices . Hey Thanks A Million You are the Stuff !!!
Twrp Builder for the fist port of twrp for tetra
Fastboot fix:
Fastboot fix:
So most users don't have fastboot access
We have a fix for this.
Ok the very first thing you're going to want to do is gain some type of temporary root shell so that we can downgrade the bootloader by writing directly to the partition so that we can then issue a command to reboot to bootloader and use fastboot to unlock your bootloader and we're going to want to do that without using sugar mtk so that we don't end up with our unlocked device from eBay being relocked like a brand-new Tetra from Walmart.
So we are going to be using a kernel exploit called mtk-su to gain the temp root access.
Here is the kit
https://drive.google.com/open?id=1JfLzT6F66yBj6Qor_t4P9340CwLz5Y18
Instructions For Windows Users:
Instructions from a booted Tetra that has no reboot to fastboot functionality:
Extract this zip.
open the folder location in a terminel/CMD/Powershell window...
enable developers options.> enable OEM unlocking.>enable USB debugging
make sure the drivers are installed for your phone on windows {likely they are }
first get device recognized by adb
./adb devices
accept the prompt on the device.
after this move on
copy paste these commands one by one into terminal...
Code:
./adb push exploit /data/local/tmp/exploit
Code:
./adb push U8M8Y0Y0CT00.mbn /data/local/tmp/lk.bin
Code:
./adb shell chmod +x /data/local/tmp/exploit
Code:
./data/local/tmp/exploit
NOTE: the file exploit is just Mtk-SU renamed to " exploit "
Wait for it to say new UID 0
should now see # instead of $ in the prompt...
then type this command
Code:
dd if=/data/local/tmp/lk.bin of=/dev/block/platform/bootdevice/by-name/lk
after that completes type this...
Code:
reboot bootloader
Now you should see the fastboot prompt...
ENJOY
Instructions For Linux Users:
instructions for linux are the same except,
remove the
Code:
./
from each adb command...
Unlocking the bootloader
Unlock bootloader:
WARNING THIS WILL ERASE ALL OF YOUR DATA
Well this is done the same as any other device with fastboot.
here's how for the neewbz out there.
Code:
fastboot oem unlock
then confirm by pressing the volume-up key on the device
and then type this code to reboot...
Code:
fastboot continue
Let your device fully boot up then go through the setup wizard again {I always skip through it} and re-enable developers options and adb debugging.
Your bootloader should now be unlocked and you will see a warning message each time it boots. this warning can safely be ignored, In fact it can also be removed completely but that's a subject for a different topic.
NOTE:
though your bootloader is unlocked there are 2 files inside the device that will replace your recovery with the stock one on boot if you don't remove them, but you also have to disable dm-varity in the fstab before you remove the files or you'll get a soft brick.
Fstab lives in /vendor/etc partition
the easiest way for most users to fix this is to follow the instructions in this gsi prep package by @PizzaG ,
https://drive.google.com/file/d/1ir_S_fEX3SU3G-Fk7-YFl2z5NXfsIJ5l/view
the thing to remember is that you only need the backup to restore from his package, and DO NOT DO the LK DOWNGRADE from his package it's old and uses sugar MTK to replace LK and it messes up network stuff in the process.
You already completed the LK downgrade if you followed my instructions in the last post.
You should be ready to flash the recovery of your choice, do a backup from that recovery and then follow PizzaG's instructions on how to replace your backup with his one.
then if you wanted cricket-rom restore it all if not just restore /vendor and /system to get gsi working and fstab fixes and to auto remove the files that are in stock system to replace recovery on booting
Flashing the custom recovery
Flashing recovery and choices of recovery:
You can use any recovery that yourself or anyone else ports to the Tetra.
The TWRP images in the pizzaG package work but adb is broken in those.
So if you want TWRP that has ADB functionality "sideload etc."
grab the version here:
https://forum.xda-developers.com/showpost.php?p=79815342&postcount=253
Other Better Alternatives:
Pitch Black Recovery Project Ported By LgPWN'd:
https://forum.xda-developers.com/android/development/unoficial-pitchblack-recovery-alcatel-t3946122
Red-Wolf recovery ported by LgPWN'd:
https://forum.xda-developers.com/android/development/red-wolfrecovery-alcatel-tetra-5041c-t3946121
So Choose your recovery, and flash it in fastboot...
Code:
fastboot flash recovery recovery-file-name
Example :
Code:
fastboot flash recovery TWRP.Tetra.img
after this to get to recovery without booting all the way back to system
Code:
fastboot oem reboot-recovery
You should now be in a custom recovery environment .
Remember if u want to use userdata partition u need to disable variety in fstab mentioned earlier, and u need to format data to f2fs to
Kill the encryption and then reboot to recovery to be able to use data partition.
Also there is a file that will cause the stock recovery to over write your custom one.
/system/bin/install-recovery.sh
Rename it or delete it from custom recovery before rebooting
Also some people have had errors using the menu to format data
From the p.b.r.p port.
If it happens to you, try it from one of the twrp images in pizzaG prep package
The older version works when the newer ones don't sometimes
Enjoy !
ROMs:
Most of the ones listed Here are good :
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
the thing to remember is that you need an image for an Arm A-only Device
How to root the Tetra
Reserved
To root or not to root....?
How to root the Tetra.
To root the tetra, follow up instructions to unlock Bootloader flash recovery
then flash your choice of root.zip
When using LOS roms I prefer to use the addon-su from LiniageOS extras
{google search that ^^^} which works out of box just flash and reboot
or you can also use Magisk which is many peoples favorite.
But to get magisk to work you'll need a few things,
first the latest magisk zip to flash, secondly to get it to show you a root prompt in gsi's you'll need to add back some missing library files.
Luckily Myself and @PizzaG have made a flashable zip that can be flashed from custom recovery to do just that.
It'll be in the attachments to this post.
AND NO THIS MAGISK FIXER WILL NOT WORK FOR ANYTHING BUT A TETRA 5041C !!!
so to get magisk running:
first flash :
Magisk_17.2+(GSI_Android_9-Helper)[7-12-2019].zip
then reboot back to recovery,
then flash magisk latest zip
reboot and enjoy root
Gapps to flash or not to flash....?
This is solely up to personal preference.
some users like google and the convenience of google apps,
some users Absolutely abhor Google and all of it's policies and data collection.
Where to get Google apps.
https://opengapps.org/
How to make them work with custom rom/GSI .
there's a great article on it already here:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/
Support Group
Device support:
Where to get help FAST if you're stuck.
We are doing most of our development work on a telegram group, here's the links for that, come ask questions, grab latest updates before they are released here on XDA etc.
https://t.me/Android_General_Chat
EDIT: URL FIXED TO POINT TO CORRECT PLACE 03/08/2020
A word about Carriers and networks
lock/unlock status:
Carriers or other third parties that have unlocked your tetra have done so by manipulating the data contained in your NVRAM and NVCONFIG and Simlock partitions....
so you can factory reset , flash boot.img or system.img or vendor.img and still retain your unlock, though you may need to adjust your APN settings depending on your choice of ROM.
How to keep from accidentally re-locking your network:
The only way this happens is when you flash those protected OEM partitions or corrupt the data in said partitions.
The sure-fire way to relock a tetra to At&t is to flash / upgrade it using SugarMTK tool
as it flashes EVERY partition with the latest stock released from the server in china or where-ever.
What you can do if it happens to you....
There's not a lot you can do about it. Your carrier will likely refuse to help, at least thats what other users have reported to me.
What you can do is contact any reputable Unlocking service and most times they can re-un-lock it for you.
BUT NOTE: you want to use someone that has the cable-unlocks via pc and usb cable, not the ones who offer some code as your device likely will never ask for the code if you changed things to get this far.
And
Why we can't discuss it further here...
WELP, the big deal here is liability and the Forum rules of XDA.
We are not to discus these things because they actively seek to bypass Carrier Network Restrictions
and as such it's against XDA rules.
However if you find yourself in this position, you might want to contact someone at our device support group for help/advice as we have had to fix this situation before.
we can at least point you in the right direction,
since here on XDA i'm not allowed to Promote/recommend anyone to help fix this because it'll cost you money PERIOD and that's basically considered advertising.
Bricked Devices
Bricked Devices.
Un-bricking.....
FIRST-OFF WHY HAVE YOU NOT MADE A COMPLETE BACKUP TO STORE SOMEWHERE OFF THE DEVICE TO HELP YOU IN THESE SITUATIONS?
that will be your saving grace in most soft-brick situations, where you can still get to recovery Via button combo or via
Code:
fastboot flash recovery recovery.img && fastboot oem reboot-recovery
To unbrick from a hard brick our only choice for now is SugarMTK.
you can find it in @PizzaG Gsi Prep package...
NOTE:
flashing with sugar restores ALL partitions of the device to factory stock release...
what this means is that even if your carrier or some service unlocked your device to use on networks other than At&t you will NOW be stuck with At&t or cricket or it's MVNO's
SUGAR MTK WILL LOCK THE NETWORK ON YOUR TETRA EVERY TIME
Reserved.
Tools
Miscellaneous
Reserved
Discussion of dual boot and other stuff
We are currently working on.
I there an updated easy way for root yet preferably without pc
Thanks for the guide and fastboot fix. I'm running the LineageOS gsi based on pie, but along the way I have lost the ability to turn on wifi and bluetooth. I'm new to mtk roms, so I was wondering where the firmware for the radios is living.
Idealxtra
Pureindica said:
Idealxtra
Click to expand...
Click to collapse
??
So anybody struggling along here can ask about help or other devices such as Idealxtra on our support group on telegram
https://t.me/Android_General_Chat
Is there an updated easy way for root yet preferably without pc ?
Nope, you can however use mtk-su with a terminal emulator to get tmp root then u could use DD to make a copy of your boot.img
then u can use magisk manager apk to patch said boot.img, and then u can write that back to the device using mtk-su and terminal emulator. but this still requires you to have the device bootloader unlocked i believe or you'll brick
Thanks for the guide and fastboot fix. I'm running the LineageOS gsi based on pie, but along the way I have lost the ability to turn on wifi and bluetooth. I'm new to mtk roms, so I was wondering where the firmware for the radios is living.
i think its in vendor partition
The link for the gsi prep package does not work. Anyone have a new link?
sazechman said:
The link for the gsi prep package does not work. Anyone have a new link?
Click to expand...
Click to collapse
Visit our Website, TeleGram and get AIO ToolKit
Website Down
PizzaG said:
Visit our Website, TeleGram and get AIO ToolKit
Click to expand...
Click to collapse
I have tried to get to your website "http://a-team-solutions.dynu.net/" to no avail. I have tried from many different sources both with and without vpn. I have posted in the thread for the site but have not received a reply. Is the site still available? I would gladly pay for the registered version if it solves my bricked phone problem.
Thanks
This guide is general guide for the installation of custom ROMs. I will also include guide to install stock ROM on devices which have been bricked or for solving various problem which you may encounter in custom ROMs. There are other guides for the same purpose but most of them are outdated and many of you seem to ignore old guide despite the fact that those guides can be helpful.
This is guide is only relevant for installation of custom ROMs which were released up to the date of posting this guide or up to android version 11. Recovering a bricked device can be done in the same way as to this one but installation instruction for devices with android version greater than 11 may differ.
DISCLAMER
Code:
I am NOT responsible for bricked devices,
thermonuclear war or for you getting fired because your alarm app failed.
Make sure the bootloader is unlocked and never lock the bootloader
How to unlock bootloader ?
>See in this thread.
Hard Brick, Soft brick, Problems in custom rom due to bad base, installation of base for switching to custom roms: windows linux
Installation of stock ROM through fastboot : The reply below
Migration from stock base to custom ROM : CLEAN FLASH
Migration between different version of same custom ROM : DIRTY FLASH
FOR SPECIFIC THREADS
Oragne Fox For Daisy
TWRP For Daisy
Magisk
CREDITS:
LInkBoi for his previous guide and TWRP
DarthJabba9 for Orange Fox Recovery
Every pros in daisy telegram groups.
EDL FLASHING (For windows only)
EDL flashing can be helpful when flashing every partition of device is needed either for clean stock base or after brick or after some failure.
EDL flashing can be the final resort when everything else fails.
PREREQUISITES
1) A good USB cable, your phone
2) A PC with either windows or linux
3) Fastboot drivers from google and edl drivers from qualcomm
4) Platform tools from google
5)Fastboot rom. This should be full rom in .tgz format.
6)Xiaomi flash tool (LATEST VERSION AVAILABLE)
Install the adb and fastboot drivers from google. If you are on windows 10 or greater then you can also use "windows update > optional updates" to update adb and fastboot drivers + edl drivers. For the installation of drivers always use trusted sources and don't turn of driver signature enforcement if you can.
Extract the platform tools in a convenient folder, we will be doing our operations from this folder for fastboot and adb opeartions. Extract the fastboot ROM and place that in convenient folder as well. And for xiaomi flash tool extract the zip and launch XiaoMiFlash.exe .
If you can access fastboot in you phone then the phone can be booted into edl mode through fastboot else you have to take out back cover and short the testpoint pins to make the device boot into edl mode (see the attached image ).
If you can access fastboot. Boot into fastboot and type the following command in terminal.
To check if device is connected properly and drivers are properly installed
If no devices is shown then connect device properly with good usb cable and check the drivers.
Code:
fastboot devices
To boot phone into edl mode. This is only possible if the bootloader is unlocked else testpoint-edl is the only option
Code:
fastboot oem edl
The device should be shown as COM device in device manager ( Windows ). If not then either drivers aren't installed properly or your phone isn't in edl mode.
Now click on refresh button in xiaomi flash tool. Your device should be recognized as com device. Set the path to the images folder ( extracted fastboot rom ). Select CLEAN ALL option . If everything is good then click
on FLASH. The flashing process should start now. After the process completes keep pressing power button to boot device into the currently installed ROM.
Just install the rom and setup once even if you're going to flash custom rom next. This reduces various problems which may come in custom ROMs.
If any error occurs then try the following:
Make sure you are using latest flash tool.
Good fastboot rom (shouldn't be corrupted )
Good USB cable and try different ports of the PC.
The flashing should be done immediately after booting to edl. If not then take out battery and reconnect it if you have back cover open(In case of hard brick). Or keep pressing power button and volume down to boot into fastboot and boot to edl mode again from the above instructions(If fastboot is accessible)
For booting to edl using testpoint:
> Take out backcover
> Disconnect battery
> Short the pins
> Flash
> Connect battery after flashing is complete
> Keep pressing power button to boot into system.
qdl flashing ( linux only )
For very detailed guide github -> bkerler edl
Thanks to DEFXZ and LinkBoi for suggesting this alternative.
Make sure you have platform tools, fastboot rom and other prerequisites to detect device properly.
clone the repository in convenient place
Code:
git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git --depth=1
change to qdl directory
Code:
cd qdl
Build qdl tool
Code:
make
Finally flash the rom
Code:
./qdl --storage emmc --include /path/to/stock/images /path/to/stock/images/prog_emmc_firehose_8953_ddr.mbn /path/to/stock/images/rawprogram0.xml /path/to/stock/images/patch0.xml
The paths are the paths to various files inside the images folder which will be obtained after fastboot rom is extracted.
For further informations:
Original github link
qdl discussion in XDA
FASTBOOT FLASHING
PREREQUISITES
FASTBOOT DRIVERS
PLATFORM TOOLS
FASTBOOT ROM
GOOD USB CABLE
PC WITH WORKING USB PORT
See this for meeting prerequisites.
Install fastboot drivers, connect device to PC via USB.
Extract platform tools into a convenient folder.
Extract fastboot ROM into a convenient folder.
Go to platform tools folder ( this will contain files and executable like fastboot.exe) and open powershell or any terminal window there
[ shift + right click and select open (powershell) window here ]
Type this command to see everything worked correctly.
Code:
fastboot devices
If not then check every step properly.
Now execute the script to flash the ROM.
Execute flash_all.bat script for windows PC.
Execute flash_all.sh script for linux PC.
If platform tools cannot be accessed system wide then.
Code:
./fastboot devices
will provide fastboot devices information.
For flashing drag and drop flash_all.bat or flash_all.sh file into the terminal.
Code:
'/media/user001/user/daisy/stock_roms/daisy_global_images_V10.0.18.0.PDLMIXM_9.0/flash_all.sh'
It will look something like this in linux and similar in windows.
If any error occurs the search for particular error. Most of the times the error is due to corrupted fastboot ROM or bad connection between phone and PC.
FINALLY! FLASHING CUSTOM ROM
STEP 0
Flash(if not flashed already) the stock base recommended by particular ROM, if the ROM doesn't recommend a specific stock base flash 10.0.18.0 from the above instructions.
PREREQUISITES
TWRP or ORANGE FOX RECOVERY
Fastboot drivers and platform tools (details above )
The ROM which you want to flash, choose from here
GAPPS package if rom is vanilla and you want to install it.
Magisk if you want to root.
As you may have known by experience, our device doesn't have recovery partition so, flashing recovery through fastboot isn't possible. For flashing recovery first we need to boot recovery image and then only we can flash it.
If you want to use twrp:
Download both twrp*.zip and twrp*.img and place it in a convenient place.
If you want to use orange fox recovery:
Download orangeFox*.zip and extract it.
Keep both the .zip and .img file in convenient place.
If you have sdcard then copy ROM file, gapps, magisk, twrp or orange fox files into sdcard.
If not then there will be further instructions.
Now, connect the phone to the PC via USB and enable usb debugging. And open terminal in the platform tools folder as in above instructions.
Check device connectivity:
Code:
adb devices
Reboot into fastboot:
Code:
adb reboot bootloader
Check device connectivity:
Code:
fastboot devices
Lets check if the bootloader is unlocked:
Code:
fastboot oem device-info
If bootloader isn't unlocked you won't be able to flash custom recovery into the device. So, first unlock the bootloader. This should be allowed in the developers option of your phone first. This will factory reset the device.
Code:
fastboot oem unlock
Now if everything is good then it's time to boot into custom recovery:
Code:
fastboot boot recovery.img
recover.img is name of image of whichever custom recovery you want to use.
Code:
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
It's like this in my case. You can drag and drop after typing fastboot boot
The phone should now boot into custom recovery. If it ask for decryption then your lockscreen password should work there.
if you want to flash recovery only then find the recovery.zip you want and flash it.
The steps further is also valid for moving between different custom roms. The term used for such process is CLEAN FLASH.
For Flashing custom ROMS :
SOMETIMES FLASHING INSTRUCTIONS MAY DIFFER SO, BE SURE TO CROSS CHECK FOR INSTRUCTION IN ROM SPECIFIC XDA THREAD OR TELEGRAM GROUP
The following action will wipe userdata if not wiped already. Be sure to backup data before these steps. Also if you encounter any future problems full backup from custom recovery may be able to solve most of the problems. So, be sure to keep full backup(including every partition) of your device.
Go to main menu > wipe > select all except internal storage and microSD.
Swipe right to perform wipe.
Install custom recovery by flashing recovery.zip
(This is done in case adb push doesn't work below and sdcard isn't available for flashing)
Again go to main menu > wipe > format data
Type yes and press enter.
If you don't have files in your sdcard then:
push rom file + gapps + other files into your device through adb push.
The command will be something like this:
Code:
adb push '/media/user001/storage (1)/daisy/posp/potato_daisy-11-20210919-dumaloo.v4.2.3+20.Community.zip' /sdcard
If adb push fails to work then you can reboot recovery and simply copy the files through file explorer.
Reboot to recovery only if you had installed recovery after wiping system else the device will soft brick
Now flash the rom.zip by selecting the file and swiping right.
Flash custom recovery if the ROM doesn't contain recovery
We have to change current slot even if we don't want to flash anymore things.
Latest recoveries changes slot automatically So, go to main menu > reboot > recovery
Now flash files which you want to flash i.e. gapps and magisk.
Again, Don't flash gapps if the ROM is of Gapps variant
Most of the roms now have implemented FBE (File Based Encryption ). So, you need to format data before rebooting to system. Again, check for specific ROM installation instruction if that is required or not. If you keep data from previous ROM that won't be considered a clean flash so, for proper clean flash format data before rebooting to system.
reboot system
MOVING BETWEEN DIFFERENT VERSION OF SAME CUSTOM ROM
Dirty flash or OTA
Most of the newer ROMs have seamless update ( even the unofficial ones ). The OTA update is simple. Just go to updater ( in settings > system or native app, depends upon the rom). If your ROM is of vanilla version then make sure gapps and/or magisk which you have installed, your ROM and custom recovery all support addon.d survival script. If they don't then you may have to flash everything again after update process is complete.
If custom recovery itself doesn't support update then you may need to choose different recovery or dirty flash ROM from the recovery. Don't worry most of the roms and both the recoveries for daisy support OTA and addon.d survival.
DIRTY FLASHThe process of flashing a ROM on top of existing one keeping the /data partition intact is known as dirty flashing. Such flashing must be done only on different builds of same ROM and it isn't recommended to flash build of lower version on top of higher version.
The steps for dirty flashing:
Download the update package.
Reboot to recovery
Enter password for decryption if encrypted.
Flash the update.zip package.
Reboot recovery, if recovery/rom doesn't support survival of recovery then flash recovery before rebooting to recovery.
If gapps and/or magisk survival isn't supported then flash gapps and magisk, make sure gapps is of the same type which was flashed before.
reboot system
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
We have to change current slot even if we don't want to flash anymore things.
Click to expand...
Click to collapse
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Execute flash_all.bat script for windows PC.
Click to expand...
Click to collapse
Is this a section i can bypass ? if not where can i get them from ?
Cheers
steve.loveday said:
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Is this a section i can bypass ? if not where can i get them from ?
Cheers
Click to expand...
Click to collapse
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
user-001 said:
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply,
I'm getting confused with all the various guides all seem to want you to do it a different way.
As i'm wanting Lineage thier instructions are...
Installation:
Download the latest build from here
Download LinkBoi00's version of TWRP here
Reboot to bootloader (adb reboot bootloader)
Fastboot into TWRP recovery (fastboot boot twrp*.img)
Do a factory reset in TWRP
Flash the latest build of Lineage OS
Boot into your new phone
Click to expand...
Click to collapse
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
This guide deals with how to do something rather than what to do, meaning you should always do what particular rom suggests but the way to do this is mentioned here.
edl or fastboot flashing comes under clean flashing with new base, most of the time you aren't required to do this.
The script should be clean_all.bat or something similar just don't execute script with lock in the name(it will lock the bootloader)
And if you're already on the recommended base you don't have to flash the fastboot rom.
First of all, thank you very much for the detailed guide. What you have done here took a lot of work to do but it will help a lot of people (including me) to understand, albeit rudimentarily, the structures and functions of the devices etc.
For all that, thanks again.
When I start using the guide, I will update this post with any questions, such as :
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
why not doing below? (For those who, like me, are not very familiar with linux.)
1. > adb push <twrp.img> /sdcard or same adb push "C:\platform-tools\twrp-3.5.2_9-2-daisy-unofficial.img" /sdcard
( which means push <file> from "adb|platform-tools\ folder" (eg. C:\platform-tools\)
into the root of <internal storage> | /storage/emulated/0 )
2. Reboot from adb to fastboot:
> adb reboot bootloader
3. Boot the image from <internal storage>:
> fastboot boot /sdcard/twrp-3.5.2_9-2-daisy-unofficial.img
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
I followed your "EDL FLASHING" post (#2) and it worked exactly as you mention!
In short, I was comming from unsuccessful flashing... but this is out of topic.
For me, did not worked the first time (after restarts) but the other day worked perfect.
The point is, most of times, it's becase windowz drivers.
We have to point that windowz needs their time to take the drivers in place. So, be patient and leave windowz to (not forced) restart(s).
AntonyMan said:
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
Click to expand...
Click to collapse
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
For future references, the extracted fastboot ROM should be like this and you need to execute flash_all.bat or flash_all.sh script depending upon your OS or terminal.
user-001 said:
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
Click to expand...
Click to collapse
Of course I'm talking about something else. lol
I was talking about that 'strange' address. fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img' (explained in post #11)
There is not such a directories in my miA2Lite phone. Obviously, it's because you are on Linux or Mac (UNIX). On Windowz 'command prompt' syntax it's slightly different.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
AntonyMan said:
Of course I'm talking about something else. lol
I was talking about that 'strange' address. There is not such a directories in my miA2Lite phone.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
Click to expand...
Click to collapse
The twrp image was on my pc(linux) i was booting directly from pc's terminal. And if you use only adb(or fastboot) then the paths are pc's absolute paths.