yashsingh1/xdaforums huggingface dataset:
[Nokia 7 Guides, News, & Discussion] Robin>Hood:
Hi there!

Two simple guides for you... since I had a lot of trouble finding all the information in one post.

1. How to get into recovery mode on our Nokia 7 (TA1041).

2. How to restore stock (official) software phones shipped with unofficial software so you can easily update to the newest software! :)

This is what to do, and it WORKS!

1. Shut the phone down.

2. Connect a power source. Wait for the device to start charging.

3. Press and hold Volume Up and Power Button together. Release the Power Button when the phone vibrates, but keep the Volume Up pressed.

4. If you do it correctly, then you will be on the "no command" screen of stock recovery.

5. Press and hold the Power Button and quickly press and release (so 1 short press) the Volume Up key . Then release the Power Button too.

6. You should be in the recovery. And you can now use the Volume Buttons to navigate and Power Button to select your choice.

Good luck!
[Nokia 7 Guides, News, & Discussion] Robin>Hood:
Oke, so I thought it might be useful to share some other info too..

If you bought a Nokia 7 from China and it has the unofficial software which can not be updated this is the way to get it back to 100% stock!

What is needed?

Minimal Fastboot & ADB

Unlock key (from the_laser or techmesto - search for it on Google)

Stock firmware & OST LA & Patch (Google Drive link - thanks to hikari_calyx & Heineken78)

0.1 You need a bootloader unlock key. Some users on here know how to make it, I do not. I bought mine for $5 here on a website called techmesto allthough I rather see it as a donation because the guy is really helpful and excited. He also has a Nokia 7 :)

0.2 Install OST LA, copy patched .exe to the installation folder.

0.3 Install Minimal Fastboot ADB

Then the real works starts:

1. Start up you Nokia 7 and in the Google Setup click "next" all the time. When it asks for a username just press "ok", do not write anything as a username.

2. Go to about phone and tap "build" 7 times to get acces to developer options.

3. In developer options allow "oem unlock"

4. Turn of the phone and boot into Download Mode (which is fastboot!): plug in usb charger and then press Volume Down and Power Button

5. Use the following fastboot commands:

fastboot devices
fastboot flash unlock [unlock_file.bin] #whatever the name of your unlockfile is
fastboot oem unlock-go

6. Select "Yes" by pressing Volume Up and Power Button

7. Phone will reboot. Now go back into Download Mode (fastboot).

8. Use the following fastboot commands:

fastboot flash unlock [unlock_file.bin] #whatever the name of your unlockfile is
fastboot flashing unlock_critical

9. Select "Yes" by pressing Volume Up and Power Button

Now your phone is fully unlocked.

10. Go into Download Mode (fastboot again).

11. Unpack the stock rom file and open OST LA (by opening the patched onlineupdatetool.exe). Click "edit phone information". Wait for the error and click "ok" then click "next" and select the stock rom file and click "next" again, the software will now flash the stock rom and reboot.

12. After reboot, turn off the phone and go into recovery mode.

13. Select "factory reset" with the Volume Buttons and click Power Button to do a factory reset, then reboot the phone.

14. Turn off the phone again and enter Download Mode (fastboot).

15. With Minimal ADB Fastboot use the following command:

fastboot oem lock

16. Select "Yes" by pressing Volume Up and Power Button

17. Your phone will now boot into Android. Now you have Android 7.1.1 stock rom with locked bootloader! Go to system settings and start updating your phone :)

Good luck! Hope this helps out. It helped me out for sure!

Q: I get stuck on the "Powered by Android" screen or the phone keeps rebooting into Download Mode?

A: Just plug in the phone, get into Download Mode and use OST LA to flash the firmware. Nothing needs to be flashed, it will get stuck. But after it gets stuck you can reboot your phone again! :)
[Nokia 7 Guides, News, & Discussion] dcribeiro:
Thank you so much for the guide! It worked for me :)

However, I could only flash the stock rom with the OST v6.0.4.

During flash OST v6.1.2 blocks when 'Checking device status' and nothing happens.

Just a warning to other users that might face the same thing.

Cheers!
[Nokia 7 Guides, News, & Discussion] PaideLis:
So if I do this I will get ota update to 8.1 and maybe (in future) 9.0 Pie? Another question, I will have my native language Brazilian portuguese or only chinese and english?

