Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.
adrian0883 said:
Hello Everyone,
Today a friend gave me a phone that I would like to use, but it has a screen lock passcode on it that she doesn't know. The phone was given to her, but she couldn't use because it's AT&T and she is on T-Mobile so she passed it on to me. I checked the IMEI number on several sites and it's clean so i shouldn't have any issues. Is there a way I can remove the passcode from this phone?
My apologies if this is in the wrong section.
Click to expand...
Click to collapse
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process
i can help you , if your device still soft break
Osamaaj03 said:
Hi, do you still have the phone on you? I've basically hard brick mine and now I need a full mtk dump to get it back as it was. so if you do, can you upload this files? don't worry if you don't know how to do that, I can walk you through the process
Click to expand...
Click to collapse
sahelkhan022 said:
i can help you , if your device still soft break
Click to expand...
Click to collapse
it is, I think the problem is with the super image but I'm not 100% sure. so if you can share a full mtk client backup it would be awesome. if not, a super image will do
your device stuck on logo ? or deadboot ?
842.92 MB file on MEGA
mega.nz
sahelkhan022 said:
your device stuck on logo ? or deadboot ?
Click to expand...
Click to collapse
every time I try to turn it on it bootloops to fastboot mode, I suspect that the issue is a super image I found online, flashed not knowing that it was corrupted (which I discovered later), and I foolishly didn't create a backup (why I went and downloaded the corrupted image in the first place) thinking that I will never go back to the stock rom but now after I have used a couple gsi's for a while found out that the og rom performance was much better and decided to go back
sahelkhan022 said:
842.92 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
so this is just a bunch of .bin files that I have to flash using mtk client to said partitions? just making sure
and just to let you know I might not be able to download the file today, the internet is pretty sucky where I'm rn, so I hope you don't have a problem keeping the file up till tomorrow. and just wanted to thank you for the incredible help, I've been trying to fix this phone for the last two weeks which was headache inducing say the least.
you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..
sorry for the late response, but yeah I've flashed all of the files using mtkclient and it didn't work Idk if I have messed things up, I thought reflashing all of the stock firmware would fix everything but it seems that there's still something wrong
sahelkhan022 said:
you can flash this with lots of free tools .. if secure boot on you can't flash directly but i will help you . you just need to share your screen with me ..
Click to expand...
Click to collapse
I've unlocked the bootloader and disabled boot verification, tried fastboot -w and fastboot format userdata and non of it worked, and I'm really sorry but I can't share my screen because as I've mentioned before my internet is bad and I had to go somewhere else to get the files. can I share anything else with you that might help, I have some recovery log files
IT WORKED!!!!! I don't know what was the problem, I've tried flashing the files again but this time using the terminal instead of the gui AND IT WORKED. THANK YOU THANK YOU THANK YOU
I'm going to upload the files later in case someone else encountered the same problem
Related
hello,
This morning i was using my phone like every day, but i notice that i had no signal so i decided to restart the phone. When it restarted out of nowhere the phone started to boot loop.. i didnt do anything for it to start doing that.. after a long while trying to fix it i gave up and got into recovery and decided to clean install the rom. It did install but after 1 minute of being on the screen it would boot loop.. I download it the same rom and installed it and still kept doing the same thing.. i had a back up so i decided to install it which i did but again after 40 seconds of start up it would boot loop.. finally, i decided to use the LG Flash tool TWICE and it did work but again after a little while the phone turns off and on.. idk what lese to do??? any ideas?
Check if it displays your IMEI in the Settings. If not you should check if you've got a EFS Backup.
vixman said:
hello,
This morning i was using my phone like every day, but i notice that i had no signal so i decided to restart the phone. When it restarted out of nowhere the phone started to boot loop.. i didnt do anything for it to start doing that.. after a long while trying to fix it i gave up and got into recovery and decided to clean install the rom. It did install but after 1 minute of being on the screen it would boot loop.. I download it the same rom and installed it and still kept doing the same thing.. i had a back up so i decided to install it which i did but again after 40 seconds of start up it would boot loop.. finally, i decided to use the LG Flash tool TWICE and it did work but again after a little while the phone turns off and on.. idk what lese to do??? any ideas?
Click to expand...
Click to collapse
mmeidl78 said:
Check if it displays your IMEI in the Settings. If not you should check if you've got a EFS Backup.
Click to expand...
Click to collapse
I already checked and everything says unknown. I do not have any type of backup! is there something i can do?
Congratulations! Now your on the same step as I am. Don't know how to fix this without a EFS Backup.
vixman said:
I already checked and everything says unknown. I do not have any type of backup! is there something i can do?
Click to expand...
Click to collapse
mmeidl78 said:
Congratulations! Now your on the same step as I am. Don't know how to fix this without a EFS Backup.
Click to expand...
Click to collapse
OHH wow!! so im basically stock with a brand new phone that boots on and off ..Wow.. well if you ever find an answer can you please share it with me!!! thank you in advance.
I have no idea what kind of backup you are talking about but could we use it from another G2?
Maybe this will help you find out what a EFS-Backup is:
http://forum.xda-developers.com/showthread.php?t=2451390
I've seen the question somewhere else (to use a backup from another g2) and they said, that it will boot but don't login into the network, cause you'll get a IMEI with 00000 or something like this.
Don't know a answer. I think I must send my G2 to LG and pay a lot of money IF they'll fix it.
vixman said:
OHH wow!! so im basically stock with a brand new phone that boots on and off ..Wow.. well if you ever find an answer can you please share it with me!!! thank you in advance.
I have no idea what kind of backup you are talking about but could we use it from another G2?
Click to expand...
Click to collapse
mmeidl78 said:
Maybe this will help you find out what a EFS-Backup is:
http://forum.xda-developers.com/showthread.php?t=2451390
I've seen the question somewhere else (to use a backup from another g2) and they said, that it will boot but don't login into the network, cause you'll get a IMEI with 00000 or something like this.
Don't know a answer. I think I must send my G2 to LG and pay a lot of money IF they'll fix it.
Click to expand...
Click to collapse
OHH i see what you mean... I have added EFS backup to the IOroot scripts so that everyone that roots will have a copy of their EFS partitions on the computer you run IOroot from. Regardless, this current thread will still be a good "heads up" and an alternative for those who insist on using other shady root methods or for those who just want another way to back things up.
I did use IOroot, does that mean that if i connect it to the computer and try to root it again it would fix it? you think???
vixman said:
OHH i see what you mean... I have added EFS backup to the IOroot scripts so that everyone that roots will have a copy of their EFS partitions on the computer you run IOroot from. Regardless, this current thread will still be a good "heads up" and an alternative for those who insist on using other shady root methods or for those who just want another way to back things up.
I did use IOroot, does that mean that if i connect it to the computer and try to root it again it would fix it? you think???
Click to expand...
Click to collapse
In the Thread is a step-by-step tutorial how to restore EFS-Files. Make a Backup of these 2 files before you root your phone again! Don't know, if those 2 files got overwritten (maybe with the damaged data) when you root your phone again.
Fixed my phone
mmeidl78 said:
In the Thread is a step-by-step tutorial how to restore EFS-Files. Make a Backup of these 2 files before you root your phone again! Don't know, if those 2 files got overwritten (maybe with the damaged data) when you root your phone again.
Click to expand...
Click to collapse
Well just wanted to let you know that i sent my phone to LG for them to fix it. They didnt charge me and all they did was re-flash the rom. if you havent fixed it you should try sending it to them.
Hello XDA, this is my first post, this comunity is awesome and helped me a lot for a couple of years now.
there always seems to be a solution to everything!
but now i realy ****ed up. i accidentaly checked the wrong thing on the so called "smart phone flash tool"
i klicked firmware upgrade instead of download only.
is there any way so rescue my phone? thank you very much in advance! :crying:
here is a screenshot: (i cant paste link because i am new):crying:
I'd better let someone more qualified answer your query but I'm pretty sure your situation can be recovered easily. What happens if you try to reflash the firmware again with the correct settings? These phones are pretty hard to brick!
charliepie said:
I'd better let someone more qualified answer your query but I'm pretty sure your situation can be recovered easily. What happens if you try to reflash the firmware again with the correct settings? These phones are pretty hard to brick!
Click to expand...
Click to collapse
there probably is SOME way to fix it, i am sure, but the phone does not even boot into recovery.
Mediatek phones are hard to brick, haha
It is PROBABLY going to give a headache in order to find the needed files, flash the stuff again and etc using the proper way, but PROBABLY your phone will relive again. Try rooting and installing Eragon after a full wipe, if that option is available.
You may look here:
Bricked P8000
This may help.
I was in the same state when I accidentally flashed a the wrong logo.img file. I fixed it by doing a format on flashtool>stock rom>custom recovery>custom rom again!
abubakar486 said:
I was in the same state when I accidentally flashed a the wrong logo.img file. I fixed it by doing a format on flashtool>stock rom>custom recovery>custom rom again!
Click to expand...
Click to collapse
hi, thank you; but my phone does not even boot. it gets recognized by the pc though
New problem
OKAY now i got everything working so far. but there is a new real big problem. it has some kind of imei error so it doesnt let me use data on the way
how can this be fixed? i mean, i have the correct imei s right here whith me.
thank you in advance.
Data is turned on under data usage in settings menu and the APN is correct? What does the error message say and can you make calls/SMS OK?
FIXED
charliepie said:
Data is turned on under data usage in settings menu and the APN is correct? What does the error message say and can you make calls/SMS OK?
Click to expand...
Click to collapse
Hey! i fixed it. again fith XDAs help
http://forum.xda-developers.com/canvas-a1/general/fix-imei-perfect-fix-android-imei-t2943567
solution 2 worked for me.
Also i have a new problem. when connecting my bluetooth speaker it says...well maybe this belongs to another forum :good:
KillSwitch​
Three different ways that I found to get rid of the KillSwitch
Through deactivating and then reactivating your google account/s.
Using the Hard Brick Recovery method.
Octopus/Octoplusbox.
Explanation​
The one I actually tried was the Hard Brick Recovery Method (WillCracker), but
even after that I was still unable to bypass the KillSwitch. So I went back BoardDiag and decided to flash the System, UserData, and Cache since I still couldn't get into download mode.
After about 5-6 hours it was completed. I try booting up download mode and guess what?! KillSwitch is still there xD. I'm absolutely fustrated now and all I could think of is to flash the rest of the files that the HBRM didn't say anything about.
I started flashing in this order: Modem, Misc, Persist, and RCT. Everything is now flashed and I hope everything worksout.
I turn on the phone, waiting patiently. Bootloop over and over again, but guess what?! I tried download mode one last time before I was going to go ape $h!t. Then to my surprise the download mode screen turned on, I used the LG Flash Tool and I am now killswitch free.
KillSwitch did come back after a few updates, but I was able to enter in a pin code allowing me in the future to turn it off at will
Well thank you all for listening, just wanted to share my experience.
as my first post, I do apologize in advance if this is the wrong area for this.
Keep on keeping on xD
Can you tell me the exact order you flashed the phone using boardiag? Thanks in advance!
siredux said:
Can you tell me the exact order you flashed the phone using boardiag? Thanks in advance!
Click to expand...
Click to collapse
Warning: This may or may not work, and might brick your phone.
Hope this helps
http://forum.xda-developers.com/lg-g3/general/guide-unlock-mcafee-lock-lg-g3-t3264963
Solved
JackTraits said:
Warning: This may or may not work, and might brick your phone.
Hope this helps
http://forum.xda-developers.com/lg-g3/general/guide-unlock-mcafee-lock-lg-g3-t3264963
Click to expand...
Click to collapse
Link u shared shows Test points for G2 .... Correct test Points for G3 are Shown in following video
https://www.youtube.com/watch?v=04AgASAWJu8
Hey guys i have a serious problem..i tried to unlock bootloader and install another rom but my phone i think so its dead... :crying: I unlocked it succesfully,installed twrp,then rom by recovery mode,i made reboot the device,and the rom wasnt installed,so i made again reboot device in twrp by the tool https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 and then it was like everything was deleted..no partitions nowhere,like everything had gone..and now i cant even reboot on twrp just on fastboot and i can only lock/unlock my bootloader.When i lock i take the message "Cant find vaild operating system,The device will not start....:crying: The case is that i didnt made any kind of wipe...how its possible this to happen?Can any professional guy help me here because i tried so much to bring it back to the normal condition but i dont see any solution anymore..
You have a Pixel/Nexus device. Download and flash the factory image the correct way from Google and start over.
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Good instructions at top of this page, then the download for your phone model is below.
If you do not understand any step, Google it, then read and understand completely
before proceeding. Be sure you have most current version of Android Tools.
https://developers.google.com/android/images#taimen
Don't panic and make it worse. Make sure you have adb/fastboot environment and drivers on your computer and follow the directions for reinstalling stock.
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
Jinthegodstyle said:
Wich is the correct way..?i tried everything but i cant flash....:/ on other devices i had owned and tried flashing roms i didnt had this problem that i have now..
Click to expand...
Click to collapse
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Yeah as others above have said, don't panic. I've been flashing/ rooting/modding since the way back and one thing I've learned is, it's VERY hard to brick a phone completely. Especially with newer ones, there's almost always a way to recover your phone, and especially since you have fastboot, you're not bricked either. Flash the stock rom through fastboot and you should be all set!
also make sure that your cable is good. i had major problems with many cables. finally one cable actually worked. took me hours to realize tha the cables were the culprits.
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
mac796 said:
I noticed in your comment you said you could lock and unlock the bootloader I hope you didn't lock it when you had a ROM installed you might be screwed if that's the case.
Click to expand...
Click to collapse
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
Az Biker said:
Here are some easy to follow steps,
All needed file, or links are also in one place.
As long as you can fastboot, you should be able to get up and running.
Good luck!
Click to expand...
Click to collapse
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Jinthegodstyle said:
thx alot eveyrone for your answers..i step up a little bit forward but still i cant finish it...i can go on twrp mode,and there it doesnt shows me any kinf of file..only on Restore i have the last rom that i tried to install...how its possible?
i follow your instructions but i have errors on cmd like:
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'...
Edit* Also in twrp when i go to make reboot, i have the message No OS installed..
And Failed to mount "/system" (Structure needs cleaning)
Click to expand...
Click to collapse
Dude. Start from scratch. Can you get in fastboot and is your bootloader unlocked? Are you doing this all with a tool or are you manually putting in commands It's hard to tell you what to do without all the info.
Edit.... Just saw you used a tool.... I don't care for tools. because of stuff like this. The tool should have installed the adb folder on your computer. Find that folder and open it. Download the Google zip file with stock os and Unzip into your adb foldee or SDK folder . Open the file from Google. While in there open a terminal. Have phone in fastboot mode and plugged in. Type "fastboot devices"
If it shows a number, you are connected.
Now run the bat file and it should install the os
Read all the way through then reread it .
Carefully follow steps. Forget about twrp for now.
https://developers.google.com/android/images
Don't forget to open terminal as administrator
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Jinthegodstyle said:
Good morning and thanx a lot to each one of you guys!!)) finally i made it.. The bug was on that tool i think so.. One other guys mentioned me to put all the contents of factory image, etc on the tool folder and from the tool application to choose the factory image and flash it.. And it worked!! I am Just saying it if somebody will have a problem with that, how to Solve it.. For today i am not gonna try to flash any rom, next Days i will give another try.. It would be mistake if i will lock again device? (Just asking to know for the future, because this message after rebooting Phone its kinda annoying) Again thx a lot everyone spending your time For my problem!!
Click to expand...
Click to collapse
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches ?
Badger50 said:
DO NOT LOCK THE BOOTLOADER!! Unless you want to return it or sell it to someone else, even than, I still wouldn't do it. The annoying message your getting is just that...an annoying message, nothing more. IGNORE IT! You'll save yourself a bunch of headaches
Click to expand...
Click to collapse
Thx for advice mate!! Finally after yesterdays adventure with my new toy,today i flashed without any issues in 5 minutes the rom i wanted and it was more easy than i imagined..you see after many xiaomi phones i was confused and couldnt imagine how easy could be on google phones..Now i wont touch nothing since evertything works preety good!! Thx again!!
CyberpodS2 said:
THIS IS A PUBLIC SERVICE ANNOUNCEMENT. People, Please stop locking your bootloader. It may or may not be this guys issue but it certainly "can" destroy your phone if your not 100% stock!!
Click to expand...
Click to collapse
when rma'ing it, one should defo go with locking bootloader though, i reckon.
xflowy said:
when rma'ing it, one should defo go with locking bootloader though, i reckon.
Click to expand...
Click to collapse
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
I always always always make sure the device boots before i ever lock the bootloader. I've read to many horror stories.
With this kind of phone, i think anyone should refrain from using any kind of so called "tool", aside from the basic adb n fastboot itself.
Badger50 said:
Heck no. Just do a factory reset and send it back. Unlocking the bootloader does not void your warranty ?
Click to expand...
Click to collapse
does this also apply to the critical unlock method or do i, at least, have to lock critical?
So, I made a bit of dumb mistake after getting the TA-1050 TWRP installed and accidentally wiped the system partition and I'm kinda freaking out at how I'm going to get this phone functional again. If not in download or TWRP recovery mode, it is in a constant boot loop (which sucks) but it's hope that I haven't completely messed up.
So, to the point, is there firmware flying about that I can use to help dig myself out of this hole or will I need to rely on a backup phone until said firmware is brought to light?
Lesson to learn: Don't touch anything that doesn't need to be touched :good:
Edit: My phone now only reboots into download mode. Not sure what that's all about but it still at least works, so there is hope.
Going to bump this and say that if anyone can provide how I can flash it with the firmware (well, once I can get it) in a step by step format.
Either numbered or bulletin would be fine but just something that's clear and get's right to the point of how I can reverse this issue.
Anyone got anything?
Only firmware files i'm aware of is https://forum.xda-developers.com/no...-to-flash-global-firmware-pl2-222e-0-t3831764
who knows what models it works on and if its legit though
really sucks nokia doesn't provide factory images
I had the same problem several days ago and the only way I was able to fix it was using the stock 1043 (I have a 1045) system images to get a functional device. My device still registers as a 1045 so give it a try. I do advise using fastboot to erase and format both the A and B partitions before flashing.
Ozonethegreat said:
I had the same problem several days ago and the only way I was able to fix it was using the stock 1043 (I have a 1045) system images to get a functional device. My device still registers as a 1045 so give it a try. I do advise using fastboot to erase and format both the A and B partitions before flashing.
Click to expand...
Click to collapse
which thread did you get the 1043 image from?
prg318 said:
which thread did you get the 1043 image from?
Click to expand...
Click to collapse
I cannot remember nor find it, lol. Give me a sec, I'll upload them
https://drive.google.com/open?id=1fMySPkJSj8VGiFkUj5t3DMz3yDZdrI2L
if your model has android one softwear (( global version )) follow my thread to get your stock firmware
good luck
https://forum.xda-developers.com/no...pl2-222e-0-t3831764/post77389130#post77389130
Thanks guys, I'll see what I can do with what you've provided. Will report back if it works or fails.
So I didn't intend to get back so much later than I have, uni studies can get pretty hectic.
Unfortunately, it didn't work. I have no idea how much damage I've actually caused but even the daemon can't pick it up when I try to run it in ADB or running powershell to run ADB. Because it's not being detected, I don't have much confidence I'll get this fixed.
Has anyone got any solutions? If you need a video of what I'm dealing with, I'll see what I can do if that'll help.