Develop Bugs

[Q] stuck on htc quietly brilliant screen

Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.

You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium

Thanks sir, I'll try.

sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.

thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card

sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too

dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.

See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA

Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.

"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command

sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA

Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!

Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.

Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!

I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?

All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot

i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.

mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?

When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s

Nobody can help me?!! ((

Botched my old recovery, and can't flash a new one...help?

I've been playing around with some of the JB ROMs, and was using Goo Manager and TWRP to do it. Then, because I'm an idiot, I decided I wanted to upgrade TWRP to 2.3.3.0 (I think I was running 2.3.1.0).
That's when I ran into the "TWRP doesn't always install properly" problem. I've now tried updating TWRP from within Goo Manager more than 5 times, but it's not working.
So I decided I'd install the new recovery via the FASTBOOT method.
I have HBOOT 0.92. I have ADB and FASTBOOT loaded on my laptop. (I'm pretty sure this is the way I originally installed CWM 5.0.2.0 when I first rooted my phone ages ago.)
When I boot the phone into the bootloader and choose FASTBOOT, then plug it into my laptop, I get the "FASTBOOT USB" indication that it's connected, so that's good.
However, when I open a terminal window on my laptop, navigate to my miniadb folder (where the fastboot.exe and recovery images are located), and try to flash the recovery image, I see the green bar in the upper right corner of the phone, but on the laptop I get this:
c:\miniadb>fastboot flash recovery openrecovery-twrp-2.3.3.0-inc.img
sending 'recovery' (3642 KB)... OKAY [ 11.235s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 11.268s
So then I decided to give up on TWRP and go back to CWM, but there's no joy there, either:
c:\miniadb>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 12.370s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 12.402s
What causes the "FAILED (remote: not allowed)" response? Clearly I'm sending the data to the phone, but the phone's rejecting it for some reason.
Does anyone have a suggestion for a foolproof way to get a recovery (either CWM or TWRP--at this point, I'm not picky!) back on my phone?
Thanks!
MC

Check the last two pages of the tarp thread for a twrp hboot PB31IMG.ZIP or see my direct link below.
http://goo.im/devs/tiny4579/mods/PB31IMG-TWRP-2.3.3.0.zip
This method works without fastboot.
Sent from my Galaxy Nexus using Tapatalk 2

Many thanks, tiny! I'll give that a shot.

MysticCobra said:
What causes the "FAILED (remote: not allowed)" response? Clearly I'm sending the data to the phone, but the phone's rejecting it for some reason.
Click to expand...
Click to collapse
For what it's worth, I think you need to upgrade HBOOT to 1.02 or 1.07 and unlock it through htcdev to be able to use the fastboot flash commands. But the flashable zip for TWRP should fix it for you too and that way is easier and just as reliable.

HTC One M8 Root failed - Australia

Hi there,
I have just tried to root my HTC one, and I am now stuck in the boot loader screen and it is showing *Tampered* at the top.
Can someone please advise me, or point in the direction of what I need to do now?
Thanks.

If it says tampered it should say unlocked right below it.... go to this site and follow the instructions to get full root. http://forum.xda-developers.com/showthread.php?t=2699065

jeanxx said:
If it says tampered it should say unlocked right below it.... go to this site and follow the instructions to get full root. http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
I should have mentioned that I only have a Mac.....
Yes it does say unlocked underneath it...
Suggestions?

millhhaus said:
I should have mentioned that I only have a Mac.....
Yes it does say unlocked underneath it...
Suggestions?
Click to expand...
Click to collapse
Once you have unlocked your bootloader then it will show you tampered.
Download a custom recovery (I prefer TWRP) and flash it via fastboot.
Then download @Chainfire Supersu flashable zip from his site and flash it in recovery.
You have rooted your phone.

Ater placing my device into fastboot mode, I have tried flashing my downloaded TWRP file to my HTC One in Terminal using these instructions:
Now let's flash your downloaded TWRP file to your HTC One. Type one of the following commands into your terminal window, depending on which file you downloaded above.
For the International editions, type:
fastboot flash recovery Desktop/openrecovery-twrp-2.7.0.2-m8.img
However I get the following error:
command not found
any help would be most appreciated.

Did you setup your mac to use adb / fastboot commands?

lazydesi said:
Did you setup your mac to use adb / fastboot commabds?
Click to expand...
Click to collapse
I feel like a total N00b at the moment. LOL.
No. How do I do that?

try this
http://forum.xda-developers.com/showthread.php?t=2638673

Thanks for that information.
Now, when I am trying and to flash TWRP via fastboot I am getting this error message:
ERROR: Unable to create a plug-in (e00002c7)
< waiting for device >
ERROR: Unable to create a plug-in (e00002c7)

millhhaus said:
Thanks for that information.
Now, when I am trying and to flash TWRP via fastboot I am getting this error message:
ERROR: Unable to create a plug-in (e00002c7)
< waiting for device >
ERROR: Unable to create a plug-in (e00002c7)
Click to expand...
Click to collapse
hi,
plz try CWM, M8 got some issues with twrp.
philz_touch_6.26.6-m8.img is the stable version plz try that.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8

So I am starting to move forward :
I have followed the instructions to install philz_touch_6.25.5-m8.img by flashing it to my HTC where I get the setup screen for philz_touch_6.25.5-m8.img. I cleared the cache and I then installed the UPDATE-SuperSU-vx.xx.zip using the install zip from sdcard and then rebooted the HTC.
Unfortunately I have come back to the bootloader screen.
For what the instructions say it should be working now, but it does not seem to be?
Now it seems that whatever I try I cant seem to get past the bootloader....
And when I power down from the bootloader, It shuts down for a few minutes and then boots back into the bootloader.
Not sure what to do now?

millhhaus said:
So I am starting to move forward :
I have followed the instructions to install philz_touch_6.25.5-m8.img by flashing it to my HTC where I get the setup screen for philz_touch_6.25.5-m8.img. I cleared the cache and I then installed the UPDATE-SuperSU-vx.xx.zip using the install zip from sdcard and then rebooted the HTC.
Unfortunately I have come back to the bootloader screen.
For what the instructions say it should be working now, but it does not seem to be?
Now it seems that whatever I try I cant seem to get past the bootloader....
And when I power down from the bootloader, It shuts down for a few minutes and then boots back into the bootloader.
Not sure what to do now?
Click to expand...
Click to collapse
is your problem similar to this?
http://forum.xda-developers.com/showthread.php?t=2784232

May be you are using the wrong version.If you have international device you should try international version of philz/cwm recovery.I would suggest you to use TWRP since it is basically meant for htc devices.

Why am I getting this "FAILED (remote: image error! (BootMagic check fail))" error message all the time?
Davids-MacBook-Air:desktop millhhaus$ fastboot flash boot cm-10.2.1-m7ul.zip
target reported max download size of 1830711296 bytes
sending 'boot' (198067 KB)...
OKAY [ 6.904s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 6.905s

millhhaus said:
Why am I getting this "FAILED (remote: image error! (BootMagic check fail))" error message all the time?
Davids-MacBook-Air:desktop millhhaus$ fastboot flash boot cm-10.2.1-m7ul.zip
target reported max download size of 1830711296 bytes
sending 'boot' (198067 KB)...
OKAY [ 6.904s]
writing 'boot'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 6.905s
Click to expand...
Click to collapse
because you are using M7 files mate. you need to use M8.
M7 - Htc one - 2013 model
M8 - Htc One - 2014 model
http://download.cyanogenmod.org/?device=m8

writing 'bootloader_b'... FAILED

I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot.
I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD.
----------------------------------------------
D:\Download\platform-tools-Flash>fastboot flash bootloader bootloader-taimen-tmz12a.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.097s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.107s
D:\Download\platform-tools-Flash>
------------------------------------------------
I can not use the new phone anymore, please help to check my problem. Thanks.

Have you performed in fastboot Mode, at any time, this command: "fastboot flashing unlock_critical" ? (Without " ")

You can't flash factory image in recovery, it has to be done in bootloader mode, also can you boot in bootloader? Is your bootloader locked or unlocked?

Beast38 said:
I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot. I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD. I can not use the new phone anymore, please help to check my problem. Thanks.
Click to expand...
Click to collapse
Apparently you have not unlocked your bootloader (critical) correctly. There are two separate commands needed to fully unlock it. That and you can't flash images from Recovery mode, you flash while in Bootloader mode. Read and follow the directions found on the same page you downloaded the image from HERE.

Thanks all. I re-check all procedure and re-do all process. It finally works fine for now.
I can not sure which step went wrong. All I know is "unlock done" "root failed or not complete".

soft brick solution

hi, long story, solution needed, help!
I was on evolutin x + orange fox recovery.. was working pretty fine for 2 months.. I was using chrome and all of a sudden the phone just froze and I had to force shut it down..
now it boot loops.. ofox stays on welcome screen and doesnt go past it..
tried "fastboot clear userdata".. then tried " fastboot flash recovery recovery.img" it gives out error
--
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (47472 KB)...
OKAY [ 1.008s]
writing 'recovery'...
FAILED (remote: Error flashing partition : Write Protected)
finished. total time: 1.099s
--
tried flashing stock fastboot rom via miflashtool it says "Flash xbl error"
bootloader is unlocked aswell
what to do now? any help much appreciated..