Hey guys, I am having a huge problem with my PIN. I've been using the same pin for a very long time so I know for a fact that it's right. Now I cannot boot the phone, or get into TWRP.
When I boot the phone it's asking me for the PIN and it just keep saying that it's wrong which I know it's not. When I try to do a hard recovery into TWRP it's asking me for the PIN and then just sits at "trying decryption".
Anyone have any thoughts with where I should go from here? There's nothing on the phone that I need in terms of data so if it needs to be completely wiped out I don't care.. just looking for some guidance.
Thanks in advance.
Seems like you had your phone set up to require a pin even before it starts, which is why you can't even get into TWRP. It's a problem with the 6P, I'll link the thread in a bit if I can find it but basically when you back up a ROM, always remove ALL pins and passwords to unlock the phone first.. There's an issue that if you back up a ROM and keep it password protected, it won't let you get back into it even if the pin is correct, UNLESS you go in your file explorer (in TWRP) and delete a specific file that pertains to the the security features AFTER you restore it, but BEFORE you reboot the phone.
In your case it's worse because you had the device set up to not boot unless a code is entered. Don't ever do that, especially when flashing ROMS. The standard security on the lock screen when you boot the phone up regularly is enough. Had you not did that you'd still be able to boot into TWRP, delete that file, to get access to your back up.
There's nothing you can do now. I had to learn this the hard way too just like you. Load up your laptop and completely restore the phone using Nexus Root Toolkit or something similar, you'll most likely lose all data too. Sorry pal.
Edit- found the thread
http://forum.xda-developers.com/nexus-6p/general/psa-twrp-backups-lockscreen-security-t3245070
Hey it's no problem I don't mind losing all the data on the phone I everything backed up elsewhere.. as long as I can get it back running again it's all that really matters to me.
I'll give Nexus Root Toolkit a shot right now and let you know how it goes.. I appreciate the input.
Where would I go to be able to have the toolkit recognize the phone?
Got it all squared away.. I was able to get the phone recognized by just booting it and letting it sit at the PIN screen. Again I appreciate all your input it was very helpful.
Related
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
I have to have screwed the pooch pretty bad, I'm caught in a loop at the HTC splash screen and then it reboots. Any helps would be very much appreciated. I know I did something, I just don't know what.
you dont give enough info..i mean what steps did you follow? when did things go wrong? what step was it? what was the last thing you did?
pull the battery and then boot into recovery (hold volume down+hold power)
EVOKeith said:
This is the first phone that I have tried any kind of rooting or flashing or etc. I followed steps where given, but I think something has gone wrong in the process because a lot of the folders that used to be on the SD card are now gone. I need to start from square one, and I'm not exactly sure how to accomplish that. I know this is a very noob-ish question, but I would appreciate the help.
Click to expand...
Click to collapse
Flash the RUU from the "All roms" thread
Everything was fine after the root guide I followed (the idiot-proof one). When I attempted to do the Nand access portion something went wrong because I got an error that the SD card was blank or had an unsupported file system. The only choice I had was to format the SD card.
Now, when I attempt to install a downloaded .zip from recovery it acts like it is going to install but goes right back to the menu after a few seconds. IF I tell it to reboot then I get caught back in the splash screen rebooting over and over again.
do a full wipe and cache wipe, reboot and see if that helps before you go any further. you do that when you boot into recovery. that will likely fix it. If not post what it does then.
What happens:
When I boot into recovery the first bit is that it tried to load PC36IMG.zip, I get the following:
Main version is older!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
I selected No and went into Recovery. I wiped all data and cache and rebooted. Once again the white HTC EVO 4G screen comes up for a few moments and then the phone powers off and restarts with the same screen over and over. I'm at a complete loss.
bumping for help
is that pc36img.zip the rom that you initially flashed that worked or is it a different one that was part of the 'nand access portion'? I figured that would be from an 'update.zip', but I barely know what I'm doing outside of the well detailed guides.
If it isn't the rom you flashed, try loading that rom back on there. I hope you have another device you can read/write micro-sd's from.
If it is the rom you flashed try flashing another rom.
...I'm a noob here too, but I'm on my second rooted/custom recovered phone so I'll help as I can.
Did you make a nandroid backup?
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
EVOKeith said:
Whelp, it rolled over and died. Going to Sprint tomorrow. Thanks for trying to help guys.
Click to expand...
Click to collapse
Lucky for you that none a single rep I've ever spoken to in any Sprint store has any idea about anything whatsoever. I returned a Samsung Moment that I never bothered to restore to stock...hey turned it on, it booted up with a "Hacksung, XDA developers" screen, proceeded to load up a (then hours old) 2.1 lock screen and said "Okay, it still works", didn't check to see if I had kept the memory card in or even re-packed the charger and gave me a refund for everything on the receipt, even things I didn't have in the bag.
...another time before that I was asking about the Android 2.1 update and when it was being rolled out to which the sales rep stood up, turned around and yelled "Bobbyyy....what's an android and when do we get one in?"
Though I'm sure there is a way to bring your phone back...perhaps check in on the thread where you got your rom and see if anyone else has had such issues, give all the details you can in the order in which they happened.
If you can still get to the hboot screen try the zip posted here using the instructions here
Alright, so last night I was fooling around with "Type Fresh," which you guys have probably heard of. It was released here... It's a font changer...
Anyway, things were going good until I tried a font named, "Joystix," which replaced quite a few of my fonts. That caused my phone to go into a crazy bootloop.
So, at this point, I do not have Clockwork Recovery. I actually have the Stock Recovery. For some strange reason, my stock recovery just takes me to a screen with a red triangle, and factory reset just shows this hard drive and a loading bar that never goes anywhere before rebooting my phone into a boot loop.
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
wauterboi said:
I've checked to see if ADB will work in my stock recovery, and it does, except for the fact that my phone is, "offline," which is probably not good.
Is there anyway I can get my phone to work again? I remember when I was getting bootloops and I somehow got the phone to reinstall all the correct stuff after going into the stock Volume Down+Power thing a few days ago. I don't know or remember how. Like, it was going into the whole process of giving me the choices and said, "Do you want to update?" I said yes and voila, everything is back to normal. Sadly, this isn't the case atm. :|
halp
Click to expand...
Click to collapse
Well I've never personally used type fresh to change fonts, I've done it in other ways. Just a thought for ya, but I would recommend that if you can get adb to recognize your device (cmd: adb devices) try booting into hboot(volume down + power), and see if it recognizes it regularly that way, from there I recommend trying a program called Droid. It's a windows program that I used when I messed up re-rooting my replacement mt4g (tip: Don't try rooting when having been awake for 26 hours for no apparent reason ). It has a feature called Debug Console which fixed a bootloop, and constant force close that I somehow managed. I also suggest pulling your sdcard, getting a usb scard reader, and installing the stock recovery zip (Pdimg or something like that, I forget off hand).
That's all I can think of, hope it helps
...I finally looked at my SDCard via my brother's phone.
Every thing in my SD Card pretty much has "Font" in front of it in regards to the name.
I mean... Yahoo became FontsYahoo.
wat
Solved.
For those who were wondering, I found out that I had to rename the recovery file to the PBNASFASodhwhatever it was.
Somehow when updating twrp for my girlfriend lost rewrite rights. Have the dreaded lockout without a password even though she was never locked down. Suggested default password does not work. Wug-fresh tool kit is able to connect but gets stuck. Cant boot to enable usb debugging.
sully112277 said:
Somehow when updating twrp for my girlfriend lost rewrite rights. Have the dreaded lockout without a password even though she was never locked down. Suggested default password does not work. Wug-fresh tool kit is able to connect but gets stuck. Cant boot to enable usb debugging.
Click to expand...
Click to collapse
You should be able to go into fastboot and flash a complete factory image. I had the exact same problem. Using flash-all.bat command and image from Google website fixed phone but that also erased everything. Maybe someone else has a less drastic solution.
sully112277 said:
Somehow when updating twrp for my girlfriend lost rewrite rights. Have the dreaded lockout without a password even though she was never locked down. Suggested default password does not work. Wug-fresh tool kit is able to connect but gets stuck. Cant boot to enable usb debugging.
Click to expand...
Click to collapse
So at this point you have only written to the recovery partition? Is her phone stock 7.1.1? Encrypted? Rooted? Kernel? Try to provide as much information as you can. Have you just tried wiping the recovery partition and installing the stock recovery? You can also use NRT to install the previous version of TWRP you started with. That may get you back into the OS. Before wiping data, I would try the flash-all.bat method jhs39 suggests, but removing the -w switch to preserve data. Either that, or use NRT to flash stock + unroot (but select preserve data).
Got it back up and running. Could not get anything to connect through USB. Not even adb. Found a thread where someone had the same problem and tried skipsofts tool so gave that a go and low and behold it work. Got a little nervous for a bit plus had a few adults beverages. Hence the panic thread. Haha. Thanks for the response guys! She's back up and running on pure Nexus.
sully112277 said:
Got it back up and running. Could not get anything to connect through USB. Not even adb. Found a thread where someone had the same problem and tried skipsofts tool so gave that a go and low and behold it work. Got a little nervous for a bit plus had a few adults beverages. Hence the panic thread. Haha. Thanks for the response guys! She's back up and running on pure Nexus.
Click to expand...
Click to collapse
OK good, but are you out of the dog house? :laugh:
v12xke said:
OK good, but are you out of the dog house? :laugh:
Click to expand...
Click to collapse
Haha! That I am.
Ok guys, new here and I've done a bit of reading on this already. From what I gather, the S7 Edge is difficult if not impossible to unlock without a factory reset. Here's the issue.
This phone belongs to my friend's husband who was severely injured in an accident at work. He's in a coma and probably won't survive. He was severely burned over 90% of his body with chemicals and he has no fingerprints to unlock the fingerprint scanner. In addition, his wife doesn't know his password, so I figured I'd see if I could do anything for her. I tried the Dr. Fone program, but it's apparently incompatible with the S7 Edge. He keeps getting texts and messages and we can't check them. The phone is also set for a daily alarm at 1:30 AM, and apparently you can't power it down without the lock code either. Ideally, I'd like to either gain access for her or at least extract what data we can from the thing before factory resetting it. It would also be nice to power it down so that it doesn't keep putting out an alarm every night in the middle of the night. All his contacts with his family are inconveniently stored in the phone as well. It's kind of a worst case scenario.
Any assistance or recommendations for a course of action for this situation would be fantastic. I don't have any other information on the device itself other than that it's running on Freedom Mobile's network in Ontario, Canada. They've said they can factory reset it for her, but we were trying to avoid that and get any contacts or messages from his phone if possible.
Thanks in advance for any help! I know it's a long shot!
Edit: I managed to power down the phone with the Power Button/Volume Down trick after about 9 tries, so at least the alarm won't go off. Other than that, no luck.
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
UnNaMeD__ said:
Unique situation? More like fked up situation.
Anyways I am assuming its a completely stock phone with USB debugging turned off. Hope its not carrier locked, if yes then here are the steps:
1. Flash Custom Recovery on the Phone using Odin
2. Use aroma file manager from the Recovery, you need to download it separately, put it on its SD card.
3. Now using aroma file manager navigate to Data Folder and then; System Folder and find “gesture.key” or “password.key” for pattern lock or password lock respectively.
4. Delete those any password related file and reboot. It should be unlocked now.
Click to expand...
Click to collapse
maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Use odin 3.13 the latest
Then download twrp recovery 3.2.2.0 tar file for hero2lte the latest.
Boot your phone into odin mode by restarting your phone while holding power home button and vol down. When your reach the confirmation screen press OK.
Open odin and put the tar file in the ap slot and click the ap box and hit start to begin flashing.
Now restart ur phone by holding power home and vol down then immediately hold power home vol up to reach custom recovery.
Edit I just tested this myself
Flash the zip file from this thread no need to go looking for files in system.
https://forum.xda-developers.com/showthread.php?t=2780696
Should remove password pin or pattern.
To check if it's network locked just look at the back of your phone if it says 935u or Verizon wireless or 935W8 then the phone is unlocked for different networks.
maxlords said:
Thanks VERY much, UnNaMeD__!!!
I'm looking at Odin and the Recovery firmware right now. Is there a recommended version? I see TWRP and CWM, but primarily TWRP mentioned, and it looks like the .tar files are easy to find. I'm pretty new to this type of mod and I don't want to brick the phone, I know it's a risk. I'm looking at faqs on theandroidsoul and the cyanogenmods forum which seem quite thorough. Apparently I can't post the links as I'm a new user here....seems fair I suppose, especially considering the forum content.
My friend's husband didn't have a microSD card in (just checked), but I can toss a spare one of mine in for Aroma, which I found. I probably need for format it for FAT32, not NTFS though? Is there any way to tell if it's carrier locked? It's from a small phone company, not one of the bigger guys. I'm going to wait until I hear back to get started on this, as I'm decent with Windows based systems, but unfamiliar with the nuances of modding Android. I use a stock Sony XZ Premium myself.
Again, thanks very much! I've got some hope we can get in touch with his family now!
Click to expand...
Click to collapse
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
UnNaMeD__ said:
Just look at back of your phone and tell me its model, Like G935F. I will give you the correct recovery file. And recoveries have option to enable storage too so you can access data from computer. But to be honest it never worked for me. You could also give it a try before doing other steps.
You could contact on PM, or even better I could also help you over whatsapp if you wish.
And I never heard that you could brick phone by flashing recovery, maybe only if you flash incorrectly. A bad recovery will make recovery useless, but phone would still boot. Thats my experience.
I have broken password before of a Mediatek device. If you want I could try it on my own S7 Edge too to be 100% sure.
Click to expand...
Click to collapse
maxlords said:
I'll send you a PM as well, but I just checked and it's a G935W8. Sorry for the delay, I work shift work and I'm pretty busy. I'm going to work on the phone on the weekend. I don't have Whatsapp currently, but I can get it. Thanks again for your kindly assistance!
Click to expand...
Click to collapse
Hey alright no problem.
Download TWRP for G935W8 from official TWRP website:
https://teamw.in/samsung/samsunggalaxys7edge.html
You can follow some instructions from this thread regarding flashing:
https://forum.xda-developers.com/s7...overy-official-twrp-hero2lte-3-0-0-0-t3334084
Flashing TWRP might cause your phone to not boot. You will need to download dm-verity disabler from the thread above.
So download TWRP, Aroma file manager, dm-verity bypass, and zip file to disable pass that the other user posted: https://forum.xda-developers.com/showthread.php?t=2780696
Download all these files and put aroma file manager, dm-verity bypass and that password zip file bypass on your SD.
Make sure auto reboot is disabled in odin, follow instruction in thread about how to install twrp. If the auto reboot is disabled, phone will just remain at the same screen, so after the flashing is done from odin. You need to force reboot on your phone (volume down + power button for few seconds), just when the screen goes off, you need to immediately press recovery button combination (vol up + home + power). Here once you enter TWRP recovery see if you can enable MTP and trasnfer data to PC, if not, goto install zip and try password bypass zip file. If it works file then ok and proceed to install dm-verity bypass file and reboot your phone. If that zip doesn't works. You need to go to same install zip file option and now install aroma file manager. From there delete the password files that I told you about earlier, flash dm-verity and reboot again.
Thats it, if get confused about a step, tell me.
Well, I attempted to install TWRP through the latest version of Odin, but it didn't work. The error message I got in Recovery/Download mode was:
"Custom Binary (RECOVERY) Blocked By FRP Lock."
I looked that up online and apparently to install TWRP, I need to remove the FRP lock. I found a program called RealTerm which can supposedly bypass the FRP lock, but it doesn't seem to be connecting to the locked phone and it's not exactly user friendly.
Am I missing something here? Or is there no way to bypass the FRP lock on the unit?
My phone suddenly had a momentary display malfunction (some of the text on the screen just turned into garbled pixels) and then entered into a boot loop. I didn't make any changes or updates to the phone recently. It no longer boots normally - just the Samsung logo and some of the Verizon logo animation, then it reboots and starts again. How do I pull my user data off (photos mainly) before trying a factory reset? The phone is totally stock. I haven't unlocked it, rooted it, or installed any custom recovery/ROM/bootloader/whatever. (I sound like I don't know what I'm talking about because I don't, haha.) The touchscreen is fully functional. I'm sure this has been covered here before, but I haven't found anything that totally explains how to do this in this particular situation, so I'd really appreciate any help anyone can provide.
The only time I can get the phone to show up under adb devices is when I boot it in recovery mode and select "Apply update from ADB". But it says "sideload" next to it in adb devices, and the push, pull, and shell commands return errors. I've read that this is normal. Wiping the cache partition didn't solve the boot loop problem.
If it helps, this is what the top of the recovery screen displays:
Android Recovery
Verizon/heroqltevzw/heroqltevzw
8.0.0/R16NW/G930VVRSBCTC1
user/release-keys
I'm no Android expert, clearly. I've heard it mentioned that I need to install a custom recovery in order for this to be possible. To be clear, I want to make sure I don't erase the user data before I have a chance to pull it off the phone. These are the questions that I still have after reading information elsewhere (some of which I'm just asking out of an abundance of caution):
Is it correct that I need to install a custom recovery before I can pull this data off the phone?
Do I need to have it unlocked/rooted/anything else in order to be able to install a custom recovery? Or is there anything else I should do before installing it?
Which custom recovery should I install?
Do I need a custom ROM, if that's a different thing?
Do I need a custom...bootloader, if that's also a different thing?
Should I use Odin or Samsung Smart Switch to install the custom recovery?
(Extra credit: Does it sound from my description of how the boot loop started that this phone has hardware problems and should be replaced ASAP?)
Thank you so much for any help you can provide! Any extra information beyond my questions will be very much appreciated, too, of course. You guys never cease to impress.
You have a B version bootloader like me, and so far no root/custom recovery has been made for our versions of bootloaders. If I were you, I would check if you had maybe like a previous backup, and if Google made an automatic backup of your apps and photos? If you didn't use a 3rd party backup, and if you don't want to wait, you might lose some files. I also think you might be able to flash a certain part of stock firmware to get your phone to boot again, but I'm not sure
Also, if you don't care about files that can't be get through automatic backups, might as well flash a whole stock firmware, which as far as I know, may be the easiest way to get out of one.
Please correct me if I'm wrong
Also to answer your bullet points:
1. I'm not sure if you need a custom recovery, but from my experience from a Verizon s5, that's probably a yes.
2. Since this is Verizon, you would need to unlock your bootloader in order to install a custom recovery, which in where I posted my first reply, the B version of the bootloader is still locked down without any known way to unlock it. You and me are stuck with this, as I also have the B version.
3. If the heavens line up and you somehow unlock the bootloader, try to flash a recovery Called TWRP under the name "Herolqte" (that's what I think). If that doesn't work, try to find one that works with the phone on XDA. If neither of those show up try to use another custom recovery like CWM.
4. If your trying to recover data on a phone, flashing a custom ROM is probably the last thing you want to do. A custom ROM is a modified version of Android, which may mean you'll have to format your device anyways so this is probably not what you want (even though it would be nice :[ )
5. As in post 2, all you would need to get a custom recovery is to unlock the bootloader. I'm not even sure if you CAN get a custom bootloader, as Odin won't even let me flash a stock bootloader to my phone that is the same exact Version >:[
6. You would need to use Odin if you were trying to flash something to your phone. Smart switch I think WOULD let you back up your device, but you would need to be on the home screen on your phone, which in turn, would probably need you to be out of that bootloop.
7. This is probably a software issue. If you don't care to much about the idea, try flashing some parts of a stock firmware. I was personally in a boot loop 2 days ago, but I flash a stock modem file (I think that was the second file slot from the bottom in Oden) and that got me out, but for some reason wiped my phone clean, and I'm not sure why.
Anyways. Goodluck in recovering your data. Also I'm not sure if a factory reset would even fix a boot loop
yaas
yaas