Well, I have been trying for a while to SIM unlock the sprint HTC One M8 but with no luck. Yesterday I was giving it a try and used the SIM Unlock helper app, but it seems like it screwed up my phone. By mistake I pressed on Lock option, it restarted my device, wiping out all data, and leaving the phone with only a lock scree with a password that I didn't set. I googled and found that someone said it is 1866 but that didn't work. I relocked the bootloader., then tried to perform a factory reset, using the bootloader menu, but it keeps giving me message Security warning.
I tried it using fastboot, but it gives "erasing 'userdata'... FAILED (remote: not allowed)", I tried installing the stock ROM, but it keeps giving me error that battery is less than 30% while it is fully charged with the green led on.
I just want the phone to work now, even if SIM locked, doesn't matter!
Please help
Unlocked bootloader
Alshoabi90 said:
Well, I have been trying for a while to SIM unlock the sprint HTC One M8 but with no luck. Yesterday I was giving it a try and used the SIM Unlock helper app, but it seems like it screwed up my phone. By mistake I pressed on Lock option, it restarted my device, wiping out all data, and leaving the phone with only a lock scree with a password that I didn't set. I googled and found that someone said it is 1866 but that didn't work. I relocked the bootloader., then tried to perform a factory reset, using the bootloader menu, but it keeps giving me message Security warning.
I tried it using fastboot, but it gives "erasing 'userdata'... FAILED (remote: not allowed)", I tried installing the stock ROM, but it keeps giving me error that battery is less than 30% while it is fully charged with the green led on.
I just want the phone to work now, even if SIM locked, doesn't matter!
Please help
Click to expand...
Click to collapse
This is driving me crazy, I unlocked bootloader, factory resetted using winteam recovery project, but password stll there, please help!!!
Have you tried the latest RUU?
Make sure you are using a USB2 port.
Sloth said:
Have you tried the latest RUU?
Make sure you are using a USB2 port.
Click to expand...
Click to collapse
I am using the one I was able to find online and that matches Radio version, I used TWRP to wipe everything, went to wipe, advanced, and selected everything to delete it, now phone has no system, but TWRP is still there, and when every I try excuting the RUU on my laptop, it will tell me phone battery is less than 30%, I tried draining it out last night, and recharge again until phone said 53% and same issue persisted!
Related
Hi guys, hoping one you can help.
I recently had my unlocked/rooted HTC One replaced after it completely died on me. Almost the exact same thing as what happen to this guy http://forum.xda-developers.com/showthread.php?t=2295374
Anyway, I went to unlock/install custom recovery on my new One. Done the unlock process fine, I've always used ClockWorkMod but I decided I'd flash TWRP to try. Files were sent/written ok and everythig seemed fine. But when I try to boot into recovery it shows the "Entering Recovery" screen (with the red warning text at the bottom) for a split second, then it just reboots the phone... So I tried Flashing CWM instead, again process went as normal but still can't boot to recovery. Even flashed the stock recovery and still the same. Tried flashing CWM through Rom Manager, just gives me "An error occurred while flashing your recovery".
It's a 3uk phone and their is no RUU for it yet that I've seen, so I thought if I can get S-Off I can change CID and use a generic European RUU. This when I realised it's not rooted and as I can't get to recovery I can't root it that way. Tried using the "Perm Root" option in the All-In-One kit but that just throws errors back.
Also the TAMPERED doesn't show above UNLOCKED for me in bootloader.
Any ideas? I stumped
Thanks.
Anyone?
saibogu009 said:
Anyone?
Click to expand...
Click to collapse
Try 'fastboot erase cache'
MacHackz said:
Try 'fastboot erase cache'
Click to expand...
Click to collapse
Yeah I had done that, before and after flashing.
Funny thing is this morning after a full charge (wasn't like it was flat last night, had at least 50%) it worked fine, fired up the bootloader and the TAMPERED had appeared and now it loads the recovery perfect... :/ Just rooted it and now I'm off to S-Off and super CID.
Very strange but it's working now so I'm not complaining.
Thanks anyway guys.
Hi I have the Developer edition 64Gb and I have this problem too...
Aparently the TWRP flash went well (I tried both ways, AIl in one kit and fastbbot ways) but I cannot get into recovery.
I erased cache and reflashed again but nope.
Since this phone comes unlocked I assumed that I can just skip those steps of unlocking it (am I correct there?) and went straight into flashing recovery but it does not seem to have worked.
Anybody has a different suggestion?
Thanks,
EDIT:
Never mind, I just waited few hours and tried again and it works
???
Hey guys, I seriously need your help. First off, I have a TMO version of the HTC One, S-On, and Unlocked bootloader, and I was running Android Revolution 31.6 with TRWP 2.6.3.3.
Ok now the good stuff. I went to reboot my phone because a text message wouldn't send. Well, the phone never booted back up properly. It kept booting up into the splash screen, then it would restart, and the process would repeat. IT DID THIS FOR LIKE 4 HOURS. FINALLY after it booted up, it is bringing me to a screen that says I have to enter in my password to decrypt my data. The thing is, I never had a password on my phone that would encrypt the data. Whenever I enter in a password, it doesn't accept it, and it still says that I have 30 more tries before it factory resets my phone.
I was able to boot into recovery, but I couldn't mount any part of my phone, it just says "not found". It completely wiped my phone, there are no roms or anything on it, and I can't transfer a new rom onto the phone either because it can't mount itself. I was able to sideload a rom, so I went to Android Revolution 31.5, and it flashed properly, however when it booted up, it took me right back to that decrypt data screen, with no luck.
I honestly have no idea what to do, and any help that you guys can give me is greatly appreciated. I want to take it into TMO tomorrow too see if they can give me another, since when I boot the phone back up, it doesn't say "unlocked" or "tampered" on the boot screen when it normally should.
Update: getting ADB up and running, my computer is having an issue with recognizing my device while in fastboot mode. I'm going to try and restore to complete stock/relock the bootloader, but I have to get my computer to recognize the phone first, then go through then next processes. Luckily, my phone still has adb debugging enabled, because I was able to get adb to recognize/do some commands on my main computer (which runs windows 8, but it won't recognize the device like I've said, so I'm installing adb/fastboot on an old laptop that has Windows 7)
Fixed it. Was able to relock bootloader and flash to stock. I want to switch to an S4 because I have the purple tint issue, but when booted into bootloader, it shows "relocked" so idk if they'll let me.
oshizzle1991 said:
Fixed it. Was able to relock bootloader and flash to stock. I want to switch to an S4 because I have the purple tint issue, but when booted into bootloader, it shows "relocked" so idk if they'll let me.
Click to expand...
Click to collapse
Hi, do you still know how you went back to stock?
i have the same problems on my phone.
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
chg911225 said:
Good evening, everyone.
Few hours ago, my N6 randomly shut down and not booting up to the system. I tried to re-install the factory image for 5.0.1 but I got stuck at bootloader screen. I tried every options available from bootloader screen(Start, Recovery mode, Restart bootloader etc.) but it performed nothing but coming back to the bootloader screen. When I tried to use 'Nexus Root Toolkit' to install new system and whenever the process was trying to initiate the process, it is giving me same error message 'FAILED <remote failure>'
What can I do from here?
I appreciate your attention.
Click to expand...
Click to collapse
If your bootloader is unlocked, you should be able to either flash the stock factory image, or re-flash each partition separately through the tool-kit. Since you're getting remote errors with the toolkit, double check that you have the right drivers installed, the tookit and a search on the forum should help with that.
did you already try :
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Don't want to raise any alarms already but I shut mine down on Sunday night (Unlocked/ Rooted/ custom kernel & rom) in order to boot in Recovery and flash a new kernel version and:
1) The sdcard looked empty, it read ~ 26 GB free (I had no more than 20 gb free before reboot) and no folders whatsoever.
2) The phone was stuck at the Google logo heating up but going nowhere.
As I said don't want to start assuming things but the phone randomly going "nuts" and losing all data is scary... I had to spent my entire day yesterday flashing stock 5.0.1 back and re-setting up everything. I followed the guide posted above (http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 oh, go with Method 2 and it will work fine).
Out of curiosity how does your SD look like from recovery? Oh, but then you say you can't even boot to Recovery. Which recovery do you have? (I had/have TWRP 2.8.3.1 ). Anyway to repair it you only need to be able to boot into Bootloader properly I guess.
Hello,
I fear my daughters european HTC Desire 510 is bricked. First of all, we have already given up on what is on the phone. So no worries if a solution means wiping EVERYTHING from the phone, as long as we can get it to start again.
For some unknown reason, possibly an update the phone went into an almost constant bootloop a month or so before christmas. It could eventually get to the login screen, after going in circles for anything between 20 mins and hours. So I thought I would try to tamper with it. I know how to get into the bootloader from rooting other phones, so I went there to try to reset the phone to the factory settings. The result was that the phone now wouldn't go there again. If I tried to do a second reset it went straight to boot, without any way to interrupt, same thing when trying to go into recovery, instant reboot in the blink of an eye.
What then happens when the phone reboots? It gets to the first screen, green HTC logo and "Powered by Android", it sits there for maybe 30 seconds, then it goes black, buzz and back to the previous HTC logo. And this goes on until the battery dies, I pull the battery or I quickly push the vol down and power buttons to go into HBOOT.
I usually don't give up this easily. I found another thread here on some european guy having trouble with his Desire 510, and one of the answers linked to a RUU for a european 510. So I thought, why not, I hadn't unlocked the bootloader yet. So I downloaded the RUU and tried to install it. It messed with me a little, aparently as expected, and then ran through the whole installation. Before the upgrade, well downgrade to be specific the OS was ver. 1.51.401.4 but now claims to be 1.51.401.1. Problem though is, absolutely no change in behaviour. I have restarted the phone after pulled the battery and waited for anything between seconds and an hour, and the phone does exactly the same thing. It happily goes into HBOOT but won't allow me to do a factory reset, nor will it allow me to access recovery.
It will allow me to access Fastboot though, so I thought, hmmm if I install ClockWorkMod or TWRP, maybe something will change. Since I'm more used to working with CWM I went down that road, went to htcdev.com, got the unlock code and unlocked the phone. It now says <<< UNLOCKED >>> and I ran the fastboot devices command, that happily returned some "CC4********7 fastboot". So I went ahead and installed CWM, the installation went all the way and in the end it happily stated that CWM was installed. But did that mean any difference, noooo. If I try to access either Recovery, that should start CWM or Factory reset and also Check smartsd, instant reboot. And I mean INSTANT. Fastboot works, as already stated. I can also get into Image CRC and Show barcode, but what good is that.
Any ideas. I'm beginning to think that something is physically broken inside the phone.