I'm wondering if anyone has had any success with the Oppo A57 and either rooting it with a recovery that's had the root option removed, or otherwise replaced TWRP with the stock recovery to do an OTA update.
I've spent the last week and a half realising that rooting my Oppo A57 was a horrendous idea (took me two days to get signal back, woops!) and now I'm regretti and have no spaghetti.
I followed this guide to root the phone, then I used flashed a zip which replaced the Chinese TWRP with an English one, which no longer has the option to root the phone. I've also accidentally unrooted the phone, but ColorOS keeps complaining that it's rooted despite its being not.
Oppo gives an option to 'remove root' by installing an OTA update; which then loads into recovery where I have no idea how to install said OTA update or even if it's a good idea or not. As far as I can tell there's no one who's released the stock recovery yet.
Thanks for any and all replies
I have had a similar problem with my Oppo A57, and as it turns out, the store i bought it off gave me a refund even though it was rooted. Perhaps you could try that? Sorry i couldn't be more help I've been looking everywhere trying to fix mine too.
My phone has no signal. You said you fixed that? How did you go about doing that?
How did you change the Chinese custom recovery to English
LividGryphon said:
How did you change the Chinese custom recovery to English
Click to expand...
Click to collapse
Flashed a zip which replaced the Recovery, flashed a different zip (findable somewhere in the 'how to root your oppo a57' thread) which fixed the signal issue.
Looks like there's still some issues with trying to root this phone...
Okay so I´m trying to flash original firmware to my oppo A57 using the MSM download tool and the problem is that it doesn´t recognize my phone in the download mode (or whatever it is called). Under the ´status of connection´ it says N/A. However the Qualcomm drivers are installed and when I checked the device manager it shows that my phone is connected. Any help in this regard would be most appreciated. Thank you!
Hi posting for helping my friend A57, he installed twrp and he doesnt going to install stock rom... always failed!
Related
Chapter 1: The Foolishness of the User
Hi, I have the korean version of the optimus one(KU3700). It was on gingerbread(2.3.4) stock. I was trying to root it by downgrading it. I entered "adb reboot recovery" and I'm stuck. I tried to reflash it by going to emergency mode with the button combinations using the KDZ updater with this
"csmg. lgmobile. com:9002/swdata/WEBSW/LGKU3700/AKTFBK/KU370040_00/KU370040_00.kdz"
and it worked without any errors but when it when it came up it was still on recovery mode. Is there any way I can change the phone mode to the regular mode
Chapter 2: Journey to Salvation
For anyone who has this korean optimus one, after days of searching, I've found a web site that gave me hints to solve the problem. I just needed a different kdz file and I got it here:
h t t p://sirospace.tistory.com/category/Android%E2%97%86
popped it in google translate because I'm Filipino and can't read korean.
Downloaded the froyo kdz and flashed. I hope this can help other people stupid enough to play with their phones by typing random commands without knowing what it does, like me, LOL...so happy, now it's time to root
Chapter 3: False Hope
OK so I have successfully unbricked and rooted my KU3700, now The problem I have is installing a custom recovery on this phone, none of the images I try work.
Recovery images I have tried are as follows:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
Every time it finishes and reboots, it gets stuck at the LG logo.
Chapter 4: Wisdom Within
Found the problem. The images above are for the P500.Even if the KU3700 hardware is similar to the P500, flashing firmwares made for the other model will result in errors. The same holds true for custom recoveries.
Chapter 5: The Plea to the Gods
I've contacted drellisdee and submitted the files needed for custom recovery creation for the KU3700.
Just waiting for the flash image now. Thank you everyone
Chapter 6: The Forgotten
It seems drellisdee is busy right now. I'm a windows user and knows nothing about programing. So if anybody can help I'm sure the KU3700 community would be greatful. I've attached the files I think are needed to make a custom recovery.
Chapter 7: Quest for the Custom Recovery
I got tired of waiting. So as a windows user with no experience in programming, I did a lot of copying and pasting, I managed to port clockwork mod using virtualbox following this website:
h t t p://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
So I have got a bootable and flashable custom recovery but nothing works yet. I still need to configure it according to the device.
I have uploaded the image and the build files. Please help me configure it and tell me what's wrong. I really don't know that I'm doing
PS: you can try flashing the custom recovery by doing "fastboot flash recovery /Path to/recovery.img and you can go to recovery by using android terminal and type "boot recovery". It will boot, but that's that LOL. Take out the battery to boot to normal mode.
Chapter 8: The Holy Grail
LOL, I found the answer again. I was so frustrated that I kept squishing the phone in recovery and found out that it was just a button configuration problem. A bit of research and I found out that I can toggle it by pressing volume up and volume down at the same time. WOOHOO!!! Custom Recovery at last
Chapter 9: Invasion of the ROMS
And here at last, the user is retired. But the adventure is far from over. It is foretold that the creation of the Custom Recovery will begin a new era. The key to open the gate has been found. So our hero will await the invasion of the ROMS<background music...> END
you can see at
tinhte.vn/threads/908874
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
vidgen13 said:
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
Click to expand...
Click to collapse
yes i see.but i'm newer android.i only send you link to fix
i hope have a pro android to fix your brick
This is just a shot in the dark because i didn't understand what you did entirely : have you used the combination to actually recover the stock rom after you flashed with KDZ ? (Home+VolDown+Power)
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
vidgen13 said:
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
Click to expand...
Click to collapse
Are you sure you flashed the right rom for your phone? There's an application that downloads the required rom for your phone according to your IMEI/SN, but i don't know if it works with the korean version.
Yes it's the KDZ file, unfortunately it's the only KDZ file out there for ku3700. Shouldn't have settled for this korean version
why you wanna downgrade the latest version?
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
asmOne said:
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
Click to expand...
Click to collapse
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
I dont get it ,p504,p505,p506 are versions of p500??? And why some of our roms work on those phones?? So by logic this stock work on p500???
Sent from my LG-P500 using XDA Premium App
vidgen13 said:
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
Click to expand...
Click to collapse
this method worked for my working KU3700 when I'm using my 1st KU3700 I also was struck as you and finely I realized there are No custom roms for Optimus one Korean edition (KU3700/SU370) and I had to connect my phone to an Octopus box (lg softwere box) via software box installed the official firmware. if this method not working you have to connect to a software box.
connect to the internet your PC and 1st install Driver and 2nd install the LG update tool. after installation connect your phone to computer and wait a five seconds for comport installation. after install your phone Run LG Update application.
it is connect to the server automatically indicating red line and after search for latest firmware.
if you can Update your phone it is shows Update butten.
Driver
http://www.4shared.com/file/C3BSNx9P/lgunitedmobiledriver_s4981man3.html
LG Update Tool
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Thank you all for the quick answers, but I already have a rooted ku3700. All I need now is a working custom recovery. If someone has the same phone, please tell me which image is compatible
you can appear the emergency mood with android logo.
it means you have an Empty phone. your Os was been erased. You have to connect your phone to Octopus software box and box server has you original Os for your IMEI. this is the only solution. if you will able to solve this problem without a Software box please inform me. we can open a New Thread for Korean edition.
(ku3700/su370)
I already got out of the emergency mode without an octobus box. It's really simple, you just need to use a different kdz file. The hard part was looking for the kdz file. I have 3 kdz files. KU370017(froyo), KU370033(gingerbread-rootable), KU370040(latest one from LG, gingerbread-unable to root). Just flash with the KDZ updater. I'm on the second firmware because I can't root the latest firmware. To root it, I used super one click(latest version, use zerg rush option). Now I'm just waiting for a custom recovery from drellisdee so I can use custom roms. When I get it, I'll ask him if I can post it so we all can have uber phones LOL
Updated the thread. Can somebody help?
vidgen13 said:
Updated the thread. Can somebody help?
Click to expand...
Click to collapse
If you have flashed a working clockworkmod you can enter into clockworkmod via ROMManager (search in google play aka market). In ROMManager you have "reboot to recovery" option in case you want to go to recovery to flash something. Also you can try to flash from ROMManager a custom recovery (5.0.2.0 for oldBB or 5.0.2.7 for newBB), try to choose to phone model LGP500 oldBB, try and test if it's working. Wish you luck.
Thanks but I already have a working recovery. I just need some ROM makers now
vidgen13 said:
Thanks but I already have a working recovery. I just need some ROM makers now
Click to expand...
Click to collapse
Have you tried CM7.2? if your phone is very similar with Optimus One i doubt it isn't compatible with your phone.
If your phone use 2.6.35.10 or 2.6.35.14 kernel you can give a shot to try CM7.2 on your phone, but before try this make a backup first.
Check this thread Post Your CyanogenMod 7.2.0-RC1 Nightly Questions HERE!! for CM7 custom rom.
yep, it doesn't work. Is there a tutorial for building cyanogen for unsupported devices? All I can find are tutorials for supported devices. I've already got the source code from LG. The problem is just incorporating it in the cyanogen mod. I wish this phone had more users LOL
Greetings fellow XDA Users,
Let me get right to the point. A week ago my Cubot One arrived which I ordered from dealxtreme. Eveything was fine and I was very happy with the phone.
But 3 days ago I tried to change the resolution of the screen with an app from the Play Store and of course I did not backup my rom a really stupid thing to do on my part.
Now my Cubot One is soft bricked I think as it only boots to the android logo and that's it. I can still access the recovery menu but unfortunately I only have the stock recovery.
I have tried like literaly everything to unbrick my phone but nothing has worked so far. I tried to use the Cubot One T card upgrade and install it from an SD card but it fails with an MBR related error I think. I have tried to flash an older ROM I think V0.3 throught SP Flash Tools. I tried to only flash the CWM recovery through SP Flash tools again but that didn't work either. I tried to install custom roms through the ADB sideload ability of the stock recovery but nothing seems to work.
Is there any way I can repair my phone? Is it possible for someone that has recently baught a Cubot One running the V0.7 rom to do a backup and send it to me and instruct me how to install it? I would really appreciate any help.
I just want you to know that I am opening this thread as a last resort I have tried everything I have even tried the MTK Tools software but It doesn't recognize my phone possibly because It doesn't boot or I have lost the root and usb debugging previleges.
Can someone please give me a backup of the V0.7 ROM? I think that that is my last chance to save the phone.
Thanks in Advance.
VagProt said:
Greetings fellow XDA Users,
Let me get right to the point. A week ago my Cubot One arrived which I ordered from dealxtreme. Eveything was fine and I was very happy with the phone.
But 3 days ago I tried to change the resolution of the screen with an app from the Play Store and of course I did not backup my rom a really stupid thing to do on my part.
Now my Cubot One is soft bricked I think as it only boots to the android logo and that's it. I can still access the recovery menu but unfortunately I only have the stock recovery.
I have tried like literaly everything to unbrick my phone but nothing has worked so far. I tried to use the Cubot One T card upgrade and install it from an SD card but it fails with an MBR related error I think. I have tried to flash an older ROM I think V0.3 throught SP Flash Tools. I tried to only flash the CWM recovery through SP Flash tools again but that didn't work either. I tried to install custom roms through the ADB sideload ability of the stock recovery but nothing seems to work.
Is there any way I can repair my phone? Is it possible for someone that has recently baught a Cubot One running the V0.7 rom to do a backup and send it to me and instruct me how to install it? I would really appreciate any help.
I just want you to know that I am opening this thread as a last resort I have tried everything I have even tried the MTK Tools software but It doesn't recognize my phone possibly because It doesn't boot or I have lost the root and usb debugging previleges.
Can someone please give me a backup of the V0.7 ROM? I think that that is my last chance to save the phone.
Thanks in Advance.
Click to expand...
Click to collapse
I really don't want to spam but I really need some help the phone is brand new I can't just leave it like this. Thanks!
No help at all? Nice community... I am just supposed to throw the phone away.
Did you tried this rom?
Hello, i found this firmware in needrom page.
Check it!
www_needrom_com/mobile/cubot-one-turbo/
change _ with .
Hello,
I rooted a Medion P4501 for a friend of mine via vroot (I know about the concerns on vroot possibly being malware, but I rooted a lot of phones with it by now without any problems) and it worked perfectly, deleted the chinese SuperSU and installed the german version of the app, and after several reboots no problems occurred.
Then I used flash gordon app, which is able to flash zips without custom recovery needed, to flash the Sony Xperia keyboard flashable zip, which worked on every phone I installed it on until that day, the app said "success", and after the next reboot, it went into some kind of native recovery mode, and since it only boots into recovery mode.
Anybody knows what to do now?
Thanks in advance,
Nash.
nashsx said:
Hello,
I rooted a Medion P4501 for a friend of mine via vroot (I know about the concerns on vroot possibly being malware, but I rooted a lot of phones with it by now without any problems) and it worked perfectly, deleted the chinese SuperSU and installed the german version of the app, and after several reboots no problems occurred.
Then I used flash gordon app, which is able to flash zips without custom recovery needed, to flash the Sony Xperia keyboard flashable zip, which worked on every phone I installed it on until that day, the app said "success", and after the next reboot, it went into some kind of native recovery mode, and since it only boots into recovery mode.
Anybody knows what to do now?
Thanks in advance,
Nash.
Click to expand...
Click to collapse
hey i made an thread for P4501 you can use it to root
flash gordon app is still in beta version so cant gurantee any thing of it.
Ithink your phone is bricked thats why its going back and back to recovery mode. Try flashing Boot image and see the problem is resolved or not.
Arrowblue said:
hey i made an thread for P4501 you can use it to root
flash gordon app is still in beta version so cant gurantee any thing of it.
Ithink your phone is bricked thats why its going back and back to recovery mode. Try flashing Boot image and see the problem is resolved or not.
Click to expand...
Click to collapse
Hello, thanks for reply, but it seems there are no noot images for this device on the internet.
nashsx said:
Hello, thanks for reply, but it seems there are no noot images for this device on the internet.
Click to expand...
Click to collapse
Thats why i made an whole thread related to p4501 just go there tell to other who own p4501 i need more attention over there to start develop some thing for p4501 but i do need help since i dont own the p4501 any more
here you go https://www.copy.com/s/BRrQ6CUwPLOOMvJ6/Kernel
Q&A for [RECOVERY][ROOT] Ulefone Be Touch Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][ROOT] Ulefone Be Touch Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Ulefone Be Touch OTA
Hi,
I have rooted my Be Touch and installed custom recovery as well using this guide
- http://forum.xda-developers.com/android/development/recovery-ulefone-touch-lollipop-t3132204
Now, there is an available OTA from the local reseller and I can't install it due to custom recovery. How do I update my phone now? The error I am getting is System is Damaged which I have attributed to CUstom Recovery upon searching google
I have the same problem to update phone. The downloaded update.zip file over OTA could be found in my SD-card, just 18.89Mb. I've tried to install it using recovery by choosing "install zip -> choose zip from sdcard". But finally I got following error:
...
Verifying current system...
"EMMC:boot:7262208:..." has unexpected contents.
E:Error in update.zip
(Status 7)
Installation aborted.
Hofefully someone could help?
yes same with me, I am trying sideloading with ADB but I do not know about that, unable to make a connection between PC and phone. Maybe someone has stock recovery image so we can perform the OTA update? Anyone can upload their stock recovery?
Reverting back to kitkat.
I tried flashing using spflash on my Ulefone Be touch, it was on lollipop and it did not transition to kitkat. it in fact got semi bricked but i got through that and fixed it. the phone was originally rebranded so it had another skin on top of it (not ulefone). how can i get it back to kitkat? do i have to root it and manually flash it on my phone? or is flashing a downgrade not possible by just regular means?
blank_blank said:
yes same with me, I am trying sideloading with ADB but I do not know about that, unable to make a connection between PC and phone. Maybe someone has stock recovery image so we can perform the OTA update? Anyone can upload their stock recovery?
Click to expand...
Click to collapse
Here is the latest stock rom: http://ulefone.com/download/betouch.html. You will find the boot.img and recovery.img in the zip file. But I'm afraid to brick my phone to have a try. Moreover I don't know whether this root method could still work if I get phone flashed successfully...
are you using a rebrand? I already flashed the recovery of Be Touch, unrooted my phone as well but OTA is still failing, even manual zip install and sideload fails. I guess it is because my phone is a rebrand and thus, uses another recovery as stock. I have used this ROM as my base now and I can confirm that root is still working
blank_blank said:
are you using a rebrand? I already flashed the recovery of Be Touch, unrooted my phone as well but OTA is still failing, even manual zip install and sideload fails. I guess it is because my phone is a rebrand and thus, uses another recovery as stock. I have used this ROM as my base now and I can confirm that root is still working
Click to expand...
Click to collapse
I think my phone is not rebrand, because there is ulefone logo on rear cover. I got it rooted with Build 20150513 ROM.
With the rooted Build 20150513 ROM, I get phone flashed with official Build 20150529 ROM successfully. Afterwards, the root method still works!
yup and i hope we get new build soon with bug fixes! Does your phone get a lot of heat when charging and browsing 3G?
blank_blank said:
yup and i hope we get new build soon with bug fixes! Does your phone get a lot of heat when charging and browsing 3G?
Click to expand...
Click to collapse
I've used several phones and can accept this one. More faster to change the phone more heat will get produced. Surfing or gaming will need more hardware resource and power for display, no wonder that it will get warm too. Maybe a metal cover will get heat better distributed, but then it will be sold in another price...
blank_blank said:
yup and i hope we get new build soon with bug fixes! Does your phone get a lot of heat when charging and browsing 3G?
Click to expand...
Click to collapse
You should try 20150702 ROM. Phone is now not less hot when charging and surfing. I did flash back to official 20150529 ROM and then do the OTA update.
There is a ROM of ulefone be touch 2 on needrom !
Rooted Be Touch 2, Xposed, Loving it.
Hi folks. I used this process to successfuly root my Ulefone Be Touch 2. Instead of the provided recovery.img and boot.img, I used a version of Carliv Recovery and the Be Touch 2 boot.img found through needrom and it worked perfectly.
I was also able to install Xposed Framework by changing the Android version from 5.1 to 5.0 in prop settings (using BuildProp Editor) - which is fine since most say it's fake 5.1 anyway.
Does anyone know whether people have successfully installed custom roms to the Be Touch 2? I find the stock ROM laggy - more so than it should be - but I hesitate to install something like CM or Liquidsmooth without knowing.
Thanks again to the OP!!
Looking for Be Touch 2 Root and Recovery too! Any luck? Thanks in advance!
Download link dosen´t work
Hi, I don´t get the download link to work. I only gets the error code "403 forbidden". Can you please upload the files again, thanks.
[edit] Got it working, was just my antivirus that was blocking it for some reason
It worked!!
Thanks alot man.
I have looking for a root to this device since i got it, and now its rooted
I got this working on win10 (and also working on win8/8.1), but what you have to do is disable "driver signature enforcement". Check this vid if you don´t know how (youtube.com/watch?v=PAxTCvRmlio)
Please make a video
Please Im really new to rooting I have always had iOS and I would really appreciate it if anyone would like to make a video tutorial
Error while trying to root Be Touch 2
Hi,
After following http://forum.xda-developers.com/android/development/recovery-ulefone-touch-lollipop-t3132204 i get to the download part after selecting boot and recovery.
BDROM ERRPR : S_DL_GET_DRAM_SETTING_FAIL (5054)
[EMI] Obtain DRAM Failed!
[HINT] : Please check your load matches to your target which is to be downloaded.
And now the phone won't boot. It does detect when the battery is removed on com15, can I use any other tools to at least boot the phone?
all0gIc said:
Hi,
After following http://forum.xda-developers.com/android/development/recovery-ulefone-touch-lollipop-t3132204 i get to the download part after selecting boot and recovery.
BDROM ERRPR : S_DL_GET_DRAM_SETTING_FAIL (5054)
[EMI] Obtain DRAM Failed!
[HINT] : Please check your load matches to your target which is to be downloaded.
And now the phone won't boot. It does detect when the battery is removed on com15, can I use any other tools to at least boot the phone?
Click to expand...
Click to collapse
Or to download the correct files?
Fingerprint scanner
Does this include functionality for the fingerprint scanner of the ulefone be touch 2 or nah?
I cant seem to find anything on this thing. My searches keep bringing up other Alcatel devices or the Oneplus 3T. I got this tablet from tmobile for free and I was only planning on using it to mirror in my cars android auto.
I have tried kingroot and the process just sits at 1%
Please let me know if you need any other tablet information.
its running android 8.1.0
model 9027W
If for some reason this cant be rooted does anyone have any cheap tablet suggestions that can be rooted easily?
I have tried every method suggested to root mine and nothing. There is an update that i need to charge tablet up so i can install and will attempt them all again. I am running a samsung SM-T357T that is rooted and twrp installed till I can root this tablet . Hope to be soon.
CaptainJager said:
I have tried every method suggested to root mine and nothing. There is an update that i need to charge tablet up so i can install and will attempt them all again. I am running a samsung SM-T357T that is rooted and twrp installed till I can root this tablet . Hope to be soon.
Click to expand...
Click to collapse
I would like to see this as well. T-mobile really locked this device down and even took away the built in call kit as it's VOLTE.
Would SP Flashtool work as it's a mediatek device ?
Likewise searching for a means to root my Alcatel 37 9027W. T-mobile seems to have modded the android 8.1.0. in such a way
making it impossible to remove or otherwise stop google news feed running constantly in the background.
Sure would be nice to root this puppy.
pls have anyone found a solution to root this phone?. i'm trying to unlock. but everytime i use sigmakey,once its get to 'unlocking', it shows phone servicing has stopped and the software exits its self. or do anyone know any other solution for unlock that does not include rooting?
Same!
Interested in a way to get rooted for the device.
mariojohn said:
Interested in a way to get rooted for the device.
Click to expand...
Click to collapse
stephan6 said:
pls have anyone found a solution to root this phone?. i'm trying to unlock. but everytime i use sigmakey,once its get to 'unlocking', it shows phone servicing has stopped and the software exits its self. or do anyone know any other solution for unlock that does not include rooting?
Click to expand...
Click to collapse
moonhop7 said:
I would like to see this as well. T-mobile really locked this device down and even took away the built in call kit as it's VOLTE.
Would SP Flashtool work as it's a mediatek device ?
Click to expand...
Click to collapse
Guys please, I need urgent help, I tried flashing gsi, but they didn't boot, I forgot to take a backup earlier, and the device is kind of bricked now, can anyone please provide me with the stock rom, it's a request please..
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
This works but we need a custom recovery or rooted boot image.
I was able to get a permanent root through a link to a reply on that thread.
Follow the instructions here: https://forum.xda-developers.com/an...atek-armv8-t3922213/post79626434#post79626434
I haven't fully tested the extent of the root, but I was able to get a prompt, root checker confirmed root, and Magisk is reported as installed. Obviously this will not unlock the bootloader or allow for a custom recovery (that I know of) so we will have to wait until someone can get fastboot working on this device for that.
Concur. Root works!
I used this tablet today . Very slow and laggy. Defiantly needs a new rom. Has anybody been able to flash any modules through Magisk or remove any of the T-mobile bloat ?
Found this thread looking for a root method for my Joytab. I just disabled the "Modify system settings" and " Draw over other apps" settings for Smart Manager and my Joytab is definitely way less laggy. No root required.
no twrp for 3t8?