yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] pitrinn:
Well, well, relax and take it easy.

You still install recovery and ROMs with bootloader LOCKED, doing test points, but I asume this isn't your case.

I questioned it because if that case could had been the possible situation.

If you don't know, please don't laugh on others.

You could had been an advanced user with need of help, not a rat kid telling things he doesn't know.

Enjoy your new rom
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] kool_guy01:
I am not laughing at him and I apologise if it came that way.

I am not that advanced user ??? and I do find xda forum helpful. I thank you again for taking interest in my problems with the ROM.
[Xiaomi Redmi 5 ROMs, Kernels, Recoveries, & Other ] pitrinn:
Anyway, enjoy your ROM, and be careful.... imagine you install any ROM full of malware.
[Honor 8 Questions & Answers] MahmouDev:
Wifi kill and net cut not work in my honor 8 rooted device plz help me and sorry for my English
[Xiaomi Redmi Note 5 Pro Questions & Answers] aciupapa:
Hi. As some of you have noticed snapchat on our devices stretches recorded video horizontalli, and that's because our navbar is transparent and not solid like on for ex. S8. Does someone have an idea how to fix it or how to disable optimized app from using fullscreen and force it into 16:9? In settings i cant disable it because it is grayed out. I am rooted so terminal commands or modifying files is ok to me. Any ideas?
[Xiaomi Redmi Note 5 Pro Questions & Answers] Luckzzz:
have you figured it out??
[Xiaomi Mi 5s Questions & Answers] legend999C2A:
Which rom you guys recommend to replace official ROM?

I've been reading the threads and it seems every rom has a bug, but i'm actually fed of MIUI and want stock android.
[Xiaomi Mi 5s Questions & Answers] friwave:
LineageOS 15.1, no bug for me, smoother than MIUI. Just a weak SOT at some moments.
[Xiaomi Mi 5s Questions & Answers] legend999C2A:
Thanks for the reply!
[Xiaomi Mi 5s Questions & Answers] friwave:
Moreover, there is weekly update which is really cool for bug fix and security.
[Xiaomi Mi 5s Questions & Answers] predragiPredrag:
LOS16 is also good rom, it doesn't still have all customizations of regular LOS15, but battery life is better :)
[Xiaomi Mi 5s Questions & Answers] friwave:
I'm waiting Official builds to update to LOS16 but I'm glad to know the battery is better than LOS 15.1 (which is not at the top...).
[Xiaomi Mi 5s Questions & Answers] LordStanley:
I'd say that LOS 16 is stable enough for daily use
[Android Apps and Games] YOPS ltd:
PIPEIO - a simple time killer, in the spirit of Ketchapp.

PIPEIO - game in which the main thing is collecting and holding the combo, to achieve better results.

The more points you have, the higher you will be on the cross-board leaderboard.

Screenshots:

◉ Rules of survival:

1. Fall down and catch the combo

2. Earn as many points as possible

3. Every 5 floors is a level.

4. Do not fall on the tile of your color

5. More colors = more points.

6. Get as many points as possible!

◉ Top - every week.

Jump in an endless journey with the ball at various levels from the lungs to the supercomplex. Get to the Dark Essence. Try to maneuver in a spiral, try the edges, earn the greatest combo. Be brighter with the Tricolor game. Open for yourself a new one and collect more points.

Enter the TOP list and become the Master of the Pipeio!

Show whose balls are steeper! :D

Available in Google Play and AppStore
[Nexus 7 Q&A, Help & Troubleshooting] Ashram56:
I presume I'm stuck, but just in case…

