yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] AVillart:
I have read, watched many Videos on rooting my Sprint Note 4 5.1.1 on N910PVPS4COK1 , most are from few years past. All I want to do is to Root my Phone, I did flash TWRP 3.1.1-0. I do not want to Upgrade, downgrade or Flash another ROM.

I am confused since some mention that a new Kernel must be flashed and some Just mention to Flash CF Auto Root. Please Help.

Thank you all in Advance.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
Most just flash a zip in TWRP recovery to root.

SuperSU is in Google Play but honestly I've not rooted stock from there to day that works but used the recovery zip instead. This link may get you started; read the OP and follow the link to get stable release or read notes. The title will change with latest beta test version but here is a good place to start for SuperSU.

https://xdaforums.com/showpost.php?p=55256620&postcount=1

If you're looking to pass safety net, Google search Magisk. SuperSU doesn't support hiding root from Google's safety net but doing so may be dodgy and require frequent updates.

Older methods you find may mention older methods and kernel requirements. I'm not sure if CF Auto Root gets updated with latest SuperSU but it's intended to be a shortcut to root and for those not looking to not Odin TWRP to use a custom recovery.

You've gone the common route, starting with Odin to flash TWRP. You're next step would likely to root with one of the methods above or flash a custom kernel first. There are a few but stock kernel can also be used. I use Beastmode for permissive mode to flash sound modes that include ViPER4Android; permissive kernel is recommended for that one.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] AVillart:
Thank you for Quick response, Basically I need to flash a custom Kernel before I flash SuperSu Root. Which Stock Kernel can I use that will allow me to do that. Thank you again
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
The stock kernel you have would work with SuperSU or Magisk root. Stock kernel is enforcing selinux so it may not fully work as expected with ViPER4Android and maybe some other apps too. The need for permissive kernel impacted lollipop 5.1 and I've used it since then so I'm not having to know which apps are impacted.

If you're interested, Beastmode kernel is in the development forum for Sprint Note 4. Beastmode is very close to stock feel right out of the box without having to tune it; it may improve your battery stats too. The kernels with "r" are Samsung Marshmallow kernels do you'd use the numeric-only ones for Samsung lollipop.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] AVillart:
Which One would I flash as I only see BeastMode r56 RAGE for N910P on that page.

Thank you
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
I agree it was a bit of a search to find and not where I recalled it being.

https://www.androidfilehost.com/?fid=24052804347789588

Flash kernel then SuperSU zip. That should give you root on stock 5.1

I actually have a newer version but it's only had limited testing with a custom 5.1.1 ROM; original links were removed. Other updates were incorporated in custom ROMs. Since this is the only one readily available, try that one if you like. Recommend flashing over stock kernel only and make a full TWRP backup before flashing in case you prefer stock kernel.

If wishing to root stock with stock kernel, flash latest SuperSU.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] AVillart:
Thank you again.
[Android Q&A, Help & Troubleshooting] nemo001:
Hello.

I just downgraded my CPN3L from crdroid custom ROM to Coolpad MM V10. Each time I start the WiFi, there is a network named "NVRAM WARNING: Err = 0x02". I can't remove it.

Any idea how can I get rid of it?
[Android Q&A, Help & Troubleshooting] bhuvanbm7:
Fix is here

youtu.be/ZpJ2aCJEF_8

Follow this steps it will help you:cool:
[Nexus 5 Q&A, Help & Troubleshooting] Fox-UK:
First off, forgive the newbie questions here. I've been reading the forum all day to try to work out how to fix this and am stuck.

I'm running some sort of custom ROM I installed a couple of years ago and forgot about. It's been grinding to a halt recently and is now stuck in a boot loop. The device is rooted, the bootloader still unlocked, TWRP installed etc etc. I can connect via ADB. What I cannot do is see the user data, specifically photos, which is the only thing I want off this device before I do a full wipe and reinstall. Encryption has been turned on and the device is pattern locked when it works but the code that I think should unlock the device (74869, a small M using the lowest two rows of dots) does not decrypt the data when entered in through TWRP.

I am drawing a blank here and am wondering what to do next. If I flash a new ROM to try to get past the boot loop will I be able to decrypt the data using the new ROMs or will everything be lost? Am I doing something wrong when trying to decrypt through TWRP?

These are the current settings from the device.

