yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 Android Development] thedropdead:
Requirements:

[ROOT REQUIRED]

[OEM Unlocking must be allowed under the developer options before flashing this file AND

stay activated

as long as you want the device to stay unlocked (OnePlus implemented security features which locks the device on reboot with the switch off)]

WARNING: THESE FILES ARE BASED ON THE OXYGEN OS 2.1.1 FIRMWARE, PLEASE ANALYZE YOUR DEVINFO IF THE VERSION IS DIFFERENT TO MAKE SURE NOT BRICKING SOMETHING!

I have not upgraded my device to 2.1.2 yet because there have been some issues with the newest firmware.

Tested and confirmed working on:

OxygenOS 2.2.0 - thanks to [MENTION=6907559]pryggi[/MENTION]

OxygenOS 2.1.1

Hydrogen OS 1.2.0 - thanks to [MENTION=4844194]fareed_xtreme[/MENTION]

I looked at this thread, thanks to Naman Bhalla for this great work.

and found out that the file attached to this post is the answer to my problem, described in another thread.

After the whole day of work analyzing and dumping and saving via adb from my device to the pc and the other way around i finally did it.

On the frist screenshot is my situation before flashing the new devinfo, on the second after flashing the devinfo from the thread mentioned above.

By changing the bits with a Hex Editor of your choice, or by flashing the files below via dd:

dd bs=4096 of=/dev/block/bootdevice/by-name/devinfo if=/sdcard/oneplus2-devinfo-factory.img

The output should look like the following:

0+1 records in
0+1 records out
1024 bytes transferred in 0.005 secs (204800 bytes/sec)

You can restore your OnePlus 2 to a factory state while still having root or unlock your phone again without having to wipe it! :highfive:

Credits:

Naman Bhalla

Also to segv11 who already managed this in the OnePlus One and Nexus devices :)
[OnePlus 2 Android Development] 22vlaja:
wow nice job m8

sent from rooted phone
[OnePlus 2 Android Development] fareed_xtreme:
Modified the same location using a HEX Editor (root) whilst on the Hydrogen OS 1.2.0 and I must say it works.

Screenshot Attached. Good Find [MENTION=5549875]thedropdead[/MENTION]
[OnePlus 2 Android Development] thedropdead:
Thank you and thanks for testing it out on Hydrogen OS [MENTION=4844194]fareed_xtreme[/MENTION] ;)

It is not a Revolution like CM13 on the 1+2, but its helpful for people like me who use their developer devices as daily drivers and still want to lock and unlock the device because of security reasons without wiping the whole device. ;)
[OnePlus 2 Android Development] fareed_xtreme:
I needed it for resetting the tamper flag. I have certain issues with my phone and might have to return it in the near future and hence this was important. So thanks again.
[OnePlus 2 Android Development] thedropdead:
Thats another good thing to do with it ;)

It was a pleasure to help you out mate :)
[OnePlus 2 Android Development] pryggi:
Thanks, I was waiting for this for securing my OPT. Has anyone tested, if it works also on OOS 2.2.0?

Just to clarify, the dd command should be executed in TWRP console?

Would be cool if someone could make an app for this like the Nexus devices have:

https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
[OnePlus 2 Android Development] thedropdead:
Hello pryggi,

It should also work on OOS 2.2.0, you could check that by dumping the partition (by reversing the dd command) like this:

dd bs=4096 if=/dev/block/bootdevice/by-name/devinfo of=/sdcard/oneplus2-devinfo-oos220.img

And looking at the file in the hex editor for differences or by posting it here and i can check it for you. ;)

I have executed the dd command from ADB Shell with the Phone connected via wireless ADB.

You can also execute dd in the Android Terminal Emulator App.
[OnePlus 2 Android Development] pryggi:
Thanks for your reply. My device is already unlocked. As I don't have a computer with ADB/drivers at hand right now, I managed to run the dd command in Terminal Emulator app after elevating with su. Result is attached. Viewing it in hex seems to confirm, that at least the locking bit seems to be in the same position.
[OnePlus 2 Android Development] thedropdead:
Thank you for the Dump, i can confirm that the bit is at the same position and the unlock bit is the same.

I compared the file attached at my first post with yours and they are identical ( see attachment, sorry its german, meaning is they are identical).

