Database Info

Help needed installing Cyanogen(mod)

Hi all, first of all, sorry for being a complete noob to all this.
I was wondering if I could have some help installing Cyanogen mod on my HTC sensation as I find the stock ROM to be far to slow and bloated.
I have downloaded KGS Utility for all rooting/ S off purposes, my main issue at the moment is unlocking the bootloader,
I have got a unlock token from HTCdev but when I try and flash it, I get the following error:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.159s
I have followed all the instructions to the letter and tried multiple times.
Does anyone know what could be causing this. The device is definitely in bootloader USB mode with fastboot off and USB debugging enabled (though I have tried different combinations of these settings with no luck).
My next question is when it comes to flashing the ROM what order do I need to do everything. From what I can gather, once the bootloader is unlocked, I need to root, S-off and then install a new recovery in that order before flashing cyanogen. Is this correct?
Thanks for any help in advance.
Tom

armadacd55 said:
Hi all, first of all, sorry for being a complete noob to all this.
I was wondering if I could have some help installing Cyanogen mod on my HTC sensation as I find the stock ROM to be far to slow and bloated.
I have downloaded KGS Utility for all rooting/ S off purposes, my main issue at the moment is unlocking the bootloader,
I have got a unlock token from HTCdev but when I try and flash it, I get the following error:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.159s
I have followed all the instructions to the letter and tried multiple times.
Does anyone know what could be causing this. The device is definitely in bootloader USB mode with fastboot off and USB debugging enabled (though I have tried different combinations of these settings with no luck).
My next question is when it comes to flashing the ROM what order do I need to do everything. From what I can gather, once the bootloader is unlocked, I need to root, S-off and then install a new recovery in that order before flashing cyanogen. Is this correct?
Thanks for any help in advance.
Tom
Click to expand...
Click to collapse
have you installed htc drivers?
if yes reboot your pc
after unlock bootloader you can root and install recovery
about S-OFF it is optional.you can flash roms even with S-ON

rzr86 said:
have you installed htc drivers?
if yes reboot your pc
after unlock bootloader you can root and install recovery
about S-OFF it is optional.you can flash roms even with S-ON
Click to expand...
Click to collapse
Hi there sorry about posting twice, I wasn't sure if I had posted to the right forum
Thanks for the reply.
I did have the HTC drivers HTC and had rebooted. The trouble happens when I try and flash the unlock_code.bin using windows cmd.
I just get the fail message no matter what....
Ill try uninstalling and then reinstalling the driver and see what happens and get back to you.
Cheers
Tom

armadacd55 said:
Hi there sorry about posting twice, I wasn't sure if I had posted to the right forum
Thanks for the reply.
I did have the HTC drivers HTC and had rebooted. The trouble happens when I try and flash the unlock_code.bin using windows cmd.
I just get the fail message no matter what....
Ill try uninstalling and then reinstalling the driver and see what happens and get back to you.
Cheers
Tom
Click to expand...
Click to collapse
just make sure to open the command window in the folder where adb and fastboot files are located
then do again the command

rzr86 said:
just make sure to open the command window in the folder where adb and fastboot files are located
then do again the command
Click to expand...
Click to collapse
Ok I have reinstalled HTC sync and it recognizes the phone ok, disabled all antivirus software and anything else that might interfere.
I have the required files on the root of by drive in a folder called Android so type 'cd c:\Android' into the command window if that's what you mean.
The phone is connected and is in fastboot and reads fastboot USB. I then type: 'fastboot flash unlocktoken Unlock_code.bin'
I am still receiving the same error though

Do I need to S-Off before I can unlock the bootloader?

armadacd55 said:
Do I need to S-Off before I can unlock the bootloader?
Click to expand...
Click to collapse
there is no need but you can also to S-OFF without unlock the bootloader
are you sure you have adb and fastboot files?
if yes go to that folder,open the command window there and do only the command for unlocking the bootloader

rzr86 said:
there is no need but you can also to S-OFF without unlock the bootloader
are you sure you have adb and fastboot files?
if yes go to that folder,open the command window there and do only the command for unlocking the bootloader
Click to expand...
Click to collapse
Im still getting the same error sadly. I have also just tried to unlock the bootloader under my mac partition using the tutorial found here:
http://forum.xda-developers.com/showthread.php?t=1417839
and get exactly the same error.
Thanks for your help, suggestions and patience by the way, it really is appreciated