C:\phonerecovery>fastboot getvar all
(bootloader) max-download-size: 0x40000000
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.28
(bootloader) version-bootloader: HHZ12k
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D821(E) 32GB
(bootloader) serialno: 072b709a0ae65fbf
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: yes
(bootloader) product: hammerhead
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1600000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1600000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 40000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 6ce9fa800
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 2bc00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:persist: 1000000
(bootloader) partition-type:persist: ext4
all:
finished. total time: 0.183s

All help appreciated.
[Nexus 5 Q&A, Help & Troubleshooting] Fox-UK:
OK a bit more digging and I am starting to think the EMMC is fried. So my request has changed. Is there any way to decrypt an encrypted user data area if you know what the password is supposed to be, because TWRP does not seem to want to let me through. Alternatively, how do I download the encrypted data through ADB?

Second alternative, is there a kernel I can boot into through fastboot which will allow me to enter the decrypt pattern?
[Nexus 5 Q&A, Help & Troubleshooting] speed&vodka:
Did you manage to recover afterall?

Hello Fox-UK,

i have the

exact

same trouble in a Xperia Z1. Custom ROM from a couple of years ago, internal storage encrypted, no booting (actually not a loop in my case, just the fashion animated wallpaper of the final boot instance never gives way to the OS) .

I have access to CWM but it obviously can't mount the encrypted internal storage.

I have managed to install .ZIPs from CWM, such as Aroma file manager, but since nothing's mounted, no access aside from the system files.

I wish I could somehow recover my encrypted partition (which I know the password for) through ADB but don't know if that's possible or the required commands.

Many thanks to any expert that can asist!
[Tilt, TyTN II, MDA Vario III General] NoFatePPC:
Where can i find the speeddial , i want to create a shortcut to it...

thnx
[Moto G4 Plus Questions & Answers] tjsudarsan:
Hi eveyone, I have moto g4 plus with good working conditions. I have facing the screen flickering issue (ghost touches) for few months when i was on a stock rom. i dont have any problems when i charge with turbocharger all works fine. it flickers while running on battery. i thought that if i used custom ROM then i wont get this issue bcoz many have told this as a stock rom bug. Then, i have flashed custom rom AEX 4.4 Nougat 7.1.2 b4 a week. after that still problem persists. i have also disassembled and assembled it again each and every parts after cleaning it. but no more fix. but, after i carefully notice it, when the phone is exposed to sunlight or to a open space then the screen flickers every 2 mins. but it doesn't flicker not even 1 time when it is inside a room, home or closed place. it flickers only when in open space or in sunlight.

Please tell me what will be the problem. i have tried service centers he asks me to replace the screen frame, but i dont think so that the problem is with screen bcoz it doesnt flicker not even one time also.

please let me know if you have any fix or where or what will be the root cause of the probelm..
[Amazfit] Neuer_User:
Dear all

Huami has started locking their bootloaders (see the other thread) and, so far, has not offered any official way of unlocking the bootloaders to allow custom ROM flashing.

Due to the great work of our distinguished XDA developer Olivier (@kasakdor) :good: we have reverse engineered the unlock mechanism of the bootloader and can now offer to send you unlock codes for opening your bootloader again and flashing other software.

Please read and understand the following terms and conditions:

You unlock your bootloader on your own risk. Nobody else takes any responsibility on your actions and any possible consequences.

We are therefore NOT responsible for any bricked devices, invalid warranty claims, heart attacks or world wars.

Huami / Xiaomi will consider your warranty void. Do not contact Huami / Xiaomi or your dealer if anything goes wrong after you have unlocked your watch. Only YOU are responsible for the outcome of any modification you do.

This service is for personal usage only. Any identified commercial activities will be blocked.

A maximum of three unlock codes can be requested by each individual.

This service is provided free of charge. You accept that you cannot claim any charges towards us, if you are unhappy with the service or if the service does not work for you.

If ever Huami offers an official unlock service, we will stop our service. The goal is not to be in competition with Huami here, but only to provide something as long as they are not able to.

INSTRUCTIONS

You need to have fastboot installed and working correctly on your PC. You need to enter fastboot mode and get some information from your watch. Then go to the website https://unlockamazfit.com and enter your information. We will check your data and send you the unlock code. This can take 1-2 days typically.

We need to do the manual checking as we do NOT want to support any abuse (e.g. pirate companies reflashing watches).

If you have questions or feedback, please feel free to post here. Please also report briefly back, if the unlocking was successful.

Enjoy custom ROMs! :cowboy:
[Amazfit] Talleco16:
Very good!

I'll try tonight!
[Amazfit] Gruchi:
C:\adb>fastboot getvar all

< waiting for device >