There's no way to "translate" it to portuguese? Thankyou.
[Nokia 7 Guides, News, & Discussion] darek8804:
I have problem with fastboot devices - it not see my Nokia 7 at all...
[Nokia 7 Guides, News, & Discussion] kaisoulpro:
1. Yes, you can update via OTA to Android 8.1.

2. Only Chinese and English.

3. You can add more languages by using "MoreLocal2" app on Play Store. Search tutorial on YouTube, many people make video about this app.
[Nokia 7 Guides, News, & Discussion] PaideLis:
Wow cool.

One last question (I swear): Can I make a backup of this current shop ROM to go back if something goes wrong or I don't like it?
[Nokia 7 Guides, News, & Discussion] kaisoulpro:
You can ask as much as you like =))))

I think you can't because we don't have this "custom ROM" file.

Chinese sellers mod a stock ROM to Android One version, but it is lag and unstable, it's not official ROM, either
[Nokia 7 Guides, News, & Discussion] Bambalam.x:
Just wanted to add that for me, in the OST v6.0.4 tool, the 'Check System AP Status' update option is selected by default along with 'Normal Download' and seemed to cause the update process to fail. Deselecting it having only 'Normal Download' selected solved it.
[Nokia 7 Guides, News, & Discussion] Rene0105:
I did unlock my nokia 7 and I get the 5 sec delay when its unlocked

Then I Flash the rom C1N-0430-0-00CN-B05.nb0 it does flash but when it tells me finished and does boot its still my old android with dutch language and error com.android.phone I can click on it but its directly back phone is useless now.

Can someone help me ?
[Nokia 7 Guides, News, & Discussion] Rene0105:
After factory reset my phone did boot the stock ROM. I select english and it works ok.

Done several OTA downloads and finished the 10-2018 update no more available.

I wanted to remove some of the stock apps but failed.

Can someone tell me how I can root my Nokia 7 (is there a guide supersu or magisk ?) and how to install TWRP I read something about saving a partition or maybe mistaken. A good guide with steps would be great.
[Nokia 7 Guides, News, & Discussion] stevenjj28:
HELP!!

My nokia 7 plus hard bricked, trying to use ost la, so far 40 mins and counting been in download mode, no errors so far.

just there in the reflash service bootloader, is this normal or is there a problem.

Before trying ost my phone wasnt responding,no buttons working or combo and no charging indication..basically no type of boot up
[Nokia 7 Guides, News, & Discussion] singhnsk:
OST 6.1.2 cannot be cracked so it will not work. You should use OST 6.0.4. You will need to have an unlocked bootloader to flash it yourself.
[Nokia 7 Guides, News, & Discussion] kylemarco03:
Bootloader unlock

Have you tried unlocking your bootloader for free? Does anyone in here knows how to unlock it? thank you.
[Nokia 7 Guides, News, & Discussion] kylemarco03:
software update

I was be able to unlock bootloader and flash the rom but why the software update is december 2017 patch?
[Nokia 7 Guides, News, & Discussion] singhnsk:
Are you not receiving any updates? Check in settings :)
[Nokia 7 Guides, News, & Discussion] kylemarco03:
Thanks. But why there is no pie update on my nokia 7? others has pie update. Please help

---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------

Thanks. But why there is no pie update on my nokia 7? others has pie update. Please help
[Android Apps and Games] mmhs:
delete
[Android General] cupid59:
so, the pint is that the app will lock (turn off) your phone when exceed the safe speed limit of 20 Km/h and i need your feedback, i just released

it's called roboAngel and it is available on the play store
[Android General] str8upx:
Great idea, I'm going to try it out for a bit.

https://play.google.com/store/apps/details?id=com.inc.autorobit.roboangelv2
[Android General] vrhacker:
I like it!
[Android General] cupid59:
thank you, if you want to help please consider spreading the word, i still have faith in this app!
[Moto G6 Questions & Answers] Uclydde:
I want to return to stock after trying the AOSP GSI. Does anyone have the Project Fi version of the G6 firmware?
[Magisk] Haphim:
I'm doing a clean install of this rom on my Samsung S4 using the Aroma installer (Note: problem not related to aroma - see edits below).

The installer has an option to use Privacy Guard (for phones with a locked bootloader), SuperSU, or Magisk.

If I install Magisk, the phone is stuck at the Samsung logo indefinitely. If I choose either of the other options, it boots fine.

I've tried a number of different ways around this:

1. Choosing the Magisk option in the Aroma installer.

2. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 afterwards.

3. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.0 with the updater-script modified (commenting out the two lines) afterwards.

4. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 afterwards.

5. Choosing Privacy Guard for the rom install and then manually installing Magisk 16.6 with the updater-script modified (commenting out the two lines) afterwards.

All of the above options - every way I can think of - results in bricking the device.

Is there a way to make this work?

Edit:

1. I'm using TWRP 3.1.1.0, if it matters. And yes, my S4 has an unlocked bootloader (MDL).

2. The phone will boot fine if I choose the Aroma SuperSU option, but I discovered that SuperSU is not installing correctly either. It just doesn't brick my phone.

3. I tried running the NON-aroma rom installer. Then I used UnSU to remove the non-functioning SuperSU, and ran the Magisk 16.0 installer (normal one). Bricked.

Rebooted into recovery, ran the Magisk Uninstaller - it failed, saying "Magisk is not installed".

So I tried installing Magisk again - which installed with no errors. And then I immediately ran the uninstaller, and again it failed, saying that Magisk was not installed. Maybe that's a clue as to what's going on. Because it's clearly not related to the aroma installer anymore.

4. I added the recovery log. This shows me doing a wipe, installing the rom linked to above, flashing Magisk, then flashing the Magisk uninstaller so you can see it say that Magisk was never installed in the first place.
[Magisk] Haphim:
I've been having zero luck getting this to work. Does anyone have any ideas?
[Magisk] yung40oz84:
Maybe you should read this, https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post77014053, sounds like the issue you're having and apparently Armoa breaks Magisk install. Also go to general support thread and post logs, etc. You will get more help there.
[Magisk] Haphim:
Thank you. However, as I stated above, although I started with the aroma installer, I eventually tried the non-aroma installer and had the exact same problem.

In addition, I also tried the normal versions as well as ones that had been patched as per the instructions on the link you posted.

So whatever is causing this does not appear to be aroma related.
[Magisk] Didgeridoohan:
It would be interesting to see the recovery log from that...

It kind of sounds like there's some issue with your recovery. Have you tried letting the Manager patch your ROM's boot image and then flash that to your device manually?
[Magisk] Haphim:
I tried letting the Manager patch the boot image. I got the boot image by extracting it from the LineageOS rom. However, it would appear that the rom installer Loki's it on the fly, so the extracted rom by itself didn't pass the kernel signature check. This wouldn't be a problem if Magisk Lokied it during the patching process, but apparently it doesn't.

If there's an easy way to get the already lokied boot image off of my phone, I would appreciate being pointed in the right direction and I'll try it again. When installing Magisk, it allegedly backs up the boot image - if so, is there a way for me to recover it?

In any case, I went through the full routine all over again so that I could get the recovery log. I added it to the top post. It shows me doing a wipe, installing the LineageOS rom linked to in the top post, flashing Magisk, then flashing the Magisk Uninstaller immediately afterwards so that you can see it say that Magisk was never installed in the first place.
[Magisk] Haphim:
I just tried using TWRP 3.1.0.0 instead of 3.1.1.0 - no change.

