Related
So I recently bought myself a Nextbook Ares 11A (you can get look at it here: http://www.nextbookusa.com/productdetail.php?product_id=33
For the life of me, I can't figure out how to root it at all. Anyone have an idea how to root it. I have tried King and Kingo root, both PC versions. Vroot/iroot, framaroot apk, and some others that i kinda forgot.
One of the first things I did to this tablet was upgrading its android version to 6.0.1
I think one of the main exploits to use for this would be the firmware update
-quick note. If your having problems with this tablet rebooting by itself re download the android 6.0.1 firmware update and install it again.
Firmware update download: https://goo.gl/Cev80L
Same here. Can't root it. Awesome tablet for the price just $197 for a 11 inch tablet running Android 6.0.1 Marshmallow. Here are my specs. Hope e can find a root soon. Boring without root access. No cool apps without have root.
Netbook Ares 11A
Model# NX1611264
Running Android ver. 6.0.1 Marshmallow
Security patch level 2015-11-01
IFWI ver.
Build # V1-1.9.LMY47I.20160803.154546
Kernel-3.14.37-X86_64-L1-R517
I am so glad some of the community is interested in this.
can you post a copy of the update? ive been having a hard time gettin the update.zip to fully dl
mrspinler said:
can you post a copy of the update? ive been having a hard time gettin the update.zip to fully dl
Click to expand...
Click to collapse
no problem. ill do that when i get home from school today
GRIMMMMS said:
no problem. ill do that when i get home from school today
Click to expand...
Click to collapse
ty
also any luck actually rooting this tablet? ive tried but the device isnt recognized by the fastboot drivers.
however adb recognizes it when it is actually turned on normally wich is weird.
mrspinler said:
ty
also any luck actually rooting this tablet? ive tried but the device isnt recognized by the fastboot drivers.
however adb recognizes it when it is actually turned on normally wich is weird.
Click to expand...
Click to collapse
No I really havent had any luck wth any pc rooting software's or apk viersons. I tryed all the ones I trust. And i dont really know how to root a divise other than using the software.
mrspinler said:
ty
also any luck actually rooting this tablet? ive tried but the device isnt recognized by the fastboot drivers.
however adb recognizes it when it is actually turned on normally wich is weird.
Click to expand...
Click to collapse
here you go. the dl :https://goo.gl/Cev80L its from google drive
i installed the update and my tablet doesnt make it all the way through and is stuck on logo screen its the same model as op ..looks like i cant go back in firmware cause the older firmware says bad footer
nextbook ares 11 a
After installing the correct adb/fastboot drivers along with the intel chip usb drivers, i was able to unlock/flash boot.img and bootloader. All i need now is a working twrp_recovery image to finish rooting this tablet and remove encryption. If anyone has a working twrp recovery or knows how to make one based off the rom, then please post it. I would love to have this tablet rooted and non encrypted.
11a
i have the same tablet is there anyway you could send a copy of firmware or the stock recovery @mrspinler
look-up vampiro's work on the ares 8, he has made a twrp that will work, with a mouse connected to the ares 11, the are a few modified roms for the ares 8, including a remix os, that works great, except for touchscreen doesn't work, but touchpad, and attaching a mouse works great
nextbook ares 11 a
tim121283 said:
i have the same tablet is there anyway you could send a copy of firmware or the stock recovery @mrspinler
Click to expand...
Click to collapse
tim i am sorry but i am unable to give a stock recovery seeing as i tried to flash other recovery images. however i would be glad t post the update file but i can't post links yet. The update file is in the very first post, and you have to unzip it onto the sd card to get the tablet to notice it.
If you are familiar with rooting android then perhaps you could provide the stock recovery image so that someone with more programming knowledge can actually make a cwm or twrp recovery from it. The boot.img file is correct as well, which happens to be inside the update file. I know this because i almost bricked my tablet XD.
---------- Post added at 03:14 AM ---------- Previous post was at 03:09 AM ----------
thew-tab said:
look-up vampiro's work on the ares 8, he has made a twrp that will work, with a mouse connected to the ares 11, the are a few modified roms for the ares 8, including a remix os, that works great, except for touchscreen doesn't work, but touchpad, and attaching a mouse works great
Click to expand...
Click to collapse
Have you been able to root this tablet with the ares 8 files? If so then how did you get the recovery.img to work and what about the encryption files? I ask because the ares 8 has the same cpu but it is android 6.0.1 rom versus android 5.0/5.1.
11a
heres the deal i downloaded the update on the first page and always got stuck at like 35 percent tried to flash the recovery from the 11rootkit it didnt work tried from the ares 8 and just get an error screen ive got the tablet unlocked fully and can flash anything in fastboot but no file at all with bring it back ive tried the firmware files and there not in the right format for fastboot the tablet is bricked but can still get into fastboot but no working recovery
mrspinler said:
After installing the correct adb/fastboot drivers along with the intel chip usb drivers, i was able to unlock/flash boot.img and bootloader. All i need now is a working twrp_recovery image to finish rooting this tablet and remove encryption. If anyone has a working twrp recovery or knows how to make one based off the rom, then please post it. I would love to have this tablet rooted and non encrypted.
Click to expand...
Click to collapse
i have no idea
if you ever get it done please come back and help us get ares rooted XD
If anyone can manage getting a copy of recovery.img off your tablet, please post it. I will try and make a twrp img with it. Hopefully a dev can pick this up cause I am sort of out of my league atm.
I'm very interested in this endeavor. I have a Ares 11A as well but I'm in desperate need of a stock ROM as mine got trashed by the Marshmallow update. As a result I had to install Win 10 on the device temporarily, but i would like to get it back to the original stock ROM and try again. If that fails, then I'm going to have to build an entirely new ROM (never done this before) based on Android-x86 Marshmallow.
What's really sad is that support for this device is sorely lacking from the vendor(Efun/Yifang). They don't even post a stock ROM on their website (nextbookusa.com) for this device. However, this device is similar to some of the Chinese tablets posted on techtablets.com so I MAY be able to find a stock ROM / drivers there.
baharvey7817 said:
I'm very interested in this endeavor. I have a Ares 11A as well but I'm in desperate need of a stock ROM as mine got trashed by the Marshmallow update. As a result I had to install Win 10 on the device temporarily, but i would like to get it back to the original stock ROM and try again. If that fails, then I'm going to have to build an entirely new ROM (never done this before) based on Android-x86 Marshmallow.
What's really sad is that support for this device is sorely lacking from the vendor(Efun/Yifang). They don't even post a stock ROM on their website (nextbookusa.com) for this device. However, this device is similar to some of the Chinese tablets posted on techtablets.com so I MAY be able to find a stock ROM / drivers there.
Click to expand...
Click to collapse
I'm in the exact same situation how did you get windows to boot?
tim121283 said:
I'm in the exact same situation how did you get windows to boot?
Click to expand...
Click to collapse
Basically, I deleted the Android partitions and reallocated the space a a Windows partition. I got into the device UEFI boot manager by pressing the power + Vol down buttons, then releasing the power button when the Nextbook logo appears, then release the Vol down button. It's a little tricky to get into it but it can be done. Before you attempt to do so you have to get the device into fastboot mode (power+vol up buttons) and unlock the bootloader first. Be advised though that finding Windows 10 drivers will be VERY difficult! It's not for the faint of heart! I went to the techtablets.com website to find the drivers as they specialize in supporting Chinese-made tablets.
As I've stated earlier this is a temp solution. When all is said and done, this will become a dual-boot or multi-boot tablet
this is the only thing i can find but cant get it right http://www.nextbookusa.com/_gendownloads/NX16A11264/update.zip
Good afternoon everyone.
I got interested in putting a custom rom on my Galaxy Note 8 I have laying around (Current Daily driver has been upgraded to a Note 20 Ultra so I have no hurry to fix this issue.)
I followed the steps from one of the forum guides and installed TWRP, the first thing I noticed was that my Note 8 had 2 System directories while this is supossed to be a A only model. (Which struck me as odd.) After installing a android 11 Rom (A Only) I was stuck on the boot screen not loading any further. I found this logical as Android 11 is not really supported as of yet on this model.
I then decided to grab Havoc OS seeing as that was a stable version that should run properly i've seen people on Youtube install it on their S8's without a hitch. After installing this the way the guide told me I got stuck in a boot loop. (Also used an A only ROM) My final attempt will be downloading an A/B ROM and see if that works (Which i genuinly doubt.) but will update this post when that's finished.
On the post I also have added a screenshot of what I see when trying to install an Image. My question to you guys is, does this phone have a A/B configuration after all or am I doing something wrong?
Edit: AB was also not the solution.
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
QuirkyTechGuy said:
After rummaging around a bit more with the phone I found out that i was using an extremely out of date version of the Pie Vendor. I looked at download by Version number instead of by date. Reinstalled Havoc, installed pie vendor.
Now the phone reboots into downloading mode. It's been this way around 10 minutes now will post an update in about an hour or so of leaving it in that state.
Click to expand...
Click to collapse
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
maxed4901 said:
Odd. Truly. It could be due to the first install of GSI version. Here's what I suggest.
I hope u have a back up of your old rom, if so, flash it back. If not, check your twrp version. Update it to latest. Flash a non gsi rom. Boot the phone. If it boots and you have it running, then flash a gsi rom .
Click to expand...
Click to collapse
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
QuirkyTechGuy said:
I sadly forgot to make a back up of the rom which in hindsight is stupid of me. I did check and have the latest TWRP version, and managed to get LineAge OS 17.1 working without it being Treblized .
Should i now go on with the procedure of trying to flash a GSI rom with the Treble Convert?
Click to expand...
Click to collapse
Let's take a back up first and then try. Which tutorial are u following.
Install Android 11 (R) On Any Treble Device ( Detailed Guide)
This way you can install Android 11 On any device without the need of waiting for your manufacturer to push the latest update.
xtremedroid.com
And try Google or aosp gsi from here https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Here's @corsicanu thread for instructions.
But it's for android 9? M not sure though
[AOSP][Treble][G95*F/FD] hadesTreble [03.09.2019]
Disclaimer I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it...
forum.xda-developers.com
I see that XDA is filled with threads that leave a lot of loose ends. I did not see anyone post this yet, but there is an MSM unbrick tool for this model, hidden in plain sight (I will be testing it some time tonight):
Index of /list/Unbrick_Tools
You'll also need the Quantum drivers, duh...
https://drive.google.com/uc?id=1zKPFtcc2X_Nf70mcvn9TBu60bHl6Q3cP&export=download
I miss the good ol' days when we could flash a K20 Plus without having to do backflips. These new devices are awful. Anyway, once I unbrick this piece of junk I may get adventurous enough to try and install Lineage, again. I suspect that trying to install it when 12 was already on had something to do with it. Will try to use MSM to put 11 back on (it is softbricked in a loop but I can at least get into fastboot, so we'll see).
I'm soft bricked but got into fastboot by pressing all three buttons simultaneously to turn the phone on.
I would LOVE to have a vintage android version on here, back when things were fast and simple. I'm not yet talented enough to make that happen. My only real experience is with Mr. Travis Holt's K20 roms back in the day. They worked so well that I'm considering just buying an old K20 again and being done with all this new stuff. It's quite a disappointment.
Gonna get back to unbricking, flashing and ripping my hair out. Wish me luck.
averyboringusername said:
I suspect that trying to install it when 12 was already on had something to do with it.
Click to expand...
Click to collapse
Yes absolutely. The lineage install page warns that you must be on android 11 https://wiki.lineageos.org/devices/dre/install
Warning: Before following these instructions please ensure that the device is currently using Android 11 firmware.
Click to expand...
Click to collapse
They even make you click a button to acknowledge that you've read the warnings before they show the install instructions.
There is also a thread in this forum warning people
Downgrade US OEM (DE2117) Android 12 firmware to Android 11 BEFORE installing Lineage!
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to: DE2117 OEM...
forum.xda-developers.com
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
Click to expand...
Click to collapse
I'm sorry, but how many more warnings do you want?
Search the forum on how to recover the softbrick.
Hi
Quite bored of Oneplus updates for my Nord 2 5G that transforms more and more the phone in publicity support for OnePlus CEO messages, and adding features I don't care at all, I'm looking to flash it with an alternative ROM.
What is most stable and operational ROM for that device currently ? The version of the device I have is DN2103 (bought in Switzerland).
Thanks for your advices,
Vincèn
Tried them all. Evolution X is the most often updated and works the best for me.
Hey there!
I also need some much needed insight in how to continue with this device (DN2103 bought in NL, Europe; just updated from 11.A.14 to 11.A.21). I suspect I will probably need the same answer as OP is looking for.
This is my second OnePlus, I was using a OnePlus X before running my first and only ROM, Lineage OS, to be able to move on to Android 10. Then screen broke for the second time after I had already fixed up the whole phone myself before that using brand new parts (Screen, frame, backplate) except for the motherboard still original. So I decided it was time for a new device.
Really love the DN2103 itself, except for the whole rooting / OTA update process, although it was a good training in getting to know all the technicalities. I had been running rooted 11.A.14 since it came out till yesterday, because I was avoiding dealing with the whole process again.
Anyway I kicked myself under my butt and got myself to 11.A.21 now. I was planning to just continue updating OOS till the latest 11.C.10 / 11.C.13, because after all this effort, I'm too curious to not check out the new Android.
But I just happened to read some thread where people were saying that somewhere after 11.C.4 it's not possible anymore to get into fastboot / BROM mode and thus no means to get TWRP?? That sounds horrible, one mistake rooting and it would be a big mess, having to downgrade to OOS 11 again and bla bla bla, why the f...?
So, I just need to hear this from someone, is this correct? I'm too tired to investigate now myself after a 20h OTA/rooting session behind me and just 3h sleep.
And how is everyone dealing with it that wants root? Has everyone moved on to other ROMs for Android 12 / 13, because of this?
In the update process yesterday for some reason my phone did a complete wipe without asking / warning. So I really need to get to a stage in this update process where I can restore all my ****. I've been at this for 24h right now and was happy to do so as I was making steps. but now I suddenly got hit in the face by this news.
tl;dr PLEASE confirm/deny this news (underlined part above) and help me decide if the only comfortable way is to ditch OOS for a custom ROM to get Android 12 / 13 with root & TWRP. I've thrown 24 hours into OTA updating OOS 11, now got to 11.A.21, but phone somehow got wiped in process, so now I really need to finish upgrading and restore data, because I'm without all the apps / accounts etc. I depend on for daily life.
I do really enjoy the road but now I HATE being lost along the way. Show me the light and, if ROM, same question as OP
Sorry if a bit off-topic + long post...
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
wuttehhell said:
Yes, you need to have android 11 to enter fastboot. I had 12 and had to downgrade. Trust me, this is the most fuked up thing.
Click to expand...
Click to collapse
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Btw, u dont need root to change rom, only if you want. I personally dont use root and works great.
wuttehhell said:
Tried them all. Evolution X is the most often updated and works the best for me.
Click to expand...
Click to collapse
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
wuttehhell said:
Stop waiting for oneplus. There are great roms on android 13 that work very nice. What i am using is Evolution X. Tried them all and this is the one i stick to. Found no bugs, very consistent updates and the team as i see work very fast on every bug people find.
Click to expand...
Click to collapse
Thanks a lot for confirming! I'd already read the thread and indeed Evolution looks like the best option, so that's decided then. Wish me luck flashing the ROM
And about root, I really have some essential mods that need root. For example Advanced Charge Controller (I use it with the GUI app ACCA for convenience, else it's only terminal). I limit my charging by default to 80%, which translates in about a 4x increase in lifetime of the battery. On normal days I don't need any more than that, and it always has the option to charge to 100% if you know you're gonna have a long day without charging capabilities.
vincebay said:
Thanks for the info, and noticed too in forum that it looks to be the most up-to-date and maintained ROM for DN2103 and it looks to have no more any blocking bugs such as Wifi or Bluetooth not working, or random reboots/crashes. I'm running right now version DN2103_11_C.12 with Android 12. Is it ok to upgrade to Evolution X straight ? as I see people speaking about downgrade first to Android 11 :/
Click to expand...
Click to collapse
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Releece said:
As I understand, and as @wuttehhell just confirmed in this thread, once you update OxygenOS beyond Android 11, fastboot and BROM mode don't work anymore. This means you can't install a custom recovery like TWRP to flash a new ROM, neither can you flash it using fastboot.
This means you have to rollback to Android 11 first. Fortunately OnePlus has official rollback packages, which is just a .ZIP archive like any other update, except it will downgrade to a previous version. Warning: a rollback package will WIPE ALL DATA. So make sure to backup anything you need to keep before downgrading. The upside is you can do a clean flash of the ROM (flashing method where device gets wiped), which is the most stable method and gives you a fresh OS that will use less battery and such.
I think the process of downgrading itself is very simple though. If you get stuck let us know, there's many knowledgeable people here lucky for us so keep a positive attitude and with a little luck we'll both be running Evolution X in the coming days!
Click to expand...
Click to collapse
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
vincebay said:
@Releece thanks for the details and so if I have well understood the whole process:
backup datas
Downgrade to Android 11 using the OTA downgrade package and procedure from oneplus (which implies a full reset of device)
Reboot at least one tine in Android 11
Flash TWRP
Reboot in TWRP (be careful not to boot Android or I'll have to reflash TWRP)
Flash Evolution X zip
Boot normally and enjoy Evolution X
Am I correct ? I have seen also that the phone has the same annoying double "bank" when you flash it that I had on previous OnePlus phones. Does it imply I have to do each flashing process on both banks ?
Thanks
Click to expand...
Click to collapse
Yep that should do it, looks like you did your research and understand the process.
I had the same question earlier. Strangely I found that the Nord 2 does not have A / B partitioning. I can only detect an A-partition with apps designed to test it. I didn't have to do anything extra / another way while rooting with Magisk, OTA updates or flashing ROM. I thought A/B was enforced on all phones since Android 10 or sth, but apparently not all.
I would add one extra step, after you reboot into TWRP (before flashing the ROM) make a backup of all the individual partitions one by one (so you can restore any single partition in the future), even the tiniest ones.
Some contain calibration data for e.g. Bluetooth and fingerprint sensor that are specific to your device. Now this whole process should leave them untouched, but if anything ever happens to them, the only way to get your phone working again is to send your phone to a service centre, so it's a good idea to have everything backed up.
They will be stored in the TWRP folder in /sdcard/, which is the folder you can see on your PC. So after backing them all up, you can just copy them to your PC.
I successfully flashed Evolution yesterday, and all went well Initially the new Android 13 UI was a bit of a shock from what I was used to, but I'm starting to like it already, especially after going over the settings. And it works smooooth like butter. The only thing that annoyed me was the haptic feedback, which feels very mushy instead of snappy. But putting vibration strength to low helps a lot. Maybe I can find a way to modify it later.
I had one little hickup: Evolution install instructions say this for TWRP before flashing ROM:
"3. Tap [Wipe] , then [Format data]. type "yes" and Enter"
But when I did this, it removed the media folder at /data/media/ instead of just emptying it. I remember it gave me a pop-up saying something like, for /data/media/ to get populated I would probably need to boot to system. But if I would've done that stock would overwrite recovery.
I don't have a lot of knowledge about this, but this folder gets mounted to /sdcard/ and is where your internal storage is mounted to. So after the wipe I wanted to copy the ROM .zip to my phone using the file manager. Windows did recognize my phone as having internal storage, and I could open it, but it didn't see any file/folder/free space and I couldn't copy anything to it.
I solved it by renaming ROM to sth simple like evolution.zip, placing it inside platform-tools folder, and then using ADB push command, so it looked like:
ADB push C:/platform-tools/evolution.zip /data/
It doesn't give any feedback while copying and I didn't even see much disk usage on Windows task manager, so I was about to get nervous and close the terminal, but then it suddenly completed successfully and I could see the evolution.zip in TWRP file manager. After that flashing took just a few minutes and everything went perfect.
Now I don't know if it's maybe a typo in the instructions or if TWRP had a bug, but I don't think so as it specifically gave me a prompt about it. I think it's better to just tap [Wipe] and then do the usual factory reset slider, with data, dalvik and cache selected. Think I'll make a post later in the Evolution thread to ask.
Good luck!
Hi, I don´t like the colors on Oxygen OS. I don't know if it's cause by our screen or is something related with the ROM. In Samsung or Xiaomi colors are more brilliant and saturated. In Evolution ROM, can you modify this issue?
So I have been able to dowgrade my DN2103 to 11_A20 running Android 11 but I'm stuck there !
Each time I try to flash twrp or load it in device I get that:
[email protected]:~/Bureau$ fastboot boot twrp.img
Sending 'boot.img' (131072 KB) OKAY [ 3.310s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
[email protected]:~/Bureau$ fastboot flash recovery twrp.img
Sending 'recovery' (131072 KB) OKAY [ 3.371s]
Writing 'recovery' FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I have unlocked OEM protection into it and allow USB debug. Any ideas what's the problem ?
damn was a long time I had not done Android flashing so was a little more complicated but made it (well it looks to be so far Will see if it boots after initial setup and now hanging on the Phone initial preparation but should go very soon I think
Thanks
I just can't get it to work. After going through some newbie hiccups, I am able to install TWRP through Odin, but no version of TWRP that I found works. And they all seem to not work in different ways.
Based on the threads here, it obviously worked in the past but either the download links are dead, or the link leads to an archive where the specified version doesn't exist. No knock here, that's normal for old threads anywhere.
So, no TWRP, no root; no root no making the J6 useful. Disappointing, but since the J6 doesn't seem to have ever been supported very well with official versions of anything, I'm not surprised.
Does anyone have any insight or suggestions?
Lol its easy to root using magisk app and ADB without using twrp just follow the instructions from topjohnwu.. also there is twrp 3.6 unofficially made for J6 i have it on hand but i will not share it to protect you from experimenting.. ive been using GSI from 2019 til 2022 and end up realizing its better to stay on stock. Rooted stock is ok but GSI it has bugs..
danicadanicadanica said:
Lol its easy to root using magisk app and ADB without using twrp just follow the instructions from topjohnwu.. also there is twrp 3.6 unofficially made for J6 i have it on hand but i will not share it to protect you from experimenting.. ive been using GSI from 2019 til 2022 and end up realizing its better to stay on stock. Rooted stock is ok but GSI it has bugs..
Click to expand...
Click to collapse
It might be easy for you, but I'd like to make TWRP through Odin work before moving on to something else that I have no experience with.
You have something that might work but won't tell me where to get it because you want to "protect me from experimenting". What do you think I've been doing all this time?
So yeah, lol.
captainjarvis said:
It might be easy for you, but I'd like to make TWRP through Odin work before moving on to something else that I have no experience with.
You have something that might work but won't tell me where to get it because you want to "protect me from experimenting". What do you think I've been doing all this time?
So yeah, lol.
Click to expand...
Click to collapse
Hi Jarvis I use a Samsung J600G as my daily driver with Corvus 17 based on android 11 on TWRP 3.2.3.
Requirements -
Odin installed on your computer.
USB cable
TWRP tar file
To install TWRP -
1. Switch your phone off and hold volume up and down buttons at the same time while connecting your phone to the computer by cable.
2. Open Odin and go to options, switch off auto reboot, now click on AP and select your TWRP tar file.
3. Now after Odin says PASS disconnect the cable from your phone and hold Volume down + power button for 7 seconds and as soon as the screen goes black hold Volume up + power button. This will boot you into your newly installed TWRP.
When it comes to custom roms J6 has some limitations for a few good ones. In my opinion you can install EvolutionX 4.0 (made by @adi_ss) that is based on android 10 as its the easiest rom to install. All you have to do is follow the instructions given by the developer. And there is no need to worry if you mess up somewhere as I have made my fair share of mistakes and still haven't managed to brick my phone.
Thanks for reading guys.