Nothing more, any idead how to solve problem ?
[Amazfit] 1immortal:
your watch needs to be in fastboot.

please read the description again.
[Amazfit] Gruchi:
it is in fastboot mode

C:\Users\Gruchi\Desktop>cd adb

C:\Users\Gruchi\Desktop\adb>adb shell reboot bootloader

* daemon not running. starting it now at tcp:5037 *

* daemon started successfully *

C:\Users\Gruchi\Desktop\adb>fastboot getvar all

< waiting for any device >
[Amazfit] 1immortal:
please post a screenshot of your device manager.
[Amazfit] romail:
Try to use different cable, sometimes it should be problem.

Or other ADB drivers version...
[Amazfit] MarcolinoV112:
I got the code but I unlocked the smartwatch ... ... I tried several times but after entering the string by unlocking it tells me failed
[Amazfit] bootsie99:
Worked perfect!
[Amazfit] Neuer_User:
Send me a PM with a screenshot of fastboot and the command that failed.
[Amazfit] superino:
Also for me error:

FAILED (remote: ED)

finished. total time: 0.078s
[Amazfit] mantidae:
Worked just like the tutorial says. Many thanks !!!!

OS ver: 1.3.3a

US version

fastboot getvar unlocked

unlocked: yes

finished. total time: 0.033s
[Amazfit] jardaz:
im geting always invalid serial number... and is the same on watch.. :(
[Amazfit] Neuer_User:
Hmm, I see that you and MarcolinoV112 both have OS 1.2.29i. Maybe Huami changed the mechanism already in that OS version.
[Amazfit] jardaz:
My bad i forget the / :) waiting for the email :)
[Amazfit] My Public:
Bootloader unlocked successfully! Many thanks!

(1.3.3a US)
[Amazfit] jardaz:
Work :) many thanks :) 1.3.3a :)
[Amazfit] SwidonMola:
FAILED (remote: ED)

finished. total time: 0.068s

With 1.3.3a :'(
[Amazfit] renaldofreire:
Waiting for the unlock code in my email.
[Amazfit] Vinnie1:
Thank you, worked great!!

My watch was suffering from battery drain, 100% ~ 8 hours, now 40% ~ 9 hours so far, I might get a whole day out of a single charge :).

I bought my watch from Aliexpress, and the seller is refusing to communicate, so I'm waiting to buy a replacement English version of the WeLoop Hey 3S when it is finally released, hopefully soon.

The problem now is that the HR sensor and the compass do not work now, and they did before the flash from 1.3.3A, its not a big deal, but did anyone else have this problem and managed to sort it?
[Amazfit] McFlyH:
It possible to unlock new version 1.3.4b ?
[Amazfit] lesscro:
basically, this support locked bootloader...
[Amazfit] AxA_200000:
hi what i need to unlock me watch?

and if the video for how unlock the watch plz told me i need it
[Amazfit] STEVE_MARS:
Please, I need help with my problem. Fastboot say: arg is 3.

And unlock don't work.

Please, help ?
[Amazfit] STEVE_MARS:
SOLVED ¡¡¡ :)
[Amazfit] 1immortal:
what was the solution ?
[Amazfit] drakxstar:
to those whom created the manual and unlock the bootloader...

You guys are rock.

can not say anything except thanks thanks thanks :good::good::good:

at last i can unlock my chinese pace and directly change the fw to english...

thanks guys...you are awesome:good::good:
[Amazfit] gabyonyx:
Is the unlock code dependent to ROM version? For example, if I get a code for 1.2.35 version and I use it to unlock the bootloader when I have 1.2.36, the code will work?
[Amazfit] Neuer_User:
You can't say for sure. Huami may change everything they want with every update. That's why we ask for the ROM version and so on to see, if something changed on the unlock mechanism. So far, they haven't changed it, so there is a good chance that it will still work with the next bootloader update, but there is no guarantee.

Btw, there is also no guarantee that Huami may not go and change the bootloader that it cannot be unlocked at all. Everything may happen. That's why with PACEfied I try to stay as long as possible on one bootloader and only update that if necessary for operation of the watch.
[Amazfit] cobra1000:
The unlock did not work.

Also for me error:

FAILED (remote: ED)

finished. total time: 0.078s

Im on 1.2.35
[Amazfit] Morphine1:
Thanks for this outstanding work.

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[Amazfit] cobra1000:
someone else?
[Amazfit] frnchu:
Hi, I tried to unlock the bootloader but I've been waiting for 4 days and I don't have any emails. When I tried to make the request again, the page sends me the following message:

