Database Info

Blu development

Let's get the ball rolling with this thing... I am new to blu
Search shows SP Flash tool as a main flash tool.
I expect to get root with towel root or kingroot.
If we do acquire root, the next step is to dump a stock ROM, I haven't done much dev. since jellybean, but hopefully we could map partitions (important), and do a raw dump (.img) backup, etc. A secure kernel, could prevent that, I think. If we are able to make or acquire a stock ROM, we have something to fall back on. There's always hope, they will allow unlock of bootloader from developer options in settings, or fastboot oem unlock. It looks like quite a few other blu devices have been unlocked. If worst came to worst, I'm sure we could pony up some donations to get this device into a developers hands to help.
Once we get bootloader unlocked, all we need is a custom recovery, and some source code bits, and its off to the builds, we hope!
Please share any beginning steps to help get things moving here....
this looks promising.. http://androidxda.com/download-mtk-droid-tool
Thanks!

Yes let's get the ball rolling. I'm eagerly waiting for this device. The source for the x10 is released so it looks like we're in the green for now.
Sent from my A0001 using Tapatalk

Rooting
chrisrotolo said:
I expect to get root with towel root or kingroot.
Click to expand...
Click to collapse
No luck with either of those. I've tried a lot of "one-click" apks and none of them work. It looks like I'm going to have to dig out an old desktop from my basement and make myself a Windows machine (urgh!!). I agree, Sp Flash Tools and MK Droid Tools look like a good place to start.

SP Flash Tool for Linux
I've been trying to get my linux (Ubuntu 14.04) to recognize the phone with this s/w but no luck so far, even though the system finds it (see screenshot).
http://forum.xda-developers.com/general/rooting-roms/tutorial-how-to-setup-spflashtoollinux-t3160802

You kernel messages suggest you have the Allview version... Is it possible that software or partitioning differences in the default load of the Allview vs. the Blu may make a difference in whether the root apps work?

clipcarl said:
You kernel messages suggest you have the Allview version... Is it possible that software or partitioning differences in the default load of the Allview vs. the Blu may make a difference in whether the root apps work?
Click to expand...
Click to collapse
I have no way of knowing.

I sure hope the developers jump all over this phone.

xathras said:
I have no way of knowing.
Click to expand...
Click to collapse
So it could be too soon to assume that the current rooting apps won't work on the Blu phone just because they don't work on the Allview.That is, if Blue has their own software stack they install that is different than the Allview...

Rooting from PC failed
I now have a Windows 7 machine running so I've tried a couple of root from pc apps.
Drivers http://androidxda.com/download-gionee-usb-drivers
I installed the Gionee E8 drivers from here successfully - or so Windows said.
Root Genius v2.4.1 http://androidxda.com/download-root-genius-application
First ticked "USB debugging" under "Developer options" on phone. Ran Root Genius and it found the phone first time. Click on "Allow Computer" box that pops up on phone. Root Genius started, got to a couple of % and then crashed. Rebooted PC, clicked on "Revoke USB debugging authorisation" for a clean start and tried again. Same result; click "Allow computer", start program and crash. Tried a couple more times with same result.
iRoot v1.8.5 http://androidxda.com/download-iroot-application-all-versions
Used same procedures as with Root Genius. iRoot started, found the phone, went all the way though it's operations before reporting that rooting failed (i.e. it did not crash). Retried a couple of times with the same result.
The only plus is that the driver I used appears to be OK for Windows 7 at least (both programs found the phone).
Later I tried Kingo Root http://androidxda.com/root-android-device-using-kingo-root
It couldn't find the phone using the driver I previously used or it's own driver, although the "Allow computer" box popped up on the phone both times

xathras said:
I now have a Windows 7 machine running so I've tried a couple of root from pc apps.
Drivers http://androidxda.com/download-gionee-usb-drivers
I installed the Gionee E8 drivers from here successfully - or so Windows said.
Root Genius v2.4.1 http://androidxda.com/download-root-genius-application
First ticked "USB debugging" under "Developer options" on phone. Ran Root Genius and it found the phone first time. Click on "Allow Computer" box that pops up on phone. Root Genius started, got to a couple of % and then crashed. Rebooted PC, clicked on "Revoke USB debugging authorisation" for a clean start and tried again. Same result; click "Allow computer", start program and crash. Tried a couple more times with same result.
iRoot v1.8.5 http://androidxda.com/download-iroot-application-all-versions
Used same procedures as with Root Genius. iRoot started, found the phone, went all the way though it's operations before reporting that rooting failed (i.e. it did not crash). Retried a couple of times with the same result.
The only plus is that the driver I used appears to be OK for Windows 7 at least (both programs found the phone).
Click to expand...
Click to collapse
Cool... It's good to test this stuff. More information is always a good thing.
BUT, since the software / partitions of the Blu Pure XL phone will almost certainly be different than the Allview phone you have your tests really don't really tell us anything about the Pure XL for certain. The hardware may be exactly the same (or there may be differences in the radios) but if the software and / or partition layout is different then what works on your phone may not work on the Pure XL and vice versa.
So I'd request that you keep posting your useful information... BUT that you clearly post that you don't actually have a Blu Pure XL but the Allview phone so you don't confuse people. Yes, they may be based on the same hardware but that does not make them exactly the same as one another. For example, there are different versions of the LG G4 and they all have pretty much the same hardware but they can't all use the same ROMS or the same rooting techniques.
So what you are posting helps because more data is better, but is not definitive for the Pure XL because your phone is NOT a Pure XL.
Thanks,
Carl

