Database Info

[Q] how to mod w9 rom system.img

mid w9 use rk2818 chip
i use rk2808 mod tools unpack the system.img but not
pls help me how to unpack/pack to the w9 system.img
thanks master

any one help me

You got any luck with that? I have been trying everything I could think of without success.

http://twitter.com/naobsd has expressed interest in helping.
He needs a system dump
RK2818 can be rooted with UniversalAndRoot
You then need to run a Terminal Emulator application to dump the contents of /system into a tar and upload it
If you can dump the contents of other useful partitions, that might be good as well.

sorry for my inaccurate explaination.
I don't want dump image itself.
I already know
1. system.img in update.img is encrypted (other files are not encrypted, same as RK2808)
2. RKAndroidBatchUpgrade.exe for RK2818 decrypt system.img, then flash into device
3. decrypted system.img(cramfs) can be get by dumping system partition on live device
4. dumped decrypted system.img can be unpacked by fsck.cramfs
then, I want know following procedure can be done:
5. pack update.img with dumped decrypted system.img from device
6. flash update.img(5.) by RKAndroidBatchUpgrade.exe for RK2818
it should be easy to try, but I don't have any RK2818 device. I'll get ONN-N2 but no official firmware is released yet. so I can't make complete update.img for ONN-N2. (no RK28xxLoader(L).bin)
--
I know old flash tool for RK2808 can flash single partition. I think it should work on RK2818 because new flash tool for RK2818 can be used for my RK2808 device (iRobot)
but, anyway, I don't have RK2818. I can't test anything on real RK2818 device.
need your help! see here: http://www.slatedroid.com/index.php?topic=12683.msg105067#msg105067

Wopad?
I'm not sure if I have the same device as in this thread, but I'm familiar with adb and rooting. I've tried universal Androot on my device and it doesn't give me root. Z4root does but only temporary. I would love to help with whatever you guys need, just need a couple commands and will send files.
Oh it's a wopad rk2818 capacitive no trackball 2.1 model 7001
i can give any other info if needed. Hopefully we can get some kind of development going on this tab. It's a good little device, Rom is not so good though.

For reference, W9 ROM:
http://ramos.com.cn/support.php?support_downid=264
2010-12-08

fun_ said:
sorry for my inaccurate explaination.
I don't want dump image itself.
I already know
1. system.img in update.img is encrypted (other files are not encrypted, same as RK2808)
2. RKAndroidBatchUpgrade.exe for RK2818 decrypt system.img, then flash into device
3. decrypted system.img(cramfs) can be get by dumping system partition on live device
4. dumped decrypted system.img can be unpacked by fsck.cramfs
then, I want know following procedure can be done:
5. pack update.img with dumped decrypted system.img from device
6. flash update.img(5.) by RKAndroidBatchUpgrade.exe for RK2818
it should be easy to try, but I don't have any RK2818 device. I'll get ONN-N2 but no official firmware is released yet. so I can't make complete update.img for ONN-N2. (no RK28xxLoader(L).bin)
--
I know old flash tool for RK2808 can flash single partition. I think it should work on RK2818 because new flash tool for RK2818 can be used for my RK2808 device (iRobot)
but, anyway, I don't have RK2818. I can't test anything on real RK2818 device.
need your help! see here: http://www.slatedroid.com/index.php?topic=12683.msg105067#msg105067
Click to expand...
Click to collapse
My tablet is based on the rockchip 2818 ref. design, the pure odm device as it were, model is the yifang m7.
The issue i stumbled upon is that the little ****er is still encrypted on the blocklevel device. (mtdblock4 for /system)

[Resolved] [Q] AOSP ICS Porting to Samsung Galaxy Tab2 10.1(GT-5100) Please Help!

Hello everyone,
I am newbie Android ROM development. Nowadays I try to port a specific custom ROM(a special ROM for my company) for Galaxy Tab2 10.1 (GT-P5100). But there is a point that I cannot figure out.
First of all I downloaded android ICS source code and apply my company's module patch to this source. Then I found device and vendor tree for my GT-5100 device and put it my source tree. Finally I built Samsung GT-P5100 kernel and put output file to correct place. At the end of these operations, I compiled all device tree successfully, now I have out/target/product/p5100 file which contains boot.img, system.img, userdata.img etc.(I attached an image file). Everything is fine untill this point. Normally in fastboot mode, I use "fastboot flashall -w" command and img files are automatically flashed to device. But GT-P5100 does not support fastboot mode.Question is this: How can I flash these img files(out/target/product/p5100 file) to the device? I searched lots of threads but cannot find a solution. I also tried to create a ROM which includes system file, boot.img and META-INF file. However it is not worked. Because create a META-INF file is very complicated and I have to find a quick flash option.
I need your helps.
Thanks,
------------------------------------------------------
Edit:
Finally I found solution. Just nedded to use command : make -j4 otapackage and then I get the ROM package to flash this AOSP.