I used TWRP to flash the latest LineageOS, and for some reason the bootloader got erased/corrupted (I'm not entirely sure how this can happen).

As a result, the tablet is now stuck in APX mode when booting up. Inconvenient to say the least…

I can still access TWRP, but any attempt to access Fastboot (ie adb reboot bootloader) results into the unit getting into NVIDIA recovery mode (ie APX)

And of course I don't have a backup of the boot keys.

Since I can access TWRP, is there anyway I can get access to the boot keys to reconstruct my bootloader ?

Regards
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, Ashram56...

Just to confirm, we are talking about the Nexus 7 (2012) tablet here? Because if you can still access TWRP, the bootloader is not 'dead'. If the bootloader were corrupted or erased, the device would not boot at all... ever! Not even in TWRP!

If it is a Nexus 7, you should be able to manually boot the device into its bootloader by long pressing and holding the volume down button, and at the same time, press the power button.

With regard to doing it via a command prompt, I think you need...

fastboot reboot bootloader

...as ADB commands only work when Android is fully booted.

Hope this helps.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Ashram56:
Yes this is a Nexus 7 2012

However that's the point: I can boot TWRP (hence adb mode), however if I select "adb reboot bootloader", or if I select "Bootloader" using the Power+Volume Down menu, I don't get into fastboot, I only get into APX, which is recovery

I was under the impression that the bootloader was corrupted, I'm glad this is not the case. Now I just need to figure out how to recover from where I am at this point
[Nexus 7 Q&A, Help & Troubleshooting] Ashram56:
And to clarify even further:

- I tried to use TWRP to flash boot.img that I extracted from LineageOS, still boots into recovery

- Did the same with the recovery image, same behaviour

- I realized that I had performed (my bad) a complete "internal storage" wipe, after flashing originally, which might have caused the issue

Bootloader indeed seems to be intact, the info page on the recovery menu (ie before booting TWRP) states 4.23
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
I suspect some confusion of technical terms is going on here.

Can you as describe, as precisely as possible, exactly what your Nexus 7 is displaying, when you enter what you think is, or might be, APX mode.

A picture/photograph would be even better.

APX/nvFlash mode is NOT Recovery. These are very, very different things.

Recovery is either the devices Stock Recovery, or a Custom Recovery, such as TWRP or CWM.

Rgrds,

Ged.

---------- Post added at 07:07 PM ---------- Previous post was at 06:52 PM ----------

OK, just seen this post.

You dont use TWRP to flash .img files, you use fastboot, so for example, you'd use the following command lines...

fastboot flash boot [name-of-boot-file].img

...or...

fastboot flash recovery [name-of-recovery-file].img

...with the Nexus 7 booted into fastboot mode and USB connected to a laptop or a PC.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, again Ashram56...

Some further thoughts regarding your situation...

So that would be on the fastboot menu then, and not the recovery menu:). I'm not trying to be needlessly pedantic here, but when dealing with this kind of thing, and when asking for advice, it's important to use the correct terms, otherwise confusion can arise.

Anyhow, your reporting of this indicates that your Nexus 7's bootloader is alive and well, which means the device is almost certainly recoverable.

Furthermore, bootloader v4.23 is the latest and the very last bootloader version this device will ever receive.

Whatever you chose to do, I'd strongly recommend against reflashing the bootloader again, as this process is the 'Achilles Heel' of the Nexus 7, and it's a potential terminal weakness. A bad bootloader flash, perhaps via a dodgy USB connection, can corrupt the bootloader, and render the device permanently hardbricked. And the only realistic solution to that is a motherboard replacement.

And which brings me to this...

I'm aware that you mentioned in your original post, something you called 'boot keys'. I assume you refer to the Nexus 7 'flatline' procedure for generating bootloader 'blobs', described here...

https://xdaforums.com/showthread.php?t=2455927

Such 'blobs' can ONLY be used on the original Nexus 7 with which they were originally generated. They are NOT transferable from one N7 to another N7.

Running the 'flatline' procedure is a fairly high risk venture, and requires a good knowledge and a high level of familiarity with using fastboot commands, because it involves flashing a special build of the bootloader. I ran it myself, a few years ago, and it's a pretty nerve wracking experience, wondering if your Nexus 7 will ever boot again!

Mine did, and I now have my N7 bootloader 'blobs', stored on my laptop ~ but I have absolutely no idea at all, if they'd be of any use should I have need to dig myself out of an APX shaped hole!

Fortunately that hasn't happened yet, and my 'blobs' will now likely forever remain untested, as I rarely use my Nexus 7 these days.

------------------------------------

...And it can't happen!. A TWRP flash of a Custom ROM, such as LineageOS, goes nowhere near the bootloader partition. It doesn't touch it at all. Same with a TWRP Nandroid restore. Bootloader partition is left alone, unmodified and untouched.

