Does anybody know whats wrong here??
DruoGaby said:
Does anybody know whats wrong here??
Click to expand...
Click to collapse
what did you do to your device to end up here?
neudof said:
what did you do to your device to end up here?
Click to expand...
Click to collapse
its in bootloader mode...just wanna know why the info is invalid
DruoGaby said:
Does anybody know whats wrong here??
Click to expand...
Click to collapse
Interesting, do you have service at the moment? Just by coincidence, a friend of mines sent me a screenshot with this exact issue just this morning. He said the device had to be exchanged since he wasn't getting any service.
themuffinman said:
Interesting, do you have service at the moment? Just by coincidence, a friend of mines sent me a screenshot with this exact issue just this morning. He said the device had to be exchanged since he wasn't getting any service.
Click to expand...
Click to collapse
everything works fine...nothing is wrong with it once i power up...
DruoGaby said:
everything works fine...nothing is wrong with it once i power up...
Click to expand...
Click to collapse
All my friend did was root and s-off but didn't flash or mod anything else. What all have you done to your device?
I've got the same thing. I'm htc-dev unlocked and running Captain_throwback's stock rooted rom. But when I go into the bootloader I get the same invalid info.
Can't run firewater s-off against it either, just says it isn't supported on my device.
When booted, mine works fine, data / voice / everythings perfect, but just shows the invalid info in the bootloader.
ffttgghh said:
I've got the same thing. I'm htc-dev unlocked and running Captain_throwback's stock rooted rom. But when I go into the bootloader I get the same invalid info.
Can't run firewater s-off against it either, just says it isn't supported on my device.
When booted, mine works fine, data / voice / everythings perfect, but just shows the invalid info in the bootloader.
Click to expand...
Click to collapse
guess we gotta wait...i do see in other bootloaders the date is feb..mines is april
Related
Hi, I was hoping I can get some help with my phone. I'm trying to unlock my boot loader using htcdev but I keep getting this problem after I enter in my device token.
Unlocking Bootloader Failed!
Error Code:173
Error Reason: Check Rule Fail with exception.
Can anyone help me with this? I've unlocked many android phones before (nexus are a lot easier) but my One is giving me issues...
I literally just got this phone lol and I want to unlock it. It has the latest 4.3 update and hboot 1.55
Thanks!
robherley13 said:
Hi, I was hoping I can get some help with my phone. I'm trying to unlock my boot loader using htcdev but I keep getting this problem after I enter in my device token.
Unlocking Bootloader Failed!
Error Code:173
Error Reason: Check Rule Fail with exception.
Can anyone help me with this? I've unlocked many android phones before (nexus are a lot easier) but my One is giving me issues...
I literally just got this phone lol and I want to unlock it. It has the latest 4.3 update and hboot 1.55
Thanks!
Click to expand...
Click to collapse
Me too!! same error i have tried several times today same error
Error Code:173
Error Reason: Check Rule Fail with exception.
PM me your token I'll see if I can get it to work
I have a brand new blue model and the same thing is happening to me, and has all day.....
robherley13 said:
Hi, I was hoping I can get some help with my phone. I'm trying to unlock my boot loader using htcdev but I keep getting this problem after I enter in my device token.
Unlocking Bootloader Failed!
Error Code:173
Error Reason: Check Rule Fail with exception.
Can anyone help me with this? I've unlocked many android phones before (nexus are a lot easier) but my One is giving me issues...
I literally just got this phone lol and I want to unlock it. It has the latest 4.3 update and hboot 1.55
Thanks!
Click to expand...
Click to collapse
are you registered and signed in on htedev.com and are you highlighting it properly if you highlight one row to far it will err, also use a 2.0 usb port not a 3.0, also selecting all other supported devices in selection list
BMP7777 said:
I have a brand new blue model and the same thing is happening to me, and has all day.....
Click to expand...
Click to collapse
Must be HTC Dev then
Aldo101t said:
are you registered and signed in on htedev.com and are you highlighting it properly if you highlight one row to far it will err, also use a 2.0 usb port not a 3.0, also selecting all other supported devices in selection list
Click to expand...
Click to collapse
Yes to all in my case
BMP7777 said:
Yes to all in my case
Click to expand...
Click to collapse
this is weird, i had no idea there are others having this problem, wonder whats going on??
Aldo101t said:
this is weird, i had no idea there are others having this problem, wonder whats going on??
Click to expand...
Click to collapse
Me too same error , signed , i have unlocked tow devices before but not now.
Aldo101t said:
this is weird, i had no idea there are others having this problem, wonder whats going on??
Click to expand...
Click to collapse
I think it's HTC Dev I just tried and it would hang when I clicked submit and got the same error as everyone else.
Maybe they are overwhelmed with all the new Black Friday deals..everyone trying to unlock at the same time
bigdaddy619 said:
I think it's HTC Dev I just tried and it would hang when I clicked submit and got the same error as everyone else.
Maybe they are overwhelmed with all the new Black Friday deals..everyone trying to unlock at the same time
Click to expand...
Click to collapse
yeah that's possible.
Unlocked smoothly and quickly this morning; probably an overworked server yesterday......
unlocked att galaxy s5 saying "SIM not allowed MM#3" how do i fix this and what does that mean
running stock
It's either not unlocked or its blacklisted or ur sim has no service.
Sheon849 said:
It's either not unlocked or its blacklisted or ur sim has no service.
Click to expand...
Click to collapse
thanks figured it out
sanquante said:
thanks figured it out
Click to expand...
Click to collapse
Well, let us know what the problem was! We are all here to learn.
gspears said:
Well, let us know what the problem was! We are all here to learn.
Click to expand...
Click to collapse
just had to flash the PDA.md5 for my phone with odin fixes it
sanquante said:
just had to flash the PDA.md5 for my phone with odin fixes it
Click to expand...
Click to collapse
Where did you find the file? Do you mean you flashed the tar.md5 to the phone and it works? I'm suffering the same issue. Can't get the S5 to work with an ATT Straight Talk sim even though it's an ATT phone, clean IMEI and the ATT card works in an S4.
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
wolfnumba1 said:
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
Click to expand...
Click to collapse
reboot into bootloader mode and flash that way. OTA is the worst way to update, IMO.
mikeprius said:
reboot into bootloader mode and flash that way. OTA is the worst way to update, IMO.
Click to expand...
Click to collapse
I can't flash images with a locked bootloader or is there a way around that?
wolfnumba1 said:
I can't flash images with a locked bootloader or is there a way around that?
Click to expand...
Click to collapse
the OTA wiped your custom recovery and didn't load the ROM properly !??!?!?! Yikes....................if your phone has stock recovery and the bootloader is locked then it is bricked and you need to send it in.
Device was completely stock, including recovery no custom recovery or root or anything.
That's strange....
mikeprius said:
That's strange....
Click to expand...
Click to collapse
Lol I know tell me about it.... I am going to see if motorola will send me a replacement but not to confident they will.
did you have root before taking the ota? anyways, sounds like you have the first N brick.
wolfnumba1 said:
Lol I know tell me about it.... I am going to see if motorola will send me a replacement but not to confident they will.
Click to expand...
Click to collapse
They may....I think the big question is if they still have any in stock......anyways, let us know what happens....that's a very unfortunate situation. The first thing I did when I got my phone was unlock the bootloader and I have not re-locked it since.
simms22 said:
did you have root before taking the ota? anyways, sounds like you have the first N brick.
Click to expand...
Click to collapse
No did not have root, was completely stock.
mikeprius said:
They may....I think the big question is if they still have any in stock......anyways, let us know what happens....that's a very unfortunate situation. The first thing I did when I got my phone was unlock the bootloader and I have not re-locked it since.
Click to expand...
Click to collapse
Yea sucks, device is out of warranty so I am SOL it seems. Lol I don't unlock because it breaks android pay and other security features which I did not want to disable.
wolfnumba1 said:
No did not have root, was completely stock.
Click to expand...
Click to collapse
yea, read. i was going to post when no one else posted, but had a customer walk in. by the time i posted it was too late :angel:
wolfnumba1 said:
Yea sucks, device is out of warranty so I am SOL it seems. Lol I don't unlock because it breaks android pay and other security features which I did not want to disable.
Click to expand...
Click to collapse
This is even more unfortunate. You can use Android Pay with an unlocked bootloader. I've flashed my phone back to stock images with the bootloader unlocked and Android Pay works. It's not contingent on a locked bootloader, only factory stock images.
mikeprius said:
This is even more unfortunate. You can use Android Pay with an unlocked bootloader. I've flashed my phone back to stock images with the bootloader unlocked and Android Pay works. It's not contingent on a locked bootloader, only factory stock images.
Click to expand...
Click to collapse
Oh weird, when you check off the allow oem unlock it says disabled security features, I wonder what that means then... yes it sucks, now a very nice looking paperweight lol
wolfnumba1 said:
Oh weird, when you check off the allow oem unlock it says disabled security features, I wonder what that means then... yes it sucks, now a very nice looking paperweight lol
Click to expand...
Click to collapse
That's just a general warning. No bearing on AP.......well you may be able to sell the phone as some people may buy it. I'm sure someone out there has a way to get it back, but I'm not sure how. I recall seeing a thread where someone in Cambodia did the same thing and he took it to a shop that was able to reverse it.....
mikeprius said:
That's just a general warning. No bearing on AP.......well you may be able to sell the phone as some people may buy it. I'm sure someone out there has a way to get it back, but I'm not sure how. I recall seeing a thread where someone in Cambodia did the same thing and he took it to a shop that was able to reverse it.....
Click to expand...
Click to collapse
Lol really? Recall where?
wolfnumba1 said:
Lol really? Recall where?
Click to expand...
Click to collapse
I can't find the thread, but I did find this one:
http://forum.xda-developers.com/nexus-6/help/nexus-6-bricked-november-security-ota-t3242773
It looks like you are not the first to be bricked with an OTA update. There should be a sticky about this issue moving forward.
mikeprius said:
I can't find the thread, but I did find this one:
http://forum.xda-developers.com/nexus-6/help/nexus-6-bricked-november-security-ota-t3242773
It looks like you are not the first to be bricked with an OTA update. There should be a sticky about this issue moving forward.
Click to expand...
Click to collapse
Lol so ****ty, looks like the phone is ****ed
wolfnumba1 said:
Hey guys,
Not sure if I am going to be able to do anything about this. I signed up for the OTA beta program, device downloaded the OTA. When I got to the flashing stage it went to recovery and failed for some reason. Now I am unable to boot the device just gets stuck at Google splash screen. Cannot OEM unlock in fastboot because it was not enabled in developer options prior so flashing any images is out of the question. Is there any hope for me past this point or is the device bricked?
Click to expand...
Click to collapse
Count me in as one of the potentially many more that bricked his phone while trying out the Beta program via OTA...
sorry to tell you this , but with locked bootloader , your phone is hard bricked, no way to recover, only by sending it back to motorola or amazon if you bought from them. i sold about 100 pieces of nexus 6 to customers and my first advice to them is to check " Enable oem unlocking "
anyway email google and blame them for this and i am sure they will help
Hello guys ! I have a problem. I have an HTC One mini 2 and i can't flash recovery through fastboot. I've unlocked the Bootloader, but when i try to flash TWRP i get an Unkown error...can someone help me in this problem, i don't understand why doesn't work.
Blazer17 said:
Hello guys ! I have a problem. I have an HTC One mini 2 and i can't flash recovery through fastboot. I've unlocked the Bootloader, but when i try to flash TWRP i get an Unkown error...can someone help me in this problem, i don't understand why doesn't work.
Click to expand...
Click to collapse
Can you elaborate it more? What error came up, what command you gave. A screenshot would further help
csoulr666 said:
Can you elaborate it more? What error came up, what command you gave. A screenshot would further help
Click to expand...
Click to collapse
Nevermind...i made it....the problem was my PC...i have some problems with USB Ports...connected to another PC and i made it...
Now i want to know if there is another method to make S-Off, other then Sunshine ?
Blazer17 said:
Nevermind...i made it....the problem was my PC...i have some problems with USB Ports...connected to another PC and i made it...
Now i want to know if there is another method to make S-Off, other then Sunshine ?
Click to expand...
Click to collapse
Currently there is no other way to S-OFF besides Sunshine.
csoulr666 said:
Currently there is no other way to S-OFF besides Sunshine.
Click to expand...
Click to collapse
Then i dont have any chances to remove the Sim Lock without S-Off...right ?
[/COLOR]
Blazer17 said:
Then i dont have any chances to remove the Sim Lock without S-Off...right ?
Click to expand...
Click to collapse
If it is a carrier branded phone, maybe your carrier may allow SIM-unlocking it.
csoulr666 said:
[/COLOR]
If it is a carrier branded phone, maybe your carrier may allow SIM-unlocking it.
Click to expand...
Click to collapse
Yeah...it's from Vodafone....but here in Romania they want money for this... :lol:
I know the Sprint bootloader is locked, but does anyone know if there will be a way to work around this?
I have seen some threads on a trick to unlock the Verizon bootloader even though it also comes locked- would this work for Sprint? Thanks
UPDATE: What is the Pixel version of MSM/ODIN? I know how to get to EDL mode on it, but from there how would you go about flashing a different firmware to potentially get around the bootloader? Anyone know?
Vonsk said:
I know the Sprint bootloader is locked, but does anyone know if there will be a way to work around this?
I have seen some threads on a trick to unlock the Verizon bootloader even though it also comes locked- would this work for Sprint? Thanks
Click to expand...
Click to collapse
Have you got a link for the trick as mine is coming today and it's locked thanks
jaythenut said:
Have you got a link for the trick as mine is coming today and it's locked thanks
Click to expand...
Click to collapse
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Vonsk said:
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Click to expand...
Click to collapse
Nice one I'll try that tonight when my phone comes ?
Got my sprint version yesterday through bestbuy, came locked I booted up with no sim or activating the esim and skipped everything and is still grayed out for me even after factory reset and just signing into wifi... sucks.
joeyddr said:
Got my sprint version yesterday through bestbuy, came locked I booted up with no sim or activating the esim and skipped everything and is still grayed out for me even after factory reset and just signing into wifi... sucks.
Click to expand...
Click to collapse
Why didn't you activate the eSIM option? Went smooth and easy for me on my unlocked Google version.
Sent from my Pixel 4 XL using Tapatalk
EeZeEpEe said:
Why didn't you activate the eSIM option? Went smooth and easy for me on my unlocked Google version.
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Mine is not the unlocked version and I read a few threads saying it isn't grayed out if you don't activate the sim first, but alas it was still locked.
Anyone know if the sprint version is unlocked for other carriers
Vonsk said:
https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
Click to expand...
Click to collapse
Didn't work for me did say success but didn't unlock ?