Related
hey guys i have asked this in other threads with no answer
a customer hard reseted the device using the opyion inside the rom
not the devies gets to htc logo then reboots then htc logo and green logo like updating then red triangle
thas it after a while reboots and on and on
i wanted to install oem
i went to hboot
then to fastboot
run the oem ruu
goes to bootloader
and erases the user data and then starts sending
and thats it nothjing elses happens for hours
no instalation
what can i do?
Does the phone has unlocked bootloader? If yes it could be why. You can't go back to stock ruu unless you have locked bootloader. Try relock it before you flash ruu.
phidung3721 said:
Does the phone has unlocked bootloader? If yes it could be why. You can't go back to stock ruu unless you have locked bootloader. Try relock it before you flash ruu.
Click to expand...
Click to collapse
it says tampered locked
it was new when sold
customer dont know how to do the
bootloader unlocking
The carrier ID (CID) of the phone needs to match the CID for the RUU, or you need the phone to have SuperCID. That may be your problem also.
Need more details on what version (carrier) of the phone you have, and which RUU you are trying to run.
If it was having an issue, you would get an error telking you why it failed. If it gets as far as to start the process it recognizes the phone and is worjing properly. On slower pc's the process can take up to an hour ive seen. Start the procesz and do not touch it unless it finishes the process, or gives u an error of some sort. As long as it says sending, its sending and let her do her thing.
---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------
You can also select the recovery option when your in bootloader. Once in recovery select the factory reset option, then reboot.
all night long and nothing
D:\Elman Ortega\Desktop\android>f
cid: CWS__001
finished. total time: 0.003s
D:\Elman Ortega\Desktop\android>
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
mine is a quadcore 3.6ghz desktop pc
1.09.0000
radio 0.16.32.09.01
Your in fastboot right there. From right there you can type
fastboot erase cache
Then
fastboot reboot
Or
Fastboot erase cache
Then
Fastboot reboot recovery
Then do a factory reset
18th.abn said:
Your in fastboot right there. From right there you can type
fastboot erase cache
Then
fastboot reboot
Or
Fastboot erase cache
Then
Fastboot reboot recovery
Then do a factory reset
Click to expand...
Click to collapse
Can you do a factory reset with a stock recovery?
Sent from my HTC One XL using Forum Runner
Absolutely
18th.abn said:
Absolutely
Click to expand...
Click to collapse
Hi I actually haVE THE SAME PROBLEM.
THis is how it happened
MIUI
CM10
MIUI
Stock
MIUI
Clear Cache
SD card not recognised in TWRP
Tried Factory reset, system cache etc
RUU failed
Unplugged
Not recognised by Windows but can by mac
Flashed hBoot from the RUU
Now bricked
Still have lights, TWRP, HBOOT
Please help!!!
PM me or hit me up on gtalk. Ill help you out
XsMagical said:
PM me or hit me up on gtalk. Ill help you out
Click to expand...
Click to collapse
Sorry but i'm very new, how to pm you
cw99, having twrp and hboot is very very very far away from a brick.
odds are you made the mistake of factory reset inside the phone or bootloader instead of in twrp only. only time i made that mistake i just ran the ruu and never plan on making the mistake again. others might have done it for testing purposes to find ways to properly revive it without needing to run ruu.
with newest twrp 2.3 you might be able to get away with adb sideload flashing of a rom if that works. then format internal storage once you boot into rom.
DvineLord said:
cw99, having twrp and hboot is very very very far away from a brick.
odds are you made the mistake of factory reset inside the phone or bootloader instead of in twrp only. only time i made that mistake i just ran the ruu and never plan on making the mistake again. others might have done it for testing purposes to find ways to properly revive it without needing to run ruu.
with newest twrp 2.3 you might be able to get away with adb sideload flashing of a rom if that works. then format internal storage once you boot into rom.
Click to expand...
Click to collapse
Hi I tried it but it did not work. When I clicked ADB SIDELOAD, they said mounting of storage failed and hence I cannot enter it.
XsMagical said:
PM me or hit me up on gtalk. Ill help you out
Click to expand...
Click to collapse
Thanks XsMagical for the help! You really saved my life!
Awesome, what was the issue?
Okay so I have been running CM10 fine for months. But I got a notification about an OTA update to CM10.1 and decided to let it install... bad idea.
the install process failed somehow and then my phone was stuck at the HTC screen when booting. Booting into recovery wouldn't work because it would try to install the ROM but always fail. So I figured I could just flash my recovery and restore. So I download the newest TWRP and flasht he recovery. Once I get into TWRP I couldn't read the SDCARD or find any of my files. But if I use an adb shell I can see CM10.1 and Gapps for 4.2.2 So I tried restarting recovery a couple times but I could never get the recovery to see the files. I figured I would just relock the bootloader, run RUU, then start the rooting/unlocking process fresh as I have done in the past when I got into trouble. Only problem now is that I get error 155 when trying to run the RUU utility, and can't boot into recovery since I re-locked my bootloader. I can still use fastboot but that's it, HALP!
What ruu are you using? Error 155 usually means its the wrong ruu.
iElvis said:
What ruu are you using? Error 155 usually means its the wrong ruu.
Click to expand...
Click to collapse
I tried this one. http://forum.xda-developers.com/showthread.php?t=1814217
SkuzeeII said:
I tried this one. http://forum.xda-developers.com/showthread.php?t=1814217
Click to expand...
Click to collapse
Do you have an AT&T phone? Or something else?
I was able to get the RUU to work last time, but when I try to unlock using the X_Factor root it doesn't actually unlock the bootloader. I've done this plenty of times before and followed the steps correctly. Any idea what's going on?
SkuzeeII said:
I was able to get the RUU to work last time, but when I try to unlock using the X_Factor root it doesn't actually unlock the bootloader. I've done this plenty of times before and followed the steps correctly. Any idea what's going on?
Click to expand...
Click to collapse
unlock yourself using "fastboot flash unlocktoken Unlock_code.bin"
Right, just push your unlock token again. Once you unlock the first time, subsequent unlocks are a simple fastboot command.
iElvis said:
Right, just push your unlock token again. Once you unlock the first time, subsequent unlocks are a simple fastboot command.
Click to expand...
Click to collapse
I've been at the same issue myself.
Have tried using the toolkit and pushing manually. I can get to the screen where you choose yes/no to unlock, which I choose yes. Then the phone just shuts off. When I turn it back on, the factory reset is done but I'm still stuck at "RELOCKED". I've probably tried this 20 times tonight and do not know what I'm missing. My CID is still all 1s.
FYI, using 2.20 RUU (had a similar issue... CM10 nightly bricked phone completely so used 2.20 RUU to restore phone)
i sometimes have alot of problems getting token to stick. try booting into bootloader without phone plugged up to computer, once booted into bootloader plug in phone, then push the token.
I've found that you need to unplug and reboot your phone before pushing the token. When I do this, it always takes the first time.
Sent from my HTC One X using Tapatalk 2
So I found that I was rebooting the phone myself when I shouldn't have during the unlock process. So I've got it unlocked now, and I can install recovery like TWRP or CWM but now I'm trying to get a ROM to load. I'm using the last Evita CM10 build but it always gets stuck on the booting screen. I think maybe I need an update.zip or need to use adb to get root from fastboot or recovery but I can't remember how and searching hasn't helped me yet...
I'm going to try to do a fastboot flash boot boot.img with the boot.img file from my CM10 zip file. Maybe that's what I was missing
I really should just be more patient before creating a thread. I got into CM10 then got S-OFF so now I'm on CM10.1
Hello,
I cannot recover my Sensation anymore, so the experts in this forum are my last hope:
I suffered from "eMMC corruption" described in
http://forum.xda-developers.com/showthread.php?t=2542506
That meant that a RUU got stuck in the middle and after a reset the phone remains in "RUU mode". In order to fix the partition table I tried a lot of things. Among others, I reinstated S-ON (via fastboot writesecureflag 3) and lock (via fastboot oem lock) because I had read that RUU needs a locked bootloader.
In hindsight that was a very stupid thing to do, as RUU still fails. But now I cannot flash any recovery anymore.
I tried unlocking the phone again using the HTCDev method (fastboot flash unlocktoken Unlock_code.bin) but this seems to fail now - I supposed because I'm in RUU mode, not in the normal bootloader.
As a consequence, my phone is still in RUU mode but doesn't respond to fastboot commands anymore.
I've searched this forum but couldn't find a workable solution for my problem.
I could imagine the following ways out of it:
- somehow get out of RUU mode and back into the normal bootloader; I imagine the HTCDev unlock process works there
- find a different method of unlocking that doesn't require adb but only fastboot (I only know of Revolutionary, Juopunutbear and rumrunner S-OFF, all of which need working adb)
- somehow try to compose a RUU that has a shorter (not working) image for the partition that fails in order to complete RUU and get into the bootloader this way
Has anyone else any other idea for me how to proceed?
Thanks a lot in advance.
lotan_rm said:
Hello,
I cannot recover my Sensation anymore, so the experts in this forum are my last hope:
I suffered from "eMMC corruption" described in
http://forum.xda-developers.com/showthread.php?t=2542506
That meant that a RUU got stuck in the middle and after a reset the phone remains in "RUU mode". In order to fix the partition table I tried a lot of things. Among others, I reinstated S-ON (via fastboot writesecureflag 3) and lock (via fastboot oem lock) because I had read that RUU needs a locked bootloader.
In hindsight that was a very stupid thing to do, as RUU still fails. But now I cannot flash any recovery anymore.
I tried unlocking the phone again using the HTCDev method (fastboot flash unlocktoken Unlock_code.bin) but this seems to fail now - I supposed because I'm in RUU mode, not in the normal bootloader.
As a consequence, my phone is still in RUU mode but doesn't respond to fastboot commands anymore.
I've searched this forum but couldn't find a workable solution for my problem.
I could imagine the following ways out of it:
- somehow get out of RUU mode and back into the normal bootloader; I imagine the HTCDev unlock process works there
- find a different method of unlocking that doesn't require adb but only fastboot (I only know of Revolutionary, Juopunutbear and rumrunner S-OFF, all of which need working adb)
- somehow try to compose a RUU that has a shorter (not working) image for the partition that fails in order to complete RUU and get into the bootloader this way
Has anyone else any other idea for me how to proceed?
Thanks a lot in advance.
Click to expand...
Click to collapse
Hi this is for another device but u can have a look, the thread title is "how to flash a rom in ruu mode" i dunno tho.
http://forum.xda-developers.com/showthread.php?t=1087164
jmcclue said:
Hi this is for another device but u can have a look, the thread title is "how to flash a rom in ruu mode" i dunno tho.
http://forum.xda-developers.com/showthread.php?t=1087164
Click to expand...
Click to collapse
jmcclue: Thank you for the link to the thread. Unfortunately, that doesn't help me because the eMMC bug causes an RUU to never finish. It always get stuck somewhere in the middle. As a consequence, it always stays in RUU mode.
lotan_rm said:
jmcclue: Thank you for the link to the thread. Unfortunately, that doesn't help me because the eMMC bug causes an RUU to never finish. It always get stuck somewhere in the middle. As a consequence, it always stays in RUU mode.
Click to expand...
Click to collapse
I'm afraid that even if you find a way to gain S-Off again or an unlocked bootloader, you won't find a way to fix the eMMC.
I think it's like a broken flash drive, you won't ever be able to fix it.
Sajito said:
I'm afraid that even if you find a way to gain S-Off again or an unlocked bootloader, you won't find a way to fix the eMMC.
I think it's like a broken flash drive, you won't ever be able to fix it.
Click to expand...
Click to collapse
Are you sure repartitioning wouldn't help. I've found a friend who has a Sensation as well (working of course) and I would've tried remodelling the partition table after his'.
lotan_rm said:
Are you sure repartitioning wouldn't help. I've found a friend who has a Sensation as well (working of course) and I would've tried remodelling the partition table after his'.
Click to expand...
Click to collapse
I'm not 100% sure, you can always try.
I'm not even 50% sure it would work but I'd hate giving up on an otherwise good phone.
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
kunalrokz said:
Hey Guys! so recently I purchased Sunshine to S-OFF my SPRINT HTC U11. I changed the CID to unlocked version BS_US001 to flash the unlocked RUU. it kept on failing because the bootloader was unlocked. so then I typed the worst command ever "fastboot oem lock" and now my bootloader is locked, device is S ON, and the worst part is that the bootloader comes up saying that the device is corrupted and cannot be trusted. Now I cannot get into twrp, or my rom. because I changed the CID I can't use my original RUU to revert back. Moreover the android OS version in the download mode comes up as 1.28.651.3 and the unlocked RUU which could work is 1.16.617.6 . The unlocked RUU gives me an error that the android versions either missing or set to 1 and the sprint RUU gives me Invalid Customer ID error. I have access to fastboot. I need a way to change the CID back to SPCS_001. I know I should've used superCID but I panicked while doing all the steps. if anyone could give me or provide me with a way to create a sprint rom.zip which is signed and has a modified android-info.txt including the CID for my phone. I cannot unlock my bootloader as it expects bootloader unlocking to be turned on the android system which unfortunately has been factory reset due to the corruption and is no longer booting. if there is a way to S OFF via fastboot then I can recover. please help me. I have good experience with flashing roms and messing with this stuff but I was out of the android scene for 2 years until recently when I got the U11.
Click to expand...
Click to collapse
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
Thanks I'll try it out shortly!!
kunalrokz said:
Thanks I'll try it out shortly!!
Click to expand...
Click to collapse
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
I'm on the same boat as you... Any news?
wranglerray said:
Maybe try to reflash the unlock token again from fastboot and get the bootloader unlocked and reflash twrp
Click to expand...
Click to collapse
The unlock token wont flash gives me a permission error. I will post the exact error in a while.
OMJ said:
sounds like you're in a pickle....someone had a similar issue, read here
you may be able to boot into twrp via fastboot boot twrp-3.1.1-0-ocn.img while in bootloader
then you could try either erasing OS version or changing it
good luck!
Click to expand...
Click to collapse
I tried your recommendation but to no avail. when I boot into the bootloader and send the fastboot command it gives me error "FAILED (remote: GetVar Variable Not found)" and when I do it in download mode it says okay and gets stuck on booting... the phone itself downloads the recovery and displays flash images success (1/1) but nothing else happens.
HOWEVER after sending that command I tried the unlock bootloader command and miraculously it WORKED! I got access to recovery!! I think that being in the download mode explicitly helped the bootloader recognize the unlock token.
zopostyle said:
I'm on the same boat as you... Any news?
Click to expand...
Click to collapse
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
Good to hear!
Cheers
Your neighbor to the south
kunalrokz said:
I tried the fastboot boot twrp-3.1.1-0-ocn.img command as recommended by @OMJ which got stuck on booting...
I then pressed ctrl+c which exits out of the stuck command and allows you to type "fastboot flash unlocktoken unlock_code.bin"
Somehow the bootloader got unlock which removed the device corruption check and I was able to boot.
@wranglerray and @OMJ thank you so much for your help
Click to expand...
Click to collapse
sweet!
zopostyle said:
I was able to boot to recovery only... Couldn't make any rom boot,don't know where I'm going wrong...
Click to expand...
Click to collapse
stock recovery or twrp? you'll need to give more specifics...
OMJ said:
sweet!
stock recovery or twrp? you'll need to give more specifics...
Click to expand...
Click to collapse
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
zopostyle said:
With both, I flashed twrp tried to restore a nandroid backup and it stop at the black screen with HTC and powered by android.
I've also tried with stock recovery flash a RUU from SDCard, but I receives Error 14.
What I did was change this:
(bootloader) mid: 2PZC10000
(bootloader) cid: VODAP110
To this:
modelid: 2PZC50000
cidnum: BS_US001
I also tried to change the mainver from 1.27.166.7 to 1.16.617.6, and without it.
RUU from SDCard or PC always give me error 14 or 8.
Oh forgot to mention, when I'm in twrp I always get a message Failed to mount /cota (Invalid Argument)
Click to expand...
Click to collapse
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
kunalrokz said:
I would recommend flashing a custom rom. I'm going to take a wild guess and say that you successfully unlocked your bootloader. if that's the case then you just reflashed twrp on an unlocked bootloader. now because you're trying to downgrade your OS you need S OFF.
not sure about the mounting error in twrp. maybe try fastboot -w in download mode. sounds like the file system is corrupt. but once you're able to install a rom, use any custom rom and get sunshine for s off. the s off will allow you to downgrade using RUU mode. make sure you get the new htc_fastboot.exe from the temp folder of the RUU that you want to install.
Click to expand...
Click to collapse
Hum, OK, thanks.
Yes, my bootloader is unlocked and I can flash recovery and boot.img successfully.
I'm at work right now at night I'm gonna try that fastboot -w option.
About the custom rom I've already tried leeDroid and MaximusHD but none of then booted.
What is this?
Failed to mount '/cota' (invalid argument)
AndrzejQ said:
What is this?
Failed to mount '/cota' (invalid argument)
Click to expand...
Click to collapse
An error that I received.
I got it working already.
i have the same problem. had you worked this out ? what's the solution ?
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Void tracer said:
Same issue , but i can't unlock the phone's bootloader , it gives me the message about ticking allow bootloader unlock in developer options but i can't access the OS...
Click to expand...
Click to collapse
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
MSMC said:
Same here. It doesn't say that, but o know that's what my error messages mean because when I did this before, I forgot to tick that option in developer options. Now, since after I flashed leedroid, I haven't checked that box again, and now I can't boot. I was simply trying to relock the bootloader to get rid of that annoying message everytime it turned on, then this corrupt error pops up. Please someone lead us in the direction of the fix, even if that fix happens to be get a new phone, just so I have closure, tho I have a hard time giving up and I kinda never believed that a device can be fully "bricked," just super locked.
Click to expand...
Click to collapse
I can't guarantee this will work, but try the following:
Use the spreadsheet here to find the latest RUU for your phone's CID and MID.
Rename the downloaded RUU to 2PZCIMG.zip
Move 2PZCIMG.zip to the root of your external SD card. If you don't have an external SD card you'll need to get one. If using a PC make sure to format the card as exFAT.
Follow the instructions at 'https://www.the custom droid.com/how-to-restore-htc-u11-stock-firmware/#Method-1-Flashing-RUU-in-Download-Mode' to flash the RUU to your phone.
Good luck!
EDIT: I don't why but XDA forums are filtering the string c u s t o m d r o i d (w/o the spaces)