------------------------------------

Anyhow, and in conclusion, it sounds like your bootloader is still working, and you should therefore be able to recover the device.

The easiest way of doing this, is to download a Google Factory Stock image for the Nexus 7 and flash it via fastboot, and which you can find here...

https://developers.google.com/android/images#nakasi

------------------------------------

Good luck with getting your Nexus 7 up and running again, and I hope this helps.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] Ashram56:
You are correct to ask to be very precise, as words have different meaning, and can lead to confusion, as is the case here

I used the word "recovery" by mistake (I'm actually in HW Embedded design, and APX mode is called "recovery" mode in a lot of Tegra related literature). So to be clear, I will only refer to APX mode.

APX mode is essentially a mode the chip enters when it cannot find a valid bootloader, or when the bootloader fails to load a valid kernel (see similar details here for those who really want to get their head spinning: http://developer.nvidia.com/embedded/dlc/jetson-fuse-burning-secure-boot-28-2-ga , need registration to access the document though). You can also access this mode by asserting some HW pins at boot up (which are not exposed on the Nexus 7 2012 anyway)

Screen is black in this case, since the kernel has not loaded

Symptoms I have:

- I can access the "Boot select" menu, through Power+Volume- menu

- I can access from the "Recovery", which launches TWRP

- If I use the "Reboot" option from TWRP, or the "Bootloader" option from the "Boot select" menu in 1/, I get a black screen, and the tablet appears to be in APX mode (seen through simple linux lsusb command)

It turns out that in "some" instances I was able to actually turn on the tablet and boot the OS, but I can't figure what sequences (ie I can't find a reproducible way of booting correctly, 9 times out of 10 I get into APX mode).

I'll try to figure out further what the heck is going on. My suspicion is that the bootloader is attempting to load the kernel, and the first copy is corrupted. In most Tegra implementations, this should be covered through redudancy of the kernel at multiple locations (same for bootloader actually), but I'm not knowledgeable enough about Android to determine if this is the case as well here.

Thanks for the help in any case
[Nexus 7 Q&A, Help & Troubleshooting] Ashram56:
And to add to that:

when in "Boot select" menu, units does appear in Fastboot mode, however "fastboot reboot bootloader" gets me into APX mode (black screen, tablet seen as APX device, fastboot and adb not functional), same as booting to Bootloader from TWRP or "select" menu.

I'm quite puzzled...
[Nexus 7 Q&A, Help & Troubleshooting] Ashram56:
Just a note: one time out of 10 I can boot into the OS

I'll settle for that for the moment :)
[Nexus 7 Q&A, Help & Troubleshooting] Ashram56:
Reviving this 4y old thread...

So, recently I unburied my Nexus 7, to use it as a secondary device for some home automation application.

Took me a while to find my bearings again, but here's a summary of where I stand:

- If I power on normally (ie power button) the tablet for the first time or do a reboot (either through the UI or the adb command), it enters "NVIDIA Tegra recovery mode", ie device driver appears as APX

- When is this mode, if I press the power button for 10s or so it powers off

- When fully off, if I simultaneously press Volume - + power button, I can enter the bootloader mode (ie Fastboot mode), with the small droid, the info text at the bottom left, and a big "Start" button on the upper right corner.

Info reported in the bottom left in that case:

Fastboot mode

Product name - grouper

Variant name - grouper

HW version - ER3

Bootloader version - 4.23

Basedband version - N/A

Serial Number - sequence of numbers

Signing - not defined yet

Lock state - Unlocked

- in this mode, the volume keys do not have any effect, I can't select anything, only "Start" is available. I can indeed "Start" the tablet using the power button

It starts Android (in my case LineageOS), but in safe mode only, so limited functionality

And I'm stuck, since I can't use the tablet.

I know it's a very old thread, but if anyone has any clue on how to resolve this, I'm interested

Regards

[EDIT] Some additionnal data

- First, looks like my volume buttons are actually broken. I don't get any response inside Android UI, that would explain why I can't select anything in when in fastboot besides "Start" option

- I reverted back to the stock image, but I'm still stuck in safe mode.

I can't install LineageOS back, since I can't navigate in fastboot menu and access twrp (unless I can do that using a fastboot command) ?
[Samsung Galaxy J3 (2016) Questions & Answers] barjos12:
Hi everyone,

I am trying to root my device but I have had no luck!

I flash the TWRP with Odin and get a pass, but when I boot my phone into recovery mode to install SuperSu I am faced with the normal Android recovery mode.

I am running 5.1.1 Lollipop and have made no changes to the device.

Can anyone help?
[Samsung Galaxy J3 (2016) Questions & Answers] barjos12:
Bump
[Samsung Galaxy J3 (2016) Questions & Answers] djeman:
Do not restart on the rom after the flash but on the recovery.
[Samsung Galaxy J3 (2016) Questions & Answers] barjos12:
Hi there,

Sorry im quite new to all of this.

Do you mean untick auto-reboot on odin?
[Samsung Galaxy J3 (2016) Questions & Answers] djeman:
At reboot, after the recovery flash, you need to press "volume up+home+power" to reboot on the recovery.

If you uncheck auto-reboot you can reboot with "volume down+home+power" and when the screen goes off press "volume up+home+power".
[Samsung Galaxy J3 (2016) Questions & Answers] barjos12:
So for my problem the solution is not to tick auto-reboot on odin right? I am highly confused
[Samsung Galaxy J3 (2016) Questions & Answers] djeman:
Disable auto reboot or you need to be faster to press buttons when the screen goes off ^^

If the stock rom boots it'll replace the recovery by the original, you need to accept a popup in the twrp recovery to lock this function.

I forgot to say, supersu is not the best software at the moment magisk is maybe a little better :

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Samsung Galaxy J3 (2016) Questions & Answers] edyID:
Untick auto reboot, after flashing twrp pass then remove your battery from phone.

