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?!! ((

no devices found on list of adb attached

Hi all.
Please help me fix my HTC One X!! I am trying to restore my phone back to its former glory after a failed attempt to upgrade to Jelly Beans. I installed Clockwork Recovery by
c:\Fastboot>fastboot flash recovery recovery-clockwork-touch-5.8.2.4-endeavouru.
img
sending 'recovery' (5452 KB)... OKAY [ 0.701s]
writing 'recovery'... INFOFormat partition SOS done
OKAY [ 0.556s]
finished. total time: 1.257s
However now I can not seem to mount my sdcard!! I have tried
c:\AndroidSDK\tools\platform-tools>adb devices
List of devices attached
>>>> which lists nothing!!
I need to put the operating system back on, but I am at a loss for what to do next after hours searching fruitlessly.
Please help if you can!!
Zugz

Why would you use such an ancient version of clockworkmod? You want 5.8.4.0, then you can mount SD card from recovery. And charge. Both good things

Try to install Android revolution ,then if you want follow going to stock threat :reboot to bootloader and flash rom boot.img , erase cache , boot into recovery bootloader->hboot->recovery or if it dont work try to flash recovery again than do full wipe and flash rom.zip
You can now boot system
Sent from my HTC One X using xda app-developers app

I updated
ms0 said:
Try to install Android revolution ,then if you want follow going to stock threat :reboot to bootloader and flash rom boot.img , erase cache , boot into recovery bootloader->hboot->recovery or if it dont work try to flash recovery again than do full wipe and flash rom.zip
You can now boot system
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I updated to
c:\Fastboot>fastboot flash recovery recovery-clockwork-5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)... OKAY [ 0.738s]
writing 'recovery'... INFOFormat partition SOS done
OKAY [ 0.564s]
finished. total time: 1.304s
But I still didn't get can't seem to mount the sd card.
c:\AndroidSDK\tools\platform-tools>adb devices
List of devices attached
>>> still finds nothing.
Please would someone mind giving me basic instructions as how to go about remounting the sd card?
@ms0, I installed the Android Revolution, but I didn't understand your instructions properly.
Thanks for the messages so far, I am still very stuck

1) go into recovery
2) mount storage as USB.

When you're in fastboot it won't show in adb - you need android running for that
Sent from my HTC One X using xda premium

Adb only work when booted in system.
Sdcard mount can work in system and recovery.
To install recovery or system you can use fastboot command in bootloader
(Phone connected to USB and in bootloader-fastboot
Tab.)
To enter bootloader just shut down your phone (hold power for 10sec)and hold both vol- and power button.
When you are in bootloader on your computer you can run
Fastboot flash recovery -filename-.img
to flash recovery
Fastboot flash boot boot.img to flash rom kernel (you must also do fastboot erase cache ).
When this is done on your phone you can go to main bootloader screen and from there you can enter recovery and flash rom itself. Now you should be able to boot system and check usb debuging in settings . You should now be able to connect to adb if this don't work make sure you have proper drivers on your computer (HTC sync manager and Android sdk.)
Sorry for bad english - i hate htc keyboard
Sent from my HTC One X using xda app-developers app

Unable to Boot to Recovery with TWRP

I flashed clockworkmod recovery a couple days ago, not knowing that TWRP was out there. I'm trying to flash TWRP but now my phone won't boot into recovery after flashing. I tried erasing the cache and still no luck. Here's how I did it
Code:
#fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.672s]
finished. total time: 0.672s
# fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.116s]
writing 'recovery'...
OKAY [ 0.877s]
finished. total time: 1.992s
Then when I try to boot into recovery I get the HTC logo with pink text saying it's booting into recovery, it stalls, and then reboots normally. I'm running CM 10.2 and using adb in linux mint.

i had the same problem, i just left clockwork on there, i gave up after flashing it like 30 times. I did all the exact same things as you. Also checked the MD5 and verified what i had was what it was. Just letting you know i had the same problem as you, id love to find a answer myself. BTW you can still flash clockwork back on it to do recoveries.