What can I do about it? Thank you!

EDIT: Just this morning I received the code. Everything working!!
[Amazfit] timberwo1f:
It works with US watch on 1.3.3a!
[Amazfit] struppex:
It works with the US version and on 1.3.3.a

Thx guys

Awesome work:good:
[Amazfit] armenterosjm:
Good and good friends to all my pass me the same I'm waiting for the code I have the same problem
[Amazfit] radwar:
Can confirm 1.3.3a US works perfectly, how you guys manage to dish out the unlock hash in less than 24h is beyond me but let me say it's the only reason why i bought this watch in the first place.

Thumbs up for your hard work!
[Amazfit] ais0:
I have requested the code the 7 day and on the 15th I have not yet been sent, I have checked the spam and neither is this, if I ask for it again, it puts me in. There is an issue with your request: duplicate request for serial

Our team will look into this.

What do I do wrong? What solution do I have?
[Amazfit] 1immortal:
please provide full information filled in PM
[Amazfit] ais0:
What information do you need?
[Amazfit] 1immortal:
everything you filled in the form for the unlock
[Amazfit] ais0:
I have already received the unlock code, now only try it, thank you very much
[Amazfit] poycain:
Code

Please send me the code. Last time I went but did not get it.
[Amazfit] DarknessDragon:
Received the code and unlocked the watch. Love u guys, thanks!
[Amazfit] jaroc4:
Hi,

I received my code on 14.09.2017. Yesterdat I updated my PACEfied to version 27 and today wanted to unlock the bootloader but I can't.

When I eneter fastboot and try to execute the command "fastboot getvar unlocked" then nothing happens. It stays like this forever.

I also tried to enter my unlock code but same result. It stays without reaction forever.

I run adb as administrator and when I run command "fastboot devices" I can see the watch as "0123456789 fastboot".

What can I do?
[Amazfit] lynxys77:
reception code de déblocage

Hello everyone

I made an unlock request for a friend but it never arrived.

so i can not install pacefied

who can help me?

thank you in advance
[Amazfit] 1immortal:
try to run fastboot getvar all - what is the outcome of that ?
[Amazfit] lynxys77:
after, you write "fastboot oem code" to unlock your bootloader