clipcarl said:
Cool... It's good to test this stuff. More information is always a good thing.
BUT, since the software / partitions of the Blu Pure XL phone will almost certainly be different than the Allview phone you have your tests really don't really tell us anything about the Pure XL for certain. The hardware may be exactly the same (or there may be differences in the radios) but if the software and / or partition layout is different then what works on your phone may not work on the Pure XL and vice versa.
So I'd request that you keep posting your useful information... BUT that you clearly post that you don't actually have a Blu Pure XL but the Allview phone so you don't confuse people. Yes, they may be based on the same hardware but that does not make them exactly the same as one another. For example, there are different versions of the LG G4 and they all have pretty much the same hardware but they can't all use the same ROMS or the same rooting techniques.
So what you are posting helps because more data is better, but is not definitive for the Pure XL because your phone is NOT a Pure XL.
Thanks,
Carl
Click to expand...
Click to collapse
Thanks Carl, you're quite right of course. I'll check back in a couple of weeks once you guys have actually got your hands on some genuine Blu. When you do these adb tools (http://androidxda.com/download-best-android-adb-driver) and MTK Droid Tools worked v2.5.3 work on my Allview.

xathras said:
Thanks Carl, you're quite right of course. I'll check back in a couple of weeks once you guys have actually got your hands on some genuine Blu. When you do these adb tools (http://androidxda.com/download-best-android-adb-driver) and MTK Droid Tools worked v2.5.3 work on my Allview.
Click to expand...
Click to collapse
Please don't stop posting your test results! Just let people here know they're for the Allview and thus may not be the same as what would happen on the Pure XL. But it's also quite possible that your phone is exactly the same with the same software and layout just with cosmetic changes. We just don't know yet. It's also possible that your phone could be flashed to be exactly the same as the Pure XL even if it's not out of the box. In any case it's definitely useful information you are providing!

@xathras - Have you tried flashing SuperSU from recovery or otherwise injecting root from a recovery package?
http://www.recovery-mode.com/android/gionee-elife-e8.html

neatojones said:
@xathras - Have you tried flashing SuperSU from recovery or otherwise injecting root from a recovery package?
http://www.recovery-mode.com/android/gionee-elife-e8.html
Click to expand...
Click to collapse
Flashing SU from recovery fails and although I haven't tried the other option I'm fairly sure that that would fail too, due to /system being a secure read only partition. It is going to take someone with the necessary skills to extract boot.img, make the needed changes and re-packing it. I've seen a webpage for a china wholesaler for the Gionne version of this phone who offers an "unlock and root" option for $2.99 per device, so it must be doable.

Bootloader unlocked
Have look at post #108
http://forum.xda-developers.com/pur...v-friendly-t3197751/post63383416#post63383416

xathras said:
Have look at post #108
http://forum.xda-developers.com/pur...v-friendly-t3197751/post63383416#post63383416
Click to expand...
Click to collapse
Great! You were one step ahead, that was going to be my next suggestion. Now with an unlocked bootloader you should be able to make a TWRP and flash whatever you want including injecting su or flashing a completely modified ROM with root.

Posting this here so we can have a to go to thread.
xathras said:
Now that some of you look like your'e about to get your hands on this device I'll post a few of the resources you might need. The MediaTek X10 Helio (mt6795 based) is only now beginning to appear in phones; there is little help from devs as yet (Hey! Your'e An Early Adopter). The Gionee version has just gone on sale in India so something (in English) might appear there soon. Due to MTK devices being common in Asia you'll find a lot of help in sites there.
Blu related sites
BLU Products Development Team - Community - Google+
https://plus.google.com/communities/117846429749085694805
BLU Developers Repository
http://www.blu-dev.com/
Asian sites
China Devices
https://www.china-devices.com/
China Phone Arena
http://www.chinaphonearena.com/forum/Forum-MTK-General-Tools
Android Urdu
http://androidurdu.net/mediatek-scatter-files-download/
http://androidurdu.net/sp-flash-tool-database/
MTK Roms
http://www.mtkroms.com/
http://www.mtkroms.com/2015/03/mtk-bootimg-unpack-repack-tool.html
http://www.mtkroms.com/2015/02/how-to-root-your-mediatek-device.html
http://www.mtkroms.com/2015/03/philz-touch-recovery-for-all-mtk-devices.html
and many others.
Rooting and flashing
http://whiteboard.ping.se/Android/Rooting
http://whiteboard.ping.se/Android/BootLoader
https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro#Common_fastboot_commands
https://wiki.cyanogenmod.org/w/Template:Fastboot_oem_unlock
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
MTK Droid Tools 2.5.3
http://forum.xda-developers.com/showthread.php?t=2160490
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
This tool does not work on this phone because it can't recognize the new 64-bit SOCs. I thought that when it found my phone it might work but the "TotalBytesPerChunk Not Found" error (see attached screenshot) is fatal. However, it does do one useful thing in that it displays a blocks map even thought it can't create a scatter file. I'd like to know if the Allview and Blu blocks maps match.
MTK Droid Tools is sadly no longer being maintained.
Attached files are the MTK Droid Tools screenshot (too big - had to zip it) and the Allview build.prop file. I'd be interested in seeing the Blu version.
Click to expand...
Click to collapse
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
Can we as a community keep hammering Mediatek to release the helio x10 sources so we can start porting roms to the pure xl? I'm doing my fair share of posting on their social media sites. We'll be able to get 6.0 if they post up the sources. They had them up on github but they removed them I don't know why.

FuMMoD said:
Can we as a community keep hammering Mediatek to release the helio x10 sources so we can start porting roms to the pure xl? I'm doing my fair share of posting on their social media sites. We'll be able to get 6.0 if they post up the sources. They had them up on github but they removed them I don't know why.
Click to expand...
Click to collapse
This is probably where I stop being useful since I'm a "monkey see, monkey do" kind of guy as far as rom development goes, although I'm up for testing stuff.
Is this any of use to you?
http://www.mediafire.com/download/dx698xy19xg5xq8/MT6795.kernel-master.zip
https://github.com/jawad6233/MT6795.kernel/tree/master/alps/kernel-3.10
Both from this link:
http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886

xathras said:
This is probably where I stop being useful since I'm a "monkey see, monkey do" kind of guy as far as rom development goes, although I'm up for testing stuff.
Is this any of use to you?
http://www.mediafire.com/download/dx698xy19xg5xq8/MT6795.kernel-master.zip
https://github.com/jawad6233/MT6795.kernel/tree/master/alps/kernel-3.10
Both from this link:
http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886
Click to expand...
Click to collapse
Dude you're awesome at researching and finding useful Intel! I'm going to go over everything you've provided over course of today and tomorrow and start working on the phone. I should get it by tomorrow evening. I built my own rom before privately so hopefully I have enough know how to get Development rolling in here. I just hope I can motivate others of better skills to come over once it's proven roms can be ported over and such.
Sent from my A0001 using Tapatalk

FuMMoD said:
Dude you're awesome at researching and finding useful Intel
Click to expand...
Click to collapse
I can resist anything except flattery!
In my Allview build.prop there's a line that says "ro.gn.gnromvernumber=GiONEE ROM5.0.16". I'd be very interested in knowing what your Blu build.prop has to say.

New OnePlus One Came Rooted With Adware

Brand New OnePlus One rooted and with adware etc
I am a very newbie to not all but many of the particular issues in this post so would be grateful of any newbie taylored advice.
Background:
==============
I purchased a Oneplus one recently, stocked and fulfilled by amazon with amazon returns policy but seller was a chineese company.
It was advertised as 100% Original Oneplus One New Cell Phone
The phone arraived and appeared to already be rooted
evidence:
Barclays App says it is rooted and won't run. It ran fine on my Nexus 4
I can connect via adb and set to su straight away
The phone appeared to have arrived with significant malware / adware with popups and auto launch ad in browser pages and bloteware / PUPS(?), and other issues. After a great deal of research checking notifications and trial and error I disabled the following, some via settings\apps some via adb, pm ... disable ...
2048 (com.digiplex.game)
App Manager (com.shyz.steward)
Browser (com.android.browser)
Caller ID (com.android.tools.callassistant)
Clean Master (com.cleanmaster.mguard)
Cool Browser (com.cool.coolbrowser)
DU Speed Booster (com.dianxinos.optimizer.duplay)
Magic Photo (cn.dotui.magicphoto)
Videos (com.haolianluo.video)
and disabled gestures due to torch issues
The phone now seems quite stable.
I installed MalwareBytes, however None of the items it identifies is it able to disable/uninstall I set it not to scan automatically but it continues to tell me I have not responded to its list of issues, but I have responded by selected them, but on selection it tries to uninstall them but fails.
I was able to disable one of them via adb because it provided the package name for that one but:
CallerID.apk (disabled in settings\apps)
coolbrowser.apk (disabled in settings\apps)
201507140923731g.apk
AppStore.apk
I do not know how to uninstall (or disable at least on 2 of them) and I do not know how to refer to them from package manager because I don't have the package name.
Key Questions:
================
I am familiar with much of software engineering and programming but not with mobile phone OS / disk / memory / file system, etc. I am having a lot of difficulty getting to grips with the vocabulary, definitions and terminology depending what you read.
- Some say OnePlus from factory comes with cyanogenmod but is not rooted
- So one wonders how my phone go to be rooted if the seller is a retailer
- Some say if the phone is rooted the warentee is invalidated. What do you think?
- WhatsApp says the phone has a custom rom and watsapp may not work properly with a custom rom
It is very difficult to get to the bottom of exactly what the difference is between a stock rom
and a custom rom. Some seem to be saying cyanogenmod is a custom rom, but then others say what
comes on the phone from the mobile manufacturer is a stock rom, eg HT Sense or in the case of
OnePlus, cyanogenmod! Is it only a custom rom if it is somehow NOT proven to be a
custom rom validated by the mobile manufacturer in factory (i.e. stock rom)?
- Some say having a custom rom invalidates warrantee, is this right?
- How do i prove that the rooting and the custom rom were not introduced by me?
- I have thought about factory reset, but I cannot manage to find anything that tells
me what this actually means and does, only how to do it.
- does a factory reset actually do what it suggests. I have read that factory reset does
not involve going to the manufacturers site and obtaining an appropriate image and flashing
it to the phone so I do not quite understand how else it could guarantee it
- If a factory reset will just make it like it was when I received it then that I do not want.
- Can I and ought I to flash a fresh image on the phone to get it like it WOULD HAVE been
had I bought it from OnePlus factory on invite and not through a mediator
- Finally. There is a notification "System Update is ready" . When I select this it appears
to download something (next version of cyanogenmod I guess though I don't recognise the version
number against any cyanogenmod versions) then it restarts and goes to a recovery app.
At this stage it is not completely intuitive what one should do and it seems to want you
to navigate to a location.
Now, I think I could probably figure this out with some reading but two things come to mind:
1) Presumably for a from factory OnePlus phone this kind of ambiguous unintuitive update
process would not be going on for people who just bought their phone and knew nothing
so it suggests the phone is in a different state to that. I also read you need root
already to install a (good) recovery app.
2) I am loath to do this update since it is not clear whether the update is this retailers
system update and will reintroduce all that I have disabled to create stability. Therefore
up to now I have always selected just do nothing and reboot. I favor stability over
features.
I am kind of inclined now I have managed to get it stable to just stick with it as it is and just use it without any further updates / resets / flashes and without returning it, but...
Sorry to ask all these questions. I would be grateful of any advice. Can be given with the assumption that I understand foundational general stuff ram, rom (though this word seems to be used differently to what I'm used to), flash, image, partition etc, but not that I actually know all about how the android/cyanogenmod platform is laid out and behaves as an installation.
Thank you.

Hi, All Oneplus One phones comes with CyanogenMod without rooted. One must Unlock bootloader and Flash custom recovery and Flash SuperSu to get root access.
Yours already says rooted means either you bought the used phone or refurbished. However even when a phone is refurbished OnePlus company locks it and make it unrooted.
OnePlus Phones warranty doesn't get over bu rooting. OnePlus actually supports rooting. Warranty becomes void when you do something blunder while flashing and your devices becomes dead aka bricked.
What I am suspecting is the chinese seller bought new OnePlus and Installed different ROM as the chinese OPO comes with ColorOS which doesn't have PlayStore. Now in the procedure they introduced unwanted Adwares which may be Intentional or Unintentional.
Now you have 2 options.
Either ask Amazon for a refund.
Or if the time is passed then I suggest you to start fresh. If you have already custom recovery installed then go ahead and install fresh stock CyanogenMod ROM from xda.
sent from Bacon (OnePlus One)

Hi Abhinav_Rakesh,
Thank you so much for your response, I really appreciate your advice. I think I understood most of what you said, generally but I am still a bit unclear on some points:
Is there any way to tell if the phone is refurbished. I would rather it were new even if they have installed a different rom.
What do you mean by "time is passed" I have only had the phone a few days. I am in a quandary whether to return it or not, whether amazon will believe it was not me who rooted it and whether I will be able to get another one that is not just the same as this one anyway since you cannot get them direct from OnePlus any more.
I saw some kind of recovery screen over one reboot but did not do the install. How do I know if this is the "custom recovery" you describe, if it is not how do I obtain / get to "custom recover"?
Can you direct me to a script that shows me how to "install fresh stock CyanogenMod ROM from xda"? Will that completely blank out everything that the chineese company may have done on the phone, or might some stuff still be left behind? Is there a risk to that process, given that I at least have a fairly stable phone now? Will it include or do I have to get separately "PlayStore" so I can download my usual apps?
Thank you again, I really appreciate it?

i suggest you to start from fresh, since obviously your OPO is not in stock state and has been tampered with..
the (general) steps to make the OPO like new are as follows..
(1) connect it to a pc via usb cable
(2) in command prompt, issue "adb reboot bootloader" (and wait for it to boot into bootloader/fastboot mode)
(3) issue "fastboot oem unlock" (to unlock the bootloader.. all data will be wiped but the warranty is not voided)
(4) issue "fastboot flash recovery custom_recovery.img" (replace "custom_recovery.img" with the actual recovery file name)
(5) power off mobile and disconnect from pc
(6) press power button together with volume down button (to boot into custom recovery we just flashed)
(7) while in recovery, install rom image (which should be put in the internal storage beforehand)
(8) reboot to enjoy the reborn mobile
to be able the complete the above steps, you need to get some files in advance:
- adb.exe/fastboot.exe (which you should already have since you could do adb)
- custom recovery (TWRP suggested.. get the image for OPO, whose codename is bacon, at http://twrp.me/ ), and put it in your pc..
- stock or custom rom (the stock for OPO is cyanogenmod, and there is also a OnePlus provided OxygenOS rom.. go to respective sites to get a copy), and put it into the mobile's internal storage..
mind you that by doing so (the fastboot oem unlock step) all your mobile's data will be wiped..

@hardya Hi .. You can follow this link to restore your phone according to OnePlus Standards. This will remove all that chinese ads and all and will make it fresh.
http://forum.xda-developers.com/showthread.php?t=2970390
sent from Bacon (OnePlus One)

I feel like i need to reanswer a some of your question even though some already have answered them. You seem very interested and it seems fair to clear up some things.
hardya said:
- Some say OnePlus from factory comes with cyanogenmod but is not rooted
Click to expand...
Click to collapse
There is a little misconception about what cyanogenmod is.
The offical Oneplus One comes preinstalled with CyanogenOS (or CM12S), which is derived from Cyanogenmod. It get's a bit complicated. Cyanogen is a company founded by the lead programmer of Cyanogenmod. CyanogenOS is a commercial product, that is licensed to phone manufactures.
Cyanogenmod is the codebase for CyanogenOS. CyanogenOS adds some functionalities that are not present in the community maintained Cyanogenmod. (e.g. a alternate dialing app, theme store, etc.)
The offical Oneplus One comes NON-rooted. You need to manually enable root.
Please keep in mind that it gets REALLY complicated from this point!
The Oneplus One debuted with CM11S (CyanogenOS, the commercial version of Cyanogenmod). Cyanogen (the company) promised users 2 years of support and updates for the owners on the Oneplus One. But Oneplus and Cyanogen had some major issues that resulted in ending the partnership.
Oneplus had to offer an alternative Android Firmware for their upcoming phone Oneplus Two. So they did another android version called OxygenOS. This was installed onto all Oneplus One phones from a certain date onward!
THIS is the OFFICAL Android Software Version for your Oneplus One!!!
See: https://oneplus.net/de/support/answer/how-can-i-download-oxygen-os
I would strongly recommend to install OxygenOS, as it is the easiest way of experience the phone as Oneplus intended it to be.
Most tutorials on here are a little bit older so they are offering guides which mention either CM11S, CM12S, Cyanogenmod or OxygenOS. (or if you are more familiar with other customroms, whatever you'd like to install! But this is something you should look into, when you are more familiar with what costumroms are and what they do! There are so many excellent guides on here, which i'd recommend you to read sometime!)
- So one wonders how my phone go to be rooted if the seller is a retailer
Click to expand...
Click to collapse
He rooted it either manually or used an android version (e.g. something downloaded off XDA or got one from some developer). Such versions are often called Customroms.
Also note, that there are no official retailers of Oneplus phones. They are officially offered from the website only. However, there are some shops in China, that offer Oneplus phones.
- Some say if the phone is rooted the warentee is invalidated. What do you think?
Click to expand...
Click to collapse
Most phone manufactures actually tell you that your warranty is void when rooting your phone.
Oneplus however is very, very supportive when it comes to rooting!
And of course installing other Android Versions and Roms!
See: https://oneplus.net/de/support/answer/will-rooting-or-unlocking-the-bootloader-void-my-warranty
- WhatsApp says the phone has a custom rom and watsapp may not work properly with a custom rom
It is very difficult to get to the bottom of exactly what the difference is between a stock rom
and a custom rom. Some seem to be saying cyanogenmod is a custom rom, but then others say what
comes on the phone from the mobile manufacturer is a stock rom, eg HT Sense or in the case of
OnePlus, cyanogenmod! Is it only a custom rom if it is somehow NOT proven to be a
custom rom validated by the mobile manufacturer in factory (i.e. stock rom)?
Click to expand...
Click to collapse
Cyanogenmod is indeed a custom rom. (or sometimes aftermarket firmware)
See: https://en.wikipedia.org/wiki/CyanogenMod
A stock rom is the firmware that is installed by the manufacturer. (in your case: CyanogenOS, called CM12S. the 12 stands for the version number of Cyanogenmod. 12 = Android 5, 13 will be Android 6. There was a CM11S version, when the phone debuted last year.). The S marks it as CyanogenOS, the commercial product. So CM12 would be the community maintained Cyanogenmod. CM12S the product by the company Cyanogen. As said before, it's a bit complicated, as the current OFFICIAL rom is OxygenOS
Your findings of software not present in the official stock Oneplus One rom (which is either CM12S or OxygenOS), suggests your software on the phone is actually a unofficial costum rom.
- Some say having a custom rom invalidates warrantee, is this right?
Click to expand...
Click to collapse
See the answer to the rooting question. Almost all major phone manufactures void your warranty if you flash a custom rom. As it involves tampering with system files and most people are not very knowledgeable when it comes to "computery things". It's just a security measure, so that people won't sue the company when something bad happens (most likely deleting precious pictures, etc.)
Oneplus actually encourages people to try other roms. This made the Oneplus One a very popular phone for tinkerers and as you can see on this forum there are a lot of custom roms you can choose from.
- How do i prove that the rooting and the custom rom were not introduced by me?
Click to expand...
Click to collapse
If the seller was not so careful, there will be a notice, which can be read by software programs available here on XDA, that say how many times a custom rom was installed.
However, i think your main concern is, that you wouldn't be able to get support form Oneplus, because you think your warranty is not valid anymore. As said above, your concerns are not that problematic. Especially as you seem to be knowledgeable enough to actually fix things on your own!
- I have thought about factory reset, but I cannot manage to find anything that tells
me what this actually means and does, only how to do it.
Click to expand...
Click to collapse
A factory reset will delete all your apps and reset the system to the state"it came out of the factory". So when you start up your phone, you need to set it up again. Enter your name, configure your WiFi settings, install your favorite apps.
However. Your photos and your music files will not be deleted! Be careful though. Resetting your system will delete your app settings. I just want to point that out, because the first time a did a factory reset and reinstalled everything i thought i lost all my Whatsapp photos. They were there in the Picture folder, but weren't linked to the images in my chat window! This is a bit complicated, but can be solved quite easily, if you know what your doing (backing up your apps with certain programs, e.g. Titanium Backup).
- does a factory reset actually do what it suggests. I have read that factory reset does
not involve going to the manufacturers site and obtaining an appropriate image and flashing
it to the phone so I do not quite understand how else it could guarantee it
Click to expand...
Click to collapse
Factory reset is a internal function of your phone (to be precise of your phones recovery!)
However, as most people said and your suspected is: Your phone does not run the official factory image, provided by Oneplus (or Cynaogen).
The official software can be obtained from
https://oneplus.net/de/support/answer/how-can-i-download-oxygen-os
- If a factory reset will just make it like it was when I received it then that I do not want.
Click to expand...
Click to collapse
Yes it will most likely to what you fear. It depends on what the retailer did. Most costum roms include software in their phones, that will be installed again with a factory reset. If your seller did install the programs AFTER the phones original state (e.g installing it from an appstore or from the APK's (Androids Software Packages)) they won't be present!
- Can I and ought I to flash a fresh image on the phone to get it like it WOULD HAVE been
had I bought it from OnePlus factory on invite and not through a mediator
Click to expand...
Click to collapse
Absolutely! I'd recommend you to flash a new image to your phone!
There are a lot of great programs here on XDA that offer easy and intuitive options of doing that, without even knowing anything about flashing programs! Try to take a look around and see what you can make of it.
I personally think they are great, but can be dangerous if you didn't read the proper instructions. I'm just saying, as they often delete EVERYTHING on your phone. So whatever you do to your phone, backup everything before!!!
But these simple programs are what you are looking for. They will install the firmware (Cyanogenmod or OxygenOS) that are bloatfree and as the Oneplus intended them to be.
- Finally. There is a notification "System Update is ready" . When I select this it appears
to download something (next version of cyanogenmod I guess though I don't recognise the version
number against any cyanogenmod versions) then it restarts and goes to a recovery app.
At this stage it is not completely intuitive what one should do and it seems to want you
to navigate to a location.
Click to expand...
Click to collapse
This further suggests, that your are not running an official version. The official update process is fully automated and doesn't need any user intervention! From your description it doesn't do anything and you are stuck in recovery, that is waiting for user input. This is not the case with proper official roms!
Now, I think I could probably figure this out with some reading but two things come to mind:
1) Presumably for a from factory OnePlus phone this kind of ambiguous unintuitive update
process would not be going on for people who just bought their phone and knew nothing
so it suggests the phone is in a different state to that.
Click to expand...
Click to collapse
Absolutely correct! See above.
I also read you need root
already to install a (good) recovery app.
Click to expand...
Click to collapse
You do not need root to install a recovery. This is a bit complicated, as there are some misconceptions about what is what. You need to "unlock" your phone to install another recovery. This is not rooting, but is also restricted by many manufacturers. But as with rooting, Oneplus is offering support on unlocking your phone and there are lots of guides on how to do it.
2) I am loath to do this update since it is not clear whether the update is this retailers
system update and will reintroduce all that I have disabled to create stability. Therefore
up to now I have always selected just do nothing and reboot. I favor stability over
features.
Click to expand...
Click to collapse
Wise decision.
I am kind of inclined now I have managed to get it stable to just stick with it as it is and just use it without any further updates / resets / flashes and without returning it, but...
Click to expand...
Click to collapse
I would strongly recommend to NOT leave it this way! As you yourself found out, there are chances that there are programs on the phone, that are not to be supposed to be there. I'm not saying that there is spyware on your phone, but it is most likely that there could be malicious code running in the background of your phone. I would strongly recommend NOT to use apps, that need sensitive information of yourself!
Try to look for guides and tutorials here on XDA and just install CM12S, Cyanogenmod or even better OxygenOS, the official ROM from Oneplus! OxygenOS is not everyone's favorite choice, but that way you can be sure, that NOTHING fishy is going on on your phone!
There is an easy app available from the offical oneplus site!
https://oneplus.net/de/support/answer/how-can-i-download-oxygen-os
Or use the app that is mentioned in the post above! Will to the same thing!
Use the instructions on there and you are much safer on using your phone than you are in the present state!
BUT PLEASE, PLEASE DO A BACKUP OF YOUR DATA! I mean, your photos, contacts and everything important before doing anything to your phone. I'm just stressing that out, as so many people complain afterwards that they lost everything, etc.! Not just because the process they did was unsafe, but becaus the didn't properly read the instructions that tell people that they should make a backup, BEFORE tampering the system. It says factory RESET, so it should be clear, that everything will be reset!

I'd suggest you return it and get one through official channels. Official OnePlus devices can only be purchased through the OnePlus store.

I'd suggest you to read this story:
https://medium.com/@tuesdev/as-many...ve-a-oneplus-2-invite-ba20ac8606ae#.qgq3fhmn7

Ctuiku,
Sorry I wasn't able to respond sooner. I really do appreciate your very clear and detailed response and it's care to address each point very clearly and to make clear distinctions between similar things gives me significant confidence in its accuracy.
I must say I appreciate the significant amount of time you have taken and I do hope that at least some of your responses were cut and pasted from text you had already written else where.
I think I may have a number of minor follow up questions, but for now I shall digest your advice and decide on my plan of action.
Thank you again for being so helpful and understanding.
Andrew

I actually didn't read much of it and the comments, but I'd suggest you to unlock the bootloader, flash TWRP, take a backup, wipe everything(not the internal storage of course) , and perform a clean flash of CM13.0 by sultanxda. It's the smoothest and the most stable ROM out there.
Well, that was all in brief. You gotta read(and understand) and perform. It's fun, just like programming. Keep flashing!
~noob (you gotta start from somewhere)

Ctuiku
Thank you again for all your help. Sorry for the delay in responding been busy with other things and also since had some time to digest...
THIS is the OFFICAL Android Software Version for your Oneplus One!!!
See: <I am not allowed to include this link in quote>
I would strongly recommend to install OxygenOS
Click to expand...
Click to collapse
This link appears to be out of date
or even better OxygenOS, the official ROM from Oneplus! OxygenOS
Click to expand...
Click to collapse
My search and his post
_forums_oneplus_net_threads_mirrors-for-official-oxygen-os-roms-and-ota-updates.387615
suggests you cannot get the official OxygenOS ROM from Oneplus, doesn't this pose some risks using TP apps to download and flash OS ROM?
There is an easy app available from the offical oneplus site!
<I am not allowed to include this link in quote>
Or use the app that is mentioned in the post above! Will to the same thing!
Click to expand...
Click to collapse
Doesn't this pose some risks using TP apps to download and flash OS ROM?
Also the official link
_account_onepluscontent_com_downloads_tools_oneplus-one-reflash_zip
appears to be out of date
I cannot seem to find a way to find an official location or to identify the genuineness of CM12S image or OxyGenOS image. Is there some kind of published standard hash of the file or something? How does it work?
a lot of what I read, like on the oneplus site or the way links are named seems to suggest that OxygenOS is just for OnePlus Two. I believe that OnePlus One moved to OxygenOS at some point, but I don't want to apply an OS version to a device that is under resourced. Is there a version of OxygenOS that the OnePlus One should not go beyond.
P.S. How do I get your XDA user name to appear as a link?

iamelton
Thank you so much for your advice I really do appreciate the time you took to help me. Sorry for the delay in responding. Difficult circumstances.
regarding your point (7)
(7) while in recovery, install rom image (which should be put in the internal storage beforehand)
Click to expand...
Click to collapse
- I wonder if you would mind indicating where beforehand in this list putting the rom image in the internal storage ought to occurr?
- Also, so sorry, but I wonder would you mind elaberating just a little on how to put the rom image in the internal storage?
Regarding the files, I am happy with adb.exe, fastboot.exe, TWRP.
However I understand that the genuineness of OxygenOS images are not provided by OnePlus, is this right?
_forums_oneplus_net_threads_mirrors-for-official-oxygen-os-roms-and-ota-updates_387615
How do confirm the genuineness of OxygenOS images?
Is it a kind of hierarchy of trust, i.e. n users use and recommend this location for the images.
Or is there some kind of standard hash for the images that is published on secure OnePlus site?
I have similar issue / understanding issue with CM12S
It would appear after roaming around forums etc that the official Cyanogen OS (not mod/custom) are located below here _builds_cyngn_com_ but the site itself seems to have no web pages I visit cyngn.com_get-cyanogen-os but can find no page with a list of rom images and their corresponding dates, attributes and inclusions etc.
I hear that some versions of CM12S do not support 64GB (as per my OPO) but I seem to have no clear certified single source way to know exactly the name/url of the CM12S I should get.
I am probably misunderstanding the philosophy behind things, but it seems if anyone can do anything with the source you would think that OnePlus would into the bargin also provide users (of which there will be a variety) a "sure fire" way to get their (grey market?) phone to (original) factory standard. They still apparently cover it for warentee, so...
Many thanks
P.S. How do I get your XDA user name to appear as a link?

!!To all the new Essential Phone owners who recently cashed in on the Amazon deal!!!!

read this 3 times from start to finish before you start asking questions....itll help with most of your questions...also...
When your unlocking your bootloader using the "fastboot flashing unlock" command....after the system has booted.... boot back into fastboot and also run the "fastboot flashing unlock_critical” this makes this device nearly unbrickable.... please do it you won't regret it.
Next twrp is in boot.img with a/b devices..so if you flash twrp and want to root you have to reflash the stock boot.img of your rom before you flash magisk....if you don't you'll have a bootloop that gets you nowheres
http://mata.readthedocs.io/en/latest/

Also, welcome to the forums! Hopefully posts this don't scare away people and potential new devs since it's dead enough around here already.
Feel free to message me if you have questions, I won't jump down your throat.

Thank you for this.
Switched over from a Nexus 6P (that is still working great, to be honest). can't wait to start flashing

Thanks for the link to the document. Didn't realize there are two partitions.
I'm sure this question has been answered before but I'll ask here again for the newbies.
If I root the device with Magisk but stay with the stock ROM, does the OTA updates work? If the updates do work, do I have to root each time after the update?
TIA.

csrow said:
Thanks for the link to the document. Didn't realize there are two partitions.
I'm sure this question has been answered before but I'll ask here again for the newbies.
If I root the device with Magisk but stay with the stock ROM, does the OTA updates work? If the updates do work, do I have to root each time after the update?
TIA.
Click to expand...
Click to collapse
They don't work if rooted, however I, and many others, have issues with the OTAs in general anyhow.
It's super quick to just fastboot flash the firmware files yourself anyhow (modify a boot.img beforehand with magisk), and then flash the modified boot.img at the end.

I got in on the Amazon deal...should be here next week. Will be coming from a Nexus6.

Quick question for a Prime Deal newbie. Do you have to unlock the bootloader if you are just side loading the OTA file? I know you have to in order to fastboot any images but I thought the ota file would be fine. No biggie if not just curious.
After another search it looks like you do not have unlock the bootloader just to flash the ota.

Really helpful and it definitely going to keep the rest of the section tidy!

Picked one up also. Coming from/still have a Pixel 2 xl and previously a first gen pixel, so I'm familiar with a/b slots. Not having a perm twrp suuuuuucks. I got my ph1 on Sept security patch and it's updated twice now to the Jun patch will that cause issues with any root or roming?

Also coming from the Nexus 6. Looking forward to this phone.

thank you for the heads up.
Sent from my SD4930UR using XDA Free mobile app (Yep Firephone)

crixley said:
Also, welcome to the forums! Hopefully posts this don't scare away people and potential new devs since it's dead enough around here already.
Feel free to message me if you have questions, I won't jump down your throat.
Click to expand...
Click to collapse
Thanks for the welcome everyone!!
Coming from a Nexus 6 running PureNexus. Phone is still rocking, but my goodness you should see how busted my screen is.
I'm excited to get the Essential set up and flash some ROM and camera goodies!

Tech_Savvy said:
read this 3 times from start to finish before you start asking questions....itll help with most of your questions...also...
When your unlocking your bootloader using the "fastboot flashing unlock" command....after the system has booted.... boot back into fastboot and also run the "fastboot flashing unlock_critical” this makes this device nearly unbrickable.... please do it you won't regret it.
Next twrp is in boot.img with a/b devices..so if you flash twrp and want to root you have to reflash the stock boot.img of your rom before you flash magisk....if you don't you'll have a bootloop that gets you nowheres
http://mata.readthedocs.io/en/latest/
Click to expand...
Click to collapse
Thanks for the heads up, wonder if it will help the people who don't know which hole to put the sim card removal tool into.

[emoji23] I watched my brother keeps poking the microphone hole for like the 5th time until he figured it out. It is kind of a bad design imho tho.
Sent from my PH-1 using Tapatalk

This seems a welcome thread. I haven't tweaked Android for about 2½ years. From 2010 on I always had custom recovery and root and ROMs, but my last device (htc10) I didn't root, life got too busy.
Just got essential from Amazon, and trying to figure out what this AB slot stuff is is confusing the hell out of me. Also, this phone seems laggier than any device I've had, and I also just noticed a lot if the text is outlined with black, like on the LG get. Gotta get rid of that.
Sorry if this is the wrong place for those comments.
If anyone could give an explanation to what the AB slot is, to someone who is already pretty familiar with using custom recoveries, and understanding the partions (to a degree), I'd super appreciate it.
Again, I've been away from xda and customizing Android for about 3 years.
Anyone else feeling like this device isn't quite what they hoped? I always saw it at sprint stores and couldn't put it down. Now it's in my hand, doesn't seem so great. Think my htc10 is better, but maybe I'm missing how to make it great.
I hope this is in the right place.

scottspa74 said:
Anyone else feeling like this device isn't quite what they hoped? .
Click to expand...
Click to collapse
you can't beat it for $250, but I think I'm getting the OnePlus 6T or OnePlus 7 when it comes out.
installing TWRP and customs roms is such a chore on this device. I had AOSiP installed...but for some reason which I couldn't explain, it didn't feel like AOSiP on my Nexus 6P or OnePlus5 (that I just gave to my mom). Substratum worked...Magisk worked. But something didn't feel right. If I'm going to have to be on a stock ROM, I'd rather be on OxygenOS with its additional customizations.
only one of my 9 USB-C to USB-A cables seem to work for file transfer AND fastboot AND charging. It also happens to be the shortest cable I have.

See this weirdness where text is surrounded by black outline? That happened on LG g stock rom. It was fixed. Is a custom rom only way to fix this on ph1. ? Much thanks.

scottspa74 said:
See this weirdness where text is surrounded by black outline? That happened on LG g stock rom. It was fixed. Is a custom rom only way to fix this on ph1. ? Much thanks.
Click to expand...
Click to collapse
I think your phone high contrast text mode is on. Uncheck that under accessibility

scottspa74 said:
This seems a welcome thread. I haven't tweaked Android for about 2½ years. From 2010 on I always had custom recovery and root and ROMs, but my last device (htc10) I didn't root, life got too busy.
Just got essential from Amazon, and trying to figure out what this AB slot stuff is is confusing the hell out of me. Also, this phone seems laggier than any device I've had, and I also just noticed a lot if the text is outlined with black, like on the LG get. Gotta get rid of that.
Sorry if this is the wrong place for those comments.
If anyone could give an explanation to what the AB slot is, to someone who is already pretty familiar with using custom recoveries, and understanding the partions (to a degree), I'd super appreciate it.
Again, I've been away from xda and customizing Android for about 3 years.
Anyone else feeling like this device isn't quite what they hoped? I always saw it at sprint stores and couldn't put it down. Now it's in my hand, doesn't seem so great. Think my htc10 is better, but maybe I'm missing how to make it great.
I hope this is in the right place.
Click to expand...
Click to collapse
I am with ya on that...I started with Samsung devices, So using Odin for flashing was my cup of Tea. The Nexus6 was my first device using Fastboot, but I ended up using Wug's toolkit most of the time.
From what I gather the A/B slot partitions are the same thing. You basically have a kernel and ramdisk on both partitions. The ramdisk is now your recovery. You just have to make sure when you flash anything, it's to the active partition. The point of A/B slots is so Android can install upgrades seamlessly while still running by installing them to the inactive partition. Click the link in the OP, it explains things pretty well.

I have been pretty happy with the PH-1 so far. I really like the form factor and the notch hasn't bothered my at all. Coming from Note 3/4 and the 6P which was super easy to flash by the extra steps on the Essential don't seem to bad. Sucks that you need a computer most times to flash but not the end of the world.
I haven't flashed a custom ROM yet but I did bump to the P preview for a day or two and then back to stock with EX and Magisk. No issues there but I'm comfortable with ADB and fastboot. No issues with various cables as well whatever I used on my 6P seem fine for this phone as far as charging, adb and file transfers go.
Overall pretty happy.

Proper OS cleanup of new OnePlu7 Pro

Hi Everyone,
Living in Japan, we have no official channel to purchase a OnePlus handset here.
Really wanted to get a OnePlus 7 Pro as I felt it is the best model on the market as of today.
Knowing that, I got mine on Amazon Japan from a HK online shop which had very good reputation.
Now, the problem is these phones always come already opened as they say they need to confirm operation before sending it.
I have been reading news and article about this where we see more third party companies flash their roms with malware/ransomeware already built in...
In these situation, the best way to clean the phone is to do a full re-install of the OS.
I did review a bunch of article on XDA and it seems that now, due to the A/B partition setup, we can't just use official OnePlus image to load from the fastboot easily.
We have to rely on community provided too and stock rom to be able to do so....
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Sorry if I sound paranoid. Ideally, I understand the best thing to do was to buy directly from Oneplus and work a way to have it shipped to Japan but thought it would be interesting for me to learn more about android.
With previous Oneplus, it was easier as they were provided this type of official file for recovery but they stopped...
Thank you again for your time and hopping to learn more about how new android setup works.

Is the bootloader locked? Is Widevine (Netflix HD) certification still there? You can check these things to see if the phone has been tampered with.

brissoukun said:
Hi Everyone,
When I raised the question to OnePlus and Oneplus forums, they mentioned to me that installed the updated like here (Page: support.oneplus.com/app/answers/detail/a_id/4312/~/oxygen-os-for-oneplus-7-pro)would do the trick using the local update function.
What I was directed to do is use the recovery boot to delete system settings/cache and everything data user and then, run the local update. Doing so, that would do it while not using community tools.
Here are my questions and which I would hope to get your experience:
1 Is the process I did really does use a brand new clean OS and do not rely/integrate part of the OS that came with the handset originally (that was the target).
2 Is there a way for me using OnePlus only provided tools and image to fully delete the phone and install the OS (maybe I am thinking this too much like a PC which I have more experience with...)
3 The OS looks fine and no strange apps shows up at all but how can I be sure nothing dodgy is running? Is there tools I could use to confirm this?
Thank you again for your time and hopping to learn more about how new android setup works.
Click to expand...
Click to collapse
Good questions. Before you start, check the model number of your device through Settings > About. I'm assuming it's the international/global/unlocked version (GM1917).
With regard to question 1, a full build downloaded from the link you provided should contain every part of the OS, and flashing it through local update should overwrite anything that was there before. Before flashing, I would perform a full data wipe through recovery like you mentioned.
Q2: There is an MSM tool that will completely flash a system image for the OP7 Pro. I don't think they're generally intended for public use but they always get leaked anyways. They write an image (in the case of OnePlus, a .ops file) to the phone using a PC and USB connection. Here is a link to a thread which contains the MSM tool:
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Download the tool for the model of your phone (probably the international, firmware GM21AA), and extract its contents into a directory. In order for the tool to work, you need the OnePlus USB drivers installed on your PC. Plug the phone into your PC with it on, and enable USB file transfer. Open File Explorer and you should see a drive labeled "OnePlus drivers" or similar. Open it and run the driver setup executable file. You'll also need ADB to make your phone reboot into a mode that will allow the tool to perform its tasks. Here is a guide to installing ADB:
https://www.xda-developers.com/what-is-adb/
Once you've set that up, make sure the phone is plugged into the PC and the MSM tool is open. Make the phone boot into edl mode by typing
Code:
adb reboot edl
and once it says Connected next to a COM port in the tool, press start. Don't interrupt the process until it completes the download and the status message turns green. The phone should automatically reboot. This method is arguably more risky than using the local upgrade option, so do it at your own risk.
Q3: Make sure that OEM unlocking is turned off in developer settings and that the bootloader is locked (if the bootloader is unlocked, you'll see a yellow warning message after you power on the device from a power off state). Without an unlocked bootloader it would be pretty difficult to make any deep modifications to the device.

Hi @Zocker1304 and @TManchu,
Please let me thank you very much first for your kind and detailed reply, this is really welcome.
@Zocker1304:
I checked using the ADB/Fastboot connection that indeed, the Bootloader is locked so, that looks good.
Also installed (using a separate Google account) DRM Info app to confirm that the Widevine is properly installed and at L1 level which indeed again, looks good.
@TManchu
Thank you again for your very detailed reply! This was exactly what I needed as information.
I did already exactly as mentioned for the #1 so, it looks I should be good now with a proper rom from OnePlus (and did a full wipe in the Recovery boot mode)
For #2, I think I will skip that since as you rightly said, with #1, it should be fine so, prefer to keep with the recommended step.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:

brissoukun said:
.
For #3, we are covering what Zocker1304 mentioned too and I could confirm it.
My only concern about #3 was that you can actually relock the bootloader but (and please correct me If I am wrong), you can only do so if you are using stock OnePlus images (to date...seems like dev teams are working to have this changed? Bootloader locked with custom firmware?) which then means the image is safe.
I suppose the last item was my only open query for your thoughts but so far, the handset looks fine.
Thanks to you and the community, I have learned about the A/B partition scheme, msm tool, Fastboot/Recovery mode and Bootloader and ADB tools.
It is always good to learn more about the tech we use (especially phones, we have so many sensitive information stored into them today).
Not being careful could potentially means quite a lot of troubles down the road with Ransomeware/data leak tools.
Of course again, I could have simply purchased a JP phone from a brick and mortar shop next to my place and be fine with it. :silly:
Click to expand...
Click to collapse
No problem! I’ve just done some reading and from what I understand, re-locking the bootloader on anything other than a completely stock ROM will result in a bricked phone. I believe this is due to the way Android handles data encryption. If what you’ve heard is true, being able to lock your bootloader on a custom ROM would be great for device security. However, should something go wrong with the ROM having a locked bootloader might make it more difficult to fix.

I know that there are ways to sign system and boot images so that you can lock the bootloader with them installed, but I think that would still show a warning though I'm not sure.
Anyways, if all the build dates and numbers in the system info are correct, the firmware should be stock and as long as the bootloader is locked too, I don't believe you can tamper with that.

Hi Gents,
Thank you very much for the answer to the thread and much appreciated.
Apologies for not getting back to you all earlier as yesterday was family day...haha!
Well, since things looked good on the OS and the build, I went ahead and started to use the phone properly setting up my accounts. It did give me some incentive to get all my sensitive accounts setup with 2FA so that in case I get hacked with my passwords in the future...they would still need the 2fa (using Google Authenticator).
I did check also all system apps/running process and didn't see anything shady.
Just for reference, here were the type of articles I was refering too for the OS being plagued with malware even out of the box:
Page_theverge.com/2019/6/6/18655755/google-android-malware-triada-ota-rom-ads-spam-oem (sorry gents, new account, cannot put links yet)
However here, it seems it is due to lax review from the maker to third party tools which were including malware...
To have the same level on the oneplus I bought from the HK shop, they would have needed access to OnePlus Dev team to inject the malware in official image (knowing anyway I have re-installed a new image from the local update).
Otherwise, I was reading on the web about the fact to relock the bootloader with a custom roam and there seems to have a lot of messages but not concrete steps. It seems it depends a lot on phone model and brand.
When you are checking
Page_gizmochina.com/2019/06/10/relock-bootloader-oneplus-7-pro/
This is where you can read at the end:
"The above method only works if OnePlus 7 Pro is running on stock recovery and stock firmware. The ability to relock devices running custom recovery is expected in the next few weeks. "
That was published last month so, not sure if they got this to work on the OnePlus 7 pro yet.
So that's it, I am now using my new device which looks to work great and hopefully, won't get any bugs down the road.
I appreciate you taking the time to get back to me and will continue to learn about android.:good:

New Project?New Root Answers? LG Stylo 6 and a TWRP??

Hi everyone I just got a lg Stylo 6 from boost. I was hoping that as I picked mine up for pennies(50$) that there would be a way already spoken, that doesn't seem to be the case. I heard that taking KDZ rom info and splice the original r software and patch it through magisk. This can be don? I hope so . But what I was going to do was start a thread that supports having a TWRP
Built for it would be better, I've got (40$) onit being a new created re covery would be better, idk I haven't been online in years since
The J3 emerge was the last thing I worked on as a tester, that I could get a gang of people needing the TWRP too. Anyone down?? (7876006741) that's my work number for phones and like minded things. So anyone down to start this new project let me know I'll hit up Ashyx when I get enough behind it. Thanks

Its looking like there is gonna be a flood of people now needing a TWRP for the Stylo 6 now there is a bootloader unlock & root-I myself being one. Start(if you wish) to post what you need & lets get this baby rollin'!!!

I tried to contact twrp them selves but like they say on their site they rarely respond and I've got no response, I've used Hovatek's twrp porter tool and I've not had any success. My discord group is nearly done with the V60 twrp and I might be able to get the developer working on that to build one. I've got no experience building a twrp myself or else I'd give it a shot, but being a mediatek device with a-b slot It will be more difficult than a regular custom recovery build.

Warlockguitarman said:
I tried to contact twrp them selves but like they say on their site they rarely respond and I've got no response, I've used Hovatek's twrp porter tool and I've not had any success. My discord group is nearly done with the V60 twrp and I might be able to get the developer working on that to build one. I've got no experience building a twrp myself or else I'd give it a shot, but being a mediatek device with a-b slot It will be more difficult than a regular custom recovery build.
Click to expand...
Click to collapse
You're quite the intellegent fella. Have you tried to make any custom TWRP recoveries for any mediatek based chip-ed devices? (almost typed chipset. )
At this point, I wouldn't even care if Stylo 6 ever got a TWRP. Outta give it a try to a custom one yourself and see if you can add a new feather in your cap, war-locked guitar man? (ok ok, will never make fun of the awesome name again. Old habits, never feed the trolls after midnight!)

Whoops, just ran across this after the comment from earlier. This answers my question, I retract my previous comments and questions. Wish you a good day, dude.