SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
OnePlus will not do anything due to the warranty being void...
DM me. I can work this out with you. I ran into a similar problem.
oCAPTCHA said:
It sounds like the MSM tool does not do a full restoration of the device.
If I understand correctly
1. You are able to boot into the operating system, but it crashes during setup when you turn on the wifi.
2. You can get into settings from inside the initial setup, but do not have permissions to access developer options.
I assume you have tried tapping the build number 7 times.
Without the ability to unlock developer options, you will not be able to use ADB and fastboot commands.
Without the ability to unlock the bootloader, you will not be able to fix the device.
Try what you can to prevent the crash during setup. Boot into recovery mode to do a factory reset, Run the MSM tool again, etc.
If that does not work, I think your best option would be to return it to One Plus for repair.
Click to expand...
Click to collapse
Tried sending it for repair but had the op guy look up my imei and ITS A DAMN DEMO PHONE I GUESS!? Cant return it, bought off amazon refurbrished and due to my anger problems i shattered the screen but other than that i shouldnt of been sold a damn demo phone from the start.
T3CHN0T33N said:
OnePlus will not do anything due to the warranty being void...
Click to expand...
Click to collapse
they would repair it, they even repair tmobiles version and metro and all but it really ticked me that amazon refurbrished sold me a demo phone or the phone is now thinking its a demo phone somehow..
Springles2 said:
DM me. I can work this out with you. I ran into a similar problem.
Click to expand...
Click to collapse
Never discuss in DMs! This person has illegitimate intentions.
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
it's not against the rules it's just not a good idea to do
T3CHN0T33N said:
it's not against the rules it's just not a good idea to do
Click to expand...
Click to collapse
Thank you for the advice! Just wanted to see if I could legitimately help!
T3CHN0T33N said:
Never discuss in DMs! This person has illegitimate intentions.
Click to expand...
Click to collapse
illegitimate intentions, lol what are you trying to say? didnt know my intentions had any type of rules to be followed.
if oneplus sends people on the daily unlock codes in order to unlock their bootloaders on their phones, shouldnt people be able to explore some other OS's and things of that sort? My intentions were to TEST out GSI's that developers worked hard on to work with certain devices and provide some feedback and hopefully come along one that i can use on the device as a daily.
This is Forums, know your place. I think we are all a lil illegitimately intentional at times dont ya think?
no offense.
Springles2 said:
Thank you for the advice! Just wanted to see if I could legitimately help!
Click to expand...
Click to collapse
Thanks for your gratitude.
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
jerryhou85 said:
Hello everyone,
It is OK to ask others to send DM for communication if both parties agree.
But, as a general reminder (across the internet), please be caution when you exchange DMs. Make sure you do not post any personal information or financial information to others. Be safe and be alert.
Click to expand...
Click to collapse
Thank you for explaining it to others who might need it
Also, will never ask for anyone’s personal info or financial info or anything to do with their identity. That is their information and have no interest in knowing more than their username on here
Maatt_OG said:
SO, haha been about a week now trying to figure out how to revive my n200 without sending it in to OP..
I successfully converted it to oem, but that wasnt enough for me so i flashed the CherishOS GSI and tried a few other treble projects..
Wanted to go back to oem but in the process of doing so from a GSI , i lost some partitions so i figured to just use the msm tool knowing it was the tmo variant version, since i converted it to OEM it wouldnt work , CORRECT??? Because when it went to boot up after the tool finished it froze on the tmobile boot screen and started a bootloop.
I somehow got it into EDL mode because it didnt recognize the original button combinations to get into edl mode and with the bootloader now re-locked i cant do a damn thing. Used the msm tool again and weirdly when it went to boot up after completion it didnt boot up the tmobile boot screen, it was the oneplus boot screen which had me happy bcuz i wont have to convert it again but at the sametime annoyed because IT WAS STILL IN BOOTLOOP.
BUT WAIT THERES MORE>>>
I finally get it to get passed the boot logo, onto the set up when you first buy the phone, i agree to the terms, it reads my sim and that checks out but when it goes to turn on the wifi to continue set up, it freezes and guess what BOOTLOOP. Have tried a bunch of things even somehow got into settings from emergency call but cant access developer options to be able to unlock bootloader.....
SOSOSOSOSOSOSOSOSOSOSOSOSOSOSOSOS PLEASE HELP?!
Thanks.
Click to expand...
Click to collapse
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Maatt_OG said:
So i actually got the phone going FINALLY, had to wait for the android 12 update and found a couple tricks to get the phone to turn on without it freezing and going into bootloop. I know for a fact that some of the files for the wifi hardware and network were corrupt or deleted along with some partitions so thats why the msm tool didnt work, Converting to oem from tmobile variant also threw a red flag for the msm tool because it is now identified as a oem variant and the tool was only for tmobile.. Just happy to have this phone back, aint the best but after the andoid 12 update, its pretty damn good to me honestly. After this experience i have learned alot about coding, developing, and just more knowledge about how operating systems work along with other components and so on. thanks for trying to help everyone.
Click to expand...
Click to collapse
Please write something up on how you did it! It could save someone!
Springles2 said:
Please write something up on how you did it! It could save someone!
Click to expand...
Click to collapse
Well at times it would just bootloop nonstop after using the msmtool, but then tried entering safe mode and that was a success but remembered each time it went to turn on the wifi to set up the phone it would freeze and bootloop no matter what,
So from emergency call find your way into permission manager , from there you can open settings app, disable location and anything that would trigger wifi to turn on , airplane mode is on remember this, you need to turn it off withput having the wifi kick on. Disabling some modem/network apps or that has anything to do with wifi, location, carrier, modem that you can disable, do it. Once you're able to turn airplane mode off successfully you can get passed the wifi part of the phone setup and use your mobile data instead, or what I did is use gnirehtet , you can find it on GitHub. Install on PC, make sure you enable USB debugging and have the default USB config set to USB tether, not hotspot .extract zip to platform tools, Move the apk file from gnirehtet zip to your phone, run the provided command from the zip and you'll get a request to allow debugging on your phone from PC, once you do that. You'll finally be able to update your n200 T-Mobile phone to Android 12 which is the only way I found to do this. Make sure you update to Android 12 and not another android 11 before turning wifi on or anything else or you will have to start ALL OVER. Done it twice it's a pain in the arse
Springles2 said:
Oh... Didn't know we weren't allowed to talk in DM's.... I'm sorry...
Click to expand...
Click to collapse
I was going to say keep discussion in the open in case any future people come across the same issue. If there's one thing I hate is coming across the same issue as my issue on stack overflow or elsewhere and OP from 7 years ago saying, "Never mind, I figured it out."
Related
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the bootloader but I've never done anything with ADB or fastboot so I'm wondering if that can save me?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
C-4Nati said:
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the bootloader but I've never done anything with ADB or fastboot so I'm wondering if that can save me?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
Click to expand...
Click to collapse
Solved, mod please delete.
C-4Nati said:
Solved, mod please delete.
Click to expand...
Click to collapse
Please post your solution, so others can see it.
C-4Nati said:
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
Click to expand...
Click to collapse
Once you unlock the phone, it'll say "tampered." I don't think you can change that, even if you relock. It's fine, really, though if you want to resell the phone at some point, an unfamiliar user will see this as a red flag, even if you tell them you've rooted the phone. It's sort of a poor choice of working on HTC's part, given that they offer you as a user the tools with which to unlock the phone.
stevedebi said:
Please post your solution, so others can see it.
Click to expand...
Click to collapse
I went into fastboot usb mode in the bootloader then connected the phone to the computer then dragged the fast boot file inside the sdk rar you download for the One into the command prompt then entered "fastboot erase cache" and hit enter then it let me boot into recovery and I reflashed the rom.
maigre said:
Once you unlock the phone, it'll say "tampered." I don't think you can change that, even if you relock. It's fine, really, though if you want to resell the phone at some point, an unfamiliar user will see this as a red flag, even if you tell them you've rooted the phone. It's sort of a poor choice of working on HTC's part, given that they offer you as a user the tools with which to unlock the phone.
Click to expand...
Click to collapse
So essentially if you have a problem and have insurance or a warranty you can't get anything done to repair the phone because even if you re lock the bootloader and unroot they can still see it?
C-4Nati said:
So essentially if you have a problem and have insurance or a warranty you can't get anything done to repair the phone because even if you re lock the bootloader and unroot they can still see it?
Click to expand...
Click to collapse
I hope it's not that extreme. HTC gives you the tools to unlock, after all, for the purpose of doing things that people do with unlocked and rooted phones. At http://www.htcdev.com/bootloader/, HTC says
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
So they imply that at least some claims on an unlocked phone will be covered, possibly even some claims related to the unlocking. I don't know what HTC's history is along these lines, but I'd hope that they see it as being in there interest to reasonably support the dev and geeky community. Getting a bad reputation on XDA, for example, doesn't strike me as being a great business tactic. Not that companies are always so benevolent.
There is warranty risk in unlocking any phone, but it's done all the time as the participation in this forum shows.
When I install a custom rom and get stuck in boot loop. I always do a factory reset and my new rom starts right up. Works every time. I see you solved your problem but maybe next time you try this before you do anything else. Please thank if help
Sent from my Nexus 4 using xda app-developers app
maigre said:
I hope it's not that extreme. HTC gives you the tools to unlock, after all, for the purpose of doing things that people do with unlocked and rooted phones. At http://www.htcdev.com/bootloader/, HTC says
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
So they imply that at least some claims on an unlocked phone will be covered, possibly even some claims related to the unlocking. I don't know what HTC's history is along these lines, but I'd hope that they see it as being in there interest to reasonably support the dev and geeky community. Getting a bad reputation on XDA, for example, doesn't strike me as being a great business tactic. Not that companies are always so benevolent.
There is warranty risk in unlocking any phone, but it's done all the time as the participation in this forum shows.
Click to expand...
Click to collapse
Yeah I understand. I know I'm going to terminate the insurance I have with T-Mobile soon because I've violated the terms with them. I just have a slight screen lift like many others described on the top and bottom by the speakers and it's not bad at all just noticeable because I inspected it like a mad man when I heard the rumors. I can deal with it easily in it's current state as it's not a problem but if it were to become worse I'm not sure what to do. I know the chances being taken by unlocking as I've always done on every device I've had, I've just fortunately never had a defected device so it wasn't a problem.
4_SUXEN said:
When I install a custom rom and get stuck in boot loop. I always do a factory reset and my new rom starts right up. Works every time. I see you solved your problem but maybe next time you try this before you do anything else. Please thank if help
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope that didn't work, I've owned several android devices and did what you just said and it always worked. This is the first time I've owned a non Samsung device in a while (because I used Odin with those) and I couldn't get into recovery at all and factory reset in the bootloader did nothing. Not much experience with fastboot as I've never had to use it but I'm glad I did so I have that in case I need to do it again in the future.
TL;DR; I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
I wanted to share my experience up until this point. And if the physical keyboard doesn't work continue sharing. And perhaps someone else would have a miracle answer.
The story (sorry this is long - hence the TL;DR; at top) :
I had the swipe touch password enabled. My daughter was playing with my phone for some time until it deactivated the swipe-touch password and started asking for a PIN. This is when she handed it to me. My first reaction was "oh no - I don't remember this" But, I gave a few numbers some tries that I thought might work. I failed ... Then I began research on the internet. I saw something about incorrect guesses after 5 times would reveal a way to enter username/password associated with my gmail. So, I failed a couple more times, but never saw this option.
Then I found "Android Device Manager". I thought I was in luck so I quickly checked my google account and found out that I could ring my phone and the option for "Lock" was also available so I quickly locked it ... and my phone updated ... and I tried to unlock it ... and my phone tells me that it was the wrong password. What the what?! I tried again ... and again ... and again ... failing repeatedly. Why doesn't this work? Isn't this feature here to keep unfortunate people like me from getting permanently locked out of my phone or resorting to factory resets? (Ok, sure - this feature is also here to lock out thieves and help find lost phones ... but come on - it should work for this situation too!) Anyhow, at this point, sure, if I had already backed everything up or had Google+ auto-backup installed I would just delete/restore my phone, but I have photos on here that aren't backed up and I don't want to lose. I also found that if I had my phone registered with a Samsung account I could just unlock it ... but alas ... I don't have a Samsung account ... so ...
Somewhere in here I contacted Samsung and they told me they couldn't do anything and to attempt getting help from my provider - inferring that I could verify with Verizon that I am the owner of the phone and they could unlock it. So ... I called Verizon and even went to their physical store location in town and no one was able to help. They all were searching the same web-search results I was finding and suggesting things that I'd already tried. This seems kind of ridiculous to me ... I pay them the money for their services and they don't have a magical machine to help me out with this kind of thing? (Benefit of the doubt - perhaps they don't have a magical machine so that employees at Verizon can't steal phones and strip out the data themselves?) Speaking of magical machines - I did happen upon mobiletechvideos guys and was curious about them ... but I'm trying to do this without paying $30-125 and shipping my phone off if I can avoid it.
So ... I began researching other options ... reading that it is unfortunate that I don't have USB Debugging enabled ... moved on to Heimdall / Odin / JOdin3 - etc (recovery tutorial I found)... I tried flashing my recovery image ... fail ... I compiled my own versions of Heimdall with newer code even because I read that the current release version has some issues ... fail again ... oh, not a Heimdall/Odin problem - it is because of a Verizon lock on bootloader(?) ... and/or b/c I never rooted my phone(?) ... So I began researching more ... it looks like having a Verizon version of this phone makes it even more difficult. So I stopped trying this recovery image flash option and pondered what else I could try.
Then, I had an epiphany "why can't I just restore to factory and THEN use some kind of file recovery program?" BAM! How about that - there's tons of these recovery programs on the internet. BUT, I didn't want to do this to my own phone in case it failed. So, luckily, my wife has the same phone. I backed up all her data, delete/reset to factory defaults, 7 taps to the build number activating dev mode and then activating USB Debug mode, and then tried a number of these recovery programs. NONE of them succeeded. They all appear to have trouble finding and connecting to the phone. Myjad seems to get the farthest in that it appears connected to the phone, but then tells me "activate USB Debugging" and then tells me I don't have it active, but I do! Why isn't it working? Do these recovery programs only work on rooted devices? MTP/PTP don't work? Or perhaps our Android versions are too new? So I'm still stuck on these questions for this ...
This is where I am with this. I just read that perhaps I have to type the Android Device Manager password in with an external keyboard for the Android Device Manager password to work. I'm going to try that.
If that doesn't work I think I'm going to start researching a method that involves rooting the phone without delete/reset? Then perhaps I can try a recovery img flash, but I don't think this is looking promising given the Verizon lock on bootloader? So then I might try the root/delete/reset + recovery program ... perhaps a recovery program will be more flexible on a rooted phone? But, considering I have not rooted before, if this is where I end up with this - I will be asking questions about how to go about that - because it looks like it is particularly tricky with this Verizon S4 ...
If you made it this far - thanks for reading! And thanks in advance if you have some ideas.
TL;DR; (copied from top) I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
roboshawn said:
TL;DR; I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
I wanted to share my experience up until this point. And if the physical keyboard doesn't work continue sharing. And perhaps someone else would have a miracle answer.
The story (sorry this is long - hence the TL;DR; at top) :
I had the swipe touch password enabled. My daughter was playing with my phone for some time until it deactivated the swipe-touch password and started asking for a PIN. This is when she handed it to me. My first reaction was "oh no - I don't remember this" But, I gave a few numbers some tries that I thought might work. I failed ... Then I began research on the internet. I saw something about incorrect guesses after 5 times would reveal a way to enter username/password associated with my gmail. So, I failed a couple more times, but never saw this option.
Then I found "Android Device Manager". I thought I was in luck so I quickly checked my google account and found out that I could ring my phone and the option for "Lock" was also available so I quickly locked it ... and my phone updated ... and I tried to unlock it ... and my phone tells me that it was the wrong password. What the what?! I tried again ... and again ... and again ... failing repeatedly. Why doesn't this work? Isn't this feature here to keep unfortunate people like me from getting permanently locked out of my phone or resorting to factory resets? (Ok, sure - this feature is also here to lock out thieves and help find lost phones ... but come on - it should work for this situation too!) Anyhow, at this point, sure, if I had already backed everything up or had Google+ auto-backup installed I would just delete/restore my phone, but I have photos on here that aren't backed up and I don't want to lose. I also found that if I had my phone registered with a Samsung account I could just unlock it ... but alas ... I don't have a Samsung account ... so ...
Somewhere in here I contacted Samsung and they told me they couldn't do anything and to attempt getting help from my provider - inferring that I could verify with Verizon that I am the owner of the phone and they could unlock it. So ... I called Verizon and even went to their physical store location in town and no one was able to help. They all were searching the same web-search results I was finding and suggesting things that I'd already tried. This seems kind of ridiculous to me ... I pay them the money for their services and they don't have a magical machine to help me out with this kind of thing? (Benefit of the doubt - perhaps they don't have a magical machine so that employees at Verizon can't steal phones and strip out the data themselves?) Speaking of magical machines - I did happen upon mobiletechvideos guys and was curious about them ... but I'm trying to do this without paying $30-125 and shipping my phone off if I can avoid it.
So ... I began researching other options ... reading that it is unfortunate that I don't have USB Debugging enabled ... moved on to Heimdall / Odin / JOdin3 - etc (recovery tutorial I found)... I tried flashing my recovery image ... fail ... I compiled my own versions of Heimdall with newer code even because I read that the current release version has some issues ... fail again ... oh, not a Heimdall/Odin problem - it is because of a Verizon lock on bootloader(?) ... and/or b/c I never rooted my phone(?) ... So I began researching more ... it looks like having a Verizon version of this phone makes it even more difficult. So I stopped trying this recovery image flash option and pondered what else I could try.
Then, I had an epiphany "why can't I just restore to factory and THEN use some kind of file recovery program?" BAM! How about that - there's tons of these recovery programs on the internet. BUT, I didn't want to do this to my own phone in case it failed. So, luckily, my wife has the same phone. I backed up all her data, delete/reset to factory defaults, 7 taps to the build number activating dev mode and then activating USB Debug mode, and then tried a number of these recovery programs. NONE of them succeeded. They all appear to have trouble finding and connecting to the phone. Myjad seems to get the farthest in that it appears connected to the phone, but then tells me "activate USB Debugging" and then tells me I don't have it active, but I do! Why isn't it working? Do these recovery programs only work on rooted devices? MTP/PTP don't work? Or perhaps our Android versions are too new? So I'm still stuck on these questions for this ...
This is where I am with this. I just read that perhaps I have to type the Android Device Manager password in with an external keyboard for the Android Device Manager password to work. I'm going to try that.
If that doesn't work I think I'm going to start researching a method that involves rooting the phone without delete/reset? Then perhaps I can try a recovery img flash, but I don't think this is looking promising given the Verizon lock on bootloader? So then I might try the root/delete/reset + recovery program ... perhaps a recovery program will be more flexible on a rooted phone? But, considering I have not rooted before, if this is where I end up with this - I will be asking questions about how to go about that - because it looks like it is particularly tricky with this Verizon S4 ...
If you made it this far - thanks for reading! And thanks in advance if you have some ideas.
TL;DR; (copied from top) I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
Click to expand...
Click to collapse
What do you have on your phone that you are worried about deleting? If it's contacts that should be saved with your google account. If it's pictures, you should keep dropbox installed so it always backs up your pictures. Now here's how to save your phone. Factory reset it. That's your only option.
You ask
i7vSa7vi7y said:
What do you have on your phone that you are worried about deleting? ... If it's pictures, you should keep dropbox installed so it always backs up your pictures. ...
Click to expand...
Click to collapse
I originally stated
roboshawn said:
Anyhow, at this point, sure, if I had already backed everything up or had Google+ auto-backup installed I would just delete/restore my phone, but I have photos on here that aren't backed up and I don't want to lose.
Click to expand...
Click to collapse
So yes, I understand the problem and what I could have done, but harping on that doesn't help me recover the photos.
But enough of that - it is done. So what next?
I tried the physical keyboard connected and it had no difference. I even reset the lock with Android Device Manager in the web browser and then disconnected that keyboard from the computer and used it on my phone. No luck.
The fact that this phone does not properly work with Android Device Manager is infuriating because it really should! And what's happened to me really shouldn't be a problem.
So yes - the next option appears to be to reset to factory. BUT. It still seems like there may be a way to save these photos with a recovery software if I am able to root the phone immediately following the reset. If it doesn't work then I'll just have lost those photos.
roboshawn said:
You ask
I originally stated
So yes, I understand the problem and what I could have done, but harping on that doesn't help me recover the photos.
But enough of that - it is done. So what next?
I tried the physical keyboard connected and it had no difference. I even reset the lock with Android Device Manager in the web browser and then disconnected that keyboard from the computer and used it on my phone. No luck.
The fact that this phone does not properly work with Android Device Manager is infuriating because it really should! And what's happened to me really shouldn't be a problem.
So yes - the next option appears to be to reset to factory. BUT. It still seems like there may be a way to save these photos with a recovery software if I am able to root the phone immediately following the reset. If it doesn't work then I'll just have lost those photos.
Click to expand...
Click to collapse
Well looks like the only thing you can do is not repeat the same mistake. Factory reset your phone set it up and get dropbox or google drive also root your phone and have usb debugging.
roboshawn said:
So yes - the next option appears to be to reset to factory. BUT. It still seems like there may be a way to save these photos with a recovery software if I am able to root the phone immediately following the reset. If it doesn't work then I'll just have lost those photos.
Click to expand...
Click to collapse
Ok. This is how it went.
I reset to factory defaults.
I enabled USB Debugging.
I rooted my phone using the guide over here How to root i545vrufnk1.
I tried various recovery photo/file programs such as Myjad, Yodot, Tenorshare, etc. These programs advertise that they can restore photos after a factory reset. None of them found my old photos. I didn't pay for any of these - I was just using their trial versions. If anyone has used one of these or something like it and had it succeed after a factory reset - please let me know.
I set up Google+ backup.
Next step I'll probably take as additional precaution is to setup the Samsung account service.
To reiterate - this is utterly frustrating that the Android Device Manager remote lock solution does not work for these phones - it goes so far as to tease you with the functionality, but essentially permanently lock your phone.
For anyone else looking to solve this problem - you may or may not have success depending on if you have a samsung account or usb debugging already on or a phone that is not exactly an I545, check out these links:
[RESOLVED] HELP please!! Unable to unlock device locked by Google Device Manager
How to Recover Photos and Data From a Keylocked Android Phone
Samsung Account
Good luck and fix your stuff - Samsung and Google!!!
If you reboot to recovery you should be able to use adb to pull files even without debugging turned on is the OS?
I'm having the exact same problem on my nexus 10 did you ever solve it? Seems really stupid that the adm lock function is so broken
I just had the same problem with a Samsung Galaxy S5. I solved the problem and unlocked my phone. Suggest the following if you locked your phone with a lock pattern:
1) Try the wrong pattern 5 times
2) You will see a message asking if you," Forgot Password"
3) Tap that message and you will be presented with a screen requesting your email and password.
4) Use your Google credentials and you will be able to unlock your phone.
Good luck!
change the lock pattern from settings
Go to settings>security and change your home lock screen.This worked for me.
ADM - Blessing and a curse?
Ok so yesterday my wife's phone was stolen out of a car. First we had AT&T shut down the services. According to the history, the attacker actually tried to access Paypal, and tried for a couple of minutes and gave up when he didn't get anywhere. He sent a password reset, that didn't go through. Then I found the ADM and turned on the Lock-screen with a message to call me. According to those who found the phone, the attacker apparently threw the phone underneath a car in a parking lot. The ADM-lock screen allowed them to call me... "Thank you 'Google!'"
Now to the bad news: I cannot get it to 'UNLOCK!'. No password I put in works. And when I attempt to reset the lock I get: "Since Google has verified that a screen lock is already set, the password you entered won't be needed". I guessing this means that it won't alter the password or it can't. Many people all over the internet have come up with all sorts of ideas for this. But I don't see anything 'satisfactory'. Besides just a complete 'reset'. So I really have killed the phone I just recovered? Meaning the ADM is also a 'Curse'? With sarcasm: "Thank you 'Google!'"
This is a Samsung Galaxy S4 Active SGH-I537. I've already attempted to hook up an USB cable, I see nothing. I'm pretty sure that USB debugging is not enabled.
I can enter the password 15-20 times, it never offers me for a 'forget password'. It sometimes says that I need to wait 30 seconds. It keeps tract of how many so-called bad attempts.
PS: I got it... After 30 guesses. The first password apparently stuck. Apparently I wasn't thinking too much, and I put in 'dude'. LOL. And it is now unlocked.
You are living my Exact Story!!
I have a Galaxy S4, and I had a pattern lock on my screen. I also have a 2-year-old, who unfortunately got ahold of my phone and locked it out. It's asking me for the backup Pin- which I've entered over and over, but it keeps saying it's incorrect. Now I have one try left before a factory reset Please help!! I don't want to loose all my memories of the precious (however difficult) daughter
It's also started having a white pop up box that says "Unfortunately, phone has stopped." Then asks me to click ok- it goes away for 5 seconds then pops back up again.
I have already contacted Verizon both over phone and went into the store. Both told me they could not help.. also already went to the Android Device Manager and tried to lock it so I could at least call my husband- I put in the Call Owner thing...
SO FRUSTRATING!!!! Anyway- still don't know what to do..... But just couldn't help but reply when I read your story- It was serious deja vu!!!!!
roboshawn said:
TL;DR; I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
I wanted to share my experience up until this point. And if the physical keyboard doesn't work continue sharing. And perhaps someone else would have a miracle answer.
The story (sorry this is long - hence the TL;DR; at top) :
I had the swipe touch password enabled. My daughter was playing with my phone for some time until it deactivated the swipe-touch password and started asking for a PIN. This is when she handed it to me. My first reaction was "oh no - I don't remember this" But, I gave a few numbers some tries that I thought might work. I failed ... Then I began research on the internet. I saw something about incorrect guesses after 5 times would reveal a way to enter username/password associated with my gmail. So, I failed a couple more times, but never saw this option.
Then I found "Android Device Manager". I thought I was in luck so I quickly checked my google account and found out that I could ring my phone and the option for "Lock" was also available so I quickly locked it ... and my phone updated ... and I tried to unlock it ... and my phone tells me that it was the wrong password. What the what?! I tried again ... and again ... and again ... failing repeatedly. Why doesn't this work? Isn't this feature here to keep unfortunate people like me from getting permanently locked out of my phone or resorting to factory resets? (Ok, sure - this feature is also here to lock out thieves and help find lost phones ... but come on - it should work for this situation too!) Anyhow, at this point, sure, if I had already backed everything up or had Google+ auto-backup installed I would just delete/restore my phone, but I have photos on here that aren't backed up and I don't want to lose. I also found that if I had my phone registered with a Samsung account I could just unlock it ... but alas ... I don't have a Samsung account ... so ...
Somewhere in here I contacted Samsung and they told me they couldn't do anything and to attempt getting help from my provider - inferring that I could verify with Verizon that I am the owner of the phone and they could unlock it. So ... I called Verizon and even went to their physical store location in town and no one was able to help. They all were searching the same web-search results I was finding and suggesting things that I'd already tried. This seems kind of ridiculous to me ... I pay them the money for their services and they don't have a magical machine to help me out with this kind of thing? (Benefit of the doubt - perhaps they don't have a magical machine so that employees at Verizon can't steal phones and strip out the data themselves?) Speaking of magical machines - I did happen upon mobiletechvideos guys and was curious about them ... but I'm trying to do this without paying $30-125 and shipping my phone off if I can avoid it.
So ... I began researching other options ... reading that it is unfortunate that I don't have USB Debugging enabled ... moved on to Heimdall / Odin / JOdin3 - etc (recovery tutorial I found)... I tried flashing my recovery image ... fail ... I compiled my own versions of Heimdall with newer code even because I read that the current release version has some issues ... fail again ... oh, not a Heimdall/Odin problem - it is because of a Verizon lock on bootloader(?) ... and/or b/c I never rooted my phone(?) ... So I began researching more ... it looks like having a Verizon version of this phone makes it even more difficult. So I stopped trying this recovery image flash option and pondered what else I could try.
Then, I had an epiphany "why can't I just restore to factory and THEN use some kind of file recovery program?" BAM! How about that - there's tons of these recovery programs on the internet. BUT, I didn't want to do this to my own phone in case it failed. So, luckily, my wife has the same phone. I backed up all her data, delete/reset to factory defaults, 7 taps to the build number activating dev mode and then activating USB Debug mode, and then tried a number of these recovery programs. NONE of them succeeded. They all appear to have trouble finding and connecting to the phone. Myjad seems to get the farthest in that it appears connected to the phone, but then tells me "activate USB Debugging" and then tells me I don't have it active, but I do! Why isn't it working? Do these recovery programs only work on rooted devices? MTP/PTP don't work? Or perhaps our Android versions are too new? So I'm still stuck on these questions for this ...
This is where I am with this. I just read that perhaps I have to type the Android Device Manager password in with an external keyboard for the Android Device Manager password to work. I'm going to try that.
If that doesn't work I think I'm going to start researching a method that involves rooting the phone without delete/reset? Then perhaps I can try a recovery img flash, but I don't think this is looking promising given the Verizon lock on bootloader? So then I might try the root/delete/reset + recovery program ... perhaps a recovery program will be more flexible on a rooted phone? But, considering I have not rooted before, if this is where I end up with this - I will be asking questions about how to go about that - because it looks like it is particularly tricky with this Verizon S4 ...
If you made it this far - thanks for reading! And thanks in advance if you have some ideas.
TL;DR; (copied from top) I'm locked out of my phone by Android Device Manager and typing the password in that I gave it is not working using the virtual keyboard. I'm going to try a physical keyboard next as per (http://forum.xda-developers.com/showthread.php?t=2767278) ...
Click to expand...
Click to collapse
This might work
KateJuleLynn said:
I have a Galaxy S4, and I had a pattern lock on my screen. I also have a 2-year-old, who unfortunately got ahold of my phone and locked it out. It's asking me for the backup Pin- which I've entered over and over, but it keeps saying it's incorrect. Now I have one try left before a factory reset Please help!! I don't want to loose all my memories of the precious (however difficult) daughter
It's also started having a white pop up box that says "Unfortunately, phone has stopped." Then asks me to click ok- it goes away for 5 seconds then pops back up again.
I have already contacted Verizon both over phone and went into the store. Both told me they could not help.. also already went to the Android Device Manager and tried to lock it so I could at least call my husband- I put in the Call Owner thing...
SO FRUSTRATING!!!! Anyway- still don't know what to do..... But just couldn't help but reply when I read your story- It was serious deja vu!!!!!
Click to expand...
Click to collapse
i too had locked my nubia device through android device manager.
it can be bypassed by rebooting into recovery mode and you need to format /data and /cache.
after this restart your phone through recovery mode it may take 5 to 10 minutes to finally show "android is updating your apps " something like this.
this method worked on my nubia mini and i thing technically it might work on every android phone that is capable of booting into recovery mode.
this method would not delete your photos,music,etc.
only contacts and app data will be gone,i am sure that won't be an issue.
NITLOC1 said:
i too had locked my nubia device through android device manager.
it can be bypassed by rebooting into recovery mode and you need to format /data and /cache.
after this restart your phone through recovery mode it may take 5 to 10 minutes to finally show "android is updating your apps " something like this.
this method worked on my nubia mini and i thing technically it might work on every android phone that is capable of booting into recovery mode.
this method would not delete your photos,music,etc.
only contacts and app data will be gone,i am sure that won't be an issue.
Click to expand...
Click to collapse
This method WILL delete all data that is on the device! This will only not happen if your using a custom recovery solution!
Please be careful when giving advice.
If you log into the Android device manager website, it will assist you in unlocking your device. You can set up a password to bypass the pin lock, and make sure you don't lose your data
Sent from my SCH-I545 using Tapatalk
Can you just not flash system... I know there is a nc5 emergency no wipe for odin.. should be one for other firmwares, no?
Samsung SM-T531 Google locked
Hi All
Customer came in with a tablet that was stolen, google locked by her, but later recovered.
In short, this is where i'm at. ADM with her login details, unable to remotely unlock.
When blocking she used a password and device is asking for a PIN instead.
Device wont boot into recovery mode to factory reset.
Cant access device to connect to a network..
I cant think of another way around this.. ANYBODY, PLEASE HELP?
Android Device Manager Samsung Resolution
I read this in another forum, can't remember exactly where but if its your Samsung device use the find my Samsung app. Lock you phone then it may take a minute but the Samsung proprietary app will take over and lock your device. This will allow you entry into the device. Set the screen time out for 30 min then backup your device. This worked my Samsung Galaxy Note 3.
My phone did not originally have a lock screen until i used the Android Device Manager. Each time I entered the password it was incorrect. I wasn't presented with an option to enter my email after 5 attempts either. After completing this procedure the option to remove the lock screen was still unavailable as I didn't know the password that was set. I was able to backup my device and reset.
Hope this helps
how can you able to unlock when it is locked by ADM??
Same thing with my Galaxy S5. Many, many times of password & pin incorrect over 5 days, 8 hours of phone & online with AT&T and Samsung and in-store visits. Finally, I did Findmymobile again. The unlock feature never did show up on the left side, but I right (I think) clicked on the location when it found my phone and unlocked it. I was so surprised that I didn't even realize my home screen was visible for at least a half minute. It's worth a try, 'cause I did the same stuff as all of you have said without any good results.
This worked!
microi said:
I just had the same problem with a Samsung Galaxy S5. I solved the problem and unlocked my phone. Suggest the following if you locked your phone with a lock pattern:
1) Try the wrong pattern 5 times
2) You will see a message asking if you," Forgot Password"
3) Tap that message and you will be presented with a screen requesting your email and password.
4) Use your Google credentials and you will be able to unlock your phone.
Good luck!
Click to expand...
Click to collapse
I left my device at a Starbucks and didn't realize until I got home. I went into my Google account to change password and found I could locate my locate and lock it so I did. It located the device exactly where I left it - at Stuckbucks. So, I went back in the morning to recover it...with a locked home screen with my message on it. Unable to unlock directly on the device. I went back home to research this on my desktop. Google Account doesn't have unlock device feature so I used the search engine and found this forum. I followed the instructions and bingo, my device is now unlocked! I was about ready to get a new device!
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Pyrolectic13 said:
Hi hello
So here’s a head scratcher I hope someone can help me with that won’t involve replacing my main board.
Got myself the p20 lite (ANE-LX1 C432) - Single Sim.
I unlocked the bootloader with Huawei just before they stopped handing out the codes. All was good and happy with the world.
Rooted with Magisk and Was busy messing around With Termux, Linux deploy, Mobile Terminal and some pretty basic stuff. I’ve been out of the android scene for a while so was getting reacquainted with the scene.
Anyway. I was messing around in the terminal in a root shell just fixing basic permissions after messing up my termux environment as root. Phone randomly rebooted (I must’ve messed with the wrong folder -no idea which) came back on and my IMEI and baseband were gone.
No worries, I thought. Happened tonnes of times with my previous Devices (looking at you Samsung) just a quick restore or flash and all will be happy again.
Yeah, not quite.
Note that up until this point I hadn’t touched the system partition (probably besides the mobile terminal mishap -no idea)
So over the last week or so I have tried everything. Restore from Twrp backup. Flashed stock through fastboot, through erecovery. Those flashed ok but didn’t fix it.
Putting numerous different update.app FULL & OTA updates in dload folder on SD and internal all failed. Only used my builds version of course and only ones firmware finder deemed compatible/available
Then I got desperate (read: stupid) Decided to take the unpacked firmware files and flash whichever ones twrp would let me. First tried just the modem files. Didn’t help. Then just went through the list and flashed all I could.
I think the kicker came in when I installed the Trustfirmware.img because once I did that I rebooted and now I was stuck in an endless boot loop. No way to get into recovery. Not with their ton combo nor adb/fastboot.
I still had access to fastboot at this point at least and started doing every single thing suggested all over the net just trying to get back to stock.
Tried the unbrick option on The Huawei Multi-Tool. Flashed ok. Phone still wouldn’t boot. Did it a few times with 3 approved versions. Nothing. Only access to fastboot otherwise I was in a boot loop with error mode error no 15 and the verification failure (Attached below)
Last thing I tried after reading online was to relock my boot loader and flash stock. So I locked it with Huawei Multi-Tool. Reboot......
Now I don’t even have access to fastboot. My PC’s (windows and Linux) don’t even acknowledge it and holding volume down in all the weird and wonderful ways and times does nothing. All I get is startup Huawei Logo, Error Mode as per pic Below and then reboot. That’s it.
I’m assuming it’s trying to do a factory reset after relocking the bootloader (if it even locked properly, can’t check) but it can’t get into recovery/erecovery. I dunno ?
That’s my essay of where I’m at. Warranty is already void so not an option and I don’t want to buy a new mainboard (may as well buy a new phone).
So here I am. Is this my life now or does anyone have any magic tricks to possibly suggest?
Click to expand...
Click to collapse
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
kilroystyx said:
Check the second post in this thread:
https://forum.xda-developers.com/honor-7x/help/help-stuck-error-mode-screen-t3735067
Click to expand...
Click to collapse
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Pyrolectic13 said:
Thanks for this.
The battery discharged fully about two days ago.
I haven’t tried plugging it in and out as/if it turns on immediately (though even though it shows dead without charger it still comes on immediately).
I’m gonna get a weaker lower amp charger and see if that maybe helps. Fml ?
***UPDATE***
Been at it for hours. Battery is completely flat. But h second I plug it in the the Black Huawei logo comes up ten a few seconds later it’s on the same error screen for a little longer then boot loops like that constantly.
The error isn’t the same as the post in that link though. And I am FRP unlocked.
Eh.
Click to expand...
Click to collapse
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
kilroystyx said:
I guess your previous error was related to ramdisk...
Now what is your current situation?
-What error is showed in the Error mode?
-Can you reach FASTBOOT&RESCUE MODE menu?
-What is your current recovery?
Click to expand...
Click to collapse
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
As it stands I cannot enter fastboot or recovery mode. Update from SD also doesn’t do anything. Battery is completely discharged. And if I leave it on the charger it doesn’t charge, only boot loops.
So with all that the ONLY thing this phone does now is:
- Starts up Showing Huawei logo
- Error Mode Screen with Func No: 15 (bl31 image) & Error No: 1 (security verify failed)
- Reboots
Ths happens whether it’s plugged into the pc’s usb or the charger. Tried all combinations of buttons too.
It has stock recovery as I flashed that back when trying to revert back to stock.
I lost access to fastboot after I locked the bootlaoder again using the Huawei Multi Tool. It’s like it trying to do the factory wipe that it usually would after locking/unlocking the bootloader but is unable to due to the error mode screen.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
kilroystyx said:
I see, it is really bad
My last hope is to be able to do a forced Firmware upgrade. Press power button and VOL + and VOL- simultaneously. Do you see the same as the attached image?
Click to expand...
Click to collapse
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Pyrolectic13 said:
Ah man, I wish it would even do that. It makes no attempt to even pretend to see the sd card update. If I hold all the buttons in it still only comes up with the error mode and reboots.
I popped it open and connected a charger up battery to see if that would help but it doesn’t.
Do you maybe know the pin layout on the inside or know where I could get schematics? Been looking everywhere.
I’m almost done building my own Jtag box and am hoping to bring it back to life by writing straight to the damn thing.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
kilroystyx said:
That is sad!!!
With JTAG and schematics stuff I cannot help you.
What I found recently and it was new for me (I didn't tested yet) is a possibility to install firmware via "dload" folder, but to start installation the stock recovery have to be full functional.
If I found something interesting for you I'll post here.
Click to expand...
Click to collapse
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Pyrolectic13 said:
To my knowledge the recovery is installed. Well erecovery. It was working up until I locked the bootloader again and it went into a boot loop instead of doing the factory reset.
Is there any other way to force sd update other than with the dload folder?
Thanks for tying to help, I appreciate it.
Click to expand...
Click to collapse
You can check the official documentation about that.
Please let us know how you solved this problem.
kumarsid7 said:
Please let us know how you solved this problem.
Click to expand...
Click to collapse
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
Sent from my iPhone using Tapatalk
in first picture youle see many circles golden 2 smallest is testpoint good luck
Pyrolectic13 said:
Still unsolved as of yet.
I’ve finished building my own version of the Riff/Octoplus box as well as a makeshift Jtag. I’m still trying to find and piece together some firmware files and other board software I think I need.
Also, if anyone has any idea where the test point is on this board I’d really appreciate you pointing it out. I cannot find the schematics or any solid documentation anywhere.
I will attach the pics I have of both sides of the board as soon as I get home.
View attachment 4579956
View attachment 4579957
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
in first picture youle see many circles golden 2 smallest is testpoint good luck
well, try to restore your device using dload method. It needs you to copy the UPDATE.APP in dload folder of an external sd card(formated in NTFS format) and then just press both vol up+down along with power button for a few seconds. It will auto launch huawei e-recovery and will try to flash the UPDATE.APP you stored in ext sd card. This should definitely work.
Dload method doesn't need you to unlock your device or bootloader.
Maybe?
I know it’s a long shot but I still have this phone. If anyone maybe knows if there’s been a way to fix this as of yet please let me know. ?
Lol. Still got this damn thing. Been searching around and seen a few people reporting similar errors. Never find out if they ever solve it though.
So. Anyone maybe have any knowledge to share? Anything at all.
I don't know if you still have your device, but I had the exact same issue with a P10 (VTR-L09)
I was able to fix fastboot using https://github.com/mashed-potatoes/PotatoNV
That tool was designed to unlock the bootloader, but I noticed that It actually flashes a slightly modified version of fastboot.
PotatoNV can also unlock P20 lite bootloader, so you should give it a shot.
Good luck!
If it works, you should be able to flash stock recovery image and then restore the system using the dload folder.
you can Repair it with Software Testpoint and Full Bootloader Unlock ,and then flash a Board Software via Software Testpoint, that helps 100%!!!
use this Firmware Download ANE-LX1
use the Software with logins and you have all what you need.
you must start the Software Testpoint so!!
VIDEO : how to start Software Testpoint P20 Lite
than in Software Testpoint you flash the included Board Software with DC-Phoenix and after that use the included dload update via sdcard and eRecovery mode and your Phone is running!!!
I would unlock the bootloader via Software Testpoint with DC-Phoenix, then the FBLock is unlocked and you can flash as you wish!!!! And the great thing about it is that you don't need an UnlockKey either, you can then read this with HCU client software, the only thing that's stupid is that you need a time-based license for the two programs, which you have to buy.
HCU client download
https://hcu-client.com
DC Phoenix download
https://forum.dc-unlocker.com/forum/modems-and-phones/huawei/155916-dc-phoenix
Since I accidentally bought a 3-day license twice and my P20 Lite is now completely rooted on Lineage 19.1, I can give away 2 access data, which are still valid for 2 days.
you can edit your smartphone with it.
username : bl26457
password : kKncnkMj
username : bl26390
password : JDAZqnkN
Then I wish you a lot of fun with it, hope it helps you if someone else is active in this thread.
Information available:
Boost site: https://www.boostmobile.com/phones/coolpad-legacy.html
Manufacturer details: https://coolpad.us/legacy-boost/
Youtube video I made: https://www.youtube.com/watch?v=wylMivqymUM
This phone was purchased from Walmart and obviously they are no help. Went to a Boost Mobile and a Verizon store and neither one could do anything either (BTW huge props to Verizon on their customer service). I need to know how to clear this phone of all prior information (which is seems that a factory reset from within the OS does not do) and also how to get into the bootloader. Normal physical button methods like power+volume down or up or all 3 just make it say "official" on the screen and then it boots anyway. How do I hack this thing? I've gotten into literally hundreds of Android phones that were bricked and this is the first time I have had this new problem and I don't know where the blame lies. Even if there is a halfway legit custom ROM I could put on the thing, I don't know, I've tried everything I can think of. Can anyone help?
Thank you in advance!
adrenatek said:
Information available:
Boost site: https://www.boostmobile.com/phones/coolpad-legacy.html
Manufacturer details: https://coolpad.us/legacy-boost/
Youtube video I made: https://www.youtube.com/watch?v=wylMivqymUM
This phone was purchased from Walmart and obviously they are no help. Went to a Boost Mobile and a Verizon store and neither one could do anything either (BTW huge props to Verizon on their customer service). I need to know how to clear this phone of all prior information (which is seems that a factory reset from within the OS does not do) and also how to get into the bootloader. Normal physical button methods like power+volume down or up or all 3 just make it say "official" on the screen and then it boots anyway. How do I hack this thing? I've gotten into literally hundreds of Android phones that were bricked and this is the first time I have had this new problem and I don't know where the blame lies. Even if there is a halfway legit custom ROM I could put on the thing, I don't know, I've tried everything I can think of. Can anyone help?
Thank you in advance!
Click to expand...
Click to collapse
You can get to fastboot via adb. I can't get the bootloader to unlock tho.
@adrenatek, I know this is a belated reply, but I just got one of these devices myself and wanted to chime in. Let me see if I understand correctly: are you stating that, after performing a factory data reset, your userdata remains intact on your device? Or, did you get it figured out by now? Also, as to fastboot mode, adb reboot bootloader will get you there, but this device is not supported for OEM unlocking.
can anyone tell me if i can unlock the BL of C3505L..
Is there a current, standalone method for bypassing google account protection or factory reset protection on the Samsung Galaxy A02 USA Variant?
Recently purchased from a buy sell trade group claiming fully unlocked and factory reset, ready to go. Absolutely FRP locked.
As irritating as this is, I currently do not have access to a PC and am hoping to utilize a method on the device alone to bypass.
Update, I have tried using a PC along with multiple "premium unlock options" as well as ADB and FastBoot commands. Nothing seems to work with this device. I've put it into fastboot mode successfully, but none of the normal fastboot commands work to remove frp. This is why you don't buy used phones online.
DrRoxxo said:
Update, I have tried using a PC along with multiple "premium unlock options" as well as ADB and FastBoot commands. Nothing seems to work with this device. I've put it into fastboot mode successfully, but none of the normal fastboot commands work to remove frp. This is why you don't buy used phones online.
Click to expand...
Click to collapse
You can find remote FRP unlocking solutions on Ebay (runs about 20 bucks). Basically you hook up the phone to your pc and run a USB redirector software, then a tech on the other hand uses the official Samsung server to calculate the FRP key for any Samsung model and firmware version. It worked for me a number of times.
Pm me and ill send you the firmware I used
i sure could that firm ware tried everything to bypass frp can you help im using odin firm ware is A025USQS1BVA3
Use android 10 build date 20210626133126 samfw use patched odin
Tyrone M said:
i sure could that firm ware tried everything to bypass frp can you help im using odin firm ware is A025USQS1BVA3
Click to expand...
Click to collapse
Use android 10 build date 20210626133126 samfw use patched odin 3.14.1
I am exhausted but I believe it was this one. https://samfw.com/firmware/SM-A025U/TMK/A025USQS1AUE3
jayvee1 said:
Use android 10 build date 20210626133126 samfw use patched odin
Use android 10 build date 20210626133126 samfw use patched odin 3.14.1
Click to expand...
Click to collapse
TKXS
My pleasure, I hoped it helped. Let us know your progress
At the end of my wits, i am reaching out to the great minds for aid with frp removal.
i have a samsung a02s sm-124d. At this point i have tried dozens of methods with and without pc, tool, and more. This phone does not do alliance knox, not the emergency call, and i cant really find anything that doesnt lump it over to 124dl, which it is not and im afraid would brick it.
Only thing i havent tried is with another samsung but that isnt an option atm. i have os launcher 14 on it, access to most apps and galaxy store. major settings are still locked. Any idea what would be best route?
Thanks for taking time to hear me out.
Harm
HarmoneY said:
At the end of my wits, i am reaching out to the great minds for aid with frp removal.
i have a samsung a02s sm-124d. At this point i have tried dozens of methods with and without pc, tool, and more. This phone does not do alliance knox, not the emergency call, and i cant really find anything that doesnt lump it over to 124dl, which it is not and im afraid would brick it.
Only thing i havent tried is with another samsung but that isnt an option atm. i have os launcher 14 on it, access to most apps and galaxy store. major settings are still locked. Any idea what would be best route?
Thanks for taking time to hear me out.
Harm
Click to expand...
Click to collapse
What version of android are you on? I got to settings from add to home screen on one phone and from google news feed on another.
jayvee1 said:
What version of android are you on? I got to settings from add to home screen on one phone and from google news feed on another.
Click to expand...
Click to collapse
its android 11. i can get into settings with os14 and have hidden settings installed, but it wont let me into apps, change my lock screen, and anything google checks and wants me to put in pass or previous account. i was able to indirectly sign into chrome through google, but it doesn't go into the phone.
thought maybe if i was signed in to chrome and tried to link samsung account with it; but it still wants me to sign into google.
HarmoneY said:
its android 11. i can get into settings with os14 and have hidden settings installed, but it wont let me into apps, change my lock screen, and anything google checks and wants me to put in pass or previous account. i was able to indirectly sign into chrome through google, but it doesn't go into the phone.
thought maybe if i was signed in to chrome and tried to link samsung account with it; but it still wants me to sign into google.
Click to expand...
Click to collapse
Try "add to home screen" from chrome. Don't worry about bricking the phone. It's really hard to permanently break a phone. Almost always you can hook a samsung up to odin and start over. The only phones I haven't been able to fix without a new motherboard is a motorola and an Apple.
jayvee1 said:
Try "add to home screen" from chrome. Don't worry about bricking the phone. It's really hard to permanently break a phone. Almost always you can hook a samsung up to odin and start over. The only phones I haven't been able to fix without a new motherboard is a motorola and an Apple.
Click to expand...
Click to collapse
ill give it a try. *edit* looked everywhere. can ya fill me in on that?
currently it will quite often bring up my os right after it showing the welcome screen. There are references to 124d at a few sites, including samfw, but nothing more. The detailed model info i got off of the imei is correct, but since some programs say 124dl, i figure that would be my next move.
I am planning to brainstorm/plot out a methodology on the darn thing. i figure it might be worth the headache warning for anyone else lol!
Also, my kiddo handed off a samsung to me, and two days later so does my uncle, nice older models with display issues. so i may even figure that out and try some two phone action.
Apologies for the long ramble, And thanks, jayvee1, everyone, y'all have been awesome.
HarmoneY
If you still have this issue dm me, I had it and I was able to get rid of it.. p.s. it will cost you...