Plug in your battery and press power+volume up+home together to go to twrp and flash supersu or magisk
[Xiaomi Mi Max 3 Questions & Answers] MKR94:
I purchased this phone when it first came out and struggled with the buggy "global" rom it came with. I flashed to the Chinese stable rom MIUI 10 and it's been working perfectly for almost two months.

A couple days ago, I woke up put the phone on the charger and it wasn't charging, but I could still turn it on. Then the touch screen stopped responding, I did a hard reset. Still nothing, now it wouldn't even go past the "MI logo" screen. I then tried to flash another rom, but that MiFlash software was coming up with an error. I can still boot into flash boot mode, but Idk what happened. Is my phone bricked? Can it be saved? I really like this phone, please help.
[Xiaomi Mi Max 3 Questions & Answers] dinhvtai:
1/ Is there really the China stable Miui 10? Do you mean the dev version?

2/ A screenshot or message about MiFlash error should be better to help you.
[Xiaomi Mi Max 3 Questions & Answers] MKR94:
Here's what it says when I try to flash.
[Xiaomi Mi Max 3 Questions & Answers] dinhvtai:
Have you unlock the bootloader yet?
[Xiaomi Mi Max 3 Questions & Answers] MKR94:
Yes, I have unlocked the bootloader.
[Xiaomi Mi Max 3 Questions & Answers] MKR94:
Now the phone won't even turn on and I have charged it etc... I'm not sure what happened.
[Xiaomi Mi Max 3 Questions & Answers] Klanac89:
Did you unlock the bootloader or it already was unlocked with fake ROM?
[Samsung Galaxy S8 Questions and Answers] Mistercatapulte:
Hi everybody,

I've searched on the forum and i don't found tips for my problem.

I hope i post in good section.. (sorry for my english...)

I have a SM-G950F, with the firmware G950fxxu3crgh and i don't find the combination file to break the google account.

I can root the phone if i can bypass this restriction, but i think that's can't be the solution?