So by flashing the factory.img from my first post or unchecking OEM Unlock allowed in the developer Settings your device should be locked again and can be unlocked by flashing the unlock.img via dd in ADB or the Android Terminal Emulator within the Phone.
[OnePlus 2 Android Development] pryggi:
Thanks for the further explanation. I was just wondering about this OEM Unlocking switch in dev options. What would happen, if one would use dd and the factory image file to lock the bootloader and leave the OEM Unlocking switch still unlocked...

I also am interested if this type of locking-unlocking can be done in TWRP... If it can be done there, then it does not offer any benefits in security, if my logic is correct. Although, I might be drifting off topic here.
[OnePlus 2 Android Development] thedropdead:
As i can remember i tried that too, by flashing the factory image partition via dd and leaving the switch on, the switch gets toggled off when rebooting, because the switch is just the representation of the unlocking bit in the partition. So when it is turned off, the software will set the bit to zero, means the device will get locked on reboot. Turning the switch on will not override the bit and the device can boot unlocked and the switch will stay on.

It is hard to explain ;)

Your Idea about doing the same thing in TWRP since the ADB is available there is interesting.

I think the problem here is, that once you onlock and flash a custom recovery via fastboot, and relock the device, you already tampered with it, and twrp does provide much more options than the stock recovery image (ADB commands, ...).

So the problem here lies in flashing twrp.

I solved this problem by keeping the stock recovery and locking the device via the image file.

Once i want to use twrp, i unlock the phone by using the unlock.img and use "fastboot boot twrp.img" to boot twrp to backup my device or some other action.

I know that this means if my device gets bricked in this locked state with stock recovery i will have to unlock it normally, but before making any important changes to my software i always unlock my device first in case something goes wrong and with the stock recovery i could not even flash anything so making huge software changes requires me to unlock my device and boot twrp ;)

Hope that this post helps somehow ;)
[OnePlus 2 Android Development] fareed_xtreme:
FYI: The HEX hack must work on almost all OPT OS Releases.Kinda universal :P
[OnePlus 2 Android Development] thedropdead:
That is right, i just included the notice in the first post so nobody can tell me i have not told them ;)

It is also possible that OnePlus changes the layout of that partition in one of the upcoming updates/releases and that is why it is still mentioned in the first post, thank you anyway. ;)
[OnePlus 2 Android Development] casual_kikoo:
[MENTION=5549875]thedropdead[/MENTION] I've a question: I should use the "modified" devinfo.img AFTER I go back to stock, if I want to unlock my phone without wiping data, right ? So I go back to stock, flash in fastboot or in terminal emulator the .img, and that's good ? I'me unlocked without data wiped ?
[OnePlus 2 Android Development] thedropdead:
That should be the plan if i have understood everything right.

So you are on the custom ROM, want to go back to the stock ROM?

If that is the case i do not see why you should want to flash any image. ;)

You can use TWRP to wipe and then flash the stock ROM, your phone should still be unlocked right?

Please someone correct me if i am wrong.

It would be great if you could tell me what you are trying to achieve. :)

The unlock image had the purpose to help someone unlock their device if they have a rooted device but have locked it after flashing everything for security reasons.
[OnePlus 2 Android Development] casual_kikoo:
Well, for now I'm under CM13, and, yeah, I know I could wipe and flash stock in TWRP, I just want to know in case ;).
[OnePlus 2 Android Development] thedropdead:
Okay thanks for the clarification.

In the Case of using some unbrick Tool and thus resetting everything including recovery to stock your phone should lock on the first stock boot.

Once it is locked and you do not have root, which would be the case, you have no possibility to flash the img via fastboot or the emulator.

so in conclusion you are better off with wiping and flashing via twrp so you can still flash something if anything goes wrong ;)
[OnePlus 2 Android Development] qwert.zuio:
It works on OxygenOS 3.0.2 too. I edit the same location using a HEX Editor. And everything is fine.
[OnePlus 2 Android Development] psiphiguy:
Hey guys, sounds like this is exactly what I've been looking for. Thanks for figuring this out.

But, I'm a bit of a noob, so can you break it down into like a hundred very clear steps?
[G3 Q&A, Help & Troubleshooting] FawkiDied:
I have a stock lollipop from and idk if it is worth switching over to CM13. I have a D850 so there are a couple unofficial builds. Why should I switch over to CM13 to M compared to my 5.1 rom?
[G3 Q&A, Help & Troubleshooting] nesovidiu:
If you like your camera software,menu and other accesibility items you should go for a cusyom rom based on official L...you can search for Cloudy g3 or trix which is a forward for the Cloudy G3
[G3 Q&A, Help & Troubleshooting] FawkiDied:
Im using Cloudy. I like stable, batterym customization
[G3 Q&A, Help & Troubleshooting] matthew33:
IMHO...CM13 sucks compared to standar L.

