I Have A Galaxy S1 i9000T and it is pattern locked and i want to unlock it but i forgat the pattern.
so the steps i did are:
rebooted to recovery and when i tried to wipe data it asked for a PASSWORD.
then i tried to reflash stock rom and when it has finished the phone booted up and still LOCKED!!!
then i tried to unlock from adb and when i typed cd /data/data... it said can't cd ... promission denied.
so i dont know what to do.
i also tried to root and install cwm but i can't find cf root for i9000TJJJVB.
So i really need help.
LSGio said:
I Have A Galaxy S1 i9000T and it is pattern locked and i want to unlock it but i forgat the pattern.
so the steps i did are:
rebooted to recovery and when i tried to wipe data it asked for a PASSWORD.
then i tried to reflash stock rom and when it has finished the phone booted up and still LOCKED!!!
then i tried to unlock from adb and when i typed cd /data/data... it said can't cd ... promission denied.
so i dont know what to do.
i also tried to root and install cwm but i can't find cf root for i9000TJJJVB.
So i really need help.
Click to expand...
Click to collapse
If you have forgotten your pattern, input wrong pattern multiple times. Then it'll ask you if you have forgotten the pattern. Then just enter in your gmail id along with your password. If you have forgotten your gmail password as well, then you should flash your stock firmware via odin. I will reset everything.
I know this has been asked a lot but, I see any of different info. I see there are kernels and boot images that basically decrypt. I'm going for the boot img and was wondering if I have a nandroid backup can it be restored after it has been decrypted? I haven't seen any info on it for the boot img , just the kernel way. Are the backups encrypted or just raw data and when it boots or booting it encrypts?
Anything?
bryantjopplin said:
Anything?
Click to expand...
Click to collapse
Please use the main thread:
http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
I've already read that and was not pertaining to my situation. I was already setup and running with root and unlocked boot loader and didn't want to loose anything. I have figured it out though, FYI. But thanks for not paying attention to the full question
If you backed up whilst encrypted then the data will be encrypted.
Your need to back up by connecting to computer and copy/paste all your needed data. Then decrypt then restore data back on.
flashing these kernels will not decrypt. They just dont force encryption, meaning if you factory reset and then wipe /sdcard, you wont be forced to encrypt on next boot.
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
shree alwaz said:
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
Click to expand...
Click to collapse
fastboot erase recovery
fastboot flash recovery twrp.img
thank me later
Sudhanshu030299 said:
fastboot erase recovery
fastboot flash recovery twrp.img
thank me later
Click to expand...
Click to collapse
Are you will it be successful L?
shree alwaz said:
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
Click to expand...
Click to collapse
If you flashed OOS (stock or OB), then it will always restore the stock recovery after a reboot.
If you want to have TWRP "stick", then you'll have to flash the modified boot image from here https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
The modified boot image turns off the flag that restores the stock recovery.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
If you flashed OOS (stock or OB), then it will always restore the stock recovery after a reboot.
If you want to have TWRP "stick", then you'll have to flash the modified boot image from here https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
The modified boot image turns off the flag that restores the stock recovery.
Click to expand...
Click to collapse
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
shree alwaz said:
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
Click to expand...
Click to collapse
If you are running pure OOS, then the only way to have TWRP not get replaced by the stock recovery is to either use:
- a modified boot image
- a custom kernel
- or use Magisk
This is all tied up with dm-verity. Any of the three options I listed will remove the dm-verity flags that result in overriding TWRP.
Of course you can try just flashing TWRP and see what happens. If it sticks (but I think it won't), good. If it doesn't stick then you've learnt something and you know how too fix it.
Sent from my OnePlus3T using XDA Labs
shree alwaz said:
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
Click to expand...
Click to collapse
It depends on the exact sequence you are talking about:
1) If you flash TWRP, than immediately flash a custom ROM (without rebooting), it should then be patched to prevent TWRP being overwritten (with stock recovery). So maybe that is what you did last time. Alternately, immediately rooting (SuperSU or Magisk) or a flashing a patched boot image, will in either case prevent TWRP from being overwritten.
2) If you flash TWRP, then reboot (before flashing anything in TWRP) then in most cases you will find TWRP is overwritten.
However, if you flashed TWRP then immediately tried to boot TWRP but got stock recovery, then something else is going on (TWRP never flashed, and did not get overwritten - you need to reboot the phone for that to happen). Try erase cache and flash TRWP again. Of you can try boot TWRP without actually flashing it, as a workaround: fastboot boot TWRP.img
BillGoss said:
If you are running pure OOS, then the only way to have TWRP not get replaced by the stock recovery is to either use:
- a modified boot image
- a custom kernel
- or use Magisk
This is all tied up with dm-verity. Any of the three options I listed will remove the dm-verity flags that result in overriding TWRP.
Of course you can try just flashing TWRP and see what happens. If it sticks (but I think it won't), good. If it doesn't stick then you've learnt something and you know how too fix it.
Click to expand...
Click to collapse
If flash twrp and reboot the phone and then going back to recovery giving stock recovery only. Are you saying I need to flash custom kernel or magisk to get twrp?. My doubt is with out twrp can flash kernel or magisk? I am confused what to do?
redpoint73 said:
It depends on the exact sequence you are talking about:
1) If you flash TWRP, than immediately flash a custom ROM (without rebooting), it should then be patched to prevent TWRP being overwritten (with stock recovery). So maybe that is what you did last time. Alternately, immediately rooting (SuperSU or Magisk) or a flashing a patched boot image, will in either case prevent TWRP from being overwritten.
2) If you flash TWRP, then reboot (before flashing anything in TWRP) then in most cases you will find TWRP is overwritten.
However, if you flashed TWRP then immediately tried to boot TWRP but got stock recovery, then something else is going on (TWRP never flashed, and did not get overwritten - you need to reboot the phone for that to happen). Try erase cache and flash TRWP again. Of you can try boot TWRP without actually flashing it, as a workaround: fastboot boot TWRP.img
Click to expand...
Click to collapse
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
shree alwaz said:
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
Click to expand...
Click to collapse
Temporarily boot into twrp with fastboot, copy zip files to memory using MTP (it will activate automatically, when TWRP boots successfully you can see the phone on your PC), flash them in TWRP, profit.
^ assuming you have already made a backup
Or you can flash TWRP in fastboot, then boot directly into recovery (which will be TWRP) and the recover or flash ever ROM you want.
If you restart your phone with OOS installed and TWRP as your recovery, the stock recovery will replace TWRP.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Or you can flash TWRP in fastboot, then boot directly into recovery (which will be TWRP) and the recover or flash ever ROM you want.
If you restart your phone with OOS installed and TWRP as your recovery, the stock recovery will replace TWRP.
Click to expand...
Click to collapse
Thanks for your prompt reply. I did that and now I could able to use twrp. It's a lesson learned for me.
Moreover, I have doubt that my phone is encrypted and I have not triggered DM-verity. Whenever I boot into my phone first it asks the password then only it will reboot the phone as well as twrp. What should I do to remove it? If I follow the instruction which sent me in your second reply, should I follow that?
shree alwaz said:
Thanks for your prompt reply. I did that and now I could able to use twrp. It's a lesson learned for me.
Moreover, I have doubt that my phone is encrypted and I have not triggered DM-verity. Whenever I boot into my phone first it asks the password then only it will reboot the phone as well as twrp. What should I do to remove it? If I follow the instruction which sent me in your second reply, should I follow that?
Click to expand...
Click to collapse
No, keep the on boot password. It's a great security mechanism. It prevents anybody from getting access to your data via TWRP.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
No, keep the on boot password. It's a great security mechanism. It prevents anybody from getting access to your data via TWRP.
Click to expand...
Click to collapse
Boot password is nothing but forced encryption on?
You can have encrypted storage with a default password in which case you're not asked for a password on boot or to read the data in TWRP. So then anybody could access the data using TWRP.
But if you have it encrypted and set an on boot password you will also need it to decrypt the data using TWRP.
Sent from my OnePlus3T using XDA Labs
shree alwaz said:
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
Click to expand...
Click to collapse
As you've now figured out, your mistake is rebooting. As I already described, rebooting before flashing root (Magisk or SuperSU) or patched boot image (or custom ROM w. patched boot image) will by definition wipe TWRP. This is normal and expected.
Fastboot flash TWRP. Then in bootloader screen, select recovery, and it should go to TWRP. Then flash one of the above described files to make TWRP "stick".
---------- Post added at 09:25 AM ---------- Previous post was at 09:20 AM ----------
shree alwaz said:
If flash twrp and reboot the phone and then going back to recovery giving stock recovery only. Are you saying I need to flash custom kernel or magisk to get twrp?. My doubt is with out twrp can flash kernel or magisk?
Click to expand...
Click to collapse
No, that is not what he is saying. Yes, you need TWRP to flash a custom kernel or Magisk. Fastboot flash TWRP, then immediately select "recovery" from the bootloader menu and do not reboot the phone.
You don't need custom kernel/Magisk to flash TWRP (that would be a cart before the horse type situation, as you somewhat figured out). But doing so, makes TWRP "stick" and not get wiped (replaced with stock recovery).
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
shree alwaz said:
Boot password is nothing but forced encryption on?
Click to expand...
Click to collapse
Encryption is not the same as forced encryption.
Forced encryption means that if your phone is decrypted, flashing an update will (I believe) "force" it back to being encrypted. For folks that want to stay decrypted, they will want to disable forced encryption. If your phone is encrypted, it doesn't matter if you have forced encryption or not. It will stay encrypyted in either case.
BillGoss said:
You can have encrypted storage with a default password in which case you're not asked for a password on boot or to read the data in TWRP. So then anybody could access the data using TWRP.
But if you have it encrypted and set an on boot password you will also need it to decrypt the data using TWRP.
Click to expand...
Click to collapse
There used to option in settings menu to disable that. But now I cant able to see that option. Do you know where can I find it.
And moreover I have little confusion between encrypted phone and setting up boot up password. I thought both are same. If both are not same. Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
shree alwaz said:
Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
Click to expand...
Click to collapse
Encryption is always useful if paired with bootup password - in case of theft no one can read your data.
You will be asked for password, if you explicitly set it up in OS.
And what option do you mean?
shree alwaz said:
There used to option in settings menu to disable that. But now I cant able to see that option. Do you know where can I find it.
Click to expand...
Click to collapse
If you change the security option (fingerprint, password or pattern), it will ask if you want to require a boot up password. But it will also wipe your present password, fingerprint, etc.
---------- Post added at 04:33 PM ---------- Previous post was at 04:21 PM ----------
shree alwaz said:
And moreover I have little confusion between encrypted phone and setting up boot up password. I thought both are same. If both are not same. Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
Click to expand...
Click to collapse
It's a fair question, and I'm not sure I understand all the subtleties myself. But as I understand it (and others please correct me if anything below is wrong or incomplete):
1) Encryption means all your data is essentially "garbled" and cannot be read without the encryption key (for which you need password, fingerprint or pattern). So even if someone can pull some data off your phone (which I think would be hard) they can't read the data.
2) Even if the phone is encrypted, data is decrypted once you boot TWRP. You can literally plug the phone to a computer and read the data. Boot up password prevents this (phone will not boot to TWRP unless you enter the password).
Now a couple questions that still persist in my mind:
3) Is there any point in having a boot up password on a stock device (stock recovery)? If the phone is lost of stolen, it will prevent the person from rebooting the phone. But nothing until they do so. Is there some possible exploit that requires them to reboot?
4) Encryption, no boot up password, with TWRP is not very secure (and therefore not much of a point)? I guess you can rationalize that a thief would have to be pretty tech savvy to know that data can be accessed via TWRP. But certainly possible. If you have TWRP and care about security, is it basically advised to encrypt and have a boot up password?
redpoint73 said:
If you change the security option (fingerprint, password or pattern), it will ask if you want to require a boot up password. But it will also wipe your present password, fingerprint, etc.
---------- Post added at 04:33 PM ---------- Previous post was at 04:21 PM ----------
It's a fair question, and I'm not sure I understand all the subtleties myself. But as I understand it (and others please correct me if anything below is wrong or incomplete):
1) Encryption means all your data is essentially "garbled" and cannot be read without the encryption key (for which you need password, fingerprint or pattern). So even if someone can pull some data off your phone (which I think would be hard) they can't read the data.
2) Even if the phone is encrypted, data is decrypted once you boot TWRP. You can literally plug the phone to a computer and read the data. Boot up password prevents this (phone will not boot to TWRP unless you enter the password).
Now a couple questions that still persist in my mind:
3) Is there any point in having a boot up password on a stock device (stock recovery)? If the phone is lost of stolen, it will prevent the person from rebooting the phone. But nothing until they do so. Is there some possible exploit that requires them to reboot?
4) Encryption, no boot up password, with TWRP is not very secure (and therefore not much of a point)? I guess you can rationalize that a thief would have to be pretty tech savvy to know that data can be accessed via TWRP. But certainly possible. If you have TWRP and care about security, is it basically advised to encrypt and have a boot up password?
Click to expand...
Click to collapse
Thanks you clarification. After reading your explanation even I got the same question 3 and 4.