Cheers,
Here is my problem. I ran an RUU for my HTC One Sprint and It was successful. It was m7wls_3_04_651_2_RUU. After the phone starts it asks me about about a password that I didn't set up. I tried every method in these forums but without any improvements. However, when I install a rom that isn't SENSE base, it never asks me about any thing.
Tips:
The phone is locked to sprint.
The phone is rooted.
The phone is boot-loader unlocked.
Please help.....
What type of password lock? And what have you tried that didn't work? Also, isn't there a different forum for Sprint devices?
I don't know what type of lock is that. I tried to delete the gesture key although I didn't set up a gesture before and I tried deleting the password from the recovery mode as well. I am sorry I thought this forum was for all problems.
please see the pictures I uploaded.
Related
I just bought a HTC G1 from an ebay user from USA.(I'm from Romania)
I did a hard reset on the phone and now when I put a sim I need to enter the unlock code and can`t turn wireless on if I chose not to enter the unlock code.
Are there any option on how to unlock the phone without the code, or to get past the 'fresh start' screen?
Two things you can do:
1st, contact the user back that sold you the G1. Ask them to obtain the unlock code from T-Mobile (USA) to send to you.
2nd, you can obtain the unlock code yourself by purchasing the unlock code from one of the site.
There are no option to unlock the phone without the unlock code. (as far as I know)
And what about the activation screen? how can i get past it?
Once you get the unlock code and put it in. You can activate your google account with your data plan. You might have to setup your APN setting thou.
Another thing you might or have to do is downgrade and root your phone. Then flash the custom ROM of your choice.
Done unlocking & activating, now it keeps restarting, what can I do? Also the battery lasts 1 day max
// also the screen remains black when I try to unlock (sometimes)
tachemario said:
Done unlocking & activating, now it keeps restarting, what can I do? Also the battery lasts 1 day max
// also the screen remains black when I try to unlock (sometimes)
Click to expand...
Click to collapse
First you want to find out if you are still on stock or you have a custom ROM on your G1.
If you have stock, then you have to root your G1 first.
If you phone has a custom ROM then you G1 has already been rooted. You can load other ROM that you want.
I tried to update to 1.6 but it says error line 1 etc. all the time.
Please help
I`m on stock & when I try to root it says to force close app
Also, i`m running android 1.5 & marketplace is beta & I can`t see all the stuff
Ohh! Boy here we go. You'll need to downgrade to RC29 (since your G1 is from US). Don't worry about the unlock. Once unlocked it stay unlock.
First you want to get ADB setup on your PC and have it setup with your G1.
http://forum.xda-developers.com/showthread.php?t=532719
Once you have that going then you can start with the downgrading to RC29. After you have downgraded, you will have to go through the activation screen again.
Once the activation screen is done, then you can do the rooting process.
http://theunlockr.com/2010/04/26/how-to-root-the-htc-g1dream/
After you have rooted, then you can flash the custom ROM.
Done, the phone is rooted but now I have some other issues with it.
First, my earpiece dosen`t work
Second, my screen sometimes dosen`t come 'back to life' when I try to unlock it
http://www.youtube.com/watch?v=0qk3FIs3Q-s&feature=related
this problem
Can anyone help me?
My friend this morning brought me an lg970 that he just locked by too many attemps. What are the options to at least make a factory reset since the phone doesnt aloud an option to enter recovery console.
Pls be more precise, what did he attempt? SIM-LOCK? PIN code? root attempts? see what I mean? The information given is just to little... If you can still open a dialpad, just type in 3845#*970# and do a factory reset from there.
Nevermind m8, but thanks! It was too many pattern attemps but i already solved that. I used the unbrick method and it worked like a charm. I didnt read the thread before posting that question because i thought it was a way to unbrick. But now i realize that the LG970 does not have something like factory recovery. If something like that happens it needs to be flashed to fix it unless its rooted with CWM installed.
So gentleman its about time i asked for help. I am not a dev but very android savvy, have rooted, recovered, de-bricked 100+ devices and only two hard bricks so far.
So here goes. i got a m8 hk edition brand new, proceeded with custom recovery, unlocked boot-loader, firewater s-off blah blah and next i try to sim unlock. while in programming screen i looked away and my baby boy hit a the screen and chose an unknown option, my phone rebooted, upon boot I was greeted by a phone lock screen please enter password. I never set one. I cannot call but only 911 sometimes can *2 but only for a second. cannot reset after 10 attempts, lock is persistent after flash of new rom and now i really messed up s back on and relocked bootloader. i can unlock bootloader again but since flashed new rom and reset device adb isnt on. have tried everything google got and searched for almost a year to no avail for a solution. PLEASE HELP. I AM NO NOOB. also have tryed the encryption bug fix too and nothing.....REWARD......
Have you tried a RUU? Hit the second link in my sig and read the RUU section. Then go to the thread in the link below and grab the RUU for software version 3.31.654.2 and run it from your computer.
http://forum.xda-developers.com/showthread.php?t=2729173
ruu
I have tried several ruus not sure of versions with fail if i remember right error was something about security or permissions.. also cid was changed at some point, havent worked on phone in a month downloading your link now. I appreciate any and all input on this and would like to hear of any others with this problem. as soon as i get device booted with recovery i will post more information about device specs
jamesdeanwest said:
I have tried several ruus not sure of versions with fail if i remember right error was something about security or permissions.. also cid was changed at some point, havent worked on phone in a month downloading your link now. I appreciate any and all input on this and would like to hear of any others with this problem. as soon as i get device booted with recovery i will post more information about device specs
Click to expand...
Click to collapse
If you changed your CID then you're S-off and there is no need to relock your bootloader. You may need to change your CID back to stock (SPCS_004 in your case) if you continue to get errors while trying to run the RUU, however, I don't believe that will be necessary.
If you're wanting to go back totally stock & S-on, locked bootloader and all, check out the guide in the link below.
http://forum.xda-developers.com/showthread.php?t=2826343
Ruu's flash successfully but device still boots locked. I was s off but returned device back to s on at some point. I can still re-lock and unlock bootloader, but i cannot return to s off because the Device has yet to enable ADB . Since every flash clears all settings after boot the developer settings are not even enabled because im locked out at first boot EVERY time I factory reset or flash a new Rom or ruu.
Please tell me something I havent tried yet. Something im missing? Im thinking about offering a reward to anyone who can help me solve this problem.
In the picture is something I haven't been able to find on than any other Harman Kardon m8. What password? Could it have possibly been a password set with my root anti-theft app AVAST?
If you select emergency call from the screen in the picture, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#
fgr said:
If you select emergency call fe, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#[/QUO
Dialer comes up but the only code it will take is *2
activation menu but only for a second. 25 $ bounty on this issue if anyone has some insight on how to resolve this issue. ANYONE HAVE A JTAG? ILL SEND.MY DEVIVE TO U AND.PAY YOUR FEE?
Click to expand...
Click to collapse
no dialer codes
fgr said:
If you select emergency call fe, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#[/QUO
Dialer comes up but the only code it will take is *2
activation menu but only for a second. 25 $ bounty on this issue if anyone has some insight on how to resolve this issue. ANYONE HAVE A JTAG? ILL SEND my device
TO U AND.PAY YOUR FEE?
Click to expand...
Click to collapse
Have you contacted Sprint?
So I am a developer, making a lockscreen app. Part of the app allows it to set a system lock for double protection. Upon doing this, it set PIN needed for phone to start up. The pin I had set wouldn't work so I entered it in too many times and it wiped my device. The weird thing is, the default password "0" worked in TWRP but NOT to boot Android. Now, after it wiped my device, it boots up to the Android screen, and tells me to enter my PIN again.. It still doesn't work, but tells me in -1 attempts my device will be wiped. How can I just get this all to go away and start again? I have root and TWRP installed. Is there anything I can do?
I can't even boot into Android because it asks for the PIN, even though it already wiped it. I can't use my phone at all.
Flash factory images?
Sent from my Nexus 6 using Tapatalk
Will this mess up TWRP?
DRatJr said:
Will this mess up TWRP?
Click to expand...
Click to collapse
does it matter? it takes 10-15 seconds to flash twrp, or reflash. but anyways i have a feeling that itll ask again, i hope not.
Yea. I would fastboot erase and reflash everything. If bootloader is locked you are hosed.
DRatJr said:
So I am a developer, making a lockscreen app. Part of the app allows it to set a system lock for double protection. Upon doing this, it set PIN needed for phone to start up. The pin I had set wouldn't work so I entered it in too many times and it wiped my device. The weird thing is, the default password "0" worked in TWRP but NOT to boot Android. Now, after it wiped my device, it boots up to the Android screen, and tells me to enter my PIN again.. It still doesn't work, but tells me in -1 attempts my device will be wiped. How can I just get this all to go away and start again? I have root and TWRP installed. Is there anything I can do?
I can't even boot into Android because it asks for the PIN, even though it already wiped it. I can't use my phone at all.
Click to expand...
Click to collapse
Contact the previous owner for his unlocking gesture or code/pin and Gmail account, then factory reset and login with his account and when done delete this accoubt in /settings/accounts/. Then data factory reset again and it should be fixed imo. Or send your phone to the prev. owner so he can do it himself. Look here too http://forum.xda-developers.com/nexus-6/general/guide-properly-prepare-nexus-6-resale-t3104504.
I've had this phone since it came out haha. I haven't stolen it or anything. The problem came because I was solely testing on Samsung devices. Here, I set a backup PASSWORD in case you couldn't unlock your phone. My app was a device admin so it had the ability to set phone lock and lock the phone. What happened was when I tested it on my Nexus, between making the password and setting the password there is the option of "require at boot", which mysteriously, my app automatically selected. Now the issue comes in when I rebooted my phone and Google did NOT let me put a PASSWORD it, but required a PIN. This was an impossible scenario because the android lock screen was set with a PASSWORD, not a PIN.
The even weirder thing was that my app automatically sets the backup android pin to "0" if no backup password is set. When I tried 0 at boot it wouldn't work. BUT when I tried it in TWRP 0 was the only thing that decrypted the phone. I am still not sure why this whole thing happened (Google not letting me put a PASSWORD instead of a PIN if the device is encrypted. My app automatically selecting require PIN at boot, and the backup "0" working in TWRP when it wouldn't work to boot Android).
So @gee2012 I know it may seem like another thread where someone stole a Nexus and wanted to break in to use it. But I assure you I am the only one to ever own this phone. This was just a weird scenario that hopefully won't happen again.
But for the sake of the question:
Flashing factory images worked! Thanks @HolyAngel
DRatJr said:
I've had this phone since it came out haha. I haven't stolen it or anything. The problem came because I was solely testing on Samsung devices. Here, I set a backup PASSWORD in case you couldn't unlock your phone. My app was a device admin so it had the ability to set phone lock and lock the phone. What happened was when I tested it on my Nexus, between making the password and setting the password there is the option of "require at boot", which mysteriously, my app automatically selected. Now the issue comes in when I rebooted my phone and Google did NOT let me put a PASSWORD it, but required a PIN. This was an impossible scenario because the android lock screen was set with a PASSWORD, not a PIN.
The even weirder thing was that my app automatically sets the backup android pin to "0" if no backup password is set. When I tried 0 at boot it wouldn't work. BUT when I tried it in TWRP 0 was the only thing that decrypted the phone. I am still not sure why this whole thing happened (Google not letting me put a PASSWORD instead of a PIN if the device is encrypted. My app automatically selecting require PIN at boot, and the backup "0" working in TWRP when it wouldn't work to boot Android).
So @gee2012 I know it may seem like another thread where someone stole a Nexus and wanted to break in to use it. But I assure you I am the only one to ever own this phone. This was just a weird scenario that hopefully won't happen again.
But for the sake of the question:
Flashing factory images worked! Thanks @HolyAngel
Click to expand...
Click to collapse
Who talked about stolen devices mate, I surely didn`t! I thought that you bought a used Nexus 6 mate, and the previous owner didn`t delete his account :silly:
gee2012 said:
Who talked about stolen devices mate, I surely didn`t! I thought that you bought a used Nexus 6 mate, and the previous owner didn`t delete his account :silly:
Click to expand...
Click to collapse
Oh sorry :/ haha. Wasn't sure if it seemed that way. But nah this has been my baby since unboxing lol
I can no longer seem to be able to install custom roms,ive tried the resurrection remix rom and the cm13 rom but both are asking for a password after it installs and reboot(like when you encrypt the phone) so i cant access anything and my google password does nothing nor have i set another password
All i can do is the three finger recovery and reflash a full stock rom which does work.
I have checked the OEM unlock in developer options as well and full wiped before installing roms.
There shouldnt be any anti theft on the phone because afaik i have disabled all the anti theft options so there should be no reason why it asks for a password.
Does anyone have any idea why this is happening?
Does anyone know if doing a full factory reset through twrp instead of through the phone could be the reason why?
Good to see someone else is also having this ****ing stupid problem. I've been struggling with a way to fix this as well. I'm on the EVA-109 with a single SIM and its been giving me this problem no matter what I do. I read through one of posts on the CM 13 thread which stated you need to use Surdu's tweaked TWRP in order to not have the password booting problem. It'd be nice to get an official response from Surdu on this as he hasn't mentioned the need to use his version of TWRP.
Although, despite trying this I'm still having the password problem at boot but it might be worth a try if you do it. I'll pass you the link - Do let me know how it goes, though I wouldn't place all my faith in this. https://forum.xda-developers.com/p9/development/twrp-t3493979