Matt
[G3 Q&A, Help & Troubleshooting] FawkiDied:
Can you tell me why?
[G3 Q&A, Help & Troubleshooting] donjamal:
I tried xenon HD and it flew compared to anything I had on this phone. But there are bugs and the camera sucks on any aosp roms
[G3 Q&A, Help & Troubleshooting] tietganFTW:
this question has been asked countless times on this forum already, i'll just summarise the main few points for you here. i'm using candysix so i can only comment for that since i've heard cm13 has many bugs and SOD's.

advantages of stock over cm13:

1. Camera - g3 needs lg framework to record 4k videos, so AOSP roms like cm cannot shoot 4k. Normal camera quality is also nowhere near stock quality, although you can flash camera mods to improve the quality (i'm using one m9 camera mod)

2. You don't break your warranty (if you still have one)

3. There are minimal bugs and crashes compared to AOSP

4. Can use LG apps like Miracast, Qslide apps, QuickRemote

advantages of cm13 roms over stock:

1. Much, much smoother UI. almost lag free

2. Battery life is about the same as stock or even better for me

3. No lg bloatware

4. Stock android experience

5. It's Marshmallow!
[G3 Q&A, Help & Troubleshooting] Wj287:
that's where you're wrong. With the m9 camera if you have the patch you can shoot 4k video.
[G3 Q&A, Help & Troubleshooting] FawkiDied:
So should I switch over? Or not? Im still wondering. I have a neat stock rom. I dont shoot videos if at allbut I liek battery life, and I do use the camera for photos decetnly often not to much.
[G3 Q&A, Help & Troubleshooting] tietganFTW:
i can't seem to find the option in the camera app, the highest quality for me is FHD 1080p
[G3 Q&A, Help & Troubleshooting] petenoni:
Switch... Cm13 is awesome.

1. Google now on TAP is awesome.

2. Smooth, very smooth.

3. Makes me feel up to date hahaha.

4. You can install themes... Cool thing to do.
[G3 Q&A, Help & Troubleshooting] Wj287:
That's because you don't have the 4k patch
[G3 Q&A, Help & Troubleshooting] Wardoctor:
just use open camera it has 4k video and everything you need cm13 has been epic fast and stable with no issues and battery last about 17 hours each day when setup right only issue is SD card corruption
[G3 Q&A, Help & Troubleshooting] S.AMU:
Sd card is working for me on cm13. Just need to set it as external storage and not as internal
[G3 Q&A, Help & Troubleshooting] Wardoctor:
my SD is set as external still won't work right it's a 512gb mini SD card
[G3 Q&A, Help & Troubleshooting] S.AMU:
What? 512 gb?????
[G3 Q&A, Help & Troubleshooting] Wardoctor:
yup it has no issues with tx-i rom and holds music very well
[G3 Q&A, Help & Troubleshooting] Wj287:
The m9 camera is better
[G3 Q&A, Help & Troubleshooting] Wardoctor:
ask the opencamera dev to add the m9 features
[G3 Q&A, Help & Troubleshooting] S.AMU:
Are you sure you got a real 512gb card?? Because SanDisk only reaches 200gb and the only company who says are able to make 512gb is Microdia. But for now this 512gb card is not for sale. It's only a prototype presented in june this year. (see this)
[G3 Q&A, Help & Troubleshooting] Wardoctor:
I didn't buy it I just email company's sign a contract to review any future products they say and also test things as well the last thing I got sent was from AMD that was a month ago and soon I am being send a graphics design tablet for reviewing
[Verizon HTC One (M8)] fireball0093:
-Edit- Moving to general HTC One M8 troubleshooting forum. Mods feel free to close/delete this thread
[XDA Assist] spenzo:
I flashed TWRP on my LG L70 D320 with ADB and fastboot.

When I use adb reboot recovery, it enters a purple screen, and it enters the ram dump mode, I think.

I want to install the CM13, but I can't get the TWRP on my cellphone...what should I do?
[XDA Assist] v7:
Hello,

Thanks for using XDA Assist.

Try to reflash TWRP.Is your bootloader properly unlocked?

___

v7

XDA Assist
[XDA Assist] spenzo:
I got it all fixed and I got the CM13, but the home button won't work, why? My 'back' and 'menu' buttons don't work either, I'll have to visit a cell tech for that, but how to I use my home button for now?

EDIT:

I've made a new thread to my new problem...

http://xdaforums.com/general/xda-assist/cm13-installed-home-button-doesnt-t3275600
[XDA Assist] v7:
It used to work on stock ROM?

Try to clean flash the ROM again.

___

v7

XDA Assist
[XDA Assist] spenzo:
It did work on my stock ROM, yeah.

What do you mean by clean flash? I am pretty new with this stuff.
[XDA Assist] v7:
Wipe data,system,cache and dalvik cache from TWRP and flash the ROM.

___

v7

XDA Assist
[XDA Assist] spenzo:
the CM13 ROM?

flash the ROM, install the ROM, yeS?

EDIT:

I did what you've said, but my home button doesn't work.
[XDA Assist] spenzo:
Where do I get the stock rom?
[XDA Assist] spenzo:
What do I do after I download it?

EDIT: The flash tool doesn't reconginze my cellphone...It's plugged in and my comp reconginzes it perfectly.
[XDA Assist] v7:
Try this http://xdaforums.com/showpost.php?p=53955749&postcount=1

___

v7

XDA Assist
[XDA Assist] spenzo:
Why do I need that?
[XDA Assist] v7:
That thread includes the links to the firmwares and guide to flash the stock ROM.

___

v7

XDA Assist
[XDA Assist] spenzo:
I've entered download mode, but the LG Flash tool still doesn't reconginze my cellphone...
[XDA Assist] v7:
Drivers are properly installed?

___

v7

XDA Assist
[XDA Assist] spenzo:
I fixed it with downloading EasyTouch or some ****.
[Android Q&A, Help & Troubleshooting] jetpack_gorilla:
I've spend hours trying to find a solution to this brutally obvious shortfall, with no luck.

There does not seem to be a secure way to lock or password protect an individual app. Sure, there are lots of app lockers out there, but they are easily defeated be just restarting the phone in safe mode where they will be disabled.

Some could argue to have a stronger lock screen, but nobody wants to input a long strong pin every single time they pick up the phone to use a text.

The ideal would be to have a simple pattern on the lock screen for basic unlocking and access to most of the system, but then have the option for a long password or pattern for the couple of sensitive apps that need it.

It seems so obvious, any reason why it doesn't seem to exist?
[HTC One S] Castor-designs:
I have about 1 GB App storage and 6 GB data storage.

How can I repartion my storage to increase my app storage? I run TWRP and Cyanogenmod 12 (rooted).
[HTC One S] matu89:
Upgrade to hboot 2.16
[HTC One S] Castor-designs:
thank you very much matu89. Can I just flash hboot 2.16? Do I have to use adb or can I load the file onto my phone and flash it with TWRP?

In how far does hboot 2.16 help with repartioning my device?

edit: how to get hboot 2.16? i struggle getting the image :D

edit2: I tried to flash hboot 2.16 following this instructions but I got an error 99 (as others here and there also experienced). My phone is S-ON.

Furthermore i find this information:

So it would be mandatory for me, to downgrade to HBOOT 2.15 again in terms of being able to keep up to date.
[HTC One S] Flippy498:
If you looked at the instructions which are placed 11 threads below your thread (at the moment I'm typing this) you would have known that you need S-OFF since hboot 2.16 is leaked and not official. Besides it's not only an hboot you flash but a whole firmware package whose dzdata repartionises your phone.

That warning you found only means that you should deactivate the auto update function of CM and that you need to download and install the updates which are compiled by F-L-Y-E-R. So you won't get updates as frequent as if you were using official CM but the time range between two F-L-Y-E-R releases isn't huge, either.
[Wear OS Q&A, Help & Troubleshooting] Tonypax:
Hi,

I was wondering if someone can help.

I recently bought a Tag Heuer Connected watch which was my first ever android wear watch. After setting up and pairing with my phone, the watch had two updates required. The first was successful with no issues. During the second update the screen started flashing and the phone kept vibrating/buzzing with the screen being unresponsive 99% of the time. After doing some research i was told to fully charge, let the battery drain and try again. I have done this numerous times to much frustration and very limited success.

I was also told to do a factory reset. This required many restarts and other issues as previously mentioned the screen isn't working and only sometimes (1 try in every 100) can i get to the hardware reset page and actually click it. I have finally managed a factory reset, but the watch continues to buzz and the screen flashes every second or so with the screen again not functioning correctly. I am pretty sure it had something to do with the update as i had no issues before update number 2. I have spent many hours looking at similar issues and this forum was recommended.

Any help on this will be truly appreciated.

Tony
[Wear OS Q&A, Help & Troubleshooting] epaway:
Hi Tony,

I'd take it straight back to the shop you got it from. Wouldn't expect that from a smartwatch, but from a premium brand, the problem solving shouldn't be your issue.

Paul
[Wear OS Q&A, Help & Troubleshooting] d.cortez:
if you haven't already done so, open a support ticket with TagHeuer so there's a record of your troubles. i was having battery issues (lasted on 7 hours) and after 3 days of troubleshooting they told me to take it in for an exchange. i went to the TagHeuer store and they gave me a new one without any problem.
[Wear OS Q&A, Help & Troubleshooting] PalSTagwatch:
Hey how did you guys do a factory reset? i think i am having the same issues of the flashing main screen (black and white outline of the tag logo)

thanks
[G2 Q&A, Help & Troubleshooting] legal.xchech:
vs980

Euphoria ROM 5.1.1 (6/30)

I'm unable to send or receive MMS. Multiple messages say unable to download when receiving a message. Message will say sending indefinitely. Nothing changes after a reboot or using an alternative text app. What can I do about it? How do I check that I have the correct APN settings?

Any help would be appreciated.
[G2 Q&A, Help & Troubleshooting] jcooler:
did you ever figure this out? I am having the exact same issue.
[G2 Q&A, Help & Troubleshooting] legal.xchech:
No. But I did notice that when I reboot the device the sdcard shows up sometimes where it is suppose to (in root explorer). However, when I go to enable read/write (again in root explorer) it disappears immediately. Quite infuriating.
[Android Q&A, Help & Troubleshooting] damanarora27:
My xperia u is bricked i guess when ever i start it it vibrates for one time and flashes green led at bottom but does not opens installed a custom kernel to directly enter into recovry mode . now it is not detected by my pc does nt enters either flash mode or fastboot mode ... i cannot even hard reset it .. it does not works ..

please help any one
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Pix12:
Will cyanogenmod 13 come to the kindle fire hd 7 (Tate)?
[7" Kindle Fire HD Q&A, Help & Troubleshooting] monster1612:
Yep, [MENTION=3690349]BuQQzz[/MENTION] and I (mostly him, haha) are working on porting CM13 to this device, as well as the 8.9" (jem). I'm not exactly sure when a usable build will be uploaded, but it should be in the not-so-distant future. :)
[7" Kindle Fire HD Q&A, Help & Troubleshooting] Jaybone073:
I'm running 12.1 on mine and even though the rom is very lean the Kindle is always running slow. I have 2 questions concerning this. One, based on what you're seeing so far during development, is the rom running at a better speed?

Two, what steps can I take to make sure I am running the best I can for the best results?

The system was wiped completely. I did a super clean install, I've made a backup and moved it to my desktop (in case I need to push it), and I usually only do an update about once every two weeks. Mainly due to the fact that I have to jump through all the hoops of reinstalling Google Play Services, Google games, and the SuperSU beta.

If there are other things you think may help please give suggestions and advice. I can add external storage, however at the moment I do not have an SD card in the slot. To me since storage and RAM are two different things I am thinking it would make little difference to add external storage since I have very few apps downloaded on it.
[7" Kindle Fire HD Q&A, Help & Troubleshooting] monster1612:
1) The ROM currently doesn't even boot up at this point. It's an issue with SELinux that we're working to resolve.

2) I would suggest that you avoid having too many apps on the device - doing so tends to make app optimization take longer (which usually occurs after an OTA or a manual cache wipe). Also, try not to have too many xposed modules or other android mods on your device - if modules or frameworks conflict with each other or the base system, system stability and speed can be negatively impacted. As for the issues with having to reflash gapps, xposed, etc. after an OTA, I use CM Downloader (which is available on the Play Store) to automatically handle flashing other zips after the CM base ROM.

You're right - storage and RAM are two different things. Unless you're low on storage and/or need to share files between multiple devices, I wouldn't see a need for an SD card. Also, I'm fairly certain that the 2012 HD 7" (tate) doesn't have an SD card slot (are you using a 5th generation device?). This discussion is for the 2012 HD 7" models, not for other (or later) models; flashing a ROM meant for another device can and most likely will brick your kindle.