rzr86 said:
there is no need but you can also to S-OFF without unlock the bootloader
are you sure you have adb and fastboot files?
if yes go to that folder,open the command window there and do only the command for unlocking the bootloader
Click to expand...
Click to collapse
I pretty sure I have the files. In the folder I have:
adb.exe
AdbWinApi.dll
fastboot.exe
Unlock_code.bin
Am I missing anything?
Cheers
T

armadacd55 said:
I pretty sure I have the files. In the folder I have:
adb.exe
AdbWinApi.dll
fastboot.exe
Unlock_code.bin
Am I missing anything?
Cheers
T
Click to expand...
Click to collapse
no you are not missing something.have you ever replaced your motherboard?
i can not think another solution right now.
if you won't get unlock bootloader with the unlock code bin then try to S-OFF your device
after that things will be more easier for you
otherwise if you patience wait for someone else to give you other solution

Bricked XT925

Hi all, first post here.
I have a bricked XT925 which I'm trying to recover.
It will go into fastboot and I can access it with ADB/Fastboot/mFastbootv2/RazorHDToolkit5.0/RSD lite etc, but none of these will write a new recovery to flash.
I was able to unlock the bootloader using the Motorola website and the phone will talk to the PC software, but it's as though the internal flash memory is trashed.
In fact lots of commands to the flash result in a "fastboot max download size 30mb" error.
Can anyone help?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-2.8.6.0-xt925.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (9154 KB)...
OKAY [ 0.730s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.871s
Click to expand...
Click to collapse

I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.
Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.

I would start with obtaining a clean working flash of the official ROM, before trying to flash anything custom.
Click to expand...
Click to collapse
Would that I could. All the links I've found so far are dead.
I have another XT925 in working order, anyone know how to extract the image from it?
Just a guess, but if you went to the unlock website after the phone was soft-bricked, the bootloader may still be locked. I assume that the phone needs a full working OS to receive and implement the unlock signal from Motorola. Since it hasn't booted the OS since it was bricked, it hasn't had a chance to do so.
Click to expand...
Click to collapse
I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.

ddichiera said:
Would that I could. All the links I've found so far are dead.
I have another XT925 in working order, anyone know how to extract the image from it?
I think the Bootloader error messages are to be expected, everything I've since read suggests I should ignore them.
Click to expand...
Click to collapse
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.

palmbeach05 said:
I have one of the old Canadian leaked KK stock sbf (I was using it to see if I could bring anything to my AHD). I can post it to my GDrive and post the link this afternoon.
Click to expand...
Click to collapse
Any image would be welcome, GDrive is fine.

ddichiera said:
Any image would be welcome, GDrive is fine.
Click to expand...
Click to collapse
https://drive.google.com/open?id=0B52pkPIFU2dRWFRXOU9UQlhHZ3c

Thanks for that, unfortunately my situation has become worse.
Whilst the phone was connected and in fastboot mode, I deleted the ADB driver in Device Manager and now the PC, or more specifically ADB and Fastboot wont talk to the phone. Grrrrr.
Oh, and the other handset has decided to die as well.
One thing at a time. Anyone know how to restore the driver/get-the-phone-talking-to-ADB/Fastboot again?

Fastboot error

I made a full wipe(with os too) with twrp on my p8max.
my device isn't recognized by my pc and by huawei hisuite.
To fix the problem i unistalled the twrp and tried to install the stock one with no results.
Now i am able to enter the fastboot mode and the huawei eRecovery (emui).
I downloaded the stock firmware for my device (UPDATA.APP) and used huawei update extractor. Suddenly i put the extracted files in my adb folder and tried to flash via fastboot after opening the command prompt as admin.
When i try to flash files ".img" i always get the error: "FAILED (remote : Command not allowed)"
P.s. My bootloader is unlocked and i checked that.
fastboot recognizes my device
HOW TO SOLVE THIS ERROR ? HOW TO FLASH MY FILES ?

whats the command you use to flash recovery?

fastboot flash recovery RECOVERY.img

same error..
PHONE unlocked
FRP Unlock
boot.img extracted from DAV-701LV100R001C199B005CUSTC199D002
but not accepting the command,
\P8_Max>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23388 KB)...
OKAY [ 0.773s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.778s

Drivers installed?

Hirs_E_Fruit said:
Drivers installed?
Click to expand...
Click to collapse
yes it is.. i think it is not about drivers.. because command is working but not accepting the part..

newest ADB and Fastboot files?

Hirs_E_Fruit said:
newest ADB and Fastboot files?
Click to expand...
Click to collapse
fastboot_adb(1.0.32)_071114_r21
i think it is new one.. maybe last one but it is new..

same problem here..
any one knew?

https://drive.google.com/open?id=0B7q0s3loYhP3YndkSjk3NUVJVzA

Same problem here. Reloaded drivers and no luck.
---------- Post added at 02:51 PM ---------- Previous post was at 02:47 PM ----------
lolcops92 said:
I made a full wipe(with os too) with twrp on my p8max.
my device isn't recognized by my pc and by huawei hisuite.
To fix the problem i unistalled the twrp and tried to install the stock one with no results.
Now i am able to enter the fastboot mode and the huawei eRecovery (emui).
I downloaded the stock firmware for my device (UPDATA.APP) and used huawei update extractor. Suddenly i put the extracted files in my adb folder and tried to flash via fastboot after opening the command prompt as admin.
When i try to flash files ".img" i always get the error: "FAILED (remote : Command not allowed)"
P.s. My bootloader is unlocked and i checked that.
fastboot recognizes my device
HOW TO SOLVE THIS ERROR ? HOW TO FLASH MY FILES ?
Click to expand...
Click to collapse
I tried Google and spent hours but no resolve. Please post if you get a fix..Thanks

vvette said:
Same problem here. Reloaded drivers and no luck.
---------- Post added at 02:51 PM ---------- Previous post was at 02:47 PM ----------
I tried Google and spent hours but no resolve. Please post if you get a fix..Thanks
Click to expand...
Click to collapse
Google USB Drivers installed, newest ADB/Fastboot Files, USB Debugging activated?

Hirs_E_Fruit said:
Google USB Drivers installed, newest ADB/Fastboot Files, USB Debugging activated?
Click to expand...
Click to collapse
Yes, yes and yes...Something is wrong. It appears this has happened to other types of phones too. I really want to root this thing!

vvette said:
Yes, yes and yes...Something is wrong. It appears this has happened to other types of phones too. I really want to root this thing!
Click to expand...
Click to collapse
Try it on a Linux Distribution like Ubuntu.
Otherwise i think you still have done something wrong or forget something...

Hirs_E_Fruit said:
Try it on a Linux Distribution like Ubuntu.
Otherwise i think you still have done something wrong or forget something...
Click to expand...
Click to collapse
Thanks, I have no clue on Linux... Seems like phone wont let it write to it. I can get info on ADB devices, Flash reboot no problem. BUT when trying to flash recovery or boot image it wont go. Tried 3 different computers/cables and no luck. Uggh !

vvette said:
Thanks, I have no clue on Linux... Seems like phone wont let it write to it. I can get info on ADB devices, Flash reboot no problem. BUT when trying to flash recovery or boot image it wont go. Tried 3 different computers/cables and no luck. Uggh !
Click to expand...
Click to collapse
Do you know how to do this on a mac? If so can you give a step by step? Its worth a shot. OR can anyone tell me how to use terminal on Mac and flash a recovery? Thanks!

Honor 8 Hard Bricked

Hello,
My honor 8 is hard bricked, yesterday I wished to install custom Rom and it was encrypted so I decided to return to EMUI, I installed stock recovery I installed rollback package to emui 4.1 and emui 4.1 now i'm stuck on boot screen. I already do a format data and wipe cache but nothing.
Please help me.
EDIT : I can go to ADB but I have this message when I try to flash anything... "FAILED (remote: Command not allowed)" FRP is locked

Please help me I'm so bored about this problem

There are some guides on how to unbrick phone with FRP locked... You could try to watch on them.
That's mine guide

ScardracS said:
There are some guides on how to unbrick phone with FRP locked... You could try to watch on them.
That's mine guide
Click to expand...
Click to collapse
The problem is when i use ADB command it wrongs me
"target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.894s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.903s"

If you can't find any solution with ADB, as a last resort you could use DC Phoenix to fix it. But it costs 15 Euros to use it. That's what I had to do fix the same problem you have.

BnK1986 said:
The problem is when i use ADB command it wrongs me
"target reported max download size of 471859200 bytes
sending 'recovery' (36996 KB)...
OKAY [ 0.894s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.903s"
Click to expand...
Click to collapse
Go with dload method. Try downloading the full firmware for your model and use the 3 combination to flash. There is quick guide in my signature if you are not aware of the exact method for dload.

shashank1320 said:
Go with dload method. Try downloading the full firmware for your model and use the 3 combination to flash. There is quick guide in my signature if you are not aware of the exact method for dload.
Click to expand...
Click to collapse
I can't do dload method it shows me boot screen.

BnK1986 said:
I can't do dload method it shows me boot screen.
Click to expand...
Click to collapse
You may not be doing it right. Assuming.
Keep trying couple of times, remember to press power up+powet down 1st and then power key and keep pressing all together

shashank1320 said:
You may not be doing it right. Assuming.
Keep trying couple of times, remember to press power up+powet down 1st and then power key and keep pressing all together
Click to expand...
Click to collapse
Yes I know i was doing this before and it worked but now it's not possible I will try several times like 5-10 times in a row

BnK1986 said:
Yes I know i was doing this before and it worked but now it's not possible I will try several times like 5-10 times in a row
Click to expand...
Click to collapse
are you able to get into fastboot or recovery?

shashank1320 said:
are you able to get into fastboot or recovery?
Click to expand...
Click to collapse
No I hold the 3 buttons it shows me boot screen, black screen for 1 second and again boot screen

shashank1320 said:
are you able to get into fastboot or recovery?
Click to expand...
Click to collapse
Any solutions?

BnK1986 said:
Any solutions?
Click to expand...
Click to collapse
You can enter in fastboot, by pressing volume down when the phone is powering on and holding the button, immediately insert the usb cable (already plugged in the pc) and you will enter in fastboot.
Video
Sent from my FRD-L09 using XDA Labs

grilla99 said:
You can enter in fastboot, by pressing volume down when the phone is powering on and holding the button, immediately insert the usb cable (already plugged in the pc) and you will enter in fastboot.
Video
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
I can do this but ADB commands not working

BnK1986 said:
I can do this but ADB commands not working
Click to expand...
Click to collapse
When you enter in this shell, you are not allowed to use ADB commands, but only fastboot commands, previously you typed adb devices, now you can't. But if you type fastboot device it will shown you your id number plus device, just try if what i sad is true
Sent from my FRD-L09 using XDA Labs

tnks !!!! friend save _me !!!!!

hey i have the same problem
what did you exactly do in fastboot mode? no commands works on my phone

Bricked Google Pixel 3 XL

Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?

pech_alive said:
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
Click to expand...
Click to collapse
You can get to fastboot but not recovery?

Yeah if you can get to fastboot then unlock the bootloader and flash the factory image

Tulsadiver said:
You can get to fastboot but not recovery?
Click to expand...
Click to collapse
I can enter fastboot, but when I press to enter Recovery Mode the screen goes black and that's it, nothing happens, same when I press Start.
I can't unlock it because I get an error: failed (remote: 'flashing unlock is not allowed')

Was it 100% stock when you relocked it?
Sent from my crosshatch using XDA Labs

I would open the stock recovery on the PC and try flashing the factory image from there.

ridobe said:
Was it 100% stock when you relocked it?
Click to expand...
Click to collapse
It was 100% stock when I relocked it.
krabman said:
I would open the stock recovery on the PC and try flashing the factory image from there.
Click to expand...
Click to collapse
I tried that but this is what returns to me:
flash-all.bat
Sending 'bootloader_a' (8489 KB) OKAY [ 0.310s]
Writing 'bootloader_a' FAILED (remote: 'Fastboot command (flash is not allowed when locked')
Finished. Total time: 0.867s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.054s
Sending 'radio_a' (71148 KB) OKAY [ 1.834s]
Writing 'radio_a' FAILED (remote: 'Fastboot command (flash is not allowed when locked')
Finished. Total time: 2.084s
rebooting into bootloader OKAY [ 0.050s]
Finished. Total time: 0.054s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: b1c1-0.1-4852902
Baseband Version.....: g845-00010-180619-B-4850223
Serial Number........: **********
--------------------------------------------
Checking product OKAY [ 0.060s]
Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit...
Click to expand...
Click to collapse

I seem to remember from my Pixel (original) days that there was some trick to re-locking the bootloader or you would encounter issues.
You might consider searching the original Pixel's subforum here at XDA for that thread and see if the suggestions in it apply to you.
I think this might be the thread.
Read through it to see if anything can help you.
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615

"Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit..."
The bootloader on your device is pre-release? Not sure at all, love to get some schooling on where that bootloader came from. Where did you get the phone? From the Ukrainian with the stolen batch from Foxconn? Wow, I am getting Alex Jones like too quick or what? Lol
Sent from my Pixel 3 XL using Tapatalk

MArtyChubbs said:
"Checking version-bootloader FAILED
Device version-bootloader is 'b1c1-0.1-4852902'.
Update requires 'b1c1-0.1-4948814'.
fastboot: error: requirements not met!
Press any key to exit..."
The bootloader on your device is pre-release? Not sure at all, love to get some schooling on where that bootloader came from. Where did you get the phone? From the Ukrainian with the stolen batch from Foxconn? Wow, I am getting Alex Jones like too quick or what? Lol
Click to expand...
Click to collapse
A friend of mine bought this phone from a website similar to eBay.
The software was stock.

pech_alive said:
Hello, I have a Pixel 3 XL phone with bootloader locked, unable to enter Recovery Mode or unable to start it.
I tried to put factory image through fastboot but I recieve an error saying that the bootloader is locked.
Prior to that the bootloader was unlocked but I wanted to lock it.
Anything to do about it?
Click to expand...
Click to collapse
Of course when in recovery it's all black. You have to hold vol up and power then menu pops up.

Since it's already a brick, try fastboot flashing unlock_critical
Sent from my Pixel 3 XL using Tapatalk

lucky_strike33 said:
Of course when in recovery it's all black. You have to hold vol up and power then menu pops up.
Click to expand...
Click to collapse
If the Andorid Robot picture appears, pressing the Power key and click Volume Up once will bring up the menu, however, his screen is black..? I get the robot, but yet to see a black screen. Good tip cuz that may be his way out of this mess.
Regarding the older bootloader, wouldn't the newer bootloader in the current factory image upgrade it? OR (put my custom made tinfoil hat on now) Google has blocked the stolen phones from firmware updates or bricks them..? Toots and Farts, you're screwed. (Taking hat off now)
I've always unlocked my pixels right away (lucked out on my VZW Pixel XL) and haven't encountered BL mismatch unless downgrading locked BL from other manufacturers.
There were at least 120 stolen phones sold prior to launch and unless you bought it from Google or an authorized carrier, I am suspicious..?
superchilpil said:
Since it's already a brick, try fastboot flashing unlock_critical
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
But, wouldn't he need to Go to Developer Options and enable OEM unlocking first?

superchilpil said:
Since it's already a brick, try fastboot flashing unlock_critical
Click to expand...
Click to collapse
People have already done this on working Pixel 3 XL's and all it did was returned an error.

I've gota a vague recollection of needing to format before flashing the image in this situation. Anyone confirm our deny?

MArtyChubbs said:
If the Andorid Robot picture appears, pressing the Power key and click Volume Up once will bring up the menu, however, his screen is black..? I get the robot, but yet to see a black screen. Good tip cuz that may be his way out of this mess.
Regarding the older bootloader, wouldn't the newer bootloader in the current factory image upgrade it? OR (put my custom made tinfoil hat on now) Google has blocked the stolen phones from firmware updates or bricks them..? Toots and Farts, you're screwed. (Taking hat off now)
I've always unlocked my pixels right away (lucked out on my VZW Pixel XL) and haven't encountered BL mismatch unless downgrading locked BL from other manufacturers.
There were at least 120 stolen phones sold prior to launch and unless you bought it from Google or an authorized carrier, I am suspicious..?
But, wouldn't he need to Go to Developer Options and enable OEM unlocking first?
Click to expand...
Click to collapse
True, that didn't occur to me. But since it was unlocked prior it may still be unlockable.
bp328i said:
People have already done this on working Pixel 3 XL's and all it did was returned an error.
Click to expand...
Click to collapse
Being a possible dev unit it might not error out with said command. At least that was my thought process. Doesn't hurt to try anyway? If it fails, it fails. Can't hurt to try.
Sent from my Pixel 3 XL using Tapatalk

I just soft bricked my PXL3; this means access only to fastboot ( is under warranty ) and you can get it back with fastboot flashing unlock critical then flash the factory image i don't get it why you can't

I thought flashing unlock critical was p2xl and not applicable to p3xl? And was your bootloader relocked prior to softbrick?
Sent from my Pixel 3 XL using Tapatalk

Update your adb tools on your computer and try flashing stock images again. Then reboot.

Help, i'm dealing with an issue too, everything was working fine, rooted with magisk , turned off my phone to charge, it reached 100% turned it back on, and it won't boot up, I see the G logo with a grey loading bar white background screen it does this for a few minutes and it reboots and gives me a screen that says "can't load android system. Your data may be corrupt. If you continue to get this message you may need to perform a factory data reset and erase all user data stored on this device" . I don't want to do a factory reset? WTH is going on here.
The last major change i did is install greenify4magisk but i didn't enable it (unchecked in magisk screen)
Help!
Edit: How do i do rescue OTA?