Related
current state: unrooted, s-on, relocked
I successfully unlocked my phone, installed TWRP and attempted to flash a new ROM. Some how I messed up by wiping out system file without backup, and I failed to flash a new ROM either.
So I flashed my phone with RUU latest version (hboot 1.19, radio 1.12.) Now on the bootloader screen it says RELOCKED on top.
When I tried to unlock (normal HTC Dev method) the terminal gave "unlock token checked successfully OKAY", and the unlock confirmation screen showed up normally.
But after rebooting, it turns out my phone is still "RELOCKED." Is there any reason why it doesn't work? And how to reunlock it successfully?
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
om4 said:
Did you submit the unlock token to htc website so that you can be given the unlock_code.bin file to flash?
---------- Post added at 05:42 PM ---------- Previous post was at 05:41 PM ----------
Never mind I misread the post, try the relock command and unlocking again
Make sure the command is right
Fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Here is what happened in my terminal:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.011s]
finished. total time: 0.014s
C:\android-sdk\platform-tools>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.147s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.011s]
finished. total time: 0.164s
After that the green unlock confirmation screen showed up on the phone, I chose unlock, pressed power button, waited for it to reboot, then reboot again to see the bootloader. Still no avail (relocked).
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
om4 said:
Have you tried flashing twrp anyway?
Use the 2.2.2.0 release, the new 2.3 has some issues that need to be worked out. It may just flash over, and never know
Click to expand...
Click to collapse
Here's what I got:
C:\android-sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7356 KB)...
OKAY [ 1.170s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.810s
(I used the img file in 2.2.2.0 twrp zip file. The name is recovery.img)
Does the failure message have something to do with being relocked?
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Sent from my icrap 2 using Tapatalk HD
That shouldn't happen unless phone is still locked or software doesn't match
cruise350 said:
Have you tried the PJ75IMG.zip for twrp. If you are s-off you should be able to install that and not worry about being unlocked.
Click to expand...
Click to collapse
Opps sorry, I'm currently S-On.
om4 said:
That shouldn't happen unless phone is still locked or software doesn't match
Click to expand...
Click to collapse
When I tried to lock the phone again, it says my phone is already locked. But the problem is normal unlock method doesn't work with some reason.
I'm stumped, maybe ruu again?
om4 said:
I'm stumped, maybe ruu again?
Click to expand...
Click to collapse
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
chtat12 said:
Done ruu again, but still can't get unlocked.
Maybe it's worth mentioning that after select 'Yes' on the unlock bootloader screen (the green page), the phone didn't reboot. It just turned itself off with red LED charging.
Click to expand...
Click to collapse
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
I can't think of any reason it wouldn't work again, maybe someone else will see this and have a fix. Sorry
chtat12 said:
Is there another way around (manual method) for unlocking? To me it looked like some thing after the green confirmation page just didn't work right.
Click to expand...
Click to collapse
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
I would have mentioned it if closeone had a release ready but it's still a bit off. Better to wait then to have someone following directions to purposely brick their phones
premo15 said:
You could try downgrading to hboot 1.12 to get s-off...then it won't matter if you're unlocked or not. The process is still pretty new and not for the faint of heart (yet), but seems to be verified working. Check the downgrade sticky thread in the original dev forum for more details.
Sent from my EVO LTE
Click to expand...
Click to collapse
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Yes it does, I didn't even remember that lol. I just didn't mention it because right now the overall process is rough
I think the unlock process modified the boot section, and looks like mine is a bit messed up. If so, would 'fastboot flash boot <bootfile>' work? (I don't know where to find it yet, just an another thought.)
chtat12 said:
I believe downgrading method requires an unlocked phone, since it needs twrp for adb commands?
Click to expand...
Click to collapse
Good point...
Sent from my EVO LTE
any resolution to this? i find myself in the same situation
Hello,
I have tried to flash a custom ROM to my htc desire x but unfortunetly I am a almost complete noob. I have been using Desire_X_All-In-One_Kit_v2.0 in order to complete the action. The problem is that i have never rooted the fone nor i have put in the recovery into it. So basically i unlocked the bootloader and thought it would all work.Well you know yourselfs it didn't.I have been looking all over the place for a way to get my phone fixed and i found one(ima Junior member can't post links yet ( Re-flash stock ROM (RUU) after bricking a rooted device)) .I have done all the steps but in step5 i get an error
C:\rec>fastboot flash recovery recovery_signed.img
sending 'recovery' (4266 KB)...
OKAY [ 0.795s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.323s
and in step 7 i get Error 140 bootloader error during RUU
Any help here would be greatly appreciated
Regards Kuba
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
nlooooo said:
First of all write down all you have written in bootloader screen.
It will be easy to fix it.
Click to expand...
Click to collapse
How do you mean? do you mean whats written when i enter the bootloader or what have I written in in the terminal ( eg. fastboot flash recovery recovery_signed.img)
Thanks a lot for your quick reply
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
nlooooo said:
Bootloader screen, when you enter bootloader.
Also, give me the version of RUU that you have.
Click to expand...
Click to collapse
*****RELOCKED********
PROTO PVT SHIP S-ON RL
HBOOT-1.24.0000
RADIO-1.10.40.23
eMMC-boot
Oct 30 2012, 20:09:09
The most recent RUU i have downloaded is RUU_PROTO_U_ICS_40A_HTC_Europe_1.14.401.1_Radio_10.18.40.05U_1.09.45.201_release_284072_signed
But i have read that FAILED <remote: signature verify fail> error that im getting is related to wrong ruu .I guess you know better
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
nlooooo said:
There's a newer release 1.18.401.1 there's a link in Index in my signature, try to download that one and run it with phone booted in fastboot and attached to PC. If that doesn't go will try something else.
Click to expand...
Click to collapse
Great man!! thanks for help!! Could you just make it clear what i need in the folder with the ruu ?. its Adb.exe AdbWinAp.dll fastBoot.exe and the image file? is there anything else i would need? (as you see i know basically nothing about this)
It's not a folder its exe file, just run it from PC.
nlooooo said:
It's not a folder its exe file, just run it from PC.
Click to expand...
Click to collapse
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
hlick14 said:
YOUR Fuc**ng Awsome bruf everything back on track !!.....THank a lot
Click to expand...
Click to collapse
That's why I'm here and that's what the thanks button stands for...
Edit dfownloads removed as the host started serving malware.
I dont have these files anymore, sorry, please dont ask for them
For other HTC devices supported by FacePalm, please see this thread: http://forum.xda-developers.com/showthread.php?t=2155069
Welcome to Facepalm S-Off for modern HTC phones.
Credits and terms:
Exploit by beaups, full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc. Additional thanks to indirect for Evo LTE testing.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6LRSY8MT8P3A6
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
SuperCID for HTC Evo 4G LTE:
Code:
adb shell
su
echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
1)
Code:
adb reboot bootloader
2)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
3)
Code:
fastboot flash zip PJ7510000-EvoLTE.zip
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
7) Immediately issue the following command:
Code:
fastboot boot EvoLTE-rescue.img
(this is fastboot boot, NOT fastboot flash!)
8) Allow device to boot (may not fully boot on some custom roms)
Code:
adb reboot bootloader
9) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
Took me all of 2 minutes to get s-off.
Extra info: This works on 3.16 firmware and subsequently 3.15 as well.
Indirect said:
Took me all of 2 minutes to get s-off.
Extra info: This works on 3.16 firmware and subsequently 3.15 as well.
Click to expand...
Click to collapse
Probably worked on 3.16 for you as you already had supercid, I'm guessing the recent 3.16 update prevents changing the CID.
I dont think so because we've never used CID on this phone before. Only way to find out is to test.
Thanks for bringing this to the evo lte! I have windows 8 so this is gonna make it much easier compared to dirtyracun, thanks!
Thread cleaned. Going forward let's see about keeping it respectful in here.
You guys are freaking awesome thanks to all involved
Sent from my PoS MoPho
This is super easy! You guys rock. Thanks 4 this
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Chocorico said:
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Pretty sure it's that first 3 lines of code - makes your phone believe it has older firmware so you can flash older RUUs/updates. Swear there used to be a thread for it around here somewhere.
Help! I'm bricked.
C:\android-sdk-windows\platform-tools>fastboot devices
HT25KS405806 fastboot
C:\android-sdk-windows\platform-tools>adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.059s]
finished. total time: 0.062s
C:\android-sdk-windows\platform-tools>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
OKAY [ 2.435s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.450s
C:\android-sdk-windows\platform-tools>fastboot boot EvoLTE-rescue.img
downloading 'boot.img'...
OKAY [ 0.853s]
booting...
OKAY [ 0.005s]
finished. total time: 0.862s
Then my phone never booted back up.
Hold power for 40 seconds, nothing in that should be causing bricks.
EDIT:
Apparently you were not bricked, we can only support stock roms, can't control how it behaves on AOSP, given it should still work, but it might not until you do a reboot. Please next time confirm that you are bricked before posting that you are.
[23:24:30] <BB15> I'm actually not bricked. I got it to boot back up and I'm s-off, but now I get prompted to activate my phone
BB15 said:
Help! I'm bricked.
C:\android-sdk-windows\platform-tools>fastboot devices
HT25KS405806 fastboot
C:\android-sdk-windows\platform-tools>adb reboot bootloader
C:\android-sdk-windows\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.059s]
finished. total time: 0.062s
C:\android-sdk-windows\platform-tools>fastboot flash zip PJ7510000-EvoLTE.zip
sending 'zip' (35863 KB)...
OKAY [ 2.435s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 3.450s
C:\android-sdk-windows\platform-tools>fastboot boot EvoLTE-rescue.img
downloading 'boot.img'...
OKAY [ 0.853s]
booting...
OKAY [ 0.005s]
finished. total time: 0.862s
Then my phone never booted back up.
Click to expand...
Click to collapse
jcase said:
Hold power for 40 seconds, nothing in that should be causing bricks.
EDIT:
Apparently you were not bricked, we can only support stock roms, can't control how it behaves on AOSP, given it should still work, but it might not until you do a reboot. Please next time confirm that you are bricked before posting that you are.
[23:24:30] I'm actually not bricked. I got it to boot back up and I'm s-off, but now I get prompted to activate my phone
Click to expand...
Click to collapse
Yeah, I wasn't bricked. After waiting for some time for my phone to reboot after running FacePalm I unplugged the USB and held the power button and it booted right up. Rebooted the bootloader and verified that I was s-off. Then I ran into the activation problem. Just flashed MeanBean and ran through the activation, now all is good. Your work on this is much appreciated.
Thankkssssss S-off already
Chocorico said:
Sorry for the stupid question, but what is supercid.?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
mildlydisturbed said:
Pretty sure it's that first 3 lines of code - makes your phone believe it has older firmware so you can flash older RUUs/updates. Swear there used to be a thread for it around here somewhere.
Click to expand...
Click to collapse
here you go:
[SUPERCID] SuperCID For EVO LTE(Ruu to older firmware(not hboots))
So for clarity, the superCID commands are run from the phone while booted? or in bootloader? It looks from the way its written thats its meant to be done while the device is booted
Edit:
Thanks OCN
Finally have s-off!!!!
Thx to Facepalm S-Off I now have s-off. Finally,after a long year and a half of trying to get s-off.....
I must have been doing a few things wrong this whole time or Facepalm S-Off has done it right...
Rxpert said:
So for clarity, the superCID commands are run from the phone while booted? or in bootloader? It looks from the way its written thats its meant to be done while the device is booted
Edit:
Thanks OCN
Click to expand...
Click to collapse
I ran it while booted. No issues.
Sent from my EVO using Tapatalk 2
Fantastic job.
Already S off but props given.
Very nice.
Wow, this was incredibly easy. Soff in less than 2 minutes. I just followed the directions and flashed stock rom to be safe. $$ coming to you guys on payday!!
Hello all,
I'm having a problem with putting a new ROM on my device. Goiung back to backup ROm has failed to as it seems the Backup wasn't complete
I thought it had something to do with S-Off, but someone from another thread said I should make a new topic as this would probably be another problem.
I wanted to go to the SuperSense DX5 ROM, but then i need to upgrade my hboot version and boot.img.
At this moment my hboot version is 1.24.0000. Also the the device is still in S-On.
When I try to load boot.img i get the following message
flash boot boot.img
sending 'boot' (4452 KB)...
OKAY [ 0.811s]
writing 'boot'...
FAILED (remote: image update error)
finished. total time: 0.811s
Click to expand...
Click to collapse
Fot the hboot i get following message:
flash hboot bravo_alphaspl-sense.img
sending 'hboot' (512 KB)...
OKAY [ 0.234s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.234s
Click to expand...
Click to collapse
When i looked these errors up I Always ended up about S-Off or get stock recovery.img. Already got the stockrecovery.img on device but still nothing works.
Is there anyone that could help me solve this problem please? I'm completly not sure why now I'm not able to put ROM's on it anymore.
With Kind Regards,
Günther
1. You're trying to flash hboot meant for Desire not Desire X
2. Your hboot is 1.24, you cannot flash boot.img or ROM meant for hboot 1.25
3. You should flash only ICS boot.img, ICS recovery and ICS ROM
So find any ICS ROM in dev section and follow instructions there on how to flash the ROM.
Or go to general section and look for how to restore to ICS stock and update your device to JellyBean.
Then you can install all those JB ROM that you wanted to.
Remember this ? It's the same problem and the same way that you need to do to solve your problem.
doninckg said:
Got it fixed, after some Stock rom install and then tried another ROM Shadow, and it seems to be working once again.
Sorry for my question. I might have done something wrong about the hboot version I think.
Click to expand...
Click to collapse
Good thing you still have S-On or else you would have a paperweight right now
Ohhh OK,
I just followed the guide on the SuperSense DX5 where they refered to hboot 1.25.
But I still don't get why i'm not able to flash a boot.img. Tried the ICS ROM I Always used before "Sense Revolution+ R2
But I'm not able to get this working anymore
But I actually wanted to upgrade because I had some difficulties with this ROM about my Mobile Data. Had high hopes that it could be fixed with a JB ROM for Desire X. The only boot.img and hboot i tried to install was meant for the Desire-X. I'm also using Hassoon 3.0 for Desire-X to have the right recovery flashed for ICS of JB.
Still I must be doing something wrong I guess now, but don't know what then.
So S-On is alright for this device then? I don't need to change annything for this device to try and put it in s-off?
Sorry if I lack a bit of knowledge to root. Thought I did everything that was needed, like I used to do before.
doninckg said:
But I actually wanted to upgrade......
Click to expand...
Click to collapse
1. If you have a backup of your ROM, restore that then update to JB with OTA.
2. Or use the RUU RUU_PROTO_U_ICS_40A_HTC_Europe_1.18.401.1_Radio_10.21.40.06U_1.10.40.23_release_295191_signed.exe to restore your device then do OTA update.
Download : http://www.androidruu.com/?developer=Proto
3. Or for more advance user, follow this guide - http://forum.xda-developers.com/showthread.php?t=2212067 but not sure whether all links still active for the needed files.
Option 2 is the best for you.
How-to:
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
thanks ckpv5, I will try to do this now.
ckpv5, this fixed everything!!! Thanks a million times for helping me out this fast.
Hello i have HTC Desire 601 in bootloop. I can't do anyting with this phone. after i enter in HBOOT mode i see
***LOCKED****
ZARA_UL PVT SHIP S-ON RL
HBOOT 2.22.0000
After i use htcdev.com and receive unlock_code.bin, i use fastboot flash unlocktoken Unlock_code.bin i see on screen message, choose yes and after reboot bootloop again and Locked bootloader.
if i try flash any images in fastboot - i receive FAILED (remote: signature verify fail)
Pls help me, if it possible.
DenisDDD said:
Hello i have HTC Desire 601 in bootloop. I can't do anyting with this phone. after i enter in HBOOT mode i see
Pls help me, if it possible.
Click to expand...
Click to collapse
Nobody don't know what i can do with my HTC? It very sad for me.
And other two moment fastboot oem rebootRUU - also simple reboot phone. And after i try factory reset i see lines with words CW backup/ If it hardware problem - pls somebody ask me.
Thanks
DenisDDD said:
Nobody don't know what i can do with my HTC? It very sad for me.
And other two moment fastboot oem rebootRUU - also simple reboot phone. And after i try factory reset i see lines with words CW backup/ If it hardware problem - pls somebody ask me.
Thanks
Click to expand...
Click to collapse
pull out the battery then reinsert it after 1 min and then go to bootloader and hard reset (factory reset)..........i think this might help...if still problem persist then let me know..........
rajat836 said:
pull out the battery then reinsert it after 1 min and then go to bootloader and hard reset (factory reset)..........i think this might help...if still problem persist then let me know..........
Click to expand...
Click to collapse
Thanks for answer. i try to make it - after i enter to stock recovery - i choose wipe data/factory reset - i see
--- Wipping data...
Formating /data
Backup Data Preload
Backup CW Package
Restore Data Preload
Restore CW Package
Formatting /cache
Data wipe complete
Write host_mode: 0 done.
My phone don't want boot - usually bootloop, occasionally ш can see statusbar with time and nothing more
DenisDDD said:
Thanks for answer. i try to make it - after i enter to stock recovery - i choose wipe data/factory reset - i see
--- Wipping data...
Formating /data
Backup Data Preload
Backup CW Package
Restore Data Preload
Restore CW Package
Formatting /cache
Data wipe complete
Write host_mode: 0 done.
My phone don't want boot - usually bootloop, occasionally ш can see statusbar with time and nothing more
Click to expand...
Click to collapse
u fomatted ur phone.................now first get s-off and then use duir's method to unlock bootloader..............
rajat836 said:
u fomatted ur phone.................now first get s-off and then use duir's method to unlock bootloader..............
Click to expand...
Click to collapse
Thanks for answer.
May be. Can you give a link how i can get s-off with locked bootloader and what is duir's method ?
DenisDDD said:
Thanks for answer.
May be. Can you give a link how i can get s-off with locked bootloader and what is duir's method ?
Click to expand...
Click to collapse
when u are unlocking ur bootloader did u installed all the driver needed like htc sync manager and others...............
try sunshine http://theroot.ninja/ since u have kitkat with 2.22 hboot ver..............
rajat836 said:
when u are unlocking ur bootloader did u installed all the driver needed like htc sync manager and others...............
try sunshine since u have kitkat with 2.22 hboot ver..............
Click to expand...
Click to collapse
In begin this thread i wrote - i can't unlock bootloader - my phone after confirmation simple reboot and bootloader stay locked
DenisDDD said:
In begin this thread i wrote - i can't unlock bootloader - my phone after confirmation simple reboot and bootloader stay locked
Click to expand...
Click to collapse
i m asking that u have installed htc sync manager on your pc cause without it wont be unlock...................and if u have that token then redo it ,,might unlock ..........
rajat836 said:
i m asking that u have installed htc sync manager on your pc cause without it wont be unlock...................and if u have that token then redo it ,,might unlock ..........
Click to expand...
Click to collapse
I install HTC Sнтс - nothing new.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.125s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.141s
I choose yes - and phone simple reboot.
I have locked bootloader and phone that wan't boot up. I can't enter RUU mode. I think throw this phone in wall
DenisDDD said:
I install HTC Sнтс - nothing new.
fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.125s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.016s]
finished. total time: 0.141s
I choose yes - and phone simple reboot.
I have locked bootloader and phone that wan't boot up. I can't enter RUU mode. I think throw this phone in wall
Click to expand...
Click to collapse
I think u should search around the net for help .......or simply ask any XDA contributer they might help u.......but gain s-off if u do that then u will be able to install custom ROMs ......
rajat836 said:
I think u should search around the net for help .......or simply ask any XDA contributer they might help u.......but gain s-off if u do that then u will be able to install custom ROMs ......
Click to expand...
Click to collapse
In first row i need unlock bootloader. Other things possible only with unlocked bootloader. But this i can't do it. Thanks for help.
DenisDDD said:
In first row i need unlock bootloader. Other things possible only with unlocked bootloader. But this i can't do it. Thanks for help.
Click to expand...
Click to collapse
u can s-off without unlocking bootloader through many softwares..........
rajat836 said:
u can s-off without unlocking bootloader through many softwares..........
Click to expand...
Click to collapse
As i wrote - my phone not boot and i can't access with adb comand promt
DenisDDD said:
As i wrote - my phone not boot and i can't access with adb comand promt
Click to expand...
Click to collapse
is ur phone can go to fastboot mode if yes then u can do it
go to this link
it has all the stock roms and recovery............
rajat836 said:
is ur phone can go to fastboot mode if yes then u can do it
go to this link
it has all the stock roms and recovery............
Click to expand...
Click to collapse
In my first message i wrote
if i try flash any images in fastboot - i receive FAILED (remote: signature verify fail)
Nothing changed since i open this thread.
DenisDDD said:
In my first message i wrote
if i try flash any images in fastboot - i receive FAILED (remote: signature verify fail)
Nothing changed since i open this thread.
Click to expand...
Click to collapse
this link might help.................and search for the reason on the net..............if u dont have s-off then cause of high security sometimes it becomes impossible ............. because without unlock bootloader u wont be able to use fastboot mod this is the reason u are getting the error
and go to this link also
rajat836 said:
this link might help.................and search for the reason on the net..............if u dont have s-off then cause of high security sometimes it becomes impossible ............. because without unlock bootloader u wont be able to use fastboot mod this is the reason u are getting the error
and go to this link also
Click to expand...
Click to collapse
Thanks for your replays.
Second link - is simple mistake in command.
First - is something named "goldcard" - i think this not possible for my phone. Today i have no idea what i can to do.
If you have - are you welcome
DenisDDD said:
Thanks for your replays.
Second link - is simple mistake in command.
First - is something named "goldcard" - i think this not possible for my phone. Today i have no idea what i can to do.
If you have - are you welcome
Click to expand...
Click to collapse
what is goldcard?????????????? i cant understand
rajat836 said:
what is goldcard?????????????? i cant understand
Click to expand...
Click to collapse
if you read first link thread - you understand what is "goldcard".