Develop Bugs

[Q] Phone stuck on HTC Logo Help !!!

These are the steps I did & forgot to place rom.zip to sdcard & now I am stuck at the HTC Logo.
1. Unlocked bootloader.
2. Installed CWM Recovery.img
3. Installed Super Swipe from Android HD Rom 6.0 ICS
4. Went into fastboot & done Swipe directly. It erased all the data & now only stuck at HTC Logo.
I tried even
1. Reboot phone and erase cache (Not worked).
2. Install cwm & then custom rom (Not worked).
3. Relock bootloader & install stock rom (Not worked).
4. Installed latest RUU directly (Not worked as my phone has 1.28.720.10)
5. ADB shell mount /sdcard & adb push rom.zip /sdcard (Not worked).
6. Even factory Reset didn't work.
Developers plzz guide needed.....

me too
i'm having the same problem, tried everything... i just updated my rom OTA 1.29.707..... then try to install some roms, then now i'm stock at htc logo...
the last thing i remember is i did a superswipe, then the rest is history...
i can't downgrade either... i guess the solution is to wait for ruu of hTC_Asia_WWE_1.29.707.10 so i can install ruu that will not make error 140...
is there any solution?? please help...

Install the latest CWM recovery with USB storage auto-mounted. Put in any custom rom that you like and install it. Don't forget to flash the boot.img that comes with the custom rom.
To be back on stock, yes you need to wait for the RUU.

urgent help
when i lost the network signal,read from forums that i need to make unlock and as you know install the new custom rom's so i did many times, but still no phone signal,i am living in moscow but phone intended from Poland. Then when i was trying the other roms in the recovery mode wiped away sdcard and system etc.now phone just stuck HTC logo.
Is there a solution or i need to buy a new phone?
best regards.
Saldiray Yildiray Cakmak

i made a thread about this guys.. just follow the instructions
http://forum.xda-developers.com/showthread.php?t=1692681

[Q] Stuck on white htc screen after flashing custom rom

