LG G3 Receives Oversharpening Fix via Modified Kernel

Nothing is perfect, as they say. No matter how alluring or seemingly perfect, … more

APKTool Updated with Android Lollipop Support

One of the beauties of Android is the level of flexibility we have over our devices. Whether … more

Lollipop Leak for Sprint Galaxy S5, TWRP for Micromax Canvas Magnus – XDA TV

Android 5.0 Lollipop has been leaked for the Sprint … more

Velocity is Like OpenTable on Steroids

We all enjoy a night out with friends or our significant other from time to time. However, there is … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Phone won't unlock after **Relocked**

OP itzjonjon69

16th April 2014, 09:29 AM   |  #1  
OP Senior Member
Flag Tempe, AZ
Thanks Meter: 27
 
343 posts
Join Date:Joined: Jan 2009
More
Hey guys i just flashed the 1.54 firmware and in the process i relocked the phone. I flashed the firmware and everything, but now i can't unlock it for some reason. I tried the command to flash the token but no luck it gives me:

C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s

please help!

***and on a side note, whenever i plug the phone into the computer it takes a good 2-3 minutes before it detects the phone and starts working. wtf?***
16th April 2014, 12:43 PM   |  #2  
Account currently disabled
Flag nassau
Thanks Meter: 666
 
3,194 posts
Join Date:Joined: Jul 2012
Donate to Me
More
Quote:
Originally Posted by itzjonjon69

Hey guys i just flashed the 1.54 firmware and in the process i relocked the phone. I flashed the firmware and everything, but now i can't unlock it for some reason. I tried the command to flash the token but no luck it gives me:

C:\Users\haswell\Desktop\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1830711296 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.124s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.129s

please help!

***and on a side note, whenever i plug the phone into the computer it takes a good 2-3 minutes before it detects the phone and starts working. wtf?***

Apply for a next token

Sent from my HTC One_M8 using Tapatalk
16th April 2014, 01:19 PM   |  #3  
OP Senior Member
Flag Tempe, AZ
Thanks Meter: 27
 
343 posts
Join Date:Joined: Jan 2009
More
I did, same thing
16th April 2014, 05:01 PM   |  #4  
OP Senior Member
Flag Tempe, AZ
Thanks Meter: 27
 
343 posts
Join Date:Joined: Jan 2009
More
i tried this (http://forum.xda-developers.com/show....php?t=2708571) however i got this:

1|shell@htc_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|shell@htc_m8:/ $
C:\Users\haswell\Desktop\platform-tools>

i also realized that my recovery is no longer working as my super SU... please someone help me
16th April 2014, 05:52 PM   |  #5  
Account currently disabled
Flag Dhaka
Thanks Meter: 23
 
384 posts
Join Date:Joined: Feb 2014
I also did .
20th April 2014, 06:44 AM   |  #6  
Senior Member
Flag Jersey City
Thanks Meter: 31
 
227 posts
Join Date:Joined: Sep 2009
Quote:
Originally Posted by itzjonjon69

i tried this (http://forum.xda-developers.com/show....php?t=2708571) however i got this:

1|shell@htc_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|shell@htc_m8:/ $
C:\Users\haswell\Desktop\platform-tools>

i also realized that my recovery is no longer working as my super SU... please someone help me


I had about the same issue and did all the stuff your doing.
Check in your hboot if it says S-On.
If so then like me you may need to visit the guys in the #firewater IRC channel on freenode.
They ran me through a couple things that didn't work then we all came to the conclusion that my system was write protected.
Something set incorrectly in my mmcblk0p2 caused everything to act as if the phone is S-On.
Finally Beaups remoted into my laptop with the phone connected and ran through some stuff in adb that allowed him to write a fresh copy of mmcblk0p2 to my phone and everything went back to normal.
Sorry I don't know the specifics but it was a couple hours into it then Beaups just remoted in and did it, it was to fast for me to follow.
The Following User Says Thank You to mc_365 For This Useful Post: [ View ]
20th April 2014, 06:48 AM   |  #7  
OP Senior Member
Flag Tempe, AZ
Thanks Meter: 27
 
343 posts
Join Date:Joined: Jan 2009
More
Quote:
Originally Posted by mc_365

I had about the same issue and did all the stuff your doing.
Check in your hboot if it says S-On.
If so then like me you may need to visit the guys in the #firewater IRC channel on freenode.
They ran me through a couple things that didn't work then we all came to the conclusion that my system was write protected.
Something set incorrectly in my mmcblk0p2 caused everything to act as if the phone is S-On.
Finally Beaups remoted into my laptop with the phone connected and ran through some stuff in adb that allowed him to write a fresh copy of mmcblk0p2 to my phone and everything went back to normal.
Sorry I don't know the specifics but it was a couple hours into it then Beaups just remoted in and did it, it was to fast for me to follow.

oops i thought i updated the thread, but forum member russellvone SAVED my ass. So what he did was he had me download this file for my ATT M8

https://mega.co.nz/#!NUURzC5T!tCjG3n...c6zRAwOPZ8T2PI and told me to rename it 0P6BIMG.zip and place it in my adb fastboot folder

then he told me to run these commands:

fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
fastboot reboot

then once everything was done we ran the commands from this thread (http://forum.xda-developers.com/show....php?t=2708571) and voila! i'm once again unlocked! He explained to me that when i tried to run the unlock commands before it didn't work because i had the secure boot.img and what he had me flash was a file he created which made it unsecure so i could run the command. HUGE HUGE props to this guy.
20th April 2014, 06:55 AM   |  #8  
Senior Member
Flag Jersey City
Thanks Meter: 31
 
227 posts
Join Date:Joined: Sep 2009
good to hear

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes