Greetings everyone, I have a China tablet that I got from Amazon and was wondering if anyone could guide me in rooting the unit.
These are the details I was able to get through CPU-Z, I apologize ahead of time as I'm just typing up this information from what I'm seeing.
Manufacturer: jlinksz
Model: TK-E101GC
Brand: TK-E101GC
Board: TK-E101GC
Hardware: MT6580
GPU: Mali-400 MP
SoC: Mediatek MT6580
revision: r0p3
Doing a quick search in the forums has led me to jlinksz Beista 10.1 [MT6580] K107/K960 root TWRP. Bit I'm unsure if this is applicable to my unit. I was hoping I could find a kind soul to guide me in this journey that I have. Thank you in advance.
Hi all, I was able to find the following:
1. AndroidUrdu
2.cyanogenmods
Anyone able to confirm if any of these are good sources?
Hi, I got this tablet too. Same model TK-E101GC, same chipset MT6580.
I tried the method you put, but when it comes the time I have to scatter the memory, it shows 0, so I think the software doesn't accept this very precise chipset.... I didn'd find nything else related, so the only thing we can do i to find some scatter file on the web and use it to patch and root the boot.img
Hi, I post again if somebody can help with this matter. Thank you.
MTK devices typically gets rooted with MTK Droid Tool
DL: http://www.mediafire.com/file/miqmy69ogpqrar6/Mtk_Droid_Tool_v2.5.3.zip/file
Thank you @jwoegerbauer but i'm afraid MTK Droid Tool doesn't recognise this specific MTK chipset. It is the MT6580 and when you try to pair the tablet within MTK Droid Tools, it shows this message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I can't create scatter.txt for this tablet. I've found some TWRP unofficial recovery for this MT6580 chipset and Kernel 3.18.35+ (which is the kernel of the device). Do you know if i can flash this recovery without corrupting anyting? Thank you so much.
Sillyw4lks said:
Thank you @jwoegerbauer but i'm afraid MTK Droid Tool doesn't recognise this specific MTK chipset. It is the MT6580 and when you try to pair the tablet within MTK Droid Tools, it shows this message:
So I can't create scatter.txt for this tablet. I've found some TWRP unofficial recovery for this MT6580 chipset and Kernel 3.18.35+ (which is the kernel of the device). Do you know if i can flash this recovery without corrupting anyting? Thank you so much.
Click to expand...
Click to collapse
I can see on your printscreen that you are on android 7. You should give a try to kingoroot.
Sillyw4lks said:
Thank you @jwoegerbauer but i'm afraid MTK Droid Tool doesn't recognise this specific MTK chipset. It is the MT6580 and when you try to pair the tablet within MTK Droid Tools, it shows this message:
So I can't create scatter.txt for this tablet. I've found some TWRP unofficial recovery for this MT6580 chipset and Kernel 3.18.35+ (which is the kernel of the device). Do you know if i can flash this recovery without corrupting anyting? Thank you so much.
Click to expand...
Click to collapse
Never heard that MTK Droid Tool is restricted to specific MTK chipsets. FYI: MTK Droid Tool is developed by MediaTek Inc
Never flashed TWRP on any device, and this for good reason. If I had to flash a Custom ROM then I just booted the device into TWRP.
Sichroteph said:
I can see on your printscreen that you are on android 7. You should give a try to kingoroot.
Click to expand...
Click to collapse
It's weird, because Kingoroot says it is rooted but another apps like Root Checker says it doesn't.
I'm going to update you with this adventure, and see if somebody can help with this matter:
I think i've broken the Recovery System trying to flash an internet Recovery with the same chipset, thus the device was bootloop trapped in the Recovery System. First I thought I had a cheap chinese brick, but then I thought to drain all the battery a few days and see what happens if I try to boot again. Magic happened. It booted in Android like nothing happened, so now I've got chinese device without recovery.
If someone has this exact device - Jlinkz TK-E101GC - would be very nice to share a Recovery partition, or even a full clone of the device. Thank you.
Amazing Temp Root for MediaTek works in MT6580 too...
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
CXZa said:
Amazing Temp Root for MediaTek works in MT6580 too...
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Click to expand...
Click to collapse
Thank you for your help, but I can read there is some trouble with dm-verify with Android 6.0+ devices. Mine is 7.0. Thank you anyways.
Sillyw4lks said:
Thank you for your help, but I can read there is some trouble with dm-verify with Android 6.0+ devices. Mine is 7.0. Thank you anyways.
Click to expand...
Click to collapse
Well it allows you use Magisk and patch that boot...
Jlinkz's tablets can be a bit weird... faked ect. but their ftp server
has some firmwares that recovery might work in your device.
ftp://BMXC:[email protected]
CXZa said:
Well it allows you use Magisk and patch that boot...
Jlinkz's tablets can be a bit weird... faked ect. but their ftp server
has some firmwares that recovery might work in your device.
ftp://BMXC:[email protected]
Click to expand...
Click to collapse
Oh! Thank you so much! I will update if I can figure out something.
@Sillyw4lks
Also if you have recovery-from-boot.p file in the system folder,
you should be able to fix that recovery. Actually it should fix itself
during the boot. Unless that TWRP has disabled it - or Jlinkz...
CXZa said:
@Sillyw4lks
Also if you have recovery-from-boot.p file in the system folder,
you should be able to fix that recovery. Actually it should fix itself
during the boot. Unless that TWRP has disabled it - or Jlinkz...
Click to expand...
Click to collapse
I'm going to check if I have that file. You're helping me a lot! So grateful.
Edit: Found it! So, You say it should recover itself when the device reboots? I'm gonna try to enter the recovery system. If doesn't show up and loops trying to enter again, I will have to wait until the battery drains again so I can enter to the ROM again. But knowing this I have backdoor if I mess up too much.
Edit2: I have access again to Recovery. I know I sound cheesy, but thank again. Now I can start from scratch.
Sillyw4lks said:
I'm going to check if I have that file. You're helping me a lot! So grateful.
Edit: Found it! So, You say it should recover itself when the device reboots? I'm gonna try to enter the recovery system. If doesn't show up and loops trying to enter again, I will have to wait until the battery drains again so I can enter to the ROM again. But knowing this I have backdoor if I mess up too much.
Edit2: I have access again to Recovery. I know I sound cheesy, but thank again. Now I can start from scratch.
Click to expand...
Click to collapse
Hello, I have the same tablet as you, and I'm facing the same problems. Did you get any progress?
Sorry I didn't respond, I ended up disposing the tablet.
xerrrman said:
Hello, I have the same tablet as you, and I'm facing the same problems. Did you get any progress?
Click to expand...
Click to collapse
No. I fashed some random image i found on internet but I don't know how it killed the fastboot. Anyway I can run the stock rom w/o any problem. I just decided to surrender. I hope you success.
Does your tablet run snappy and fast? Mine doesn't. The hardware is not so bad, so it should run faster, I guess.
I used adb to uninstall bloatware and I ended removing all the mediatek and google apps as well and then the tablet runs a bit better, but it's still not fast or responsible.
Do you have any advice about how to make it run faster and better?
It works laggy, that's why I wanted to root it and flash a new rom. I don't use it. Is just not worth spend energy into that piece of trash. I hope you have better luck.
Related
Hi everyone, I have a Blackview bv6000 device with android 6.0, firmware BV6000_blackview_V01_20160608
I have already unlocked the bootloader and i would like to unlock the root but i don't know how do it. Can someone help me?
Another thing, i have unlock the System UI Tuner but it doesn't appere in my settings menu, any idea to solve it?
Regards, Marco
traneXD said:
Hi everyone, I have a Blackview bv6000 device with android 6.0, firmware BV6000_blackview_V01_20160608
I have already unlocked the bootloader and i would like to unlock the root but i don't know how do it. Can someone help me?
Another thing, i have unlock the System UI Tuner but it doesn't appere in my settings menu, any idea to solve it?
Regards, Marco
Click to expand...
Click to collapse
Hi Marco,
could you please describe how to unlock the bootloader?
Thanks,
Chris
HI, for the bootloader just go in settings, unlock developer options and u can find there unlock OEM
I Have BV6000 now too, an no way found to root it.
Pappmann said:
I Have BV6000 now too, an no way found to root it.
Click to expand...
Click to collapse
Hi mate the System UI Tuner appere on your device?
Ring R00T?
Does King R00T work? This would be my 1st choice.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Avast! detects it as a PUP (POTENTIALLY UNWANTED PROGRAM) due to the exploit. And yes, avast!'s detection is correct, it is "Potentially" unwanted, you have the choice to have it ignored.
Also, I have the desktop version of King R00T installed into a netbook, so I don't have all the detection's going nutz, I do my R00T and jail brakes from the netbook.
Also, does the phone have an LED notification for calls/text/mail/charging on the front?
UnableToResetOldProfile said:
Does King R00T work? This would be my 1st choice.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Avast! detects it as a PUP (POTENTIALLY UNWANTED PROGRAM) due to the exploit. And yes, avast!'s detection is correct, it is "Potentially" unwanted, you have the choice to have it ignored.
Also, I have the desktop version of King R00T installed into a netbook, so I don't have all the detection's going nutz, I do my R00T and jail brakes from the netbook.
Also, does the phone have an LED notification for calls/text/mail/charging on the front?
Click to expand...
Click to collapse
The Phone have not led notification, i haven't tra King root yet because nobody have used it on this device
R00T, The '00' is the base directery in R'00'T
traneXD said:
The Phone have not led notification, i haven't tra King root yet because nobody have used it on this device
Click to expand...
Click to collapse
King R00T is for Chinese phones, by Chinese people, who live in China .... :silly:
Use the desktop version as it has better exploit ability's. It works on most Chinese phones that I R00T, the last Chinese phone I did (THL T7) it was flawless.
KR has a page here at XDA: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
PLEASE REPORT BACK WITH YOUR SUCCESS
.
.
.
.
.
.
.
UnableToResetOldProfile said:
King R00T is for Chinese phones, by Chinese people, who live in China .... :silly:
Use the desktop version as it has better exploit ability's. It works on most Chinese phones that I R00T, the last Chinese phone I did (THL T7) it was flawless.
KR has a page here at XDA: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
PLEASE REPORT BACK WITH YOUR SUCCESS .
Click to expand...
Click to collapse
I tried to root my BV6000 with KR, but it failed!
dr.dog1987 said:
I tried to root my BV6000 with KR, but it failed!
Click to expand...
Click to collapse
I guess it's early, this device was released in may :/
i tried kingroot too, does not work yet.
its quite simple, just flash TWRP from Needrom and then su.
worked for me
yankeeboy said:
its quite simple, just flash TWRP from Needrom and then su.
worked for me
Click to expand...
Click to collapse
yankeeboy,
could you please provide more details?
thanks in advance!
SuperSU 6.0 R00T
"Chainfire has released SuperSU root for Android 6.0 Marshmallow without modifying system partitions"
Give this a try: http://www.supersuroot.com/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:fingers-crossed:
chris-ba said:
yankeeboy,
could you please provide more details?
thanks in advance!
Click to expand...
Click to collapse
1. copy UPDATE-SuperSU-v2.65-20151226141550.zip (attached) to BV6000, remember where you place it
2. flash TWRP recovery.img(decompress from zip attached) with sp flash tool v5.1604 or newer, use scatter file attached, check only recovery for flashing
3. boot into TWRP recovery
3. flash UPDATE-SuperSU-v2.65-20151226141550.zip within TWRP recovery
4. wipe dalvik/cache
5. reboot
done
i'm not responsible for any bricked phone, use this all at your own risk!!!
yankeeboy said:
1. copy UPDATE-SuperSU-v2.65-20151226141550.zip (attached) to BV6000, remember where you place it
2. flash TWRP recovery.img(decompress from zip attached) with sp flash tool v5.1604 or newer, use scatter file attached, check only recovery for flashing
3. boot into TWRP recovery
3. flash UPDATE-SuperSU-v2.65-20151226141550.zip within TWRP recovery
4. wipe dalvik/cache
5. reboot
done
i'm not responsible for any bricked phone, use this all at your own risk!!!
Click to expand...
Click to collapse
many thanks for your remarks. I'm going to test it as soon as my phone arrives.
on needrom I read that some people have some problems. the touchscreen is not responding or they lost their IMEI.
were you faced with any problems quite like this?
chris-ba said:
many thanks for your remarks. I'm going to test it as soon as my phone arrives.
on needrom I read that some people have some problems. the touchscreen is not responding or they lost their IMEI.
were you faced with any problems quite like this?
Click to expand...
Click to collapse
no problems for me so far
Which v of TWRP?
yankeeboy said:
1. copy UPDATE-SuperSU-v2.65-20151226141550.zip (attached) to BV6000, remember where you place it
2. flash TWRP recovery.img(decompress from zip attached) with sp flash tool v5.1604 or newer, use scatter file attached, check only recovery for flashing
3. boot into TWRP recovery
3?. flash UPDATE-SuperSU-v2.65-20151226141550.zip within TWRP recovery
4. wipe dalvik/cache
5. reboot
done
I'm not responsible for any bricked phone, use this all at your own risk!!!
Click to expand...
Click to collapse
Sorry, for the post, I figured out my own question ... :silly:
Hi, does the bootloader need to be unlocked before flashing the TWRP and if so why is there no mention of this? Thanks!
Gyro installed incorrectly.
There is a possibility that a large production run is defective.
This defect may be in all the phones produced.
The gyro was installed incorrectly and the pitch and roll are swapped.
Check your phone and report this problem to Blackview.
https://youtu.be/LARkSzgvPjU
http://bbs.blackview.hk/viewtopic.php?f=142&t=42024
It's not on the net anywhere either, google is not working for the OT Elevate. There are no custom ROMs for the OT Elevate either.
I know that someone has one of these OT Elevate 5017B phones lying around somewhere. Post a stock ROM for download. People are suffering from bricks and soft-bricks. HELP more, we need to start a project making an attempt to catalog stock ROMs for every android device on earth.
There needs to be a larger archive of these ROMS. iOS developers are killing you. They have a database of all of the iOS firmwares, and there is a database of custom firmwares even for the iPhone 6S.
I know that the iPhone's situation is different, that one company designs the hardware and the software, and that everything is proprietary. I also feel there are too many companies making android phones. competition is one thing, but security of an OS is another. different phones from the same year with older versions of the OS on them, not good.
Marshmellow has been released and there are still 2016 phone releases with 4.5 OS on them. That's not secure. Why can't we make Android more secure by building better custom ROMs for more devices? I know there is a big shortage of developers, but you can recruit. Maybe even get funded by an organization, research grant?
Everyone needs more ROMs. Especially for Alcatel OT Elevate. Let's do something about this.
On 3. 1-2-3, Go Team!!!! :highfive: Let's Get It!
I have one of those Alcatel OneTouch phones right now, and I agree completely upon the notion for a catalog of all android devices that can be flashed.
@mU$!c @tyrex420
These Alcatel devices can only get attention if developers have them in their hands to work with. These devices are running a MediaTek SoC and not many developers like to work with those phones because of a lack of source code to work with or incomplete source in some cases. Yes you are correct in saying that Apple is different as it's one software, one hardware but you have to understand Google only set the stage and the companies do the rest. Not every company is Samsung or Sony. Alcatel has a tool which is really good called Mobile Upgrade Tool which has the factory ROM for their devices (which imho they need work on getting those newer devices supported). It works well if you haven't done much modification to your phone. Now the thing is that when those companies take the phones and modify them in some way like in locking the bootloader or hiding fastboot mode (Tracfone,MetroPCS), there's not much that a developer can do about that. Also those companies do not have that same support tool that Alcatel has which re-downloads the factory ROM because they are modified in some way.
Here's the good part about the phone running a MTK SoC. There are third-party tools such as MTK Droid Tools or SmartPhoneFlashTool (SPFT) which enables the users to make factory backups of their ROMs in the event that their devices suffers from a bootloop. What you can now do is become that developer that you are asking for to work on your phone and make something out of it. Be the first to upload a flashable factory ROM for your phone. Create a thread where users can come and post their issues and assist each other positively. It's nothing hard to do unless as I said before the company locks some part of the phone and makes these tools useless. By the way, MTK Droid Tools developer dropped support at Jelly Bean so KitKat and up won't work with the tool as it should.
Again, yes I agree with you in saying it would be nice for a users to find a compilation of ROMs that they can just follow instructions and flash but the thing is source code and users themselves not knowing how to use the tools mentioned above. If you want you can ask me for help in guiding you on how to use the tools. I've been doing this for 3 years now working with MTK and I'm learning something new everyday.
Sorry for my long reply, I hope to see a reply from you concerning getting a factory ROM for this device maybe a thread similar to mine .
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
bg260 said:
@kirito9
Thank you. I learned more in 2 minutes from your reply than in two hours searching the internet. XDA needs more people like you!
-Cheers
Click to expand...
Click to collapse
You're welcome .
kirito9 said:
You're welcome .
Click to expand...
Click to collapse
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
bg260 said:
I had one of these fall in my lap. Charging port is shot. At least I can remove the battery and charge. I'm trying to see if it's worth fixing. All signs are pointing to no, unfortunately. OEM Bootloader unlock is available but without Fastboot.......
Click to expand...
Click to collapse
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
kirito9 said:
Hmm so you don't have a working charging/usb port. I doubt you'll be able to do much with this phone in terms of development. Not sure if there is a way to unlock the bootloader from the device itself, doubt it.
Click to expand...
Click to collapse
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
bg260 said:
I'll see if I can get something useful out of it. Maybe a recovery.img, boot.img, system.img. I'll have to use one of those dreadful one-click apps though.
As for the OP I think this is as close as it gets.
http://forum.xda-developers.com/wiki/
Being a public wiki everyone is welcome to add to or amend it.
Click to expand...
Click to collapse
Yeah although the information is quite old still useful.
Root with Kingroot and backup with flashify haha. But won't you need the unlocked bootloader to root?
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
bg260 said:
Got side tracked. Device currently disassembled, trying to replace usb but it is hard soldered to the Motherboard. Cheap phones....
Click to expand...
Click to collapse
Ahh cheap phone problems. Let me know if you get through.
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
bg260 said:
Successfully rooted with Kingroot v4.92 . I have included others JIC.
I used The paid SuperSUme Pro to eradicate Kinguser from the device. Here are some other options.
http://forum.xda-developers.com/gal...ve-kinguser-replace-supersu-sch-i545-t3334533
After updating SuperSu via the playstore I installed Busybox Pro, but the unpaid version is fine. At which point I updated the SU binaries the "Normal Way" without a hitch.
View attachment 3906591
@kirito9
I'll start with a system.img What else do you need?
Thanks
-Bg260
Click to expand...
Click to collapse
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
kirito9 said:
Did you get the the USB removed? Hmm what are we trying to achieve? A full backup or a ROM?
Click to expand...
Click to collapse
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
bg260 said:
I wasn't able to replace the USB. Without an unlocked bootloader there is not much I can do. Thought maybe I would help the cause is all. I personally will probably screw with it till it bricks. IDK. Thought someone could at least get a recovery going. I'm not a developer in that sense. I usually just crack open the system.img and add/remove a few thing to my liking. I'll go ahead and dump a system/boot/recovery.img package on AFH if anyone has interest.
Click to expand...
Click to collapse
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
kirito9 said:
Ahh, that'd be nice. Someone might mess up their stock recovery/boot/system. Please upload and maybe I can try to get a custom recovery for this device. Then make a full backup using the custom recovery.
Click to expand...
Click to collapse
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
bg260 said:
Found something different, the system partition on mmcblk0p33 is 800mb 535 used.
There is also something called custpack on mmcblk0p32 at 1gb total 663mb used. I made an img of both. I'll upload it in a little bit.
Quick question, I have been using furiusisomount with Linux mint cinnamon to rummage around system images. Lately it throws an error and won't mount. Is this familiar to you? I'm not as proficient with the CLI as I'd like to be so I often rely on GUI.
Click to expand...
Click to collapse
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
kirito9 said:
Ok, both images are critical for Alcatel devices running MTK SoC to get it booting. The furiusisomount I'm not familiar with but maybe I can help. What error are you getting?
Click to expand...
Click to collapse
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
bg260 said:
Ok, Here you go. It has boot, aboot, recovery, system and custpack. Are you going to need patitioning info? Be easy if I had adb. But I don't
I'll get back to you on that error. I'm having some other issues and I think it might be systemic. I may have to do a fresh install of Mint.
Let me know what else you need. Happy to help.
https://www.androidfilehost.com/?fid=385035244224385460
Click to expand...
Click to collapse
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
kirito9 said:
I think there may be another way to get the partitioning info but let me look into it. Thanks for the files and will let you know if I need anything else .
Click to expand...
Click to collapse
See if this is what you need. Created it with DiskInfo Pro. I used a different machine and mounted the system image fine. I thought it was a bad copy because the Build.prop displayed as broken. Then I realized it was just a symlink to the actual build.prop in custpack. At any rate, there's a copy of the build.prop in there as well.
View attachment build.prop-partitions-5017b.zip
I just bought a Alcatel Fierce 4, & I can't find anything on how to root it.
Metro Pcs Alcatel Fierce 4
Model: 5056N
Android version: Marshmallow 6.0.1
If anyone would kindly help me out & if possible give me a small walk through on how to do it I would be forever grateful.
Thanks in advance
-Joanna
Msjoannalynn said:
I just bought a Alcatel Fierce 4, & I can't find anything on how to root it.
Metro Pcs Alcatel Fierce 4
Model: 5056N
Android version: Marshmallow 6.0.1
If anyone would kindly help me out & if possible give me a small walk through on how to do it I would be forever grateful.
Thanks in advance
-Joanna
Click to expand...
Click to collapse
I looked a little and I didn't find pretty much for rooting your device. In thesr cases you will have to use general tools like kingroot, kingroot pc, kingoroot and ... If you are lucky enough your device will show weakness in the root exploits and will eventually gets rooted. To start try this apk of kingroot:
http://forum.xda-developers.com/devdb/project/dl/?id=20228
If you couldn't root Your device using kingroot you will have to use pc apps like kingoroot:
https://www.kingoapp.com
Remember to report back. Sorry that I didn't have much to give you, your device didn't even have a single xda-developers thread.
I have this phone - I tried kingroot android-no luck. Tried both kingroot and kingoroot pc, and neither will recognize that I have the phone connected via usb, so no luck yet.
Thank you, I tried all of those & no luck yet... I don't what else to do but thanks again
JohnSmit268 said:
I looked a little and I didn't find pretty much for rooting your device. In thesr caaes you will have to use general tools like kingroot, kingroot pc, kingoroot and ... If you are lucky enough yoir device will show weakness in the root sploits and will eventually gets rooted. To start try this apk of kingroot:
http://forum.xda-developers.com/devdb/project/dl/?id=20228
If you couldn't root Your device using kingroot you will have to use pc apps like kingoroot:
https://www.kingoapp.com
Remember to report back. Sorry that I didn't have much to give you, your device didn't even have a single xda-developers thread.
Click to expand...
Click to collapse
Any new updates?
Also anything on the HTC desire 626s
This phone is fairly new there won't be a root for about 3-5 more months although I have began to build my own
Stockroot said:
This phone is fairly new there won't be a root for about 3-5 more months although I have began to build my own
Click to expand...
Click to collapse
What about for the HTC desire626s 6.0.1
Msjoannalynn said:
I just bought a Alcatel Fierce 4, & I can't find anything on how to root it.
Metro Pcs Alcatel Fierce 4
Model: 5056N
Android version: Marshmallow 6.0.1
If anyone would kindly help me out & if possible give me a small walk through on how to do it I would be forever grateful.
Thanks in advance
-Joanna
Click to expand...
Click to collapse
Msjoannalynn said:
What about for the HTC desire626s 6.0.1
Click to expand...
Click to collapse
The HTC desire 626s I believe has been ahieved if im not mistakes you need to unlock the bootloader then flash twrp and use twrp to flash super su but his is the wrong forum for that
Just got this phone I miss having root.
Any word on a root method?
How much would someone charge me to make root for this device?
I mean realistically with the time and effort needed to accomplish such ?
Okay, so I successfully obtained root on the 5054n running 5.1.1. It's very much the same phone with the same specifications. I am thinking if I can trick my windows pc into thinking my 5056N is the 5054N I wlll be able to install the firmware from the official Alcatel tool on my PC I've used numerous times to update my 5054N. Any way to trick my PC into thinking it's a different model phone?
I obtained root on the 5054N also when I first bought device or was simple using kingroot. Never found any roms but was able to debloat and install freedom. Then one night I made the mistake of downloading mac address changer that I've used before on other rooted devices as soon as I have it root access phone froze then went into boot loop permanently. I have no pc right now so hard to say just how bad I messed device uti when I took it to metro they were out of 5054n and upgraded me to the 5056 no questions. That's where I'm at now with no root still
Bassin05 said:
I obtained root on the 5054N also when I first bought device or was simple using kingroot. Never found any roms but was able to debloat and install freedom. Then one night I made the mistake of downloading mac address changer that I've used before on other rooted devices as soon as I have it root access phone froze then went into boot loop permanently. I have no pc right now so hard to say just how bad I messed device uti when I took it to metro they were out of 5054n and upgraded me to the 5056 no questions. That's where I'm at now with no root still
Click to expand...
Click to collapse
If you need help on recovering it from the boot loop I can actually help! If you still got it let me know!
Any updates for rooting this phone?
I am trying kingroot on ny 5056W now (T-Mobile) on Android 6.0.1.
I'll update if it works.
Edit:
Tried latest kingoroot and kingroot - Neither worked after multiple tries (Because sometimes you need to run it multiple times.)
I'm in the same boat just switched to the 5056 after rooting my 5054n but wondering if the twrp recovery will work on it aswell like the 5054
jessteaf said:
I'm in the same boat just switched to the 5056 after rooting my 5054n but wondering if the twrp recovery will work on it aswell like the 5054
Click to expand...
Click to collapse
Personally I think it would if there was some way to spoof the PC into thinking it was a 5054N, It is essentially the same exact hardware I don't see why not. I am just unaware on how to spoof the driver for the device.
brad2192 said:
Personally I think it would if there was some way to spoof the PC into thinking it was a 5054N, It is essentially the same exact hardware I don't see why not. I am just unaware on how to spoof the driver for the device.
Click to expand...
Click to collapse
Rooting is all about software, not hardware. If the software does not allow it, blocks it, or patches it, then no amount of "spoofing" will allow root. Same hardware or not, the devices will have essentially different firmwares (Not talking about ROM) and Kernels that can and probably are preventing root access. The best way at this point is for someone to port TWRP to our device, we OEM unlock, and then flash SuperSU (And pray it does not cause a bootloop)
I saw this in the developer settings.
http://i.imgur.com/8C8Nze5.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://i.imgur.com/8C8Nze5.jpg
Kingoroot
I have just purchased the Alcatel Raven A574BL with a Qualcomm 210 chipset . It's a great value running Android N and 2gb RAM, so being able to run a custom recovery will also make it a great value as a developer's tool. At $30 it's basically expendable, so I don't mind risking to brick it. So far I have not been able to find any root support for this device on Google. If anyone can help me get started with this, or point me in the right direction, it will be much appreciated.
mscott9437 said:
I have just purchased the Alcatel Raven A574BL with a Qualcomm 210 chipset . It's a great value running Android N and 2gb RAM, so being able to run a custom recovery will also make it a great value as a developer's tool. At $30 it's basically expendable, so I don't mind risking to brick it. So far I have not been able to find any root support for this device on Google. If anyone can help me get started with this, or point me in the right idirection, it will be much appreciated.
Click to expand...
Click to collapse
My understanding is the system is locked down and cannot be done. I've been wanting to do the same on same phone in your post.
thanks for the reply. i am disappointed to learn that it's impossible to root this phone... what i really need is a phone which is under $50 and can be easily rooted. also otg support will be a great bonus. it's totally ridiculous to pay up to $500 for a pixel... just so i can have root functionality. even if i could find a good deal on a recertified, most likely it won't support the latest android OS. if anybody out there can help me with this issue... which really shouldn't be an issue at all, it will be much appreciated. i'm trying to run android N at a minimum.
mscott9437 said:
thanks for the reply. i am disappointed to learn that it's impossible to root this phone... what i really need is a phone which is under $50 and can be easily rooted. also otg support will be a great bonus. it's totally ridiculous to pay up to $500 for a pixel... just so i can have root functionality. even if i could find a good deal on a recertified, most likely it won't support the latest android OS. if anybody out there can help me with this issue... which really shouldn't be an issue at all, it will be much appreciated. i'm trying to run android N at a minimum.
Click to expand...
Click to collapse
Search on the TWRP website, if a phone has TWRP available for it, it will also have a rooting solution.
The rest like searching one with Android N or above, I leave it to you.
HIT THANKS IF FOUND USEFUL
How do I root my Alcatel Raven
https://clickitornot.com/unlock-bootloader-on-alcatel-device/
Alcatel raven
Has anyone found a way to unlock bootloader and root this phone yet?
crazypwn said:
Has anyone found a way to unlock bootloader and root this phone yet?
Click to expand...
Click to collapse
I would like to bump this thread. I am in the same boat. Googling has gotten me now where.
Possibly
Although KingRoot seems to have found an exploit, it is iffy. The problem seems to be lack of supported fastboot. Not sure about Oem unlocking, though the option still is under settings>dev options>allow oem unlock(need dev access settings>about phone>build number tap 7x) Without full fastboot support, I can't see if it does anything. There is a possible solution, but since I'm new I can't share the link
Without a potential hard brick and basically cracking the OS, root is improbable. I nay have a solution. Still working on it.
Possible solution
King root seems to have taken down the exploit, since it rarely worked. There is a post on stupdroid that may have a solution. From what I can tell(I own the A574BL), although the OEM unlock function works, fastboot either does not work, or is locked down
To root your phone there are many way.
I can help you rooted your phone by getting boot.img
If you give boot.img there might be a hope
and to get TWRP
I'll need to port it by using your stock recovery.img as base.
or or or or....
You can make it by scracth
Reeak
I don't know of a way to get boot img. How do I make it myself?
or just give me your firmware files
Re
Peak.Krittin said:
or just give me your firmware files
Click to expand...
Click to collapse
How do I get those? Once again, these things are not publicly available for my device
clcombs262 said:
How do I get those? Once again, these things are not publicly available for my device
Click to expand...
Click to collapse
Well You got no hope right now.
If you came back with boot.img I will make the magic happen
Peak.Krittin said:
To root your phone there are many way.
I can help you rooted your phone by getting boot.img
If you give boot.img there might be a hope
and to get TWRP
I'll need to port it by using your stock recovery.img as base.
or or or or....
You can make it by scracth
Click to expand...
Click to collapse
you seem very helpful..
I just got this phone at BB for $15, on sale for 20 then another 5 email credit. Still using my Alcatel Ideal for phone use with Red Pocket AT&T sim for now, just using the Raven as kind of small wifi tablet. But I really like it after having gotten set up just right I'm pretty satisfied even with it not rooted. I'm watching this thread though, I'd probably be all over it if someone comes up with something. Good luck!
Maxxvds said:
https://clickitornot.com/unlock-bootloader-on-alcatel-device/
Click to expand...
Click to collapse
I have an Alcatel ZIP (A576BL), and I find it odd that you can root Alcatel's other devices and ported re-badged phones (ex ZTE Blade) but not THIER phones...
You can port TWRP recovery from alike devices with same chipset , android and kernel version etc. Also you can try 'systemless root' , for example Magisk.
Working with ADB Shell
So having just finished successfully rooting the Alcatel 5059r last night I was hoping I'd have some luck with the Raven. However I have not! At the moment I've hit a wall working with ADB Shell commands, hoping to push, move, mount/remount, and get a root out of it. As i've exhuasted the extent of my tools so down to the nitty gritty. So the problem I'm having with the ADB Shell end of things is that although I've got the proper commands nailed, I can't seem to mount/remount my system folder into read/write. Thats not a huge surprise considering I have no access beyond user. I have however found several folders and files of interest. I can manipulate the oem folder, but honestly at this point the easiest thing would justbe for me to move SuperSu Binary or MagiskSU.zip from storage or SD to the proper folders. As this is really the first time I've had to resort to such methods, and the literature on the subject is at first glance somewhat lacking; as it always is when things get this specialized.
If anyone has any ideas of how to go about using ADB Shell commands or any other method I haven't tried (all in one tool, platform tools, alcatel flasher, sp flasher, odin, frp hijacker tools ect) Keep in mind this phone at this moment in time doesn't support SD updating thru recovery, fastboot/bootloader/download is locked away somewhere, and yes ADB Sideloading methods as well. I'm willing to try anything and I'll put the time in and exhaust any ideas you guys may have for me!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.5.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
How to install:
Coming From Stock:
1. Download This TWRP Release and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
2. Under Developer Options, Tick OEM Unlock. It will tell you to factory reset. Do it.
3. After the phone shuts down, press Vol + & - button and at the same time, insert a usb cable to phone connected to a PC.
4. Check KG Status. If it is Prenormal, reboot the phone and follow this guide : (1) How to bypass KG State and/or RMM state prenormal | XDA Developers Forums (xda-developers.com)
5. Zip the TWRP recovery image to tar format and put in the AP slot of Samsung Odin.
6. Flash and after the phone screen turns off, press vol+ and power button.
7. If there is "Set Warrenty Bit : recovery" text on the top left, success!
8. Format data, flash zip downloaded from above.
9. To boot stock rom, install magisk.
From Other Recovery:
Reboot to recovery and flash this TWRP image as recovery and reboot recovery.
ChangeLog:
2021/3/2 Inital Release
Sources:
Kernel : Junak/android_kernel_custom_a6plte (github.com)
Device Tree: roynatech2544/TWRP_device_samsung_a6plte (github.com)
Recovery Source : TeamWin (github.com)
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
NOTE :
I was developing custom roms for A6+ despite of my computer specs. But my phone's LCD went out and I can't test anymore... And it takes 1 day to build in i5-5200U (2C/4T) CPU and 8GB RAM.. Now I can only build TWRP.
where is the twrp file ?
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
CRDhani said:
where is the twrp file ?
Click to expand...
Click to collapse
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
little_beppo said:
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
Click to expand...
Click to collapse
yes it works.
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Hello
Is this recovery for android 10?
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
abhisekh010 said:
Hello
Is this recovery for android 10?
Click to expand...
Click to collapse
Yes it is compiled in android 10 tree but recovery doesn't depend on android version..
Naddi2Niic3 said:
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
Click to expand...
Click to collapse
PM me
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
okwhateverok said:
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
Click to expand...
Click to collapse
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Thanks, ill hope there will be some users which ow the Galaxy A6 and not using this device as their main phone to be willing to test.
As a IT specialist myself i did try anything to at least help testing for this version of TWRP for our device. I did try to take several rom dumps with professional fabric software and hardware like software dongles but it was impossible to make a full rom dump.
With this said and knowing that a complete data wipe within TWRP is necessary to make the recovery find the internal storage makes it impossible for me to test no matter the fact that the biggest part of this recovery already exist and confirmed working.
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
nqnxev said:
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
Click to expand...
Click to collapse
I could help with the OEM unlock button. What a waist of time these lost 10 days and still no OEM unlock button while the solution is easy...
Follow guide with screenshots: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
And for those who could test on the A600 the recovery image is already uploaded within this thread thanks to Royna
I've tried that many times (no only that, but many similar guides) - and still nothing. From what I read, Samsung just fixed that "date & time" trick and I have to wait.
Ok that is strange, im on android 10 with One UI version 2.0 and got it working. If im allowed to post this link then the rom could be found here: https://www.sammobile.com/samsung/galaxy-a6/firmware/SM-A600FN/PHN/#SM-A600FN
You should do a clean flash without having the phone connected to the internet, not even once because it will do some synchronization. After the flash just follow the guide which could be found on the xda forum..
Thank you for a hint. Because of that I'm waiting so long already I'll wait till end of week and if things still will be the same then I'll try rom you've proposed. Thanks again.
Royna said:
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Click to expand...
Click to collapse
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Adam7336 said:
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Click to expand...
Click to collapse
Well because i don't own that device, it is highly experimental. I will try again.