I've come across more than one person online who has the same problem too but no definative answer.

I wonder what would happen if you wiped the recovery partition in CWM and then tried flashing twrp...

What if you tried the recovery in the thread about taking the update. And then flash twrp...worth a shot.
Sent from my One.

Chilidog said:
I wonder what would happen if you wiped the recovery partition in CWM and then tried flashing twrp...
Click to expand...
Click to collapse
I'll give that a shot this afternoon.
brymaster5000 said:
What if you tried the recovery in the thread about taking the update. And then flash twrp...worth a shot.
Sent from my One.
Click to expand...
Click to collapse
Which thread are you referring to?

I had this same issue , here is what I did to fix the issue . I flashed a modded hboot to remove the red text and now I boot into recovery every time .

cbrown245 said:
I had this same issue , here is what I did to fix the issue . I flashed a modded hboot to remove the red text and now I boot into recovery every time .
Click to expand...
Click to collapse
Hmmmm, now you got me.... Still doesnt explain why it works for some and not others

cowmoo32 said:
I flashed clockworkmod recovery a couple days ago, not knowing that TWRP was out there. I'm trying to flash TWRP but now my phone won't boot into recovery after flashing. I tried erasing the cache and still no luck. Here's how I did it
Code:
#fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.672s]
finished. total time: 0.672s
# fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (8432 KB)...
OKAY [ 1.116s]
writing 'recovery'...
OKAY [ 0.877s]
finished. total time: 1.992s
Then when I try to boot into recovery I get the HTC logo with pink text saying it's booting into recovery, it stalls, and then reboots normally. I'm running CM 10.2 and using adb in linux mint.
Click to expand...
Click to collapse
You're using the wrong image for TWRP on the HTC One. What you want is
"openrecovery-twrp-2.6.3.0-m7vzw.img".

I had a problem while trying to flash TWRP as well (I got my root and s-off with rumrun) , I'm just going to stick with CM, its much simpler anyway.

cowmoo32 said:
I'll give that a shot this afternoon.
Which thread are you referring to?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2469057
Sent from my Oney Bone.

Cant get into Recovery (clockwordk mod / twrp)

hy!
in fastboot i unlocked the nexus 7. I then flashed recovery of clockword mod and twrp but with both i end up on "google" screen with the unlocked lock symbol. After some time it boots in to stock rom. How do i get to run recovery?
i used:
sudo fastboot flash recovery <filename>..
also i cant lock it anymore, it gives me an error.
what i am trying to do? i want to root the device via a recovery rom as towelroot does not work and i dont have a modstring for the nexus 7 for towelroot. i then want to run fstrim as the device is completely nutty slow. maybe install a custom rom- anyone has a source for a good cm?
thx!
versions i tried:
recovery-clockwork-touch-6.0.4.3-flo.img
twrp-2.6.3.1-flo.img
twrp-3.1.1-0-flo.img
update: now i somehow managed to change from the "google with unlocked symbol" screen to the "fallen android" screen. that means no recovery is found.. i dont get it. after booting into stock rom after the unlocking of the bootloader i re-enabled usb debugging of course.
recovery writing ocurs very fast and no info the nexus 7 screen is displayed:
twrp-3.1.1-0-flo.imgsending 'recovery' (8962 KB)...
OKAY [ 1.115s]
writing 'recovery'...
OKAY [ 0.367s]
finished. total time: 1.482s

i tried with v 2.4. of team win recovery, which did install and execute

ok, got it up an running, dont know why it didnt want at first, but its all ok.
used twr3xx
and lineage11
and gapps pica
works
nice tut:
https://cd-rw.org/t/resurrect-a-nexus-7-2012-to-run-as-good-as-new/141
nice rom:
https://forum.xda-developers.com/ne...fficial-build-cyanogenmod-11-0-nexus-t3174831

can't unlock bootloader

Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?

Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem

amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?

Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse

Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk

n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%

n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here

Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.

Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk

tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.

Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery

Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here

Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here

tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...

amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2​) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools

jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.