try this
[Amazfit] jaroc4:
Thanks. I disconnected the watch and cleaned the bottom side. after reconnecting I tried "getvar all" and see that bootloader is off.
[Amazfit] Jasku1981:
No fastboot mode :(

Hello. I have a problem after the first step. The watch will reset, but not in fastboot mode. The watch is visible in the device manager. What could be the reason?
[Amazfit] HaiderRaza:
Where to find OS version? Is it software version? Like 1.3.3a?
[Amazfit] 1immortal:
Yes, exactly that
[Amazfit] cobra1000:
I would like to know if I can change my Pacified rom for the original rom 1.3.3 and return to the Pacified later if I do not like it.

But you have to keep in mind that I could not unlock the bootloader, since the code I requested for the unlocking did not work for me.

If I install 1.3.3 will it block me forever?
[Amazfit] jose-art:
received my code today, and it worked flawlessly!

version 1.3.3a (US)

thanks Neuer_User!
[Amazfit] Sol_Rac:
Failed to unlock: FAILED (remote ED)

First of all thank the community (sorry for my English, but it is from google translator :confuso: )

I followed all the steps indicated to unlock the watch.

But by entering the code provided by email I get this error:

FAILED (remote: ED)

finished. total time: 0.016s

You try to unlock on a Windows 10 Pro 64-bit computer

Model: A1612

Rom: 1.3.0n

serial bootloader: 0123456789abcdef

The clock enters the PC correctly in FastBoot mode.

I ask for help, please. I have seen several users report this problem but I have not seen any answers about it.

Any kind of help would be welcome.

Thank you so much.
[Amazfit] 1immortal:
you're on 1.3.0 ... its not locked yet, you have nothing to unlock.
[Amazfit] Sol_Rac:
Thank you!!

I really assumed it was blocked and it was not.

Operation OK in the change of language to Spanish.

Very thankful ;)
[Amazfit] Bond@007:
Hello, in fast boot i've : 1. version bootloader and 2. serial number of my watch but no access to 3. watch os version because my watch is blocked on QR code screen ... i've made the last official update of my CN Pace but after that and with my new phone nothing work and QR code not recognized by the amazfit app ... :(
[Amazfit] Bond@007:
Up nobody can help me and reply to my post from yesterday ?

When i've changed my phone, my pace CN version with english menu don't work ... i've made an update in last firmware and i made a full format from my watch.

Now my Amazfit App can't recognise the QR Code, i think i've made a mistake to update in last firmware and locked my watch to hack.

What can i do ? Downgrade in old firmware is possible and how can i do this ?

For you, what's the os of my watch ?
[Amazfit] cobra1000:
with what app are you pairing?
[Amazfit] relentizador:
Hello good, I have a problem to defrag the bootloader argc is 3 and I can not unlock it, the clock data is U-Boot 2013.07-00104-g46d8377

16121724036212 with version 1.3.3a and the unlock code provided:

* 05d9b0218dbe3627638755b3764495d9 not working, please i need help, thanks in advance
[Amazfit] 1immortal:
What's your OS version?
[Amazfit] relentizador:
is windows 7 64bit

reloj 1.3.3a (internacional)
[Amazfit] 1immortal:
Have you booted the watch into fastboot?
[Amazfit] relentizador:
yes
[Amazfit] 1immortal:
Please paste the outcome of:

Fastboot getvar all
[Amazfit] relentizador:
C:\>fastboot getvar all

(bootloader) version-bootloader: U-Boot 2013.07-00104-g46d8377

(bootloader) version-baseband: N/A

(bootloader) version-hardware: V1.1 20130322

(bootloader) version-cdma: N/A

(bootloader) variant: watch

(bootloader) serialno: 16121724036212

(bootloader) product: watch

(bootloader) secure: yes

(bootloader) unlocked: no

(bootloader) uart-on: NO

(bootloader) partition-size:bootloader: 0x0000

(bootloader) partition-type:bootloader: emmc

(bootloader) partition-size:recovery: 0x1000

(bootloader) partition-type:recovery: emmc

(bootloader) partition-size:boot: 0x2000

(bootloader) partition-type:boot: emmc

(bootloader) partition-size:system: 0x3000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:cache: 0x4000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:userdata: 0x5000

(bootloader) partition-type:userdata: ext4

(bootloader) max-download-size: 0x4000000

all:

finished. total time: 0.304s

C:\>

---------- Post added at 08:31 AM ---------- Previous post was at 08:27 AM ----------

C:\fastboot oem unlock 05d9b0218dbe3627638755b3764495d9

argc is 3

---------- Post added at 09:05 AM ---------- Previous post was at 08:31 AM ----------

good again, I have already managed to unlock I tried with a laptop with windows 10 and the first, thank you very much for helping me, I thank you very much, thank you and greetings
[Amazfit] poycain:
Help please me, I never get email information. But in the site said.There is an issue with your request: duplicate request for serial Our team will look into this. I have been waiting for so long.

My information

(bootloader) version-bootloader: U-Boot 2013.07-00101-g96591b8

(bootloader) version-baseband: N/A

(bootloader) version-hardware: V1.1 20130322

(bootloader) version-cdma: N/A

(bootloader) variant: watch

(bootloader) serialno: 161217240421--

(bootloader) product: watch

(bootloader) secure: yes

(bootloader) unlocked: no

(bootloader) uart-on: NO

(bootloader) partition-size:bootloader: 0x0000

(bootloader) partition-type:bootloader: emmc

(bootloader) partition-size:recovery: 0x1000

(bootloader) partition-type:recovery: emmc

(bootloader) partition-size:boot: 0x2000

(bootloader) partition-type:boot: emmc

(bootloader) partition-size:system: 0x3000

(bootloader) partition-type:system: ext4

(bootloader) partition-size:cache: 0x4000

(bootloader) partition-type:cache: ext4

(bootloader) partition-size:userdata: 0x5000

(bootloader) partition-type:userdata: ext4

(bootloader) max-download-size: 0x4000000

OS:1.2.35

please help me.
[Amazfit] Bond@007:
With Amazfit app ... Official app ...

Envoyé de mon STV100-4 en utilisant Tapatalk
[Amazfit] cobra1000:
CN app or International app?

If you have a CN firmaware you have to pair with CN app
[Amazfit] Bond@007:
I think it's not cn app but us... Where can i find cn app.apk ? Before i've a Xiaomi phone and access cn app but now with BlackBerry Priv ... Us app i think.

Envoyé de mon STV100-4 en utilisant Tapatalk
[Amazfit] cobra1000:
use this CN app for pair and after update for the playstore directly: http://es.apkhere.com/down/com.huami.watch.hmwatchmanager_1.1.4_free
[Amazfit] Neuer_User:
I'll have a look at it this evening.