Thanks in advance
[Samsung Galaxy S8 Questions and Answers] BomiAlabi:
Hey, where you able to find a solution for this?
[Samsung Galaxy S8 Questions and Answers] Mistercatapulte:
Not yet :(
[Samsung Galaxy S8 Questions and Answers] Mistercatapulte:
Try this, was ok for me!

https://vn-my.com/watchvideo/boom-s...count-bypass-frp-without-box-2YCrmh-LQSY.html
[Samsung Galaxy Watch] brownpm85:
So I'm thinking about picking up a galaxy watch today. I have been a long time wear os user. My current watch is the Ticwatch E.

Im a guy with smaller wrists, the ticwatch e 43mm case fits me pretty well so I was thinking about getting the 42mm galaxy watch, but the larger battery is in the 46mm is really appealing. For anyone who has seen them side by side in person, does the 46mm look that much larger?

How is Bixby on the watch for doing basic things like setting timers and sending texts? I have seen the reviews where it is bad at some more advanced tasks but I just use my Google assistant for basic things.

I also use Google play music, I know there is no stand alone app for the watch but is there at least a basic play/pause, next track option on the watch when playing something through play music?
[Samsung Galaxy Watch] danielvago:
I can answer the first point.

My wrists are 5.9 inches around, but when I tried the 46mm it looked absolutely fine to me, so that's what I have ordered.

The 42mm didn't seem that much smaller, but the screen was notable smaller.

Try it in a store, to know how you think it looks on your wrist.
[Samsung Galaxy Watch] ErickF:
There is play, pause and next and previous track options with name of song and album artwork on the music app. I use the widget to easily skip a track. Its not bad. The only downside compared to wear os is that you cant use google play music as a standalone app to play music without your phone.
[Samsung Galaxy Watch] tofylion:
I can say that the watch is not a huge difference from any 42mm watches, but it will look big if the 43mm watch was already a perfect or a large fit on you. I don't think bixby on the watch is anything you could use. I've tried it several times and it appears to do the bare minimum of tasks. Like how you'd ask S Voice back in the day. It can set reminders, send texts and make calls and alarms, but it can struggle sometimes and hang for some time. However, I don't think you'll need any assisstant as the rotating dial and the smooth experience can help you accomplish tasks fast enough.

As for the music, you have spotify to install as a standalone app or as a remote for your phone. The Music app on the watch is set to work as a remote with play / pause, volume up / down and skip tracks forward or backward. You can also send tracks to your watch and use the watch alone with the onboard storage with a bluetooth headset or from the watch speakers. I mainly use it as a remote for the large amount of music on my phone, but you could probably fit some music on the watch.

The verdict is: if you're looking for a smartwatch that looks cool and elegant and has good functionality, the Galaxy watch is for you. If you're the kond of person who wants the watch for apps and all that stuff, you will find some on this watch, but it's not as versatile as Wear OS. I personally like Tizen and the look of the watch plus the battery life.

___________________________________________________

Oh, and the watch has Uber (for me with a galaxy phone) if you want to catch a ride. I used to call ubers with google assisstant as my previous watch didn't have uber. It doesn't have Google maps (or pay extra for a third party app), but you can download Here maps (or Here WeGo as it's named) and it's really nice with offline maps on the watch.
[Sony Xperia XZ Premium Themes, Apps, and Mods] madshark2009:
anyone know which theme has the "xperia" text on the home button instead of a circle or whatever

I really appreciate it if any one can help
[Sony Xperia XZ Premium Themes, Apps, and Mods] beammer335d:
Theres one that has "SONY" as the home button

https://play.google.com/store/apps/details?id=com.sladluk.blackforxperia&hl=en_US
[Sony Xperia XZ Premium Themes, Apps, and Mods] madshark2009:
nav buttons move position in custom density...

any way to fix that?
[Sony Xperia XZ Premium Themes, Apps, and Mods] beammer335d:
Set smallest width to 423. Like pic
[Sony Xperia XZ Premium Themes, Apps, and Mods] zarlydoug:
I've got this one, called make.believe Xperia theme.
[Android Head-Units] celticchrys:
I haven't tried it yet, but I just noticed that a new firmware was released by Sony on Sept 27, 2018. Had anyone else tried this yet? Sony says it "Provides an enhancement to the touch areas of the Tuner and SiriusXM preset buttons to improve usability".

Here's Sony's download page:

https://www.sony.com/electronics/support/downloads/00015464