Develop Bugs

[Q] Stuck on splash after Hboot flash

Edit - Problem was after flashing hboot I could not boot into recovery .... I tried multiple recovery images AmonRa and Cwm but it would never boot.
Solved - I have no idea how, I downloaded the recovery image again with the same link as the previous images, all md5sums were ok, but the 4th download worked and I was able to flash + boot into recovery again? Do I have some other problem though because I don't see why it took so many flashes for me to be able to access recovery again?
Alphrev Cm7 r2
Bravo PVT1 Ship S- OFF
Hboot-6.83.1002
Radio-5.17:52.18
C:\android\tools>fastboot devices
HT~~####93 fastboot
C:\android\tools>fastboot flash hboot bravo_alphaspl-cm7r2.img
sending 'hboot' (512 KB)...
OKAY [ 0.096s]
writing 'hboot'...
OKAY [ 0.164s]
finished. total time: 0.261s
C:\android\tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\android\tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.039s]
finished. total time: 0.040s
Reboot to recovery - stuck on splash??? Using Reflex S...
Edit - After trying to boot to recovery, sat on splash screen for 40 mins and then my bootanimation randomly started... everything is just back to normal?
I can't seem to be able to flash recovery though, it just doesn't boot into it?! I've tried a couple of images and checked md5sum's but it always sticks on splash??

hmm that's strange, suppose you could try to flash a different HBOOT, then try a different recovery - that's what I'd do anyway

bortak said:
hmm that's strange, suppose you could try to flash a different HBOOT, then try a different recovery - that's what I'd do anyway
Click to expand...
Click to collapse
I shouldn't of posted really but something that usually take 10 minutes took an hour or two.... I used the exact command everytime and the same files... It just didn't work!? I'm still really confused but happy it's working

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

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.

[Q] i think i briked my Htc one x

Hi
Last year i was using Android Revolution custom firmware, after which i went back to stock, i stayed with stock about 1 year , then yesterday tried install Android Revolution HD, but i think i mess it up big time because i am stuck in boot screen . I tried looking for a RUU but apparently my phone is using a newer version of RUU which i can not find. I spent 1 day looking for solutions but none helped, now i am stuck. Please help. Sorry for my English , Thank You

give more info : hboot number ? what recovery ? flashed the boot.img ?

Mr Hofs said:
give more info : hboot number ? what recovery ? flashed the boot.img ?
Click to expand...
Click to collapse
version-main: 4.18.401.2, hboot 1.72.000 .recovery-clockwork-touch-5.8.4.0-endeavoru , 5.1204.167.31
. i think i flashed the boot.img , at least one of them, i did a lot of flashing , trying to recover from my mistakes

okey here we go, first flash this recovery (for working touch in recovery)
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
then you flash the boot.img from the rom.zip (copy it again to the fastboot folder and make sure its the correct one)
then enter the recovery and perform a full wipe
- factory reset (full)
- wipe cache partition
- ADVANCED - wipe dalvik cache
- MOUNTS & STORAGE - format cache, data, system
then install the rom.zip and reboot

Mr Hofs said:
okey here we go, first flash this recovery (for working touch in recovery)
https://www.dropbox.com/s/yqzlpqo8illa53j/Philz recovery 5.15.9.img
then you flash the boot.img from the rom.zip (copy it again to the fastboot folder and make sure its the correct one)
then enter the recovery and perform a full wipe
- factory reset (full)
- wipe cache partition
- ADVANCED - wipe dalvik cache
- MOUNTS & STORAGE - format cache, data, system
then install the rom.zip and reboot
Click to expand...
Click to collapse
just waiting to charge a little bit, because i can not flash anymore, As soon as i charge my phone i will fallow you instructions and revert with updates. Thanks

ursache marian said:
just waiting to charge a little bit, because i can not flash anymore, As soon as i charge my phone i will fallow you instructions and revert with updates. Thanks
Click to expand...
Click to collapse
make sure you charge inside the recovery, it does not charge in bootloader or the bootscreen !

Mr Hofs said:
make sure you charge inside the recovery, it does not charge in bootloader or the bootscreen !
Click to expand...
Click to collapse
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 1.369s
any suggestions ?
I found that batch file in other post , and i just started charging now.

ursache marian said:
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.159s]
writing 'recovery'...
FAILED (remote: battery low)
finished. total time: 1.369s
any suggestions ?
Click to expand...
Click to collapse
yea put your phone in the recovery and hook it up to the main charger !!! and leave it there for 2 hours

Mr Hofs said:
yea put your phone in the recovery and hook it up to the main charger !!! and leave it there for 2 hours
Click to expand...
Click to collapse
I can not access recovery , it's staying only in boot menu , but i found a batch file witch apparently if i run it it will charge the phone for me to be able to flash the recovery that you sent .

Yeah cool. How many mV is it ?

Mr Hofs said:
Yeah cool. How many mV is it ?
Click to expand...
Click to collapse
Managed to charge so i can flash , but no luck
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.172s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.379s.

