yashsingh1/xdaforums huggingface dataset:
[Xiaomi Redmi 3s Themes, Apps, and Mods] fachry:
Yes! Me too. On RR ROM 6.0
[Xiaomi Redmi 3s Themes, Apps, and Mods] william.johhn7!:
Use BSGs version and set config to nexus 6p.
[Xiaomi Redmi 3s Themes, Apps, and Mods] iamsumanparui:
Can i do

Without root ?
[Xiaomi Redmi 3s Themes, Apps, and Mods] william.johhn7!:
Depends on type of ROM. Is hal3 enabled? Then no. If not enabled, you'll need to edit the build.prop which requires root access. There's also a way to enable hal3 through adb without root but I'm not sure how.
[Xiaomi Redmi 3s Themes, Apps, and Mods] Rahul Dilwale:
Okay here it is
[Xiaomi Redmi 3s Themes, Apps, and Mods] Buggyflip:
Why do i get a green picture when using front cam?
[Xiaomi Redmi 3s Themes, Apps, and Mods] Developer.:
Try different version
[Xiaomi Redmi 3s Themes, Apps, and Mods] glitchinside:
did not work for me even after installing magisk module and giving it all permissions.. it always force close!!

my device is redmi 3s (Land)
[Xiaomi Redmi 3s Themes, Apps, and Mods] starlord143:
Can you please share the link. I couldn't find it.

And a detailed process to install would be much appreciated. Thanks.
[Xiaomi Redmi 3s Themes, Apps, and Mods] william.johhn7!:
https://www.celsoazevedo.com/files/android/google-camera/f/MGC_5.1.018_FINAL_3.5_beta.apk

Enable camera 2 API

Reboot

Install apk

Set config to nexus 6p.

Force close the app. And you're good to go
[Xiaomi Redmi 3s Themes, Apps, and Mods] starlord143:
Just a quick question. Do I have to do all these enabling and configuring in build.prop?

Sorry, I'm new to this.

I'm on Resurrection remix rom 8.1 (May 11 build)
[Xiaomi Redmi 3s Themes, Apps, and Mods] starboyvivek:
Camera2 api in build.prop, Nexes 6P config. from within the app.

And by configuration I mean you need to select nexes 6P
[Xiaomi Redmi 3s Themes, Apps, and Mods] sanam279:
Which is latest version?
[Xiaomi Redmi 3s Themes, Apps, and Mods] Voodoojonny:
Anyone found a 5.2 version with working camcorder? It seems since 5.2 ther´s no chance to get camcorder working...
[Xiaomi Redmi 3s Themes, Apps, and Mods] Mahdiw.grb:
Land has HAL issues so gcam would have problem with video recording or at some cases even taking photos...
[Xiaomi Redmi 3s Themes, Apps, and Mods] sanam279:
Try new version from here

https://www.celsoazevedo.com/files/android/google-camera/

Video camera doesn't work obviously but for still photography
[Xiaomi Redmi 3s Themes, Apps, and Mods] sanjeev_kannan:
Is there any gcam mod runs without camera2api
[Xiaomi Redmi 3s Themes, Apps, and Mods] heed_haseeb:
It might be a noobie issue, please help me guys

I tried to search for persist.camera.HAL3.enabled=0 and it didn't show up.
[Xiaomi Redmi 3s Themes, Apps, and Mods] zathyaz:
Then add the same and Change value to 1
[Xiaomi Redmi 3s Themes, Apps, and Mods] Pirate0rex:
Can anyone suggest a decent g-camera mod for redmi 3s prime ? I mean there is lot of cams. Some working, some not (front cam issue or video not working,app crashing etc !). So please suggest gcam version where portrait,hdr+, video all working (yah i have root enabled). Thanks in advance.
[Xiaomi Redmi 3s Themes, Apps, and Mods] Saurabh266:
I tried this on resurrection remix pie rom on redmi 3s prime and it is working fine
[Magisk] Aria.A97:
I saw some people reporting bootloop with Magisk 15.0

I guess that's because Magisk 15 no longer disables dm-verity by default and Samsung Devices won't boot with custom recovery and dm-verity enabled.

So flashing dm-verity disabler by [MENTION=5672995]jcadduono[/MENTION] can fix your problems.

[Insert General Disclaimer Here]

Download Link

Original LazyFlasher Thread
[Magisk] [Lemmy]:
so do I flash this before or after magisk 15.0?
[Magisk] Kaos1337:
I'm with the s6 edge+ stock rom and TWRP.

I tried to flash Magisk 15.0 and then dm-verity disabler but the issue persisted: the bootloop.

