Hi folks!
I have still installed the stock recovery and so I connected my RN5 to my computer in order to boot TWRP via fastboot boot twrp.img. After that, I have normal storage access without entering any passwords/my pin...?
Well, I'm a bit confused about that. Can anyone explain me how that is possible - and what to do to prevent that?
I'm using RR 8.1, just fyi.
Regards
That's how it is ?
I had some other phones (Mi A1 & Vernee Apollo), where I needed to enter my PIN. Why do I don't need to enter it in this case?
And what are you doing about it? I think that's a bigger security issue than choosing 1234 as pin lol
tbXD said:
I had some other phones (Mi A1 & Vernee Apollo), where I needed to enter my PIN. Why do I don't need to enter it in this case?
And what are you doing about it? I think that's a bigger security issue than choosing 1234 as pin lol
Click to expand...
Click to collapse
Unlocking the bootloader itself biggest security issue...
tbXD said:
Hi folks!
I have still installed the stock recovery and so I connected my RN5 to my computer in order to boot TWRP via fastboot boot twrp.img. After that, I have normal storage access without entering any passwords/my pin...?
Well, I'm a bit confused about that. Can anyone explain me how that is possible - and what to do to prevent that?
I'm using RR 8.1, just fyi.
Regards
Click to expand...
Click to collapse
in MIUI
enable Encryption & set either PIN or Fingerprint to unlock, then Boot in to recovery, this time twrp Should Either ask pin to access internal storage , or it will show internal storage as 0 byte.
if not then I have nothing else to share
Thanks, but I'm using Resurrection Remix Oreo as mentioned (encryption is already enabled..)
Anyway I'm probably not the only one using a device with an unlocked bootloader So, what are your thoughts about that? How are you protecting yourself? I don't really believe that nobody has thought about that issue.
tbXD said:
Thanks, but I'm using Resurrection Remix Oreo as mentioned (encryption is already enabled..)
Anyway I'm probably not the only one using a device with an unlocked bootloader So, what are your thoughts about that? How are you protecting yourself? I don't really believe that nobody has thought about that issue.
Click to expand...
Click to collapse
everything on google cloud hehehe
Related
Hey guys,
I've been messing around with my brand new N7 yesterday and somehow screwed up badly.
Right now, all I have is a working TWRP recovery and a locked bootloader.
When I try to unlock the bootloader, the device just freezes so flashing stock images is not an option.
Can I do something via TWRP to get my N7 working again?
I already opened a RMA with amazon.
Second question: If I am out of options, is there a way to remove TWRP?
Really need your help right now,
thanks in advance,
DrTek
which method did u try to unlock the bootloader?
MoonBlade said:
which method did u try to unlock the bootloader?
Click to expand...
Click to collapse
I tried with "fastboot oem unlock"
The moment I choose yes and push the power button for confirmation - the device freezes.
drtek said:
I tried with "fastboot oem unlock"
The moment I choose yes and push the power button for confirmation - the device freezes.
Click to expand...
Click to collapse
is it freezing for more than 2 mins ? it should not freeze like that unless it is already unlocked ??
It might already be unlocked. Do you have an unlocked symbol when you turn it on? If you do, run the Dead Nexus batch file from here. I was unable to do anything from TWRP or CWM. Just a bunch of errors when it tried to do anything with the drive. Flashing, copying, formatting, etc. This saved my Nexus!
http://forum.xda-developers.com/showthread.php?t=2381582
Do you have access to the internal SD? From a computer or anywhere? Because if you do you can just flash a ROM from twrp
sent from my nex7
Originally posted this issue in CyanogenMod 13.0 Nightlies for the HTC One m8, and haven't received any replies, so I am trying here...
Have been using various versions for sometime CyanogenMod without issues. S-off Super CID.
Recently updated to cm-13.0-20160511-NIGHTLYand the latest TWRP. I noticed I could no longer boot to bootloader. When I tried, the phone would shut down. This happened whether using the reboot menu or TWRP .
I couldn't get anywhere, so I wiped everything and installed Nandroid backup of a stock sense ROM through TWRP. Now the sense ROM keeps asking for my password to decrypt storage. I enter the password I used with Cyan, which doesn't work. After 50? tries, it reboots into TWRP, resets the phone, and immediately reboots to back to sense with the same result. I seem to be stuck in a loop.
Still unable to get to HTC bootloader, and I can no longer boot to TWRP either. The phone is also no longer seen by my toolkit.
Any suggestions would be greatly appreciated. Thanks.
lannatwin said:
Originally posted this issue in CyanogenMod 13.0 Nightlies for the HTC One m8, and haven't received any replies, so I am trying here...
Have been using various versions for sometime CyanogenMod without issues. S-off Super CID.
Recently updated to cm-13.0-20160511-NIGHTLYand the latest TWRP. I noticed I could no longer boot to bootloader. When I tried, the phone would shut down. This happened whether using the reboot menu or TWRP .
I couldn't get anywhere, so I wiped everything and installed Nandroid backup of a stock sense ROM through TWRP. Now the sense ROM keeps asking for my password to decrypt storage. I enter the password I used with Cyan, which doesn't work. After 50? tries, it reboots into TWRP, resets the phone, and immediately reboots to back to sense with the same result. I seem to be stuck in a loop.
Still unable to get to HTC bootloader, and I can no longer boot to TWRP either. The phone is also no longer seen by my toolkit.
Any suggestions would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Did you encrypt using android's normal way of encrypting the storage or some other way?
Bllooi said:
Did you encrypt using android's normal way of encrypting the storage or some other way?
Click to expand...
Click to collapse
I used the encryption utility provided in CyanogenMod. If I could just get back into TWRP, I could at least restore what I had before.
lannatwin said:
I used the encryption utility provided in CyanogenMod. If I could just get back into TWRP, I could at least restore what I had before.
Click to expand...
Click to collapse
You might want to try to decrypt with the password 'default_password' as this is the default password for CM encryptions. The lock screen passphrase IS NOT the disk encryption password. It's a known problem with cyanogen. (I assume) You may have assumed that the lock screen password was what it was in CM but it's not. When you get in, make sure to change the disk encryption password (with a terminal sort of program while in root) using
because cryptfs changepw password default_password <new password here>
Really hopes this helps.
It's a CM problem, so just dw and calm down xD
Let me know how this pans out :good:
Bllooi said:
You might want to try to decrypt with the password 'default_password' as this is the default password for CM encryptions. The lock screen passphrase IS NOT the disk encryption password. It's a known problem with cyanogen. (I assume) You may have assumed that the lock screen password was what it was in CM but it's not. When you get in, make sure to change the disk encryption password (with a terminal sort of program while in root) using
because cryptfs changepw password default_password <new password here>
Really hopes this helps.
It's a CM problem, so just dw and calm down xD
Let me know how this pans out :good:
Click to expand...
Click to collapse
No luck.
lannatwin said:
No luck.
Click to expand...
Click to collapse
I think you should wait for the phone to run out of battery or try leaving it off for a bit and try getting into bootloader again. You can try a hard reset with power+volup+voldown then keep holding the down button after you feel the buzz. I don't see any other way you can do it. If you can get there, there's a good chance you can get into recovery and wipe data. It'll wipe everything but it should work.
It should work because while I was reading up on how the encryption works for both sense and cyanogen, they both encrypt the /data so if you wipe that you should be good to go
You should be able to side load a ROM on
Bllooi said:
I think you should wait for the phone to run out of battery or try leaving it off for a bit and try getting into bootloader again. You can try a hard reset with power+volup+voldown then keep holding the down button after you feel the buzz. I don't see any other way you can do it. If you can get there, there's a good chance you can get into recovery and wipe data. It'll wipe everything but it should work.
You should be able to side load a ROM on
Click to expand...
Click to collapse
With the power+volup+voldown I never get a buzz. Will try letting the battery run down. Appreciate your help.
lannatwin said:
With the power+volup+voldown I never get a buzz. Will try letting the battery run down. Appreciate your help.
Click to expand...
Click to collapse
How's your problem? Anything new?
Bllooi said:
How's your problem? Anything new?
Click to expand...
Click to collapse
Still the same. I haven't been able to get it to use up the battery yet. The screen keeps turning off after a about 30 seconds, so the battery is lasting forever! Think I have myself a pretty paperweight.
I have the same problem but I fixed my phone
if your phone not charged use original charger for the phone
-first, remove any sim card or memory card
- [ hold volume down + home button (if you don't have home button skip) + power button]
- press volume down this will rester your phone
- your phone now will work fine
- now Go to settings > lock and security > disable encryption
- no turn off your phone after disabling encryption
- now insert your sim card and memory card
- turn on your phone now everything is fine ..
Good Luck
Hi everyone..
I will go into the main point directly..
firstly my phone run out of the battery then the phone slept.. I plugged the charger to get the phone powered on again...
after that the phone started and asked me for the pattern..
then I entered the pattern I save but the phone says that the pattern is wrong and I swear that pattern I use every day :laugh:
now the phone is locked and I tried to tap the "Forgot Password" button but it says that all data on the phone will be erased and that will be impossible for me :crying:
Please advice me what should I do regarding that the phone still in the warranty period!
the phone is Note 5 AI global version..
thanks in advance
If you have twrp installed then its easy to delete lock pattern. If you are stock then not so sure.. Anyways patterns dont just change, im sure you must be confusing something.
Incogn said:
If you have twrp installed then its easy to delete lock pattern. If you are stock then not so sure.. Anyways patterns dont just change, im sure you must be confusing something.
Click to expand...
Click to collapse
thank you for your fast reply..
if I used the common method on youtube using twrp then i deleted the gatekey file the pattern will reset ?
this methode won't affect warranty ?
ahmadsaadeldeen said:
thank you for your fast reply..
if I used the common method on youtube using twrp then i deleted the gatekey file the pattern will reset ?
this methode won't affect warranty ?
Click to expand...
Click to collapse
It wont affect warranty. And yes it will delete patern.
I flashed my RM5 with the CN ROM shortly after receiving the phone due to the software limitations of the NA ROM shipped on the device. With the CN ROM I successfully used face unlock. Now after flashing to the newly released global (v3.11) I get an error when trying to register my fingerprint (attached).
Steps taken:
1. Re-flashed CN ROM and attempted to register fingerprint and got the same error
2. Re-installed the new global v3.11
3. Flashed global recovery, boot, splash, parameter, then wiped data & cache. Factory reset. Still get the same error
Interesting to note that upon setup the phone said the fingerprint sensor was on the back.
JerryYin said:
You should find the person who gives you the phone. The fingerprint calibration data will lost only when you try to unlock the bootloader
Click to expand...
Click to collapse
Looks like the community is solving the problems again: https://forum.xda-developers.com/nu.../guide-calibration-finger-print-loss-t4132961
terrapin4 said:
I flashed my RM5 with the CN ROM shortly after receiving the phone due to the software limitations of the NA ROM shipped on the device. With the CN ROM I successfully used face unlock. Now after flashing to the newly released global (v3.11) I get an error when trying to register my fingerprint (attached).
Steps taken:
1. Re-flashed CN ROM and attempted to register fingerprint and got the same error
2. Re-installed the new global v3.11
3. Flashed global recovery, boot, splash, parameter, then wiped data & cache. Factory reset. Still get the same error
Interesting to note that upon setup the phone said the fingerprint sensor was on the back.
Click to expand...
Click to collapse
You need to lock the bootloader to make it work, this will wipe your phone however. It says the fingerprint is on the back because the devs didn't bother fixing the typo in the setup.
rat7lol said:
You need to lock the bootloader to make it work, this will wipe your phone however. It says the fingerprint is on the back because the devs didn't bother fixing the typo in the setup.
Click to expand...
Click to collapse
Same thing after BL unlock/wipe. Same thing after BL relock/wipe
Are you sure you're using the correct command? There's "fastboot oem nubia_lock NUBIA_NX659J" and "fastboot flashing lock".
"fastboot flashing unlock" breaks the fingerprint
rat7lol said:
Are you sure you're using the correct command? There's "fastboot oem nubia_lock NUBIA_NX659J" and "fastboot flashing lock".
"fastboot flashing unlock" breaks the fingerprint
Click to expand...
Click to collapse
Yup I'm using "fast boot flashing (un)lock". I've unlocked and relocked now.
Sent from my NX659J using Tapatalk
terrapin4 said:
Yup I'm using "fast boot flashing (un)lock". I've unlocked and relocked now.
Sent from my NX659J using Tapatalk
Click to expand...
Click to collapse
Have you tried "fastboot flashing relock"
relock not lock
zayidhs said:
Have you tried "fastboot flashing relock"
relock not lock
Click to expand...
Click to collapse
Yes, it only accepts "fastboot flashing lock".
In any event, no matter if I unlock/relock the bootloader on the CN Rom or switch to the global ROM and do the same the fingerprint error persists. I even installed TWRP again and formatted data and did everything all over again.
Looks like I'm stuck with either face unlock only on CN or no fingerprint on global.
Really appreciate all the help though!
terrapin4 said:
Yes, it only accepts "fastboot flashing lock".
In any event, no matter if I unlock/relock the bootloader on the CN Rom or switch to the global ROM and do the same the fingerprint error persists. I even installed TWRP again and formatted data and did everything all over again.
Looks like I'm stuck with either face unlock only on CN or no fingerprint on global.
Really appreciate all the help though!
Click to expand...
Click to collapse
We need @JerryYin to supply an unbrick tool. Sounds like a partition has been wiped permanently. Only an unbrick tool will reflash all proper partitions.
VZTech said:
We need @JerryYin to supply an unbrick tool. Sounds like a partition has been wiped permanently. Only an unbrick tool will reflash all proper partitions.
Click to expand...
Click to collapse
No, the unbrick tool won't help. you need re-calibration the fingerprint sensor.
JerryYin said:
No, the unbrick tool won't help. you need re-calibration the fingerprint sensor.
Click to expand...
Click to collapse
Do you have any suggestions on how to fix this?
terrapin4 said:
Do you have any suggestions on how to fix this?
Click to expand...
Click to collapse
Like Jerry said, the fingerprint sensor needs to be re-calibrated.
In the factory
With nubia
Sorry
terrapin4 said:
Do you have any suggestions on how to fix this?
Click to expand...
Click to collapse
For now you have to send the phone back to service center to perform the fingerprint recalibration.
I thought it's software issue not hardware issue , yesterday I checked my friend rooted phone it was work excellent but when I updated it and rooted again it want work again
@JerryYin
Currently I'm getting the "Loss of fingerprint calibration data" message when I try to add a fingerprint. This advises me to contact Nubia's after-sales service via the number "4007006600". This device is provided to me directly by Nubia engineers.
I've just tried to run the calibration and have gotten two errors - one being that the number of bad pixels is abnormal (even though the results are below the threshold), and the other being an "Unknown Error" message
Screenshots of results here: https://photos.app.goo.gl/NpfpDUDgSkMmAc187
gamebenchjake said:
@JerryYin
Currently I'm getting the "Loss of fingerprint calibration data" message when I try to add a fingerprint. This advises me to contact Nubia's after-sales service via the number "4007006600". This device is provided to me directly by Nubia engineers.
I've just tried to run the calibration and have gotten two errors - one being that the number of bad pixels is abnormal (even though the results are below the threshold), and the other being an "Unknown Error" message
Screenshots of results here: https://photos.app.goo.gl/NpfpDUDgSkMmAc187
Click to expand...
Click to collapse
You need to relock tge bootloader. Or send back to customer for re calibration
JerryYin said:
You need to relock tge bootloader. Or send back to customer for re calibration
Click to expand...
Click to collapse
Hi @JerryYin, The bootloader is locked (never unlocked). The device was sent directly by Nubia Engineering, so I can't send it back (no purchase receipt etc).
The issue seems to be that the device never passes the "CALBRATE_CHECKBOX" test, though everything else passes. If you could provide some insight into what this test is checking, I can finish calibrating it myself
gamebenchjake said:
Hi @JerryYin, The bootloader is locked (never unlocked). The device was sent directly by Nubia Engineering, so I can't send it back (no purchase receipt etc).
The issue seems to be that the device never passes the "CALBRATE_CHECKBOX" test, though everything else passes. If you could provide some insight into what this test is checking, I can finish calibrating it myself
Click to expand...
Click to collapse
You should find the person who gives you the phone. The fingerprint calibration data will lost only when you try to unlock the bootloader
Can someone help me, I need better clarification on some things.
So the first set of steps involve:
1) 'call' *#9959* and turn off the 'performance'
2) click 'start' and leave to phone/screen alone aka no touching it whats so ever, then I get the following text in image 1.
Now the steps after that have me confused on some things:
Step 2
3) Click 'Next' and the screen will dim abit
Do I have to leave the screen alone or do I have to put my finger immediately after hitting 'next'?
Cause I saw posts about leaving it alone and others saying to put my finger(thumb).
If I put my finger on the screen it gives me an error '0x3A self-exposure abnormal' (as in image 2);
but if I leave it alone it'll give me 'Auto_Exposure' & 'Flesh' tests succeeded (image 3)
I NEED clarification here, am I doing this part wrong by not having my finger on the Fp scanner.
Now for step 3, I have to:
4) click on 'Next' and the phone will do the 'Dark' and 'Dark-Base' tests. The should be left alone here as well. (Image 4)
I need to be in a dark room for this, correct?
Now for the final step
6) Click 'Next' and put my finger back to the screen on the blue FP scanner(?)
When I do this; I end up with '0x14 the number of bad pixels....' (image 5)
Any help is very up appreciated.
So recently my Mi 11x got stuck on the mi recovery mode 5.0. Tried reboot to system but it loops back to the recovery mode and phone dosent connect to pc via the connect to Miassistance mode , selected the safe mode option too but again loops back to the recovery mode. last ooption there is wipe data but i dont want to lose data. Only if i could get a backup or save the data how can i do it? any way i can connect it to a computer and access the files? also is this a software or a hardware issue, before this issue happened my phone was not free on space and had only 100 mb storage left so was it that thing which caused the problem? a local repair shop told me its the issue of motherboard but he didnt check the phone physically. My only priority is i need to get back my data .
Is your bootloader unlocked?
In that case, you can retrieve your personal data by booting into a Custom Recovery like TWRP or OrangeFox. You may need to enter your Password/PIN.
"fastboot boot twrp.img"
Are you simply using MIUI, or Xiaomi.eu? Do you use Magisk? Any modifications?
cyanGalaxy said:
Is your bootloader unlocked?
In that case, you can retrieve your personal data by booting into a Custom Recovery like TWRP or OrangeFox. You may need to enter your Password/PIN.
"fastboot boot twrp.img"
Are you simply using MIUI, or Xiaomi.eu? Do you use Magisk? Any modifications?
Click to expand...
Click to collapse
no the bootloader isnt unlocked and yes the phone was still using miui no modifications done
manas77 said:
no the bootloader isnt unlocked and yes the phone was still using miui no modifications done
Click to expand...
Click to collapse
Hm.. you might have to factory reset...
cyanGalaxy said:
Hm.. you might have to factory reset...
Click to expand...
Click to collapse
okkk thanks ,, also do these softwares like dr fone actually work like can i extract data even after the format ??
manas77 said:
okkk thanks ,, also do these softwares like dr fone actually work like can i extract data even after the format ??
Click to expand...
Click to collapse
Sorry, no they will not work.
you could try holding the power button until the phone reboots twice or trice and then leave the power button and let it boot.
i used to get random bootloops on my family phones that have never heard of the word root. That usually did the trick