Related
Hi - as a bit of a lark, I picked up an Aoson 7 inch tablet on Amazon Prime day for $65 CDN. I believe it is a MTK8735 device.
( https://www.amazon.ca/S7-Pro-Unlock...8&qid=1500319352&sr=8-1&keywords=aoson+s7+pro)
I was pleased to discover that the developer options allowed OEM unlocking and was - at least as far as I can tell - able to unlock the bootloader via fastboot with "fastboot oem unlock."
That's where I stand - even though the tablet is basically an AOSP build, I would like root access on the thing. I have tried booting a variety of MTK custom recoveries that I have found on xda and other places via "fastboot boot whatever_recovery_I-have_found.img" but, despite accepting some of the recovery images without error messages, the tablet always goes into a normal boot.
I have looked at the magic Twrp for Mediatek devices here on XDA but, since I don't have shell root access, I am unable to let it work its magic. I have also tried some of the one click methods (kingroot, etc.) but have not been successful with any of those methods either.
Are there any other steps that I could be taking at this stage? I am just looking for a little advice.
D
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Kenvarus said:
Basic device info
Model Number : PB1009
Android Version : 7.0
Kernel Version: 4.4.22
Build Number : PB1009_20170912
Hey so i need literally any way to root this tablet, ive been able to unlock the bootloader (easiest bootloader on the planet) but havent been able to find a compatable twrp.
i just need a custom recovery that will work or p much any root ideas, i would consider a full custom firmware as well.
i considered compiling a twrp but i dont know how i would get the source files for it...
Click to expand...
Click to collapse
how did you unlock bootloader and did you ever figure out how to root it? going through same thing now.
Kind of an old thread and old device now, but I own one myself (branded Packard Bell) and just figured this all out, so here goes:
Root
This one is really easy now thanks to a MediaTek flaw. Just go to https://github.com/JunioJsv/mtk-easy-su, download the latest release, install the APK on the device, and run it by opening the app and pressing the button in the lower-right corner (still works on this since the latest security patch level AFAIK is from 2017). Note that this gives root temporarily, so you will need to run it again after reboot if you want root again.
Bootloader Unlock
When Kenvarus said "easiest bootloader on the planet", I took a guess at the method and it worked:
Back up any important data on your tablet, as this will factory reset it.
Install ADB and Fastboot on your computer if they are not installed, including drivers. For Fastboot (as that can be tricky sometimes), it "just worked" for me and I think Windows used an Amazon driver I had installed for my KF2. YMMV.
If you haven't already, enable Development Settings by going to Settings->About tablet and tapping the build number 7 times.
Go to Settings->Developer options (switch them on if they're off) and enable the "OEM unlocking" toggle.
In the same menu, enable "USB debugging" if it is not enabled already.
Connect the tablet to your computer, confirming the authorization prompt that pops up if it wasn't connected before. Check whether the connection is good with the "adb devices" command if needed.
Run the command "adb reboot bootloader", this gave me a blank screen.
Use the "fastboot devices" command to make sure the Fastboot connection works.
Run the command "fastboot oem unlock".
Press Volume Up when the text-mode confirmation screen pops up on the tablet.
Once the unlock procedure is complete, reset the tablet. You should see text on your bootscreen saying "Orange State" and a factory reset on the first reboot if it worked.
WARNING: I highly recommend charging your battery to be at least 10-20% filled before doing this. I stupidly did this at 1% battery thinking "it's plugged in anyway" and had quite the time rebooting after unlocking the bootloader (I thought it was bricked for a good hour or so, only after walking away for 20 minutes to eat dinner did I see that the battery was now at 20% and I could boot the tablet).
After unlocking the bootloader and temp-rooting it with the above app, I was able to use Magisk to patch the boot image (using dd to shuttle the files to and from /dev/block/mmcblk0p10, use "strings saved_boot_partition_name|head -n1" and check for "ANDROID!" to make sure it's the right partition) and I now have persistent root after all these years (note that Direct Install in Magisk doesn't work here). I'd definitely be interested in a custom recovery and/or ROMs for this device, but I'm not holding my breath (I'd take a crack at it if I knew better how to do it, but I have near-zero experience with ROM development and so far have only recompiled existing ROMs for a few phones).
Hello all,
As a frequent user to the XDA Forums but a first-time poster, please allow me, from the onset, to express my gratitude for the litany of assistance this forum has offered. The resources here and pure talent have proven invaluable; from assisting me in actually taking a Nokia Windows Phone and installing Android, bypassing Google's FRP on an LG Tablet to mirroring a broken display and thus saving my S5 Neo. Please accept my humble thanks and heartfelt gratitude. Perhaps one day, I will be able to offer something back to this amazing community. Kindly bear with me as I need to ask you all for some expertise and guidance one again — I have some specific questions — as a segue into the first inquiry, pardon me if this is the wrong subforum.
Question the first. And you have my permission to all point and laugh at me for asking this one: Is this subforum dedicated to a device with a specific label of LG G Pad X 8.0 or is X expressive of a variable employing categorization of many devices? I know how to research, but I still can't find a direct answer or mere suggestion; deduction implies the latter. Specifically, I am enquiring about the LG G Pad III 8.0 FHD (the LG-V522). I do hope X was a prelude to "insert Roman numeral here" or now I just sound like a verbose moron with too much time on his hands.
Background & Specifics:
- Google FRP was bypassed and a clean, stock installation of Andriod 7.0 Nougat was employed.
- While this tablet was originally sold with Marshmellow 6.0.1, support for OTA updates extended to upgrading to Nougat which became accessible upon the successful factory reset after bypassing Google's FRP.
- This tablet is not rooted.
- According to LG and LG's Developer Blog, the V522 bootloader is not unlockable.
- This tablet does employ a SIM card slot and I've been using an active cellphone SIM (and of course, WiFi where available), but apparently the tablet is only utilizing the data component of the Rogers Share Everything plan and when I dial my own number from a third-party phone, it goes straight to voicemail. Yet sending texts to my number will pop up as a notification just like any other smartphone.
- Tablet is "Canadian" and SIM-locked to the Rogers / Fido network.
Tablet Details:
- Android Version is 7.0 Nougat employing a security patch level dated December 1, 2016. Baseband version is MPSS.TA.1.0.c3.3-00015-8952_GEN_PACK-1.79167.2 and it's running a kernel v3.10.84-g22068de [email protected]@ ) #1 SMP PREEMPT Mon Dec 19 14:48:23 KST 2016. Its build number is NRD90U and it runs a software version V52220a. Firmware version is 7.0.
- Factory Version is specified as LGV522AT-01-V20a-302-720-DEC-19-2016-ARB00 with SW Original Version being specified as LGV522AT-00-V20a-RGS-CA-DEC-19-2016-ARB00.
- Apparently, this product is also categorized as "b3_rgs_ca". I have seen this label, almost to the point of a recurring motif, through my research, as simply referred to "B3".
- The LG "hidden menu" is accessible by dialling *#546368#*522# via the Google Hangouts "Contacts" app.
- "Download Mode" is accessible through ADB commands and respective key-combinations and I have been able to reload or "flash" V52220a more than I'd care to admit.
Questions:
- Since the bootloader is apparently "unlockable" by official standards, does this explain why even through ADB I cannot get the tablet to boot into the bootloader partition? I'm familiar with ADB, Fastboot and the Command Prompt and all respective drivers on my Windows 10 desktop are the most current and configured correctly and the step of enabling USB debugging, OEM unlock, et al has already been covered (unless you've got a completely random idea of some random setting I may have overlooked). Invoking the command "adb reboot recovery" triggers an entry into the stock recovery mode, but selecting from the menu "reboot into bootloader" merely restarts the device; as does invoking "adb reboot bootloader" from the command prompt.
- If "download mode" is supposed to be synonymous with fastboot or bootloader mode, why does the tablet not acknowledge any fastboot commands?
- Can or would anyone be kind enough to explain why there is such a diverse categorization of this tablet and what the specific nuances imply (i.e. model B3 vs. LG-V522 vs. LG G Pad X)? What is the meaning of V20a contained within the descriptors/identifier of SW Original or Factory version?
- Is it possible through an entirely unofficial method to root the tablet without unlocking the bootloader (some users have reported yes, but never when utilizing the "Canadian" version)?
- Employing "dirtycow" is no longer an option as the security patch installed precludes this possibility (unless there have been updates to the process of using a muddy heifer that I haven't found yet).
- If rooting is not possible at the moment (even through unofficial methods), is it still possible to establish and employ an "emulator" on the Stock OS to "trick" the tablet into thinking it has a built-in cellular modem? I've found several references that suggest this tablet does have a cellular modem because of the SIM card, but when I try and look at the tablet's hardware on the actual device, telephony information is lacking.
Trying to unlock or hack the bootloader or even just rooting this tablet seems more like a beautiful woman slapping you for simply asking if it'd be okay to buy her a drink — yes, you want her to give you full root access — but hey, you're being a gentleman and trying to wine and dine her first (I know I'm a nerd and it has been awhile, but I digress).
- Carvio
FRP reset on the LG-V522
Hi Carvio,
I haven't been able to perform an FRP reset on my LG Gpad3 LG-V522. I didn't want to use the device on the cellular network just as a tablet at home.
I ended up buying the Octoplus FRP reset dongle but it turns out to not have the correct model in the setup.
How did you manage to bypass the FRP rest or rest it on this tablet?
I think Chimera may have a tool to do the reset but that means another $100 to unlock the tablet...
Thanks in advance,
REDRONAN.
carvio said:
Hello all,
As a frequent user to the XDA Forums but a first-time poster, please allow me, from the onset, to express my gratitude for the litany of assistance this forum has offered. The resources here and pure talent have proven invaluable; from assisting me in actually taking a Nokia Windows Phone and installing Android, bypassing Google's FRP on an LG Tablet to mirroring a broken display and thus saving my S5 Neo. Please accept my humble thanks and heartfelt gratitude. Perhaps one day, I will be able to offer something back to this amazing community. Kindly bear with me as I need to ask you all for some expertise and guidance one again — I have some specific questions — as a segue into the first inquiry, pardon me if this is the wrong subforum.
Question the first. And you have my permission to all point and laugh at me for asking this one: Is this subforum dedicated to a device with a specific label of LG G Pad X 8.0 or is X expressive of a variable employing categorization of many devices? I know how to research, but I still can't find a direct answer or mere suggestion; deduction implies the latter. Specifically, I am enquiring about the LG G Pad III 8.0 FHD (the LG-V522). I do hope X was a prelude to "insert Roman numeral here" or now I just sound like a verbose moron with too much time on his hands.
Background & Specifics:
- Google FRP was bypassed and a clean, stock installation of Andriod 7.0 Nougat was employed.
- While this tablet was originally sold with Marshmellow 6.0.1, support for OTA updates extended to upgrading to Nougat which became accessible upon the successful factory reset after bypassing Google's FRP.
- This tablet is not rooted.
- According to LG and LG's Developer Blog, the V522 bootloader is not unlockable.
- This tablet does employ a SIM card slot and I've been using an active cellphone SIM (and of course, WiFi where available), but apparently the tablet is only utilizing the data component of the Rogers Share Everything plan and when I dial my own number from a third-party phone, it goes straight to voicemail. Yet sending texts to my number will pop up as a notification just like any other smartphone.
- Tablet is "Canadian" and SIM-locked to the Rogers / Fido network.
Tablet Details:
- Android Version is 7.0 Nougat employing a security patch level dated December 1, 2016. Baseband version is MPSS.TA.1.0.c3.3-00015-8952_GEN_PACK-1.79167.2 and it's running a kernel v3.10.84-g22068de [email protected]@ ) #1 SMP PREEMPT Mon Dec 19 14:48:23 KST 2016. Its build number is NRD90U and it runs a software version V52220a. Firmware version is 7.0.
- Factory Version is specified as LGV522AT-01-V20a-302-720-DEC-19-2016-ARB00 with SW Original Version being specified as LGV522AT-00-V20a-RGS-CA-DEC-19-2016-ARB00.
- Apparently, this product is also categorized as "b3_rgs_ca". I have seen this label, almost to the point of a recurring motif, through my research, as simply referred to "B3".
- The LG "hidden menu" is accessible by dialling *#546368#*522# via the Google Hangouts "Contacts" app.
- "Download Mode" is accessible through ADB commands and respective key-combinations and I have been able to reload or "flash" V52220a more than I'd care to admit.
Questions:
- Since the bootloader is apparently "unlockable" by official standards, does this explain why even through ADB I cannot get the tablet to boot into the bootloader partition? I'm familiar with ADB, Fastboot and the Command Prompt and all respective drivers on my Windows 10 desktop are the most current and configured correctly and the step of enabling USB debugging, OEM unlock, et al has already been covered (unless you've got a completely random idea of some random setting I may have overlooked). Invoking the command "adb reboot recovery" triggers an entry into the stock recovery mode, but selecting from the menu "reboot into bootloader" merely restarts the device; as does invoking "adb reboot bootloader" from the command prompt.
- If "download mode" is supposed to be synonymous with fastboot or bootloader mode, why does the tablet not acknowledge any fastboot commands?
- Can or would anyone be kind enough to explain why there is such a diverse categorization of this tablet and what the specific nuances imply (i.e. model B3 vs. LG-V522 vs. LG G Pad X)? What is the meaning of V20a contained within the descriptors/identifier of SW Original or Factory version?
- Is it possible through an entirely unofficial method to root the tablet without unlocking the bootloader (some users have reported yes, but never when utilizing the "Canadian" version)?
- Employing "dirtycow" is no longer an option as the security patch installed precludes this possibility (unless there have been updates to the process of using a muddy heifer that I haven't found yet).
- If rooting is not possible at the moment (even through unofficial methods), is it still possible to establish and employ an "emulator" on the Stock OS to "trick" the tablet into thinking it has a built-in cellular modem? I've found several references that suggest this tablet does have a cellular modem because of the SIM card, but when I try and look at the tablet's hardware on the actual device, telephony information is lacking.
Trying to unlock or hack the bootloader or even just rooting this tablet seems more like a beautiful woman slapping you for simply asking if it'd be okay to buy her a drink — yes, you want her to give you full root access — but hey, you're being a gentleman and trying to wine and dine her first (I know I'm a nerd and it has been awhile, but I digress).
- Carvio
Click to expand...
Click to collapse
REDRONAN said:
Hi Carvio,
I haven't been able to perform an FRP reset on my LG Gpad3 LG-V522. I didn't want to use the device on the cellular network just as a tablet at home.
I ended up buying the Octoplus FRP reset dongle but it turns out to not have the correct model in the setup.
How did you manage to bypass the FRP rest or rest it on this tablet?
I think Chimera may have a tool to do the reset but that means another $100 to unlock the tablet...
Thanks in advance,
REDRONAN.
Click to expand...
Click to collapse
i tried to frp myself and i got it in qualcomm 9008 mode. can you make a backup of your device?
Hello,
can the bootloaders of Samsung devices be unlocked without internet? So offline unlocking and without online account.
My Xiaomi phone and Realme phone need an internet connection and an online account to unlock the bootloader. There is no local possibility.
How about Samsung devices, e.g. the current Samsung Galaxy Note 20, can you unlock the bootloader locally, i.e. without internet connection and online account?
FidesnsInai said:
Hello,
can the bootloaders of Samsung devices be unlocked without internet? So offline unlocking and without online account.
My Xiaomi phone and Realme phone need an internet connection and an online account to unlock the bootloader. There is no local possibility.
How about Samsung devices, e.g. the current Samsung Galaxy Note 20, can you unlock the bootloader locally, i.e. without internet connection and online account?
Click to expand...
Click to collapse
u could prolly unlock it give ur model is unlockable.. but ull runvinto issues with kg status being prenormal until u connect to data so u wouldnt b able to flash anything.. theres also a chance itll need to cojnect to data in order for the oem toggle to appear.. so most likely yes , u will need data either way
elliwigy said:
u could prolly unlock it give ur model is unlockable.. but ull runvinto issues with kg status being prenormal until u connect to data so u wouldnt b able to flash anything.. theres also a chance itll need to cojnect to data in order for the oem toggle to appear.. so most likely yes , u will need data either way
Click to expand...
Click to collapse
What do you mean by that exactly?
I want to buy a current Samsung Galaxy Note 20 (Snapdragon model) and unlock the bootloader and flash custom ROM.
That means I want to have the general possibility to unlock or lock the bootloader whenever I want to and it must be local.
I do not want these 3 points.
1. Bootloader can only be unlocked with an online account.
2. Request an unlock code on the manufacturer's website. Requires an internet connection to the manufacturer's server and must provide an email address to get the unlock code and then the user can enter it into ADB (Android Debug Bridge) to unlock the bootloader.
3. Install an unlock app (.apk) from the manufacturer and the Android device will be unlocked by the unlock app, but needs an internet connection in the unlock app.
Note:
I have tested everything with current Android 10 devices.
At point 1 I know it on my Xiaomi device.
At point 2 I know it on my Sony, LG and Nokia devices.
At point 3 I know it on my Asus and Realme devices.
I'm looking for Android devices that have a local and direct possibility to unlock the bootloader without online account, without unlock code (online request), without internet connection.
---
Another question you say on Samsung devices there is a KG State, what is that exactly?
I searched the forum, but there was no such clear information. As I understand it, it seems that when this "KG state" is set to "prenormal" on Samsung devices, the user cannot flash custom ROM and unlock the bootloader for about 7 days (168 hours).
Is this true?
What exactly does this KG State solve, how can it be prevented? Does it only happen for Samsung with Snapdragon model or only for Exynos model?
FidesnsInai said:
What do you mean by that exactly?
I want to buy a current Samsung Galaxy Note 20 (Snapdragon model) and unlock the bootloader and flash custom ROM.
That means I want to have the general possibility to unlock or lock the bootloader whenever I want to and it must be local.
I do not want these 3 points.
1. Bootloader can only be unlocked with an online account.
2. Request an unlock code on the manufacturer's website. Requires an internet connection to the manufacturer's server and must provide an email address to get the unlock code and then the user can enter it into ADB (Android Debug Bridge) to unlock the bootloader.
3. Install an unlock app (.apk) from the manufacturer and the Android device will be unlocked by the unlock app, but needs an internet connection in the unlock app.
Note:
I have tested everything with current Android 10 devices.
At point 1 I know it on my Xiaomi device.
At point 2 I know it on my Sony, LG and Nokia devices.
At point 3 I know it on my Asus and Realme devices.
I'm looking for Android devices that have a local and direct possibility to unlock the bootloader without online account, without unlock code (online request), without internet connection.
---
Another question you say on Samsung devices there is a KG State, what is that exactly?
I searched the forum, but there was no such clear information. As I understand it, it seems that when this "KG state" is set to "prenormal" on Samsung devices, the user cannot flash custom ROM and unlock the bootloader for about 7 days (168 hours).
Is this true?
What exactly does this KG State solve, how can it be prevented? Does it only happen for Samsung with Snapdragon model or only for Exynos model?
Click to expand...
Click to collapse
you will need a data connection.. even if bl is unlocked after u unlock it will wipe device.. u then need to reboot and skip through setup wizard and connect to mobile data or else kg status will be "prenormal" and not let you flash anything custom..
kg state is different than the 7day period. kg is also called knox guard and no, theres no way around it, u have to connect to data for it to change. it is on all samsung devices exynos and snapdragon.
and thats if its unlockable.. not all snapdragon devices can b unlocked.
also this isnt a xiaomi or lg or nokia or asus or realme device.. samsung has its own extra security..
theres no easier way to explain it.. i suggest u read up on it and check existing samsung device forums to get more info
I have now tested more Android devices and finally found Android devices where I can locally unlock the bootloader and also flash locally custom ROM without data connection, unlock code, online account and KG State.
It is a Google Pixel 3 and a OnePlus 7T. It is important that it is not the T-Mobile version!
So no provider devices, because when I bought a OnePlus 7T T-Mobile version I could not unlock the bootloader. It needs a unlock code (online request), because of SIM-Lock. It is not possible to unlock the bootloader directly and locally, for example to flash the stock rom (without T-Mobile).
My recommendation to the users, if you are looking for Android devices that can unlock the bootloader locally (via ADB) and flash locally custom ROM. Then Google Pixel and OnePlus devices that can do this, but only the free provider version, very important!
FidesnsInai said:
I have now tested more Android devices and finally found Android devices where I can locally unlock the bootloader and also flash locally custom ROM without data connection, unlock code, online account and KG State.
It is a Google Pixel 3 and a OnePlus 7T. It is important that it is not the T-Mobile version!
So no provider devices, because when I bought a OnePlus 7T T-Mobile version I could not unlock the bootloader. It needs a unlock code (online request), because of SIM-Lock. It is not possible to unlock the bootloader directly and locally, for example to flash the stock rom (without T-Mobile).
My recommendation to the users, if you are looking for Android devices that can unlock the bootloader locally (via ADB) and flash locally custom ROM. Then Google Pixel and OnePlus devices that can do this, but only the free provider version, very important!
Click to expand...
Click to collapse
huh? you talk about bl lock because of sim lock (sim lock has nothing to do with it, even agter getting sim unlocked they are still not bl unlockable) then unlock locally via adb (isnt it fastboot which is not adb?) then pixel and one plus (theres many many other devices that are bl unlockable besides these two) then but only free provider version (huh?)
I meant fastboot and not ADB. Sorry, I downloaded this here on XDA forum. I have simply considered ADB as a whole
https://forum.xda-developers.com/showthread.php?t=2588979
Yes generally do not buy a provider version for all Android devices. There are only additional restrictions and is always dependent on the provider server.
I have to do this here with my OnePlus T-Mobile version, see the OnePlus support page.
https://support.oneplus.com/app/ans...-to-unlock-bootloader-for-oneplus-smart-phone
I need to unlock the SIM and request an OEM code and then I can unlock the bootloader locally and flash locally custom ROM or stock rom (without T-Mobile).
I can confirm that these Android devices Google Pixel and OnePlus without provider version can by default unlock the bootloader locally and flash custom ROM locally.
The user can just buy these Android devices in the store and do everything locally right away. No data connection is required. All you need are the tools and the custom ROM on the computer, which you can download and save to an external hard drive.
Quite simply said. Something similar when the user installs a Linux distribution (Ubuntu, Linux Mint, Fedora) on his computer or notebook.
Other Android devices, like I said before, need a data connection to unlock the bootloader, e.g. via app, online account or an unlock code (online request).
https://forum.xda-developers.com/showpost.php?p=83480827&postcount=3
Samsung devices I haven't tested, but have the similar problem (needs data connection to flash custom ROM), which you wrote yourself, because of KG State.
This is important to say, thanks. True as it is, only Google and Oneplus devices are free to use (equals root). Google can even accommodate GrapheneOS.
from my poor understanding of the recent 2-3 generations:
Root and developer friendly: google, oneplus
+ GrapheneOS compatible : google
+ Ez single command unlock like when we were young : oneplus
+ OTA Updates when rooted : oneplus
+ flash update without PC : oneplus
+ Encryption never touched : oneplus
Relatively root friendly : xiaomi, asus, sony, lg
+ official "support" of unlocking : all
+ without internet spying aspect of the procedure : none?
+ "featuring" disgusting wait period : xiaomi (realme)
+ chance of losing encryption: high (it is possible to forget ROMs and TWRP and keep it on some models)
Root unfriendly : samsung
+ official "support" of unlocking : no
+ "featuring" knox trip : yes
+ "featuring" key combination to boot : most models
+ can't even unlock : note20?
Root almost impossible : huawei, oppo and other small brands
now i don't care how difficult the first root procedure is or to knock some stupid fuse, but rather care more about how update procedure is, and can't adher to the new "standard" of killing encryption by disablers, so naturally i'm stuck to oneplus for the daily driver device. i can only look at the pictures and reviews of other brands
*people who root will go to heaven*
huh?
lol i dont understand most of last two posts.. i have g988u g986u rooted on unlocked bl no problem, no buttons need to be pressed, twrp exists, custom roms are easy, dunno what grahpOS even is and the list goes on.. if u kno wat ur doing samsung isnt that bad but yes, google 0urchased devices of course are easy
doggydog2 said:
Root and developer friendly: google, oneplus
+ GrapheneOS compatible : google
+ Ez single command unlock like when we were young : oneplus
+ OTA Updates when rooted : oneplus
+ flash update without PC : oneplus
+ Encryption never touched : oneplus
Click to expand...
Click to collapse
I have read all the answers here and would like to add additional points that the OP (original poster) mentioned but did not add to a concise list.
+ Unlock bootloader without network connection and online account : Google, OnePlus
+ Rooting and flashing without network connection and online account : Google, OnePlus
Note: The 2 new points work immediately and only if it is not a provider device. If it is a provider device e.g. from T-Mobile it does not work, in this case (Google and OnePlus) you need for the first step (unlock bootloader) a code from the provider and is dependent on its server so simply put, you need a network connection.
doggydog2 said:
Relatively root friendly : xiaomi, asus, sony, lg
+ official "support" of unlocking : all
+ without internet spying aspect of the procedure : none?
+ "featuring" disgusting wait period : xiaomi (realme)
+ chance of losing encryption: high (it is possible to forget ROMs and TWRP and keep it on some models)
Click to expand...
Click to collapse
doggydog2 said:
+ without internet spying aspect of the procedure : none?
Click to expand...
Click to collapse
This point generally applies to almost all Android devices, regardless of whether the manufacturer allows bootloader unlocking or not (e.g. Huawei).
It is confirmed several times by users in recent years see in XDA forums. Some examples Sony, LG, Asus, Xiaomi, Samsung, Realme, vivo, OPPO and Nokia, no matter if provider or non provider device. These Android devices spy because the first step (unlock bootloader), necessarily requires a network connection. For example, via online account, code or app (network connection required, sometimes it works only if the user has mobile data in the app).
Simply put without internet spying is not possible.
If only compare this point with iOS/iPadOS devices, so jailbreak. Then it is almost similar, that is on current iOS/iPadOS devices you also need a network connection first to complete the "iOS Setup", when that is done a jailbreak (if available for the respective iOS/iPadOS version can be made). In some cases, so with very old iOS devices for example the first iPhone you can bypass the iOS setup (so without network connections) and can then, as usual make a jailbreak.
FidesnsInai said:
What do you mean by that exactly?
I want to buy a current Samsung Galaxy Note 20 (Snapdragon model) and unlock the bootloader and flash custom ROM.
That means I want to have the general possibility to unlock or lock the bootloader whenever I want to and it must be local.
I do not want these 3 points.
1. Bootloader can only be unlocked with an online account.
2. Request an unlock code on the manufacturer's website. Requires an internet connection to the manufacturer's server and must provide an email address to get the unlock code and then the user can enter it into ADB (Android Debug Bridge) to unlock the bootloader.
3. Install an unlock app (.apk) from the manufacturer and the Android device will be unlocked by the unlock app, but needs an internet connection in the unlock app.
Note:
I have tested everything with current Android 10 devices.
At point 1 I know it on my Xiaomi device.
At point 2 I know it on my Sony, LG and Nokia devices.
At point 3 I know it on my Asus and Realme devices.
I'm looking for Android devices that have a local and direct possibility to unlock the bootloader without online account, without unlock code (online request), without internet connection.
---
Another question you say on Samsung devices there is a KG State, what is that exactly?
I searched the forum, but there was no such clear information. As I understand it, it seems that when this "KG state" is set to "prenormal" on Samsung devices, the user cannot flash custom ROM and unlock the bootloader for about 7 days (168 hours).
Is this true?
What exactly does this KG State solve, how can it be prevented? Does it only happen for Samsung with Snapdragon model or only for Exynos model?
Click to expand...
Click to collapse
Pixels from Google and One Plus is what your looking for. In both cases you will have to fully boot the phone skip thru setup unlock developer option oem unlock toggle before you can unlock pixel or one plus
People this is a very big problem with Samsung and other manufacturers. Current smartphones are not independent devices, without server of the manufacturer nothing works.
LG is closing the bootloader unlock program that would help keep its Android phones alive
After ending its mobile business earlier this year, LG has confirmed it will also shut down the bootloader unlock program.
9to5google.com
Here is a very recent example. LG will soon close its key server for unlocking the bootloader. Until December 31, 2021, you still have time to unlock the bootloader of your LG smartphones. Later it is no longer possible.
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
SM-T227U is an American model wich doesn't have the OEM unlocking option, you could unlock using unofficial ways but those are not pretty "stable".
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
evan5935 said:
Hey man! Still got your tab 7? I also have a SM-T227U and have oem unlocked! After doing the usual stuff, you will want to turn off automatically update in developer settings. After that, go to settings>General management>Date and time and select manual time and date, and set it for exactly 10 days before the day you attempt this. OEM unlock will appear in dev settings!!!
Then turn off device and while holding power up + power down, plug into PC. It will show the pre-download mode screen where it asks if you want to continue. Just follow the on screen instructions to unlock bootloader!
*note that the bootloader unlocking results in an unavoidable factory reset**
Click to expand...
Click to collapse
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
coocooguy246 said:
Hello! So I am on a journey to attempt to root a Samsung tab a7 lite sm-t227u. So I want to be extremely transparent as to my reason for rooting:
I was given this tablet by my father whom got it from a previous job. When he left the job they never asked for it back, a long with a good bit of supplies he had that he got to keep.
So, I have this tablet, I can get into it as it doesn't have a passcode. I have wiped it by factory reset as well. However, it has IBM's MAAS360 installed and after factory reset AND a firmware flash using odin I still cannot get rid of this maas360 mdm. It is not Knox locked. I can activate developer mode and change all those settings, but I cannot download any apps through the app store at all or enable unknown source app install as those are under an IT block. I also do not have the OEM unlock option in dev options. I've tried the whole changing the date and connecting to wifi, with and without sim card but I cannot get this option to show, nor can I unlock the bootload through fastboot.
I have read that most of the new samsung phones do not have a bootloader unlock option, but from what I can tell that is specific to the snapdragon phones, and this tablet is running a mediatek chip.
Now, if I can remove mdm restrictions without rooting that's great, but I have a feeling that is the only way to properly flash this thing to completely remove the mdm.
I have tried the recovery tar that is posted in this forum but I cannot get it to flash, likely because I still don't have an unlocked bootloader
Have any of you all faced something similar or know of a solution? I may call the company the mdm is managed by and just see if they will remove it from their system, but I find it highly unlikely.
Click to expand...
Click to collapse
If it has Mediatek chipset then you can use SP flash tool to format the tablet firmware and reflash it.
I would strongly recommend you to backup the NV DATA and NVRAM files before you format the tablet.
coocooguy246 said:
Sweet! I will absolutely try this when I get home this afternoon, will report back with results!
But just for clarity. Let's say I start with a freshly wiped tablet. Go through set up and connect to wifi, do I need to add a Google and Samsung account? Then in dev settings, enable USB debugging, also enable wifi debugging? Then change the date. Is there any step I am missing?
Click to expand...
Click to collapse
You can follow this guide actually! ( https://forum.xda-developers.com/t/...220-t225-install-lsposed-magisk-mods.4406933/) it recommends just skipping the setup junk
I have found that many times, rooting methods work across different models of the same device unless there are some sort of major differences in chipsets or some sort of random change lol
The only thing that doesn't seem to work for our model is section V of the guide which is for the removal of the "bootloader is unlocked" screen at startup. so you will still need to press the power button on that screen to boot up. It's a tiny hassle, but otherwise no big deal in my personal opinion
Make sure to read all the way to the end of the root section (section 4) and especially remember step 7. I retried probably 4 times and even patched the entire AP file of the firmware for use in odin (doing this gives a second warning on Knox screen that it isn't samsung official fw then boots normally into the bootlogo screen) before realizing everything was going fine.. I recommend just using the patched Magisk boot.img first just because I find it unsightly
Just flash the boot.tar in the AP slot. Don't download any of the boot imgs from the guide because they are for the t220's and t225's. I'll link the one I made according to the guide below. It'll save you some time and you won't need to install zarchiver and Magick just to have it factory reset again lol. Just download the latest Magisk apk (26.1) from the official github (https://github.com/topjohnwu/Magisk/releases) and install it when you have completed the 2nd factory reset/the patched boot img install.