Is there an easy way to extract the current boot.img (not the one from the rom installer, since that hasn't been Loki patched)? If so, I can try the patching through the app again.

Otherwise, if there are any other ideas, I would love to hear them.

Otherwise, I may have no choice but to buy a new phone if this one can no longer be rooted.
[OnePlus 6 Questions & Answers] leicablue:
I have noticed too many rooting and unlocking guides for this device scattered round the forum and not sure which is relevant as of 8th July, can someone guide me to the latest clear root guide for people with latest OOS. A thank you click awaits. :D
[OnePlus 6 Questions & Answers] rickysidhu_:
I'm finally going to unbox my OnePlus 6 today and I will be using the following guide:

https://xdaforums.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643/
[OnePlus 6 Questions & Answers] leicablue:
Thank you Sir.
[OnePlus 6 Questions & Answers] Vivasanti:
i ALWAYS follow Funk Wizards guides, ever since my OP3T - everything is up to date!

https://xdaforums.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643/
[Moto G4 Plus Questions & Answers] Åttavantar:
Im running Resurrection Remix Oreo, and get the warning message "SElinux is not enforcing, your security has been weakened" What exactly does this mean, should I be worried and what can I do about it?
[Moto G4 Plus Questions & Answers] DizzyBinary:
Selinux just determines what processes can access certain resources on the phone. There's nothing you can do about it as the rom must be compiled with selinux enforcing. Also, there isn't much to worry about.
[Moto G4 Plus Questions & Answers] Nithish natla:
Im also facing the same issue, how can i fix it, is there any problem with it?
[Moto G4 Plus Questions & Answers] Dhanush-raj:
There is no problems with it. But if you want enforcing then try other ROMs. I think when all the bugs are fixed , selinux will be made enforcing.
[Huawei MediaPad M5  Questions & Answers] usernamenotavailabe:
Hello. Inspired by some blog posts I decided I'm going to try work from an Android tablet and make the city my office. I'm a web developer, the code editing I can handle with terminal emulator and vim. The problem is with the developer tools - there are simply none on Chrome for Android. Yes, I know I could try something like Surface Pro, but for some reason an Android tablet seems more appealing to me, and it's cheaper.

I saw some cases where people got working a Linux distro running on top of Android with chroot, and the graphical interface was made possible with VNC connection. It appeared a little laggy, but the video was from 2012. I imagine one of the most beefed up Android tablets of today should handle it better.

So if I bought one and rooted it successfully, would I be able to run Linux on top of it? Anyone has done it on this tablet? I didn't find anything on the, probably because it's a new one.

P.s. sorry for the strange username, I created this account some long time ago apparently.
[Huawei MediaPad M5  Questions & Answers] thref23:
I imagine it might be possible, but I presume that remote desktop would be a better, easier solution.

Also, there are more browsers than Chrome available on the Android platform. Firefox is really resource intensive on Android, but it is impressively desktop-like in its capabilities. And it runs OK on my 8.4" M5 (though I use Dolphin Express as my primary browser).

You are a web developer and would even consider Surface Pro? Man, Microsoft decided to self implode some time ago.
[Huawei MediaPad M5  Questions & Answers] usernamenotavailabe:
Do you mean setting up Linux on a VPS? I think that a connection to a remote server miles away would result in a very bad performance, but I haven't really tried it, so it's just a guess.

As far as I know, Firefox for Android doesn't have dev tools either.

What's wrong with Surface Pro? I would seriously consider using it, but the price tag is really high compared to an Android device. The thing is also that Android tablet feels kinda more mobile, and I don't like Windows too much.
[Huawei MediaPad M5  Questions & Answers] thref23:
Basically, you would have a PC set up at home, and you would access your PC via a remote desktop app like Teamviewer or Splashtop. I presume you have a PC at home?

Honestly, I am not that knowledgeable regarding Surface Pro. I'm just reluctant to trust anything Microsoft nowadays, and I don't look forward to the day I have to upgrade from Windows 7 (although I'm sure I could configure Windows 10 like Windows 7). And the whole Surface concept is a little gimmicky, bluetooth keyboards, mice, and tablet stands can be purchased cheap and will probably give you a better laptop/PC like experience (with any tablet) than Surface Pro will. My gut is that you are better off going for an Android tablet, or if you need better specs, a Windows laptop.
[Huawei MediaPad M5  Questions & Answers] usernamenotavailabe:
Not really one that could run 24h/7. But you know what, I will try to spin up a server on DigitalOcean server with a graphical interface and try to connect to it from my laptop, and then Android phone and I will see about the performance.

I have also found a detailed article on running Linux on Android: https://www.androidauthority.com/install-ubuntu-on-your-android-smartphone-765408/ so I might also give it a try if I get the tablet
[Samsung Galaxy S9  Questions & Answers] Nye-uhls:
Sorry if this is naive, but the s9 (g960U) is the first phone I've had with a locked bootloader

I'm wondering if anyone with this model has tried to flash a magisk boot image with odin, and had any luck?

Seems like the most likely way to get some semblance of root without being able to flash TWRP.

Any one tried it/is it worth trying, and if i do try it, is there a special version of Odin that would be necessary?
[Samsung Galaxy S9  Questions & Answers] nelsyv:
You can't. My understanding of "locked bootloader" is that the device simply won't allow you to flash anything that isn't signed by Samsung.
[Samsung Galaxy S9  Questions & Answers] Nye-uhls:
That's my understanding too, that's why i haven't taken the time to just try it.

I've read things about a modified version of odin that lets you flash unsigned images, but i don't know if that's still a thing and if it would apply here
[Samsung Galaxy S9  Questions & Answers] *Detection*:
You can't flash anything custom with a locked bootloader. modified ODIN or not
[Samsung Galaxy S9  Questions & Answers] Tel864:
I am just freaking amazed at the folks that attempt to modify their devices without thorough research and at least searching for answers that have been posted over and over again.
[Samsung Galaxy S9  Questions & Answers] *Detection*:
The best one is when they've rooted / custom, but have no idea how to return to stock
[Samsung Galaxy S9  Questions & Answers] Nye-uhls:
Do you mean me? Because i haven't attempted to modify, this is my research. And i haven't seen this asked since magisk just added support for the s9, so I'm curious to know if that changed anything for locked bootloaders, since topjohnwu didn't say much about what kind of support was added.

And I'm just desperately clinging onto hope for returning to a rooted device.
[Samsung Galaxy S9  Questions & Answers] Tel864:
If it's snapdragon it's locked.
[Samsung Galaxy S9  Questions & Answers] partcyborg:
False. There are unlockable snapdragons. The s9 is the SM-G9600 and the s9+ is the SM-G9650.

Please help stop spreading this misconception. Thanks
[Samsung Galaxy S9  Questions & Answers] *Detection*:
As OP has a US flag set as their country, and even states "G960U" in their post, their snapdragon is locked, as most of them are locked, only two that are not and are not US models, as has been the case since at least the S7, I can't speak for previous
[Samsung Galaxy S9  Questions & Answers] partcyborg:
All true, but does not change the fact that "if it's a snapdragon it's locked" is not a true statement. I live in the us, and have a snapdragon, but my bootloader is unlocked.
[Samsung Galaxy S9  Questions & Answers] Tel864:
Hmm, hopefully you can read and if not please stop spreading that misconception.
[Samsung Galaxy S9  Questions & Answers] partcyborg:
I can, but can you? Trying to parse this sentence makes me not so sure...
[Samsung Galaxy S9  Questions & Answers] bassplayer1488@gmail.com:
Thats not true. You dudes shouldn't answer questions you don't know the answer to.
[Samsung Galaxy S9  Questions & Answers] LagMaster420:
There might be a way to root it through exploit
[Tilt, TyTN II, MDA Vario III Themes and Apps] mexxx:
Hello everybody,

is there any way to get the 4 sided cube (with applications side) instead of the traditional 3 sided included in dutty's 6.1 ROM??

Thank you very much for helping me and excuse me for my bad English.
[Tilt, TyTN II, MDA Vario III Themes and Apps] DaveShaw:
Have a look in the Cube Wiki. Links in my sig :D

Ta

Dave
[Google Pixel XL Questions & Answers] ominousnimbus:
Just picked up a refurb XL and, predictably, the navbar burn-in is fairly significant. I assume this is true for the vast majority of XLs out there in the wild that have been used for any length of time.

A couple questions:

1. I believe either the 8.0 or 8.1 update introduced some kind of alternating colors for the navbar to mitigate burn-in? If this is true, is it really the period that XLs were on 7.x when most of the burn-in happened -- meaning if you got a pristine screen now and started off with 8.x right away, you'd be in the clear, meaning normal usage won't ever result in significant navbar burn-in?

2. Is there any hope of RMAing to Google for burn-in if you bought it secondhand? Is there an easy way to check whether it was originally purchased from the Goog Store vs. elsewhere?
[Google Pixel XL Questions & Answers] lafester:
I think you are vastly over estimating how many pixels have burn in. Significant burn in simply is not caused by normal use... Maybe it was a display phone or something.
[Google Pixel XL Questions & Answers] ominousnimbus:
Even for the persistent on screen buttons? It only makes sense that those will burn in over a long period of normal use, at least without special software tricks.

Mine has moderate burn-in where the navbar is when I view fullscreen videos, but none visible anywhere else on the screen. I found a few older threads here where many people report the same issue, in some cases after only weeks of normal use.
[Google Pixel XL Questions & Answers] lafester:
Mine is a 2016 pixel with no burn in. I've seen a couple old posts about it but nothing suggesting every pixel has extreme burn in issues.
[Google Pixel XL Questions & Answers] Phalanx7621:
Mine doesn't have it either, I don't think it's normal unless you sit your phone down for hours with the same thing on the screen. These phones are built to withstand normal and even heavy use.
[Google Pixel XL Questions & Answers] liam_davenport:
Had mine just over a year and have burn in on the Nav bar only slightly but noticed on a clean img only used this devices for normal use don't leave the display on that much never for like 15+ mins at a time only devices with amoled I've had burn in