[Guide] [SC8830/SC7731/SC9830] Custom Recoveries Porting guide for Spreadtrum phones.

Code:
[CENTER][COLOR="Red"]Your warranty is now void.[/COLOR]
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research before asking help and reporting bugs and please read the entire OP.
YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.[/CENTER]
All suggestions and helps are welcome here so please help me in improving this thread by suggesting your ideas.
This guide will work for any SPRD phone (any SPRD chip) from Old versions of android to latest Oreo but recoveries that I provided in this thread will work for devices from KitKat to Marshmallow no guarantees for older or newer versions.
Buckup! Backup! Backup!​
Before modifying system it's highly recommended to have full dump of your device. So don't forget to take backup.
It's simple to get custom recovery for rooted users as they can directly backup, modify and flash recovery or boot images on the go with the help of root. But non-rooted users need to do some extra which will be explained later. Follow the below steps:
=>Download and setup AIK (Android Image Kitchen)
=>Grab your stock_recovery.img
For rooted users​Install Flashify, Rashr, Partitions Backup or like apps (available on play store for free) and backup the stock recovery. If you are using Flashify to backup you have to rename the backed up image with .img extention
For non-rooted users​Download your stock firmware which will be in .pac extension extract it using this guide and copy the recovery.img
=>Now download custom recovery (for downloads see 2nd post)
=>Port recovery
For PC version of AIK​
• Extract the AIK on desktop in a folder (extracting inside other folder(s) is not recommended)
• Place stock_recovery.img (use the name recovery.img only I added stock to refer the image) in earlier extracted folder
• Now double click on 'unpacking.bat'
• Now you'll see two folders 'ramdisk (mostly executables)' and 'split-img (kernel to boot recovery) rename those folders like this 'ramdisk.s' and 'split_img.s' (renaming is used to avoid copying/moving needed files)
• Now delete the earlier pasted stock_recovery.img and paste custom_recovery.img (rename it to recovery.img)
• Unpack it just like stock_recovery
• Delete the split-img and rename the 'split_img.s' to split_img
• Open recovery.fstab from /ramdisk.s/etc (stock recovery's fstab) and /ramdisk/etc (custom recovery's fstab) using Notepad++ or with your favorite note editor. In case of TWRP recovery this file will be named as twrp.fstab if there is recovery. fstab you can ignore it.
• Edit the partition names and mount points in custom recovery with your stock recovery's fstab. But in most cases the mount points will be shown like this 'mmclbk0p17 for system partition' in that case you need to change custom recovery.fstab with the mount points of your device, to find out mount points of partitions install Diskinfo from play store and enable all options in it which will show complete information regarding each and every partition on your device
• At last double click on 'repackimg.bat' now you'll see 'image-new.img' which is ported custom_recovery.img for your device
• The final step is flashing the recovery. It's easy for rooted users simply use Flashify app to flash. For non-Root users you need to flash it over fastboot mode for this look at this thread.
For mobile version of AIK​
You can also port the recovery on-the-go using AIK-Mobile unfortunately to use this needs your device must be rooted with BusyBox (Stephen (stericson) is recommended) installed.
It's a flashable zip but you can extract the zip and place the files manually. Follow below steps for setup:
• Extract the AIK-Mobile.zip
• Paste the AIK-Mobile folder under data/local of extracted zip to /data/local
• Paste files under /bin of extracted zip to /data/local/AIK-Mobile/bin
• Make sure all files including folders are having these permissions "-rwrx-xr-x-".
For placing files, changing permissions and executing scripts 'Explorer' by speed software is recommended.
For porting follow above steps (steps in PC version of AIK) the only difference here is .bat files of PC version will be as .sh in mobile version which are to be executed as root for unpacking and repackaging images.
Note:Follow the instructions properly, don't quote entire OP while asking for help. Due to some touch related drivers missing in kernel of recovery in some devices touch recovery won't work in that case please use Non-Touch recovery. In lollipop or later versions don't flash <3.x.x versions which may result in SD card mounting issues and even flashing errors. First test the recovery that you ported by flash a simple mode (I prefer AIK-Mobile since it doesn't modify the system partition hence there is not chance of bootloop. Also see whether wipe options works properly or not in some devices wiping (even cache) takes ~10m in that case goto settings check the option "use rm -rf instead of formatting".
Hit thanks button instead of posting thanks it'll boost me to create more threads like this.
Credits:
Advan S4P [Official] (fb group), SuDroid Tech (fb group), @@ki , @Jitheshwar (it's me), and some aliens from other universe.​
Created: 27-09-2017
Last Updated: 27-09-2017

Custom recovery downloads
1) TWRP recovery images
2.7.0-0
2.8.5-0
2.8.5-0
3.0.0-0
3.0.2-0
3.0.2-0
3.0.2-0
3.1.1-0
2)Cyanogen recovery (for lollipop)
3)Cyanogen recovery (for kikat)
4)MIUI recovery
5)Ultra CWM
6)Temporary CWM (only for KitKat and older
7)Temporary Philz (only for KitKat and older)
Temporary recoveries provided here are not for porting. You can flash those zips directly from you stock recovery these recoveries will have basic functions like flashing ROMs, Wiping (in some devices it'll take too long to wipe so just use factory reset option of stock recovery and then flash this recovery finally the ROM. Back up option of recovery might not be fully functional. Scrolling is glitchy but it'll work when you press button. These are more for users who are unable get working recovery

Reserved for FAQ.

Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp

Jitheshwar said:
Click to expand...
Click to collapse
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??

Jitheshwar said:
..
Click to expand...
Click to collapse
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?

HemanthJabalpuri said:
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?
Click to expand...
Click to collapse
Read again carefully you have to pack custom recoveries ramdisk with stock split_img and reversing the process will mess up the recovery and then you have to flash the stock recovery. So read the guide carefully step-by-step and follow the process exactly unless you know different working method.

unknown said:
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??
Click to expand...
Click to collapse
Give it a try it may work. But none of the recoveries that are provided here will work for your device, you need to find Android 7.0 and later recoveries which will be compatible with your chipset model.

kaew158 said:
Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp
Click to expand...
Click to collapse
TWRP has nothing to do with boot.img. If you are not able to boot to recovery try different key combination. Is you messed up recovery too then flash it via fastboot and then flash the stock Rom.

Jitheshwar said:
Click to expand...
Click to collapse
Sir finally the process is to pack
⇛split_img of stock recovery ......
⇛ramdisk of custom recovery you listed by replacing recovery.fstab file
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....

HemanthJabalpuri said:
Sir finally the process is to pack
⇛ramdisk of recovery you listed by replacing recovery.fstab file
⇛spit_img of stock recovery right......
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....
Click to expand...
Click to collapse
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.

Jitheshwar said:
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.
Click to expand...
Click to collapse
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore

HemanthJabalpuri said:
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore
Click to expand...
Click to collapse
I clearly stated all the steps in an easy and simple way. My kind request to you to read the post again. And one more thing if you want to use apk version use it I don't have any issues but don't ask me if anything goes wrong.

i ported twrp 3.2.1 to sc8830 sucessfully but touch is not working , can you help?
where can i find non-touch recovery
I'm using android 5.1

What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.

denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones

Please fix the twrp links!!!

@Vortex said:
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones
Click to expand...
Click to collapse
No custom recovery will work on bootloader locked devices...

denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
Kernel architecture is ARM.

Alcatel Tetra AIO (start here)

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

[CLOSED][Question] About boot.img and ramdisk.cpio

Hello,
I'm just diving into Android stuff, and I'm going through Magisk stuff to understand more about it.
When I use magiskboot unpack boot.img of pixel 6a, it only gives me a kernel file. Is it normal for a stock boot.img to not to contain ramdisk.cpio?
I was under the assumption that it essentially tells the device what files to load and whatnot. If it doesn't contain the ramdisk.cpio, how does the device work when I just fastboot flash boot boot.img? Is there ramdisk.cpio already on the device?
Thanks!

drunk_santa said:
Hello,
I'm just diving into Android stuff, and I'm going through Magisk stuff to understand more about it.
When I use magiskboot unpack boot.img of pixel 6a, it only gives me a kernel file. Is it normal for a stock boot.img to not to contain ramdisk.cpio?
I was under the assumption that it essentially tells the device what files to load and whatnot. If it doesn't contain the ramdisk.cpio, how does the device work when I just fastboot flash boot boot.img? Is there ramdisk.cpio already on the device?
Thanks!
Click to expand...
Click to collapse
drunk_santa said:
Hello,
I'm just diving into Android stuff, and I'm going through Magisk stuff to understand more about it.
When I use magiskboot unpack boot.img of pixel 6a, it only gives me a kernel file. Is it normal for a stock boot.img to not to contain ramdisk.cpio?
I was under the assumption that it essentially tells the device what files to load and whatnot. If it doesn't contain the ramdisk.cpio, how does the device work when I just fastboot flash boot boot.img? Is there ramdisk.cpio already on the device?
Thanks!
Click to expand...
Click to collapse
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com