Hello !
A lot of people like me got this 'gift' tablet (in Spanish, we call it "the lamentablet", because it is "lamentable" = "terrible"):
https://www.the-china-office.com/t8100-tablet (here you can see full specifications)
That b***c allows us to unlock its bootloader, but in order to root it, we need to have the boot.img to apply magisk on it.
But the thing is that we cannot obtain it, nor dump the firmware, just in case... So, we are stuck.
Also in the docs on that webpage, it's a mention to a link with the firmware, but it is not available.
There is also no OTA update to play with...
Is there any way to obtain that boot.img / get all the partitions ? I've tested to make an adb shell to make commands to dump the partitions, but it says "it's closed", so not allowed.
I've tried to find a TWRP version but hey, guess it... There is none.
So, ... Got any ideas, you... GREAT "TECH GURUS" ?
Thanks in advance !
I have the same tablet, and would like to know if anyone has made some progress on this. As for now it's an useless piece of ****. Would like to play around with it, I can think of a couple uses for it. Thanks
can you boot into recovery and if so can you use ADB from there ?
Code:
cat /dev/block/boot > /sdcard/boot.img
3mel said:
can you boot into recovery and if so can you use ADB from there ?
Code:
cat /dev/block/boot > /sdcard/boot.img
Click to expand...
Click to collapse
I managed to reboot into recovery with ADB, but I get the following Error
C:\Program Files (x86)\Minimal ADB and Fastboot>cat /dev/block/boot > /sdcard/boot.img
The system cannot find the path specified.
What should I do?
UPDATE: Managed to unlock the bootloader with fastboot oem unlock command. I needed to install the Allwinner A100 drivers though, was stuck in a bootloop before that. Will now try to install Magisk.
This is what I got regarding the file system
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 495652 604 495048 1% /dev
tmpfs 495652 0 495652 0% /mnt
tmpfs 495652 0 495652 0% /apex
/dev/block/dm-3 592852 591024 0 100% /
/dev/block/dm-1 113696 113344 0 100% /vendor
/dev/block/dm-2 689644 687556 0 100% /product
/dev/block/nand0p17 13316076 796656 12519420 6% /data
/dev/block/nand0p7 757680 968 733120 1% /cache
/data/media 13316076 796656 12519420 6% /storage/emulated
Did you get this worked out? If not, you made reference to an OTA update file. If you have the OTA update.zip, upload it to Google Drive or other file host and post a download link. I should be able to extract the boot.img and recovery.img from the update archive. (If your tablet has a boot image devoid of a ramdisk, you will need to root using the ramdisk from the recovery.img). To determine ramdisk status, install the latest Magsk app on your tablet. Open the app and look for "Ramdisk" in the top section of items listed. If you see a "Yes," standard boot.img patching will work. If it indicates a "No," you'll need a recovery.img.
I was "given" (lol) a Qlink Scepter 8 tablet(AKA Obama tablet): exdroid sun50iw10p1 which cross references to an $49 retail Chinese ALLWINNER T8100 A100 tablet.
As the OP already stated: out-of-the-box this is an unusable POS.
I'm leaving this breadcrumb for the next poor person who inherits one of these... I spent over a hour doing research and reached a dead end.
The ARM is working at 32bit... no idea why... forcing it to 64bit will help. But why bother? A 10 year old low-end Samsung tablet would still be faster (and more stable).
If I had the boot.img, maybe I would spend a little more time with this.
Good luck and Godspeed.
I have this tablet allwinner a100 t8100 bricked BND-A863-CV2.0.Please help me with firmware
Good guys, I leave the boot.img for Tablet T8100 and patched with Magisk. Works correctly on the Rom Stock (Android 10 GO) on tablet T8100 with motherboard BND-A863-CV2.0.
As a curiosity, I am currently using GSI Roms on my tablet. The problem is that Roms based on Android 11 and 12, the Gyro Sensor does not work. On Android 10, if it works
Edit: I attached also the dump of the Rom Stock of my Tablet, in case someone needs it. https://www.mediafire.com/file/h0hnqhwah2qyf7y/RomStockT8100.zip/file
Only can be flashed by fastboot as a dump and only if you have an unlock bootloader.
Hi.
My tablet is constantly restarting and I want to reinstall the system. I have already formatted it by bios but it's still the same. How can I install this recovery by ssd card ?
TiagoG3400 said:
Hi.
My tablet is constantly restarting and I want to reinstall the system. I have already formatted it by bios but it's still the same. How can I install this recovery by ssd card ?
Click to expand...
Click to collapse
Can only be installed via fastboot
SamuEDL said:
Can only be installed via fastboot
Click to expand...
Click to collapse
But to use fastboot i have to pass those files to the sd card or i have to connect the tablet to the computer ?
If it is necessary what program do I use to install the software ?
Do I need to use the bios ?
Thanks !
TiagoG3400 said:
But to use fastboot i have to pass those files to the sd card or i have to connect the tablet to the computer ?
If it is necessary what program do I use to install the software ?
Do I need to use the bios ?
Thanks !
Click to expand...
Click to collapse
You have to connect it to the PC, but possibly you can not do much with the blocked bootloader.
PD: To put the tablet in fastboot mode press VOL - and POWER. To know if it is in FastBoot mode, there will be an image of an Android.
Instructions
1. Download the ADB / FastBoot Tool (https://developer.android.com/studio/releases/platform-tools#downloads)
2. Unzip it next to the backup files
3. Opens a cmd and introduce the following commands:
fastboot flash super super.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot -w
fastboot continue
Click to expand...
Click to collapse
4. Done.
------------------------------------------
By the way you guys, I tried to introduce the ROM from the Q-Link Scepter 8 tablet at the T8100. But without success, Phoenix (Pro and Suit) is blocked and not flash. Even though the motherboard were similar. A pity, it would have been fine to join communities.
the tablet is connected but not recognised. do i have to install the tablet drives on the pc ?
TiagoG3400 said:
the tablet is connected but not recognised. do i have to install the tablet drives on the pc ?
Click to expand...
Click to collapse
In my case, I have not had a problem of drivers. But use the Google driver "Adb Bootloader Interface"
Sorry for the trouble I'm giving you, but I'm having a lot of trouble with this tablet.
now i have the drives but i have this error ...
after running the command in cmd, the tablet restarts but still has the same problem
TiagoG3400 said:
Sorry for the trouble I'm giving you, but I'm having a lot of trouble with this tablet.
now i have the drives but i have this error ...
after running the command in cmd, the tablet restarts but still has the same problem
Click to expand...
Click to collapse
It happens because you have the blocked bootloader. Try to put the next command, although I do not think it works when not previously activated in settings:
fastboot oem unlock
Click to expand...
Click to collapse
it doesn't work, if i can unlock the bootloader can i reinstall the system on the tablet to make it functional ?
Must be tricky to do that
TiagoG3400 said:
it doesn't work, if i can unlock the bootloader can i reinstall the system on the tablet to make it functional ?
Must be tricky to do that
Click to expand...
Click to collapse
Yes, if you can unlock the bootloader. You can use that dump, to fix the tablet
TiagoG3400 said:
it doesn't work, if i can unlock the bootloader can i reinstall the system on the tablet to make it functional ?
Must be tricky to do that
Click to expand...
Click to collapse
Hi Tiago, did you find what you looking for to unlock the bootloader for this tablet?
Many thanks in advance
SamuEDL said:
Good guys, I leave the boot.img for Tablet T8100 and patched with Magisk. Works correctly on the Rom Stock (Android 10 GO) on tablet T8100 with motherboard BND-A863-CV2.0.
View attachment 5547199
As a curiosity, I am currently using GSI Roms on my tablet. The problem is that Roms based on Android 11 and 12, the Gyro Sensor does not work. On Android 10, if it works
View attachment 5547205
Edit: I attached also the dump of the Rom Stock of my Tablet, in case someone needs it. https://www.mediafire.com/file/h0hnqhwah2qyf7y/RomStockT8100.zip/file
Only can be flashed by fastboot as a dump and only if you have an unlock bootloader.
Click to expand...
Click to collapse
Can you provide a gsi rom, or link to it that works on this device?
thank you
Related
hello to all...i am new to this developing. i have a rom file in .zip format....inside it there is system folder. i want to convert this .zip into a system img file. is it possible?? actually i hav a phone on which sdcard is not getting detected. so cwm recovery wont work, niether adb is detecting that device, so i want to make a system img file from this rom so that i can flash it using fastboot. Plz help me
niranjand147 said:
hello to all...i am new to this developing. i have a rom file in .zip format....inside it there is system folder. i want to convert this .zip into a system img file. is it possible?? actually i hav a phone on which sdcard is not getting detected. so cwm recovery wont work, niether adb is detecting that device, so i want to make a system img file from this rom so that i can flash it using fastboot. Plz help me
Click to expand...
Click to collapse
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
bill.weckel said:
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
Click to expand...
Click to collapse
i am trying it for huawei u8180
shinobisoft said:
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
Click to expand...
Click to collapse
I tried this using Livesuit 1.11 for a softwinerEvb a13 tablet (no other known device specs) and it said the image file was invalid. Situation is I soft bricked my tablet by flashing the wrong cwm zip. Finally found out how to connect via Livesuit (kinda like fastboot or bootloader mode or something? like Odin?) to flash stuff to it. I decided to use an erase img .img because where I found how to connect it suggested that to the OP (on techknow). So now instead of the tablet just being stuck on the first screen when trying to boot (normal or recovery), it doesn't do anything at all since there's no boot.img. Which I'm not worried about since It connects to my laptop just fine via livesuit still so I can get a boot on it (ADB won't detect it - pretty positive it's not ADB user error [I run cmd "adb root" when the tablet is connect in whatever mode its in - the way livesuit detects it - and adb says no device found]. BUT I can't find a stock firmware/rom/boot.img for it anywhere (mainly since there's a bunch of clones of this tablet). I'm downloading a few roms (in boot.img format? - .7z files) that I found for "this" tablet (meaning the devs don't know which clones which roms work on lol).
ANYWAY haha, my question is, is there a way to do what you said in the above quote that will work in my situation? I'm not advanced enough to know why livesuit says the image is invalid. I tried it with a cm10.1 zip made for this tablet and a cwm zip made for this tablet (for both I extracted the files and then tried flashing the boot.img I found in the directory(extracted folder right?) via livesuit. livesuit said image file invalid for both .img's.
Please help me and THANK YOU in advance.
I'm open to anyone's help and any help is much appreciated! Thanks buttons will be pressed!!!
Same situation
Same Situation but I know the Specs,, It is allwinner A10 .and Stuck in the soft brick
could you solved this problem? i need a help too, the same problem
---------- Post added at 09:21 PM ---------- Previous post was at 09:13 PM ----------
vennkis said:
Same Situation but I know the Specs,, It is allwinner A10 .and Stuck in the soft brick
Click to expand...
Click to collapse
Hi, could you solved that?
i have a Chinese tablet a10, i have repaired different tablets and android phone trough ADB, but this devices is not detected, i have download some software to help me download the tablet drivers, but hasn't possible that.
finally the only source i have, is charge the firmware again, i use phoenix , and i have some rooms in zip format, what can i do for convert to IMG format?
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
how to convert?
m.morcielago said:
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
Click to expand...
Click to collapse
m.morcielago said:
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
Click to expand...
Click to collapse
hahaha...no answer....i am still waiting for this software
doelwit.sunny said:
hahaha...no answer....i am still waiting for this software
Click to expand...
Click to collapse
You know just converting is not enough
I can convert it
But you need "partition table" for making .IMG
So we don't have it
check sdat2img and imgpatchtools
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Chegger said:
Same thing happened to me!
Thank you in advance.
Please let me know if you found the solution.
Click to expand...
Click to collapse
Not the solution, but maybe a cause... did you root your device?
harddisk_wp said:
Hello all,
yesterday's OTA firmware update to my CAT B15Q (CPU MediaTek MT6582M) showed an error similar to "failed to update metadata symlink" and offered me to reboot... since then the device is stuck in a bootloop and only boots recovery and fastboot.
The recovery console doesn't offer any USB devices, except when choosing "apply update from ADB", upon which adb devices lists it as "0123456789ABCDEF sideload". adb shell however does not work, it gives an "error: closed" message.
Resetting to factory did not help either, current Android version of the device was 4.4.2.
By the looks, the failed update bricked the /system somehow; can I sideload a version of adb onto the recovery to gain shell access?
Thanks!
Click to expand...
Click to collapse
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
harddisk_wp said:
Not the solution, but maybe a cause... did you root your device?
Click to expand...
Click to collapse
Yes I did.
I also thought that was the problem.
delox88 said:
Hey my little brother just had the same problem but I managed to get the fone to boot took the battery out held Down volume down and 3 mins later it booted
Click to expand...
Click to collapse
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Chegger said:
Can you elaborate?
Do you hold before and while turning on?
Did you hold with the battery Out with charger?
I tried to hold while booting but it just stays in the inicial image forever.
Thanks.
Click to expand...
Click to collapse
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
harddisk_wp said:
Ha, same for me. Even adb comes halfway up (adb device shows up in windows' device manager, but "unauthorized", so no shell/pull/push), but it doesn't progress beyond the loading image.
Can anyone with a working B15Q please execute the command "cat /proc/mtd" in a shell or do a full(!) backup using mtkdroidtool?! I pledge €20 via Paypal to the first one who submits all of the partitions except /data up to Mega or another OCH.
Click to expand...
Click to collapse
At least you know this stuff that's half way trough.
I will post this in the original root thread since I already posted the issue there and they are now replying ( I will mention you).
http://forum.xda-developers.com/general/rooting-roms/root-achieved-cat-b15q-t2822015/page11
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
bigal1337 said:
My phone bricked after updating to 1.1019.000
I was lucky enough to save the whole ROM to a file before updating.
The problem for me was the original recovery.
My solution was to install the new 1.1019.000 recovery on my original ROM and then updated to the new (1.1019.000) firmware.
Give me your mail and i will send you the 1.1019.000 recovery. I have the whole ROM but it´s to large and i am to lazy to upload
Click to expand...
Click to collapse
I've witten you a PM - please send me your original ROM - or could you send me a link where i may download it.
huedlrick said:
I've the same problem - b15q is bricked - device was rooted to be able to use link2sd.
Click to expand...
Click to collapse
Another one here! Were you able to use link2sd after rooting the phone? Link2sd gave me a mount error when I tried to mount my sd card's 2nd ext3 partition.
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile
1.1019.000 Recovery
Original 1.1019.000 update
Scatter file
To flash the phone you only need the bootimg, recovery,android and scatterfile.
(Edit: I dont have google drive anymore)
bigal1337 said:
Many ppl wanted the stock rom. So i uploaded it to my google drive. It´s a E01 so beware those of you who has B01 or something else.
Original 1.1010.000 rom in files with scatterfile https : // drive . google . com /file/d/0ByVAMsMZdC8bdEIxWlpBeXBHNUE/view?usp=sharing
1.1019.000 Recovery https : // drive . google . com /file/d/0ByVAMsMZdC8bVXU2RzBGalV0S1U/view?usp=sharing
Original 1.1019.000 update https : // drive . google . com /file/d/0ByVAMsMZdC8bbWQ4dmhSZWVxZVE/view?usp=sharing
Scatter file https : // drive . google . com /file/d/0ByVAMsMZdC8bSkRhREEwakNhUWc/view?usp=sharing
To flash the phone you only need the bootimg, recovery,android and scatterfile.
Click to expand...
Click to collapse
Thank you very much - but how can I determine if my phone is E01/B01 without being able to boot it?
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Great and congrats.
Could you, please, describe the process and which files did you use.
Thanks.
harddisk_wp said:
So, I can confirm that reflashing your ANDROID/RECOVERY/BOOTIMG unbricked my European B15Q!
Click to expand...
Click to collapse
Can you give some hints how you unbricked it? What tools and commands have to be entered?
Best regards,
Doggy77
Uploads are not done yet. But you can prepare until I'm done... grab the driver package, spFlashTool and the 1.022 RAR from http://forum.xda-developers.com/general/general/stock-rom-cat-b15q-rom-development-t2988774.
You will need a win7 x86 machine for this to work (64-bit systems will need to disable the driver signature enforcement, but this is unreliable), and latest(!) WinRAR for unpacking.
The full backup of your device will take up ~1.5 GB, so you will need at least 3GB free and another 2GB if you also want to backup your userdata (HIGHLY RECOMMENDED).
"PMT changed for the ROM; it must be downloaded"
I'm trying to flash the files of harddisk_wp with his instructions but i keep getting the error "PMT changed for the ROM; it must be downloaded", right after I connect the phone and SP Flash Tool finishes "Download DA". I am trying with the 64bit drivers since I do not have a 32bit system, with digital signature verification disabled.
After some search, I saw in the log files that SP Flash Tool is reading the partition table on the phone and comparing it to the scatter file. There is a mismatch there and throws this exception. Now either the driver is not working correct and does not report the partition table right or there is something else going on. Anybody tried this on a 64bit system? Any ideas?
BTW the scatter file is correct for my phone. I had downloaded it myself also before the bricking and I compared it with harddisk_wp's one. They are identical.
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
walckenaerius said:
In all other aspects SP Flash Tool works fine, I read the user partition for backup without problems.
Click to expand...
Click to collapse
SPFT worked for me good to resurrect the phone with files from 1010 version (first firmware) raw partitions.
Phone came back to last user backup and booted fine.
I applied newer and suggested 1019 update that had bricked the phone even further into the loop of the booting logo stuck and rebooting.
SPFT tool memory scan showed that there is no NAND present. I assume that there is PRELOADER damaged. By trying to flush raw PRELOADER that was a no go area. Connection made red line on 100% and nothing happens after that.
SPFT stopped making connection via USB. Inserting the battery, power on - it didn't came back at all.
Phone is now dead black brick that on Linux shows: as MediaTek Inc. MT6227 phone.
In any case do not try to make the same mistake like me.
I will check if it works on some other Windows machine.
Not being Windows user I cannot tell if it is in USB driver or not.
Used W7 without admin pass, with MTKUsbAll driver.
Eh.
Hi everybody!
On our 4pda.ru forum we are struggling with this phone in two ways- rootin it and unlocking in order to update manually to 2.0 and even 2.2; and other way- working android (already have beta rom which is exact copy of rom from another alcatel 6014x which runs android and similar to our Fire E 6015x).
if there are any enthusiasts about android, i can translate the guide for you and share the needed files and programs. Almost everything works except sim-card(when there is no one- phone asks to insert it, when there is one- phone says its not registered) but we are working on it
i came over a https://www.soeren-hentzschel.at/mo...ch-verteilt-firefox-os-2-0-und-firefox-hello/ that states that in Germany some people already received 2.0 update on their Fire E. Here arises my question- are here people who own updated Fire E? I mean update to 2.0.
If there are ones, would you be so kind to make a copy of your rom for our little development? I can provide you with guides and software on how to do it.
I can post guides for making this an android phone.
Hi my dear russian brother - greetings from Germany.
I do have an updated 6015x device to FFOS2.0 and I could dump the rom for U. Just gimme links to the needed info. My russian is not one of my strength, but I think I can manage it - I'm a bulgarian after all.
hej, i also have a 6015X (fire e) with firefox os 2.0 running
tell me how to make a rom which i can send to you
root
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
cybervitexud said:
After few months of waiting my phone get the forefoxos2.0 update
01008d yes it is fine but how to root it?
Click to expand...
Click to collapse
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
dermartinac said:
Alcatel's stock ROM for the Fire E has been published at sourceforge.net in the Alcatel project.
Click to expand...
Click to collapse
I wonder how do you use it though, can you build it on its own? The B2G by Mozilla still hasn't got an option for this device.
Svinka said:
Look, please, do you have in System settings parameters of russian language on your FFOS 2.0.
HOWTO ROOT ALCATEL OT 6015X:
1. Download CWM recovery image made for 6014x.
https:// yadi.sk/d/BIdXndcbfR2Gm
2. Download Install-SuperSU.
download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
3. Turn your phone to bootloader mode anyway.
4. Run modrecovery:
Code:
fastboot boot my_recovery.img
5. In CWM menu follow "install zip" -> "install zip from sideload"
6. On pc:
Code:
adb sideload UPDATE-SuperSU-v2.46.zip
7. reboot phone
I am sure lowlevel utilities from android's SuperSU are working fine on any FFOS (because FFOS based on Android now).
WBR
Click to expand...
Click to collapse
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
sybiam said:
I tried your recovery image but it doesn't seem to work. There is no error but after booting the image, the device isn't visible in fastboot or adb. For that reason, I'm unable to sideload the Su zip update.
Click to expand...
Click to collapse
Flashing the recovery image works though, then sideloading the SU image works from clock work mode recovery.
Ok, here's some news. I built a boot image that enables adb as root. All you need is to flash it on the boot partition and reboot the phone. I made a few changes to the boot image.
default.prop
Code:
ro.secure = 0
ro.debuggable = 1
To flash:
Code:
fastboot flash boot boot3.img
and replaced /sbin/adbd by an adbd built with "ALLOW_ADBD_ROOT". (I used the sources fetched using b2g repo).
Cool thing..wish I am able
Sent from my SM-G7102 using XDA Free mobile app
Hi. Update firefox os 3.0?
lirondeespaña said:
Hi. Update firefox os 3.0?
Click to expand...
Click to collapse
As far as i know even Firefox OS 2.2 is not officially released yet.
There are only pre Versions.
Has anybody else troubles with FFOS 2.0 on the Alcatel Fire E?
The phone sometimes hangs completely while it was sleeping. (Can´t wake up or even call the phone)
Only if i press the start button for some seconds the phone starts again.
I hope someone builds a FFOS 2.2 Rom for the Fire E --> Copy and paste :good:
How can I switch this piece of **** called smartphone to bootloader mode?
Softbricked 6015x
Hey guys,
I got stuck with creating the boot.img and figured out that the backed up one doesn't work.
Does anybody have a working boot.img for the 6015x, NOT the 6014x?
I tried also getting the venezuelian one, but those TLDs are not reachable anymore - all gone.
The custom boot images from the russian 4pda forum are also not working.
I currently have only access to ADB, the TWRP recovery mod (temporarily) and fastboot, so I need a fastboot working image.
The Mobile Upgrade Q / TCL Updater / QDST distribution updater is Windows only - and crawling the binaries for URLs is a dead-end. The tool also requires
a fully booted OS, so it's pretty much the dumbest update tool out there and not practical to use. As I don't have Windows, the imgc files for the eMMC flashing tool are also a dead-end.
I really need only the boot.img file.
I really need only the boot.img file.
Click to expand...
Click to collapse
Did you try my boot img?
sybiam said:
Did you try my boot img?
Click to expand...
Click to collapse
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
cmartensms said:
Yes, my device constantly reboots and fails to initialize the display (seems like an Xorg alike error to me) when trying to figure out what logcat shows.
Due to the constant reboots I can't debug it using adb, because of constantly lost connections. That's why I'm asking for an OEM boot.img file.
I started to collect the working stuff over at github.com/martensms/alcatel-6015x (cant post links -_-)
Click to expand...
Click to collapse
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
sybiam said:
Did you try to boot with fastboot or did you flash it to the boot partition. I had no success booting with fastboot but flashing works. That said, you have to install a custom recovery image.
Also, I'm working on building FFOS from sources but as won't be home for a month, it's kind of slow.
Click to expand...
Click to collapse
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
cmartensms said:
Both. Didn't work. As I said, I have no functioning boot image available. All boot images, from everywhere including your one, don't work.
I don't know what's so hard to understand. NO custom boot.img works. Seriously. None. Simple as that. I tried 9 different boot.img out, I even tried extracting the eMMC boot.img which obviously failed.
Again, third time, I just need an OEM boot.img in order to get further debugging my device because I can't debug my device in 3 second disconnect intervals from ADB.
edit: I unbricked my device now and made backup images of all OEM partitions - github.com/martensms/alcatel-6015x
Click to expand...
Click to collapse
That's weird, my custom boot works on my own phone. 6015x, it's a russian phone. Firmware revision: 01005, hardware revision 01, platform version: 28. Firefox OS 1.3.0.0 .
I guess, if you had a newer version of Firefox, there could be something wrong with the boot image.
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Try this
Planet Indigo said:
Has anyone here rooted this tablet with Magisk?
Any very detailed step by step guide somewhere with links to the specific files to download for this tablet? (It'd be great if it didnt't require a PC but even if it does, I'd really appreciate a detailed step by step guide to put Magisk on this tablet)
Thanks
Click to expand...
Click to collapse
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
KIBS2173 said:
Hi there,
I wouldnt't use Magisk on your device as it might softbrick your drive
So use KINGOROOT.
THE STEPS ARE VERY EASY TO FOLLOW.
https://www.kingoapp.com/
Regards,
KIBS2173
Click to expand...
Click to collapse
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Planet Indigo said:
Why would Magisk be more risky than Kingoroot on this device? I liked the idea of Magisk because it is systemless root and it is easier to hide from some apps.
Can Kingoroot one click root apk even root a Teclast M16 running android 8?
Click to expand...
Click to collapse
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Karamarov1 said:
For M16, there is no root at all yet. I look forward to it myself, but so far there is nothing ....
Click to expand...
Click to collapse
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
KIBS2173 said:
Hi there,
I tried Magisk on a chinese phone, and after flashing the software, the phone just went into black screen and soft-bricking the whole phone, the phone works in the background but the screen is black. And KINGOROOT will not flash anything into your device.
Regards
KIBS2173
Click to expand...
Click to collapse
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Try this
Planet Indigo said:
So you have the tablet yourself and no luck with anything?
I can't seem to find anything on the net about rooting this tablet, it's weird too since it "only" has android 8, not the latest android versions. I sure hope Magisk or another root method is going to be developed soon because I'm really interested in that tablet model.
I heard from another forum user who has the Teclast M16 and he said that Kingoroot didn't work on it.
Click to expand...
Click to collapse
Hi there,
So i was researching more about this tablet, turns out you can root by installing a custom recovery (TWRP) and from there you can install SUPERSU to achieve root for your tablet. I am not sure if this method works, but if your able to get the stock firmware and the stock recovery and the software to flash the firmware i think you might as well go ahead using that method.
THIS IS THE ARTICLE I FOUND ONLINE :
https://www.getdroidtips.com/how-to-install-twrp-recovery-on-teclast-t30-and-root-it-easily/
*MAKE SURE YOU FIND OUT IF THIS TABLET HAS A TWRP RECOVERY BEFORE DOING ANYTHING ELSE*
Thank you for looking into it, unfortunately that guide is for the Teclast T30 and the guy advises to only use it for that model. I don't own that tablet yet so I can't try any of the steps myself but I'm very interested in this particular model (16/9 ratio, hdmi out, dc charger in, etc...) so I was really hoping to find a tested working method to root it before I go ahead and purchase it.
i found this: https://www.getdroidtips.com/root-teclast-m16/
I rooted my Teclast M16 using Magisk. Simply unlocked the bootloader through adb/fastboot commands, then have magisk manager patch the boot image from firmware download and then flash it using adb/fastboot command line fastboot flash boot magisk_patched_boot.img reboot system and its rooted.
I haven't found a twrp recovery yet, but I'm thinking about trying my hand at building my own, despite being a noob.
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Hi. Have you got you on working twrp recoberto?
fdsafggg said:
I can confirm
install adb fast boot
Enable USB debugging and OEM Unlock on your Android device.
adb reboot bootloader
fastboot flashing unlock
Volume up
fastboot reboot
Wait a few minutes to reinstall
enable usb debugging again
download firmware
you will finde a google spreadsheet on the facebook page of telcast
Copy boot.img on the device
install magisk manager via apk
install magisk via patch boot.img in download folder
download patched boot.img
patch device
adb reboot-bootloader
fastboot flash boot magisk_patched_boot.img
fastboot reboot
M16(M6P2)_Android 8.0_V1.07_SZ
boot.img httpx://mirr.re/d/2wHd
full httpx://mirrorace.com/m/1Ek3z httpx://mirr.re/d/2wHj
Click to expand...
Click to collapse
Hi.
I tried to unlock the bootloader .
adb devices command shows the m16.
I send the command "adb reboot bootloader" - the device enter in bootloader.
next I send the command "fastboot devices" and I get this:
PS E:\modified_fastboot> fastboot devices
???????????? fastboot
any help to make fast boot see the device?
Thank you
dcoelho said:
Cześć.
Próbowałem odblokować bootloader.
Polecenie urządzeń adb pokazuje m16.
Wysyłam polecenie "adb reboot bootloader" - urządzenie wchodzi w bootloader.
następnie wysyłam polecenie „urządzenia fastboot” i otrzymuję to:
PS E:\modified_fastboot> urządzenia fastboot
???????????? szybki start
jakakolwiek pomoc, aby szybki rozruch zobaczył urządzenie?
Dziękuję Ci
Click to expand...
Click to collapse
Hi, You bad comand when bootloader. When bootloader after comand: " fastboot oem unlock" , luck on skreen, push volume up, wait moment, after next comand:"fastboot reboot". After this command, the tablet will reset to factory settings with unlocked bootloader.
Hello everyone. I have TWRP for M16, everything is almost fine, after uploading it normally work on M16, except for touch not working, I did not check if it works with the mouse. Maybe someone will find it to correct it so that the touch works? I upload the file, it may be useful to someone. Regards RW
reupload boot.img
Received the tablet in the mail, and now looking to root via Magisk (and ideally a custom recovery like TWRP).
I found this video describing a way to download the stock ROM from Teclast:
Has anyone achieved root on this device? Can anyone confirm Treble ROM compatability for GSI A/B?
On the russian forum 4pda somebody posted the patched boot.img and vbmeta.img files required for rooting.
If anyone is registered on the forum he might try to grab the files, for me it gives 404 error when trying to download, though im not registered..
Teclast T40 Plus - Обсуждение - 4PDA
Teclast T40 Plus - Обсуждение, Планшет, 10,4
4pda.to
NightLord said:
On the russian forum 4pda somebody posted the patched boot.img and vbmeta.img files required for rooting.
If anyone is registered on the forum he might try to grab the files, for me it gives 404 error when trying to download, though im not registered..
Teclast T40 Plus - Обсуждение - 4PDA
Teclast T40 Plus - Обсуждение, Планшет, 10,4
4pda.to
Click to expand...
Click to collapse
Good find, but the link no longer works. It gives me a 404: https://4pda.to/forum/dl/post/24458874/T40_Plus_root.7z
My guess is it would work if we were logged in, its just that i cant create an account since i cannot get past rhe russian captcha
Yeah, I also can't register without knowing the Russian keyboard layout and how to identify the characters. Perhaps someone with this knowledge can register and attach the required images to root here?
Slightly off topic while someone manages to grab the files from 4pda
Do you actually get 50000+ gpu score in antutu with the t40? I have the maxpad i11 which is in theory the same hardware, and I only get 42000. I even flashed the t40 firmware on the device, but gpu score didnt budge.
To be on topic: if you want root, you may also flash phhuson's treble GSI rom-s. I tried his version of android 12, and it works, and has root.
NightLord said:
Slightly off topic while someone manages to grab the files from 4pda
Do you actually get 50000+ gpu score in antutu with the t40? I have the maxpad i11 which is in theory the same hardware, and I only get 42000. I even flashed the t40 firmware on the device, but gpu score didnt budge.
To be on topic: if you want root, you may also flash phhuson's treble GSI rom-s. I tried his version of android 12, and it works, and has root.
Click to expand...
Click to collapse
These ROMs? https://github.com/phhusson/treble_experimentations/releases
ForgottenSolstace said:
These ROMs? https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Yes.
You can either install them via DSU as dual-boot OS beside your stock rom, or just flash system partition (inside super) via fastbootd (you are going to have to delete product partition to have enough space inside super for the system image) and use them as primary OS.
Gotcha:
Just ordered a T40 Plus, did you manage to get root?
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
NightLord said:
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
Click to expand...
Click to collapse
Hi NightLord, can you explain easily the root steps for this device? do we need the software that we see in the video at the beginning or is ADB enough?
Marynboy78 said:
Hi NightLord, can you explain easily the root steps for this device? do we need the software that we see in the video at the beginning or is ADB enough?
Click to expand...
Click to collapse
Hey,
You need to use the spreadtrum research download tool (RDT), not the one seen in tthe video in the first post.
See this guide on how to use the RDT.
The basic concept is that you need to download the official firmware from the teclast homepage, load it into RDT, uncheck all partitions (save for those that are compulsory and cannot be unchecked), select only boot and vbmeta partitions, and as images to be flashed you need to browse the ones found in the archive I posted, instead of those found in the original firmware package.
Begin flashing, your device will perform a hard reset, and then you should boot into rooted firmware.
Theoretically you should be able to flash both partitions (boot and vbmeta) via fastboot too, but when I tried, i got an error message saying boot.img was too large or something. Flashing via RDT went without problem. The only caveat is that flashing via RDT will always hard reset your device.
NightLord said:
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
Click to expand...
Click to collapse
How to install android 12 gsi on this device?
marinzrncic said:
How to install android 12 gsi on this device?
Click to expand...
Click to collapse
First you need to unlock the bootloader. You need to be patient when you are flashing the unlock, my device took some 10 mins to complete, but in the end it succeeded (on the 2nd try, mind you.)
Here is a guide for unlocking in windows, though it is in russian (Im attaching the required modified fastboot in case you cannot download it from 4pda).
When you're done unlocking the bootloader, you've already done the hard part.
Next, download your preferred GSI image from Google, from phhusson's, or whatever else you find (Pixel Experience for eg.). Mind you, that the image from Google contains the Android 12L version.
Next you will flash your active system partition with the GSI image. To do that, initate ADB connection to your tablet, then enter fastbootd, by issuing the command:
fastboot reboot fastboot
you can check your active system slot by:
fastboot getvar all (but it will be slot "a" unless you have received an OTA update previously)
you need to free up some space by deleting the logical partition product otherwise you wont be able to flash your gsi:
fastboot delete-logical-partition product_a
(in case your active slot is "a")
then you can move forward to actually flashing your GSI:
fastboot flash system_a whateverisyourimagefilename.img
Lastly, you will need to wipe userdata, which can be done on the tablet by switching to recovery from fastbootd, and then selecting wipe userdata, or maybe the fastboot -w command does the same.
Reboot, and enjoy your GSI.
I'm using the Google 12L GSI, and it is perfectly stable for daily usage. For bluetooth audio to work, you will have to disable bluetooth a2dp hardware offload in developer options.
NightLord said:
First you need to unlock the bootloader. You need to be patient when you are flashing the unlock, my device took some 10 mins to complete, but in the end it succeeded (on the 2nd try, mind you.)
Here is a guide for unlocking in windows, though it is in russian (Im attaching the required modified fastboot in case you cannot download it from 4pda).
When you're done unlocking the bootloader, you've already done the hard part.
Next, download your preferred GSI image from Google, from phhusson's, or whatever else you find (Pixel Experience for eg.). Mind you, that the image from Google contains the Android 12L version.
Next you will flash your active system partition with the GSI image. To do that, initate ADB connection to your tablet, then enter fastbootd, by issuing the command:
fastboot reboot fastboot
you can check your active system slot by:
fastboot getvar all (but it will be slot "a" unless you have received an OTA update previously)
you need to free up some space by deleting the logical partition product otherwise you wont be able to flash your gsi:
fastboot delete-logical-partition product_a
(in case your active slot is "a")
then you can move forward to actually flashing your GSI:
fastboot flash system_a whateverisyourimagefilename.img
Lastly, you will need to wipe userdata, which can be done on the tablet by switching to recovery from fastbootd, and then selecting wipe userdata, or maybe the fastboot -w command does the same.
Reboot, and enjoy your GSI.
I'm using the Google 12L GSI, and it is perfectly stable for daily usage. For bluetooth audio to work, you will have to disable bluetooth a2dp hardware offload in developer options.
Click to expand...
Click to collapse
thank you very much
NightLord said:
Hey,
You need to use the spreadtrum research download tool (RDT), not the one seen in tthe video in the first post.
See this guide on how to use the RDT.
The basic concept is that you need to download the official firmware from the teclast homepage, load it into RDT, uncheck all partitions (save for those that are compulsory and cannot be unchecked), select only boot and vbmeta partitions, and as images to be flashed you need to browse the ones found in the archive I posted, instead of those found in the original firmware package.
Begin flashing, your device will perform a hard reset, and then you should boot into rooted firmware.
Click to expand...
Click to collapse
Did we need unlock bootloader first or we can flash root without unlock bootloader?
Thx
ardianz said:
Did we need unlock bootloader first or we can flash root without unlock bootloader?
Thx
Click to expand...
Click to collapse
I have no idea because I havent tried yet. But I would guess it might be possible that you can flash the patched boot.img along with vbmeta.img with RDT, and it might work, if they do pass Android Verified Boot check.
NightLord said:
Gotcha:
Click to expand...
Click to collapse
will these files work on android 10 or android 11? I have a unisoc T618 and unisoc T310. I was hoping to flash both tablets to get root access.
and also do you have a twrp for T40_plus or any unisoc generic twrp?