ursache marian said:
Managed to charge so i can flash , but no luck
C:\New folder>fastboot flash recovery "Philz recovery 5.15.9.img"
sending 'recovery' (8050 KB)...
OKAY [ 1.172s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.379s.
Click to expand...
Click to collapse
remote not allowed indicates a relocked/locked bootloader ! and to be sure rename the recovery to just recovery.img
fastboot flash recovery recovery.img
fastboot erase cache

Mr Hofs said:
remote not allowed indicates a relocked/locked bootloader ! and to be sure rename the recovery to just recovery.img
fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
C:\New folder>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.167s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.377s
C:\New folder>fastboot erase cache
erasing 'cache'...
OKAY [ 0.217s]
finished. total time: 0.217s
C:\New folder>fastboot flash recovery recovery.img
sending 'recovery' (8050 KB)...
OKAY [ 1.169s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.378s

unlock the bootloader !

Mr Hofs said:
unlock the bootloader !
Click to expand...
Click to collapse
OK, bootloader unlocked , flashed your recovery, now waiting for it to charge a little bit more. After i do a recovery wipe , i would like to install Android revolution HD, Yesterday i got stuck when i installed android revol HD becouse i couldn't select "next" button, my touch was not working, and using the Up and Down buttons was impossible. Now i see that in this recovery touch is working so maybe i will be able to install this Android HD firmware afterall.
Thank you for you help

ursache marian said:
OK, bootloader unlocked , flashed your recovery, now waiting for it to charge a little bit more. After i do a recovery wipe , i would like to install Android revolution HD, Yesterday i got stuck when i installed android revol HD becouse i couldn't select "next" button, my touch was not working, and using the Up and Down buttons was impossible. Now i see that in this recovery touch is working so maybe i will be able to install this Android HD firmware afterall.
Thank you for you help
Click to expand...
Click to collapse
no problem, let me know the result

Mr Hofs said:
no problem, let me know the result
Click to expand...
Click to collapse
i managed to flash boot and flash android hd 31.3 with your recovery.img, on mine the touch was not working . Thank you again.

Okidoki !
CASE CLOSED !

"fastboot flash recovery" went OK but the recovery didn't change

. . I have an old One X here, unused for a looong time. Recently I tried to update it and started the process by updating my Recovery (to TWRP 2.6.3.0). Soon after that I found out that most new ROMs have a new partitioning schema and I needed to switch. When trying to update the recovery, I used the fastboot flash and it went ok:
Code:
$ ./fastboot flash recovery /d/twrp2853-BiG.img
sending 'recovery' (8090 KB)...
OKAY [1.134s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [0.687s]
finished. total time: 1.820s
. . After that I did the "fastboot erase cache":
Code:
$ ./fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.213s]
finished. total time: 0.213s
. . Then I rebooted into recovery directly--I know about ROMs that flash the stock recovery when first booting, but this is not applicable to this case since I'm in a custom ROM and booting directly to recovery--, but it is still the old recovery (2.6.3.0). I tried flashing older recoveries (2.6.1.0) and repeating the process every way I could think of (more "erase caches", more "flash recovery"ies etc) but I'm stuck in this 2.6.3.0 version. The weird thing is that I flashed this version yesterday and it went all smoothly, no problems at all (flash recovery, erase cache, reboot).
. . Any tips or ideas why it is not working anymore? I want to update it to change to the new layout so I can flash new ROMs, but this it really blocking the process.

Did you try to wipe your HOX including /data as well as /system partition? This - in the guide if how to achieve new storage layout - is one of the important prerequisites and done prior to flashing the TWRP.BIG
Send by the swarm intelligence of my coffee machine (AKA HTC One M9).

dsnunes said:
. . I have an old One X here, unused for a looong time. Recently I tried to update it and started the process by updating my Recovery (to TWRP 2.6.3.0). Soon after that I found out that most new ROMs have a new partitioning schema and I needed to switch. When trying to update the recovery, I used the fastboot flash and it went ok:
Code:
$ ./fastboot flash recovery /d/twrp2853-BiG.img
sending 'recovery' (8090 KB)...
OKAY [1.134s]
writing 'recovery'...
(bootloader) Format partition SOS done
OKAY [0.687s]
finished. total time: 1.820s
. . After that I did the "fastboot erase cache":
Code:
$ ./fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.213s]
finished. total time: 0.213s
. . Then I rebooted into recovery directly--I know about ROMs that flash the stock recovery when first booting, but this is not applicable to this case since I'm in a custom ROM and booting directly to recovery--, but it is still the old recovery (2.6.3.0). I tried flashing older recoveries (2.6.1.0) and repeating the process every way I could think of (more "erase caches", more "flash recovery"ies etc) but I'm stuck in this 2.6.3.0 version. The weird thing is that I flashed this version yesterday and it went all smoothly, no problems at all (flash recovery, erase cache, reboot).
. . Any tips or ideas why it is not working anymore? I want to update it to change to the new layout so I can flash new ROMs, but this it really blocking the process.
Click to expand...
Click to collapse
I use this program and it works well. http://we.tl/8gYJ8tgcer