I know that there are similar thread's on this forum but I didn't find solution anywhere.
A couple of days ago I rooted my htc desire hd (android 2.3.5). After that I tried to flash several custom roms (http://forum.xda-developers.com/showthread.php?t=1876127 ; http://forum.xda-developers.com/showthread.php?t=1839004 ; http://forum.xda-developers.com/showthread.php?t=840040). I entered recovery (btw I have clockworkmod 5.0.1.0), wiped data/factory reset, wiped cache partition and wiped dalvik cache. Then i installed custom rom. I rebooted my phone and it stuck on htc bootscreen for several hours.
If anyone has even some idea what to do, please post it. Tnx

Did you make your phone Radio S-Off and ENG S-Off?

onlinsanity said:
Did you make your phone Radio S-Off and ENG S-Off?
Click to expand...
Click to collapse
no, tnx, i'll try that

Wait. The S-Off tool, AAHK, has been retired. You need to fastboot flash a EDIT: boot.img. Instructions are in post #7 of the the link in my signature. You need to do this each time you flash a ROM.

If you're s-on the procedure is to install the rom with whatever recovery you are using then you have to fastboot flash the roms boot.img
With s-on the boot.img cannot be flashed by the recovery.
Extract the boot.img from the rom zip and fastboot flash the boot.img from your pc
Hope this helps
Stu

if non of these works..try clearing cahe and dalvik after flashing the ROM
if not..try another ROM !

PHOENIX-9 said:
if non of these works..try clearing cahe and dalvik after flashing the ROM
if not..try another ROM !
Click to expand...
Click to collapse
Hi i have the exactly same problem. Rooted my stock DHD by easy root tool. so its unlocked but s-on(not that it should matter?)
I om on CMW touch from this forum and tried first to install Viper. but in aroma when i choose full wipe It stops in the installer and says innstall finish.
The only way it will install is to choose dirty install. then it installs but I'm stuck on HTC boot screen (the withe one)
I we tried to wipe cache. Dalvik. Factory. Mounted and un mounted everything. Different SD card. different CMW recovery, Fix recovery+++
Tried to find a versjon of ext4 zip that i can flash from cmw recovery i use now but havent found anything.
Iwe tried ruu but it says that it dosent support my rom.
Iwe gone back to ginger bread with android revolution 6.5.
But NOTHING helps nothing gets me past this F.......G boot screen.
My phone is bricked ? and I'm considering flushing it down the toilet =/
Coming from samsung and several years of flashing I always had ODIN to rely on if something went on.
This is my first HTC and it will be the last if i dont manage to fix this.
Please help me . and please explain it simple- to a htc noob.
Thanks

It Worked!!!
stuuk said:
If you're s-on the procedure is to install the rom with whatever recovery you are using then you have to fastboot flash the roms boot.img
With s-on the boot.img cannot be flashed by the recovery.
Extract the boot.img from the rom zip and fastboot flash the boot.img from your pc
Hope this helps
Stu
Click to expand...
Click to collapse
Man you are AWESOME !!!...I was stuck for 5 days with this stupid White Screen on my Karbonn a21 After flashing custom rom....just booted into fastboot mode...flashed boot.img of another custom rom (Darkboid)...and checked the "erase old boot .img"(or something like that) before flashing new boot.img...:good:

[Q] Htc one m8 stuck on logo1

Basically I'm stuck. Phone won't boot.....I can get to the white screen/bootloader.
It had a custom recovery on it (TWRP) so wonuldn't update....I followed a video to put the stock recovery on it.
I've downloaded a few files, stock recovery, stock boot etc.....put on sd card but no joy. It says reading sd card.....then "no image or wrong image"
In all honesty i'm so lost...Has anyone ever over come this???

vtec3483 said:
Basically I'm stuck. Phone won't boot.....I can get to the white screen/bootloader.
It had a custom recovery on it (TWRP) so wonuldn't update....I followed a video to put the stock recovery on it.
I've downloaded a few files, stock recovery, stock boot etc.....put on sd card but no joy. It says reading sd card.....then "no image or wrong image"
In all honesty i'm so lost...Has anyone ever over come this???
Click to expand...
Click to collapse
What are you trying to do in the first place?
If you're going to flash a custom rom, place the rom in your SD card or internal storage, do a full wipe and install the rom.
If you're returning to stock for OTA, restore your nandroid backup (system, kernel etc) after which flash your stock recovery and do a reset from settings than search for OTA.
If you can't boot into recovery, flash the latest TWRP on your phone through fastboot. Use the commands: fastboot flash boot boot.img

Bobbi lim said:
What are you trying to do in the first place?
If you're going to flash a custom rom, place the rom in your SD card or internal storage, do a full wipe and install the rom.
If you're returning to stock for OTA, restore your nandroid backup (system, kernel etc) after which flash your stock recovery and do a reset from settings than search for OTA.
If you can't boot into recovery, flash the latest TWRP on your phone through fastboot. Use the commands: fastboot flash boot boot.img
Click to expand...
Click to collapse
dude i know you are trying to help but please get your facts right and complete !
flashing a recovery image to the boot partition is not helping !!!
it's : fastboot flash recovery recovery.img

Mr Hofs said:
dude i know you are trying to help but please get your facts right and complete !
flashing a recovery image to the boot partition is not helping !!!
it's : fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Bobbi lim said:
What are you trying to do in the first place?
If you're going to flash a custom rom, place the rom in your SD card or internal storage, do a full wipe and install the rom.
If you're returning to stock for OTA, restore your nandroid backup (system, kernel etc) after which flash your stock recovery and do a reset from settings than search for OTA.
If you can't boot into recovery, flash the latest TWRP on your phone through fastboot. Use the commands: fastboot flash boot boot.img
Click to expand...
Click to collapse
It had a custom recovery on it Team win recovery project......which was stopping the software from updating.
So tried to put the stock recovery back on it.
At the moment I don't think its corresponding properly with my laptop......in the fastboot menu it does come up "fastboot usb" Drivers are installed too
But when trying to send it commands via command prompt it keeps saying device not found.
I'm wondering if it has deleted to operating system , as on the fastboot menu next to " OS - it says nothing "
Sorry for being brief....this is the first time i've ever come across all this stuff

Boot loop issue

Hey guys, I just recently got some parts for my old One X to start playing with it again (bored with ios). I was running an older version of ViperXL and wanted to get lollipop so my goal was to put CM12.0 on my phone. My recovery was twrp but a version that was older so I had to update it. The in app update wasn't working so I updated cwm instead. When I did this I tried to boot to recovery and it would attempt to go to recovery but then boot back to the os.
Then I was trying to flash the recovery using fastboot which resulted in the same problem. Somewhere in there I flash the recovery.img as my boot image (sudo fastboot flash boot recovery.img) This made my phone repeatedly try to boot into recovery. I tried flashing new ViperXL boot.img as well as a couple others but none let me get into my os again. Now it is just a bootloop trying to start my phone up.
When I try flashing a .zip I get the error 'FAILED (remote: not allowed)'. Flashing recovery and boot images work though.
I've tried a lot and done a lot of searching but nothing can get me into recovery or even out of any sort of bootloop.
I'm using Ubuntu and my phone is S-On if that means anything.
Thanks!

Try restoring any backups of old roms from the recovery. Make sure Recovery is written properly in recovery partition. If this works fine , the appropriate boot.img shud be automatically flashed , i guess.
If u dont have a backup , try finding another one x user using a custom recovery, create a backup from his mobile and copy it to ur sd card by mounting it thru recovery and restore it.
If it doesnt work , wipe all the partitions - System , cache, boot and recovery.. then try flashing a Recovery and then a Boot.img and a rom.
I havent faced such a situation. Just my suggestions as no experts have responded.
Cheers if u have already sorted it out !!!

M8s stuck in bootloader

Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!

Hi McBad,
you could try the following. I also had some problems to access the recovery.
- Again bring the phone into fastboot, flash the 2.8 recovery and access it
- Do a wipe for factory reset, not just only cache
- after that try to flash the twrp-3.0.1-0-m8ql.img version, the other one worked for me neither
- the try to install the custom ROM LOS13
I hope this will help you.
clone

It would be great if that would work, but flashing a recovery does not work. I flash it, success message, try to access it, vibrates and bootloader pops back instantly. That is the problem.

Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!

Have you tried sideloading twrp ?

McBad said:
Sorry for double post, but can anyone help me with this? This is the second day I struggle to make it work. Any chance to make the hboot locked again? It didn't work with oem lock command. I would like to lock it so I can put an official zip on sdcard so the hboot to restore it to factory stock, some RUU. Or get it s-off so I can flash a rom from fastboot? The phone does not have any ROM on it, image crc results system 0x0, recovery 0x0. Please, help!
Click to expand...
Click to collapse
Did you use HTC fastboot ?

Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.

McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Is there any way you could flash twrp 2.8 again? Once in that recovery you have sideloading option which you could use to transfer latest recovery onto your device. Are we talking about the same process?

McBad said:
Yes, I used htc_fastboot. Use sideloading? Like boot the img file directly? Tried that too.
Click to expand...
Click to collapse
Sideload as follows ....

McBad said:
Hello everyone. I got a M8s from a friend wich is stuck in bootloader. The recovery didn't work at the begin, so I flashed twrp-recovery-2.8.6.0-m8s-qlul.img (flashing recovery using htc_fastboot.exe flash recovery theimagename.img) and it worked, then I tried to install a custom ROM Android_Pandora_Rom_1.2_(Discontinued).zip wich went all the steps fine until: Optimizing applications 8 of 204..then phone shat down to black screen. I booted back to bootloader, recovery, wiped and go for a new install, same issue.
After that, I was going to install lineage-13.0-20170715-UNOFFICIAL-m8qlul.zip where the developer of this rom recommends twrp-3.0.2-0-m8ql.img so I tried to flash it (flashing recovery using htc_fastboot.exe flash recovery theimagename.img), then tried to acces recovery, brings me back to bootloader so fast, rebooted bootloader, tried again, same problem. Tried the fasboot erase cache, no help.
The Hboot state is Unlocked and the S is ON. I tried some other recovery images, as stock_signed or 3.0.1, tried the one from M8 ToolKit but all failed and I still can't access recovery, everyting I do, it brings me back to bootloader. I did htc_fastboot boot recoveryfile.img wich works, but useless, the dd if= method to set the recovery permanent load did not work after reboot, /data and /system can't be mountet, it seems the "boot recovery" option is 99% readonly.
Any advice, any help please? It would be much appreciated! Thanks in advance!
Click to expand...
Click to collapse
You can't install lineage if you haven't upgraded your device with latest official update. I would try reinstaling twrp 2.8, do a wipe of cache, dalvik cache and system, Sideload CM 12; and see how it goes. As well, while in twrp I would try relocking bootloader but only after an unsuccessful attempt to flash said rom. I don't know what your experience with soft bricked devices is, but sometimes it takes a while, different usb cable or usb slot on your PC, correct files in adb folder, re-download of rom or recovery because it easily gets corrupted while downloading. And obviously a fully charged device. Let us know how it goes.