Then I flashed Magisk 14.0, checked "Preserve AVB 2.0/dm-verity" inside Magisk Manager, updated to 15.0, but there was the bootloop again, so I flashed dm-verity disabler and now works with 15.0.
[Magisk] [Lemmy]:
I flashed stock samsung with odin, then twrp, then in twrp i flashed magisk 15.0 -> bootloop. rebooted into twrp and flashed the dm-verity disabler, still bootloop.

S6 edge here.
[Magisk] goRt:
Stock s8, installed magisk manager then flashed 15.0 without issue.

(Dm-verify was installed ages ago.)

Batstock kernel
[Magisk] [Lemmy]:
Next attempt.

Flash original samsung image with odin, reboot: phone works

Flash TWRP 3.1.1 with odin, reboot into recovery, install dm-verity 6.0, reboot: phone works.

Reboot into TWRP, install Magisk 15.0, reboot, PHONE WORKS.

Yay is me.

So dm-verity has to be installed before the update to Magisk 15.0.

---------- Post added at 11:12 AM ---------- Previous post was at 10:48 AM ----------

actually... 100% CPU load, device almost nonresponsive.
[Magisk] topjohnwu:
Can anyone here upload a recovery log and boot image when installing Magisk v15.0 to the beta thread? I am debugging the reason why dm-verity removal isn't working on your device. Thanks!
[Magisk] _alexndr:
Bootloop here v15 @ Samsung Galaxy S7 running pure stock ROM :(

According to your request in another thread - see attached (zipped) recovery.log, backed up stock boot.img and patched (zipped) boot_magisk.img

/data/adb/magisk_debug.log has not been created at all (clean install case over stock), so can't upload it...

EDIT: Accidentally answered in this thread, I have answered also in BETA's thread :)
[Magisk] afcaajax:
This worked for my S8 running the latest batman rom.

Remove magisk

flash prerooted kernel

Boot up

Reboot into recovery

Flash v15

Verstuurd vanaf mijn SM-G950F met Tapatalk
[Magisk] xTMODx:
That worked for me too (Glaxy Note 8 N9500)

installed TWRP

format the DATA partition

reboot into recovery

installed no-verity-opt-encrypt-6.0.zip https://build.nethunter.com/android-tools/no-verity-opt-encrypt/

installed magisk 15

reboot

if i dont install the no-verity-opt-encrypt-6.0.zip i get a bootloop
[Magisk] vittorio99:
if i flash magisk patched boot image i have to flag preserve dm_verity in magisk option?.

my phone is a s8
[Xiaomi Redmi Note 4 Questions & Answers] Crys2perk:
The Fastboot installation process goes all fine but device boots into Mi-Recovery by default. Currently Using Miui 9 Dev Rom (7.12.21 | Beta). This happened after I flashed the stock Dev rom after accidentally bricking my phone while unrooting through SuperSu's Full Unroot Option.

Bootloader is unlocked. Help asap plz.:(

Using The 4Gb 64Gb variant.
[Xiaomi Redmi Note 4 Questions & Answers] Jochman14:
Hi,

if you flash Global Developer rom using Fastboot method, you will always flash a stock recovery with it.

There is a great manual how to unlock your device on official CZ and SK webpage created by local admins.

Just go to miuios.cz (translate it to ENG using browser like chrome or others) create an account to be able see the links.

Then on the main page scroll down to Redmi note 4 and check

[NÁVODY] - základné /Bootloader/TWRP/MIUI/ROOT

there is everything you need to unlock device with software you need.

All credits to miuios team.
[Xiaomi Redmi Note 4 Questions & Answers] XiaomiRedUser:
I think is a problem about installation process (I had the same problem with another phone), but you can still access twrp with your computer. Just use this command: Fastboot boot "twrp.img".

Update "twpr.img" with your own twrp´s file name.

Wait untill phone´s reboot (more than 15s.)

Then use it as usual

Good luck
[Xiaomi Redmi Note 4 Questions & Answers] tinaeire:
I ran into the same problem after unlocking the bootlader:

TWRP would not install -> [Vol+] + [Power] started only the MIUI recovery.

But after some search, I found that you have to:

enter in a terminal "fastboot flash recovery twrp-x.x.x-x-mido.img"

enter after that "fastboot boot twrp-x.x.x-x-mido.img"

My Note 4 then started in TWRP.

EDIT:

Corrected step 2
[Xiaomi Redmi Note 4 Questions & Answers] MyNameIsRage:
After flashing twrp, directly from terminal boot to twrp and flash super su along with lazyflasher, after that reboot, when rebooted install official twrp app and super su app, and using the twrp app once again install twrp. That shld do.
[Xiaomi Redmi Note 4 Questions & Answers] Crys2perk:
Tried This Still Not Working.

I directly booted from fastboot to TWRP

I Magisk Rooted then , which works fine now.
[Xiaomi Redmi Note 4 Questions & Answers] dancress:
How did you get ADB commands to work in Fastboot? Having the same TWRP problem right now.
[Xiaomi Redmi Note 4 Questions & Answers] tinaeire:
From a terminal from your PC. With a Windows open "cmd.exe".
[Xiaomi Redmi Note 4 Questions & Answers] dancress:
ADB doesn't work in Fastboot... fastboot.exe does. And that can only boot into itself (the bootloader), not the recovery.

Anyway, I solved the problem. Mine is a 4X not a Note 4X. Damn you Xiaomi... they are exactly alike!
[Xiaomi Redmi Note 4 Questions & Answers] tinaeire:
You are right, my mistake.

adb does not work and I mixed it up.

But I did test 'fastboot boot twrp-x.x.x-x-mido.img' in fastboot mode and it worked on my Note 4.
[Xiaomi Redmi Note 4 Questions & Answers] Lomanic:
As others have reported, I had the same issue too. I was able to boot to TWRP with the fastboot boot command above, but it looks like after you boot to the stock ROM (mine was MIUI V9.2.1.0.NCFMIEK as far as I remember), the TWRP recovery gets replaced by the stock one. After flashing LineageOS (official lineage-14.1-20180331-nightly-mido-signed.zip), I can now properly reboot to TWRP with Vol+ & Power.

Thanks for the tip [MENTION=6740964]tinaeire[/MENTION] :good:
[Xiaomi Redmi Note 4 Questions & Answers] sk8223:
Why aren't devs mentioning this in the instructions right after the recovery flash command? I'll never understand. I guess it's more MIUI's fault for being so weird about the bootloader.
[Xiaomi Redmi Note 4 Questions & Answers] hcet14:
TWRP boots stable

Press VOLUME-UP and POWER together, when you feel the vibration release the buttons.

-> boots into TWRP

If you hold the two buttons until you see the TWRP logo flash up and release them at that moment -> boots to MIUI.

Did that with phone mentioned below, TWRP 3.2.1, and MIUI Global 9.2 Stable.
[Xiaomi Redmi Note 4 Questions & Answers] habib_561:
I am also facing the same problem, please someone guide me thoroughly how to root my xiaomi redmi note 4 snapdragon global stable version. i have successfully unlocked my phone but i can't start it up in twrp recovery mode. please tell me all the steps and files necessary.
[Xiaomi Redmi Note 4 Questions & Answers] Sachin:
Once you flash TWRP via fastboot then use command fastboot boot xxx.img

So, you'll be able to boot to TWRP, next flash magisk for MIUI, install lazyflasher.zip and reboot and check if TWRP sticks.
[Xiaomi Redmi Note 4 Questions & Answers] despeh:
i have the same issue after flash the twrp and it reboot back to mi recovery instead. However i am using redmi K20.

Found out that the issue is the twrp.img file that you flash must be a correct one that your download for your device.

If it is not the correct file ( my case is using redmi k20 pro instead of redmi k20 twrp.img), i will always failed and stay at mi recovery.
[Android Head-Units] stabone00:
Have not done much with rooting android devices in years and recently bought an Atoto A6 for a work van. I started messing around with it at home. Was able to gain root with Kingoroot and the replacing it with SuperSU. I emailed them about unlocking the bootloader but I'm not sure whoever responded even knew what I was talking about. Although ADB was working with system booted, I was not able to connect to the unit in fastboot. If you boot into recovery, it automatically runs an update and reboots. And if you boot into Fastboot with acc powered, fastboot automatically restarts. So using adb to reboot into bootloader and then removing power from acc would get me to a fastboot screen(although screen is off, putting power back to acc would show screen at fastboot mode) but I was never able to connect. I was trying different things to boot into an actual recovery, the A6 has no physical buttons, just a small hole for the reset. At some point it completely stopped responding. None of the sensor buttons light up and nothing on the screen. The micro sd I had in no longer works either. I did have update.zip backed up. Anyone know if there would be a way to use that to boot from a new micro sd or any other ideas to try, any help is appreciated.

The a6 has a mediatek mt8127. Was coming up as Alps A6. The build was alps/full_A6_series/A6_series:6.0/MRA58K/1506516231:user/test-keys . I did have it apart and have pics of the board, don't know if they would be useful though.
[Android Head-Units] stabone00:
Upon further review, board mounted reset button was screwed up, all good now. Would be nice to figure out the bootloader on this, although I don't have it installed in a vehicle, this unit seems to run pretty well. Not a fan of the the launcher setup and appearance .
[Android Head-Units] Croak:
Glad you "unbricked" it, and glad somebody is willing to risk rooting it. That might go on my weekend project list, would appreciate more details on Kingroot and how you swapped it with SSU. I miss ad blockers, among other things.

I got the same unit from Amazon last week (2gb touch only version), but wish I had opted for the physical button model now.

My biggest complaint is the damned FM radio app, which by default comes on when it comes out of sleep, and there's no obvious way to disable it. The volume level on FM is like 2x streaming/MP3 volume so it blasts you when starting the car if you forget to turn volume way down when you get out. I'd love to know the actual app name so I could disable it entirely, since I never listen to broadcast radio anyway.

Oh, and the parallax on the thing is annoying, getting a finger lined up on small touch targets takes some practice.

Other than that issue, I'm not unhappy with the unit. 2-second boot is legit, and living in Florida and an open sunroof junkie, I'm especially pleased with the screen brightness.

Using CarWebGuru instead of the default Atoto launcher makes for a much better experience, and I like the fact that the Atoto controls on the bottom (home, back, multi-tasking, brightness, mute) all remain there no matter what launcher you choose.

Sound quality using my car's factory amp (via a Metra CANBUS harness) is surprisingly good too, I can't tell much difference between the A6 and the Pioneer FH-X730 it replaced at the volume levels I like, though there is some RF bleed from the SoC. And it's a near-perfect fit in a Schoshe double-din GM dash kit, there's not enough room for a toothpick around the edges of the screen and the dash kit inner bezel.
[Android Head-Units] stabone00:
For rooting use KingOroot. You need the one for windows, the app on the unit itself won't do it. Then just google replacing kingoroot with Supersu, there are lots of threads about it. You could try the simple version but I ended up manually replacing files to do it, it's not bad at all. I wouldn't be to worried about bricking it, I have been trying all different things to get to a bootloader and at worst it re-updated and was working fine. What i did with the reset button, Ive done to othere devices, those surface mount buttons are junk. After doing a ridiculous amount of research, I found that MTK units don't enable fastboot. The preloader is what you have to get into to do anything, using mtk drivers. I could catch it right when its booting, installs the mtk vcomm drivers, but jumps right out. Once you are in that you need their flash tool, SDflash and there is MTKtools. So once thats figured out, i'm hoping to be able to get a custom recovery on. Without fastboot, it seems a bit more tricky, without that reset button I could be missing something simple. Hopefully more people start screwing with these, I doubt the people at Atoto are going to be of much help. So far tho, it seems like a decent unit. Let us know if you find out anything.
[Android Head-Units] stabone00:
So far I was able to extract the boot and recovery img files. You can connect to the preloader using SP Flash by setting it up to read
[Android Head-Units] Croak:
Ima let you do the heavy lifting on this one Stabone. :)

For now, I'm just frustrated on the damn FM app opening at startup and it's nested in the Atoto firmware somewhere, not an isolated app.

One other quirk, on my car (with GM 11bit CANBUS), the illumination signal seems to be flipped from what Atoto is expecting...lights on means brighter screen, lights off means dim. I've tried it with both an Axxess and PAC CANBUS adaptor, so it's not the harness' fault. Just using the NONE setting for now and manually dimming the screen myself.
[Android Head-Units] tagara1:
I sure hope stabone00 keeps working on this. I have been following this thread closely. I have been wanting to root this but I have it installed in the car now. why cant this be easy like a nexus 7. I am very afraid of bricking it and I really like the head unit
[Android Head-Units] stabone00:
Not sure what happened to my last post, it should've been a bit longer then that, hah, oh well. Anyway I'm a little stuck here. After finding out as much as I did, I was going to try a few things. I'm running a dual boot laptop with opensuse as my main and a windows 10, for occasions as such, the tools used for this head unit are more abundant for windows(at least found easier). So recently I wiped my systems and now am having this Rsa Key Fingerprint issue when trying to connect with adb. I'm spending way to0 much time on this as it is, lol. But running into this bs is really pain. Now I've tried for hours to do something here but it's almost as someone's watching what i'm doing and countering my moves. Now I've factory reset this thing about four times and never lost root. After struggling with this rsa fingerprint issue, I did a factory reset and now SuperSu is gone, although I can't say for sure totally cause I still have not access to ADB. Any suggestions for the rsa issue, let me know, otherwise I'm not going to be wasting much more time with this. BTW, anyone getting anywhere with this, you need the modified version of MTK android tools to recognize this unit. I have boot and recovery img's and a scatter file if needed.
[Android Head-Units] stabone00:
Got passed issue with adbkeys. Now I accidentally flashed a recovery when it was not ready. I am now stuck in a boot loop. Made lots of backups, but for some reason, none contain the preloader.bin. Not sure why that happened, but that is needed to flash backups with SP tools. If anyone could send me that, it would be great. I can't pull it cause I can't get it to connect to mtk droid tools. Maybe there is another way, but I don't know it.
[Android Head-Units] smithkt:
I have the same unit. If you can tell me how to pull it, I'd be happy to help.
[Android Head-Units] stabone00:
Have you tried anything with it yet? There's quite a bit to it. The info is all searchable on here, you are looking for mediatek devices, sp flash tool, mtk droid tools. Let me know if you have adb and drivers installed. All the info needed for this unit is available , but there is a lot of info on mediatek devices, so it's a lot to look at. You need to have developers options enabled and oem unlocked and usb debugging on . If you can connect to your unit through adb, thats a start. Don't attempt anything with fastboot, it's not enabled on this unit. You'll then want to look for the modified version of mtk droid tools 2.5.3. If you are able to connect with that, I'll tell you what to do next. Not so sure my unit is recoverable, i've lost the startup atoto screen and can no longer connect with sp flasher. Hopefully there is something that can be done.
[Android Head-Units] smithkt:
No I haven't done anything with it yet. I wasn't planning on rooting the device. The only reason it's not in my car already is it's been 10-20 F and I don't have a garage. :) I have the thing sitting on my kitchen table so I can play with it.

I'll look through the info and see what I can do.
[Android Head-Units] stabone00:
I have it hooked up with two switches, one feeds constant and other switch, and other switch feeds acc. Rooting it isn't too bad, but if you look into how the sp flasher is used, you could make a stock rom before doing it. I'm hoping there are test points on the board that can be used to get this flashed again. I'm not sure how it got this far gone. I had it bootlooping at the ATOTO startup, tried to flash the original boot and recover, seems like it wiped the preloader.
[Android Head-Units] scoolro:
Have you had luck in unbricking your atoto?

I'm thinking about buying one also buy would like to root with kingroot and put a recovery into stereo if it's possible. Let me know your success is possible.

Thanks

Steven
[Android Head-Units] stabone00:
So far it seems to be a very solid unit. Rooting it isn't an issue. I had been trying different things with this unit and at one point I thought it was almost unbrickable. It still might be, just haven't found a solution for my issue (which was completely my fault), although I'm pretty confident there is one. There is a lot of info about mediatek devices on here, a bit different approach when flashing a custom recovery.

Overall I was liking the unit, hadn't seen any issues some of the others had. Hope to see more people getting involved.
[Android Head-Units] scoolro:
I hope you get the unit working soon.

I'm thinking about getting the same unit and I want to root it so I can get ADAWARE and XPOSED app installed. I'm also thinking about getting a Bluetooth media steering control for it also.

I've only seen the Atoto A6 on Amazon.ca for about $280. Hopefully there is another site that sells cheaper.

Again good luck and keep us informed with your progress if possible.

Steven
[Android Head-Units] stabone00:
Atoto offered a to replace the unit with the PB model, as this one is no longer available. After doing as much research as I did, I am certain that this can be fixed. There should either be a way for force the preloader or get into a meta mode/ flashing mode. I'm going to keep it and see. I'm ordering the PB as soon as it is available again on Amazon.
[Android Head-Units] Croak:
So driving home from work today, I noticed an update pending for the A6. Was in a good coverage area (using a MiFi hotspot, btw, not my phone), downloaded it at a long stop light, hit install, and after reboot, I got the dead Android ERROR! graphic. About **** myself, thought I might have bricked it. At the next red light, I did a reset (I keep a slim toothpick in the console now, for just such emergencies) and I'm back to the old November build.
[Android Head-Units] stabone00:
I ended up sending my 62721p back and am waiting for the pb model.

Did you have it rooted?
[Android Head-Units] Croak:
Nope, couldn't be assed, it's basically a Poweramp/Waze/Spotify machine for me now, figured I don't need root for that, and all the cool root-level stuff the Rockchip and Sofia units get isn't available for this thing anyway.

Did get the update to stick the second time around, but noticed no changes in functionality. MCU got updated as well.
[Android Head-Units] stabone00:
Curious, cause I really don't know, what are some of the things that can be done with the rockchip and intel units after rooting?