ok , confused a bit here. have a pixel3a (android 10) bootloader unlocked and all files DL'd and ready to go.
but i read that the stock kernel doesnt support twrp. true or not?
any help please. thank you ,
dave
As far as I know, TWRP does not support Android 10 or 11.
TWRP definitely does not support the stock 3a kernel. This is because TWRP has to be compressed in order to be installed. The kernel needs to support LZMA compression which the stock kernel does not. Something like the EX Kernel does support LZMA compression, so you can use it.
That being said, as far as I know, TWRP is not officially supported on Android 10 or 11 (or obviously 12). I've read that some people have been successful in getting it to work on Android 10, but I haven't tried it myself. It's also something that hasn't been widely talked about or adopted, so I have to assume there are still some issues.
mrrocketdog said:
ok , confused a bit here. have a pixel3a (android 10) bootloader unlocked and all files DL'd and ready to go.
but i read that the stock kernel doesnt support twrp. true or not?
any help please. thank you ,
dave
Click to expand...
Click to collapse
If you update to Android 11, there's a TWRP build you can use.
@Captain_Throwback decryption of data partition is supported, too?
AndDiSa said:
@Captain_Throwback decryption of data partition is supported, too?
Click to expand...
Click to collapse
Of course.
Related
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
dark_prince said:
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
Click to expand...
Click to collapse
Thanks for your reply. That surprises me that there still isn't an miui 8 developer ROM out yet for this device. Probably shall never come in that case.
Good to hear that f2fs is supported by cm14 though. Will certainly be running this once I receive my new cases to replace the girly pink cover my mi4c currently houses
danbrown162 said:
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
Click to expand...
Click to collapse
Just flash miui 8 from xiaomi.eu ones. It supports flashing via twrp.
TLDR
anyone get twrp 3.4 working with android 10? twrp released version 3.4 which supposedly supports android 10 and pixel 3a is a supported device. i flashed twrp and now twrp boots but nothing else does. its not a problem i can give it a try again just wondering how other people flashed it and got it to work.
long version:
TWRP released version 3.4 which supports android 10! yay im all happy and crap because pixel 3a is supported so i flash a kernel that supports LZMA compression. (i installed elemental x for android 10) and now i meet all the requirements. go to boot the .img file like they say using fastboot. i typed into ubuntu terminal "fastboot boot twrp3.4sargo.img" i get "error verifying the received boot.img: invalid parameter" this is the same exact error when booting older twrp recoveries because they arent compatible with android 10. not a problem though i thought! i have ex kernel manager so i can flash the twrp zip file through there! (thats what twrp website tells you to do if twrp had booted anyways so i thought well maybe i can skip that step since it isnt booting anyway and just flash the damn file) so i open ex kernel manager and flash the zip file! twrp boots im all happy and then i go to reboot and S#!+. nothing boots except twrp. anyone have any ideas on getting this to work since supposedly pixel3a android 10 is supported now?
Whenever Ive seen that error it means its not recognizing the partition youre trying to flash. Try adding the "a" or "b" after boot. So fastboot boot boot_a or boot_b depending on which is the active partition.
All this said, what are you trying to flash? A patched boot image or TWRP? If TWRP then you dont want to flash it to the boot partition, that goes to recovery.
Have you ever had to flash a full factory image of Android 10 (not just an OTA update)? TWRP will only work on Android 10 if the device was updated from Android 9 and still retains it's Android 9 file structure. I'm wondering if the file structure gets changed to the regular Android 10 file structure when you flash a full factory image vs an OTA update from Android 9 to Android 10 - I'm betting that it does. This would mean that TWRP would not work.
I honestly didn't even know this was released and I will try to install it on my 3A XL later today. I have flashed an Android 10 factory image since I moved from 9 to 10 via an OTA update, so I guess I will be able to test my hypothesis.
ctfrommn said:
Whenever Ive seen that error it means its not recognizing the partition youre trying to flash. Try adding the "a" or "b" after boot. So fastboot boot boot_a or boot_b depending on which is the active partition.
All this said, what are you trying to flash? A patched boot image or TWRP? If TWRP then you dont want to flash it to the boot partition, that goes to recovery.
Click to expand...
Click to collapse
Sorry been busy didn't have time to check this. I did try to flash to recovery. Flashing to boot was a typo. Same error result though. I'll try the a b partition thing later.
sic0048 said:
Have you ever had to flash a full factory image of Android 10 (not just an OTA update)? TWRP will only work on Android 10 if the device was updated from Android 9 and still retains it's Android 9 file structure. I'm wondering if the file structure gets changed to the regular Android 10 file structure when you flash a full factory image vs an OTA update from Android 9 to Android 10 - I'm betting that it does. This would mean that TWRP would not work.
I honestly didn't even know this was released and I will try to install it on my 3A XL later today. I have flashed an Android 10 factory image since I moved from 9 to 10 via an OTA update, so I guess I will be able to test my hypothesis.
Click to expand...
Click to collapse
Did you ever get it to work?
AudibleDruid said:
Did you ever get it to work?
Click to expand...
Click to collapse
I haven't tried yet. Honestly I'm not very motivated either. I'm 99.9% sure it won't work (because I have flashed a full factory image of Android 10 since taking the OTA update) and I don't feel like getting myself into a situation where I might have to reset my phone. I realize it shouldn't go that far, but the "reward" simply isn't worth the risk for me right now.
The Pixel-3a partition scheme was updated when upgraded to Android 10, i.e. the Pixel-3a is an exception to the rule that a device launched with Android 9 is compatible with TWRP 3.4. The Pixel-3a having Android 10 has the same structure like a device directly launched with Android 10 and so TWRP 3.4 will not work.
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
shatheone said:
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
Click to expand...
Click to collapse
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
timba123 said:
Did you figure it out
Click to expand...
Click to collapse
yea
wait that wasn't a question for me...lol
TWRP is not required in order to root the MaxWest Nitro 5P. In fact, you could not root it using TWRP even if you wanted to. This device ships with Android 9 Pie Go Edition and is fully Project Treble supported. Also, like many devices of its kind with a System-as-Root (SAR) configuration, this phone has no boot-ramdisk. The only workaround to attain root is to patch the ramdisk in the recovery image and flash the patched image to /recovery versus the typical /boot partition. This effectively enables Magisk to hijack the recovery partition. Thus, the tricky part. In order for root to be properly installed, the phone must manually be booted to recovery mode during each and every reboot. However, it won't actually boot into recovery mode due to Magisk hijacking the /recovery partition. It will boot into the Android OS with Magisk systemless root installed. If you choose to boot the phone normal, it will still boot into Android, but without Magisk installed. This is rather unorthodox and inconvenient but it remains the only solution for these devices with no boot-ramdisk. For more info on Magisk running in recovery, see the official GitHub documentation here: https://topjohnwu.github.io/Magisk/install.html
TWRP is not compatible with this type of install and will cause a bricked device. Simply unlock the bootloader, patch the stock recovery image with Magisk, and flash the patched image to the recovery partition via fastboot. Boot to recovery mode during the next and every subsequent reboot. I am presently drafting a rooting guide on this device and I will post my link here when finished, for anybody needing instructions.
The OP of this thread originally requested info on root for purposes of possibly installing a custom ROM. Indeed, there are a few Treble GSI ROMs compatible with the Nitro 5P (ARM, A-Only). However, you do not need to have a rooted OS in order to install GSI custom ROMs, but only an unlocked bootloader. I will compile some resources for compatible GSI Treble ROMs and list this info in my rooting guide coming soon. TWRP isn't needed for GSI installation. Everything can be done in AP Fastboot Mode. I am not certain if MaxWest Telecom has released the kernel source code for the Nitro 5P. I will research this. This code will be required for the compiling of custom ROMs such as LineageOS & Pixel Experience. It is likewise needed for TWRP to be built from source.
No problem. I'm certainly not saying that TWRP cannot be booted or even installed on the Nitro 5P. I'm only stating that under no circumstances can the Nitro 5P (in its stock configuration, at least) be rooted using TWRP. The only root solution -- due to the boot image being devoid of a ramdisk -- is the method I outlined above. Now, if someone compiled a custom boot image with integrated ramdisk, this would certainly change matters. Out of curiosity, have you tried flashing TWRP to the /recovery partition using fastboot flash recovery twrp.img? Or, in the alternative, you can replace the stock recovery image with TWRP by decompiling the .pac firmware package, repack the .pac archive, and flash TWRP using the Spreadtrum Flash Tool. I'm just curious as to whether anybody has tried that.
timba123 said:
I finally got a decent laptop. Windows 10. I'd love to root this nitro 5p. IDC if it's superuser or magisk root. I could take or leave twrp.
Click to expand...
Click to collapse
Magisk is the only supported root solution for this devices
Installation
The Magic Mask for Android
topjohnwu.github.io
Scroll down until you reach the installation heading titled "Magisk in Recovery." Follow those steps and you will attain root on your Nitro 5p. In a nutshell, you will be patching a stock recovery image versus a stock boot image. Magisk will be able to hijack the /recovery partition and enable systemless root on the Android OS.
hellofriendlymanveriosns said:
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
Click to expand...
Click to collapse
Why would you want somebody to PM you in order to get help? This is a custom Android development community. Provide your input openly on the thread so it can benefit all others who need help as well.
hellofriendlymanveriosns said:
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
Click to expand...
Click to collapse
Keep in mind that you rarely ever need to be rooted in order to install a custom ROM. However, you will need a custom recovery and the custom ROM itself. To the best of my knowledge, no custom ROMs have been ported to, or compiled for, the Maxwest Nitro 5p. However, the Nitro 5p is Project Treble supported, meaning you can boot and install a Generic System Image (GSI). There are a nunber of custom GSI ROMs available here on XDA, which have been build by various developers. This is a link to several GSI ROMs built from some of the more popular custom ROMs, i.e. HavocOS, LineageOS, ArrowOS, PixelExperience and others. These are available both with and without GApps, in both 32-bit and 64-bit architectures.
[SUMMARY][PIE GSI] BEST PIE-GSI ROMS to TRY (to this moment)
As we(in the TG group) have tested a bunch of Pie9.0 (s)GSI Roms on the XDA forum (https://forum.xda-developers.com/project-treble/trebleenabled-device-development) I was asked to make a guide/summary of what there was already been tested and in...
forum.xda-developers.com
Also, this is the official Project Treble forum here on XDA. This includes numerous GSI ROMs in various versions, instructional guides, device-specific resources and a ton of general info on Project Treble.
Project Treble
The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond.
forum.xda-developers.com
shatheone said:
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
Click to expand...
Click to collapse
I've tried unlocking the bootloader with no success.
For members having difficulties unlocking the Nitro 5P bootloader, you need to use the Token Identifier method typical to Unisoc (Spreadtrum) devices. There is a comprehensive YouTube guide on the process.
You will need a modified fastboot tools build, A Linux PC (or Windows PC running Ubuntu Live), and ADB Debugging/OEM Unlocking enabled in Developer Options. Links for the files you will need can be found here https://forum.hovatek.com/thread-32287.html
To the best of my knowledge, this is the only viable method for unlocking the bootloader on the Nitro 5p.
timba123 said:
I had trouble originally but a fellow xda member ma
I had trouble but someone here made a token for me. I'm bl unlocked for sure. I'm going to try to magisk root this weekend. The specs are poor on this device (nitro 5p) but is gsi/treble compatible . So I plan on trying that but in the end I'll prob just debloat stock to be as vanilla as I can and also add custom audio.
Click to expand...
Click to collapse
Viper4Android FX with the NEON audio drivers works quite nice on the 5p. A good debloating and some build.prop tweaks to optimize RAM efficiency and responsiveness made a big difference for me. You can also add a line to build.prop to disable the boot animation during boot up, which speeds up boot time considerably. Use Kernel Adiutor-Mod (APK available here on XDA) to enable Touch Boost under CPU settings and change the CPU Governor to Performance. Set I/O scheduler parameters to a 512 KB read-ahead on internal storage, using the noop scheduler preset. Set SELinux to permissive mode as well and use the Low Memory Killer (LMK) preset of Very Aggressive. In the ZRAM options, ensure Swappiness is set to 100.
Keep in mind that when rooting, you will need to install Magisk to run in recovery versus the typical boot.img patching.
I installed LineageOS 18.1 (Android 11) on my OP7P and want to boot (or flash) TWRP.
There is a lot of different information about the state of TWRP on Android 11.
I hope someone could clearify the following questions:
1. Does TWRP [3.5.2] support Android 11?
the release notes of 3.5.1 state that they "prepared a mini release before Android-11 support."
The release notes of 3.5.2 don't mention android 11 at all.
There are various people in the LOS18.1 thread that can boot twrp, so I assume there is some kind of (partial) support.
2. What if 'fastboot boot twrp.img' doesn't work?
For me I can't boot (or flash) TWRP (on LOS18.1).
So as the twrp/lineage os guide says I do:
fastboot boot twrp.img
Click to expand...
Click to collapse
It finished succesfull, but my phone stays in fastboot and doesn't reboot.
The TWRP guide says the following:
If fastboot boot command doesn't work you need to root your device and flash the TWRP installer (remember that flashing the TWRP installer you will lose the root).
Click to expand...
Click to collapse
I find this a very vague description; what do they mean with "doesn't work"?
(when I flash twrp it results in an unbootable phone, might be related to a/b partitions, but I have not enough knowledge of that)
3. Does TWRP work on encrypted phones?
I found various posts that suggest that TWRP doesn't work on encrypted phones.
I can't find any reliable source that supports that statement.
Twrp says this, but that doesn't clearify things at all.
I hope someone could give me some answers, or guide me to some reliable source so I can find it myself.
I find the documentation of LineageOS and TWRP lacking in that perspective.
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
lenigma1too said:
For question 1, there's no official TWRP for 11.... YET.
Question 2 - I'm thinking cause TWRP doesn't work for 11, that's your issue.
Besides that, if your trying Android 10(because you don't mention what version your using in question 2), I would suggest re downloading, as that process works fine for this phone I'm typing this reply to you on.
Question 3 - I'm sorry, I've got ideas, but it's above my pay grade... So no hard knowledge I'm comfortable calling advice, to give a fellow OP7P owner.
Click to expand...
Click to collapse
I also think there is no official TWRP for android 11, but twrp doesn't make this very clear in their docs.
Multiple people are claiming they are able to (at least) boot twrp on Android 11.
LineageOS 18.1 is Android 11 (but I will clearify the post).
Thank you for your reply
there is now a working TWRP version for Android 11.
Nebrassy version: https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
worked for me with 'fastboot boot TWRP-3.5.1-guacamole-Nebrassy-3.img'
Hi! Are there any pro’s out there that can help out with some issues, we are having with 3 phones.
It would be greatly appreciated. I believe we are not the only ones.
How can a BOOT.IMG be extracted from an Android Phone if there is no Stock Firmware ROM available?
All 3 phones manufactured in 2022.
The Bootloader is unlocked for all 3. USB Debugging is turned on.
- Moxee m2160 MH-T6000 only boots to Fastboot & Recovery. I have tried to restore but it will not restore.
- Vortex V22 has a GSI Pixel Experience Plus 13 ROM installed and is unable to go back to factory ROM image.
- ANS ACK2326 is on a stock Android 12 ROM and hasn’t been modified but has a build number kirk2_v1 2.0_BTM-ST.
Is it possible to get a Generic BOOT.IMG to modify for root?
Are there other ROMS like GSI’s with a BOOT.IMG that could work to try to get root?
Are there other ways to get root without a BOOT.IMG?
Is there a way to parse the entire phone to compile a BOOT.IMG?
The manufacturers were contacted. No system firmware ROM is available online that we could find after searching. We don’t have any experience searching china websites or know where to begin. If someone knows where we could find the stock ROM's on a China website that would be a great help!
Are we SOL? Are phones that don’t publish stock firmware that secure that if you need a BOOT.img from stock firmware to get to access the entire encrypted rom, you are out of luck?
Or, would we need a Jtag hardware reader?
Thank you in advance for your time and help which is greatly appreciated!
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
V0latyle said:
The boot image contains the kernel for that specific device; there is no such thing as a "generic boot image", as the kernel has to have the basic drivers for that specific device's hardware.
It's possible to dump the boot image if you already have root, but I'm assuming that the whole reason you want the boot image is to patch it with Magisk to gain root.
The alternative, if TWRP is available, is to use ADB through TWRP to dump the boot partition.
If you can't use TWRP and aren't rooted, there is no way to dump the boot partition through fastboot.
Click to expand...
Click to collapse
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
defcondoc said:
Thanks you for the reply! That is correct. Our ultimate goal is to gain root on these devices. Is Magisk the only root pathway or are there other rooting options?
Click to expand...
Click to collapse
No, but it is the most popular and arguably the best
defcondoc said:
Can you use ADB Shell, ADB root and dd to pull the boot partitions?
Click to expand...
Click to collapse
No, because again you need root to run adbd as root. I could be wrong...
defcondoc said:
There is not a TWRP available for these devices. How would you go about making a TWRP for these phones? Do you need the stock firmware?
Click to expand...
Click to collapse
I am not a developer so I have no idea but I imagine you'd need the original kernel source, yes.
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
kelvinchinedu said:
If u have mtk there are many options
1:using mtk client
2: using mtk bypass and wwr2
Then if u have snapdragon u need the gfil software and the phone firehose programmer
Click to expand...
Click to collapse
I actually had or was going to ask this if there is a way to access firmware from the hardware level. Somehow the post never got posted or deleted.
Anyway, with MTK Client & QFIL, how complicated is it to extract the firmware from a device? Will it work with all devices, or will I run into issues with newer devices? I will do some researching on these and see what I can find. Thank you!
alecxs said:
another risky way is to flash rooted GSI. but in case it boot loops, you are screwed without stock ROM. the user @gregeerg ended up with a semi bricked phone, luckily he was able to pull boot.img from adb, so another member @Jet! with same device could finally root his phone and provide super.img for unbrick. So this method is only working if you have two identical phones.
Click to expand...
Click to collapse
Interesting. Where can I get a rooted GSI? I tried to searching but couldn't find anything. Is there a special way to search for one. I would be willing to try this. I had a boot loop on one and a unofficial unrooted PixelExp13 GSi fixed it.
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you! I'm assuming these are all GSI builds from LOS 16-20? Am I also correct in saying the difference in the bgN, bvN, bvS, files? b = a/b system, g = gapps installed, v = vanilla - no gapps installed. N = No Root? S = Root?
To get a GSI that is already rooted, I must install the file with S in the filename?
alecxs said:
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
defcondoc said:
OMG Thank you alecxs! Bravo! This is exactly what I was looking for! One install with no stock ROM rooted successfully!, two more to go. And especially thanks to andyyan for making this GSI image possible!
Click to expand...
Click to collapse
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
omb714.1980 said:
May I ask you which of your devices listed above did you get it to work on the reason I ask is I have 2 of those phones am I'm trying to do the same thing. Thanks
Click to expand...
Click to collapse
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
defcondoc said:
The Vortex V22 I got to work successfully with a GSI root. I was able to get root with the Moxee but I have yet to get a custom rom or working GSI rom. I'll post when I get a working rom with the Moxee. The ANS has been a bit of trouble because I cannot get the BL unlocked even though it has OEM unlocking turned on.
Click to expand...
Click to collapse
I'm having the same issue with the ANS your not alone.
omb714.1980 said:
I'm having the same issue with the ANS your not alone.
Click to expand...
Click to collapse
I appreciate you letting me know. Good to know I'm not the only one.
Did anyone ever figure out how to unlock the bootloader yet?
ronnieshane1 said:
Did anyone ever figure out how to unlock the bootloader yet?
Click to expand...
Click to collapse
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
defcondoc said:
I do know it is available somewhere and most likely password protected but to my knowledge it hasn't been made publicly yet. I'm still waiting as well. I've be able to do some workarounds with the stock rom but I would really like to get access to the firmware or boot image.
Click to expand...
Click to collapse
I know right! I cant find hardly anything on the ACK2326 at all! I wish they would go ahead and make it public already.